Tool was not driven

dc42

If you reboot (with the M665 line in config-override.g removed) and then send M665 without parameters, does it report 3 rod lengths or 4?

skayred

@dc42 3 length reported in that case.

dc42

If you now run auto calibration, does it report 3 or 4 after that?

skayred

@dc42 Surprisingly 3 lengths still o_O While config-override is not updated

15:57:53 M665
Diagonals 209.000:209.000:209.000, delta radius 91.146, homed height 203.228, bed radius 100.0, X -0.626°, Y -1.399°, Z 0.000°
15:57:44 G32
Calibrated 8 factors using 10 points, deviation before 0.324 after 0.009
15:57:12 G28
15:56:41 M665
Diagonals 209.000:209.000:209.000, delta radius 91.500, homed height 203.000, bed radius 100.0, X 0.000°, Y 0.000°, Z 0.000°

dc42

@skayred said in Tool was not driven:

@dc42 Surprisingly 3 lengths still o_O While config-override is not updated

15:57:53 M665
Diagonals 209.000:209.000:209.000, delta radius 91.146, homed height 203.228, bed radius 100.0, X -0.626°, Y -1.399°, Z 0.000°
15:57:44 G32
Calibrated 8 factors using 10 points, deviation before 0.324 after 0.009
15:57:12 G28
15:56:41 M665
Diagonals 209.000:209.000:209.000, delta radius 91.500, homed height 203.000, bed radius 100.0, X 0.000°, Y 0.000°, Z 0.000°

So does it auto calibrate now without those error messages?

config-override.g will only be updated if you send M500.

skayred

@dc42 yes, cold calibration was without warnings, 40C both hotend and bed as well, now I am going to try an actual Gcode

skayred

@dc42 yes, it solved also the printing problem. So, in short - if 4th arm is configured, some mechanism prevents the printer from actual printing due to triggering of heater failure

droftarts

@skayred With the fourth arm configured, it's trying to map a driver to it, and erroneously mapping the extruder. Which generates the warning when it's asked to move as the U axis. I'm a little surprised that it does this, but we should test in the latest firmware versions and see if it still does this, and raise it as a bug if it does. I note you're running RRF 2.04, you should consider updating to the latest RRF 2 version, 2.05.1.

I expect if you'd kept the M584 you originally had, with the U axis defined, it would probably have been okay! Feel free to test...

Ian

skayred

@droftarts will test for sure but before I need to reprint the carriage Due to heavyweight of Titan with its default stepper, my 'arm' for flying extruder probably tilted LM8UU too much so extruder carriage stopped while effector continued its movement... Yeah, it was loud.

And about bug - pretty easy to reproduce. Set 4th arm in the delta configuration, set some temperature (hotend only should be fine but better both), then run let's say G32. If there is no warning, try some print - in my case it looked like extreme underextrusion or filament clog.

dc42

I've fixed it in RRF 3.01-RC3 so that you can only specify as many rod lengths as there are axes. This means that the M584 command to create the additional axes will need to be earlier in config.g than the M665 command.