Trying to Configure Dual Y Axis

I think I am close but an getting one error and can't figure it out.  I attached a copy of the INI, HAL and error report file.
I ran all the timing and stepping scales on a single Y axis program and everything is calibrated and working fine.  If I could simply add this additional motor to the Y axis that would be great.  I can add parameters for homing later.

Would greatly appreciate any help.

Thanks in advance

All you need to do to set up a dual axis is to add HOME_SEQUENCE= to each of your joints in the ini file
This sets the order of homing. Joint axes are tied together with a negative value. Usually you will home the Z first to raise it out of the road. Note you have to consider homing and add home switches  now as it's required for the joint axes.
Joint 0 HOME_SEQUENCE=1
Joint 1 HOME_SEQUENCE=-2
Joint 2 HOME_SEQUENCE=-2
Joint 3 HOME_SEQUENCE=0

Routerworks wrote:

...  I attached a copy of the INI, HAL and error report file...

 

Humm, No... Only INI and HAL are attached... no error report file...

Thanks a lot. This looks encouraging. I will make the changes and give it a try.
I didn't realize the homing was required

Many thanks

Sorry about that.  Here is the report.

Had to change format. 

Nope, no report.
-
Yay, report!

Do you have it now?

From your hal file:
net ystep => parport.0.pin-04-out
then
net y0pos-cmd joint.1.motor-pos-cmd => stepgen.1.position-cmd
net y0pos-fb stepgen.1.position-fb => joint.1.motor-pos-fb
net y0step <= stepgen.1.step
net y0dir <= stepgen.1.dir
net y0enable joint.1.amp-enable-out => stepgen.1.enable
That will not work, ystep requires ypos, ystep, ydir, yenable, etc, not y0pos
this is all over the hal file, so to many things to fix.
-
Lets go back, you have a parallel port, so limited IO, do you want:
-to have limit switches on all axis/joints?
-do you need to square the gantry or is it stiff enough to stay trammed?
-do you want to have both motors/drives for Y axis run at the same time, even when jogging and before homing the machine?

From the hal file:

setp parport.0.pin-01-out-invert 1
net estop-out => parport.0.pin-01-out
net xstep => parport.0.pin-02-out
setp parport.0.pin-02-out-reset 1
net xdir => parport.0.pin-03-out
net ystep => parport.0.pin-04-out
setp parport.0.pin-04-out-reset 1
net ydir => parport.0.pin-05-out
net zstep => parport.0.pin-06-out
setp parport.0.pin-06-out-reset 1
net zdir => parport.0.pin-07-out
net ystep => parport.0.pin-08-out
setp parport.0.pin-08-out-reset 1
net ydir => parport.0.pin-09-out
net spindle-cw => parport.0.pin-14-out
net spindle-pwm => parport.0.pin-16-out
net xenable => parport.0.pin-17-ou


So, ystep and ydir is repeated:
ystep goes to pins 04 and 08
ydir goes to pins 05 and 09

BUT no 'y0' or 'y1'

Then after that you started using y0step and y1step

net y0step <= stepgen.1.step
net y0dir <= stepgen.1.dirAND
net y1step <= stepgen.2.step
net y1dir <= stepgen.2.dir...