I have the BLTouch smart, which is less critical to the z-offset installation (according to the diagram here https://www.antclabs.com/bltouch-2 , between 2.3 and 4.3, so I'm nicely within range with my 3.84).
(see below)

I will start rewiring everything, maybe there is some bad cable somewhere as now I cannot seem to get the correct z-trigger height. I know from my successful prints that it should be 3.84, and I have not changed anything to the hardware, but it keeps the head higher when it thinks Z=0. Previously, when I changed from 3.84 to a higher value, it cause a headcrash, which I want to avoid.
So I'll rewire everything and make order in the cabling: best is to first rule out some bad wire or something that may cause issues. Don't get me wrong, I will change the Z-motors as a next step, but as you see, there is something very wrong with the mesh map and the z-trigger height. So, starting to rewire everything, but I will only be able to get back to this in 2 weeks. Thanks for the help, for sure I will keep you posted.

EDIT: I may have a BLTouch Smart v2.0, which has the range at 3mm+/- 0.3, but I'm out of range (my 3.84 is when it is deployed, but when it is not I for sure have less than 2.7mm). That my indeed explain the inconsistent readouts! Ok, so going to rewire and reattach the bltouch: If I put it at 3mm, I should be fine regardless of whether I have a v2 or a v3 (but I'm 99% sure I have a v2). THANKS!!!! Not sure if this is the cause, but it seems possible.

I'm not sure that that is so straightforward... Also, it is nice that the firmware just does what the command tells it to do, without performing additional steps behind the user's back. Sure you have to know more what you do, but at least it allows you to do what you want.

@Phaedrux said in z-offset increasing 3mm on every subsequent calibration:

@VJ Done.

Thanks!

Thanks!
Perhaps a note on https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe should be added that mesh calibration should be off, or that at least you should test at a point where the calibration has 0 effect...?

Ok, finally getting back to this...

I've got it ... I think... If you do a mesh compensation, and afterwards determine the Z-offset with the mesh compensation in effect, it will affect the determination of the Z-offset... As I was doing the homing in the front left corner, but the Z-offset calibration in the center, it added the mesh offset calibration which I did before the print (but which was not used in the print) when the z-offset is calculated again afterwards. As I was using the mesh calculation to check how level everything is, it enabled it, giving me an increase equal to the amount it is compensating with the mesh (and that was a magnitude off due to other wrong settings)... Does this make sense?

I currently started repeating Z-offset calibration without mesh compensation in between, and it seems correct...

Thanks!
A bit worried about updating, so I'll hold off for now (have some things to print) and do it when being without a printer is less of an issue.

@DIY-O-Sphere

I found that that was the case for the Maestro... Thanks for confirming.

@droftarts said in config tool and BLTouch for Duet2 Ethernet:

@VJ see https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Pin_names_for_Duet_2_WiFi_Ethernet

Duex pwm pin name is the same as expansion pin, but you can rename it later.

exp.heater3, exp.8, !duex.e2heat, !duex.pwm1
exp.heater4, exp.13, !duex.e3heat, !duex.pwm2
exp.heater5, exp.18, !duex.e4heat, !duex.pwm3
exp.heater6, exp.23, !duex.e5heat, !duex.pwm4
exp.heater7, exp.31, !duex.e6heat, !duex.pwm5

Ian

Thanks... I missed that one... The instructions gave me a bit the impression that they were different, and I did not come across the page you linked.
https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Software_setup_RepRapFirmware_Num_3

So basically, if I use the pin exp.heater3, I just select duex.pwm1 ...? Do I have to change anything else afterwards in the config file?

The issue is on the page "IO Mapping", where I cannot assign a PWM Control Channel that makes sense for my configuration (available options all relate to Duex). For Z-probe input pin I can select zprobe.in, for Z-probe modulation pin I can select zprobe.mod, but for the control channel, the options are unassigned or duex.pwm1, ... duex.pwm5.

Without an assigned PWM Control Channel, the BLTouch option is greyed out in the endstop page, with the note "Note: You must specify an input and a PWM control pin on the I/O Mapping page if you want to configure a BLTouch probe. "

Hello,

I planning to upgrade my Duet 2 to firmware 3.1 and started first by checking the config tool to be sure I can create a working config after upgrading.

Starting from a new custom configuration, the config tool does not give me the option to configure the BLTouch...
For "PWM Control Channel", the only options I have in PWM Control Channel are "not assigned" and then "duex.pwm1" to "duex.pwm5". The combination of the z-probe options above this setting makes no difference... If I choose unassigned, BLTouch is not selectable in the endstop page.

I have no expansion boards installed on my Duet2 Ethernet (not told the config tool that I have).

How do I configure the BLTouch?

Thanks!

Jörg

post removed - starting a new thread