View Single Post
  #3   Spotlight this post!  
Unread 30-01-2010, 10:05
Ziaholic's Avatar
Ziaholic Ziaholic is offline
Elec/SW Mentor
AKA: Marc
FRC #1164 (Project NEO)
Team Role: Mentor
 
Join Date: Jan 2008
Rookie Year: 2002
Location: Las Cruces, NM
Posts: 194
Ziaholic is a jewel in the roughZiaholic is a jewel in the roughZiaholic is a jewel in the roughZiaholic is a jewel in the rough
Re: Data File Writing ... cRIO vs. Driver Station

Good advice. Saturday is an all day session w/ the team and we'll look at the examples ...

... but looking at the bigger picture ... what are the pros & cons of writing the file onto the cRIO vs. writing it onto the driver station? I've got a few ideas, but still appreciate advice from the folks that have already done this a lot.

Keep in mind that my data is simple columns of speeds, encoder values, accel values, etc. Some of my assumptions may be bogus if dealing with images or other sorts of data.

If the data is already available at both locations, then it'd probably be more "convenient" to be able to get the file copied off of the DS vs the extra file transfer from the cRIO.

I don't think resolution is a factor. Right? Putting the file-write into the teleop.vi, getting called at 50 Hz would result in the same rate as a driver station write ... giving me equal results.

The "saveImageFile.vi" example uses a target path of "c:\images" ... does the cRIO filesystem emulate a DOS-like filespace? How much filespace is there available on the cRIO to write to anyway?

I'm off to the team meeting ... looking forward to our results, and then coming back here to discuss.
__________________
----
There are 10 types of people. Those who understand binary, and those that do not.
Team #1164 - Project NEO Robotics

Last edited by Ziaholic : 30-01-2010 at 10:06. Reason: fixed typo
Reply With Quote