Slave axis not working until homed

[limited660]

When trying to jog the X axis (X + A), it will not work until I home the machine. I'm not sure yet if the motors are moving in opposite directions or if A axis isn't moving at all but they move together when homing and then the same jog button moves them together. I understand that UCCNC doesn't know where each is at before homing but this can mess the gantry up if you aren't squaring it with homing switches. Is there a reason the step/dir isn't sent the same before homing or is this a bug?

[cncdrive]

X and A slaving works fine at me without homing anything, I've just tested it.
Which UCCNC version and what controller are you running?
Post your profile file too.

[limited660]

Software version is 1.2047 and I'm using it with a UC100 with Gecko G540.

[limited660]

Any update on this? On my machine the motors are flipped so in normal movement A is moving the opposite direction of X.

[cncdrive]

I have tested with your profile and I do not see the issue.
I have checked it with version 1.2047 and with a UC100 controller.
I just started the UCCNC and did not do anything, I did not home or zero or anything, just started jogging and viewed the step/dir signals.
The direction signals are generated the opposite for the X and A just like how it is setup in your profile and the step signals are there for both the X and the A.
When I jog the X then I see the step signals on both the 2. and 8. pins. and I also see the dir signals generated and are always the opposite.
So, I could not reproduce the issue you described.