Following up David Lang’s comment:
I wrote a short code to try out relative movements as it doesn’t make sense when loaded into Maslow. The code is
; set incremental mode
g21
g91
g17
g40
g1 x0 y0 f2000 ; Start at bottom left
g1 x100 ; Move right 100mm
g1 y100 ; Move up a 100mm
g1 x-200 ; Move left 200mm
g1 y100 ; Move up a 100mm
g1 x200 ; Move right 200mm
On Maslow
and the simulator
Ian Abbott wrote:
Following up David Lang¢s comment:
I wrote a short code to try out relative movements as it doesn¢t make sense when loaded into Maslow. The code is
; set incremental mode
g21
g91
g17
g40g1 x0 y0 f2000 ; Start at bottom left
g1 x100 ; Move right 100mm
g1 y100 ; Move up a 100mm
g1 x-200 ; Move left 200mm
g1 y100 ; Move up a 100mm
g1 x200 ; Move right 200mmOn Maslow
and the simulator
The question is if this is only in the browser simulator, or in the firmware.
what does the machine do in the real world
In the real world it works, i.e. it followed the programmed path. So there is a problem in the browser simulator, not the firmware.
RelativeMovements.wmv (527.7 KB)
Added a G90 at the beginning to make sure I started at the home position with test program, then G91 after homing. Rest is relative movements. Without homing, subsequent runs will eventually go out of range (over the edge).
Good catch! It’s possible that the gcode preview does not correctly display relative movements
