View Single Post
  #4   Spotlight this post!  
Unread 31-01-2010, 15:20
jhersh jhersh is offline
National Instruments
AKA: Joe Hershberger
FRC #2468 (Appreciate)
Team Role: Mentor
 
Join Date: May 2008
Rookie Year: 1997
Location: Austin, TX
Posts: 1,006
jhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond repute
Re: Data File Writing ... cRIO vs. Driver Station

Quote:
Originally Posted by Ziaholic View Post
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.
Given the fact that you are already sending it to the dashboard, I tend to agree that it's just easier to do it there.

Quote:
Originally Posted by Ziaholic View Post
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.
True, though presumably you could write more often if you did it on the cRIO assuming that was beneficial to you.

Quote:
Originally Posted by Ziaholic View Post
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?
c:\ is considered the root of the FTP server. The cRIO has 128MB disk on chip. My controller has about 100MB free after reimaging.

-Joe
Reply With Quote