View Single Post
  #7   Spotlight this post!  
Unread 20-12-2016, 20:21
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,748
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: Data Logging Through Driverstation

There are a number of good suggestions in this thread, but let me add a few points.

The OS and other utilities log things to the roboRIO flash all the time. A team is running with user privileges It should be pretty easy to look at your log file design, estimate usage, and determine whether a USB stick or RIO flash is the right approach. Also, if needed, you may want to disable buffering to on file open to better deal with power loss.

If you find that your CSV file is too large, binary files are often much smaller, typically a factor of five to ten.

Depending on the rate you want to log at, you may also want to consider network table logging. This logs the data at more like 10 Hz, but it automatically logs every variable update and it is built into the default DB. It is possible to build a custom DB and log faster if you wish.

I highly encourage you to log data, though. I love it when teams have data to understand what their robot is doing.

Greg McKaskle
Reply With Quote