Thanks for all the wonderful suggestions and comments.
Here's my list so far...
1) What are the Driver stations updates for? What do they do? SOLVED
Thanks to
byteit101
Quote:
|
Originally Posted by byteit101
They update the driver station software. you should have it if you passed inspection at the competitions.
|
2) What are the possible ways that trigger a "No Robot Code" error?
Quote:
|
Originally Posted by byteit101
There are many ways, but the two main ones are: no program on the robot, or undefined symbols (linker error)
|
Hmmm... Thanks, but what is a symbol? The linker wasn't able to successfully link the dynamic libraries correctly? (Incorrect correspondence between in-program link and the actual link library?)
3) I have installed NetConsole on my computer (with LabView Runtime) and enabled the "NetConsole.out" in "ni-rt.ini" via FTP. I rebooted the robot but it still doesn't work... (auto-connect or not) Has anyone have this problem before?
4) What is supposed to come up upon booting (of cRIO) on the NetConsole? SOLVED
Thanks to
Radical Pi
Quote:
|
Originally Posted by Radical Pi
NetConsole will show a nice long list of StartupLibs being initialized, talking about FRC_NetworkCommunication at the end, as well as other errors it may see (some important, some not), and some other small messages depending on what is in your code (camera errors come to mind. No consequence on the actual robot)
|
5) What does updating the cRIO image do? Would it help? SOLVED
Thanks to
Radical Pi
Quote:
|
Originally Posted by Radical Pi
If you update the image (even if you are at v20) it will do a complete reformat of the cRIO and wipe everything on it. That's probably a good idea right now since nothing seems to work. Be sure to remove any CAN libraries as they block updates
|
So apparently, this is my to-do list:
1) Check "No App" switch.
2) Reformat/reimage cRIO. (v20)
3) Run WindRiver updates.
(4.3)
4) Run driver station
updates.
5) Load new code. Hope it works!
Thank you guys, I learned a lot!
-Masoug