View Single Post
  #1   Spotlight this post!  
Unread 28-04-2015, 16:28
tr6scott's Avatar
tr6scott tr6scott is offline
Um, I smell Motor!
AKA: Scott McBride
FRC #2137 (TORC)
Team Role: Mentor
 
Join Date: Dec 2007
Rookie Year: 2005
Location: Oxford, MI
Posts: 519
tr6scott has a reputation beyond reputetr6scott has a reputation beyond reputetr6scott has a reputation beyond reputetr6scott has a reputation beyond reputetr6scott has a reputation beyond reputetr6scott has a reputation beyond reputetr6scott has a reputation beyond reputetr6scott has a reputation beyond reputetr6scott has a reputation beyond reputetr6scott has a reputation beyond reputetr6scott has a reputation beyond repute
Re: Loop timing crio vs. roborio.

Quote:
Originally Posted by Ether View Post


One XLS says "Loop Time" and the other says "Lag Time".

Do they mean different things? How was each measured?


Both Measured the same way as the shown in the snipit. Just different programmers from different years did the log heading text.

Both loops used the "Wait for next multiple" labview timer.

I had noticed this behavior when we were doing beta testing, and have not dug into much further. But wait, I forgot I published our 2014 code as part of the beta program, and we did get the logger working in linux os before publishing...

So attached is our 2014 code running on the roborio.

Avg = 49.95124
STD = 0.7159

Just seems like the RT scheduler in the roborio, is not as preemptive in scheduling the loop, as repetitive as the cRIO was.
Attached Files
File Type: xls 2014 Code Running on Roborio-100002.xls (340.5 KB, 3 views)
__________________
The sooner we get behind schedule, the more time we have to catch up.