View Single Post
  #8   Spotlight this post!  
Unread 04-01-2013, 12:39
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: best practices for logging sensors?

The code used to make the measurement is shown in the attached screenshot.

I'd honestly expect that you will log closer to .1kB per 20ms, meaning that the whole match is hardly any data at all. That means that you can pretty easily append it to an array in a subVI or you can use the disk I/O. I didn't test enough to understand the 60ms, but I've seen it before on other controllers when flash pages had to be flushed. If it happened once a second, it would affect the robot, but if it happens once in a match, I would think that is a reasonable tradeoff. I'm eager to hear what you discover and which approach you decide to use.

Greg McKaskle
Attached Thumbnails
Click image for larger version

Name:	Clipboard 1.png
Views:	34
Size:	110.4 KB
ID:	13381  
Reply With Quote