FRC Program State Frozen at Power-up

I want to document a problem I had when starting up the FRC and OI for the very first time, out of the box. This problem and the solution is documented on the IFI website, but so far I haven’t seen anyone mention it here. It looks like it’s happened to a few people already because IFI has added it to their FAQ.

Setting the system up for the first time, I was following the instructions in the FRC quick start guide, and was able to set the channel number on the OI and then power up the FRC no problem. However, when I hooked up the tether, nothing ended up happening (at this point the OI and FRC were supposed to start talking to each other through the tether and all kinds of LEDs were supposed to light up on each). I power cycled both the OI and FRC, and then the FRC’s Program State LED was yellow, indicating that it was ready to receive a new load through the serial port. Something was definitely wrong…the FRC was “stuck” waiting for a new load. I messed with it for a while and couldn’t get the FRC out of that frozen state where it was waiting for a new load after being power cycled.

To get the FRC out of this state, you have to hold PROG and RESET down at the same time, then release RESET, then release PROG once the battery LED goes solid green. Then hit RESET and you should be un-stuck.

See the IFI link above for more info…

Yes, this has been mentioned a couple of times already.



It certainly doesn’t hurt to say it again though as I imagine more teams will see this problem. I wish this were covered in the RC documentation, since most teams probably won’t find the answer there in the FAQ.

Whoops! Sorry for re-posting about this. I searched and searched on here but wasn’t able to see it documented. But like you said, I suppose the more it’s documented, the sooner teams who suffer from this will be able to find the solution. The IFI FAQ was pretty much my last-ditch try to find info on it before posting here to ask people about it.

By the way, this hasn’t happened to us again. I’ve tested repeated power-cycling and switching on the fly between tether and radio and I’ve never been able to re-produce this.

Hey, We have also run into this problem. Does anyone know what causes it so that we can avoid it?

We have run into the same problem, but the FAQ solution isn’t working. Can anyone help?