We have two cRIOs with the exact same hardware/software, but the imaging tool doesn’t see the 9403 module for one of them, and the driver station reports no communication. Pinging the robot does work. When we swap one for the other, everything works fine. (We have tried both CRIOs with exactly the same modules and wiring. One works, one doesn’t.)
Any help would be greatly appreciated.
Your best bet would be to contact NI to see if it can be replaced.
Are these 8-slots or 4-slots?
Consider opening the non-working cRIO and blowing out any accumulated foreign debris with compressed air.
This is especially applicable if this is an older cRIO without the gaskets installed. Dirt can get in the port openings, and cause strange things to happen.
Here are errors from the NetConsole, if it helps.
>>>>ERROR: status = -63194 (0xFFFF0926) ...in GetDIO() in C:/WindRiver/workspace/WPILib/DigitalModule.cpp at line 325
Too much error data!
>>>>ERROR: status = -63194 (0xFFFF0926) ...in SetRelayForward() in C:/WindRiver/workspace/WPILib/DigitalModule.cpp at line 168
You may want to repost this in the Programming forum, or PM one of the NI guys (like Greg).
Are the cRIO image and WPILib up to date? That error code (−63194) corresponds to “NiFpga_Status_VersionMismatch” on the following page:
http://zone.ni.com/reference/en-XX/help/372928D-01/capi/errors/
Hi everyone, sorry for the late response.
This is a new cRIO and it hasn’t been used until now. It’s 4 slots and has the latest image.
We’re going to try to contact NI to see if it can be replaced. Until then, does anyone else have other ideas?
It may be possible you have a bent pin. Do other modules show up?
Yes, all the modules show up as green in the imaging tool.
We found recently that there are “soft” switches in the imaging tools. I don’t know what that means but it was reported from one of our software guys after one of our Crios was taking a very long time to run a loop.