BLTouch trigger issue on RRF 2
-
@Parabolic did you tried to inverse the pin input in config.g
Mine was always showing 1000 only and no zero when triggered . After I added the" ! " In pin output it showed zero and 1000 when triggered. Not exactly like yours but....just an idea to try out
This is for RRF3...not sure what version are you running -
Im on RRF 2.05.
No I didnt use the "!".
Can I see your config.g? -
Please post your config.g
You may not notice the probe status changing in DWC because the BLTouch triggers and than immediately resets, so it doesn't always get captured by the interface. The best way to test is to send G30 to try actually probing and then triggering the pin manually to see if it stops motion. If it doesn't kill power.
Also make sure your white wire from the BLtouch is good. That's the trigger signal wire.
-
@Phaedrux
Glad to hear on the probe status speed. I was going by one of the tutorials and it said it should show 1000 when triggered. I did try the G30 and it deploys the probe and moves z. Unfortunately it crashes (or I Estop it). The white signal wire is good all the way to the board.
heres my config:
; Configuration file for Duet WiFi (firmware version 2.03)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Sat Jan 25 2020 19:53:13 GMT-0500 (Eastern Standard Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Parabolic X" ; set printer nameM667 S1 ; select CoreXY mode
; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S1 ; enable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z800.00 E420.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X420000.00 Y420000.00 Z1500.00 E1200.00 ; set maximum speeds (mm/min)
M201 X1500.00 Y1500.00 Z250.00 E250.00 ; set accelerations (mm/s^2)
M906 X1500 Y1500 Z1800 E1500 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X395 Y410 Z400 S0 ; set axis maxima; Endstops
M574 X1 Y1 S0 ; set active low and disabled endstops
M574 Z1 S2 ; set endstops controlled by probe; Z-Probe
M307 H3 A-1 C-1 D-1 ; set Z probe type to switch and the dive height + speeds
M558 P9 H5 F1000 T20000
G31 X0 Y50 Z1.5 P25 ; set Z probe trigger value, offset and trigger height
M557 X5:385 Y0:360 S90 ; define mesh grid; Heaters
M140 H0 ; enable heated bed
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4725 C7.06e-8 R4700 ; set thermistor + ADC parameters for heater 1
M143 H1 S280 ; set temperature limit for heater 1 to 280CM307 H1 A492.3 C163.8 D3.8 V24.3 B0 ;PID settings
; Fans
M106 P0 S0 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 T50 H1 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on; Tools
M563 P0 S"HotEnd" D0 H1 F0 ; define tool 0
;G10 P0 X0 Y-80 Z2 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
;G31 X0 Y0 Z0 P25
; Custom settings are not defined -
Can you verify that you're still on RRF2 by sending M115 to get the firmware version?
Your config looks ok, except for the dive speed in M558
M558 P9 H5 F1000
Use F60 for the BLTouch.
Are you super sure the white wire is good? Not triggering would indicate the white wire isn't connected.
You could experiment with this since its a BLTouch 3.1
-
@Phaedrux
Yup, Im super sure.
When I unplug the black and white wires from the probe connector on the board the interface shows the Z probe at 1000 in red. It goes back to 0 when I plug it back in.The M280 isnt working - returns a invalid servo index 0
-
@Phaedrux 1/2/2021, 7:44:51 PM M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-12-13b1 -
@Parabolic said in BLTouch trigger issue on RRF 2:
returns a invalid servo index 0
That means your deploy and retract files are formatted for rrf3 I think. Post them.
-
-
Open bed.g and delete/comment the M307 line for the heater channel you are using to drive the BLTouch servo
I just got mine working last night.
-
@Parabolic said in BLTouch trigger issue on RRF 2:
The M280 isnt working - returns a invalid servo index 0
What exactly are you sending for your M280?
Does M401 and M402 work to deploy and retract?
-
@64bit Its already been done. Thanks!
-
@Phaedrux No my 401 & 2 does not.
Im not sure what you are asking about the 280 -
if m402 and m401 does not work, there is a problem with your wiring.
the extension wire of the bltouch tend to give poor connections. connect the bltouch directly and test again.
-
Can you send M98 P"config.g" in the console and post the response?
When you say M280 isn't working and giving you that servo index 0 message what exactly did you send for your full M280 command?
-
-
Can you post a photo of how you have the BLTouch wired?
Your config.g is using heater 3 pin on the expansion port. Are you connected to the right pin there?
If you send M401 and M402 they don't work?
If you sendM280 P3 S10 I1does that work? -
@Phaedrux said in BLTouch trigger issue on RRF 2:
M280 P3 S10 I1
Yes, 401 and 2 retract and extend the pin.
Yes I'm connected to the right pin on the expansion header - just like in the setup pics. -
I am having the same issue! my config.g looks the same as above and M401 and M402 both work. I did notice that the trigger type listed in the Z-Probe section of the Machine Properties tab says Unknown (9).
-
@Parabolic said in BLTouch trigger issue on RRF 2:
Yes, 401 and 2 retract and extend the pin.
Ok, but before you said it didn't, so I'm a bit confused.
If it's just not triggering while doing a probe with G30, then again I say
@Phaedrux said in BLTouch trigger issue on RRF 2:
Are you super sure the white wire is good? Not triggering would indicate the white wire isn't connected.
You could experiment with this since its a BLTouch 3.1
https://www.antclabs.com/logic
