I will probably start another thread once the team has done a couple more tests, but I wanted to see if anyone else has run into this behavior that the team has experienced intermittently throughout the 2014 season (but not during the 2013 season as far as I recall):
When reading the autonomous script CSV file from the CRIO during autonomous mode, the CRIO CPU usage spikes up to nearly 100% and the first autonomous action is delayed approximately 3 seconds.
The programmers finally nailed down the issue and reproduced it by just having a VI that reads a CSV file* on the CRIO (but not doing anything with the results of reading the file) followed in a sequence structure by activating a pneumatic actuator. The actuator does not fire for about 3 seconds after autonomous mode starts. (* We have been using
Chris Hibner's VIs for autonomous scripting since the 2012 season.)
Like I said, I am just curious to know if anyone has seen this. I will gather more data and have the programmers put together a minimal robot project that reproduces the problem.
Thanks!