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.
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 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
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
Any progress on this x axis fail? As i mentioned your fix worked for up and down and all angles with positive x. let me know when there may be a new release.
@tme we’re still not 100% on what’s causing your problem, but we’ve got a swath of fixes underway for the next version and perhaps one of them might address your issue but we’ll have to wait and see. The next version should be out in the next 1-2 weeks so keep your eyes out and then give it a try and let us know what you see 
1 Like
@chrismakesstuff I have updated to 1.5.3 and the problem persists in any long move containing an negative x component in the arrow I chose ON INITIAL HOME. However if I home a second time and of course long move to the right and I can now finally long move to the left. All moves seem to start working normally.
So there appears to be a difference in the initial red button “mandatory home” and the regular home button. For reference my home position is the top left corner and I am of course using home sensors. I also have soft limits enabled.
At least I can make it work now (so far)
Let me know if this helps you figure out where the problem is.
Albert
feeder $J=G21G91 X-724.53 F2999.99
error:15 (Travel exceeded)
1 Like
@chrismakesstuff I know you have been fighting spammers, just calling attention to my previous reply in case you missed it. Look above…
Thanks .
1 Like
I was surfacing a 16x16 inch chess board and i hit a soft limit error. Surfacing generated soft limit error requiring homing.
ok
G1 Y8.908
ok
G1 X7.092
ok
G1 Y7.486
ok
G1 X8.514
ok
G1 Y8.514
ok
G1 X7.486
G1 Y7.88
ok
G1 X8.12
ok
G1 Y8.12
ok
G1 X7.88
ok
G0 Z0.12
ok
G0 X0 Y0
M5
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
G4 P0.5
ok
ok
M9
ok
F3500
ok
Z25.400
ALARM:2 (Soft limit)
[MSG:Reset to continue]
ok
Grbl 1.1h [‘$’ for help] LongMill MK2 build Feb 7, 2022
[MSG:‘$H’|‘$X’ to unlock]
[MSG:Caution: Unlocked]
ok