probe modulle doesn't retract on any axis

[jrdarrah]

I've finished my CNC conversion of a Seig X2D and everything works except probing. I've spent several days checking the wiring from Phil Barrett's grblHAL breakout board to the touch plate. I even used aa custom arduino sketch to display the value of the probe pin touched=1 and not touched=0. To save on bits I have a piece of copper wire in the chuck which is more forgiving than a bit if probing fails to stop.. As it stands now the z-probe goes down and stops, the XY probe only touches the Y then quits. Will's video on probing said I should see a double tap then the bit retracts.

I'm currently running

Product Version: Universal Gcode Platform 20210208
Java: 1.8.0_275; OpenJDK Client VM 25.275-b01
Runtime: OpenJDK Runtime Environment 1.8.0_275-b01
System: Linux version 5.10.17-v7l+ running on arm; UTF-8; en_US (ugsplatform)
User directory: /home/pi/.ugsplatform/2.0.7-SNAPSHOT/dev
Cache directory: /home/pi

My probe settings for Z-axis

These are my firmware settings and a test of the Z probe command at the end. I turned on verbose and saw nothing useful. I tried several different $10 values and the only one that seems to work is $10=2. $6 is inverted . without that I get an immediate error stating the probe pin is in the wrong state. How do I collect useful information on what is happening during and after the probe move.? I'd like to stop using the by eye method of zeroing the axes.

GrblHAL 1.1f ['$' or '$HELP' for help]

$$
$0 = 10.0 (Step pulse time, microseconds)
$1 = 2 (Step idle delay, milliseconds)
$2 = 7 (Step pulse invert, mask)
$3 = 1 (Step direction invert, mask)
$4 = 7 (Invert step enable pin, boolean)
$5 = 7 (Invert limit pins, boolean)
$6 = 1 (Invert probe pin, boolean)
$7 = 0
$10 = 2 (Status report options, mask)
$11 = 0.010 (Junction deviation, millimeters)
$12 = 0.002 (Arc tolerance, millimeters)
$13 = 0 (Report in inches, boolean)
$14 = 64
$15 = 0
$16 = 0
$17 = 0
$18 = 0
$19 = 0
$20 = 0 (Soft limits enable, boolean)
$21 = 1 (Hard limits enable, boolean)
$22 = 1 (Homing cycle enable, boolean)
$23 = 0 (Homing direction invert, mask)
$24 = 25.0 (Homing locate feed rate, mm/min)
$25 = 500.0 (Homing search seek rate, mm/min)
$26 = 25 (Homing switch debounce delay, milliseconds)
$27 = 1.000 (Homing switch pull-off distance, millimeters)
$28 = 0.100
$29 = 0.0
$30 = 1000.000 (Maximum spindle speed, RPM)
$31 = 0.000 (Minimum spindle speed, RPM)
$32 = 0 (Laser-mode enable, boolean)
$33 = 5000.0
$34 = 0.0
$35 = 0.0
$36 = 100.0
$37 = 0
$39 = 1
$40 = 0
$43 = 1
$44 = 4
$45 = 3
$46 = 0
$62 = 0
$63 = 2
$64 = 0
$65 = 0
$80 = 1.000
$81 = 0.010
$82 = 0.000
$84 = 0.000
$85 = 10.000
$90 = 0.000
$91 = 0.000
$92 = 0.000
$95 = 0.000
$100 = 158.244 (X-axis travel resolution, step/mm)
$101 = 157.488 (Y-axis travel resolution, step/mm)
$102 = 159.453 (Z-axis travel resolution, step/mm)
$110 = 500.000 (X-axis maximum rate, mm/min)
$111 = 500.000 (Y-axis maximum rate, mm/min)
$112 = 500.000 (Z-axis maximum rate, mm/min)
$120 = 10.000 (X-axis acceleration, mm/sec^2)
$121 = 10.000 (Y-axis acceleration, mm/sec^2)
$122 = 10.000 (Z-axis acceleration, mm/sec^2)
$130 = 200.000 (X-axis maximum travel, millimeters)
$131 = 200.000 (Y-axis maximum travel, millimeters)
$132 = 200.000 (Z-axis maximum travel, millimeters)
$341 = 0
$342 = 30.0
$343 = 25.0
$344 = 200.0
$345 = 100.0
$347 = 5.0
$348 = 2.500
$349 = 25.000
ok
$G
[GC:G0 G54 G17 G21 G90 G94 G49 G98 G50 M5 M9 T0 F0 S0.]
ok
$J=G20G91Z0.2F20
ok
[verbose] <Idle|WPos:0.001,0.000,0.470|Bf:35,1023>

G10 L20 P1 Z0
ok
G91 G20
G20 G91 G49
G38.2 Z-1 F10
G91 G20
ok
ok
[verbose] <Run|WPos:0.001,0.000,-0.075|Bf:34,1015>
[verbose] <Run|WPos:0.001,0.000,-0.583|Bf:34,1015>

[jrdarrah]

Where are is the status of pin information shown here

I checked the log file and this is all it gave on the probe command

INFO [com.willwinder.universalgcodesender.model.GUIBackend]: Sending gcode command: G10 L20 P1 Z0
INFO [com.willwinder.universalgcodesender.AbstractController]: Probing. axis: Z, feedRate: 10.0, distance: -1.0, units: INCH

[jrdarrah]

After reading through the list of issues I decided to try one more thing. Several posts mentioned problems with probing if the units were in inches or the probe units didn't match the jog units. As a part of my debugging I updated both UGS and grblHAL to the latest stable release. In doing so I forgot to set $13=1 for inches though the ugs settings were all in inches. Today I set jog & probe units to mm and $13=0. Shutdown and powered off to ensure a clean start in mm. I went through normal start up and homed the mill. Jogged the spindle to just above the target. Still using a piece of copper wire instead of a bit I initiated the z-axis probe. Same result. The wire touched and movement stopped. No double tap to read again and no retract. The xy probe went and probed the y-axis then stopped. I checked the probe wiring by looking for a voltage between the leads when it was not touching the target and saw what I expected, about 4.8v. When touching it dropped to 0v. I invert the probe with $6=1 and get no alarms related to probing.

Has the probe been fixed in a nightly release since the latest stable release? I'm running Product Version: Universal Gcode Platform 20210208.

Is there a way to just update the probe plugin?