Quote:
Originally Posted by Russ Beavis
Did you build and deploy an application to the cRIO and set it to "run at startup"? If not, you'll need to reconnect to the cRIO via laptop or PC (through the DS-side router is fine) and download a new application.
Without build/deploy/"run at startup", the cRIO will always lose its code during a power cycle (hence the DS display of "no code").
|
No, I'm pretty sure it has an application on it just fine, and the Driver Station displays "no comms" not "no code".
Quote:
Originally Posted by Alan Anderson
Can you try connecting the ethernet cable from the computer to the other Driver Station ethernet port, and see if a ping succeeds? Maybe one (or both?) of the ports on the DS has fallen victim to a static electricity event.
Also, make sure the team number is set properly on the DS. I hate to suggest voodoo solutions, but it might be worth trying to set the team number again even if it shows correctly on the display.
|
Both ethernet ports are experiencing the same problem. The team number was set properly, and we tried changing it to a different number and changing it back. Thanks for trying to help, though.
Does anyone else have any other possible suggestions?