I run a Mac on one machine and windows on 2 of them. No issues with 640. You can open the debug screen and see if you can see which hard limit is tripping. hard limits are usually the homing switches. By chance have you replaced the Z limit switch? I found an issue with my machines on that switch cable routing.
1 Like
Interesting! We replaced every limit switch on the first machine, and the new machine obviously has all new limit switches, and the issue persisted across all of it
Sorry I didn’t tag you in my last reply. Are you trying to jog immediately after initialization? Because we replaced the main board and all of the limit switches in my original machine and then replaced the entire machine I’m essentially on my third machine and it’s having the exact same issue.
Edit: are you on Intel Mac? I have an M1 Pro
If my understanding of the root cause of Duncan’s issue is correct, the problem isn’t hard limits or switches themselves. It’s a bug in Carbide Motion that causes the machine to move to the wrong position when using Rapid Position immediately after initializing, and in doing so, it runs the machine to the limits of its travel. It’s not related to hardware. I’m going to bug the dev team to take another look at this and get it back on their radar.
3 Likes
I’ve run into this a number of times myself, most recently was just a couple hours ago.
IIRC there is a thread with a method to reliably reproduce it somewhere around here.
Let the devs know that another person has been impacted by this. <insert “there are dozens of us, dozens!” meme 
>
*Nice, looks like Flynn mentioned the relevant thread earlier in this post.
Sucks it’s happening, but glad it’s repeatable! Thanks for the response. Hopefully we they get it patched up soon.
Correct, that’s the working theory! Much appreciated:)
Tested on windows today and same issue, failed during machine setup, and on initializing as well.
It’s so confusing that the issue is not the hardware, but some of us have it and some of us don’t.
Ran the machine for some simple cuts. Clicked initialize told her to load the program and the machine asked for the tool change, I clicked enter. The machine stopped moving. The lights turned off, and the entire machine turned off and then turned back on a few seconds later without touching the button. It was then completely disconnected from the program, and I had to connect the cutter and initialize again… The cuts went ok, but ummmm, I don’t like this lol
I ran into this issue bout a year ago, I was on the phone with a Carbide tech for an hour plus. Sorry I don’t recall specifics but the issue was using the rapid positioning matrix and having my Nomad Pro grind into limit switches. When this occurs I’ve had to turn the Nomad off, restart and re-initialize.
I do remember the issue generally occurred only after some other movement. The tech and I worked on it for quite awhile but couldn’t attain predictable repeatability. This included installing different versions of CM. The tech said he would present this higher up the tech chain but I never heard back. This issue has endured through several updates.
My work around has been to not use these buttons.
1 Like
We all understand that companies have finite resources and that not every bug can be fixed immediately, and clearly this is not a critical bug so has a low priority. But, it is clear that several people, including some C3D employees, have become aware of this bug (and probably others) independently.
I really wish C3D would run a known issues list along with release notes. For a start it could ease the load on carbide support who do a great job but probably have better things to see to.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.