Hey guys so I created a two part job in Carbide create a pocket cut and then a contour cut. The pocket went fine I had two parts that needed to have a 12mm square cut in them and then a contour cut to full depth.
The Pocket worked in both cuts but once complete and it moved to the contour it failed to raise the tool head enough and just cut its way to the start point in the project. I am using the CC6 and GRBL post processor to a Duet board.
So I am not a GCode genius but I can see at the end of pocket is raises Z to 22.860 and the material was 17.5 mm or so but then still before it started the move to the start of the Contour it lowered the Z and cut the part.
The retract height was set to 5 mm and I watched the job it for sure didnt skip or max out the Z, its like it tried to drop the tool head on the way to the next operation instead of move to the next location and then drop the tool head.
So i ran the file again with the same results, as it moved from one toolpath to another it cut into the material as it moved from the finish point of the first toolpath and the 2nd toolpath in the cut list.
Do I have to run the 2 toolpaths separately even if they use the same bit for each cut?
I agree that is what it looked like to me in Gcode as well. It not mechanical for example the two pockets were cut with one tool path and it had to life the tool head to move between the two pockets and there was no issue with it cutting into the material while travelling. But when transitioning from the pocket toolpath to the contour toolpath that is where the tool head cleared the material and then as it was moving to the start of the contour the tool head lowered and cut into the material.
if you can reproduce this behavior, I suggest you manually check Z zero right after it happens. If the Z zero is not spot on anymore, either your tool slipped or you lost steps somehow.
Have you tried saving the file again and reloading it?
I have had this happen a few times and why it happen I have no clue. Why did saving the file again fix it? Again. I have no clue.
If you look at where the damage is on your part the path in the NC file does not transit thru that area without axes losing steps, pulleys slipping or belts jumping teeth. Are the pockets to correct depth? Are the contours cutting to the correct depth? Do you have any pictures after cutting before the pieces were removed from the machine? You are doing slotting operations which puts the most load on your machine and tooling. Consider adding offset geometry and pocketing a slot that is 110-125% the diameter of the tool. This will reduce the tool engagement helping with heat build up, chip clearance, deflection, etc. It takes a bit longer but is well worth while.
That is good advice and yes sorry I see the confusion I should have taken a picture of the operation while it was on the machine. The parts were opposite of how I have them pictured so the damage actually matches up to this movement.
Yes all other dimensions and depths came out correctly.
X86.404Y49.060
X86.309Y49.141
G0Z-1.400
Z7.000
(Contour.O…)
S30000 <-------------------What happens if you take this out?
X36.349Y25.822
G1Z-1.500F380.0
X36.933Y25.252F1100.0
X37.574Y24.654
The G-code does not contain the rapid motions in the work piece that are shown in your video. The move from the end of the bottle cap insert pocket to the magnet pocket is at Z 7.00. There were a few other places where the bit did not retract in the video. It is looking like a rapid move is missed by the control or not being sent to the control. The other cuts are showing mechanical repeatability. I’d try a different com cable/port, make sure there are no other tasks running on the computer, and if possible try a different computer with the sender.
Out of curiosity what controller are you running? Which G-code sender are you using? Which post processor did you select in Carbide Create? Are the files local or coming from network storage?
So I am using a Duet3D controller with 3.5 firmware on it. I am loading the Gcode file directly to the controller with no PC in the mix. And using the GRBL post processor when I export.
If I create something similar in Fusion with multiple tool paths it’s able to cut without the problem so it’s something specific to Carbide Creates Gcode but I like the program and would like to see about getting this issue resolved so i can use it more reliably.
Does the version of F360 you are using export G0 motions (I thought this was one of the missing feature in the free version)? If you replace the G0 motions in the CC file with G1 moves does it behave differently?
