I have a 4 axis CNC which has 2 Y axis tables. Until the date, I used this in Gantry mode with no homing procedure and everything worked ok; however I now need to use them separately, so i decided to route one of the Y axis to the chillipeppr Y axis and the other one to the chillipeppr A axis.
When i send a G code for moving the A axis, everything works as it should. So I started the configuration for the homing procedure of all the axis. X, Y and Z axis do a correct Homing procedure. They go towards the limit, and once they reach it they backoff according to my Zero Backoff configuration, and change the Logged value for that Axis to 0.00. However, the A axis doesnt do this. It moves towards the homing limit and once it reaches it, the axis stops moving and loggs an arbitrary value on the chillipeppr screen (not 0.00 but greater than 1000) . I have disabled the max limit switch which is not connected and configured the min limit switch as 1 (used in homing). I have also setup succesfully the softlimits, and tried disabling them to see if that was the issue but the issue persists.
A curious note is that the machine is not in an alarmed state when this occurs, it lets me move any axis i want including the A axis and when i type $hom it tells me the A axis isnt home.
Any Ideas why A isnt doing the zero backoff procedure?
PD: I have tried moving the switch to the max position and changing the motor polarity to check if it was a burned input on the tiny G, but same thing happens.