Unable to Get CRIO to Work

[Alan Anderson]

How's your battery?

[celticsfan645]

We checked the battery with our voltmeter, and it was giving off about 10 volts. I am fairly certain that is enough power, but switching to a fully charged battery is probably worth trying.

[MamaSpoldi]

A 10 volt battery is really marginal... I would definitely change the battery. But I would also suggest trying to program the cRIO by directly connecting to it (ie. ethernet cable connected between laptop and cRIO port, eliminating the wireless completely). If this works then you can take a closer look at the communications components in the chain.

[celticsfan645]

OK, I tried changing the battery, and it was connected directly to the CRIO to start with, and it still isn't working. I tried pressing the reset button to see if it would allow me to connect after, but nothing happened.

All advice already given is greatly appreciated.

[MamaSpoldi]

So you were able to successfully re-image the cRIO but now are unable to deploy code to it? Is it a 4 or 8 slot cRIO? What language are you working in? Can you ping the cRIO IP address from a command prompt? Do you have the netconsole running? Does it display any messages when the cRIO is turned on?

[celticsfan645]

I used to be able to re-image the CRIO, but as of late yesterday, the imaging software stopped connecting to the CRIO. I am running an 8 slot CRIO with labview, and the command prompt is unable to ping the CRIO. And no, I do not have the netconsole running.

[Hugh Meyer]

Originally Posted by celticsfan645

OK, I tried changing the battery, and it was connected directly to the CRIO to start with, and it still isn't working. I tried pressing the reset button to see if it would allow me to connect after, but nothing happened.

All advice already given is greatly appreciated.

The battery should not be connected directly to the cRIO. It should be wired to the PDB. Please review the "Wiring the 2013 FRC Control System which can be found at this link.

http://wpilib.screenstepslive.com/s/...control-system

-Hugh

[celticsfan645]

Sorry, that post was very poorly worded. What I meant by that was that I put on a new battery, and that the computer was directly connected to the CRIO. The CRIO is not connected directly to the battery. I am sorry for any confusion that may have caused.

[MamaSpoldi]

Unfortunately, I can't help with the LabView stuff. However, if the cRIO imaging software can't access the cRIO then it might help to reformat it in safe mode. This thread (http://www.chiefdelphi.com/forums/sh...d.php?t=111923) has lots of info on how to get the imaging back up and running. In particular suggestions related to turning off all wireless networking and firewalls on the PC (including clicking on the Advanced button in the IPV4 properties to make sure you have only one IP address set) and using the crossover ethernet cable to connect.

If you don't find the info that works there, it was suggested to contact National Instruments support at ni.com/frc.

Good Luck. I'll try to check back later.

[MamaSpoldi]

Have you installed this update to the cRIO imaging tool?

http://joule.ni.com/nidu/cds/view/p/id/2262

According to the documentation it fixes a bug in it related to "Timeout error due to various network interface configurations".

Maybe it will help?

[toastnbacon]

Is the dashboard open on your computer? That caused us a lot of trouble earlier this year. I would try several different cables, just to be sure. And of course, don't forget to reset frequently!

[celticsfan645]

Ok everyone, I managed to get the CRIO to work. What I did was I turned the IP Reset button on, rebooted the CRIO, turned the IP reset button off again, rebooted again, and then used the NI MAX to set an IP address. After that, I just had to re-image the CRIO. Thanks to all of you for your help.