Get XNET slot and chassis

[KaBooOoom]

Hi!

I'm trying to use XNET cards (LIN and CAN). Since now, i was able to get  the Slot and the chassis number of all cards using VISA function. It seems The XNET cards are not visible with VISA. In MAX,  when i select the chassis, i can't see my XNET boards (even when i select the option "show all devices accessible to VISA and i reboot the RT).

My questions are the following:

1) Is is normal the XNET cards are not visible with VISA (i have VISA 4.4).

2) How can i retrieve the chassis number and the slot number ..?

Thanks for your futures answers.

[mdelsol]

I want to know the chassis (Product Type) where my XNET device is attached. If DAQmx is used I get that information but not the XNET device associated and using XNET I don't se how to get the chassis.

I use different cDAQ chassis.

Does any one know an easy way to get that information?

Thanks in advance.

[mdelsol]

No one can help? it's possible to do it or not?

[BertramD]

Hello!

Had same problems (getting chassis and and slot number in xnet c api) and here is my solution/workaround for a NI-9862 located in a cDAQ-9188 chassis:

If you have a NI-9862 CAN Module, you can start a DummySession; eg:

    -DatabaseName: NIXNET_example
    -ClusterName: CAN_Cluster
    -Interface: CAN1
    -List: CANEventSignal1
    -Mode: nxMode_SignalInSinglePoint
For this DummySession, you get a session reference: SessionRef

With this session reference you can get the source terminal start trigger property: nxPropSession_IntfSrcTermStartTrigger

This property is a string (Data Type DAQmx terminal) and the string reads eg: /cDAQ9188-XXXXXXX/Slot3/Convert

By simply parsing this string you get chassis name (cDAQ9188-XXXXXXX) and slot number (Slot3)

Chassis name is same as chassis name in NI-MAX, so my personal choice is to never rename chassis in NI-MAX. If you add a ethernet chassis, just use the automatically assigned name and you never get problems with parsing the chassis serial number etc...

Hope, this helps for all of you...

Kind regards, Bertram Dumböck

[Sebastian.Weber]

Hi!

I use this to find all hardware connected to the system:

I have a cDAQ-9185 crate with given IP, which provides a link.

There are two NI9201 modules which connect to that link in slots 1 and 2.

And there is a USB LIN interface with two ports, which are listed in the Alias as LIN1,LIN2.

On some systems, I use X-NET LIN interface module in the craft. Those modules appear like the NI 9201 here, and their alias is LINx,LINy, since they have two LIN ports

From the snippet, you can see there is even more information, but since not every device has every proberty, you have to ignore errors inside property node (red ?!) and wire a clear errors.

(And yes, the X-Net cards are somehow special)