SamrtABL seems to be non functional on my system

[ulfertg]

The problem

After reading the readme multiple times, uninstalling and reinstalling several times I still can't get the plugin to work.
It's totally possible that I'm doing something wrong, but as for now I have no idea what that could be.

The only thing in the readme which I'm not quite sure about is this sentence:

Warning: Prusa and Klipper require at least 1 ABL to track the state.

Is that something which I need to do manually?
Or does it mean that the first print has to be with ABL?

Other than that, I saw this in the side panel:
After installation of SmartABL the P/FP shows 0/5
After the first print (with ABL) finishes it shows: 1/5
Starting the second print ABL is performed again, after which the P/FP shows: 0/5
After the second print finishes P/FP shows 1/5 again

As said, it might be totally my mistake, but I still hope to find a pointer here.

Version of SmartABL

1.2.2

Version of OctoPrint

1.92

Operating system running OctoPrint

OctoPi 0.18.0

Printer model & used firmware incl. version

Prusa i3MK3S+ FW 3.13.0

Browser and version of browser, operating system running browser

No response

Checklist of files to include below

• Systeminfo Bundle (always include!)
• Contents of the JavaScript browser console (always include in cases of issues with the user interface)
• Screenshots and/or videos showing the problem (always include in case of issues with the user interface)
• GCODE file with which to reproduce (always include in case of issues with GCODE analysis or printing behaviour)

Additional information & file uploads

octoprint-systeminfo-20230729133341.zip
plugin_SmartABL.log
helper_disk_0.4n_0.2mm_PLA_MK3S_1m.gcode.zip

[scmanjarrez]

