It appears that if a gcode program is stopped in the middle, some 
offsets from further down the program are being applied. I ran the test 
program below and stopped it during execution of line 7 (the G1 line). 
After this, when doing MDI movement or restarting the program, the G54 
offset from the G10 line and the tool offset from the next-to-the-last 
line are apparently being used by the machine, even though the program 
was stopped before that. Also, the DRO relative display doesn't include 
these offsets, so the DRO relative display doesn't agree with the machine.

G54 and G92 offsets were all zero before running. Tool 1 has zero Z 
offset in the tool table but tool 7 has a -1.0575" offset.

Am I doing something wrong here? Is this documented somewhere?

Things can be reset by issuing a G43 in MDI mode and resetting the G54 
offset.

This is on version 2.5pre (~4 weeks old). It happens using both the Axis 
and Touchy interfaces.

G54
G17 G90 G20 G98
T1 M6 G43
G0 X3.5 Y-0.75
M03 S1000
G0 Z-0.1
G1 X-1.5 F1
G80
M05
G10 L20 P1 Z0.0
T7 M6 G43
M02

Thanks for any advice.

Karl

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to