Problem with endstops and homing with Mesa 5i25

Hi,
I'am using linuxcnc with a Mesa 5i25 without a daughter card.
The mesa card is connected with a Universal interface II breakout board, see www.mechapro.de/shop/Misc-circuits/Unive...kout-board::226.html and www.mechapro.de/pdf/Univ-Interface-II_doku_2011_10.pdf for manual.
The Universal interface II breakout board is connected with the stepper drivers and endstops.

I can send all informations with the mesa card to control my steppers, but I'am not able to use my endstops.

While configuring with pncconf, I can define only a lot of pins and I'am not able to define every pin like I want.
I'm not able to integrate my endstops for homing. The signal are not useable in linuxcnc.

Is here someone who knows my problem or is able to help me?

What FPGA configuration are you using?

It may be that you:

1. Will have to edit the HAL/INI filea by hand
2. Will need a special configuration for that breakout board

What firmware are you using in pncconf?
How are you selecting your home switches?

A posting of your HAl file would help too.

Chris M

cmorley wrote:

What firmware are you using in pncconf?

I use r990x2 because of I have no daughter card

cmorley wrote:

How are you selecting your home switches?

Actually I don't use them for homing because I get no signal.
At first, I tried to use them as endstops.

This is the configuration with pncconf for the connectors.





I/O connector 3 is the parallel port of the mesa card with 25 pins.
You can see, that I'm not able to use every pin as I want.
For example, the universal board use PIN10 for X endstop. In pncconf I'm not able to use PIN10 for the endstop of x.

To test all of the I/Os pins from 10-15, I create Num 011 of I/O connector 3 for endstop of x axis.
Then I modify the HAL file to use the pins 10-15 too.
I connect all these to pyvcp hal pins for leds.
Without a result.

Is it possible you have pins and GPIO numbers mixed up?

(the 5i25_r990x2.pin file in 5i25.zip has the translation)

For example P3 pin 10 is GPIO13

So if you put a halmeter on hm2_5i25.0.gpio.013.in
you can monitor changes in P3 pin 10

PCW wrote:

Is it possible you have pins and GPIO numbers mixed up?

(the 5i25_r990x2.pin file in 5i25.zip has the translation)

For example P3 pin 10 is GPIO13

So if you put a halmeter on hm2_5i25.0.gpio.013.in
you can monitor changes in P3 pin 10

So, this was also my first idea.
And I checked the 5i25_r990x2.pin file. This is the content.

IO Connections for P3
Pin# I/O Pri. func Sec. func Chan Pin func Pin Dir

1 0 IOPort None
14 1 IOPort PWMGen 0 PWM (Out)
2 2 IOPort StepGen 0 Dir (Out)
15 3 IOPort None
3 4 IOPort StepGen 0 Step (Out)
16 5 IOPort PWMGen 0 Dir (Out)
4 6 IOPort StepGen 1 Dir (Out)
17 7 IOPort None
5 8 IOPort StepGen 1 Step (Out)
6 9 IOPort StepGen 2 Dir (Out)
7 10 IOPort StepGen 2 Step (Out)
8 11 IOPort StepGen 3 Dir (Out)
9 12 IOPort StepGen 3 Step (Out)
10 13 IOPort None
11 14 IOPort QCount 0 Quad-A (In)
12 15 IOPort QCount 0 Quad-B (In)
13 16 IOPort QCount 0 Quad-IDX (In)

I think this is ok. But if you compare this with the pncconfig, there are 2 pins called with num 0, why?
The free GPIO that I can use for my endstops are 11,12,14,15, right?
I have to call them in HAL with this number.

Physically, they are mapped to the following parallel port pin (PP-Pin):
GPIO 11 = PP-Pin 8
GPIO 12 = PP-Pin 9
GPIO 14 = PP-Pin 11
GPIO 15 = PP-Pin 12

But now, I use physically PP-Pin 10 for the endstop of x axis.
This pin is mapped to GPIO 13, so:
GPIO 13 = PP-Pin 10

But this pin is marked as none and not available in pncconf, like image 2 shows.
The other pins that I want to use are marked as QCount in the pin file.
Is this the problem? What is the meaning of QCount?
Is it reuired to change the status none and QCount in the file??

In pncconf I see, that GPIO 11 and GPIO 12 are free useable, but in the pin file they are reserved for axis 3. Can I use this pins, because I have only 3 axis instead of 4?

All pins can be used as inputs or outputs as long as they do not
interfere with secondary functions of the pins, that is if you disable all
stepgens,pwmgens, and encoder counters, all 17 pins per connector
can be used as input or output.

This is reflected in the pinout table that shows that all pins have I/O (GPIO)
as a primary function.

Pin 10 (GPIO13) says "none" in the secondary function field
because it has no secondary function so is _always_ available
as a input or output GPIO pin.