DEAD CRIO!!!!!

[screamingeagle]

HELP!!! Our CRIO has died!!! Working fine one second, power down and now our CRIO is not working. We have power going to it, but no response from the board. Any Ideas???? NI stated that they don't have any in stock...now what do we do??????

[joek]

did you press the e-stop button?

[basicxman]

Originally Posted by joek

did you press the e-stop button?

The E-Stop button's effect only works up until the point of power off. I would thoroughly test all connections between power, remove everything besides what's necessary.

I'm sure a veteran team could loan one if all else fails.

EDIT: Have you tried safe-mode?

[Tom Line]

Have you insured the battery you are using is charged?

[joek]

ask NI about it

[scottydoh]

I think it would help if you define "died" EDIT: ok you defined died

Do the lights come on?
Are the lights on and its just not responding?
Is it getting power/wired the right way? (The cRio runs on a special 24v circut)
Did someone hit the E-Stop/Is the E-Stop button plugged in?
Is the code "Enabled" on the driver station?
Did someone rub their feet on the carpet and zap it?


I'd say check that its getting power, and try re-imaging it.

[samir13k]

first of all,
i had a similair problem last year,
the Power distribution board (PDB) showed that the cRio was receiving the 24v it requires with the led light, so it looked alright... but it still didnt power up the cRio.

solution: make sure your battery has more than 12v available... i believe mine was registering about 9.9v when the cRio didnt start up.

the PDB's led's are helpful, but not 100% accurate. change your battery to a freshly charged one,

make sure all connections are good! if a positive wire touches your cRio case, it will be dead for good

[J_Beth]

We thought that ours had died the other day also. When we powered up, the lights on the Power distribution board came on, as did the lights on the Jaguar's, and the Wireless bridge. But the lights did not come on the CRio. As it turns out we just had a very low battery. Try replacing that and see if that works.

[screamingeagle]

Thanks to everyone for the replies. It was a battery problem....even though our distribution board stated that we had 12V coming through. We even metered the wires going into the CRIO and found voltage, I guess it just wasn't enough.

If you need answers...CHIEFDELPHI has them!!!!!!!! THANK YOU

[DtD]

Yeah, keep thoose batteries charged. Our programming team has been using the same battery since Kickoff for testing the cRIO and it finnally got too low yesterday (Yeah, it really lasted that long - no motors but still amazing) XD cRIO starts getting angry around 10.8 v.

~DtD

[Jon Stratis]

It can be a very good idea to put someone in charge of the batteries. Ensure that dead batteries are always being charged, that the robot has a fresh one when you get started each day, and that the batteries are changed out on a regular basis. The last thing you want to do is kill a battery only to find out none of the rest are charged, especially if it's getting near ship and you're trying to test the robot!

[joek]

and don't drive a slick-wheel robot on a springboard floor- we did that last year and fried 2 crio modules by way of static build up on our robot