Struggling To Program CRIO

[jasonpeinko]

Our team is currently getting any programing done to the CRIO in either LabView or wind river.

We setup the network system, and everything runs fine, and Wind river and LabView are able to download programs most of the time, except when the system freaks out and stops working.

We have tried default programs on both, and neither do anything. The victors that are attached to the sidecar just flash.

The DS is fine except the Battery reads No Comm.

[1jbinder]

Your first problem is that you are not getting any connectivity between the DS and the cRIO. The DS should display a voltage if you have communication. You should check the voltage of your main battery, also make sure that your analog module and bumper are attached. Have you tried going directly from the DS to the cRio? This might solve some communication problems. Just make sure the wheels are off the ground so the robot does not take off while the DS is connected.
Hope this helps,
Julian

[Cow Bell Solo]

We also somewhat had a similar problem, first if you just turned on the main breaker, what a bit to check if it still says "no comm" the cRIO has to startup. If it still says that check all of your connections, are you using the right ethernet cables in the right spots. If you get a voltage, and you get a voltage of "0" but you know that is not true(this was what was happening with us), we ended up needing to reimage the cRIO(especially since LabVIEW update 3). That is my two bits of advice. Also for next time if possible add some pictures, pictures help so we can see your wiring and other stuff instead of just having to make lots of random guesses.

[jasonpeinko]

Ill get some pictures tomorrow, did not think to take any before leaving.

We have tried tethering, but my guess is that the board is not wired up. The sidecar is the only thing plugged into the CRIO. The other modules are plugged into the CRIO but don't have cables going to them.

[chmp09]

As stated above, your CRIO is not connecting to your Driver Station. Make sure that your driver station and CRIO are on the same team number. The documentation for that is on the first site. If you changed the number on the driver station, that does not mean that you did so for the CRIO. To change the number for the CRIO, you have to flash it and check the format button, using the right team number.

[chmp09]

Originally Posted by Cow Bell Solo

We also somewhat had a similar problem, first if you just turned on the main breaker, what a bit to check if it still says "no comm" the cRIO has to startup. If it still says that check all of your connections, are you using the right ethernet cables in the right spots. If you get a voltage, and you get a voltage of "0" but you know that is not true(this was what was happening with us), we ended up needing to reimage the cRIO(especially since LabVIEW update 3). That is my two bits of advice. Also for next time if possible add some pictures, pictures help so we can see your wiring and other stuff instead of just having to make lots of random guesses.

To get the correct voltage on the DS, you need to use a jumper on the analog breakout on slot 1 of the CRIO. There are three pins on the right hand side of the cartridge. You need to use a jumper to connect the right two. This is required and will be checked at inspection.

[odel]

Hi i'mon the same team as jasonpeinko, everything is working now. Turns out out electronics didn't understand that the modules have to be in certain slots on the crio.