A few times this year, there have been programming posts, that seemed to lead me to believe the timing loops on the roborio are far less consistent than they were on the cRIO.
At TORC we log data to a .csv file every 100 milliseconds. Attached are sample match log files from 2014 crio based, and 2015 roborio based.
The 2014 data is pulled from a timed tasks control loop with a 50ms metronome timer, the 2015 data is pulled from a timed task control loop with a 20ms metronome timer. Labview picture attached.
The data from this year is all over the place as compared with the cRIO data.
We controlled our elevator with a home brew pid, so the students would learn how to pid, and not use the labview provided pid, but as typically is done, we ignored the delta-t as the loop time was to be consistent.
Which it was consistent enough to not give us issues with control, just not nearly as consistent as the crio.
discuss...
EDIT:
2014 Avg = 49.9796 with STD = 0.21929
2015 AVG = 19.67855 with STD = 3.797736
__________________ The sooner we get behind schedule, the more time we have to catch up.
How we respect the rules of the game is a reflection of our character and integrity - win, lose, or draw - JaneYoung [more] 
Threaded Mode