1661
Mach4 General Discussion / Re: Machine thinks plate is off table. Confused. Please help
« on: March 06, 2020, 02:53:13 PM »
Hi,
I would start by stripping the program down to its basics and adding lines until the fault occurs.
For example:
I have stripped the code down to the one operation.
What do M1100, M1111 and M115 do? Are you sure that one of these macros is not causing an overlimit excursion?
By the way, the Mach4 Gcode interpreter converts all Gcode to lowercase, strips out leading zeros and whitespace so
the interpreter is looking for m1100, m1111 etc. In most cases because Windows is case insensitive it will provide the
correct macro but you should get into the habit of writing ALL Gcode in lowercase. There are occasions when Mach will not
get the correct code because of the uppercase/lowercase thing and its a devilishly hard fault to pick.
The next issue is that I see your post has inserted a G91.1 line to ensure incremental arc mode. Is your machine set up that way?
If there is a clash of arc mode interpretation between the Gcode and the machine overlimit excursions are not unlikely.
Having said that the tool path display usually shows an errant tool path. Does in fact the tool path display show the
overlimit excursion?
You might test this theory by commenting out the 'G03 X5.9005 Y2.0601 I0.1205 J0.2399' line and running the program fragment
without it.
Craig
I would start by stripping the program down to its basics and adding lines until the fault occurs.
For example:
Code: [Select]
G20 (Units: Inches)
G90
G91.1
M1100
M1111
G00 X5.8502 Y2.2120
(Part: 1056.nc)
(Layer: Holes Pierce#: 1)
(Run From Here Start Point)
M1115
M14 A0 B30 C1
G01 X5.8880 Y2.0980
G01 X5.9005 Y2.0601
G03 X5.9005 Y2.0601 I0.1205 J0.2399
G01 X5.9641 Y2.0680
M15 A0 B30 C1
M01
G00 X2.8502 Y2.2120
m30
I have stripped the code down to the one operation.
What do M1100, M1111 and M115 do? Are you sure that one of these macros is not causing an overlimit excursion?
By the way, the Mach4 Gcode interpreter converts all Gcode to lowercase, strips out leading zeros and whitespace so
the interpreter is looking for m1100, m1111 etc. In most cases because Windows is case insensitive it will provide the
correct macro but you should get into the habit of writing ALL Gcode in lowercase. There are occasions when Mach will not
get the correct code because of the uppercase/lowercase thing and its a devilishly hard fault to pick.
The next issue is that I see your post has inserted a G91.1 line to ensure incremental arc mode. Is your machine set up that way?
If there is a clash of arc mode interpretation between the Gcode and the machine overlimit excursions are not unlikely.
Having said that the tool path display usually shows an errant tool path. Does in fact the tool path display show the
overlimit excursion?
You might test this theory by commenting out the 'G03 X5.9005 Y2.0601 I0.1205 J0.2399' line and running the program fragment
without it.
Craig