Mesh Bed Leveling (G80) command needs to be figured into position monitor maybe about octolapse HOT 3 CLOSED

Hmm.. G80 doesn't look like the standard mesh leveling code. Looks like I need to add more settings to my printer profiles to handle this, ug..

from octolapse.

So, here's what I've discovered and what I've done to correct it:

If you run G28, then G0 X25 y25 x100 on a Prusa, you'll end up at 25,25,100. If you then run a G80, it will re-home (sort of, I think it expects to be homed properly at this point), perform the mesh bed leveling, then return to a slightly different home position (maybe). I think this was done to maintain comparability with some other programs. I'm not sure why they didn't use the standard mesh bed leveling code. If anyone knows, please let me know. A logical explanation often leads to solutions.

I've added a list of commands that require acquisition of an up-to-date position (M400 + M114) to the printer profile. I add G29 and G28 by default (this is not configurable), and have added G80 to the Prusa profile. I've tested it with G28/G80, and it appears to work pretty well. Throwing M114s in your code around these commands (G28,M114,G80) seems to mess things up since I have no way to tell which M114 is mine and which is from somewhere else. To solve this problem i need to make the command unique somehow. I think maybe by adding a comment to m114 (m114;Octolapse) would work, but these are stripped from the commands when you use the commands() function. I'll ask Gina about this.

from octolapse.

I think I've figured this out. We can add additional commands that require a position read after completion. We probably need to add this to the default prusa profiles.

from octolapse.