|
Re: Problems with cRIO and driving while competing
The Thursday logs show a frequent stream of errors coming from teleop trying to read a Digital Input refnum that doesn't exist. This caused the cRIO CPU to be pegged near 100%.
On Friday, that was resolved, and the errors were just timeouts on RobotDrive during auto.
The 5:30 log on Friday has a one second disabled gap during teleop, but it isn't clear what caused that. The comms were clean and CPU was low.
The three qualification matches on Saturday look clean.
Saturday afternoon around 2:00, there were some tests in the pits where the auto timeouts started happening again
I haven't had a chance to look at the code yet, but the logs do not show communications drops, cRIO CPU usage or errors to be the cause.
Greg McKaskle
|