j-be/autobim

A bed tramming utility for OctoPrint using ABL

cv-jekyll

My CV

Run it locally:

• bundle install --path vendor/bundle
• bundle exec jekyll serve

autobim's Issues

Does not complete check on Ender 3 Pro

Installed the plugin just fine.
ran it and levelled the first two points and then it just stops. says moving t the next point but does not.
Have restarted OctoPrint and the printer. retried and same happens.
Running Marlin 2.0.9.1 with a glass bed and BLtouch.

The Bed visualizer plugin works for my system, but thought this would be easier to make changes to the bed.

Thanks in advance.

repeated runs don't measure the same

I find it confusing that when I complete a run and immediately start another one it already wants to change the level again. If I've successfully completed a run and start a new run shouldn't it measure the same as before?

UBL causes 3-point leveling at start of tramming

Hello,
I recently installed Jyer's Marlin fork (https://github.com/Jyers/Marlin) on my Ender-3V2. The firmware supports UBL.

I noticed that when AutoBim starts tramming, a G29 J command is executed.
When G29 J is executed in an UBL-activated firmware, a 3-point leveling action is performed instead of turning off levelling compensation. (https://marlinfw.org/docs/gcode/G029-ubl.html)

As far as I can tell from the Marlin docs, a G29 P0 is the equivalent command for UBL.

Left Corner repeated probing Creality Ender 5 Plus

Bug report

Left Corner repeated probing Creality Ender 5 Plus

Description

I have settings after Home test OK:-
X 30 Y 30 Tests OK at Front Left
X 300 Y 30 Tests OK at Front Right
X 300 Y 300 Tests OK at Front Back
X 30 Y 300 Tests OK at Left Back

Steps to reproduce

Click on AutoBim button in OctoPrint

What did you do to make the issue appear? More detailed is usually more better.

Expected outcome

To test all corners
Describe what you expected would happen after you executed the steps above.
To display an image height map

Actual outcome

Keeps Probling repeatedly in the left front corner
Describe what actually happened.
Keeps Probling repeatedly in the left front corner
I stop it Abort

Environment (leave empty if unknown or not relevant)

BLTouch Creality Ender 5 Plus

• OctoPrint version: OctoPrint 1.9.3
• Python version: Python 3.9.2
• Marlin version: Marlin-2.1.2
• Probe (e.g. BL-Touch, EZABL, ...): BL-Touch
• Printer (manufacturer/model, and please state any relevant modifications, like e.g. aftermarket mainboard): Creality Ender 5 Plus, Bigtree Tech Octopus V1.1 STM32F446ZET6 chip, BBT TF35 Dual display
• Browser (especially useful on UI issues): Chome
  OctoPi* 1.0.0 (build 2023.07.18.111854
  For UI issues a screenshot always helps.

Feature

Please note by far the quickest way to get a new feature is to file a Pull Request.

Just describe what you would like AutoBim as detailed as you can.

Question

Make sure your question is not covered by the Troubleshooting section.

Else: just fire away. But keep in mind: the more detail, the easier it is to answer 😃.

G30 coordinates ignoring probe offset

I am running Klipper, BLTouch is set up correctly with the X and Y offsets, following the Klipper documentation and Bed_Mesh works as expected. Added the G29 and G30 Macros to my Klipper config, both seem to respond to commands without an error.

When running through the Preparation section I used G0 X150 Y150 for the middle of the bed. When issuing the G30 X150 Y150 it does not move the probe over to the location of the nozzle, instead it probes in the same spot. If I was to issue G30 X183 Y139 to take into account my probe offset it moves to where I expect.

• OctoPrint version: 1.7.2
• Python version: 3.7.3
• Klipper version: 0.9.1-490-g8eef1e21
• Probe (e.g. BL-Touch, EZABL, ...): BLTouch
• Printer (manufacturer/moodel, and please state any relevant modifications, like e.g. aftermarket mainboard): Creality CR-10
• Browser (especially useful on UI issues): Chrome/96.0.4664.93

Feature Requests: Bed Heating and Auto Stop

Feature

There are a couple of features that I would love to see added to AutoBim:
When starting the autobim routine it should heat up the build plate and stabilize the temp before probing for more accurate results, you could add settings to the main settings page to adjust the pre-heat temp and wait time once temp is reached before probing starts. This seems like it should be relatively easy to add.

The other feature that would be awesome to have though slightly harder to add due to the logic needed to make it work would be a routine that checks to see if it's made a complete 4 point set of probes without calling for any adjustments then it ends the autobim routine automatically. You would need to have some if / then checks and if any 1 point needs adjustment it resets the check and starts it over once it goes back to location 1. I'm sure with enough effort this should be possible to map out but my programming skills are pretty rusty and my octoprint plugin programming skills are non-existant lol.

Thanks for creating an awesome plugin, I just wish I had found it sooner lol. I will definitely be sharing it with all of my friends.

After probing the first corner the first time M112 emergency stop issued, same as stuck waiting?

After probing the first corner the first time, occasionally my printer will issue an M112 emergency stop command and need to be reset/restarted and I'm not sure why

Steps to reproduce

Not sure honestly, it'll occasionally happen a couple times in a row. When I haven't been able to get past the first probe I've tried running G29 P4 T(Running the Bed Level Visualizer mesh update gcode for marlin), it's run from the bed level visualizer plugin for octoprint. I'll adjust the bed and eventually try AutoBim again and it'll work

Expected outcome

That it will go through the whole tramming/probing sequence without sending an M112

Actual outcome

M112

Environment (leave empty if unknown or not relevant)

• OctoPrint version: OctoPrint: 1.7.3
• Python version: Python 2.7.16
• Marlin version: 2.0.9.3
• Probe (e.g. BL-Touch, EZABL, ...):
• Printer: Ender 3, BTT SKR MINI E3 V2.0 + TFT35 E3 V3, dual z, Micro Swiss DD and Hotend
• Browser Un-Google'd Chromium on Arch Linux X86-64

Question

I wouldn't have asked about this if I was stuck at waiting as in the troubleshooting section, so I'm sorry if this is the same thing. Is this the same issue as the stuck at waiting after first probe

3 Point leveling for Ender2

Autobim requires a 4 point leveling? My Ender2 has a 3 point leveling heatbed. Is it possible to make the number of points configurable?

Stops at second point

Firstly, let me say I love this idea!

Only problem is that once I get point 1 to the right height, when the probe moves to point 2 it measures until I adjust correctly and then fails to move on to the next point.

Cannot probe over adjustment knobs on ender 3 pro

Description

I cannot get AutoBim to probe the points over any of the adjustment screws via running or the test buttons. I'm trying to reach X71 Y43 to X240 Y218. The probe position limits that do work seem arbitrary. It will not probe anything below X88 Y50 or above X235 Y197. The 235 I could maybe understand, since that is my bed size. I'm able to position the probe over the points I want using G0 without issue (ie: G0 X71 Y43 works just fine). Below are the firmware lines I could think might be relevant to this, but I feel like I'm just missing something. Is there another setting I should be looking at in the firmware or do the above limits make sense to anyone based on the below config info?

#define AUTO_BED_LEVELING_BILINEAR

X_BED_SIZE 235
Y_BED_SIZE 235

X_MIN_POS 0
Y_MIN_POS 0
X_MAX_POS (X_BED_SIZE + 5)                               = 240
Y_MAX_POS (Y_BED_SIZE + 5)                               = 240

Z_SAFE_HOMING_X_POINT ((X_BED_SIZE)/2) + 44	         = 161.5
Z_SAFE_HOMING_Y_POINT ((Y_BED_SIZE)/2) + 6	         = 123.5

NOZZLE_TO_PROBE_OFFSET {-44, -6, 0}

PROBING_MARGIN 10

Environment (leave empty if unknown or not relevant)

• OctoPrint version: Version 1.7.2
• Octopi:Version 0.18.0, running on Raspberry Pi 2 Model B Rev 1.1
• Python version:
• Marlin version: Marlin-bugfix-2.0.x
• Probe: BL-Touch 3.1
• Printer: Ender 3 Pro
• Browser: Chrome

Sensor position issues aside, AWSOME work on this plugin. I never felt like I was doing quite good enough with paper or feeler gauges, even when doing multiple rounds, but with this plugin my first layers are looking awesome and sticking great. THANK YOU!

Temperature reporting conflict.

Bug report

Temperature reporting conflict.

Description

After a corner or two adjustments become "huge" By process of elimination, I believe the temperature reports in the com stream are confusing AutoBim.

Steps to reproduce

Happens by default in my installation/environment. It is necessary to issue an M155 S(large num of seconds) then remember to set back to M155 S3 once complete.

Expected outcome

Had this issue with another bed leveler plugin. (Bed Visualizer). In that case the plugin provides a place to auto send M155 before and after the process.

Actual outcome

Will never complete because of the confusion.

Describe what actually happened.

Environment (leave empty if unknown or not relevant)

• OctoPrint version: 1.6.1
• Octopi: 0.18
• Python version: 3.7.3
• Marlin version: 2.0.9
• Probe (e.g. BL-Touch
• Printer Ender 3 Pro with 4.2.7 board
• Browser (especially useful on UI issues): Chrome/93.0.4577.63 Safari/537.36

For UI issues a screenshot always helps.

Feature

A place to indicate the number of seconds to disable temperature reporting, then reenable automatically on exit or user cancel

Please note by far the quickest way to get a new feature is to file a Pull Request.

Just describe what you would like AutoBim as detailed as you can.

Question

Make sure your question is not covered by the Troubleshooting section.
I did not see this issue in troubleshooting or open issues. Sorry if it is addresssed.
Else: just fire away. But keep in mind: the more detail, the easier it is to answer 😃.

Logic Issue

So there is a logic issue with the testing methodology implemented.

The issue is when setting the threshold is set at the lowest resolution that the firmware is reporting.

I tested my probe and got
Recv: Mean: 0.008478 Min: 0.007 Max: 0.009 Range: 0.003
Recv: Standard Deviation: 0.000844

but usually the range is closer to 0.006

But because the firmware only outputs 2 decimals, there is an inherent rounding issue where that range is really 0.02 because it can be + or - and is statistically random when it can occur.

A recommendation to help this issue (wont totally mitigate it) would be to have the AutoBIM test the point 2 separate times and compare the z value, if the z value matches than that can be reported for the adjustment. If they don't match then probe a 3rd time and average the values and round. That way if 1 comes back 0.01 and the other 0.00 if the 3rd comes back 0.01 then it would round to 0.01 but if the 3rd comes back as 0.00 it would round to 0.00. This will help prevent the issue of constantly going around and around the bed because of this possible rounding issue and having the autobim never finish unless manually cancelled.

[FR] Custom @AUTOBIM GCode Command

It would be awesome if you could add a custom @autobim command to your plugin so that we could initialize the process from other please, ie OctoDash using Custom Actions.

More information on implementation can be found here, works very similar to the gcode hooks you are already using.

https://docs.octoprint.org/en/master/plugins/hooks.html#octoprint-comm-protocol-atcommand-phase

Ender 3 S1 Pro Can't reach coordinates

Hello!

I just installed TH3D's LCD screen and unified firmware on my s1 pro. In octoprint, when I send the command g0 x30 y30, the nozzle will move to that location but the probe is no longer on the bed. When I try to test that point in Autobim (after homing, first) it tells me that it cannot reach those very same coordinates.

When I try to manually change the coordinates, the max that I can reach in the autobim menu is still way off of the adjuster knob screws. I'm fairly new to modifying a printer this in-depth, and I have no idea how to fix the issue.

What are your thoughts?

Stuck on Wait..... Point X Y seems to be unreachable

Bug report

Please do not report the "Works fine on the first (or first and second corner), display says 'ok. moving to next' but
nothing happens" bug. This is covered in detail in the "Troubleshooting" section of the README. I know it is an issue
for many, and it is on the roadmap, but unfortunately it isn't an easy fix.

Description

When Autobim is started it will home and then move to the first corner, probe, then move and say "wait." Also when I go into the settings and probe each test point it successfully probes, however it tells me "Point X30 Y30 seems to be unreachable!"

Steps to reproduce

Press the AutoBim button.
Also going into the settings and testing each point.

Expected outcome

I would expect it to probe then tell me how much to adjust before probing again.

Actual outcome

Sit on the screen that says wait.

Environment (leave empty if unknown or not relevant)

• OctoPrint version: 1.9.2
• Python version:
• Marlin version: 2.1.x
• Probe (e.g. BL-Touch, EZABL, ...): BL-Touch
• Printer (manufacturer/moodel, and please state any relevant modifications, like e.g. aftermarket mainboard): Ender 3 Pro with SKR mini E3 v3.0
• Browser (especially useful on UI issues):

For UI issues a screenshot always helps.

Add a button to settings allowing to validate the corner points

The plugin cannot determine if a given probe point is reachable or not. Afaik. It would need to take into account at least the following from Marlin:

• X_MAX_POS and Y_MAX_POS
• NOZZLE_TO_PROBE_OFFSET - can be queried using M851 - XYZ Probe Offset
• PROBING_MARGIN

but it seems it cannot get either of those.

So maybe we just add a button which makes one round like:

1. Click button
2. Send G30 <corner>
3. Dialog to user "Does printer move? Yes - No"
4. Try to correct corner point, goto 2

EDIT: Added reference to M851

Ender 3 S1

Worked fine on an Ender 3 S1 stock firmware 1.0.3C but the bed measurements need to be adjusted to:

x 10 - y 25
x 20 - y 179
x 179 - y 179
x 179 - y 25

I think the probe points (hence the x10 - y25) should sit on top of the screws for better measurement/alignment but that is my personal feeling.

Juri, this is an amazing plugin so thank you!

Avoid scrolling text on LCD

As reported here the text starts scrolling when it is too long. It shall be improved to avoid scrolling.

Inconsistent readings

Description

Inconsistent readings

Steps to reproduce

This happens often but not every time and not always on the same corner. When I adjust a corner, i'll get a message that says "0.05 >>>". If I don't touch anything and let it run a couple cycles, it will randomly jump to something like "0.09 >>>". I checked the frame and rollers, and everything is tight.

Expected outcome

I would expect if I don't adjust anything, the reading would stay the same.

Actual outcome

See description

Environment (leave empty if unknown or not relevant)

• OctoPrint version: 1.7.3
• Python version: 3.8
• Marlin version: IDK
• Probe (e.g. BL-Touch, EZABL, ...): BL-Touch
• Printer (manufacturer/moodel, and please state any relevant modifications, like e.g. aftermarket mainboard): Ender 3 V2 stock board
• Browser (especially useful on UI issues): Chrome

X and Y higher resolution and bed temp and nozzle temp upvote

I am sorry that I am unfamiliar enough to know how a pull request works.

I would like to request that when setting the four test positions, can two decimal places beyond the whole number be used also?
like instead of x:30 y:30 it could be x29.85 y:30.05?

Also I would like to second the notion of what i seen request in another of being able in a input, or drop down if you can figure out how to heat up the bed and nozzle both. I know when I do the mesh, ( the bi-linear one?) to really zero in the bed i need to heat up both the bed and nozzle.

I am on a Ender 3 pro. BLtouch, hemera all-in-one head, BRR turbo board.

But yes I would like to officially upvote that possibility of adding a function to preheat bead and nozzle to a temp first .

..and also adding a bit more resolution to the X and Y points locations.

Cannot get Z for corner

Hello,

I am using P.I.N.D.A 2 clone probe on my Ender 3 PRO. It apprears that it might have a problem with probes that are normally open? I guess that BLTouch, for example, is normally closed.

I am not an expert but it might be an issue. If not, just take it as a standard issue report with unknown cause.

Steps to reproduce:

1. Have a P.I.N.D.A 2 clone probe installed and configured with UBL
2. Open octoprint and start AutoBim
3. Printer homes while showing text "wait..."
4. Printer moves up a little, makes a multiple sounds (like when you use M500)
5. "3D Printer Ready" and nothing happens. Looks like it follows instructions to STEP 2 and then skips the others.

(I will send a video if needed.)

PS: I do have UBL set to true in your plugin. It is also updated to the latest version.

Hardware and firmware I'm using:
Ender 3 Pro
P.I.N.D.A 2 clone
Raspberry Pi Zero W
RepRapDiscount Full Graphic Smart Controller
SKR1.4 (LPC1768)
Marlin firmware 2.0.x bugfix (download: https://gofile.io/d/COue2N)

[FR] LEVEL_CORNERS_USE_PROBE

What do you think about this :

Add a option to level the bed corners using a probe. Instead of using the nozzle to paper and ajust the screws, it will probe the first corner (or the center) and save the z position. Then will go to the next corner to check if is within tolerance range. If is in tolerance, will go to next corner. If is not, will leave the probe deployed waiting the user to raise the bed until the probe is trigered. When all corners are within tolerance, will present an option to execute bed leveling.

This is how the option #define LEVEL_CORNERS_USE_PROBE works in Marlin.

Just a button to run this functionnality like when clicking on 'Level Corner' on printer's screen when this option is enabled in Marlin.

Hotend does not move after 2nd point.

I have AutoBim on my Ender3v2 running Jyers and it runs just fine. I love it.

However on my Ender3 Pro I have Marlin2.0 bugfix running and when I try to use AutoBim I will level the 1st and 2nd point just fine, but then the LCD display's that it's going to the next point and it the hotend doesn't move. I have to abort in Octoprint.

Wondering if this is a firmware issue?

Add button to execute an M48 - Probe Accuracy Test and use it to validate accuracy

Currently, it is hardly possible to determine whether Accuracy threshold in settings has a value matching the individual printer.

Using an M48 we get a report like:

Mean: 0.005000 Min: 0.003 Max: 0.010 Range: 0.007
Standard Deviation: 0.002500

Should be Accuracy threshold according to Range. I think half of it is the hard limit, so anything:

• Accuracy threshold >= Range: All good
• Accuracy threshold between Range and Range / 2: Warning - that's ambitious
• Accuracy threshold <= Range / 2: Error: no way that's gonna get you anywhere

UBL - G29 P0 is the wrong command

Haven't tried your plugin yet, but I will when I get the chance. This bug is based on a previous resolved issue.

For those of us using UBL, you issue G29 P0 to disable it before probing. Unfortunately, G29 P0 is not the right command. It doesn't disable UBL, it zeros the entire mesh. This is bad, as UBL meshes can take upwards of 15 minutes to generate. If someone were to save to EEPROM after running this, their mesh would be permanently erased, and they likely wouldn't know. Even without saving to EEPROM, their mesh would stay zeroed until they reboot the printer (or maybe just until re-loading the mesh).

The correct command is G29 D.

Although it makes sense to discard an existing non-UBL mesh (since the mesh will now be wrong), UBL has the tilt mesh feature (G29 J), so it will still accurately account for the warp of a bed.

Add wait time before moving to other corner

Suggestion:
Add a 2 second delay before moving to other corner.

Reason:
AutoBim tends to send move command to other corner immediately after desired distance is met while my big hand is still holding knob. It would be good if I had time to pull it out to avoid accidentally turning the knob with it.

Expected behaviour:

1. Measure Z distance until desired threshold is met
2. Move Z up a little to signal that conditions are met (or beep via M300)
3. Wait 1 - 2 seconds
4. Move to the other corner

Something weird is going on

Recv: Bed X: 30.00 Y: 30.00 Z: 0.04
Recv: X:74.00 Y:37.00 Z:11.45 E:3158.73 Count X:5915 Y:2969 Z:4573
Recv: ok
Send: M117 0.02 >>> (adjust)
[...]
Recv: //action:notification 0.02 >>> (adjust)
Recv: ok
Send: G30 X30 Y30
[...]
Recv: Bed X: 30.00 Y: 30.00 Z: 0.03
Recv: X:74.00 Y:37.00 Z:11.45 E:3158.73 Count X:5915 Y:2969 Z:4573
Recv: ok
Send: M117 0.04 >>> (adjust)
Recv: //action:notification 0.04 >>> (adjust)
Recv: ok
Send: G30 X30 Y30
[...]
Recv: Bed X: 30.00 Y: 30.00 Z: 0.03
Recv: X:74.00 Y:37.00 Z:11.45 E:3158.73 Count X:5915 Y:2969 Z:4573
Recv: ok
Send: M117 0.03 >>> (adjust)

Been having issues where I can go around and around and it never stops having me adjust everything so pulled the terminal logs. Looks like there is something wrong in the plugin because it goes Z0.04 telling me to adjust 0.02 and then Z0.03 telling my to adjust 0.04... How is that possible?

Recv: Bed X: 30.00 Y: 30.00 Z: 0.03
Recv: X:74.00 Y:37.00 Z:11.45 E:3158.73 Count X:5915 Y:2969 Z:4573
Recv: ok
[...]
Send: M117 0.04 >>> (adjust)
Recv: //action:notification 0.04 >>> (adjust)
Recv: ok
Send: G30 X30 Y30
[...]
Recv: Bed X: 30.00 Y: 30.00 Z: 0.03
Recv: X:74.00 Y:37.00 Z:11.45 E:3158.73 Count X:5915 Y:2969 Z:4573
Recv: ok
Send: M117 0.03 >>> (adjust)
Recv: //action:notification 0.03 >>> (adjust)
Recv: ok
Send: G30 X30 Y30

There has to be sound rounding errors going on here.

Recv: M48 Z-Probe Repeatability Test
[...]
Recv: Finished!
Recv: Mean: -0.000776 Min: -0.004 Max: 0.003 Range: 0.008
Recv: Standard Deviation: 0.002130
Recv:
Recv: X:154.00 Y:117.00 Z:11.45 E:3158.73 Count X:12309 Y:9388 Z:4573
Recv: ok

My probe accuracy is well within the 0.01 that the plugin uses.

Allow a timer inbetween probes

Would be nice to be able to make the pause in-between the probing of 1 corner longer. It probes twice and then really only shows the results when it is ready to probe again which gives you a very small window to put the corrections in.

requested feature probing failed

Hello

first of all i really like this plugin.

my bltouch on one of my printers regularly fails at probing, normally i just restart my print and than it probes fine and the print starts
I use jyers firmware which probes 10x10 points when i make a mesh but when it fails probing it just restarts the failed probing point.
Is it possible to add this feature to the plugin? because now when the probing fails i have to restart the whole procedure and start again at point 1.

thanks in advance

Sincerely

Look at the printers screen

uuuh the screen on the printer isn't showing anything... Am I doing it wrong? I'm running a Ender 5 plus.

thanks

Add option to choose corner travel order

First of all, thanks for the plugin, its awesome and really made my life easier since i don't have enough progmem to add anything else on Marlin.
I would like to suggest an option to choose the path between the corners, instead of only the "square" shape.
Something like this, lets assume the default order the head will move and probe is this one:
B------C
|---x---|
A------D
From A to B, C and D.
The user could then input the path he/she wants to override, like an X pattern: ACDB or ADBC.

Ender 3 Max - Point X30 Y300 seems to be unreachable!

I am running a E3 Max with LCD screen, CR touch and Jyers firmware, but cant get the plugin to work. When I press the tram button the printer homes and just hovers or tells me Point X30 Y300 seems to be unreachable!.

The extension works great on my 3V2, so I'm not sure what might be wrong, considering the motherboard, screen and firmware are the same.

'ok. moving to next' on first probe point when disabling Mulitpass probing

Description

I know that this error had been reported before, but the process does run fine when Mulitpass probing is enabled. I had gone through the steps in the FAQ, but they do not seem to fix the issue.

I seem to only see this issue when Mulitpass probing is disabled. The probe gets the reference either from Z offset, or from the First Corner, it then moves on to the first probe point and then just gets stuck on that point. Looking at the terminal output, it seems as though the plugin is just repeating the same G30 X28 Y198 command:

Send: M117 wait...
Recv: ok

Send: G91
Recv: ok

Send: G28 X0 Y0 Z0
Recv: X:165.00 Y:129.00 Z:11.30 E:0.00 Count X:13200 Y:10320 Z:4520
Recv: ok

Send: G90
Recv: ok

Send: G0 Z20
Recv: ok

Send: G29 J
Recv: ok

Send: G30 X28 Y198
Recv: Bed X: 28.00 Y: 198.00 Z: 0.23
Recv: X:71.00 Y:207.00 Z:11.30 E:0.00 Count X:5680 Y:16560 Z:4520
Recv: ok

Send: M117 ok. moving to next
Recv: ok

Send: G30 X28 Y198
Recv: Bed X: 28.00 Y: 198.00 Z: 0.24
Recv: X:71.00 Y:207.00 Z:11.30 E:0.00 Count X:5680 Y:16560 Z:4520
Recv: ok

Send: G30 X28 Y198
Recv: Bed X: 28.00 Y: 198.00 Z: 0.25
Recv: X:71.00 Y:207.00 Z:11.30 E:0.00 Count X:5680 Y:16560 Z:4520
Recv: ok

Send: M117 Aborted by user
Recv: ok

Steps to reproduce

I just disabled Mulitpass probing, and also tested both with First corner is reference enabled and disabled.

Not sure whether it is related, but I had changed the order in which the points are probed as follows:
┌─────┐
│1............2│
│.................│
│4............3│
└─────┘
I confirmed beforehand whether these points could in fact be probed by following the steps in the FAQ.

The only way I found to fix this is by going to the Plugin Manager, and then clicking Cleanup Plugin Data.

Expected outcome

I expected that disabling the Mulitpass probing and enabling First corner is reference would allow the plugin to check the reference point once and then probe the other 3 corners so that I can level them to that point. (Similarly to how G35 works)

Environment

• OctoPrint version: 1.7.2 (OctoPi Version 0.18.0, running on Raspberry Pi 3 Model B Rev 1.2)
• Python version: 3.7.3
• Marlin version: 2.0.9.2
• Probe: BLTouch Smart V3.1 2019 Edition
• Printer: Creality Ender 3 Pro 2019 Edition
• Browser: Google Chrome Version 96.0.4664.110

Where is the button / screen?

I just installed this plugin in octopi 0.18.0 (with octoprint Version 1.6.1) on a Pi 3b+ connected to a Ender 3 v2 with Jyers firmware 1.32 with BLtouch and UBL.

In Octopi I did not see the plugin in the repository list, so I installed it by url as instructed in the readme.
I can see it installed; in the settings I can see AutoBim under the plugins.
In the settings I enabled "show button in Navbar and restarted the Pi (all AutoBim sttings see below).

However, there is no button in the UI I can see, where is it supposed to be visible?
In the settings page - plugins AutoBim I can "Start AutoBim"and my printer start probing the four corners. The result of a probe is only visible in the "Printer Notifications"section of Octopi.

Is there anything I did miss or must change for the AutoBim button / UI to be visible?

AutoBim settings I have are:
invert arrows : off
Multipass: on
Accuracy 0.02
UBL: on
points: all default
show button in navbar: on

Stuck on "wait..."

Bug report

Please do not report the "Works fine on the first (or first and second corner), display says 'ok. moving to next' but
nothing happens" bug. This is covered in detail in the "Troubleshooting" section of the README. I know it is an issue
for many, and it is on the roadmap, but unfortunately it isn't an easy fix.

Description

Briefly describe your issue.
After clicking to begin autobim just says wait... it does G28 then but never continues
I finally get the error
AutoBim aborted
Cannot probe X30 Y30! Please check settings!
I think It is because of the location it thinks is outside of the workable area?

Steps to reproduce

click the autobim button

What did you do to make the issue appear? More detailed is usually more better.

Expected outcome

continue the autobim process

Describe what you expected would happen after you executed the steps above.

Actual outcome

it sits there after a G28 is issue from autobim.

Describe what actually happened.

Environment (leave empty if unknown or not relevant)

• OctoPrint version:
• Python version:
• Marlin version:
• Probe (e.g. BL-Touch, EZABL, ...):
• Printer (manufacturer/moodel, and please state any relevant modifications, like e.g. aftermarket mainboard):
• Browser (especially useful on UI issues):

For UI issues a screenshot always helps.

Feature

Please note by far the quickest way to get a new feature is to file a Pull Request.

Just describe what you would like AutoBim as detailed as you can.

Question

Make sure your question is not covered by the Troubleshooting section.

Else: just fire away. But keep in mind: the more detail, the easier it is to answer 😃.

Starting z offset problem (maybe due to low center on bed)

Please remove all sections not relevant to this issue (including this statement).

Bug report

Please do not report the "Works fine on the first (or first and second corner), display says 'ok. moving to next' but
nothing happens" bug. This is covered in detail in the "Troubleshooting" section of the README. I know it is an issue
for many, and it is on the roadmap, but unfortunately it isn't an easy fix.

Description

I was using the Jyers firmware Probe Assisted tramming which has a thousandth mm precision and had the bed pretty level. When I tried using autobim it would tell me I had a +.08 offset at the first corner. After leveling everything and it doing a full round and saying done. I tried to do another round to make sure it was good and it started off saying it was .07 mm again.

Steps to reproduce

Checked with manual level to see where the corners were in relation. Ran the Autobim process through again. Verified manually leveling precision and starting autobim a 3rd time. Manual leveling was +.001/.000/.000/-.008. After starting autobim a 3rd time it reported again a .007 difference.

Expected outcome

I would have expected it to run around all 4 corners and confirm that the autobim process was good. I would like to see a probe of all 4 corners similar to the Probe Assisted Tramming and an offset target based on all 4 corners. I believe the fact that I have a low center is causing it to want to raise the bed each time.

Actual outcome

Repeated use of autobim in my situation will cause the bed to continually be raised.

Environment (leave empty if unknown or not relevant)

• OctoPrint version: 1.6.1
• Python version: 3.7.3
• Marlin version: Jyers 1.3.5b
• Probe (e.g. BL-Touch, EZABL, ...): BL Touch
• Printer (manufacturer/moodel, and please state any relevant modifications, like e.g. aftermarket mainboard): Ender 3 v2
• Browser (especially useful on UI issues): Chrome

For UI issues a screenshot always helps.

Feature

Please note by far the quickest way to get a new feature is to file a Pull Request.

Just describe what you would like AutoBim as detailed as you can.

Question

Make sure your question is not covered by the Troubleshooting section.

Else: just fire away. But keep in mind: the more detail, the easier it is to answer 😃.

Probe Deploy (M401) and Stow (M402)

Description

AutoBim does not deploy ABL before probing

Steps to reproduce

When using probe such as the Allen Wrench type probe simply starting AutoBim will probe the mesh normally, deploying and stowing afterward. It will then proceed to attempt to probe the first corner without deploying the probe and fail.

Expected outcome

For it to deploy the probe, execute the process and stow when finished.

Actual outcome

As above in "Steps to reproduce"

Environment (leave empty if unknown or not relevant)

• OctoPrint version: 1.7.3
• Python version:
• Marlin version: bugfix-2.0.x
• Probe (e.g. BL-Touch, EZABL, ...): Euclid Probe
• Printer (manufacturer/moodel, and please state any relevant modifications, like e.g. aftermarket mainboard): Ender 3 Pro
• Browser (especially useful on UI issues): Brave Browser

For UI issues a screenshot always helps.

Feature

Add option to insert M401 before procedure and M402 after it's done.

Please note by far the quickest way to get a new feature is to file a Pull Request.

Just describe what you would like AutoBim as detailed as you can.

Question

Make sure your question is not covered by the Troubleshooting section.

Else: just fire away. But keep in mind: the more detail, the easier it is to answer 😃.