search

jneilliii / OctoPrint-BedLevelVisualizer

MIT License
373 stars 82 forks source link

[BUG]: Prusa MBL - 3.14.0 Firmware for MK3, MK3S, MK3S+, MK2.5 and MK2.5S #672

Closed EnduringGuerila closed 1 month ago

EnduringGuerila commented 1 month ago

https://github.com/prusa3d/Prusa-Firmware/releases/tag/v3.14.0

Describe the bug The firmware update linked above says there were MBL improvements. I tried running the visualizer and it got stuck twice. It tried to calibrate the Z height both times, slowly moving all the way to the top and running into the stops, would come back down and try again. Then it ended telling me on the printer to run "Calibrate Z"

I assume now we'll need a more complicated set of commands like for the MK4.

Debug Log Sorry, I wiped the plugin thinking that might help before realizing there was a MBL change in the latest firmware. I didn't want to rerun the visualizer just to generate a log. Can do if truly needed though

Screenshots

G80         ; run mesh bed leveling routine.
@BEDLEVELVISUALIZER ; instruct plugin to start recording responses from printer.
G81         ; report mesh bed leveling status.

enabled Flip Y-Axis everything else is default

Firmware and Version 3.14.0 1.1.1

EnduringGuerila commented 1 month ago

It looks like the gcode in the slicer had to be updated to:

G80 X{first_layer_print_min[0]} Y{first_layer_print_min[1]} W{(first_layer_print_max[0]) - (first_layer_print_min[0])} H{(first_layer_print_max[1]) - (first_layer_print_min[1])} ; mesh bed levelling from the system presets

This will probably help the Bed Visualizer too.

Edit: Updated the command in Bed Visualizer and it did run successfully but only 3x3 instead of 7x7.

Edit2: reran with just G80 _(no 'X{firstlayer..} etc.) and it still only did 3x3. I read more and the extended command is for only running the MBL on the needed print area as opposed to the whole bed.

Edit3: I'm just sleep deprived. It's 'hidden' in the printer settings to switch it to 7x7. After that, just G80 works. I think the original issue was just with updating the firmware and not recalibrating before trying bed visualizer. Now I just need to fix my uneven bed...

image (I changed the scale to 1,1 instead of default 2,2, but still that's bad.