GSender Edge version Force of home doesn't work

gSender 🐛 Bug
1

Maybe this is a user issue I have an AltMill Mk2, gSender Edge latest version (downloaded yesterday it confusingly says “Next Week” on it) and the previous version I had both do this. I have the check box enabled that’s supposed to require me to home the machine on connection yet not one time has it asked me to do that or required it to start working with the machine. When I was connected to my previous CNC machine this would pop up every time I connected to gSender.

2

  1. To be clear, “homing on startup” is a firmware feature, not a gSender feature

    gSender_Edge_YzmuCxK4od
    gSender_Edge_YzmuCxK4od1385×368 28.6 KB

  2. Homing state persists until the SLB-ext is cycled (or other homing related config changes like homing direction). If you power cycled the board and reconnected, you should get an Alarm 11 (Homing required). If you have not power cycled the board, you do not need to rehome.

  3. Was your previous CNC machine grbl based, because the Arduino power cycles on connect, forcing homing on connection. The SLB derivatives do not have this limitation.

3

Ah that makes more sense didn’t realise that. Unfortunate as if I don’t home the AltMill when I start it up then the 3 preset buttons on the e-stop don’t do anything. I do get an alarm when I connect but for some reason in my brain it’s 14 not 11 and it does not force me to home it at all


4

grblHAL can report one alarm at a time. If you’re seeing a VFD related alarm, clearing that would also clear the homing alarm - it doesn’t re-report another alarm state.