@BrainZtorm Thank you, I can confirm without the Resistor in place it works correctly.
Would be nice if the Manual could be extended to tell people they don't need to put in a resistor for the BIQU Microprobe 2.0 when using a Duet2Wifi lower than 1.04
It only states this for BLTouch newer than version 3
@jay_s_uk No, the Black and white pin is the originally shipped 2 pin header, no empty in between.
@jay_s_uk it is the one that was shipped with the probe, I didn't switch the connector on the black and white wire.
I only had to depin the 3 wire header and get the red + brown one in an extra 2 pin header to get the yellow in Pin 8 (The yellow is in the 3pin header shipped with the Probe with now 2 empty spots)
May just be the photo angle that makes it look larger
@jay_s_uk sure
; deployprobe0.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.5.4 on Wed Jul 17 2024 18:54:04 GMT+0200 (Mitteleuropäische Sommerzeit)
;M280 P0 S10 ; deploy BLTouch
M42 P0 S1 ; deploy BIQU Microprobe
G4 P500
; retractprobe0.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.5.4 on Wed Jul 17 2024 18:54:05 GMT+0200 (Mitteleuropäische Sommerzeit)
;M280 P0 S90 ; retract BLTouch
M42 P0 S0 ; retract BIQU Microprobe
G4 P500
Hello,
I have switched out my old capacitive probe for the BIQU Microprobe 2.0 and with this updated to the newest RRF version.
I am pretty sure I have done everything like described in the Manual for the BIQU Microprobe in terms of config.
In My config.g I have
M558 P9 C"^!zprobe.in" H5 F120 T6000 ; configure Touch probe via slot #0
G31 P25 X-63 Y15 Z0.35 ; set Z probe trigger value, offset and trigger height
M950 P0 C"exp.heater3" ; create servo #0 for BIQU Microprobe 2.0
The probe does selftest on startup and I can deploy it with M401 and retract it with M402.
So I guess my deployprobe and retractprobe files are correct.
The probe shows 1000 all the time though, so it is permanently in the triggered state.
When I remove the ! from the M558 line it shows 0 but does not trigger when I deploy it and touch it with my finger.
Also when I try to G30 and then touch it when the bed moves towards it, it does not trigger aswell.
Since I have V2.0 and the manual says that there should be a ! in place I already guessed that might not be the solution.
When I leave the ! in place like described in the manual, then I can of course not start a G30, because it is already triggered.
Since I have the 1.03 revision of the Duet2Wifi, I soldered a 240 Ohm resistor from GND to Probe In, because I didn't want to risk my board and the manual doesn't explicitly state if the BIQU probe does automatically default to 3.3v without any resistor in place.
My next try would be to remove the resistor but I really don't want to fry my pin so can anyone tell me if it is correct to use this probe without any resistor in place?
Greetings and thanks in advance!
Hello friends,
I just set up my CoreXY Machine with a DuetWIFI and I begin printing some test pieces now...I have stringing issues and I saw that my retractions are accelerating pretty slow, I have set the maximum E acceleration to 6000 already but it does not speed up with it. Same speed as with 3000. The Retract speed in Simplify3D is 100mm/s and 5mm distance. (E3D Volcano Hotend)
On my other printer with marlin I can specify retraction acceleration as an own parameter in the firmware and it speeds up with it. so with 3000 acceleration and also 100mm/s at 5mm distance it retracts way faster than my duet machine now.
Is there any other parameter I have to change in order to get the retracts to accelerate faster?
Thanks in advance!
Greetings