Topics created by Thugmek

@Thugmek Thanks for reporting this, I'll work out a fix.

PS: Now fixed on GitHub on v3.4-dev and v3.5-dev.

@Thugmek @Phaedrux Yes, it requires a recent DuetPi image, though. Also it's a good idea to check if the latest DSF packages are installed, recent ones should list external drives as SD card items.

M21 in SBC mode is just a wrapper for the mount utility, it could be used to mount network shares, for example. Possible examples are already documented on the G-codes dictionary page.

@Thugmek No, there is no tool to do sync the OM definitions automatically. I guess you forgot to add your key to the Tool class and if not, perhaps you haven't updated the DCS build on your SBC yet.

@Thugmek with regard to your first question, the Debug build configurations of RRF leave the SWD pins for SWD use. So you should use the Duet3_Debug build configuration for debugging.

The Debug build configurations also enable generation of debug information in the compiler settings, which may go some way towards addressing your second question.

@Thugmek we've never used debuggers with Duet 2. Older version Duet 2 boards do expose the JTAG/SWD pins but newer ones don't. All Duet 3 boards expose the SWD pins.

If the firmware crashes, the crash details are written to flash memory and can be retrieved using M122. We use the linker map file and assembler files generated by the compiler to identify the exact point at which it crashed. We usually find that sufficient to identify the bug.

I'm not a delta user, but isn't it recommended to use 0.9 degree motors for this very reason (among others)?