very dangerous behavior on 3.5.3
-
Hi there is a very dangerous behaviour with userposition and machine position.
I have WCS Z offset (G10 L2 P1 Z40) to avoid collision because I can change the height of my build plate.
When I ask the machine to go the position in a macros for ex
T0
G90
G0 Z50The machine goes well to the userPosition Z50
But if have the same command on the start.g or mesh.g
the machine go to the userposition Z10
In a macro or in the terminal, when you ask for a G90, the machine moves in userPosition, but in start.g and mesh.g the machine moves in machinePosition.
it's only for the Z axis. -
@tom33 thanks for pointing this out.
If you use G53 (https://docs.duet3d.com/en/User_manual/Reference/Gcodes#g53-use-machine-coordinates) how does that impact the behaviour?
-
@tom33 the rule is that workplace offsets and coordinate rotation are not applied when running system macro files, i.e. macros that are run automatically by RRF. This is so that macros for homing, pausing, resuming, tool changing etc. are not messed up by workplace offsets.
-
@dc42 - clarifying question. Is the rule you stated applied based on the location of the macro file in directory tree? And do tool offsets follow this rule?
-
@mikeabuilder macros run automatically by RRF don't have workplace coordinate offsets or coordinate rotation arrived. Macros invoked by M98 do have them applied regardless of where on the SD card they live, unless the M98 call is from a macro that itself doesn't have offsets and rotations applied.
-
@dc42 - thanks for the clarification.
