[Request] Bed Level mesh about octoprint-eeprom-marlin

[KenLucke]

You do like to challenge me... We'll see what happens. Might be able to steal borrow the code from Bed level visualiser that generates the table of values, and make it so it can be edited, since I'm not good enough at KO bindings to work that one out (yet).

Also more feasible now I have an ABL system, since I can actually test this myself. Would be an interesting one to work through, for sure.

LOL, have to keep you on your toes!

[cp2004]

You do like to challenge me... We'll see what happens. Might be able to steal borrow the code from Bed level visualiser that generates the table of values, and make it so it can be edited, since I'm not good enough at KO bindings to work that one out (yet).

Also more feasible now I have an ABL system, since I can actually test this myself. Would be an interesting one to work through, for sure.

[jneilliii]

I don't really remember this one either Ken, but almost sounds like RESTORE_LEVELING_AFTER_G28 is not enabled in the firmware? @cp2004 my plugin does have an event hook your plugin could use to retrieve the mesh data....

[KenLucke]

I don't really remember this one either Ken, but almost sounds like RESTORE_LEVELING_AFTER_G28 is not enabled in the firmware? @cp2004 my plugin does have an event hook your plugin could use to retrieve the mesh data....

No, it's enabled, i double checked the firmware build.

[KenLucke]

I don't really remember this one either Ken, but almost sounds like RESTORE_LEVELING_AFTER_G28 is not enabled in the firmware? @cp2004 my plugin does have an event hook your plugin could use to retrieve the mesh data....

No, it's enabled, i double checked the firmware build.

//#define AUTO_BED_LEVELING_3POINT
//#define AUTO_BED_LEVELING_LINEAR
#if ANY(ABL_EZABL, ABL_BLTOUCH, ABL_NCSW, ABL_TOUCH_MI)
  #if ENABLED(ABL_UBL)
    #define AUTO_BED_LEVELING_UBL
  #elif ENABLED(ABL_BI)
    #define AUTO_BED_LEVELING_BILINEAR
  #endif
#else
  #define MESH_BED_LEVELING
#endif
/**
 * Normally G28 leaves leveling disabled on completion. Enable
 * this option to have G28 restore the prior leveling state.
 */
#define RESTORE_LEVELING_AFTER_G28

/**

[KenLucke]

I guess Nic hasn't done too much research into the bug, here's his response when I asked him to give me all the info he had on it:

I have never looked deep into it, I discovered first when making those hex lights where the first layer is super important, I found that following a power up, using G29 or using M420 S1 in the print, did not do what was expected in that the nozzle was too close to the bed and not at its correct height by z-offset. To resolve it, all I do is a home, and bed level from the menu, and save it, and from that point up until the next power up the M420 or G29 works fine, so it some bug that causes the 0+z-offset to be wrong, unless a full bed level and save is done.

[cp2004]

Some news on this one - there's a work-in-progress plugin for UBL mesh editing:

https://github.com/The-EG/OctoPrint-UBLMeshEdit/

Seen some demonstrations on the OctoPrint discord server, it looks very promising. If (when!) it makes it to the plugin repo, I don't think there's going to be much point in me implementing the same thing here.

[KenLucke]

Some news on this one - there's a work-in-progress plugin for UBL mesh editing:

https://github.com/The-EG/OctoPrint-UBLMeshEdit/

Seen some demonstrations on the OctoPrint discord server, it looks very promising. If (when!) it makes it to the plugin repo, I don't think there's going to be much point in me implementing the same thing here.

Thanks for the update!

[cp2004]

Going to close this, since the mentioned plugin seems to be going quite well having launched on the repository.