Y2 motor not moving during test/tune within PnCConf

Added second Y motor to working 2.8 Rpi4 gantry machine. Edited with PnCConf to add Y2 motor - Mesa 7i76e setup shows 4th stepper as Y2 but with test enable it doesn't +/- jog. XYZ works, no problem. Not a hardware issue since the D542T driver and motor were swapped in/out with other axis.... wiring/hardware all OK. Since I'm testing within PnCConf (not AXIS GUI) I don't think it has anything to do with home/limit switches. Read lots of posts on tandem axis but didn't see this issue. Suggestion please?

I would just move ahead to running LinuxCNC

will do - weird but we'll give it a try first thing tomorrow - thanks
I did read something somewhere about setting reverse direction affects step not direction signals - will check that as well.

PCW - just ran LinuxCNC as you suggested and things are improving. Now only ERROR that needs a work around is "Cannot jog, home_sequence is synchronized" for joints 1 and 2 on Y axis. Based on 2.8 documents I changed the Y axis Joints 1 and 2 HOME_SEARCH_VEL and HOME_LATCH_VEL to =0 which should disable homing and allow jogging - BUT still no go. Is there a simple work around here ? Thanks,

I think that is expected for gantry configurations (you cannot jog until homed)

Yes I understand...but I'm at the stage where I want to test the motor direction and calibration and can't move (jog) the motors on the synchronized axis to do so. A little risky to shoot for 'home'. but if that's the way it works....I guess I could create a temp ini using only one at a time ..... (and make sure they are mechanically uncoupled) but was looking for a shortcut. Thanks for everyone's help...it's a great tool.

you can also not use synchronized homing if you want to jog joints to test