Fixed Tool Sensor Wizard behavior?

gSender ❓ Question
1

I’m attempting to use the Fixed Tool Sensor Wizard in gSender 1.4.9 and when the Wizard attempts to send the router to the position of the sensor, I receive Error 2. Looking at the console, it appears the Wizard is still in incremental mode and not absolute mode, so when it attempts to move to the XY position (G53 G0 X250.44 Y-30.5) it causes the error, because the system is still in incremental mode, and those coordinates would definitely be outside my defined XY area.

There have been multiple, similar notes posted over the past few years, but none of them ever noted that their issue had been resolved.

ok
G90 G94 (absolute)
G17 (plane)
G21 (metric)
G28 G91 Z0 (incremental)
G90 (absolute)
(T1) (M6)
ok (Start of wizard)
ok
ok
ok
ok
ok
 G4 P0.5 (pause)
ok
 M5 (router off)
ok
 G4 P0.5 (pause)
ok
 G91 G21 (incremental) (metric)
ok
 G53 G0 Z-10 (Z up 10)
ok
 G53 G0 X250.44 Y-30.5 (X and Y to the fixed TLS position) FAIL!
ALARM:2 (Soft limit alarm. G-code motion target exceeds machine travel. Machine position retained. Alarm may be safely unlocked.)
[MSG:Reset to continue]
2

Interestingly, it seems there were a couple of note threads about 7 months ago reporting the same issues, but the original posters never reported back if they resolved their issues.

- https://forum.sienci.com/t/new-to-tool-change-whats-missing/10720/6
- https://forum.sienci.com/t/fixed-location-tool-change-issue/9421
3

This seems like an instance that should be fixable. Thanks for your patience @JohnOCFII, I wonder if the issue is similar to another thread I was on helping with added Pausing in the TLS wizard. Are you seeing that on your side?

4

I haven’t seen that behavior – but I haven’t progressed that far through the Wizard yet, as the “Error 2” appears earlier in the sequence. But I’ll be watching for it!

Thanks,

John

2 Likes
5

I am having the same issue in 1.5 version gsender. This sucks and needs to be fixed please

6

@715workshop Welcome to the group, Tom.

As there is no version 1.5 of gSender, are you maybe using 1.50 - edge - 8? If so, you may want to try the lastest version of gSender, which is 1.4.12. Edge is the beta/test version and may have bugs while it is in development.

7

My fault. I’m using 1.4.12. I think I found the issue. Normally I have been running in inches. I switched $13 to 0 for metric. Then I had to set $132 to 220 mm for max z travel. Then it worked! Now I switch back to inches and I get the soft limit error again. G38.2 is telling z to move -189.28 in mm when probing for TLO on 1st tool. I don’t know how to change the G38.2 setting as it is not following any set parameters in firmware or preference. Trying to increase max z to avoid soft limit alarm. G38.2 needs to be changed somehow.

image
image1920×2560 634 KB

8

Update. When I switch back to inch I get soft limit alarm. I had to set $132 to 5080 mm to get it to probe since now it seems like G38.2 is using the 189.28 as inches but firmware takes the length in mm. Also now when TLO probing is complete the Z0 is way off. It is like 2 inches higher than my previous tool zero setting. I’m going back to mm to keep things moving.

9

Solution! After many painstaking hours learning code and macros lol I figured it out. Well at least to get my RapidChange ATC working. More testing needed with the gsender wizard. For me the solution was making sure to keep the “firmware” settings set to mm. If you want to see things in inches you can only change the setting to inches in preferences. There SHOULD be a major warning when changing firmware to inches, just sayin. All tool touch off and Probing seem to be calculating correctly now. Many thanks to Don G. At RapidChange spending hours testing with me. What a great crew over there. Those guys will bend over backwards to help customers.

1 Like