Holding of program

[chinckley]

Our code is not keeping loaded on the machine. We have had it work and then we come in again and it needs to be downloaded again. The blue box on the driver station says "No COMMS" or "NO CODE". The 2 jaguars are blinking green and we have lights on the Lynksis. Any ideas? I hope I have described it well enough.

Also one team member wanted to know if we are suppose to have a backup battery pack like previous years. If not, what replaced it?

Robot runs fine if we use the wires connected to the battery, without using the driver station at all. If that helps anyone with helping us.

[Alan Anderson]

Originally Posted by chinckley

Our code is not keeping loaded on the machine. We have had it work and then we come in again and it needs to be downloaded again.

How are you downloading it? The procedure for deploying an application to run on startup differs for LabVIEW and WindRiver environments; which are you using?

The 2 jaguars are blinking green...

Check again. If they're really blinking green with the Driver Station saying "No Code" or "No Comms", something is seriously wrong.

Also one team member wanted to know if we are suppose to have a backup battery pack like previous years. If not, what replaced it?

The Power Distribution board has voltage boost supplies to run the cRIO and the wireless adapter.

Robot runs fine if we use the wires connected to the battery, without using the driver station at all. If that helps anyone with helping us.

I'm obviously not understanding you properly, because I can't think of any way for a robot to "run fine" with no Driver Station connected.

[nathanww]

Perhaps they mean that the system runs when they hook up the motors directly to power? Some clarification is needed.

And yeah, NOTHING should be running on the robot with a "No comms" o "No code" error--you should check that your DS is updated correctly.

[chinckley]

Originally Posted by Alan Anderson

How are you downloading it? The procedure for deploying an application to run on startup differs for LabVIEW and WindRiver environments; which are you using? LABVIEW. Although what we are running is still the default code for driving forwards and back. Nothing else has been loaded, I believe.


Check again. If they're really blinking green with the Driver Station saying "No Code" or "No Comms", something is seriously wrong. They are blinking yellow, not green. Sorry for saying they were green.

The Power Distribution board has voltage boost supplies to run the cRIO and the wireless adapter.


I'm obviously not understanding you properly, because I can't think of any way for a robot to "run fine" with no Driver Station connected.

They hooked jumpers (aligator clips) to the battery to make sure the problem was not an electrical or motor problem and the chains moved and the dumper worked. Each was tested separately. Obviously, the joysticks and driving were not tested. So we are infering that the problem has to do with the communications between the driver station and the CRio - assuming it is a programming download issue. However, the only code we are running is the Labview default code that I was lead to understand came on the CRIO. How would that code disappear when the robot was turned off?


What does Nathanww mean by DS? We installed Update 3.0a.


Thanks so much for answering. We are getting nervous that there is something really wrong with something. No idea what though.

Carolyn

[chinckley]

We got it today. Thanks for pointing us to the FRC Framework we found on page 13 of 17 the directions for downloading to the cRIO and having it stay on startup. They must have been downloading it using the Run button or from startup, not the way that saves the code. We powered down and up a few times and it worked and kept the code.

Thanks to everyone.

Carolyn