BLTouch Config.
-
Ok...Tks
-
@Hélder-Rocha It's the 5th symbol from the right at the top of the reply dialog.
-
Hi,
You are using firmware that is very old.
The most recent v2 firmware is v2.05.1 but my memory may be faulty on that.
The most recent v3 firmware is v3.2.
I suggest you update to at least the most recent v2 firmware.
I cannot be sure about your files as I have no idea what those files should look like for v1.21
Frederick
-
Well, Frederick, there´s a big problem right there. Let me see if a find out how is that done, because i am a complete noob on this stuff.
-
@Hélder-Rocha said in BLTouch Config.:
Well, Frederick, there´s a big problem right there. Let me see if a find out how is that done, because i am a complete noob on this stuff.
I cannot help you with firmware that old.
There are special steps that sometimes need to be taken when make a big jump in versions.
For example, when I wanted to go from 2.05.1 to 3.1.1 (the most recent v3 at the time) I had to first go to 3.0.0 before I could go to 3.1.1.
I'm sure somewhere here can advise you or point you to the need references.
Perhaps if you started a new topic regarding your firmware upgrade situation?
Frederick
-
Can you send M122 and post the response here so we can see what firmware version is actually flashed?
-
-
but i ll send the M122 just to check it out
-
Ok, so the config for the BLTouch looks fine for 2.05
What problems exactly are you having?
Does the Bltouch work to home the Z axis?
After homing, does sending the nozzle to Z0 lead to the nozzle just touching the bed surface?If you've gone through the test and calibrate page to set your XYZ offsets, have you now tried running G29 to get a map of your bed surface?
-
@Phaedrux HI... the problem i am having is that, after i calibrate the offset on G31, defining the 0.0 position etc etc, when i do the first probe, the nozzle gets agaist the bed! If i increase or decrease the z value on the G31, it goes allways agaist the bed! Also, i dont haveproperly constant values when i try to define the z offset! It changes constantly. I read that a anti-backlash nut could help. I dont know!
-
@Phaedrux Oh, and yes, Bltouch work to home the Z axis.
After homing z, it stays on 5mm plus the z offset value above the bed.
I made all the steps that are on that link you sent and yes, i made also the map. Dont know hou to use it, but yes, i made it! -
@Hélder-Rocha said in BLTouch Config.:
when i do the first probe, the nozzle gets agaist the bed
do you mean it does not stop when its triggerd.
or the nozzle hits the bed before its triggered? -
@Veti i beleave it stops when triggered, and goes up for 5mm. At this moment the Z offset is marked with 1,90. So, after it makes the probe, Z ascend 5mm, in the panel i can check z height is 6,90 (5mm+1,90)... all good, but if i down it 5mm, it stops on Z 1,90, but against the bed. After slice a test cube, just to see if it runs ok, the nozzle does not get the 0,02 mm height i nead for the fisrt layer, because its touching the bed!! But Veti, i starded to download the new versions of firmware, i all strt over. Lets forget this for now. Different issues just appear. Ill open a different topic. Tks a lot for your help.
-
@Hélder-Rocha said in BLTouch Config.:
check z height is 6,90 (5mm+1,90)... all good, but if i down it 5mm, it stops on Z 1,90, but against the bed.
this means that your trigger height is incorrect
-
I made all the steps that are on that link you sent and yes, i made also the map. Dont know hou to use it, but yes, i made it!
-
-
@Veti so, you suggest i put my offset in 0.0? But look Veti, i just started to update my firmware to 3.0 and found my first problems. If you care to help me on other topic i created in "firmaware instalation categories", ill be thankfull. many tanks
-
@Hélder-Rocha said in BLTouch Config.:
i just started to update my firmware to 3.0 a
please update to 3.2 there is no point in staying on 3.0
-
@Veti all the surch i made, no one advices to go from 2.05 to 3,2 directly! The sugestion is to go first to 3.0, and then update to 3.1 or 3.2! I dont know nothing about this, just following the masters
-
you have to go to 3.2 because you cant flash directly. that is why you need to go to 3.0 first.
there is no reason to stay on 3.0
