My Shapeoko XL has a file stuck in its memory somewhere. We ran a file in Carbide Motion … the router did not start in the correct area on our test material. We re-worked all the file in Create to confirm we did not make an error. We loaded the new GCode into Motion, but the machine would only cut the old incorrect file. We deleted the LOG, we unpluged the “brain” we restarted the computer, same result. We dumped the Carbide Motion Software and downloaded and reloaded Carbide Motion again off the web… The machine will only cut
the old bad file. The computer says we loaded a new file, shows the name of the new file but will only cut the
old bad file… Any ideas out there … We are into this over a week now and still cannot get it to cooperate.
For Carbide Motion 4, when running multiple files, after loading the new file, right or control-click on the window and then choose “Reload” from the contextual menu.
Changing the name of the file can be helpful for keeping the versions straight. I know I’ve had more than one case where because it was named the same, either I loaded it wrong, failed to save it and didn’t notice, or the software did something “not as well as one would hope.” Changing the name made it obvious which file I was loading and usually straightened things out quickly.
Try generating and losing a completely different file (something basic like a circular pocket), and run an air cut.
The controller can’t store a gcode file, so it’s something on the computer (restart) or Carbide Motion (try something else).
I haven’t received my Shapoko yet but what I’ve learned (the hard way) to do on my 3D printers is to append a version number to the file name. My convention for 3D printer files is “File Name-Material-Version” (e.g. Clamp-PLA-v1). When the part is printed the way I want I’ll change the version number to Final (e.g. Clamp-PLA-Final). I suspect that I’ll use some variation on this for the toolpaths I’m using when I get my Shapoko.
Unrelated to the question but may help is to save every version of the I file you are working on. I was surprised at how many times I was able to figure out a problem by comparing the two GCode files. My favorite was the time I forgot a decimal point and was trying to print with a 4mm layer height rather than .4mm. I swear I stared at the model for a couple of hours before comparing the two GCode files showed me that doggone missing decimal point.
I would highly recommend checking the new/correct file in a Gcode 3d visualiser tool, and verifying the Gcode in there is actually correct. Sometimes the problem is not where one is looking, and it is worth 2 minutes to be very very sure that it is not the new file that is incorrect…
I just want to thank everyone who sent in suggestions for my “old stuck file” … the solution was to reset the machine, there is a button in the “brain box” on the lower left, we did this with the help of Nick in Support at Carbide 3, and then we dumped all the files on our computer that was related to the “bad old file”. Loaned a new file and we were off to cutting a new file, we still have some issues and will be on the phone with support after the Holiday to work them out… Thank You all and Have a Healthy and Happy New Year