When I make a file in carbide create and use the send to carbide motion button, it sends the file properly and starts good and all but as soon as the but enters the material, the program stops.
If I export the same file to Gcode and run it thru carbide motion, it runs flawlessly without issue.
Thats been a problem for quite a while, CM seems to truncate the gcode file when you use that feature. I’m hoping that gets fixed with the next version, it’s a great idea.
It’s on all of them now I believe, but it’s still in testing since in the current version, there’s no check for a complete transfer — hopefully that will be added and it will be reliable enough to depend on in a future version.
If I recall correctly you have to have CM running when you launch CC. Create or edit an existing .c2d file, create a toolpath, and you should see the “Send to Carbide Motion” button above the “Save G Code” button