CRIO not working with Windriver

[dpeterson3]

All right. I am tired of this CRIO. It will not take code from Windriver. We just tried a sample project and it will not deploy. The DS says no code next to the battery. Tonight, we switched the CRIO from Windriver to Labview in the imaging tool, and we all of a sudden have battery power readings, motors running, and everything else. The problem is we want to code in C++.

Here is the error message we get sometimes. "can not connect to 10.11.78.2:21" We have tried this through the DS, with a crossover, and just over the network. Any ideas what might be wrong?

[Racer26]

...are you starting with one of the example projects?

If not, I suspect thats your problem.

[m3rc1l3ss]

Yes, it is one of the example projects, specifically "simple template" We are figuring it is probably something insanely obvious, but as of yet, our team has had no luck.

[charrisTTI]

1) Did your system pass benchtop test?
2) Did you successfully format (reimage) the cRIO and update driver station?
3) Did you select the development environment (C++ vs LabView) AFTER the reimage?
4) Can you ping the ip address of all elements of your "robot" network? cRIO, driver station, etc. from the PC?
5) Have you tried turning off the firewall in your PC?

[jtdowney]

Originally Posted by dpeterson3

All right. I am tired of this CRIO. It will not take code from Windriver. We just tried a sample project and it will not deploy. The DS says no code next to the battery. Tonight, we switched the CRIO from Windriver to Labview in the imaging tool, and we all of a sudden have battery power readings, motors running, and everything else. The problem is we want to code in C++.

Here is the error message we get sometimes. "can not connect to 10.11.78.2:21" We have tried this through the DS, with a crossover, and just over the network. Any ideas what might be wrong?

I am going to echo charrisTTI and say the problem sounds like you didn't tell it to switch environments. You have to use the FRC Imagining Tool to reflash the cRIO and tell it if you wan't to use LabView or C++.

[kyungjin]

Can you connect to your cRIO device? If you can connect, it should have a list of processes that are running on your device in the target pane. Having said that... If it says "No Code", I would go FIRST -> Download (after your cRIO is connected). After the file successfully transfers... Reboot your cRIO and your DSU and hopefully it will switch from No Comms to a battery voltage level.

[nickmagus]

I am going to echo charrisTTI and say the problem sounds like you didn't tell it to switch environments. You have to use the FRC Imagining Tool to reflash the cRIO and tell it if you wan't to use LabView or C++.

JTdowney is right. Its sounds as if you imaged your cRio to be LabView compatible. What you probably want to do is download the new cRio image update and make sure you select C++ in the cRio Imaging Tool.

[m3rc1l3ss]

The problem has been solved. I guess the first notation figured that the crio would automatically connect to the crio as I didn't see any notes about how to connect. (The button is nicely buried) Anyway thank you for all of the tips.


If anyone else has this problem there will be an icon in the bottom corner that says show as fast view. In that window make sure you right click on the "vxworks6x" and click connect. Subsequent connections seem to be automatic. Another note to teams having difficulty is if you get an error saying you cant connect plug in directly with a crossover cable, and if problems persist, turn off the computers wireless if it has wireless capability. (