cDAQ 91X8 windows startup detection issues

[JoePerkins]

Hi guys,

we have a pretty huge and complex vi to adquire data from various cDAQ modules connected to cDAQ-9178 and cDAQ-9188 and we need to execute it when Windows 7 starts, so there is a shortcut in the startup folder.

We have the executable installed in many systems (some of them 9178 and some others 9188, just one chassis each system) with the same modules but different motherboards, and we try to wait for the chassis to be ready with functions from the System Configuration Palette. Since each motherboard is different, a simple wait doesn't work, we don't want the system to wait 5 minutes .

This usually works, but sometimes it doesn't, and we don't understand why. Any ideas to do this in a better, bullet-proof way?

Thanks!

[ErinaceousAgnomen]

If you know your setup, you can use the Device property node to detect what chassis and modules are in your system. This can reveal both their names and products, so it can be used even if you don't know the names of your devices. You can use a while loop at the beginning of your VI that waits for your setup to appear on the system so that the VI does not execute until all devices are ready.

I hope this helps,

Joshua

[JoePerkins]

Sure, but you get that information if the chasis has been previously connected; so, if you turn on the computer you will almost immediately get that info, but the chasis would not be ready yet.

There is maybe some window process or service that could assure the chasis is detected and ready to work?

Thanks again!