Should Test/Tune jog Y and Y2 motors at the same time?

Hello folks! 
I have an XYY2Z machine with a 7i96s.  I'm just getting into first tests and setup. My question is whether or not both Y axis motors should move when you jog them from the "test/tune" screen in pncc?  X and Z axis move fine in + and -, but only the motor assigned to Y Main StepDir (in the TB1 assignments tab) will move when jogged. Swapping cables at the mesa shows Y2 motor is good, and if I also swap the TB1 assignments again, the jogging capability follows whichever motor is assigned as main axis. I'm not getting any output for the motor assigned as Y2 Tandem. Is this normal behavior? 

Thanks! 

You have to home your machine first, then joints Y and Y2 should move together. Before homing it is normal that only one joint will move when jogging.

Let me clarify....

I am not at the point where I need to jog from within LCNC.

I am referring to the axis motion test interface from within pncconf.

From within the individual axis setup pages, where you set the scaling, max speeds, accels, etc, there is a [Test/Tune] button. When you click that, it opens up a new window allowing you to move the axes in +/- directions after enabling them. From my understanding, there does not need to be a homing procedure done prior to moving the axes in the "test" environment.

I confirmed this because all axes will move while either the + or - button is pressed with the exception of the Y2 axis. If i go back to the TB1 pin assignments and switch the Y and Y2, effectively so the physical Y2 motor is assigned as Y, then it moves, but the other one doesnt.

Shouldnt both Y and Y2 move in the test environment?

It doesnt make logical sense that there would need to be a homing procedure done prior to this point since the other axes are allowed to move. What is preventing only the Y2 motor from turning in tandem with Y?

Does this apply to the pncconf interface or from within LCNC machine control interface?

I havent gotten to the point of configuring limits/home sequence. I was attempting to confirm all axis motors move in the right directions and that all of my scaling variables actually move an axis in the distance I expect it to.

Thats good news. I was chasing my tail trying to diagnose a communication issue for motors linked to the Y2 mesa outputs. If the design intent of LCNC/Mesa is to only move Y and not Y2 in the test environment, I can move on to setting up homing and limits.

I believe I have all the TB2 inputs set up for the switches. I am sharing home & limit switch on each axis. That gives me 8 total inputs to the TB3 for that function, I'm using 2 others for Estops (2 separate estop switches at different locations around the workspace), but my other concern was how to wire in the motor alarm signal to the mesa so that itll stop a program if there is a motor fault.

I might start a new thread on it when I get to that point. My new priority is the home/limit setup.

Thanks for the help so far, Tommy. Im getting anxious to have this machine running.

So i shouldnt use pncconf to get the machine going? This is where I set all of the homing and axis parameters.

I get the "Joint 0,1,2,3 on limit switch error" when i try to power on the machine [F2] and the homing buttons are greyed out. Not sure why that is yet but im trying to research it.

If you get on-limit errors, it likely means you need to invert the limit switch inputs

This would be the case with normally closed limit switches.

This is where running LinuxCNC and using halshow is very useful

(testing limit switch polarity and functionality)