My first problem was jogging. Continuous jogging doesnāt work most of the time. Here I connected, homed and did a single click jog without issue. Then it failed on the first continuous jog attempt. Y10,000 seems way too big but I donāt often look at the output from jogging so what do I know.
Apparently Iāve been jogging around without connecting!?! Letās connect inside my connection, that should bring us to a Level 2 connection. Or maybe itāll be a squared connection?
Hey I found the missing UI elements! Too bad I still canāt jog right. The corner buttons also give me a soft limit error now that I have one to click.
This was all done with the Debian package. The AppImage wont even run. Canāt find libfuse.so.2. I guess thatās because Ubuntu is on libfuse3? I was able to extract the image and change owner and permissions of chrome-sandbox. After that it ran! With all the same issues as the Debian package unfortunately.
I ran gSender from the terminal so I have the output from a short Wayland and X11 session.
You are not the only one Michael. Sometimes the P and HOME button show up, usually not. I changed the mid speed, and it will not stay. Longmill MK1 with the Longboard. Windows 11. Other wise it works. I may just go back to 1.4, that always worked. Havenāt found a setting to delay the spindle either.
Yeah, Iāve already gone back and forth between versions a couple of times. I reinstalled 1.5 today so I could document my issues. When I first tried 1.5 I was doing something and had no patience for it! Iām sure theyāll get it sorted and Iām fine with 1.4 for now. I guess itās not just a Linux thing since your on Windows 11 and have had some of the same issues.
i recently found a fix for continuous jogging that for me was only bugging in rapid.
instead of having 20 for the XY change it to 5, sure you can only move 5 at a time when tapping , but it is a āfixā
I am having the same problem. First installed it seemed to work even though the screen size on the carve page doesnāt open properly. I know get a undefined feed rate code 22 and tried shutting and resetting but nothing works.
Iām also having a problem with gSender 1.5.0 and jogging. I have an ACER Aspire 5 laptop running windows 11 connected to a 1st gen MillRight CNC. In the past (only a month ago) I was running V1.2.2 with no problems at all. I had not upgraded because I am always wary of Beta versions of anything. When I saw that 1.5.0 was on general release to the community I decided to upgrade my system. I have 2, thankfully I only upgraded my smaller older system! Anyway, I followed the install instructions rigorously and appeared to have no issues. However, I wasnāt able to jog anywhere even though I had set the machine to MillRight in the software. When I looked at the jogging settings I realized that they were nonsense. So I reset the values to those that i knew had worked previously. Eureka! Simple fix, happy user. Not for long! If I pressed the diagonal jog button the system froze. Similarly, if I tried to press a single jog movement it may jog 3 ot 4 times and then freeze. Trying a continuous jog was useless. To reset the system I have to power down the controller and reboot gSender, but then I noticed another problem. Even though I had updated the correct jogging parameters in the config icon and the correct XY, Z, and āatā numbers were displayed in the āNormalā jogging window when I rebooted, as soon as i toggled between ānormalā to ārapidā and back to ānormalā the jog settings went back to the gibberish numbers that were there before I updated the config settings. I have attached png files showing the two ānormalā setting. Iām old school and still work in inches the correct settings as XY 1, Z 0.05, at 118.11. The āatā may seem odd but its what came back when i entered 3000 mm/min as the speed in the config menu. So it seems that the firmware is not updating correctly, and this may be causing some people like me problems.
Because of this I decided to look at the consul readout after rebooting the system and before I tested the jogging again. Here I noticed another problem, in that there was a disconnect between what was reported as the machine settings in the Stats window, and the grbl commands in the console. In the config I had set soft limit, hard limits, and homing, to off but the lines corresponding to soft and hard limits in the gcode console were reporting as āonā. I manually changed the gcode in the console and that has solved that problem for anyone who may be having ālimitā problems. I thought I would give the jogging test one last try before I gave up and tried to contact gSender support. I first made sure that all of the settings were correct in both the config and firmware sections and were showing up correctly in the jog window. As before the system allowed me to jog a few times either left or right up or down and then would randomly. I tried this a few times to see if there was a pattern and there wasnāt, but what I did realize was that, as Michael saw in his console readout, when the jog button worked the readout would be something like $J=G20 G91 X0.965, F118.11 in my case, and this format would be consistent while the jog worked. However, as soon as it failed the gcode was corrupted it now read $J=G20G91 X1000 F118.1. The first two G commands had been combined and the X distance command had increased from ~1 to 10000, which is the same increment that Michael saw even though he was using a different computer, different OS, different CNC with different connections, and trying to jog in a different direction and with different starting increments. To me this seems like it has to be a bug in the software diagnostics_6-27-2025_13-32-15.zip (80.7 KB) gSender-firmware-settings-6_27_2025-1_31_15 PM.json (556 Bytes) gSender-settings-6_27_2025-1_28_59 PM.json (72.0 KB)
which, for whatever reason, is defaulting to the largest X or Y increment available. This may be because the two G commands at the beginning have been merged but Iām not a coder. Iām attaching my diagnostic file, gSender file, and format files together with some screenshots to illustrate the problem. I hope this helps someone get to the bottom of this
@Tig I did not read your entire post, but Sienci announced that 1.5.1 was now available. You may want to look at the fixes in it to see if they address your issues.
Hi Grant, thanks for the heads-up. The update did solve the problem of the software not saving changes made in the config file when gSender closes but unfortunately it didnāt solve the jogging problem.
@Tig Don, there is a thread on here now for the release of 1.5.1. Contribute to that topic by explaining your remaining issues. You can see there that @chrismakesstuff believes that these issues have been resolved, but he is open to input on that.
