cDAQ-9184 modules missing after PC restart

[kingokingo]

Hi All

I have a cDAQ-9184 chassis with a few I/O modules. Everytime i restart the PC, the modules cannot be detected by the chassis.

The chassis is seen on the ethernet port without an issue, but the modules are not (see attachment 'After Restart.')

If I click 'Self test' on the chassis, it finds the modules and my software can then run without issue until the next restart (see attachment 'After Self test.')

Ive tried different ethernet cards, cat6 cables and putting fixed/DHCP ip addresses in without success.

Any ideas what this could be?

Best Regards

Oliver

[MiloB]

I have the same problem ...  Any ideas?

[JonasM]

Reserv the chassis either through MAX or programmatically through the DAQmx API before trying to do any configurations or measurements.

[MiloB]

What does it mean 'reserv'? How can I do it? Can you explain please?

[JonasM]

Sorry for misspelling. Reserve of course. See the image below for best explanation. Make sure to highlight your cDAQ chassis then you will have the manual option to make a reserve for the chassis. When doing so the modules should autopopulate again. You can as I said also do this with the daqmx API.

[JonasM]

If it is reserved, try unreserve and then reserve again.

[BauerL]

I got same problem. However when the chasiss is detected but modules are not detected, the chassis is already reserved. So I kind of doubt un-reserve then reserve again will permanently make the chassis not 'lose" the modules again.

[kingokingo]

After a while of trying and testing, the only true solution (worked for the last few months) was to programmatically reset the cdaq chassis on startup of the software.

Annoying, but nothing else seems to work.

[BauerL]

Look through posts on this topic, looks like a "self-test" shall also work? I think Self-test is much faster than Reset-device?

[JonasM]

As this is an Ethernet chassis that requires reservation and drops of TCP coms can cause modules to not apear in the chassis. Therefore are the best practices to do a unreserv->reserv in beginning of program and unreserv in the end. Yes this takes startup a bit longer but the system will be much more robust.

Things that can help but not always what I've seen;

1. Self-test will most of the times get all modules back

2. Reset will also most of the times get all modules back

3. Unreserv and reserv again will most definitely work.