As the title suggests the Z-Axis on my shapeoko pro xxl only goes down when initializing, and then I get that error. I’ve checked all the cables and all limit switches to make sure they work. Carbide Motion 618.
video
When the router goes down during initialization it is 99% of the time configuration. The Z-Plus and HDZ run in opposite directions. So check your configuration. The Z-Plus is a Lead Screw and the HDZ is a Ball Screw.
During initialization the first thing is the router travels up to the homing switch. Then the X and Y axis home. So if the router goes down the configuration is set for the wrong Z most likely.
The question is did this just start or is this a new machine that has never been initialized?
I have it set to the Z Plus as I just got the Pro xxl. This is a brand new machine.
The screenshot seems to indicate the Z axis limit switch is triggered. The video of the switch does not show the red LED being on. does the limit switch LED light when you hold metal next to it? Does the indication in CM change when you trigger the switch with a piece of metal? I would start by checking the wiring for the limit switch. If the switch was on the correct motion is to go down to get off the switch then turn around and find it again.
2 Likes
The switch turns red when I keep a piece of metal next to it. As for the initialization, it does the same thing regardless.
As @LWSIV said the problem could be in the 1 % range. The Z-plus has a stud at the bottom of the z with a hole in it the lead screw goes through. The HDZ has a bearing block at the bottom of the ball screw.
@LWSIV suggested go to settings and see if any sensors are triggered with
Prior to initialization being complete how would i check sensors being triggered?
You powr on and connect. Do not initialize. Go to settings and you will see any active events inputs. In the newest versions the Menu may be Debug.
Yeah I don’t see any issues as of such unfortunately.
This is what it says:
Machine: Shapeoko
GRBL Version:
Carbide Motion 618
Machine Controller State: INIT
Grbl Cycle: Idle
{
"bitRunnerEnabled": false,
"bitSetterEnabled": true,
"bitSetterX": 0.0,
"bitSetterY": 0.0,
"bitZeroType": 0,
"connection": 1,
"lastConfigSent": 6,
"lastProbeIndex": 0,
"lastSizeOption": 0,
"odometer": [
{
"cleared": true,
"minutes": 0.07003333333333332,
"startDate": "2023-08-31",
"travelX": 119.99999996460974,
"travelY": 0.0,
"travelZ": 49.99999998882413
},
{
"cleared": false,
"minutes": 0.15666666666666668,
"startDate": "2023-08-31",
"travelX": 91.72499859333038,
"travelY": 689.024998664856,
"travelZ": 34.99999997019768
}
],
"showCarbideRouterRpm": true,
"spindleType": 0,
"travelX": -865.0,
"travelY": -850.0,
"travelZ": -140.0,
"version": 0,
"workOffsetX": 0.0,
"workOffsetY": 0.0,
"workOffsetZ": 0.0
}
0 = 10, Step pulse, microseconds
1 = 255, Step idle delay, milliseconds
2 = 0, Step port invert, mask
3 = 5, Direction port invert, mask
4 = 0, Step enable invert, boolean
5 = 0, Limit pins invert, boolean
6 = 0, Probe pin invert, boolean
10 = 255, Status report, mask
11 = 0.02, Junction deviation, millimeters
12 = 0.01, Arc tolerance, millimeters
13 = 0, Report inches, boolean
20 = 0, Soft limits, boolean
21 = 0, Hard limits, boolean
22 = 1, Homing cycle, boolean
23 = 0, Homing dir invert, mask
24 = 100, Homing feed, mm/min
25 = 2000, Homing seek, mm/min
26 = 25, Homing debounce, milliseconds
27 = 3, Homing pull-off, millimeters
30 = 24000, Max spindle speed, RPM
31 = 0, Min spindle speed, RPM
32 = 0, Laser mode, boolean
100 = 40, X steps/mm
101 = 40, Y steps/mm
102 = 200, Z steps/mm
110 = 10000, X Max rate, mm/min
111 = 10000, Y Max rate, mm/min
112 = 1000, Z Max rate, mm/min
120 = 500, X Acceleration, mm/sec^2
121 = 500, Y Acceleration, mm/sec^2
122 = 270, Z Acceleration, mm/sec^2
130 = 845, X Max travel, millimeters
131 = 850, Y Max travel, millimeters
132 = 95, Z Max travel, millimeters
Maintenance:
Travel (km) 0.00, 0.00, 0.00, 0.00 Hours since 2023-08-31
Travel (km) 0.00, 0.00, 0.00, 0.00 Hours since 2023-08-31
Queue Empty
On the CM screen on the left side it will show if any inputs are active. So take a metal object and place on the 3 homing switches to see if the state changes or displays. Also pushing the BitSetter button down manually you should see the state change.
So again power on and connect but do not initialize. Do the above to see if you see the inputs change state.
This menu remains unchanged, I see the red lights iluminating, but nothing changes on the software side.
connect to the machine but don’t initialize.
Go to settings and select the debug tab.
If you see the Z Home on without the red LED on the switch that is your problem. It would either be a connection issue, wiring issue or bad switch. The dot should match the state of the red LED on the prox switch. Check each axis to be sure Z is the only one acting up.
I did see that Z Home on=… checked the wiring and the LED is off so that seems to be the issue…Thanks for the help!
@LWSIV got there first. I upgraded to CM 618. I have an SO3 XXL but the screens are the same. I had some problems at first with getting the configuration to go forward. But I quit CM and restarted.
So as you connect do not initialize. Go to the Settings menu and Debug. There you see if any inputs are already active. If none are active put a wrench or metal object under each of the 3 homing switches. The light on the Debug screen will change state and change back when the wrench is removed. Make sure your machine is away from the homing position or the homing switch could be activated due to the position of the gantry in relation to the homing switches. You can push down on the BitSetter and see the state change while holding it down. It will quite illuminating when you release the plunger on the BitSetter.
So you have to verify that all your homing switches are good before proceeding. Not sure if this matters but if you have a BitZero make sure the magnet is not touching ground. That can cause its own issues.
Above you can see I had a wrench on the Y homing sensor.
So I did some testing and turns out it was only my X axis limit that was the issue, the Z was just wired to X so it showed up as a Z-axis issue. Moved the metal piece and no change in the software (always on).
If I forcefully flip the X limit cable around, it works.
1 Like
This topic was automatically closed after 30 days. New replies are no longer allowed.