Been using CM for a couple of months and have some ideas for improvements. CM is a great program and I like it, these are just suggestions.
On the run page, have a slider so you can fast forward. Sometimes I have to restart and have to wait until it does the first part all over again. I had a problem with it just stopping in the middle of a pass.
If you start the probing process and you started too high in Z, the probe fails and then you have to go home and start all over. If the probe fails, you leave the router where it is.
If you unexpectedly hit one of the limit switches during a pass, stop! I was hitting the limit unknowingly and it reset the Z offset. The result was taking too deep of a cut in aluminum, it wrenched the material out of the clamps, spun it around and broke 6 V-wheels.
When you are in the jog menu, if the user selects the run menu go to it. I have not trained myself well enough yet and still fail to hit the done button before changing menus. I come from a software programming background and just expect to be able to change menus without hitting done first.
We have feedrate override in CM so you can run the machine at 200% speed. You cannot select an arbitrary percentage of a program to start from because that might plunge the machine into a partially completed cut. If you need to skip one or two time consuming toolpaths, it’s best to just go into the NC file and remove it manually.
If you’re running the latest version of Carbide Motion, there shouldn’t be a ‘Done’ button. CM may not show an update available, need to go to the download page. v428 is the latest.
Thanks I have to become more knowledgeable about g-code. All my work to date has been in assembler, C, C++, and a little Java. Guess I’ll have to learn a new one