PNCconf 7i92H and 7i76

The fact the mesaflash does not find the 7I76
(and the firmware seems correct) suggests
a hardware issue (either bad 7I92,7I76, or cable)

yes, thank you very much for your help so far. It's demoralizing to imagine after a little over a month that one or two new cards are defective. And now - throw it away? That just can't be true?

Did you verify that your cable is correct?

I had to assemble the cable myself because there was no such cable anywhere. So I was recommended the following parts.

www.reichelt.de/ch/de/flachbandkabel-awg...8-26g-3m-p47644.html
www.reichelt.de/ch/de/d-sub-stecker-25-p...?&trstct=pos_0&nbc=1
www.reichelt.de/ch/de/index.html?ACTION=...A=3&nbc=1&q=pfl%2026

I assembled it according to the instructions and until last Monday I was always a little worried about whether the poles of the cable were connected correctly. The two of us then ran the cable through with the multimeter and everything was ok so far. Since it is a 25-pin DSUB connector and a 26-pin cable, I suspect the cable

I'm currently studying the specifications of the DB25 and P2 26Pole connectors
What mistakes can be made during assembly?

Shorts, opens, off by one errors would be the most common

Do the 7I76 step/dir outputs work?

Yep,  cable 26 HDR end put on backwards.

Good catch tommylight.
 

Gentlemen, did you realise that from my photo on page 9?
I will check this and make a cable which is reversed.

dear Gentlemen, brilliant - it was the DB25-IDC26 cable, because now I have the 7i76 on the Halshow radar :o), your attention deserves a lot of praise.

Did I assemble the cable incorrectly, or is a special cable required for use with the Mesa cards? Isn't that what a parallel port printer cable is for other applications?

The machine brought an error because of the latency with 2000000.
I set the value to the original 1000000 and the error is gone.
The axes can be simulated and referenced.
But now I have an error again, but I can't figure out where it comes from?