2 Z probes Bltouch independent Z and X axis

jsinicro

Re: Connecting multiple Z probes for multiple independent Z axis

This is related to an older topic, and I am actually doing the same thing taking the Zidex concept and making the bed 700mm X 800mm X 800mm I got both probes working and triggering, so now the question is how to define the G31 command for both as the offsets are different so this is what I was thinking as the documentation on the G31 command says that two separate G31 commands can be defined each after the respective M558 cmd this is what I am thinking:

; Z-Probe
M558 P9 C"^1.io4.in" H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
M950 S0 C"1.io4.out"
G31 X42 Y0 Z2.098 P25

M558 P9 C"^3.io4.in" H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
M950 S1 C"3.io4.out"
G31 X-44 Y0 Z2.098 P25

However the documentation also mentions
X,Y,U,V,W,A,B,C...nnn Probe Offsets for all axes except Z1 (RRF >=3.3beta2)

I use V as my other Z axis so how would the G31 command be set so that it will be tied to the V axis
G31 V.X-44 V.Y0 V.Z2.098 P25 ;I don't think this is right

Phaedrux

You differentiate between the two probes with the K parameter.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M558_in_RepRapFirmware_Num_3

jsinicro

@phaedrux OK, thx I will try it, also in the deployprobe and retract probe I put the commands for both probes, do I need to have 2 separate files for each probe or just put as an example to retract poth probes in one file as in:
When I issue these commands at the terminal they individually retract the correct probe.
M280 P0 S90 ; retract BLTouch
M280 P1 S90 ; retract BLTouch x axis 1

thx.

Phaedrux

Multiple Z probes are supported. M558, G29 and G30 now accept an optional K parameter to specify which Z probe to use. Each Z probe can now have its own deploy and retract files. Z probe number # (where # counts up from zero) looks first for deployprobe#.g and if that is not found it falls back to deployprobe.g. Similarly it uses retractprobe#.g in preference to retractprobe.g. The M401 (deploy probe) and M402 (retract probe) commands now accept an optional P parameter which is the Z probe number to deploy or retract, default 0.

jsinicro

@phaedrux Yes I suspected at I got the probes working and with the K parameter I actually see 2 in the DWC however when I do the probing on the 2nd Z axis they bot deploy, so this makes sense I will put 2 separate files.
thx

jsinicro

@jsinicro OK, just tested this, now the probes are deployed independently however when I probe the V axis which is the 2nd X axis eventhugh the probe triggers and the axis stops moving I get a response G28 V Error Homing failed. Can this be debugged or any suggestions. This is the probingV.g file: -I changed the file that was generated, maybe I need to put the original back as now I have the probes working?

homev.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun Apr 18 2021 23:08:10 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 H1 X50 Y50 V5 F6000 ; lift Z relative to current position
G30 K0

; Uncomment the following lines to lift Z after probing
G91 ; relative positioning
G1 V10 F100 ; lift Z relative to current position
G90 ; absolute positioning