Situation:
I deleted objects from the design that had toolpaths associated with them. I did not delete the toolpaths. Therefore, they showed up as empty (as expected).
Those vectors do not exist in the code and the toolpath is “empty”…but they are still being cut (not sure if it would cut if I ran the job or not, but I’m guessing the GCODE is in there if the simulation is showing it.
Saving the file removed the problem.
So the defect occurs in memory, while you’re deleting and moving things. Pretty low-impact bug. I’ll try to come up with steps to make it happen - but I’m not sure you’re going to want to spend a whole lot of time on it.
Gary
[LATER EDIT]: This problem doesn’t really GO AWAY when you save the file. It is still present when the c2d makes its way to CM — so it’s actually a larger problem than I originally thought. I don’t want this post to cause folks to ignore the error.
OK Will…now it’s getting really funky:
Here’s the file: test solution.c2d (76 KB)
Open it in CC (757) and you will not see those cut outs on the left hand side
Run the simulation : STILL NO cut outs
I exported the GCODE into a GCODE-only file and ran it through NCViewer and I DON’T SEE THE SLOTS.
HOWEVER:
Bring it into CM (611) and look at the top view and you’ll see that IT IS going to cut those slots. I ran the job and sure enough, it went to cut those pieces out.
The problem seems to be in the interpretation of the c2d gcode - because the extraction code works properly: if you save the GCode only from the file:
and bring that into something like NCViewer - the GCode seems clean (I haven’t brought the NC into CM yet…but I will…I’ll include it below as well:
Does it still show if you delete that empty toolpath. I thought that is what you described initially.
When I save a toolpath to the file so also go to the file menu and do save there as well. I don’t know if that is really necessary but it seems safest. I
Am sure that would not impact your scenario though.
Hey Cullen:
I did not delete the toolpath (there are often valid empty toolpaths when you’re tiling, btw)
When you save the file and reopen it, it LOOKS LIKE the toolpath is gone from the simulation - but when you bring that same c2d into CM and look at it with something like Top View, you will see that it the toolpath is actually still there - and will get cut.
I deleted some geometry and created an empty toolpath the other day and it turned yellow as expected.
Once I redefined the toolpath to use different vectors the simulation looked good and the timing on the toolpath was there but it was still highlighted in yellow. I don’t know whether that is a bug or the yellow was telling me something different.
I will try your test case on my machine and see if I can replicate it.
You don’t really see the problem in CC, you see it when you get to CM. You see it ni CC until you save the file and reopen it…but if you take the saved file to CM, those deleted vectors still have their toolpaths in the c2d. If you export the gcode from CC, however, those toolpaths are NOT included in the GCOde file…but will actually cut in CM
I actually wrote up, and then deleted a report on this because it went away on reloading the file in Carbide Create — will work up a report for it the next time I am at a machine.
