Just got my machine, just set it up.
I did the Setting and Load data configuration with right info, I think.
I have a 2 x 2.
The Z goes down then go up with a super big noise.
It stop at the top with error message
“Machine controler restarted unexpectedly and may be in undefined state”
Then next message : “GRBL Error: homing failed, couldn’t find limit switch” Homing cycle failed.
Every wire look ok.
During initialization the Z goes up. Almost 99% of the time when the Z goes the wrong way it is the configuration. The Z-Plus and HDZ run in opposite directions.
The initialization has the Z go up and trigger the homing switch. Then the x and y move to the back right corner and hit their homing switches and if the BitSetter is unchecked it just sits there. If the BitSetter is checked the homing takes place and then moves to the center front and prompts for a bit. During the first initialization you should uncheck the BitSetter because there is no position set for it to move over to. Get the initialiation to finish and then jog to the BitSetter and center a bit over it and then go into settings and set the current position for the BitSetter and check the BitSetter.
The Z-Plus is refereed to as a Leadscrew and the HDZ is refereed to as Ballscrew. Most machines come standard with the Z-Plus and the HDZ is an option.
The most common first initialization problem is sending the wrong config. So determine if you have the Z-Plus or the HDZ and send the appropriate configuration.
The next most common initialization problem is the homing switches need to be adjusted so they trigger properly. During assembly you can have the homing switches too far away to trigger properly.
The configuration is primarily configuring Carbide Motion so it sends the correct commands to the Shapeoko/Nomad.
So get your Z moving in the right direction first and then tackle the homing (proximity) switches. Fix one thing at a time because the shotgun approach leads to frustration. Make one change at a time until the initialization progresses through the whole process.
2 Likes
Got it, I put the Bitzero to None instead of leaving it a Bit Zero v2, the default value.
I tought that since i did not have a BitZero that I had to put it at None.
Now, everything initialize fine.
I can now go to bed.
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.