|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#5
|
|||
|
|||
|
Re: cRIO data logging
Much of the VI you posted seems to deal with a file group with some naming scheme that increments.
The write to spreadsheet string actually opens and closes the file each time. That should be more effective and a bit more expensive than a flush on an open file. If it works, go with that. If it slows down your program too much, open it up to see how the lower level primitives are used. If you still decide to do the file group, you basically have to step through enough instances that you trust the logic. I try to avoid the file group or keep it simple, as I seem to make a mess for myself that I have to debug whenever I attempt such a thing. Greg McKaskle |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
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 |