# Bed leveling but not during print

**URL:** <https://forum.lulzbot.com/t/bed-leveling-but-not-during-print/27414>\
**Category:** LulzBot TAZ\
**Created:** [March 14, 2025, 7:49pm UTC](https://forum.lulzbot.com/t/bed-leveling-but-not-during-print/27414 "2025-03-14T19:49:35Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![Elec-tech89](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@Elec-tech89](https://forum.lulzbot.com/u/Elec-tech89)\
**Post date:** [March 14, 2025, 7:49pm UTC](https://forum.lulzbot.com/t/bed-leveling-but-not-during-print/27414/1 "2025-03-14T19:49:35Z")

</div>

I have a workhorse I just updated with the Meteor 285 tool head, magnetic bed, and runout sensor. When I manually do bed leveling from the menu on the printer it works just fine. Then when I try to print, the nozzle misses the wipe pad vertically and then only goes halfway across the bed to level. It has been calibrated, firmware updated, etc. I’m not sure what is wrong. It is a print I have successfully printed on other upgraded printers (the rocktopus test print from Lulzbot).

---

<div class="post-metadata">

**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:** [March 14, 2025, 10:20pm UTC](https://forum.lulzbot.com/t/bed-leveling-but-not-during-print/27414/2 "2025-03-14T22:20:17Z")

</div>

What version of CuraLE are you running? What version of the firmware? After updating the firmware, did you set your toolhead from the menu on the printer?

Can you post the GCODE that’s generated that you’re running?

At least until it gets to the part when it’s starting the first layer.

---

<div class="post-metadata">

**Author:** ![Elec-tech89](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@Elec-tech89](https://forum.lulzbot.com/u/Elec-tech89)\
**Post date:** [March 18, 2025, 3:18pm UTC](https://forum.lulzbot.com/t/bed-leveling-but-not-during-print/27414/3 "2025-03-18T15:18:16Z")

</div>

I am using version 4.13.10 of CuraLE and the latest firmware from that version. I did set the toolhead from the menu on the printer. I’m not sure how to post the GCODE that is generated. If you can tell me how to do that I can post it.

---

<div class="post-metadata">

**Author:** ![Elec-tech89](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@Elec-tech89](https://forum.lulzbot.com/u/Elec-tech89)\
**Post date:** [March 18, 2025, 4:25pm UTC](https://forum.lulzbot.com/t/bed-leveling-but-not-during-print/27414/4 "2025-03-18T16:25:52Z")

</div>

I would also like to add that I had to put in a new SD card because it disappeared. I copied the files from another SD card from a working printer to the new SD card.

---

<div class="post-metadata">

**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:** [March 18, 2025, 6:49pm UTC](https://forum.lulzbot.com/t/bed-leveling-but-not-during-print/27414/5 "2025-03-18T18:49:57Z")

</div>

To post the gcode, save to disk, and open that file, if you’ve been writing to SD card, you could just open what’s on the SD card.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/lulzbot/original/2X/7/74aa6f4b2e06da9fdadf8643b343e92bd8cf1ac2.jpeg)

Towards the top of the GCODE file, you’ll see the wiping/leveling section:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/lulzbot/original/2X/4/4461e9238b6a997038b50eef7d429cec384f9ea3.png)

This is pulled from GCODE generated for a Workhorse with the MET285. The only wipe code is to issue the firmware sequence with the G12 command. This is the same sequence that is called by the menu when you do “Clean Nozzle”. After heating up, it then does the probing (bed leveling). This is similarly achieved with a single firmware command - G29.

The G12 sequence as defined in the firmware is:

```auto
#elif ENABLED(Workhorse)
    #define WIPE_SEQUENCE_COMMANDS 
G28O ; home xyz as needed
M117 Wiping nozzle ; display message
T0 ; ensure it's on tool 0 
G1 X-17 Y25 Z10 F4000; move above the wipe pad
G1 Z1 ; should be nozzle slightly into the wipe pad material, unless the wipe pad is too short
M114; report position
G1 X-17 Y25; wipe back and forth
G1 X-17 Y95
G1 X-17 Y25
G1 X-17 Y95
G1 X-17 Y25
G1 X-17 Y95
G1 X-17 Y25
G1 X-17 Y95
G1 X-17 Y25
G1 X-17 Y95
G1 X-17 Y25
G1 X-17 Y95
G1 Z15; lift nozzle
M400; wait for movements to complete
M117 Wipe Complete; display message

```

Basically, go to X-17 Y25 Z1 and move back and forth.

So, if it’s too high, there’s a few things that could be happening: The wipe pad may be squished down too low, or the MET285 could be mounted too high. Since the Workhorse gets the initial Z (prior to bed leveling) by hitting the top of the frame and measuring down, it may not be low enough to hit the wipe pad if the MET285 is not seated completely, or if something is causing the Z limit switches to be hit early.

Can you post a video of the behavior you’re seeing? I am not sure what would cause the nozzle to only go halfway across the bed with the G29 command coming from GCODE or from the printer’s menu.

---

<div class="post-metadata">

**Author:** ![Elec-tech89](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@Elec-tech89](https://forum.lulzbot.com/u/Elec-tech89)\
**Post date:** [March 18, 2025, 7:12pm UTC](https://forum.lulzbot.com/t/bed-leveling-but-not-during-print/27414/6 "2025-03-18T19:12:39Z")

</div>

;FLAVOR:Marlin  
;TIME:2182  
;Filament used: 0.881091m  
;Layer height: 0.3  
;MINX:98.317  
;MINY:98.255  
;MINZ:0.4  
;MAXX:181.689  
;MAXY:181.732  
;MAXZ:18.4  
;Generated with Cura\_SteamEngine 4.13.10  
M82 ;absolute extrusion mode  
;This G-Code has been generated specifically for the LulzBot TAZ Workhorse | MET285

;SETTINGS  
;Nozzle diameter = 0.5mm  
;Filament name = 3D-Fuel Pro PLA+  
;Filament type = PLA (Easy Printing) 2.85  
;Filament weight = ~7.03g  
;Extruder temp = M109 S230  
;Bed temp = M190 S60

;The following lines can be uncommented for printer specific fine tuning  
;More information can be found at [Gcode | Marlin Firmware](https://marlinfw.org/meta/gcode/)  
;  
;M92 E420 ;Set Axis Steps-per-unit  
;M301 P21.0 I1.78 D61.93 ;Set Hotend PID  
;M906 E160 ;Digipot Motor Current ((875mA-750)/5+135) = 160  
;  
M73 P0 ; clear GLCD progress bar  
M75 ; start GLCD timer  
M117 Starting rocktopus\_WH-MET285-05… ; progress indicator message on LCD  
M107 ; disable fans  
M420 S0 ; disable previous leveling matrix  
M900 K0.05 ; set linear advance K factor  
G90 ; absolute positioning  
M82 ; set extruder to absolute mode  
G92 E0 ; set extruder position to 0  
M140 S60 ; start bed heating up  
M109 R180 ; soften filament before homing Z  
G28 ; Home all axis  
G1 E-15 F100 ; retract filament  
M109 R180 ; wait for extruder to reach wiping temp  
M104 S160 ; set extruder to probe temp  
M106 S255 ; turn fan on to help drop temp  
; Use M206 below to adjust nozzle wipe position (Replace “{machine\_nozz1e\_z\_offset}” to adjust Z value)  
; X ~ (+)left/(-)right, Y ~ (+)front/(-)back, Z ~ (+)down/(-)up  
M206 X0 Y0 Z0  
M117 Wiping… ; progress indicator message on LCD  
G12 ; wiping sequence  
M206 X0 Y0 Z0 ; reseting stock nozzle position ### CAUTION: changing this line can affect print quality ###  
M107 ; turn off part cooling fan  
M109 R160 ; wait for extruder to reach probe temp  
M117 Probing… ; progress indicator message on LCD  
G29 ; start auto-leveling sequence  
M420 S1 ; activate bed level matrix  
G1 X0 Y0 Z15 F5000 ; move up off last probe point  
G4 S1 ; pause  
M400 ; wait for moves to finish  
M117 Heating… ; progress indicator message on LCD  
M190 R60 ; wait for bed to reach printing temp  
M109 R230 ; wait for extruder to reach printing temp  
G1 Z2 E0 F75 ; prime tiny bit of filament into the nozzle  
M117 Printing rocktopus\_WH-MET285-05… ; progress indicator message on LCD

---

<div class="post-metadata">

**Author:** ![zenotek](https://avatars.discourse-cdn.com/v4/letter/z/ad7895/32.png) [@zenotek](https://forum.lulzbot.com/u/zenotek)\
**Post date:** [March 18, 2025, 7:55pm UTC](https://forum.lulzbot.com/t/bed-leveling-but-not-during-print/27414/7 "2025-03-18T19:55:03Z")

</div>

> [@Wrathernaut](#):
>
> I am not sure what would cause the nozzle to only go halfway across the bed with the G29 command coming from GCODE or from the printer’s menu.

Seems the printer is losing a bunch of steps in Y getting stuck somewhere in the wiping and then being in the wrong place to start the probe on the front left disc.

---

<div class="post-metadata">

**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:** [March 19, 2025, 12:37am UTC](https://forum.lulzbot.com/t/bed-leveling-but-not-during-print/27414/8 "2025-03-19T00:37:42Z")

</div>

Definitely a possibility, I do recall reports of loose Y axis belts and loose grub screws on the stepper motor gears on some workhorses. If the MET285 is sitting at a different height, it could be catching more than the previous toolhead.

---

<div class="post-metadata">

**Author:** ![Elec-tech89](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@Elec-tech89](https://forum.lulzbot.com/u/Elec-tech89)\
**Post date:** [March 20, 2025, 4:05pm UTC](https://forum.lulzbot.com/t/bed-leveling-but-not-during-print/27414/9 "2025-03-20T16:05:39Z")

</div>

I just understand why when I do the bed leveling from the printer it works just fine, but when I go to print it doesn’t.

---

<div class="post-metadata">

**Author:** ![Elec-tech89](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@Elec-tech89](https://forum.lulzbot.com/u/Elec-tech89)\
**Post date:** [March 20, 2025, 5:05pm UTC](https://forum.lulzbot.com/t/bed-leveling-but-not-during-print/27414/10 "2025-03-20T17:05:21Z")

</div>

This is when i print from Octoprint

[](https://www.youtube.com/watch?v=ieU8SXnq3IQ)

---

<div class="post-metadata">

**Author:** ![Elec-tech89](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@Elec-tech89](https://forum.lulzbot.com/u/Elec-tech89)\
**Post date:** [March 20, 2025, 5:36pm UTC](https://forum.lulzbot.com/t/bed-leveling-but-not-during-print/27414/11 "2025-03-20T17:36:31Z")

</div>

And this is when I do the bed leveling from the printer.

[![](https://us1.discourse-cdn.com/flex020/uploads/lulzbot/original/2X/0/0aae77bf1f37ae4fa4e69612f64e5bc76c32e5b1.jpeg "bed leveling") ](https://www.youtube.com/watch?v=g_Dr0_GIouA)

---

<div class="post-metadata">

**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:** [March 20, 2025, 6:00pm UTC](https://forum.lulzbot.com/t/bed-leveling-but-not-during-print/27414/12 "2025-03-20T18:00:14Z")

</div>

The wipe procedure should be returning to the same spot and going back and forth from where it initially hits the wipe pad.

It starts here, at the correct spot in the pad:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/lulzbot/original/2X/7/7437f00e5ffde9c23d4e819d98189564f120e1a4.jpeg)

But by the end is off the pad here:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/lulzbot/original/2X/4/4e1ecb34eeaf03834104db15d3b7228cc1944813.jpeg)

Stepping through the frames of the video, I do not see any where the bed is not moving, so it doesn’t appear to be a loose belt or gear, but the FPS limits accuracy there.

What I did notice was the sound of the Y axis limit switch clicking exactly when it stops moving on the X axis. [https://youtu.be/ieU8SXnq3IQ?t=110](https://youtu.be/ieU8SXnq3IQ?t=110)

Because that limit switch is hit, it is ending the movement command, which was moving in both the X and Y. Then it goes to the next command, which is to probe the current location, which isn’t above the washer since movement was canceled.

So the underlying cause is the Y-axis shift during the wipe. Something is reducing the distance the bed is moving when the bed moves forward during the wipe. You can easily rule out drag on the nozzle from the wipe by pulling out the wipe pad and doing a quick test. This drag should not be the sole reason for failure, but if there’s another weak link, like an issue with a stepper or stepper driver, this resistance could be causing the issue.

---

<div class="post-metadata">

**Author:** ![Elec-tech89](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@Elec-tech89](https://forum.lulzbot.com/u/Elec-tech89)\
**Post date:** [March 28, 2025, 4:40pm UTC](https://forum.lulzbot.com/t/bed-leveling-but-not-during-print/27414/13 "2025-03-28T16:40:42Z")

</div>

Looks like its drag from the wipe pad. When I removed the wipe pad it worked just fine. So how do i fix it?

---

<div class="post-metadata">

**Author:** ![Elec-tech89](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@Elec-tech89](https://forum.lulzbot.com/u/Elec-tech89)\
**Post date:** [March 28, 2025, 5:36pm UTC](https://forum.lulzbot.com/t/bed-leveling-but-not-during-print/27414/14 "2025-03-28T17:36:18Z")

</div>

I figured out what happened! I had replaced the y-axis belt a while back and didn’t put the screws in correctly and it wasn’t tight enough so the y axis wasn’t moving right. Its working now!

---

<div class="post-metadata">

**Author:** ![Mushe](https://avatars.discourse-cdn.com/v4/letter/m/b3f665/32.png) [@Mushe](https://forum.lulzbot.com/u/Mushe)\
**Post date:** [July 6, 2026, 6:51pm UTC](https://forum.lulzbot.com/t/bed-leveling-but-not-during-print/27414/15 "2026-07-06T18:51:22Z")

</div>

Im having the same problem and might check the y axis belt
