Recently I’ve noticed an issue when exporting gcode from Carbide Create to Carbide Motion that occasionally the gcode won’t actually send the current CC toolpaths, but instead seems to send the toolpaths from the previously run project. (Or maybe CC just isn’t sending anything, so the previous project’s gcode remains in CM?) Weirdly, the active file name in CM keeps updating each time the Export button is clicked (from tmp_gcode_5.nc to tmp_gcode_6.nc, etc) as expected, so everything appears fine until the machine actually starts cutting - and then I see that it’s running the wrong project. I’ve gotten into a habit of clicking the Export button several times just to make sure the new gcode is sent, but even then it sometimes doesn’t work, and I’ve ruined several small projects this way.
No apparent problems if I click “Save GCode” instead and manually import into CM.
Any idea what might be going wrong? Thanks!