I'm trying to write an embedded LabVIEW program to do control and datalogging on a compact FieldPoint 2020 controller with a flash card. The program works perfectly, so long as I only try to write data to either the internal nonvolatile memory or the flash card, but if I do anything with both, the entire controller freezes--the program is clearly not operating, and the 2020 will not respond to any network requests, including FTP and FieldPoint Explorer.
Specifically, what I'm trying to do is read from a preference file stored on the built-in memory, drive "C" (using the preference vis) at startup, then check the free space on the flash card, drive "D", and if there's enough, open a file
and begin writing data to it. The program never gets past the free space check, however, before locking up the cFP controller.
Ideally, the program would also use the internal storage as a fallback if the flash card fills up, which is the main reason I'd like to be able to write different files to different locations.
If I target both operations at either the C: or 😧 drives, the program works fine, and creates the appropriate files.
Finally, if I target directly to the cFP controller, rather than embedding an auto-start application on it, and run a similar version of the program successfully, the suspect program will apparently run properly, which is even more confusing to me.
Doing everything on the flash card is a workaround solution, but at the very least I'm wondering if I'm doing something wrong, or misunderstanding cFP file I/O. I've so far been unable to get a simplified test case to fail completely, so I don't have an example to offer.
I'm running LabVIEW 6.1
with the 6.1 RT module, and ver 3.0.2 of the fieldpoint software.
