[phurley67]

At the Week 1 Standish-Sterling event we (862) had a very disturbing experience. Our robot while disabled and on the field decided to move. It did this 3 times after power cycles before we were disqualified for the match. We have now seen this behavior with 3 different motors including both PWM and CAN motor controllers -- so we are making the assumption that the issue lies with the RIO.

The problem seemed limited to immediately after a power cycle or when attaching either a USB or ethernet cable to to the RIO.

Given time constraints and an already rough start to our first outing we decided to try reformatting the RIO, which appears to have resolved the problem (we have not seen it since); however, we are a little nervous because this does not seem like the type problem that just reformatting should affect.

We have not done any low level coding or modification of the FPGA, WPIlib, etc. The code that was on the robot is labview code, that was put back on the robot after the reformat.

Wondering if anyone else had ever seen anything similar.

p.s. going into lunch after a very disappointing qualification outing, we were resigned to doing the swap, until a very gusty scouting job by our wonderful alliance partners 5488 and 6098 selected us (2nd from last in quals) and we managed to pull everything together and finish as finalists. Congratulations to 1918, 4377, 5166 look forward to playing with all of you later in the season.