|
Re: [FRC Blog] Einstein Report Released
Quote:
Originally Posted by JB987
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...
|
Yes, I admit, I have not read carefully enough. Still, that's a shame IMHO. A deadlock anywhere is not good.
__________________
Do not say what can or cannot be done, but, instead, say what must be done for the task at hand must be accomplished.
|