cp2004 / OctoPrint-GCodeMacros

Configure custom gcode macros you can use anywhere!
https://plugins.octoprint.org/plugins/gcode_macro
GNU Affero General Public License v3.0
7 stars 2 forks source link

@BEDLEVELVISUALIZER #14

Open Supreme-Bob opened 1 year ago

Supreme-Bob commented 1 year ago

Adding @BEDLEVELVISUALIZER to a macro seems to get ignored. I'm using both the BedLevelVisualizer and BLTouch plugins

I've created a Macro that includes the @BEDLEVELVISUALIZER then used that macro in the probe bed script on the BLTouch Plugin. The BedLevelVisualizer doesn't pickup the command and start watching for the mesh. @ABL macro

M140 S50 ; starting by heating the bed for nominal mesh accuracy
M117 Homing all axes ; send message to printer display
G28      ; home all axes
M420 S0  ; Turning off bed leveling while probing, if firmware is set
         ; to restore after G28
M117 Heating the bed ; send message to printer display
M190 S50 ; waiting until the bed is fully warmed up
M117 Creating the bed mesh levels ; send message to printer display
M155 S30 ; reduce temperature reporting rate to reduce output pollution
@BEDLEVELVISUALIZER ; tell the plugin to watch for reported mesh
G29 T      ; run bilinear probing
M155 S3  ; reset temperature reporting
M140 S0 ; cooling down the bed
M500 ; store mesh in EEPROM
M117 Bed mesh levels completed ; send message to printer display

If I change the BLTouch Plugin bed probe to this it works fine.

@BEDLEVELVISUALIZER
@ABL

If I use the @ABL macro from the octoprint terminal the @BEDLEVELVISUALIZER in the macro also doesn't work.

https://plugins.octoprint.org/plugins/bedlevelvisualizer/ https://github.com/jneilliii/OctoPrint-Bltouch

cp2004 commented 1 year ago

Sorry, I don't currently have time to look into this and might not for a couple of weeks. If I can get to it I will of course let you know. There have been issues before about this plugin intercepting too many @ commands so I wonder if it is another case of that.