Klipper: Extruder nozzle crashing into bed when doing bed mesh calibrate

Created on 11 Sep 2019  路  5Comments  路  Source: KevinOConnor/klipper

Your firmware is awesome! Way better than marlin in my opinion.
I am having an issue with bed leveling. I updated the firmware today for the first time in a couple of months. Before updating I never had a problem with bed leveling, after the nozzle crashes into the bed repeatably. Initially I had probe_count set to 8,8 with that setting it would crash into the bed on the 12th probe every time with the same error message. Then I went to 7,7 and it would crash into the bed on the second probe every time I tried to level the bed. Then went back to the default setting of 3,3 and it crashed on 5th probe repeatedly. The BLtouch is V3 with an in-line resistor. I can home just fine, do z-tilt and probe_accuracy commands without an issue. Only bed mesh seems to be the issue. I went through the config file and changed what I could see needed to be changed. I am guessing I must have missed something and can't find it. I also attached the octoprint terminal output as well as the klippy.log file. I have been messing with this for the last 8 hrs and can't figure out what I am doing wrong. Please help!!!

Main mcu arduino mega with ramps 1.6
aux mcu arduino mega with ramps 1.4
raspberry pi model 3b

Kevin
klippy.log

Octoprint Terminal.txt

Most helpful comment

If you want to use the command line, you can rewind the HEAD to a previous commit using its hash. For example, the last commit on August 10th is lcd_st7920: Add brief delay around gpio toggle calls on fast MCUs, and its hash is effe6f6. You can navigate the the klipper directory and enter the following:

git checkout effe6f6

You can then restart the Klipper service. It is likely that you will need to rebuild and reflash the MCU first.

FWIW, nothing in the bed_mesh or bltouch modules has changed recently. It sounds to me like your BLTouch is failing, but you can verify with an older version of Klipper.

All 5 comments

Is there anyway to revert back to a older version of klipper, from about a month ago? Now the BLtouch doesn't work at all. I currently have an expensive paper weight. Attached is the latest klippy log file.

Thanks in advance,
Kevin
klippy.log

To go back to a particular date you can do the following....

  1. Browse to the klipper git repository https://github.com/KevinOConnor/klipper
  2. Click on the item with the small clock label that says "xxxx commits " where xxxx is a number so something like "2450 Commits". This should give you a list of all of the commits in date order.
  3. Browse back in time to the date you want to download from.
  4. Click on the "<>" item over to the right of the commit you want to download from ("browse the repository at this point in the history").
  5. You should now have a view of the repository for the selected point.
  6. Click on the "clone or download" item and select "download zip"

This should give you a download of the state of the repository at the selected date.

There are other ways to do this (using the git command line) but this is probably the simplest way and gives you a complete snapshot of all of the files without touching your "current download or git fork"

@gloomyandy Thank you so very much for taking the time to help! I truly appreciate it. At least now I can test and see if it is the bltouch is bad.

If you want to use the command line, you can rewind the HEAD to a previous commit using its hash. For example, the last commit on August 10th is lcd_st7920: Add brief delay around gpio toggle calls on fast MCUs, and its hash is effe6f6. You can navigate the the klipper directory and enter the following:

git checkout effe6f6

You can then restart the Klipper service. It is likely that you will need to rebuild and reflash the MCU first.

FWIW, nothing in the bed_mesh or bltouch modules has changed recently. It sounds to me like your BLTouch is failing, but you can verify with an older version of Klipper.

Thank you @gloomyandy and @Arksine. Was able to go back to the commit I was originally on and indeed @Arksine you are correct BLtouch is dead. Thank you again! I will now close this.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

superg3 picture superg3  路  6Comments

speendo picture speendo  路  3Comments

Michael-Bell picture Michael-Bell  路  5Comments

CHILLYSMOKES picture CHILLYSMOKES  路  5Comments

jannoke picture jannoke  路  3Comments