Stuck configuring 5i25 to run G540

I didn't want to post, but I've been scraping the internet for days trying to fix this.

Machine: XYYZ gantry with a G540 and steppers, no encoders
Linuxcnc: 2.9.0-pre0-135
Mesa 6i25 flashed with 5i25_g540x2.bit

Background: I ran this machine with a parallel card but ran out of IO quickly, upgrading to mesa now.
I have a parallel cable connected to P3 on the back of the 6i25, this cable works perfectly over parallel.

I flashed the above firmware to the 6i25, verified it and checked the pins with "mesaflash --device 5i25--readhmid", the pins look good.
I chose "5i25 Internal Data" then G540x2, then set up the axis the best I could tell how to.

I set up the estop and limit switches, both of which work correctly
After starting linuxcnc, if you jog the display changes, the values update, but the machine doesn't move.

The estop and switches working correctly leads me to believe it's not the 6i25 board or cable.
No errors are thrown in dmesg or from the linuxcnc console that I can see but I'll attach a snapshot of the startup and movement activity.

I'm attaching my HAL, INI, readhmid, and dmesg.







THANKS!!

UPDATES:

Chargepump switch is OFF

switched 6i25 W2 to the down position, confirmed all the other jumpers are in the mesa default locations.

Yes, the motors have detent, the drivers are on. Hitting the G540 ESTOP stops the drivers, estops linuxcnc and kills the detent.

Fixed having attached the hal and ini to this post with wrong filenames

Is the G540 chargepump enabled?

Nope, should it be? And are you referring to a software setting? The switch on the G540 is set to OFF, It wasn't on with the parallel card either.

The led on the G540 is green and the motor drivers are on FYI.

I have the ESTOP connected to the G540 and linuxcnc is detecting it from the G540's pin 15 via the 6i25 if that's helpful at all.

Are you connected to P3 (the DB25 connector and is W2 down?)
(W2 must be down for non-mesa daugterboards/breakouts)

I did not have the W2 jumper down, but I do now. All jumpers are in the default positions.

I tried jogging again with no luck

The ESTOP and limit switches still work though.
I added the limit switches to GPIO 13-16, but 16 isn't enabled in the bitfile for some reason, so it doesn't work.

GPIO16 is plain GPIO bit that connects to P3 DB25 pin 13
its always available in a G540x2 configuration
(since it has no alternate function in that configuration)

Are the motors energized? i.e. can you turn the shafts by hand or not?
Have you connected the step/dir signals correctly?

I notice you said you used 5i25x2 in pncconf which is not possible.
Did you mean G540x2? details like this can be very important.

Chris

PCW wrote:

GPIO16 is plain GPIO bit that connects to P3 DB25 pin 13
its always available in a G540x2 configuration
(since it has no alternate function in that configuration)

I do see that GPIO16 is connected to parallel pin 13, but it's the only switch not working. And if you check the halhmid dump I attached, it's the only GPIO OF 13-16 (DB 10-13) that says "None" and doesn't work. Does the "NONE" indicate that no function is set in that bitfile? It just seemed like an odd correlation.

Aciera wrote:

Are the motors energized? i.e. can you turn the shafts by hand or not?
Have you connected the step/dir signals correctly?

Yes, the motor drivers are on and they have detent. I'm not %100 sure I have the signals set up correctly, but I do have *an* axis on each Stepgen, so it should be moving even if the axis assignment is wrong. Right? I do have my Hal attached at the top.