Hi, with that excerpt I meant that the first print when you connect your printer is automatically ABL enforced due to how prusa/klipper works (doesn't "allow" mesh saving). So the first print when you connect your printer always do an ABL (automatically) to start tracking the state.

Every time an ABL is triggered, the counter is reset, so the counter is set to 0. If you keep printing, the counter will be increased by one every time, and when you get to 5/5 (or the number you set), ABL is triggered again and the counter is reset.

For some reason, the output received from G81 (to query the mesh state) is incorrect, so you're forced to ABL again. Can you give me the output from the gcode G81?

[ulfertg]

Thank you for clarifying, I understand.

This is the output of G81 (after powering on the printer, connecting it to OctoPrint and printing one object):

end: G81
Recv: Num X,Y: 7,7
Recv: Z search height: 5.00
Recv: Measured points:
Recv:   0.03550  0.20800  0.32300  0.38600  0.36250  0.28450  0.26450
Recv:   0.14950  0.27050  0.34300  0.34350  0.36150  0.35600  0.29000
Recv:   0.18150  0.32050  0.40300  0.37450  0.37750  0.35200  0.25350
Recv:   0.13950  0.29150  0.36400  0.37400  0.32113  0.26800  0.16500
Recv:   0.20200  0.28950  0.34150  0.30962  0.26500  0.20950  0.07100
Recv:   0.23000  0.27950  0.28850  0.25800  0.20600  0.12800  -0.03150
Recv:   0.12950  0.16050  0.17100  0.09750  0.04350  -0.05850  -0.21300
Recv: ok

[scmanjarrez]

Is ABL being triggered every print? Can you share your logs after completing 2 o 3 prints?

[ulfertg]

Yes, every print.
The log I've attached to my first post was after two prints iirc.

Here are the logs after a couple of more prints:

octoprint-systeminfo-20230730121817.zip
plugin_SmartABL-2.log

[scmanjarrez]

can you test this? Start a print and paste the output here (right before ABL starts), I need the exact output of the G81, because I don't understand why the plugin isn't recognizing the above output (it should match)

[ulfertg]

This is the output:

Recv: echo:busy: processing
Recv: E-motor current scaling enabled
Recv: ok
Send: N18 G81*41
Recv: Mesh bed leveling not active.
Recv: ok
Send: N19 G80*41
Recv: T:214.9 /215.0 B:59.9 /60.0 T0:214.9 /215.0 @:28 B@:68 P:0.0 A:31.9
Recv: E-motor current scaling enabled
Recv: E-motor current scaling enabled
Recv: echo:busy: processing

[scmanjarrez]

I see, can you share your starting gcode? I don't know why you're receiving the message "Mesh bed leveling not active", that's why the plugin forces ABL

[ulfertg]

This is the output from the start (I hope that's what you meant? Or do you want the gcode of the printed file?):

Changing monitoring state from "Operational" to "Starting"
Send: N0 M110 N0*125
Recv: ok
Changing monitoring state from "Starting" to "Printing"
Send: N1 M73 P0 R1*21
Recv: NORMAL MODE: Percent done: 0; print time remaining in mins: 1; Change in mins: -1
Recv: SILENT MODE: Percent done: 100; print time remaining in mins: 0; Change in mins: -1
Recv: ok
Send: N2 M73 Q0 S1*22
Recv: T:214.8 /215.0 B:60.6 /60.0 T0:214.8 /215.0 @:30 B@:4 P:0.0 A:32.1
Recv: NORMAL MODE: Percent done: 0; print time remaining in mins: 1; Change in mins: -1
Recv: SILENT MODE: Percent done: 0; print time remaining in mins: 1; Change in mins: -1
Recv: ok
Send: N3 M201 X1000 Y1000 Z200 E5000*10
Recv: T:215.1 /215.0 B:60.5 /60.0 T0:215.1 /215.0 @:26 B@:26 P:0.0 A:32.1
Recv: ok
Send: N4 M203 X200 Y200 Z12 E120*8
Recv: ok
Send: N5 M204 S1250 T1250*39
Recv: ok
Send: N6 M205 X8.00 Y8.00 Z0.40 E4.50*57
Recv: ok
Send: N7 M205 S0 T0*36
Recv: ok
Send: N8 M862.3 P "MK3S"*12
Recv: ok
Send: N9 M862.1 P0.4*99
Recv: ok
Send: N10 M115 U3.11.0*97
Recv: ok
Send: N11 G90*32
Recv: ok
Send: N12 M83*43
Recv: ok
Send: N13 M104 S215*81
Recv: ok
Send: N14 M140 S60*102
Recv: ok
Send: N15 M190 S60*106
Recv: LCD status changed
Recv: LCD status changed
Recv: ok
Send: N16 M109 S215*89
Recv: LCD status changed
Recv: T:215.3 /215.0 B:60.5 /60.0 T0:215.3 /215.0 @:24 B@:20 P:0.0 A:31.8
Recv: T:215.1 E:0 W:1
Recv: echo:busy: processing
Recv: T:214.9 E:0 W:0
Recv: T:214.8 /215.0 B:60.4 /60.0 T0:214.8 /215.0 @:29 B@:38 P:0.0 A:32.0
Recv: LCD status changed
Recv: ok
Send: N17 G28 W*82
Recv: tmc2130_home_enter(axes_mask=0x01)
Recv:   0 step=45 mscnt= 735
Recv: tmc2130_goto_step 0 13 2 1000
Recv: tmc2130_home_exit tmc2130_sg_homing_axes_mask=0x01
Recv: tmc2130_home_enter(axes_mask=0x02)
Recv: T:215.1 /215.0 B:60.3 /60.0 T0:215.1 /215.0 @:26 B@:47 P:0.0 A:31.9
Recv: echo:busy: processing
Recv: T:215.0 /215.0 B:60.3 /60.0 T0:215.0 /215.0 @:27 B@:42 P:0.0 A:32.1
Recv: echo:busy: processing
Recv: T:215.1 /215.0 B:60.2 /60.0 T0:215.1 /215.0 @:26 B@:62 P:0.0 A:32.1
Recv:   0 step=33 mscnt= 543
Recv: tmc2130_goto_step 1 33 2 1000
Recv: tmc2130_home_exit tmc2130_sg_homing_axes_mask=0x02
Recv: echo:busy: processing
Recv: E-motor current scaling enabled
Recv: T:215.2 /215.0 B:60.2 /60.0 T0:215.2 /215.0 @:25 B@:49 P:0.0 A:31.9
Recv: echo:busy: processing
Recv: T:214.9 /215.0 B:60.0 /60.0 T0:214.9 /215.0 @:28 B@:66 P:0.0 A:32.0
Recv: echo:busy: processing
Recv: E-motor current scaling enabled
Recv: ok
Send: N18 G81*41
Recv: Mesh bed leveling not active.
Recv: ok
Send: N19 G80*41
Recv: T:214.9 /215.0 B:59.9 /60.0 T0:214.9 /215.0 @:28 B@:68 P:0.0 A:31.9
Recv: E-motor current scaling enabled
Recv: E-motor current scaling enabled
Recv: echo:busy: processing

[scmanjarrez]

I meant the gcode you use in the slicer, that is put on every file at the start

[ulfertg]

That should be this code (I use PrusaSlicer, the code it from the Start G-code section):

M862.3 P "[printer_model]" ; printer model check
M862.1 P[nozzle_diameter] ; nozzle diameter check
M115 U3.11.0 ; tell printer latest fw version
G90 ; use absolute coordinates
M83 ; extruder relative mode
M104 S[first_layer_temperature] ; set extruder temp
M140 S[first_layer_bed_temperature] ; set bed temp
M190 S[first_layer_bed_temperature] ; wait for bed temp
M109 S[first_layer_temperature] ; wait for extruder temp
G28 W ; home all without mesh bed level
G80 ; mesh bed leveling
{if filament_settings_id[initial_tool]=~/.*Prusament PA11.*/}
G1 Z0.3 F720
G1 Y-3 F1000 ; go outside print area
G92 E0
G1 X60 E9 F1000 ; intro line
G1 X200 E27 F500 ; intro line
{else}
G1 Z0.2 F720
G1 Y-3 F1000 ; go outside print area
G92 E0
G1 X60 E9 F1000 ; intro line
G1 X200 E30.5 F500 ; intro line
{endif}
G92 E0
M221 S{if layer_height<0.075}100{else}95{endif}

[scmanjarrez]

Can you test these commands in your octoprint terminal?

G28 W
G80
G81

And paste the output here?

[ulfertg]

Here it is:

[...]
Send: G28 W
Recv: tmc2130_home_enter(axes_mask=0x04)
[...]
Recv: tmc2130_home_exit tmc2130_sg_homing_axes_mask=0x04
Recv: tmc2130_home_enter(axes_mask=0x01)
Recv:   0 step=13 mscnt= 223
Recv: tmc2130_goto_step 0 13 2 1000
Recv: tmc2130_home_exit tmc2130_sg_homing_axes_mask=0x01
Recv: tmc2130_home_enter(axes_mask=0x02)
[...]
Recv:   0 step= 1 mscnt=  30
Recv: tmc2130_goto_step 1 33 2 1000
Recv: tmc2130_home_exit tmc2130_sg_homing_axes_mask=0x02
[...]
Recv: ok
[...]
Send: G80
[...]
Recv: LCD status changed
Recv: ok
[...]
Send: G81
Recv: Num X,Y: 7,7
Recv: Z search height: 5.00
Recv: Measured points:
Recv:   0.07550  0.20750  0.29750  0.36200  0.34550  0.29300  0.37700
Recv:   0.16300  0.24300  0.28750  0.27700  0.31450  0.33900  0.32000
Recv:   0.16750  0.26000  0.32500  0.29900  0.31350  0.31850  0.25350
Recv:   0.12050  0.22550  0.27500  0.28050  0.24750  0.20350  0.14100
Recv:   0.20200  0.24050  0.27400  0.23375  0.19250  0.16800  0.05900
Recv:   0.24400  0.24050  0.22800  0.18800  0.14750  0.09400  -0.01800
Recv:   0.17250  0.14600  0.12600  0.04450  0.01200  -0.05800  -0.15050
Recv: ok
[...]

I'm wondering, have you ever successfully tested this plugin on a Prusa MK3?
I'm beginning to wonder if it's even possible to store and reload an ABL mesh on a Prusa?

[scmanjarrez]

Some users have used SmartABL successfully in their prusa (all variants). I'm not loading the mesh from prusa because prusa doesn't have eeprom enabled in their firmware.

I don't know why the output from G81 is different now and when I send it from the plugin... for some reason the mesh is disabled when you start a print. I don't know what could be the problem, to be honest. I'll ask in discord if some user has encountered the same problem

[ulfertg]

As far as I understand it "G28 W" deletes the mesh data.
Hence "G81" after "G28 W" returns "Mesh bed leveling not active."
But I could be wrong.

[scmanjarrez]

No, G28 W just home your axes without doing ABL. G80 does the ABL, so it should return the mesh after G81 https://help.prusa3d.com/article/prusa-specific-g-codes_112173