Go to Post What happens on your team is not everyone's business!!!! - Bruneau1727 [more]
Home
Go Back   Chief Delphi > Technical > Programming > NI LabVIEW
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #3   Spotlight this post!  
Unread 05-12-2010, 11:03
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,754
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: cRIO data logging

There probably isn't one pat answer or it would just be built in.

The simplest to use are the single icon blue functions. Easy, but probably not highest performance, and not as much control.

A step up from that is to open the file once, store the refnum or pass it through the looping element. Each iteration adds to the file with a write text or write binary, possibly flushing the file. The flush ensures that the underlying file manager actually writes the info it may be caching into the disk representation of the file and will ensure that a power outage or crash will not lose data. Outside of the loop, you can close the file and zero out any info you may have about the log.

If either of these simple approaches works, stick with it. If not, you may need to introduce your own caches or find ways to sneak the I/O writes in and have less impact on execution. You can keep info in arrays and write the info to a new file all at once. You can alternately put the file I/O into a background priority subVI and use queues or RT FIFOs to send data to the logger and allow the logging to proceed whenever it has enough info and CPU. I'm sure there are lots of other tricks that can be applied as well, but as usual, start simple and determine where that gets you.

Greg McKaskle
Reply With Quote
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Logging console data to text file on crio Kingofl337 Programming 3 09-04-2009 18:57
recieve data from cRIO byteit101 Programming 9 07-03-2009 16:37
Data delay between Crio and DS Tom Line NI LabVIEW 9 17-02-2009 08:40
Data logging to internal memory JBotAlan C/C++ 13 13-02-2009 00:04
pic: Team Data Logging Device falconmaster Extra Discussion 8 13-03-2007 10:01


All times are GMT -5. The time now is 21:37.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi