Hi all, I am running gSender on a custom lathe build. The controller I am using is a “Jackpot v2” flashed with grblHAL. Most things appear to work as expected except for, gSender can not seem to write to the eprom, i.e. steps per mm, etc.. I am running the board directly connected over USB and I did not flash the components necessary to use a web UI. I “says” that it is writing but the settings never actually stick. Is anyone else experiencing this?
@Philshel Welcome to the group. From the little research that I did on your board, it is running FluidNC. You may want to search here for fluidnc. You will see many post about incompatibilities with it and gSender. They may help - or not. 
Thanks for the reply. It “ships” with Fluid but is capable of running grblHal as well. I flashed the firmware to grblHal because I wanted to run gSender. I have tried using Fluid in the past and ran into the issues you mention with gSender, so I’m aware of the incompatibilities which is why I flashed this new board to grblHal. This issue appears to be between gSender and grblHal and I have not ran into it before.
@Philshel I’ve no doubt that Sienci will reply soon. In the meantime, what version of grblHal did you flash? Where did you get it?
I just used the grblHal web builder.
Our main boards are grblHAL so there’s no incompatibility between the firmware and the sender.
What happens if you directly try to change the value in the console?
Is this an issue with a specific EEPROM setting or all of them?
Thank you for responding. I’m not sure if its “all” of the settings, I’ve only been trying to setup the motors so far. Either from the UI or from the console, I can change all the setting except the steps, the issue is that it’s not persistent. They will change back to a “default” as soon as the board it powered down or gSender is disconnected from the board. Now, the microsteps refuse to change from 16 no mater what. It appears to write to the firmware but actually does not.
If you get the same behaviour from the console, it means you have some write protection on your flash memory - the issue is with your board/firmware driver, not gSender. I’m not familiar enough with your controller to say what the fix is.
Yes, I’ve came to that conclusion myself. I apparently did something wrong during the flashing. I will be going back to my old Blackbox until I get this figured out. I appreciate you taking the time to look at my issue though.