xPC Target : problem with multiple NIC card

Hi,

I have 3 NIC on my xPC. One is an onboard NIC which is not supported by xPC, so I've gotten myself two other NIC cards:

Intel Gigabit CT desktop adapter 893647

I tried running a simple model on both cards separately, and it works fine. However, when I install both cards in the computer, I cannot run one of them. (That is, one of the cards will fail when I use the command 'xpctargetping'.)

I'm not sure if this helps: When I use the 'Ethernet Init' block in my model, I can build and connect to the xPC. But when I run it, the following error appears:

ERROR: EtherInit: EtherID 2: Open Error 779

This issue really got me stumped. Any ideas?

Thanks, YA

Additional: When both NICs are present, the xPC always displays Bus: 1, Slot: 0 regardless of which card I used to boot the system.

Answer 1

[Dag Christian]

I have the same problem, when trying to setup a second NIC for use with real-time UDP. Any solutions?

Answer 2

[Rajiv Ghosh-Roy]

Gigabit Ethernet is not supported for Real Time UDP or Raw Ethernet. If you are trying (and failing) to accomplish host-target communication, you may need to set the EthernetIndex.

Try executing

setxpcenv('EthernetIndex', '1')

Then rebuild the kernel and boot the new kernel and see if you can connect to it.

Answer 3

[Mirko Kunze]

I searched through the whole internet to find a network adapter, that has

1. gigabit ethernet
2. intel network boot client
3. xpc target compatibility (according to this list http://www.mathworks.com/products/xpctarget/supported-hardware/xPC_Target_Supported_Ethernet_Chipsets.pdf)
4. a PCI connection

-> Intel PRO 1000 MT

and buy two of them only to find that real time UDP does not work with them? Why not? And why is that not mentioned in the UDP real time block help? Will it be supported in future versions?

[Gijs van Oort]

It actually is mentioned: http://www.mathworks.nl/help/toolbox/xpc/io_ref/bss5rbr-2.html

Answer 4

[Gijs van Oort]

The link in my comment above seems to be broken. I tried to re-find the documentation page by hand, but I didn't succeed. I know that the page does exist, but the fact that it is hard to find (even if you know it's there) is not good. Could Mathworks make a link on the 'Network Configuration' page ( http://www.mathworks.nl/help/xpc/io_ref/network_configuration_rt_udp.html) to it? It seems that many people suffer from the problem of not knowing which network card to buy.

I directly emailed Gordon Weast a while ago, and his answer was (for Matlab 2012b):

> Dear Mister Weast,
> Could you tell me if the i8256x chipset is supported by the Real Time
> UDP blocks for xPC?

I need to know the PCI device ID that the board is set to.  That's how we look up the driver to use.  Use 'getxpcpci all' with the target booted and you'll be able to find the device ID of the board.  It is an Intel board and we support many of these Gigabit chips.  However, different system manufacturers put different device IDs on them.  I don't see any devices in the 8256x series though.

The device ID is more important than the name on the device.  If a given device is not on the list, that means we haven't had one to test with.

The list of supported device IDs is:

xpcIntelGbEDriverInfo SupportedDrivers [] = {
    {INTEL_GBE_82544GC_EI,           0x1008 }, /*82544EI copper*/
    {INTEL_GBE_82544GC_EI,           0x1009 }, /*82544EI fiber*/
    {INTEL_GBE_82544GC_EI,           0x100C }, /*82544GC*/
    {INTEL_GBE_82544GC_EI,           0x100D }, /*82544GC -*/
    {INTEL_GBE_82540EP_EM,           0x100E }, /*82540EM*/
    {INTEL_GBE_82545GM_EM,           0x100F }, /*82545EM copper*/
    {INTEL_GBE_82546GB_EB,           0x1010 }, /*82546EB copper*/
    {INTEL_GBE_82545GM_EM,           0x1011 }, /*82545EM fiber*/
    {INTEL_GBE_82546GB_EB,           0x1012 }, /*82546EB fiber*/
    {INTEL_GBE_82541xx,              0x1013 }, /*82541EI*/
    {INTEL_GBE_82540EP_EM,           0x1015 }, /*82540EM -*/
    {INTEL_GBE_82540EP_EM,           0x1016 }, /*82540EP -*/
    {INTEL_GBE_82540EP_EM,           0x1017 }, /*82540EP -*/
    {INTEL_GBE_82541xx,              0x1018 }, /*82541EI mobile -*/
    {INTEL_GBE_82547xx,              0x1019 }, /*82547EI -*/
    {INTEL_GBE_82541xx,              0x101A }, /*82547EI mobile -*/
    {INTEL_GBE_82546GB_EB,           0x101D }, /*82546EB quad copper -*/
    {INTEL_GBE_82540EP_EM,           0x101E }, /*82540EP */
    {INTEL_GBE_82545GM_EM,           0x1026 }, /*82545GM copper*/
    {INTEL_GBE_82545GM_EM,           0x1027 }, /*82545GM fiber*/
    {INTEL_GBE_82545GM_EM,           0x1028 }, /*82545GM serdes*/
    {INTEL_GBE_82547xx,              0x1075 }, /*82547GI  -*/
    {INTEL_GBE_82541xx,              0x1076 }, /*82541GI  -*/
    {INTEL_GBE_82541xx,              0x1077 }, /*82541GI mobile -*/
    {INTEL_GBE_82541xx,              0x1078 }, /*82541ER -*/
    {INTEL_GBE_82546GB_EB,           0x1079 }, /*82546GB copper*/
    {INTEL_GBE_82546GB_EB,           0x107A }, /*82546GB fiber*/
    {INTEL_GBE_82546GB_EB,           0x107B }, /*82546GB serdes*/
    {INTEL_GBE_82541xx,              0x107C }, /*82541GI/PI*/
    {INTEL_GBE_82571EB_82572EI,      0x107D }, /*82571GI*/
    {INTEL_GBE_82546GB_EB,           0x108A }, /*82546GB -*/
    {INTEL_GBE_82573E_82573V_82573L, 0x108B }, /*82573E -*/
    {INTEL_GBE_82546GB_EB,           0x1099 }, /*82546GB -*/
    {INTEL_GBE_82573E_82573V_82573L, 0x109A }  /*82573L*/
};

We ended up buying a 82541PI-based network card ( this one), which worked well.