Tandem Y Axis in stepconf assistance.

I have spent quite a while trying to get one of our older CNC's to run again. I had a lot of issues with getting the gantry properly setup and I heard that 2.9.4 has support for tandem motor pin outs so I downloaded it and I have managed to get the gantry to move. The problem is that if i'm in the test axis in stepconf only 1 motor moves and in the actual jog interface the motors are separate joints so if I jog the gantry then I have to jog joint 1 and then joint 2 instead of pressing one button. As a result I move it incredibly slowly to avoid skewing it as much as possible. I would imagine I did something wrong or that their is some way to combine the two joints too run at the same time? would I need to do this in the HAL or INI files?. My other question is about how i'm supposed to setup the limits because I have just been setting up as: both limit X, both limit Y, and the same for the other two motors. I did get an error about limits on one of the Y's  but it didn't say much other than something along the lines of "Error limits Joint 2"
www.probotix.com/CNC-ROUTERS/CNC-ROUTER-GX2525 Here is the machine (It only says Comet on it but I am very sure this the same one)
www.probotix.com/wiki/index.php/Unity_Controller  Here is the controller its using as the old one had some fried chips that couldn't be replaced. It also has the pin outs where I got the limits from.
Sorry if I it's something obvious because I really haven't used linuxCNC ever before (Also disclaimer: I haven't set the latency test right yet because I only got it working in a test setup yesterday and I didn't have time for it but I know I need to do it)
 

Well it has 2 motors and the web page mentions that it needs limits/homing switches because of the tandem setup. Each motor for the gantry also has its own cable and port. I am assuming thats what drives are.

I would imagine that it does. All the documentation suggests so and from what i can see on the other side (Its right up against a wall) It looks the same on both sides so I would wager it has them on both. So im going with yes on that.

Read the online documentation for V 2.9  for "homing configuration" (Several times)
the HOME_SEQUENCE parameter for each side of the gantry must be the same and it must be negative to tell Linuxcnc to treat it as a joint axis.

Ok so what im getting is that if two joints have a HOME_SEQUENCE = -1 then that tells the two motors to run together right?

I did do what RodW said to do and from that I figured to add "HOME_SEQUENCE = -1" to the two Y motors. would there be anything else I need to add in the INI files?
Also I don't know if you want to take a look but if you do here it is

# Generated by stepconf 1.1 at Fri Apr 25 14:44:59 2025
# If you make changes to this file, they will be
# overwritten when you run stepconf again

[EMC]
MACHINE = 22222222222222
DEBUG = 0
VERSION = 1.1

[DISPLAY]
DISPLAY = gmoccapy
EDITOR = gedit
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
ARCDIVISION = 64
GRIDS = 10mm 20mm 50mm 100mm 1in 2in 5in 10in
MAX_FEED_OVERRIDE = 1.2
MIN_SPINDLE_OVERRIDE = 0.5
MAX_SPINDLE_OVERRIDE = 1.2
DEFAULT_LINEAR_VELOCITY = 0.10
MIN_LINEAR_VELOCITY = 0
MAX_LINEAR_VELOCITY = 1.00
CYCLE_TIME = 0.100
INTRO_GRAPHIC = linuxcnc.gif
INTRO_TIME = 5
PROGRAM_PREFIX = /home/probotix/linuxcnc/nc_files
INCREMENTS = .1in .05in .01in .005in .001in .0005in .0001in

[KINS]
JOINTS = 4
KINEMATICS = trivkins coordinates=XYYZ kinstype=BOTH

[FILTER]
PROGRAM_EXTENSION = .png,.gif,.jpg Greyscale Depth Image
PROGRAM_EXTENSION = .py Python Script
PROGRAM_EXTENSION = .nc,.tap G-Code File
png = image-to-gcode
gif = image-to-gcode
jpg = image-to-gcode
py = python

[TASK]
TASK = milltask
CYCLE_TIME = 0.010

[RS274NGC]
PARAMETER_FILE = linuxcnc.var

[EMCMOT]
EMCMOT = motmod
COMM_TIMEOUT = 1.0
BASE_PERIOD = 100000
SERVO_PERIOD = 1000000

[HAL]
HALFILE = 22222222222222.hal
HALFILE = custom.hal
POSTGUI_HALFILE = postgui_call_list.hal

[TRAJ]
COORDINATES = X Y Y Z
LINEAR_UNITS = inch
ANGULAR_UNITS = degree
DEFAULT_LINEAR_VELOCITY = 0.10
MAX_LINEAR_VELOCITY = 1.00

[EMCIO]
EMCIO = io
CYCLE_TIME = 0.100
TOOL_TABLE = tool.tbl

#*** AXIS_X *******************************
[AXIS_X]
MAX_VELOCITY = 1.0
MAX_ACCELERATION = 30.0
MIN_LIMIT = -0.01
MAX_LIMIT = 8.0

[JOINT_0]
TYPE = LINEAR
HOME = 0.0
MIN_LIMIT = -0.01
MAX_LIMIT = 8.0
MAX_VELOCITY = 1.0
MAX_ACCELERATION = 30.0
STEPGEN_MAXACCEL = 37.5
SCALE = 8000.0
FERROR = 0.05
MIN_FERROR = 0.01
HOME_OFFSET = 0.0
#******************************************

#*** AXIS_Y *******************************
[AXIS_Y]
MAX_VELOCITY = 1.0
MAX_ACCELERATION = 10.0
MIN_LIMIT = -0.01
MAX_LIMIT = 8.0

[JOINT_1]
HOME_SEQUENCE = -1
TYPE = LINEAR
HOME = 0.0
MIN_LIMIT = -0.01
MAX_LIMIT = 8.0
MAX_VELOCITY = 1.0
MAX_ACCELERATION = 10.0
STEPGEN_MAXACCEL = 12.5
SCALE = 4000.0
FERROR = 0.05
MIN_FERROR = 0.01
HOME_OFFSET = 0.0

[JOINT_2]
HOME_SEQUENCE = -1
TYPE = LINEAR
HOME = 0.0
MIN_LIMIT = -0.01
MAX_LIMIT = 8.0
MAX_VELOCITY = 1.0
MAX_ACCELERATION = 10.0
STEPGEN_MAXACCEL = 12.5
SCALE = 4000.0
FERROR = 0.05
MIN_FERROR = 0.01
HOME_OFFSET = 0.0
#******************************************

#*** AXIS_Z *******************************
[AXIS_Z]
MAX_VELOCITY = 1.0
MAX_ACCELERATION = 30.0
MIN_LIMIT = -4.0
MAX_LIMIT = 0.01

[JOINT_3]
TYPE = LINEAR
HOME = 0.0
MIN_LIMIT = -4.0
MAX_LIMIT = 0.01
MAX_VELOCITY = 1.0
MAX_ACCELERATION = 30.0
STEPGEN_MAXACCEL = 37.5
SCALE = 8000.0
FERROR = 1
MIN_FERROR = .25
HOME_OFFSET = 0.0
#******************************************

Well I'm quite sure it has 2 limits on the gantry. I will check tomorrow and I will check if they work tomorrow. sorry for the confusion here I Rod just said read through the configuration manual.