Welcome to LinuxCNC.org

Chris,

Apologies...

The file was compressed into a RAR format and relabeled as .ZIP to comply with the file extension filter.

This is a more complete drawing

EDIT: still too large

Updated schematic diagram ( atium DXp 2004 version available) This attachment is hidden for guests. Please log in or register to see it.


EDIT:

Ought we move this to a separatetopic?

ya we prob should... I have most of a config built. I don't use mm often ans so a few bugs showed up..working through them

how about a actuall map out of the physical pins on which daughter board to be connected. as in ok my spindle pmw that i configured in the mesa tabs will be say pin 1, and 2 on the 7i48 p2 connector. does that make sence

Can't be done very easy as every configuration used creates different pins for GPIO depends on how many of each component is used.

John

I would like to request support for the 5i25 card (17 IO per port). I am willing to assist with debug and am somewhat familiar with Python.

Thanks.

5i25 is likely to be a bit of a special case, as the pin behaviour is different depending on the installed firmware (which is not PC-side downloadable like it is on the other cards)

Well actually the 5I25 firmware is PC side downloadable but not from
linux (yet) and currently requires a system power cycle to load the FPGA
with the (new) firmware in the EEPROM

Because loading new 5I25 firmware re-writes the EEPROM on the 5I25,
which has limited write cycle life, its not appropriate to reload it every EMC
startup like our other FPGA cards, but only when it needs to be changed

I understand the issues with loading the firmware on startup but it looks like there is driver level support for the 5i25 in 2.5 now. I assume that the driver does not try to load the firmware at this time. I will try it out tonight and see how far I get

In PnCConf, you would need to select the correct firmware that you have on your card instead of the firmware to upload. I don't think this would be a major issue and only need documentation. From what I have read, I think the pin behavior is the same as the other HostMot2 based cards after firmware load.

The main issue I see in getting it to work with PnCConf is the different number of pins per port. Is it possible to have the missing pins there as virtual dummy pins with reserved functions? That way the UI could stay the same while allowing the lower pin count.

ZincBoy wrote:I have one plugged in now, and it mainly works.