Toolpath changes don't update in gcode

Software
1

I had this happen yesterday, screwed up a piece of material, and I just saw it happen again today. I’m making changes to my toolpath in CC, running a simulation, and saving the gcode to a new file name. When I go run the job, some of previous settings are still in there. Super dangerous, and it’s f-ing up my workpieces.

Example A: Yesterday I had to pick up on a profile cut that glitched halfway through, so I set the starting depth .13" into the material and re-saved the gcode, reloaded it into CM. The gcode didn’t register the starting depth and ran the entire depth again (added an hour to the job, cutting air half the time). Then I set up the same cut on a new piece of material, removing the starting depth from the toolpath, re-saved gcode etc… I go to run the job and it tries to start the profile .13" inches deep in 6061 Aluminum. Snapped the flutes off my 1/4" bit, ruined the part, exhausted my sailors vocabulary. Deep breaths.

Example B: Today I’m checking everything extra carefully. Triple check all my settings (I happened to change the first feed rate from 60 to 45), delete all previous gcode files, run simulation, save new gcode file. Start the new job at 50% feedrate just in case… sure enough the first path is running at 60 instead of 45. More swearing.

The worst part is that now I don’t trust any changes to update in my gcode now. It’s happened both to starting depth and feed rates, what else is going to ignore my settings updates?

Has anyone else run into this? Fixes, work-arounds? For reference I was running v462 on CC and 513 on CM. Updating CC to 464 to see if that helps.

2

I always add a version # to the end when exporting, and then verify in a tool such as CAMotics.

3

I think I figured it out, or at least narrowed it down. I’ve been doing my design work on a PC, and then accessing the cut files from a laptop (via my home network) to run the jobs. My network is a little glitchy to begin with, and I think if the files aren’t completely… accessible?.. Carbide Motion will update the file name, but actually keep the gcode from the previous job.

I’m basically taking everything a little slower (navigating to the file starting from the network instead of jumping straight to the destination folder, making sure the gcode has time to load before navigating away, etc.), and checking the first few lines of gcode within CM to make sure feed rates and doc’s line up, haven’t had much trouble since.

1 Like
4

That seems an unlikely scenario, but hope your workflow changes work out for you.

5

This topic was automatically closed after 35 days. New replies are no longer allowed.