Quote:
Originally Posted by davidthefat
ಠ_ಠ So, asides from the intentional foul play, it seems as if their was a lot of errors on the teams themselves. Seems like 987's problem was that there was a deadlock with their software. So, that's a shame.
|
David,
If you read the full report carefully and pay close attention to the following:
987 – While testing of this robot revealed programming issues that could cause higher than normal trip
times, or the cRIO controller user code to lock up,
none of these issues were found to cause a command response failure. Which was the cause of our "dead" time on the field). The duration of these losses were too short to be attributed to a cRIO or robot radio
reboot, but
fit well with the symptoms of failed client authentication.
You will see that we too were likely victims of the intentional"failed client authorization" debacle...