Topics created by nickpm

Looks like you are running an out-of-date version of Duet Web Control.

Nevermind I fixed it, was a client issue.

@dc42 As always you're on point! Thanks I added an M208 in my home macros just in case.

You guys rock!

@nickpm said in Can't get any IO to work on Duex with RRF3:

M950 F5 C"fan5"

https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Pin_names_for_Duet_2_WiFi_Ethernet

I guess the right pin name would be "duex.fan5"

type can be 1 through 4 with varying levels of detail. There is also rr_config.

Until the documentation is complete, here are two suggestions.

Suggestion 1: use M409 to enumerate all kayes.

Send M409 F"v". That will return a list of the root keys in "result". For each root key, send M409 K"xxx" F"v" where xx is the key. That will return the whole subtree in "result". Paste it into https://codebeautify.org/jsonviewer to make it easier to navigate.

Ask about any keys that you find in the response that you need further information about.

Note, some keys are only present when the printer is in a certain state, for example printing from SD card.

Suggestion 2: get the information fro the DSF documentation.

Go to https://github.com/chrishamm/DuetSoftwareFramework and clone it to your machine Navigate to and open docs/index.html in that tree Follow the link to DuetAPI, then expand DuetAPI.Machine, then click on MachineModel. You will find all the keys listed under Properties. A few of them (e.g. HttpEndpoints and UserSessions) exist in DSF only, not in RRF.

Duet 3 to Expansion: Duet 3 6HC main to 3HC expansion is RJ11. Use good cables. One way to get that from the retail channel is to order cables advertised as "high speed" (without getting into exotic BS).

The main has one connector, the expansion two, for chaining. The expansion has physical switches for its CAN address. The main is always zero, the first expansion is normally 1 (but could be something else if you wish), etc. The second 2, etc.

Tool boards are more complicated. See https://duet3d.dozuki.com/Wiki/Duet_3_Tool_Board#Section_Commissioning_a_new_Tool_Board

In reality, you will spend a few minutes wiring the CAN and setting addresses. Most all of your time will go into other wiring and configuration.

Are you going to run a Pi? Or stand-alone?

@dc42 Yup that was it, I'm just gonna pass through the enable signals through to the stepper drivers on the Duex and set the external stepper drivers to be active low enable.

@nickpm your pronterface connection problem: maybe you need M555 P2 according to https://forum.duet3d.com/topic/6956/cannot-connect-through-pronterface

In newer firmware M555 P2 is the default, but your firmware may be older.

You can tap into the expansion bus if you clamp a third 50-way connector on to the ribbon cable. However, if you have a DueX5 connected then the firmware will assume that all the drivers connected to it are TMC2660 and will try to drive them accordingly.

If you use a DueX2 then you can drive 3 external stepper drivers using the unused motor signals on the expansion bus.

You can also connect 2 external stepper drivers to the CONN_LCD connector.

As others have said, M28 ignores comments in commands. Like you can (probably, I haven't tried) send console commands with comments, but they are lost as soon as the command is sent.

I can see why you might want to do this (maybe for logging?), but it's probably easiest to write the gcode file in a text editor, then send each line by copying and pasting that into your terminal program (I assume that's how you're connecting). Then you'd have a local editable copy of the file from the SD card, with comments. Or remove the SD card from the Duet, copy the file onto it locally, then replace it in the Duet.

Ian

Is it possible to change the firmware to allow it to monitor the stall detection under manual moves as well as regular moves.