Error code 200020 after self-test when chassis turned off

[Djaunl]

Hi,

This may seem silly, but I accidentally ran a self-test in MAX on one of the NI PXI boards (6533) in my chassis (NI 1042Q) when the chassis power was off. It returned with an error code of 200020. The same happened with the three other NI PXI boards: 6723, 6713, and 6221. I turned the chassis on and the same error code occurred. Then, I restarted my computer, loaded up MAX,  and none of the devices were even recognized anymore.

I followed the steps here to reset MAX, and the devices were recognized again and all the self-tests were passed again. 

I am however concerned as to why this happened. Why did the error code keep occurring after I powered on the chassis? Why did MAX cease recognizing my devices? Did something get messed up when I tried to communicate to a turned-off device? Also, what does error code 200020 mean? I couldn't find documentation on it anywhere. 

Thanks

Message Edited by Djaunl on 05-27-2009 09:26 AM

[Djaunl]

Quick update: I just tested turning the chassis power off and then on again while my computer is turned on. I closed MAX, turned chassis off, then turned it on. When reloading MAX, the self-tests all fail and give the error code 200020. I'm very confused.

If it helps, I'm using NI PXI-8360 MXI-E board to communicate between the chassis and the PC. 

[Justin_E · Accepted solution]

Hey,

From your description, it seems like you are turning the chassis off when the PC is still on. This will definitely cause some issues with your PXI devices, as you are essentially hot-swapping the PXI devices in your system. This may have also messed some things up in MAX as well, like you saw. You should always have your PXI chassis powered on before your computer boots, and powered off after your computer has been shut down. This allows your BIOS to correctly enumerate the PXI card, which should hopefully avoid these errors in the future. 

[Djaunl]

Geez I feel silly right now. What you described was definitely the problem. Thanks a lot for the reply; I still have a lot to learn!

[Justin_E]

No problem, glad to hear that this fixed the error!