Hello all,
Recently I have been seeing this error when my CompactDAQ chassis runs with 9233, 9263, and 9205 modules:
the Labview program crashes, and I get a message stating that an "Internal Software Error occurred in MIO software."
The system is acting as a controller, taking voltage measurements on the input, and generating voltage signals on the output. I have not seen this error occur when the program runs in the lab (yet?), where the equipment isn't conencted, but this crash occurs too frequently when in the field (perhaps once or twice in a day). It has been dealt with by shutting down Labview and restarting the program with a clean memory, or the computer may need a restart.
The 9233 and 9205 modules act as analog inputs, while the 9263 is generating voltage output. I'm sorry, but I cannot recall the exact error code at the moment - I'll be sure to, should this error happen again. The trouble is that this error has happened before: see, the chassis I presently have is a replacement to one that stopped communicating with the computer (one day, the chassis was switched on, and the system did not detect the hardware at all; it was working fine one day, and not working the next). Prior to the old chassis' malfunction, this error message was appearing on occasion. Now, I do not know why this "internal software error" occurs from time to time, but I would like to know if it's an indicator that the chassis or any of the modules are in need of repair, or if such an error can be resolved in the program.
Incidently, when I was trying to search for a solution for the old chassis' miscommunication with the computer, I believe I came across a similar situation. Through a Google search, I found some people were having problems with those USB hubs that split one USB port into four: USB 2.0 hubs sometimes stopped being detected. It turns out the solution in some of these cases was to uninstall the USB drivers, and the operating system would reinstall them again, and the hubs would work once more. I only mention this because I wonder if these errors stem from something occuring in the USB backplane?
If anyone has seen similar behaviour in the cDAQ chassis, or any modules, please offer up some advice. I anticipate that I'll be advised to send the hardware in for repairs, but considering that this is a 'new' chassis, then any insight into the situation would be welcomed.
Thank you,
Dan
