BLTouch M401 M402 test does not work
-
@Veti said in BLTouch M401 M402 test does not work:
please post the output of m115
M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet WiFi 1.02 or later + DueX5 FIRMWARE_DATE: 2020-05-19b2 -
I would like to also add the following:
; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Mon Oct 05 2020 11:50:09 GMT+0300 (Eastern European Summer Time)
M280 P0 S90 ; retract BLTouch; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Mon Oct 05 2020 11:50:09 GMT+0300 (Eastern European Summer Time)
M280 P0 S10 ; deploy BLTouch -
can you confirm that you have put a jumper on "5V AUX JUMPER SELECT PINS" between the 5V AUX and 5V INT pins on the duex.
-
![0_1602247267920_Duex 5 pin config.jpg](Uploading 100%)
-
-
if heater 3 is PWM1 then pwm 5 should be heater 7 not 5
-
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds.
H5 becomes H7?
-
Nevermind the last question. I meant to ask that "duex.e5heat" becomes "duex.e7heat", in the M950 bellow?
M950 S0 C"duex.e5heat" ; create servo pin 0 for BLTouch
-
@campeancalin said in BLTouch M401 M402 test does not work:
M950 S0 C"duex.e5heat" ; create servo pin 0 for BLTouch
the configurator even suggest to do this
M950 S0 C"duex.pwm5" ; create servo pin 0 for BLTouch -
There 2 options in the configurator : "duex.pwm5" and "duex.pwm5"(active low). Wht's the diferrence between them?
-
@campeancalin
the output value is inverted -
@campeancalin your P0 should be P7 in your deploy and retractprobe.g
-
@wdenker said in BLTouch M401 M402 test does not work:
your P0 should be P7 in your deploy and retractprobe.g
P0 is correct for RRF3
P7 was RRF2 -
@Veti you are right sorry I pulled from my 2.05 version. and 3.1 I only have working on duet 3 so far.
-
Thank you again for the info @Veti. Everything works with "duex.pwm5" set up.