# New Lulzbot Mini 1 issues **URL:** \ **Category:** General\ **Created:** [August 8, 2025, 1:21am UTC](https://forum.lulzbot.com/t/new-lulzbot-mini-1-issues/27674 "2025-08-08T01:21:21Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![ManyATrueFail](https://avatars.discourse-cdn.com/v4/letter/m/ccd318/32.png) [@ManyATrueFail](https://forum.lulzbot.com/u/ManyATrueFail)\ **Post date:** [August 8, 2025, 1:21am UTC](https://forum.lulzbot.com/t/new-lulzbot-mini-1-issues/27674/1 "2025-08-08T01:21:21Z")
I recently got a used Lulzbot Mini 1 and it repeatedly fails to level the bed. It will go to touch the first washer, stop right above it, then go to wipe the nozzle. Do that a few times then it disconnects itself from my computer. I tried updating firmware and lowering the Z offset but neither works. Any advice? ---
**Author:** ![Wrathernaut](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.lulzbot.com/wrathernaut/32/13542_2.png) [@Wrathernaut](https://forum.lulzbot.com/u/Wrathernaut)\ **Post date:** [August 8, 2025, 1:27pm UTC](https://forum.lulzbot.com/t/new-lulzbot-mini-1-issues/27674/2 "2025-08-08T13:27:37Z")
What is your Z offset now? Are you using CuraLE 4, or some older version? It sounds like there may be a short in the zero/ground sense wire. In CuraLE’s terminal, send M119 as a command. You should something like this back: ![image](https://us1.discourse-cdn.com/flex020/uploads/lulzbot/original/2X/c/ca5f4e6963c8f9ac9cc90341f499e4c0342e938b.png) If z\_min is triggered and it’s not touching a washer, you’ve got a problem with the loop for detecting when it touches the corner, so the instant it tries to move down to touch the corner, it thinks it already is, and since that contact never stops, it goes to try and wipe, and after that same failure, it shuts down, since something is obviously wrong. If M119 lists the z\_min as OPEN, connect a wire between the corner washer and the nozzle, and send M119 again. If it’s still OPEN, ensure you have a good connection on the nozzle, and that it’s not obstructed by plastic, and try M119 again. ---
**Author:** ![ManyATrueFail](https://avatars.discourse-cdn.com/v4/letter/m/ccd318/32.png) [@ManyATrueFail](https://forum.lulzbot.com/u/ManyATrueFail)\ **Post date:** [August 8, 2025, 4:14pm UTC](https://forum.lulzbot.com/t/new-lulzbot-mini-1-issues/27674/3 "2025-08-08T16:14:35Z")
My Z offset is currently -0.7 When I ran M119 It gave me this > > > [10:09:00] M119 \<\<\< [10:09:00] Reporting endstop status \<\<\< [10:09:00] x\_min: TRIGGERED \<\<\< [10:09:00] x\_max: open \<\<\< [10:09:00] y\_min: open \<\<\< [10:09:00] y\_max: open \<\<\< [10:09:00] z\_min: open \<\<\< [10:09:00] z\_max: open I dont have any wire on hand so I used a paperclip, and when I touched it to the washer and nozzle it gave me the same return ---
**Author:** ![Wrathernaut](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.lulzbot.com/wrathernaut/32/13542_2.png) [@Wrathernaut](https://forum.lulzbot.com/u/Wrathernaut)\ **Post date:** [August 8, 2025, 7:02pm UTC](https://forum.lulzbot.com/t/new-lulzbot-mini-1-issues/27674/4 "2025-08-08T19:02:36Z")
Z offset with the washers should be somewhere around -1.25 with the standard (non-magnetic) bed, the washers sit on the bed, so the z offset should be the height of the washers. If your nozzle is dirty, using a -0.7 offset would be an attempt to compensate for the plastic delaying electrical connection, and lead to very inconsistent bed leveling. But that isn’t the cause of the issue here. Paperclips wouldn’t be a very great way to do the connection, but you can simply move the nozzle manually to (gently) contact with the washer and do an m119 again. ---
**Author:** ![ManyATrueFail](https://avatars.discourse-cdn.com/v4/letter/m/ccd318/32.png) [@ManyATrueFail](https://forum.lulzbot.com/u/ManyATrueFail)\ **Post date:** [August 10, 2025, 8:03pm UTC](https://forum.lulzbot.com/t/new-lulzbot-mini-1-issues/27674/5 "2025-08-10T20:03:20Z")
When I brought the nozzle into contact with the washer it gave me this \<\<\< [14:02:14] x\_min: TRIGGERED \<\<\< [14:02:14] x\_max: open \<\<\< [14:02:14] y\_min: open \<\<\< [14:02:14] y\_max: open \<\<\< [14:02:14] z\_min: TRIGGERED \<\<\< [14:02:14] z\_max: open ---
**Author:** ![Wrathernaut](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.lulzbot.com/wrathernaut/32/13542_2.png) [@Wrathernaut](https://forum.lulzbot.com/u/Wrathernaut)\ **Post date:** [August 11, 2025, 2:05pm UTC](https://forum.lulzbot.com/t/new-lulzbot-mini-1-issues/27674/6 "2025-08-11T14:05:19Z")
Are you able to use the manual axis movement to get the nozzle to touch, or are you having to move it by hand? Let’s see where it thinks it is when it’s touching, use the command M114 to get the position, for example: ![image](https://us1.discourse-cdn.com/flex020/uploads/lulzbot/original/2X/5/585e24eb8e0e2375fbf976202d9dd1fecfcb2b29.png) If you can move it through manual axis movement, it should be giving you a Z coordinate when you’re right at the washer, what is that coordinate? If you’re having to move the nozzle down by hand to contact, how far from the washer is it and what is the reported coordinate at the lowest it will go with the manual movement controls? Compare that with the software endstops, use M211: ![image](https://us1.discourse-cdn.com/flex020/uploads/lulzbot/original/2X/d/da7569d9f846efb6561ee97581d400a00ce9218a.png) If it’s just not allowing enough Z travel to find the washers, since homing Z is initially done at the top, it subtracts from that max Z and gives a minimum. One way around that is to disable the software endstops, but that could lead to damage if plastic is on the nozzle and prevents electrical contact long enough that there is damage to the nozzle or printbed. G92 adjusts the software endstops, so you can use it to fool it to go lower, either. That leaves the option to just trigger the Z max switches a few millimeters sooner. If your wipe and probe sequence attempt is similar to SoCalRedneck’s here: [https://youtu.be/W8EC\_yOBRls?t=110](https://youtu.be/W8EC_yOBRls?t=110) then the nozzle isn’t getting low enough to wipe either, so if you put some spacers just slightly taller than the height the nozzle stops at when trying to probe, it should correct both issues. I’m not sure if the firmware had the limits changed, or if they changed an X gantry part that caused the switches to be hit too late when using the old part. ---
**Author:** ![b-morgan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.lulzbot.com/b-morgan/32/11517_2.png) [@b-morgan](https://forum.lulzbot.com/u/b-morgan)\ **Post date:** [August 11, 2025, 5:16pm UTC](https://forum.lulzbot.com/t/new-lulzbot-mini-1-issues/27674/7 "2025-08-11T17:16:19Z")
I know we are working on a `z_min` issue so I hate to state the obvious, `x_min: TRIGGERED` doesn’t seem right. ---
**Author:** ![Wrathernaut](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.lulzbot.com/wrathernaut/32/13542_2.png) [@Wrathernaut](https://forum.lulzbot.com/u/Wrathernaut)\ **Post date:** [August 11, 2025, 5:59pm UTC](https://forum.lulzbot.com/t/new-lulzbot-mini-1-issues/27674/8 "2025-08-11T17:59:35Z")
I just assumed the toolhead was starting from the Xmin, since he didn’t mention issues with the wipe. ---
**Author:** ![ManyATrueFail](https://avatars.discourse-cdn.com/v4/letter/m/ccd318/32.png) [@ManyATrueFail](https://forum.lulzbot.com/u/ManyATrueFail)\ **Post date:** [August 11, 2025, 7:32pm UTC](https://forum.lulzbot.com/t/new-lulzbot-mini-1-issues/27674/9 "2025-08-11T19:32:12Z")
Its exactly like the video you sent, should I use some standard washers stacked on top of the original ones to fix the issue? ---
**Author:** ![ManyATrueFail](https://avatars.discourse-cdn.com/v4/letter/m/ccd318/32.png) [@ManyATrueFail](https://forum.lulzbot.com/u/ManyATrueFail)\ **Post date:** [August 11, 2025, 7:32pm UTC](https://forum.lulzbot.com/t/new-lulzbot-mini-1-issues/27674/10 "2025-08-11T19:32:55Z")
I think that the first bed leveling spot is at x min, so it should be triggered ---
**Author:** ![Wrathernaut](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.lulzbot.com/wrathernaut/32/13542_2.png) [@Wrathernaut](https://forum.lulzbot.com/u/Wrathernaut)\ **Post date:** [August 11, 2025, 7:46pm UTC](https://forum.lulzbot.com/t/new-lulzbot-mini-1-issues/27674/11 "2025-08-11T19:46:57Z")
Ok, see the response to that post about using spacers to artificially lower the Z maximum trigger spot, or disabling the software endstops prior to wipe/probe. ---
**Author:** ![cdsmith](https://avatars.discourse-cdn.com/v4/letter/c/22d042/32.png) [@cdsmith](https://forum.lulzbot.com/u/cdsmith)\ **Post date:** [August 13, 2025, 2:43am UTC](https://forum.lulzbot.com/t/new-lulzbot-mini-1-issues/27674/12 "2025-08-13T02:43:09Z")
The X min triggered might actually be an issue. If the move down is a simultaneous X and Z move, and it starts the move with the X axis not already against the X\_min switch, and it hits the X\_min switch before it finishes the Z downward movement, it will probably abort the rest of the Z movement, leaving the nozzle higher than intended. It’s a bit of a stretch, but it would be worth checking if this is happening. We saw a similar issue on the Workhorse a while back. When you started an auto-calibration, it would do a simultaneous X and Y move toward the calibration cube. To reach the center of the cube it has to go right to Y\_min, but due to a fraction of a millimeter of variance on when the switch actually clicks, sometimes the Y\_min switch would click early and abort the rest of the X/Y move, leaving the X axis short of reaching the cube. Then it would move down like it was probing the cube, but miss the cube a few centimeters to the left. I fixed it by separating the X and Y moves, so that it wouldn’t matter if it bumped the Y-Min switch. Something similar could be happening here.