GCode Stops Running

[oakfordhome]

Hi all,

I'm hoping someone might have some advice with my problem.  My gcode was generated through Fusion 360 and I'm using UGS to read the gcode.  My machine is the M3.

For a specific 2d pocket operation that I'm working on, the job stops at the same line of gcode every time I run the machine.  It doesn't error out or crash, it just gets to this one line of code and stops moving.  I tried running it 3 separate times and each time it stops at the same line of code.

I've ran other similar operations as recent as yesterday with no issues.  I'm assuming it's something specific with the line of code that it stops at.  I'm not very versed in Gcode, just the basics, but the line of code looks like any other to me.

Below is the gcode from the start until the point where it stops moving...note, I bolded, underlined, and italicized the last line of code that the machine reads before it stops moving.  I included the next line as well in case that helps.

I'm still new to CNC, so if there's other information that would be helpful in troubleshooting, please let me know.

Thanks so much!!

Sam
___

%

(1001)

(T1 D=0.25 CR=0 - ZMIN=-1.25 - flat end mill)

G90 G94

G17

G20



(2D Pocket1)

G0 X3.5673 Y-4.7939

Z0.6

Z0.2

G1 Z-0.105 F50

X3.5674 Y-4.7936 Z-0.1085

X3.5676 Y-4.7927 Z-0.1118

X3.568 Y-4.7913 Z-0.115

X3.5685 Y-4.7894 Z-0.1179

X3.5691 Y-4.787 Z-0.1203

X3.5699 Y-4.7842 Z-0.1223

X3.5707 Y-4.7812 Z-0.1238

X3.5715 Y-4.7779 Z-0.1247

X3.5724 Y-4.7745 Z-0.125

X3.6109 Y-4.63

G2 X3.8083 Y-4.1962 I1.3891 J-0.37

G1 X3.8088 Y-4.1954

X3.8107 Y-4.1925 Z-0.1247

X3.8126 Y-4.1897 Z-0.1238

X3.8144 Y-4.1871 Z-0.1223

X3.816 Y-4.1847 Z-0.1203

X3.8174 Y-4.1827 Z-0.1179

X3.8185 Y-4.181 Z-0.115

X3.8193 Y-4.1798 Z-0.1118

X3.8198 Y-4.179 Z-0.1085

X3.82 Y-4.1788 Z-0.105

G0 Z0.2

X3.3327 Y-4.8865

G1 Z0.1394 F35

Z-0.105 F50

Y-4.8862 Z-0.1085

X3.3328 Y-4.8853 Z-0.1118

X3.3329 Y-4.8838 Z-0.115

X3.3331 Y-4.8818 Z-0.1179

X3.3333 Y-4.8794 Z-0.1203

X3.3335 Y-4.8765 Z-0.1223

X3.3338 Y-4.8734 Z-0.1238

X3.3341 Y-4.87 Z-0.1247

X3.3343 Y-4.8666 Z-0.125

X3.3345 Y-4.8646

G2 X3.8084 Y-3.8285 I1.6655 J-0.1354

G1 X3.8091 Y-3.8278

X3.8115 Y-3.8253 Z-0.1247

X3.8139 Y-3.8229 Z-0.1238

X3.8161 Y-3.8207 Z-0.1223

X3.8181 Y-3.8187 Z-0.1203

X3.8198 Y-3.8169 Z-0.1179

X3.8212 Y-3.8155 Z-0.115

X3.8223 Y-3.8144 Z-0.1118

X3.8229 Y-3.8138 Z-0.1085

X3.8231 Y-3.8136 Z-0.105

G0 Z0.2

X4.1057 Y-3.3184

G1 Z0.1394 F35

Z-0.105 F50

X4.1059 Y-3.3183 Z-0.1085

X4.1067 Y-3.3179 Z-0.1118

X4.108 Y-3.3172 Z-0.115

X4.1098 Y-3.3163 Z-0.1179

X4.112 Y-3.3151 Z-0.1203

X4.1145 Y-3.3138 Z-0.1223

X4.1173 Y-3.3124 Z-0.1238

X4.1203 Y-3.3108 Z-0.1247

X4.1234 Y-3.3092 Z-0.125

X4.1252 Y-3.3083

G2 X4.6258 Y-3.1326 I0.8748 J-1.6917

G1 X4.6268 Y-3.1324

X4.6302 Y-3.1317 Z-0.1247

X4.6335 Y-3.1311 Z-0.1238

X4.6366 Y-3.1305 Z-0.1223

X4.6394 Y-3.1299 Z-0.1203

X4.6418 Y-3.1294 Z-0.1179

X4.6438 Y-3.129 Z-0.115

X4.6452 Y-3.1287 Z-0.1118

X4.6461 Y-3.1286 Z-0.1085

X4.6464 Y-3.1285 Z-0.105

G0 Z0.2

X5.223 Y-3.1024

G1 Z-0.105 F35

X5.2233 Z-0.1085 F50

X5.2242 Y-3.1026 Z-0.1118

X5.2256 Y-3.1029 Z-0.115

X5.2276 Y-3.1033 Z-0.1179

