Missed Gcode?

[deweycheatem]

I recently upgraded our Carve King system to run UGS over a Raspberry PI with a 7" touchscreen. No more blowing out the keyboard and a solid state drive!

We use MeshCam for our CAD to CAM conversion and UGS Platform for our sender.

Yesterday I had a file that did not complete the design as intended. There were missing holes. Leaving the piece clamped in place, I re-ran the file with the same result. I believe this would lead to the problem being in the MeshCam generated file, but has anyone else seen similar behavior? I would have thought that if it was a function of UGS that it would have potentially cut it the second time around. Will UGS skip lines if for some reason they are too long?

Thanks for the feedback.

[Derek the Admin]

Have you looked at the visualizer to make sure that it actually appears in the code?

[Mototech]

I use nc corrector to double check my tool path. It's free😁

nc-corrector.inf.ua/index_EN.htm

Curious what post processor you use when saving your gcode. I use meshcam mostly for importing an image file, then exporting as an stl, then importing into vcarve for creating the tool path. Can't remember what post processor i used before I started exporting the stl files, but will check when I get home and update my post with which post processor I used to use.

[Mototech]

I think I used to use the carbide3d post processor.

[tjstandley]

I just set-up my new Carve King, so this is fresh on my mind: The UGS command code length should be set to 70 (Tools -> Options -> UGS (icon) -> Controller Options (tab) -> Command Length Processor -> ? (button)). Also, the checkbox should be checked.

Does your G-code have command lines longer than 70 characters? If so, the post processor itself may have a setting to limit the length. If the checkbox in UGS is not checked, I believe it will not trigger an error.