LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

The pathname, directory name, volume label, or filename is incorrect. ?????


Viewed 1 time


I am trying to send a file from my RTOS remote system to my Windows Host computer across the network. I keep getting this error. I have tried to build this pathname with backslashes, front slashes, double slashes, quotes, absolute path, relative path, IP address, machine name, and everything else I can think of. The "FTP Put File.vi" gives me this error no matter what I try. I can easily get and put files from the command line FTP on both of these machines. When I run my vi, I monitored the reply string and value I got from the "FTP Open Session.vi" and all looks normal. Does anyone out there know what the syntax that it is looking for should be?
 
C:\Inetpub\ftproot
C:/Inetpub/ftproot
c:\inetpub\ftproot
c:/inetpub/ftproot
C:\\Inetpub\\ftproot\\
C://Inetpub//ftproot//
ftp:\\192.168.1.91\Inetpub\ftproot
ftp:\\192.168.1.91\\
 
 
etc, etc, etc.....
0 Kudos
Message 1 of 3
(2,714 Views)
I like letting labview build the path.  That way I do not have to try to remember various path syntax for whichever OS the vi is running on.


Message Edited by jasonhill on 05-11-2006 12:39 PM

0 Kudos
Message 2 of 3
(2,708 Views)

Thanks Jason. You gave me the clue that finally got me on track. I tried your way and then experimneted some more. Eventually I got it to work the way I want. Two items.

1. The "Pathname" seemed to be a "red herring". The FTP Put File vi doesn't need the entire path. It was happy with " \ " as a path. The file was placed in C:\Inetpub\ftproot\ because that is the "root" directory of my ftp server on the host.

2. My problem was that I had forgotten to provide the "FILENAME" even though the help for this vi doesn't say anything about the filename. I mistakenly thought that the filename I specified on the local path input would simply be carried through and sent with the FTP transfer. As soon as I stripped the filename from the "local" input and concatenated it to the "remote" input, then the transfer went fine.

 

technomage

0 Kudos
Message 3 of 3
(2,694 Views)