X5.23 Y-3.1038 Z-0.1203

X5.2328 Y-3.1043 Z-0.1223

X5.2359 Y-3.1049 Z-0.1238

X5.2392 Y-3.1056 Z-0.1247

X5.2426 Y-3.1063 Z-0.125

X5.3738 Y-3.1325

G2 X5.8749 Y-3.3083 I-0.3738 J-1.8675

[Derek the Admin]

It can be pretty hard to pin down something like that. I see no reason why it would stop there.

Does it always stop right there?

[tgattis]

I've had some screwy issues with UGS and my code as well, trying to face a 609 X 609 mm spoilboard and after setting the WCS to the lower left top surface, positioned the tool at that point and send it, the machine goes 15-20mm in the Y axis then goes -X till the ballscrew mount hits the mount, it shows it going in X axis on the visualizer and on the tool path simulation...I still have no clue why. Then I go to jog the machine and can click the direction button 3-4 times and nothing happens, click with my keyboard and it'll take off 3-4 times the inputed distance...

[Bruce]

I was using a old laptop (11 years old) and was getting flakey reliability running larger jobs. Then it got worse only running a few lines of code before it would stop. I switched to my new laptop and it runs rock solid (bCNC on Win10, 2 year old laptop) Even though the resource requirement is low running UGS or bCNC, I think the newer USB hardware is important for a reliable connection. I want to setup a Raspberry Pi with bCNC one of these days.

[oakfordhome]

Thanks all for the replies!

Derek - yep, it stops at the same exact line of code each time for some reason.

Tgattis - same thing here, the simulation runs fine in Fusion 360, no collisions, no issues until I actually try running it.  Maybe there's another program instead of UGS that would be better?

Bruce - that's a good thought, the laptop I'm using is definitely almost 10 years old at this point, though it does have Windows 10 and I've run similar intensive jobs before without issue, so not sure why this one would be different.

Any other thoughts on troubleshooting would be great.

Thanks again!

Sam

[Bruce]

Well an option is to modify the G-Code, just remove or comment out that line of code that it stops at. Dry run the code on the machine without an endmill in the router. See if it stop at the next line or if it goes on from there.

[oakfordhome]

Thanks Bruce, I'll give that a try today!

[Derek the Admin]

I just don't see why it would stop there. It could be some glitch that won't present itself again.

The only other thing I could think of is if you have soft limits enabled. It looks like that's the greatest X value you have up to that point. If you have enabled them this might be the problem.

[Bruce]

Oh, that's a good point Derek. Post the machine settings for us to check. Go to the UGS console window and type $$ and copy the result here.

[oakfordhome]

Here are the results of $$...


$0 = 10 (Step pulse time, microseconds)
$1 = 255 (Step idle delay, milliseconds)
$2 = 0 (Step pulse invert, mask)
$3 = 0 (Step direction invert, mask)
$4 = 0 (Invert step enable pin, boolean)
$5 = 0 (Invert limit pins, boolean)
$6 = 0 (Invert probe pin, boolean)
$10 = 1 (Status report options, mask)
$11 = 0.010 (Junction deviation, millimeters)
$12 = 0.002 (Arc tolerance, millimeters)
$13 = 0 (Report in inches, boolean)
$20 = 0 (Soft limits enable, boolean)
$21 = 0 (Hard limits enable, boolean)
$22 = 1 (Homing cycle enable, boolean)
$23 = 0 (Homing direction invert, mask)
$24 = 25.000 (Homing locate feed rate, mm/min)
$25 = 1000.000 (Homing search seek rate, mm/min)
$26 = 44 (Homing switch debounce delay, milliseconds)
$27 = 4.000 (Homing switch pull-off distance, millimeters)
$30 = 12000 (Maximum spindle speed, RPM)
$31 = 0 (Minimum spindle speed, RPM)
$32 = 0 (Laser-mode enable, boolean)
$100 = 40.000 (X-axis travel resolution, step/mm)
$101 = 40.000 (Y-axis travel resolution, step/mm)
$102 = 80.000 (Z-axis travel resolution, step/mm)
$110 = 8000.000 (X-axis maximum rate, mm/min)
$111 = 8000.000 (Y-axis maximum rate, mm/min)
$112 = 3000.000 (Z-axis maximum rate, mm/min)
$120 = 250.000 (X-axis acceleration, mm/sec^2)
$121 = 250.000 (Y-axis acceleration, mm/sec^2)
$122 = 250.000 (Z-axis acceleration, mm/sec^2)
$130 = 264.000 (X-axis maximum travel, millimeters)
$131 = 264.000 (Y-axis maximum travel, millimeters)
$132 = 69.000 (Z-axis maximum travel, millimeters)
ok

[Bruce]

Hard and soft limits looks good (=0).
These are the defaults for settings $25 and $26:

$25=600.000 (homing seek, mm/min)
$26=244 (homing debounce, msec)

I don't think this has anything to do with the problem, but you have $25=1000.0 and $26=44
You should increase the debounce delay to the $26=244. I'm not sure if you are pushing it too hard with 1000mm/min homing search rate.

Everything else is the default setting.