I am having an issue with my hdz lossing z placement after the first shape cut where it doesnt raise high enough and cuts through the material. Then when it plunges for next cut after dragging through material it buries itself into the wasteboard. I have ran the gcode on a simulator and it doesn’t show this problem so i’m curious if its the newest version of carbide motion.How can I download earlier versions of carbide motion? Thanks for your help!
Hi @Scott.Creque,
Can you please confirm whether your Z axis collides at the top, upon the initial retract move ?
If so, this is most likely because your retract height is set too high, compared to how much Z travel you have left after zeroing (especially if you have a thick piece of stock)
In CC, reduce retract height to the minimum (to still clear your top clamps, if you do use clamps)
It’s normal that the router will plunge too far if an initial collision happens at the top of the Z, so you should avoid that, always.
Post a picture of your setup, or better yet a video if you can, for us to confirm this is what is happening
in addition to @Julien’s question, I would suggest redoing the settings screen in CM and send the settings to your system
(and can you make a screenshot and post it just in case it shows something interesting)
I am cutting 0.20 inch plywood. Using vcarve desktop. I have run it twice with retract heights set to 0.20 inches and 0.35 inches. So it cuts the first shape out perfect with tabs and all. Then when it retracts to go to the next shape it doesn’t retract all the way and drags across the material. I have never had this problem before switching to the HDZ and carbide motion 431.
I am not able to screenshot yet but I have resent the configuration data both times before I cut and it takes around 33 sec to send it. After sending I initialize the machine and it homes to all the limit switches. I reset all the zeros again and then same problem.
Issue may have been resolved. I restarted carbide motion and resent config data. I also changes 1/8 inch bits and seemed to work perfect now. Fingers crossed one of those was the issue. Thanks all!
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.