@Twisthem488 Search on here for reverting to a previous version of gSender. There are several threads that explain what you need to do before installing an older version.
Hey Trig, I think Iāve found something out. Mine seemed to stop working randomly, but it turns out if I didnāt click fast enough it would thing Iām holding the button and try to do a continuous move. Whenever this happened it would stop responding to future commands. I was able to replicate this by purposefully clicking and holding the button. Whenever I did, it would send the G20G91 move command with the value of 10000 and then always fail to followup or respond afterwards until reconnecting to the cnc.
I found a workaround and wonder if you could try to see if itās true for you as well. Go to your Gsender settings and change it from inches to mm. Then try to do a continuous move while pressing and holding a jog button. You should notice that the jog command changes from G20G91 to G21G91 (since youāre now in metric), and at least for me will do a proper continuous move and continue to work afterwards. I donāt know if this is related to some unit conversion that is happening behind the scenes or what, but for the time being Iāll just work in mm.
2 Likes
Hey Twistthem88 (great handle) I just read your note and will try it out shortly and will let you know the result. Thanks!
You absolutely nailed it my friend. There is obviously a bug in the conversion code that crashes the system when it has to convert too quickly. The code then becomes a mix of a G20 command and metric units! This should be something that the gSender people can track down quite quickly, there must be quite a few people who want to work in inches who are affected by this bug.
1 Like
Hey Grant if you have a look at the thread below you will see that there appears to be a bug in the metric to inches conversion code that is crashing the program for several of us. Can you let the folks at gSender know?
Cheers, Tig
@Tig Don: Sienci tech monitors the gSender topics so Iām sure that they already know of this bug. That said, I suspect that Sienci is closed today and they will definitely be closed tomorrow for Canada Day.
I think my problem is the 720p monitor and older computer sending 1080 that gets downgraded by monitor.
I played with all my settings with regards to sizing and resolutions.
I plan on upgrading cpu shortly to either your display/cpu or just a newer mini cpu.
1 Like
I just updated to the new 1.5.1 from an older 1.4.x and the first thing I notice is that jog no longer does anything when you click and hold on to the direction. i.e. no continuous jog. If I momentarily click on the jog arrow I get the expected short burs of movement. Running GRBL tried mm and now back to inches all speeds work the same.
Iām using a Longmill MK1, SLB and gcontrol panel. The jogging problem has been fixed when using both VCarve and Lightburn. Iām really enjoying many of the new features!
1 Like
Roger that @Tig and @Twisthem488, weāll see if we can find a solution to this and get it out on the next release - keep an eye out. Itās the werenāt 1000 inch jog movements that are causing your machines to freeze up
@Johan.Mota the reason for this is that we now have combined firmware settings and app setting together in this new version and since firmware settings can never change from using mm (itās built into the core of grbl and grblHAL) then we chose to also have gSenderās settings follow suit with mm as well. Otherwise, it would look quite disjointed with different units intermingled. Donāt worry, you can still convert your dimensions from inches to mm, enter them into the settings, and you should be good to go.
@saskia itās really sad to hear about that. Itās been unfortunate that the libraries weāve been working with continue to drop support for older devices, since that puts us in a spot where thereās no other way to keep making new gSender iterations without losing support for older devices. You can still of course download all older gSender versions that are compatible so at least thereās that - sorry I canāt offer any other solution
@tme can you provide some more information about your issue with click-and-hold jogging? Weāre not seeing that happen in our setups
1 Like
There is really not much more to say. If I click and hold on a jog arrow I expect it to move in that direction until I let go, but nothing happens. I am using your original longboard running GRBL and I have set up sender for GRBL. Seems I remember a similar issue a long time ago and went from inches to mm and it fixed it back then. Tried that this time and it did not fix it, @saskia your not just missing out on support on older devices if you are not supporting GRBL then you are not going to make gsender the supreme sender of all G-Code senders. A quick solution to this problem would be for your company to send me a upgrade tp a Super LongBoard. 
1 Like
Console output of what commands are being sent when itās not continuous jogging for you would be helpful as a start, along with your configured eeprom settings so we can easier recreate it.
Here is my console output with long click on up, right, down, and left arrows:
$J=G20G91 Y10000 F118.11
error:15 (Travel exceeded)
$J=G20G91 X10000 F118.11
error:15 (Travel exceeded)
$J=G20G91 Y-10000 F118.11
error:15 (Travel exceeded)
$J=G20G91 X-10000 F118.11
error:15 (Travel exceeded)
here are eeprom settings and gsender settings.
gSender-firmware-settings-7_11_2025-2_50_33 PM.json (561 Bytes)
@tme Iāll preface my remarks by emphasizing that I am not Sienci tech support.
You said in your post that you were using an original longboard and running grbl. But, the .json file that you attached shows that the ādefault firmwareā is grblHal.
That is not selecting the firmware, it only goes to HAL if the autodetect fails. Its a backup setting the way I understand it. It doesnāt matter where I set that my autodetect always works. I set it back to GRBL and it still does not do continuous jog. I think I read somewhere you can leave that at default.
1 Like
@tme I can see your issue is the same as what I noted for @Tig and @Twisthem488 above with the 10000 inch jog movements which is causing your jogging to not work. Weāll have a fix for that out in 1.5.2 which should be released tomorrow, then you can let us know if youāre right as rain again!
3 Likes
@tme Kevin mightāve also found some other possible edge cases that weāre still investigating so they might not be done on time for the build tomorrow, but either way let us know once you update to 1.5.2 after we release and we can work on it more from there
Notes
- Fix issues with remote mode disconnecting main client and jobs stopping when connecting from remote mode
- Significantly sped up file loading and rendering on larger files
- Job end notifications will no longer appear if toggled off
- SVG visualization no longer teeny-tiny on inches post processor files
- Plus and Minus buttons returned to jog speeds with the prior existing logic
- AutoZero touchplate renamed to just AutoZero
- Added new Config option for Jog Delay, which configures how long a keypress/UI press/gamepad press needs to be made before swapping to continuous jogging
- Commands sent later in connection cycle to reduce situations where Error 1 occurs when unlocking and resetting the board
- Generating a surfacing file no longer causes issues on main visualizer if not sent there
- Motors sections again will disappear from config when empty
- Restore defaults and default highlight works correctly in Config on settings considered hybrid between grbl/grblHAL
- Prevented situations where alarm list was not populating correctly
- Continuous jog without soft limits now sends more sane values when jogging in Inches across both controllers (used to be 10000)
- Stopping a file that has an early M0 already sent will no longer pop up the pause modal
- Config look and feel tweaks
- Shortcuts rearranged so more commonly set ones are higher up
- File stat feed rates now convert correctly
- Zero All on grblHAL no longer sends Zero on A if A-axis not reported
- Various look and feel changes
Download
As always, gSender can be downloaded on Github:
2 Likes
Well I may still be an edge case. The problem is mostly resolved but still does not move continuously at any angle that has -x movement. Here are the console commands that still fail and the directions that pass.
$J=G21G91 X-598.26 Y190.09 F2999.99
error:15 (Travel exceeded)
$J=G21G91 X-598.26 F2999.99
error:15 (Travel exceeded)
$J=G21G91 X-598.26 Y-662.91 F2999.99
error:15 (Travel exceeded)
$J=G21G91 Y190.09 F2999.99
ok
$J=G21G91 Y-691.41 F2999.99
ok
$J=G21G91 X216.74 F2999.99
ok
1 Like
I upgraded from 1.4. Which had no problems other than the screen locking if it is running in the background. That was the main reason for installing the new version. It would just sit there, not letting me hit pause or stop, locked up if I had it in the background.
I am using a FoxAlien XE-Pro running Grbl 1.1h. I have the config set for Grbl vs GrblHAL.
After I zero the Z axis and I hit the XY button my machine dives into the workpiece at full force and I have to unplug it. I tried switching back to GrblHAL but it did the same thing.
It seems to only happen after Zeroing the Z axis. Iām lucky it didnāt break anything. Iām lucky it was positioned where it was and not over a hold down. It pushed a .25" shank, 4 flute, 30 deg v-bit almost all the way through .75 plywood.
Update: I went back to version 1.4.12 and it is doing the same thing.