ftp via System Exec VI

[stefano_foglio]

Hi,

    I'm using the System Exec VI to tranfer via ftp files from an application running in WIN7 built with LV_8.2 to a RT PXI crate (controller 8108) with LV_2012 installed.

This application is used to transer .txt files from my pc to the controller.

It usually seems to work fine but sometimes I noticed at the end of the transfer that the files NIRT.INI, niwebserver.conf, persist.pal, phexec.exe, ph_exec_smp.exe are deleted from the root folder causing che system crash at first reboot.

Is someone aware of some bugs in this library that can lead to this phenomenon?

Thanks

[Bob_Schor]

A program that I "inherited" that ran LabVIEW RT 7.0 (heaven help us!) used to collect all of its data on the PXI (RT) side, then if the user Paused the program, it would FTP the data from the PXI to the Host where it would be saved to disk.  Talk about kludgey and risky (data were frequently "slightly mangled" when the Host or Remote crashed before the transfer took place.

When the system was (completely) rewritten in LabVIEW 2011 (and kept up-to-date, last used in 2014 with LabVIEW 2014), I did all communication between Host and Remote using Network Streams.  As data were collected on the PXI, they were Network-streamed to the PC, where they were streamed to disk.  No more pausing, no more waiting for disk I/O, it all happened "transparently" by utilizing those cycles "between the State Transitions" (we typically are saving 16-24 16-bit channels at 1000 Hz continuously for 30-60 minutes, plus a second "Event" channel that registers "point-in-time" Events (such as "User Pushed Button" or "DIO Line 5 went High"), saving a Cluster for each Event that includes a Millisecond clock time and Event Identifiers.

We have had very good results with this system.

Bob Schor