Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] [Bedleveling] Z dont rise on deploy with fixed probe and homed to max #27626

Open
1 task done
KillerInk opened this issue Jan 6, 2025 · 1 comment
Open
1 task done

Comments

@KillerInk
Copy link

Did you test the latest bugfix-2.1.x code?

Yes, and the problem still exists.

Bug Description

Hi
My setup on Z have max endstop and on min side an inductive sensor as FIX_MOUNTED_PROBE.
It homes to max side because its on bottom. No good idea to home to min after a print is done^^
After a G28 and everything is homed, i do a G29 to start the bedleveling.

`

G29 X0.00 Y0.00 Z122.00
Machine Type: Cartesian
Probe: FIX_MOUNTED_PROBE
Probe Offset X0.00 Y-80.00 Z0.00 (Middle-Front & Same Z as Nozzle)
Auto Bed Leveling: BILINEAR (disabled)
remember_feedrate_scaling_off: fr=66.67 100%
set_bed_leveling_enabled X0.00 Y0.00 Z122.00
<<< set_bed_leveling_enabled X0.00 Y0.00 Z122.00
current_position= X0.00 Y0.00 Z122.00 : Probe::set_deployed
deploy=1 no_return=0
Raise Z to 10.00
do_z_clearance(10.00 [122.00 to 10.00], 0)
`

at that point the bed should start to rise, but it do not^^

after looking through the code i ended up here

if (z_raise_wanted) {
const float zdest = DIFF_TERN(HAS_HOTEND_OFFSET, Z_CLEARANCE_DEPLOY_PROBE, hotend_offset[active_extruder].z);
if (DEBUGGING(LEVELING)) DEBUG_ECHOLNPGM("Raise Z to ", zdest);
do_z_clearance(zdest);
}

wich brought me there

if ((!lower_allowed && zdest < current_position.z) || zdest == current_position.z) return;

so we start at 122 and the bed should go to 10. but lower_allowed is by default false it returns silent and z never rise.

changing the code inside the probe line 529 to
do_z_clearance(zdest,true,true);
rises Z finaly.

its equal if i use Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN or Z_MIN_PROBE_PIN, acts both the same.
also that affects every auto bedleveling

due the fact that i have no idea, if that is the correct way, nor how that affects other probes, i opend that issue and not a pull request.

if you wonder why the slow probs triggered, it hit the max endstops^^

happy new year and thx for marlin. it never went boring with it^^

marlin_probe log.txt
Configurations.zip

Bug Timeline

I dont know

Expected behavior

No response

Actual behavior

No response

Steps to Reproduce

No response

Version of Marlin Firmware

latest bugfix-2.1.x

Printer model

be3D DeeGreen(only orginal are the axis and the case)

Electronics

mks tinybee tmc2209-standalone

LCD/Controller

no lcd

Other add-ons

No response

Bed Leveling

ABL Bilinear mesh

Your Slicer

None

Host Software

Pronterface

Don't forget to include

  • A ZIP file containing your Configuration.h and Configuration_adv.h.

Additional information & file uploads

No response

@Danez-DK
Copy link

Danez-DK commented Jan 7, 2025

I can confirm this is a problem with anycubic kossel plus (Marlin-2.1.3-b1) using BD Sensor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants