If you are unable to jog your machine, ensure you are connected to the correct firmware for your controller when using gSender. You may have recieved an Error 2 notification when connecting to the controller.
Resolution:
Firmware Connection
Longboard controllers will use grbl firmware.
gSender 1.4.12 and under
gSender 1.5.0 and above, auto connect to grbl
SuperLongBoard and SuperLongBoard-EXT will use grblHAL firmware.
gSender 1.4.12 and under
gSender 1.5.0 and above, auto connect to grblHAL
If your controller is auto connecting to the wrong firmware, go to Config, at the sidebar go to Basics and set Firmware fallback to the desired firmware. Then press Apply Settings.
Jogging Presets
If you are using the correct firmware, check and confirm your Jogging presets are defined.
Open the diagnostic report and under preferences, if it states "undefined" it's missing the settings for jogging the machine.
You can also check on gSender's main screen. In the Jog Control you may see the letters NaN in the text fields, as below. If your gSender matches below, the Jogging Presets are not defined and will need to be restored back to default.
Open the Firmware Tool (gSender 1.4.12 and under), OR Config (gSender 1.5.0 and above).
Under Jogging Presets click the Reset to Default button. This will restore your Jogging Presets and you should be able to jog your machine.
gSender 1.4.12 and below
gSender 1.5.0 and above
Motor Cables
Check that the green connector going to the motor has all of its connections intact and are not loose. For the closed loop motors: to insert wire into each terminal use a small flat screwdriver to press down on the orange tab to open the terminal. Tug wires to check they are secured.
Furthermore, to verify whether the issue is with the controller, motor or motor harness, please follow the troubleshooting chart (file attached to this article).
Motor Alarm
On gSender's Console, check if you have a motor alarm. See this article for details on how to troubleshoot.