RS-CNC pausing / stopping sporadically

[SebastianM]

Hey guys,
I finished my CNC some weeks ago but I still didnt mill any "real parts" cause I am still waiting for the flutes from china.

However, I tried to run some gcodes without any flute. In general, its working fine. But yesterday I tried a very "complex" gcode (67 MB file) and the machine just stopped / paused after some minutes. 4 Minutes later, it moved a few cm, then it stopped again.

When I paused the process by touchscreen, the machine responded (Z moved up and down again) - so it hasn't freezed / hung up.
The elapsed time in the TFT also counts up...

It seems as the controller was kind of "stuck" in die gcode.
Are there any limitations regarding gcode "complexity" / number of lines in the file?

The gcode was generated by estlcam (marlin profile).




thx in advance

[Steve H]

Hi, I’m not familiar with Estlcam but are you using the right post processor to create the gcode?


Sent from my iPad using Tapatalk

[mstrens]

There is no limit in the size of the Gcode files as far I know.

[SebastianM]

Yes, I used the correct postprocessor.

Is there a possibility to debug the CNC while its working? Can I get a serial output?

I ran this gcode 4 times. It stopped 3 times but worked once.

Help ?!

[SebastianM]

Hello,
I ran the same gcode with repetier-host over usb. The problem is the same - the proccess stopps at a certain time.

The log shows that the commands are sent continuously (green) by my computer, but the CNC just stays at the same position over and over again (red). But its alive, it has not freezed.

Help... ?

< 09:16:36: ok 4959
< 09:16:36: X:111.40 Y:43.73 Z:0.005 E:0.0000
> 09:16:36: N4963 G1 X108.02 Y44.07 Z-0.963 *120
< 09:16:36: ok 4960
< 09:16:36: X:111.40 Y:43.73 Z:0.005 E:0.0000
> 09:16:36: N4964 G1 X108.10 Z-0.937 *45
< 09:16:36: ok 4961
< 09:16:36: X:111.40 Y:43.73 Z:0.005 E:0.0000
> 09:16:36: N4965 G1 X108.18 Y44.06 Z-0.915 *117
< 09:16:36: ok 4962
< 09:16:37: X:111.40 Y:43.73 Z:0.005 E:0.0000
> 09:16:37: N4966 G1 X108.25 Y44.03 Z-0.902 *123
< 09:16:37: ok 4963
< 09:16:37: X:111.40 Y:43.73 Z:0.005 E:0.0000
> 09:16:37: N4967 G1 X108.32 Y43.98 Z-0.902 *121
< 09:16:37: ok 4964
< 09:16:37: X:111.40 Y:43.73 Z:0.005 E:0.0000
> 09:16:37: N4968 G1 X108.39 Y43.93 Z-0.914 *113
< 09:16:37: ok 4965
< 09:16:37: X:111.40 Y:43.73 Z:0.005 E:0.0000
> 09:16:37: N4969 G1 X108.44 Y43.86 Z-0.937 *127
< 09:16:37: ok 4966
< 09:16:37: X:111.40 Y:43.73 Z:0.005 E:0.0000
> 09:16:37: N4970 G1 X108.47 Y43.78 Z-0.963 *116
< 09:16:37: ok 4967
< 09:16:37: X:111.40 Y:43.73 Z:0.005 E:0.0000
> 09:16:37: N4971 G1 X108.50 Y43.70 Z-0.985 *115
< 09:16:37: ok 4968
< 09:16:37: X:111.40 Y:43.73 Z:0.005 E:0.0000
> 09:16:37: N4972 G1 X108.51 Y43.62 Z-0.998 *126
< 09:16:37: ok 4969
< 09:16:37: X:111.40 Y:43.73 Z:0.005 E:0.0000
> 09:16:37: N4973 G1 X108.50 Y43.53 Z-0.998 *124
< 09:16:37: ok 4970
< 09:16:37: X:111.40 Y:43.73 Z:0.005 E:0.0000
> 09:16:37: N4974 G1 X108.48 Y43.44 Z-0.985 *120
< 09:16:37: ok 4971
< 09:16:37: X:111.40 Y:43.73 Z:0.005 E:0.0000
> 09:16:37: N4975 G1 X108.45 Y43.36 Z-0.963 *121
< 09:16:37: ok 4972
< 09:16:37: X:111.40 Y:43.73 Z:0.005 E:0.0000
> 09:16:37: N4976 G1 X108.40 Y43.28 Z-0.937 *113
< 09:16:37: ok 4973
< 09:16:37: X:111.40 Y:43.73 Z:0.005 E:0.0000
> 09:16:37: N4977 G1 X108.34 Y43.22 Z-0.915 *121
< 09:16:37: ok 4974
< 09:16:37: X:111.40 Y:43.73 Z:0.005 E:0.0000
> 09:16:37: N4978 G1 X108.26 Y43.16 Z-0.902 *116
< 09:16:37: ok 4975
< 09:16:37: X:111.40 Y:43.73 Z:0.005 E:0.0000
> 09:16:37: N4979 G1 X108.18 Y43.12 Z-0.902 *124
< 09:16:37: ok 4976
< 09:16:37: X:111.40 Y:43.73 Z:0.005 E:0.0000
> 09:16:37: N4980 G1 X108.10 Y43.09 Z-0.914 *127
< 09:16:37: ok 4977

[Steve H]

Did you ever find a cause of this, as I have had it happen a couple of times as well.

Many thanks

[SebastianM]

I never found a cause, but I have a theorie:

I think my gcode was simply to complex. In ESTLCAM I had set my tool to do a 0.5mm oscillation in z, so the router always moved a little up and down. This led to a 250mb gcode file. I gues this was just "too much" for the arduino.

But I found another very strange issue:
When you create a minimal gcode file with only two lines, the system just freezes:

G90
G01 X300 Y300 F600

---> doesnt work. I have to hard-reset the device.

[Steve H]

Hi Sebastian. Thanks for that, its certainly something to look at. I was also wondering about the issue of ensuring screend cables, that I think was raised somewhere.
If I find anything I will cetainly come back.
Thanks again

[SebastianM]

Do you have a rs-cnc or rs-cnc32?

[Steve H]

RS-Cnc32


Sent from my iPad using Tapatalk