MarlinFirmware / Marlin

Marlin is an optimized firmware for RepRap 3D printers based on the Arduino platform. Many commercial 3D printers come with Marlin installed. Check with your vendor if you need source code for your specific machine.
https://marlinfw.org
GNU General Public License v3.0
16.28k stars 19.23k forks source link

Bltouch v3.1 probing but not leveling #19390

Closed ase95 closed 4 years ago

ase95 commented 4 years ago

Bug Description

my bltouch v3.1 is probing but my first layer not even near being level, i have pre leveled the bed manually. i've checked my axis steps but even after adjusting them,it's not working... (im using marlin 1.8 since im having issue with the 2.0 and infinite loop of the bootscreen)

My printer is a Tevo Tornado

My starting code: G28 ; home all axes G29; Auto Bed Levelling G1 Z0.2 F3000 ; get ready to prime G92 E0 ; reset extrusion distance G1 X160 E15 F600 ; prime nozzle G1 X180 F5000 ; quick wipe

Here some pictures to see what im talking about

My Configurations

config.zip

Steps to Reproduce

im just printing a bed level test to see if it's leveled or not.

Expected behavior: [What you expect to happen] expecting to have an even layer on all the printing bed

Actual behavior: [What actually happens] looks like bltouch its not even on

boelle commented 4 years ago

marlin 1.8 is no longer active worked on, Please test the bugfix-2.0.x branch to see where it stands.

ase95 commented 4 years ago

marlin 1.8 is no longer active worked on, Please test the bugfix-2.0.x branch to see where it stands.

i would use the 2.0 if i could, but for some reason my printer gets stuck on the bootscreen,other people tried my config and it works fine on them

Azrael321 commented 4 years ago

I think there is missing

M420 S1

in the start code

ase95 commented 4 years ago

I think there is missing

M420 S1

in the start code

should put it right after g29?

mustang5269 commented 4 years ago

He wouldn't need that if he has restore leveling after g28 enabled in his firmware correct?

Azrael321 commented 4 years ago

Yes, should be somewhere after G29. If you use G28 after this command, command is normaly deactivated again.

Yes, if you have restore leveling after g28 enabled you should not need this command

oliver-eifler commented 4 years ago

if you use G29 after G28 in your start g-code neither M420 nor restore leveling (it only restores leveling state not data) in firmware is needed...G29 probes the mesh and activates auto bed leveling.

There was extra code for bl-touch 3.x added in marlin 1.1.9 ... AFAIK bl-touch 3.1 wouldn't work with marlin 1.1.8 You should use at least latest marlin 1.1.9

ase95 commented 4 years ago

if you use G29 after G28 in your start g-code neither M420 nor restore leveling (it only restores leveling state not data) in firmware is needed...G29 probes the mesh and activates auto bed leveling.

There was extra code for bl-touch 3.x added in marlin 1.1.9 ... AFAIK bl-touch 3.1 wouldn't work with marlin 1.1.8 You should use at least latest marlin 1.1.9

THANKS! i'll start doing the config on the 1.1.9 asap and i'll hope by bltouch finally start working

ase95 commented 4 years ago

still having same issue 😢

Hokeric commented 4 years ago

still having same issue 😢

This might sound too obvious, but have you checked Z offset?

ase95 commented 4 years ago

still having same issue 😢

This might sound too obvious, but have you checked Z offset?

sadly i have...im out of ideas,tried so many different firmwares/versions but this issue isn't going away. Any chance the issue is the bltouch itself? like getting wrong readings (?)

Hokeric commented 4 years ago

still having same issue 😢

This might sound too obvious, but have you checked Z offset?

sadly i have...im out of ideas,tried so many different firmwares/versions but this issue isn't going away. Any chance the issue is the bltouch itself? like getting wrong readings (?)

I have not tested it myself, this could be related. I am making a wild guess here. If the bed level difference is greater than 3mm then the probe might not have gone low enough during leveling.

define Z_PROBE_LOW_POINT -3 // Farthest distance below the trigger-point to go before stopping

From your pictures, the front is ok (probed first), the middle looks less ok and the backs look worst. There seems to be a trend from front to back. Try change the -3 to -4 and see how it goes.

fiechr commented 4 years ago

if you use G29 after G28 in your start g-code neither M420 nor restore leveling (it only restores leveling state not data) in firmware is needed...G29 probes the mesh and activates auto bed leveling.

I'm sorry, but could you explain what the difference between restoring level state and (level?) data actually is? When I was using Manual Mesh Bed Leveling, I saved the Z-offsets from the G29 procedure with M500 to the EEPROM and later (before printing) restored them/it with M501 and M420 S1. Now, using BLTouch, I'm unsure if this works the same way for Auto Bed Leveling? So after running G29 and a M500, can I completely restore the state after the G29 with M501 and M420 S1? Since I don't want to run a leveling procedure every time I print something. I would prefer running a more thorough leveling procedure once after filament change etc..

ase95 commented 4 years ago

still having same issue 😢

This might sound too obvious, but have you checked Z offset?

sadly i have...im out of ideas,tried so many different firmwares/versions but this issue isn't going away. Any chance the issue is the bltouch itself? like getting wrong readings (?)

I have not tested it myself, this could be related. I am making a wild guess here. If the bed level difference is greater than 3mm then the probe might not have gone low enough during leveling.

define Z_PROBE_LOW_POINT -3 // Farthest distance below the trigger-point to go before stopping

From your pictures, the front is ok (probed first), the middle looks less ok and the backs look worst. There seems to be a trend from front to back. Try change the -3 to -4 and see how it goes.

difference from front to back should be 1mm max looking at what Z the probe activates. My #define Z_PROBE_LOW_POINT is set to -2 so i'll try change it to -3 if that doesn't work i'll go with -4

sjasonsmith commented 4 years ago

I am closing this issue, since this is for Marlin 1.1.x which is no longer developed. I recommend you seek help from the community to create a working Marlin 2.x configuration.

This Issue Queue is for Marlin bug reports and development-related issues, and we prefer not to handle user-support questions here. (As noted on this page.) For best results getting help with configuration and troubleshooting, please use the following resources:

After seeking help from the community, if the consensus points to a bug in Marlin, then you should post a bug report.

github-actions[bot] commented 3 years ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.