LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

FTP to fieldpoint works in development environment but not in deployed app?

I have developed a VI which employs FTP to upload data files created by another application
embedded on a FieldPoint, not altogether unlike the "Redundant Datalogger" example VI found
in the NI Developer Zone. Unlike that example, I am not employing DataSockets, Citadel
database functionality or any other DSC functionality which I know or suspect does not work
in a deployed application without the DSC Run-Time Engine.

This VI works fine when I run it in the LabVIEW Development System (Full + RT + DSC), but
when I deploy the VI as a standalone application FTP (at least) appears to quit working.
I don't have the specific error code -- my VI re-interprets FTP errors to a novice-
friendly "check the LAN connection and/or FieldPoint power" warning and I will have to
modify the code to extract better diagnostics. I will also not be able to probe further
until I can get back to the fieldpoint, which is happily running its little app in a little
one-room water plant in the mountains. Meanwhile, is there something more fundamental (and
obvious to the veterans) which I am overlooking?

This application employs DSC security features and I have deployed it bundled with the
associated DSC files per the DSC manual instructions. All of that is apparently working fine;
the stand-alone just won't FTP to the fieldpoint while the development copy will.

Bob Miller

P.S. This VI also employs TCP to continuously communicate control and status info with the
fieldpoint, but the VI gives up on the link when FTP fails and never tries to open the TCP
path.
Message 1 of 2
(2,903 Views)
I will answer my own query for any casual readers. I dragged my
notebook and my carcass up into the mountains last night to attempt
to diagnose the problem. One word answer:

Firewall.

The Symantec firewall on the PC had been configured to allow Labview
to access the network via TCP (which FTP is built on), but not an
application named "Water Plant Watchdog". Reconfiguring the firewall
(a two-minute job) fixed the problem.

NI embeds a lot of "Disable Windows firewall" messages in the LabVIEW
installer and/or documentation. This is an issue for a standalone PC
connected to a fieldpoint and a dial-up ISP. So the firewall (and the
LabVIEW application) must be managed to allow each other to do their
job. Fortunately Symantec (Norton)'s firewall seems flexible enough.

Bob
Message 2 of 2
(2,893 Views)