Hi!
My LV software runs kind of stand-alone, and should be able to re-connect to devices if the connection to them is lost.
This works fine for many devices, but I have some trouble with cDAQ crates.
Here's a screenshot from MAX, showing a cDAQ crate with an 9860 XNET module and a single XNET LIN interface connected. Hence, the second interface is marked red, which is totally OK:

The 9860 itself is marked red because I removed the network cable. It's already connected again, I can run a self-test on the cDAQ or release and reserve it.
After, the 9860 is not red any more, my software can re-create its LIN sessions and start communicating.
Now, I do know how to run a self test or reserve the cDAQ programmatically, but I have not idea how to determine that this is necessary.
I played around with properties of the LIN interface itself, but I found nothing reliable. I needed a running session at least, but this will not always be the case in my software. Furthermore, my cDAQ might also contain DAQmx modules (mostly digital/analog IO cards), which would require their own detection mechanisms.
I also played with the DAQmx system VIs, and can gather lots of information about the devices, but nothing indicating the current state.
So, how can I get that?