Sending errors with gSender but not with UGS

I have a Genmitsu 4040 Pro Max. If I use UGS, I can run large files with no problem. However, with gSender, I get an error after a few tens or hundreds of lines, and it stops. e.g.

X3.288 Y2.847
ok
X3.094 Y3.711
ok
X2.957 Y4.587
error:25 (Invalid gcode ID:25)
error:25 (Invalid gcode ID:25)
ok
ok
ok
ok
ok
ok
error:25 (Invalid gcode ID:25)

I sometimes get: error:2 (Bad number format), even when establishing the connection.

I have replaced the USB cable with a good quality new one. I have put ferrite cores on the cable. I have even reinstalled MacOS on the MacBook (Intel, with Sonoma).

This is a shame as I really prefer gSender over UGS.

This is with the latest version of gSender (1.5.2). It worked without a problem on 1.4.

For a long time I was sure this must be due to cabling, interference etc. However, it is consistent that when I run UGS, I can send a file with no problem, but when I use gSender, it is only a few seconds before the error occurs.

@JulianG I suggest that you open a support ticket with Sienci. The additional information that the support ticket form includes will, no doubt, help Sienci determine what is going on. In the meantime, you may want to revert to 1.4.12, as you’ve said that worked well for you.

I reported this to Support, and they have given me the fix. Apparently, when you connect, if the machine is not identified, gSender defaults to grblHAL. My Genmitsu uses grbl.

The answer is to go into Config Basics and change the firmware fallback from grblHAL to grbl. You can also find this in Stats. Press Change in the Configuration section.

Julian

1 Like