![Rat Rig Community [Unofficial]](https://cdn.discordapp.com/icons/582187371529764864/08375bea6b5b9088b6d4cfc2b6e25fba.webp?size=48){kind=icon}
First Layer Failure
motion🤷otherV-Core 4 (500) + Beacon + RatOS update → nozzle prints too high (first layer never reaches bed) / seems like mesh is getting overridden
Hey all — I’m stuck on a first-layer / Z height issue that started immediately after the latest RatOS update.
Setup: RatRig V-Core 4 (500x500), Beacon probe, RatOS
(Printer is currently on carpet, but this issue is new post-update — before the update I could at least get first layers down and finish prints.)
Problem
• On any print, the nozzle is too high and the first layer never reaches the bed.
• I can only get it to touch the bed if I manually adjust/reset the Z offset.
• I’ve re-run:
• Beacon calibration multiple times
• Commissioning guide steps
• Height Map / mesh calibration in the UI
Weird behavior I’m noticing
• When I start a print, the printer scans the bed again.
• After that scan, I see what looks like a different mesh/profile than the one I generated manually in the Height Map tab.
• There’s a mesh/height map entry labeled something like “RatOS” and its values/range look different (usually “shorter/smaller”) than my manual mesh.
• It feels like the print start routine is loading/creating a different mesh and/or overriding the Z offset, which leaves the nozzle too high.
What I’m asking
1. Is RatOS now generating/loading its own mesh during PRINT_START that can override the mesh from the Height Map tab?
2. Where do I check/fix this so the correct mesh + correct Z offset is used every print?
3. What’s the most common cause after an update: saved Z offset getting wiped, new beacon/z-offset behavior, or bed_mesh profile mismatch?
If there’s a specific macro/config section you want me to paste (PRINT_START, bed_mesh, beacon), tell me exactly which and I’ll post it.”
That keeps it “Discord-only” without you doing a whole info-dump upfront.
Hey all — I’m stuck on a first-layer / Z height issue that started immediately after the latest RatOS update.
Setup: RatRig V-Core 4 (500x500), Beacon probe, RatOS
(Printer is currently on carpet, but this issue is new post-update — before the update I could at least get first layers down and finish prints.)
Problem
• On any print, the nozzle is too high and the first layer never reaches the bed.
• I can only get it to touch the bed if I manually adjust/reset the Z offset.
• I’ve re-run:
• Beacon calibration multiple times
• Commissioning guide steps
• Height Map / mesh calibration in the UI
Weird behavior I’m noticing
• When I start a print, the printer scans the bed again.
• After that scan, I see what looks like a different mesh/profile than the one I generated manually in the Height Map tab.
• There’s a mesh/height map entry labeled something like “RatOS” and its values/range look different (usually “shorter/smaller”) than my manual mesh.
• It feels like the print start routine is loading/creating a different mesh and/or overriding the Z offset, which leaves the nozzle too high.
What I’m asking
1. Is RatOS now generating/loading its own mesh during PRINT_START that can override the mesh from the Height Map tab?
2. Where do I check/fix this so the correct mesh + correct Z offset is used every print?
3. What’s the most common cause after an update: saved Z offset getting wiped, new beacon/z-offset behavior, or bed_mesh profile mismatch?
If there’s a specific macro/config section you want me to paste (PRINT_START, bed_mesh, beacon), tell me exactly which and I’ll post it.”
That keeps it “Discord-only” without you doing a whole info-dump upfront.
![Rat Rig Community [Unofficial] banner](https://cdn.discordapp.com/banners/582187371529764864/4ee3e42e227d6aac26f048a3e69d5924.webp?size=480)
The #1 unofficial Rat Rig Community on Discord!
14,034Members
Resources
Was this page helpful?
![Rat Rig Community [Unofficial]](https://cdn.discordapp.com/icons/582187371529764864/08375bea6b5b9088b6d4cfc2b6e25fba.webp?size=16){kind=icon}