Robot not Listening to Code (LabView)

[SamJr.]

Ok, so, yesterday, everything was working. Even Autonomous, more or less. This morning, we came back in to work, and the robot was simply unresponsive. Eventually, we succeeded in connecting, but the code seemed to be completely ignored. All throughout the day, we tried everything we could think of, including switching out the C-RIO. Symptoms include: flashing Talon lights, brief spurts of activity in the drive train before a return to silence (without any input from us), and random motion in other motors. Probing all of the lines in the code proved that there were no errors. Replacement of the C-RIO, most of the PWMs, and old code that we know works had little to no effect. We've never seen anything like this before. Any help, soon, would be greatly appreciated.

[ehochstein]

Ensure the cable going from the crio to the digital sidecar is fully plugged in. Are you seeing all of the lights on the digital sidecar turn on?

Also just to confirm, you can connect to your robot from the driver station right now?

[SamJr.]

The answer to all of you questions is yes. We have replaced ALL of the vital electronics. The driver station and everything works completely OK. There is no hints as to what the problem would be, tethered or wireless, computer or classmate, anything we try produces the same result.

[MathMaven]

Have you tried replacing your battery? It sounds like you've got an unusably low voltage, and you haven't said anything about your battery.

Alternatively, try making sure each cRIO module is in its proper place -- this will mess everything up.

[Greg McKaskle]

There is still a lot that you haven't said.

Were you running from a deployed and built app, or were you running from the run button? If you are running from code, you should be able to set breakpoints, probe, and determine if the code that is running is involved in the symptoms or if it is largely electrical issues.

You can also place the DS into test mode where your periodic code is still running, but neither auto or tele is called. You can click through the dashboard table and view if sensors are working and even drive the motors.

You also have lots of info on the charts tab. It tells you the robot battery voltage, the CPU usage. It tells you the errors coming front the code and it tells you when your robot is processing an auto or tele packet.

You may want to post some of these elements to aid in debugging things.

Greg McKskle

[Invictus3593]

...brief spurts of activity in the drive train before a return to silence ...

Do you get any repeating errors in your Diagnostics tab? Do you have any vision code running on your cRio?

This sounds like the lag our team gets sometimes. Check your DS Charts tab and look at the CPU usage of your cRio and the packets being lost. A lot of times, we get "brief spurts" whenever our CPU is pegged at 100%, which can be caused by anything from vision code to error messages.

[Elfonzo]

We aren't sure of the actual problem, but we did try a different computer and the code worked. We plan to re-install LabView on our original computer to see if things improve there for the next season. Thank you all for your input.
-the other 931 programmer

[killer_rabbit3]

We've had this happen to us before. our biggest two culprits were either low battery, or the cRIO CPU is slamming 100% use. both were pretty easy to deal with. see if the cRIO is being overloaded