@Raxtus14 M997 S2 updates the Raspberry Pi. Send M997 or M997 S0 to update the 6HC itself. See https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m997-perform-in-application-firmware-update
For SBC setup, see https://docs.duet3d.com/en/User_manual/Machine_configuration/SBC_setup
Ian
You can re-execute the config.g after the board is powered up in order to configure it. Or have the 3HC config in a separate macro you can call after you've executed PSON.
@3DOeste I understand. No, Duet firmware doesn't do that at the moment. I'm not sure it would be possible over CAN, there would be too much latency. Perhaps raise a feature request for this functionality here https://github.com/Duet3D/RepRapFirmware/issues and @dc42 can look into it.
Ian
@dwuk3d One of the first multicolour prints we did at RepRapPro with the Tri-colour Mendel, around 2013/14, was a Union Flag!
I don't have any pictures of the print, but the files are here: https://github.com/reprappro/Interesting-3D-Prints/tree/master/RRP Union flag2
Our other favourite was the multicolour frog: https://www.thingiverse.com/thing:329436
Ian
@Arkadiusz said in Can't turn off input shaping:
When my printer runs it makes very jittery arc movements and printer seems to ignore jerk and acceleration settings, I got it set to 1mm/min and it still moves very rapidly. Travel jerk is so strong makes motors skip steps.
I don't think that relates to input shaping. Assuming this is happening during a print, it sounds more like the slicer is emitting Gcodes for speed, acceleration and jerk, and overriding what you're setting in config.g. Check the Gcode for M201, M203, M204 and M566 commands, usually near the beginning.
You won't get good arc movement with low jerk settings, though. Usually something in the 5 to 15mm/s gives smooth arcs.
Ian
@3DOeste Duet3D produce a closed loop motor driver board, the Duet 3 Expansion 1HCL, that connects to a Duet 3 mainboard. See https://www.duet3d.com/duet-3-expansion-1hcl
These are integrated into the Duet firmware, so you get a lot more information back than typical closed loop motor drivers.
I'm not sure I understand what you mean by
I mean not only the drivers are closed loop but also the control board and the software
If you mean the spindle control and/or other tools, Duet can control these and read any feedback using RS485/Modbus, which is supported on 6HC/6XD mainboards with newer firmware versions. EtherCat is not supported.
Ian
@Tinchus the state of a heater can be off, active, standby, or one of a number of tuning states. The 'active' state means that RRF is attempting to maintain the configured active temperature. That's why the OM does not report it as active during tuning.
@ironhydroxide thanks for your feedback.
Regarding getting encoder counts back from the 1HCL boards, unfortunately it is quite a large change involving all f the 1HCL firmware, the CAN message format and the main board firmware. Firmware 3.6 is too close to release for us to consider adding it before then. Perhaps you would like to create a feature request at https://github.com/Duet3D/RepRapFirmware/issues.
@kazolar was that M122 report taken after the problem with driver 5 occurred, or before?
@DuetUser if a motor vibrates instead of moving, that usually means that only one of the phases is being energised. Possible reasons include:
In cases 1 and 2 the Drivers section of the M122 report should report the error. So if it happens again, run M122 before restarting.
