No love on CRIO patch…
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).
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…
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!