I have a really simple spot/drill/counterbore program I'm trying to run and something is way off with one of the drill cycles. I'll include the gcode but it's just canned drill cycles. First is spot drill, works fine. The second drill is where the issue occurs. I change the tool (I have all 4 tools for this program with their heights preset, and I have verified that they are indeed correct so that's not the issue), restart my spindle, hit cycle start and it starts to rapid over to the next hole but the Z height goes way past the Zero point/retract height and just keeps going down, slamming into my part before even getting to the correct X/Y position. It's broken 2 of my drills. Dry running it appears to want to go all the way to the bottom Z point of the hole, THEN move up and start drilling normally once it's at the correct X/Y. I can only test so much in dry run since it's a long drill and soft limits come into play, let alone physical space I have before it crashes into something more important than a drill. I can't imagine this is a post processing error. I'm making 2 (almost) identical parts, they're symmetrical. So the holes and c'bores are offset from center on one part, then the opposite way on the second part. Because of this I modeled and did the CAM separately in F360 with 2 different setups, one for each drilling/c'bore cycle.
If I post process JUST this one drill, it works perfectly fine. But that's inconvenient and defeats the purpose of presetting tool heights. There's also no way of predicting this happening to any given tool in the future either and could break something more expensive than a HSS drill bit. Even with the feedrate at minimum there's really no way to stop it in time from crashing without a ridiculous retract height set in the program.
I was also sent another software update 3.37.10pre that I hadn't yet loaded. 3.37.7pre seemed to be working fine for the most part until now and I was unsure what 3.37.10 entailed so I didn't want to just blindly update to it. I'll have to try that once I have some more time then update the post.
As always, using Clearpath servos on all 3 axes, and my gcode and masso settings are attached.
Thanks,
Brandon
If I post process JUST this one drill, it works perfectly fine. But that's inconvenient and defeats the purpose of presetting tool heights. There's also no way of predicting this happening to any given tool in the future either and could break something more expensive than a HSS drill bit. Even with the feedrate at minimum there's really no way to stop it in time from crashing without a ridiculous retract height set in the program.
I was also sent another software update 3.37.10pre that I hadn't yet loaded. 3.37.7pre seemed to be working fine for the most part until now and I was unsure what 3.37.10 entailed so I didn't want to just blindly update to it. I'll have to try that once I have some more time then update the post.
As always, using Clearpath servos on all 3 axes, and my gcode and masso settings are attached.
Thanks,
Brandon