gSender-Edge 1.3.7 fails completely at probing using GUI

gSender 🐛 Bug
1

BUT I can zero by entering G38.2 commands in the console

Errors in console when it tries to use the GUI probe functions:

feeder G38.2 Y[Y_PROBE_DISTANCE] F[PROBE_FAST_FEED]
error:2 (Bad number format)
feeder G91 G0 Y[Y_RETRACT_DISTANCE]
error:2 (Bad number format)
feeder G38.2 Y[Y_PROBE_DISTANCE] F[PROBE_SLOW_FEED]
error:2 (Bad number format)
feeder G4 P[DWELL]
error:2 (Bad number format)
feeder G10 L20 P0 Y[Y_THICKNESS]
error:2 (Bad number format)
feeder G0 Y[Y_RETRACT_DISTANCE]
error:2 (Bad number format)
feeder G38.2 Y[Y_PROBE_DISTANCE] F[PROBE_FAST_FEED]
error:2 (Bad number format)

And I get a dialog with error 8 on line 2911 - Not Idle
X166.889Y132.489
X166.724Y131.347
X166.492Y132.052
Z2.540
(Logo - Vee)
M0 ;T301
S18000 <— line 2911 <—
G0X310.045Y91.223
G1Z-2.540F304.8
X310.048Y92.627F889.0
X310.072Y92.995
X310.276Y94.412
X310.348Y95.296
X310.460Y95.959
X310.636Y96.715

And after I probe using G38.2 commands in console gSender locks up and I have to quit and restart at the proper line

Model Identifier: iMac12,2 Processor Name: Intel Core i5
Processor Speed: 2.7 GHz Number of Processors: 1 Memory: 12 GB
System Version: macOS 10.13.6 (17G14042)

2

Which touchplate type (Autozero, standard) and which probe routine were your running? We’ll take a look - it looks like the variables aren’t being parsed correctly on whatever routine you’re running.

3

I am having a similar problem with gui probe. On Z probe I can test the probe connectivity fine but when I click the probe button there is no z movement. I see the notification that the probe initialized but no movement.

XYZ probe was working fine. I did not try the other probe methods.

Using the standard touch plate on upgraded MK1 30x48 with gSender 1.3.7 edge on Windows 10 mini PC

4

This should tentatively be fixed next edge release - the variables weren’t properly propogating on single-axis probing.

1 Like