Welcome! Log In Create A New Profile

Advanced

Auto_Bed_Leveling_Bilinear Issues

Posted by grimspyder 
Auto_Bed_Leveling_Bilinear Issues
October 16, 2024 02:46PM
Hello, hoping i could get some help or pointed in the right direction.
I am having uses trying to get a mesh with AUTO_BED_LEVELING_BILINEAR.
I recently changed out my BL-Touch (it was working great before) for the Bed Distance Sensor (https://www.pandapi3d.com/product-page/bed-distance-sensor). It gave me some issues to get working. So much so that I had to change firmware to Marlin-bugfix-2.1.x_skr1_4_20240418. I was eventually able able to get it working (some what) I still am having issues where the Nozzle temp is reading 0/0 (zero) and when I do an M119 the " z_min:" is not showing up. But it still homes just fine and reads the distances correctly. I will fix those issues after this one.
The issue I am having with the ABL Bilinear is that it only probes the first 6 positions then stops. It doesn't matter how many points I put in 9, 36 still stops after 6 probes.
I have tried a bunch of different things like changing how many probe points, changing the distance from the bed for it gets to far away and stops, making the area for the printer probe smaller, and a few others I cant remember.
But It keeps doing the same thing.
I have attached my config's, hoping someone can look thru it and see if I have something wrong.

Any help on this would be great, I have been at this for days trying to get it to work.
Thank you
Attachments:
open | download - Configuration.h (134.3 KB)
open | download - Configuration_adv.h (187.1 KB)
Re: Auto_Bed_Leveling_Bilinear Issues
October 16, 2024 07:21PM
Your config says you don't have a Z-endstop, your using a probe. So you don't get a z_min in the endstop listing.



"Nozzle temp is reading 0/0 (zero)" on a BOARD_BTT_SKR_V1_4_TURBO this is normally caused by having a dead ADC pin..
The ADC pin on these boards are sensitive and can only take 0 - 3..3 volts, sadly when the hotend develops a fault it often sends 12v to this pin.
Re: Auto_Bed_Leveling_Bilinear Issues
October 16, 2024 07:39PM
Thanks for the reply, it helps a lot.
Would that mean that this board is dead? Or could I change from E0 to E1?
Re: Auto_Bed_Leveling_Bilinear Issues
October 17, 2024 06:52AM
I installed another Firmware "version", of Marlin-bugfix-2.1.x and made all the changes I think i need. And now all my Endstops are now working.
The Touch mode doesn't seem to be working correctly, but the Marlin mode seems to be working.

I have strange issue were the Y_axes isn't stopping when it hits the Endstop, it grinds way. even though I can see it trigger.
So I cant home, much less test G29.
If i flash back the previous Firmware, the Endstop's work again, but I don't have the Z endstop appearing. I have gone thru the config and cant notice any differences with the end stop settings. Is there another place where I should be checking?
Any idea of what could causing this?

Edited 1 time(s). Last edit at 10/17/2024 07:13AM by grimspyder.
Attachments:
open | download - Configuration_adv.h (183.6 KB)
open | download - Configuration.h (134.3 KB)
open | download - Endstop_triggered.jpg (21.5 KB)
Re: Auto_Bed_Leveling_Bilinear Issues
October 17, 2024 07:15AM
with TMC2209's on BOARD_BTT_SKR_V1_4_TURBO you must remove the diag pin from the stepper driver when using endstop switches

you have #define DIAG_PINS_REMOVED but did you actually do it?




Edited 1 time(s). Last edit at 10/17/2024 07:34AM by Dust.
Re: Auto_Bed_Leveling_Bilinear Issues
October 17, 2024 07:37AM
Yes I did remove the pin.

The printer was working fine before I tried to switch to BDsensor from the BL-touch.
Re: Auto_Bed_Leveling_Bilinear Issues
October 17, 2024 08:55AM
Configs are older... not current bugfix

missing
#define I2C_BD_SDA_PIN
#define I2C_BD_SCL_PIN
#define I2C_BD_DELAY

no custom boot screen or icon files so I disabled those

I added under #define MOTHERBOARD BOARD_BTT_SKR_V1_4_TURBO
#define I2C_BD_SDA_PIN Z_MIN_PROBE_PIN
#define I2C_BD_SCL_PIN SERVO0_PIN
#define I2C_BD_DELAY 20 // default value is 20, should be in the range [10,30]
#define DIAG_PINS_REMOVED

so its all in the one place


Cleaned up and updated Configs for current bugfix 2.1.x

Configuration.h
Configuration_adv.h

Edited 2 time(s). Last edit at 10/17/2024 09:03AM by Dust.
Re: Auto_Bed_Leveling_Bilinear Issues
October 17, 2024 06:09PM
I appreciate the help.
I had the I2C configs in the pins/lpc1768/pins_BTT_SKR_V1_4.h so I thought it was good there.
I got the latest bugfix 2.1.x and added the Configuration's you fixed (thanks again)

But now I am getting a few errors:
identifier "MINIMUM_PLANNER_SPEED" is undefined, 'MINIMUM_PLANNER_SPEED' was not declared in this scope, 'new_entry_speed_sqr' was not declared in this scope; did you mean 'next_entry_speed_sqr'?, and a few others.
I have spent about 5 hours trying to find the issue of the error, but I am not sure where to look.

Is there any documentation that explains how the firmware is put together?
I am not understanding why these changes affect the builds differently. It seems that the same settings on different builds cause different issues.
I am really confused, right know.
Re: Auto_Bed_Leveling_Bilinear Issues
October 17, 2024 09:27PM
there are no references to MINIMUM_PLANNER_SPEED in current marlin bugfix. [github.com]

MINIMUM_PLANNER_SPEED was removed on Oct 28, 2023.... update your code.
Re: Auto_Bed_Leveling_Bilinear Issues
October 17, 2024 11:38PM
Thanks for the firmware. Those configs built correctly and I was able to flash it, and its homing and moving correctly again.
It still is only probing the first 6 points when I try to do the AUTO_BED_LEVELING_BILINEAR.
I'm not understanding why, I am not able to find any info what would be causing it.

Question? Is this not the place to get the latest firmware: [marlinfw.org]
This is where I downloaded what I thought was the latest version.

Thanks again for the help.
Re: Auto_Bed_Leveling_Bilinear Issues
October 18, 2024 01:32AM
marlinfw.org and the link I provided point to the same place.
Sorry, only registered users may post in this forum.

Click here to login