Custom Drive Mapping stopped working
-
@propellerhat Oh yes, I tried also putting the custom mapping in the macros and commanding it separately after the startup. No effect.
-
@propellerhat Also tried without the tool configurating and with only the tools that were working configurated in the config.g before the changes. No help.
-
I also moved the M208 next to movement lines but no help.
-
Just wondering.... M584 defines 3 extruders, for drives 2, 3 and 4. In many places the E parameter is followed by 4 values, like the M350 and M92 codes. Have you tried insuring that you don't have more than 3 values for any E parameter present in the file?
-
Removed now all the extra E parameters from M566,M203 and M201. Also the tools are cleaned from everything else than T8.
Still same behaviour
-
Now updated the firmware to 1.21. It has been a while since updating it. After the successfull in-app update from the SD card nothing moves.
-
Now when trying to move the axes I get this in the console: "G0/G1: insufficient axes homed"
-
Firmware 1.21 requires all axis to be homed before allowing movements in order to properly enforce actual machine area. There are workarounds, just search the forum.
-
M564 H0 got the things in movement, pity that exactly the same problem remains as before updating.
Drive custom mapping doing nothing.
-
If you run M584 from the command line, what does it report?
-
Oh heck... Just found the flat between Duet and Duex being a tad loose. Stuff making a lot more sense now after pushing that corner in.
