search

j-be / AutoBim

A bed tramming utility for OctoPrint using ABL
Other
29 stars 3 forks source link

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

Closed SoaringEagle93 closed 11 months ago

SoaringEagle93 commented 11 months ago

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)

For UI issues a screenshot always helps.

j-be commented 11 months ago

Hi,

Unfortunately, it seems the settings are off. This depends on settings in the firmware, that can afaik. not be queried, like X_MIN_POS. But if you know those you should be able to easily compute them. Also, be sure that your probe-to-nozzle offset is correct. See https://github.com/j-be/AutoBim#works-fine-on-the-first-or-first-and-second-corner-display-says-ok-moving-to-next-but-nothing-happens for details.

j-be commented 11 months ago

Oh, and could you please provide the terminal output while probing?

I.e. start a probe (e.g. using the "Test" button in "Settings") and afterwards go to OctoPrint's "Terminal" tab and copy the last couple of lines and post them here.

Please make sure to at least include the output starting from the G30 command.

SoaringEagle93 commented 11 months ago

My X_MIN_POS and Y_MIN_POS are 0,0 in the firmware and when homing XY the nozzle is over the front left corner as it should be.

When I run the test after Homing this is what I get in the terminal:

[...] Send: G30 X30 Y30 [...] Recv: Bed X:30.0 Y:30.0 Z:0.09 [...] Recv: ok

j-be commented 11 months ago

Wow, that's interesting: it seems like your firmware - different from anything I have seen yet - does not put spaces between the coordinates and the values in the G30 respomse. I.e., I have always seen:

Bed X: 30.0 Y: 30.0 Z: 0.09

but yours is

Bed X:30.0 Y:30.0 Z:0.09

Could you please try to put the following in Settings -> Custom G30 response pattern:

^Bed X:-?\d+\.\d+ Y:-?\d+\.\d+ Z:(-?\d+\.\d+)$

and see if it works then? If so, it should be an easy fix.

Also, what firmware are you running? Like exact version in case of self-compiled or place where you downloaded it from?

SoaringEagle93 commented 11 months ago

I added the custom G30 response pattern and got the same result. It probes the spot but then says it is unreachable. My firmware is self compiled and is version bugfix-2.1.x (Jul 30 2023). I used the Creality/Ender-3 Pro/BigTreeTech SKR Mini E3 3.0 example to build it.

j-be commented 11 months ago

Weird... I think I have some time tomorrow to dig deeper. I may need to increase logging verbosity to see what is going on here.

I'll keep you up to date if something comes up. To be honest: I'm at the moment not quite sure what is going on here.

j-be commented 11 months ago

I think I figured out what is going on: the following changed the response of the G30 command. https://github.com/MarlinFirmware/Marlin/commit/574dd34c49fde76e1e736b8a7e1ea579d724ff22 It (seems) to currently be only included in bugfix-2.1.x, which is why I have never seen it before: I only use stable releases, no bugfix.

I built a current bugfix and can reproduce it. I wasn't able to fix it yet, though. Will keep you up to date.

j-be commented 11 months ago

Alright, I think I fixed it. I just releases version 0.4.1 - OctoPrint should offer the update shortly (I think it caches release data for 24 hours).

Please countercheck if it is now working at your side, too. Please clear "Custom G30 response pattern" when doing so - should now work out of the box.

SoaringEagle93 commented 11 months ago

That seem to do it. Now it tells me each point is available and when I click the "Start AutoBim" everything acts as it should. Thanks for looking into and fixing this so quickly!

j-be commented 11 months ago

My pleasure. Thanks for reaching out. This would have caused issues to a lot of people with the next Marlin release.