Help 2013 Robot won't run

[IronBenderII]

How did this turn out? We are having the same symptoms as the OP. Our code worked 2 days ago and now we're getting an error that no robot code is running (but we have a green light on the DS for robot code).

Any help is greatly appreciated.

[Greg McKaskle]

The errors and warnings are timestamped. The message may be true at time t0 and then the code finishes loading and the LED comes on. Based on robot behavior, do you believe the code is running, or not?

Greg McKaskle

[IronBenderII]

Our programmer (Joe) says he believes the code is running. He probed a wire inside the main robot loop and he says non of the wires are executing.

[IronBenderII]

If you are willing/able, you could call me/my programmer @ 916-949-9626

[IronBenderII]

We just patched the CRIO, crossing our fingers and testing. Still not sure why this would pop up all the sudden...

[IronBenderII]

No love on CRIO patch...

[inkspell4]

Could you verify that the code is uploaded in a way such that the code runs on start-up (this option is available in the imaging tool)?

Try running the code instead of deploying it then enabling it from the driver station (connect using ethernet).

[IronBenderII]

Hi there. It does run on startup and we have been running it (not deploying it). At this point we are re-writing the code one function at a time and testing. Going to be a late night...

[mrscience21]

Hello from Team, 3859

After rewriting all of our robot code we discovered the original source of the problem was in our ADXL Accelerometer's interface to the I2C port on our Digital Sidecar. My guess is that the device was malfunctioned and was overloading the digital sidecar, forcing the C-RIO to stop interfacing with the software requesting the malfunctioning interface.

Hope This Helps anyone else out there!