NI-DAQmx 9188 configuration

[Tom_W_[DE]]

Hi toyan-

The lookup features that allow, for example, chassis to show up automatically in MAX (without having to search by IP or hostname) depend in some cases on the device being on the same subnet as the host.  This is a technology limitation and not a problem with NI's implementation.  However, if the chassis is on another subnet with a consistent IP address, it should be re-connectable without searching.  If the IP address changes, the last course of lookup that might succeed on a remote subnet is hostname lookup, but only if your network and DNS settings are configured to allow remote hostname lookups.  Many networks are not. 

In the case of a device on a remote subnet with a changing IP and whose hostname isn't resolvable, you will have to tell MAX (and, by extension, DAQmx) which IP address the device can then be found at.  There are limits to how crafty we can be in re-finding devices if they have no discernable way to be correlated to their previous network locations. 😉

I am not saying that you *need* to add a Self Test at the beginning of your application, because not all applications will require it.  But I am saying that I would recommend it and that I consider it a best practice in general.  Make sure you are Self Testing the chassis by name and not any of the modules.  Still, if the chassis isn't re-connectable for the reasons that I mentioned in the first part of my post, Self Test will fail because the driver won't be able to resolve the device by name, IP, etc.  But if it is re-connectable, Self Test will make an effort to re-connect to it and restore communication with the modules.