|
Re: It's about time I ask for help... How do you know if your cRio is fried?
Your original GSR issue sounds like the code failed to build, so the FRC_Communications library will load the backup code on the cRIO. When you download new code, the old stuff is kept and renamed, not deleted. This doesn't mean anything is wrong with the cRIO, but with the code or the way it was built.
My suggestion would be to open default code, framework template code, or even example code. If it matches the wiring of the robot and doesn't run, then it is likely a HW problem. If it runs and your code doesn't, then that gives you something to focus on and may hint more to a code or isolated HW issue.
The cRIO is a modular system. This makes it possible to change out one breakout, one I/O module, or even to move things to another slot if a pin is bent.
At this point I have almost no description as to what has been tried and what works and what doesn't. If you want us to help diagnose and correct the system, you need to give us accurate descriptions of how the system behaves.
Greg McKaskle
|