02-13-2008 02:03 PM
02-14-2008 09:57 AM
02-14-2008 10:07 AM
02-14-2008 12:56 PM
Correct. The LabVIEW TCP/IP functions are not capable of duplicating or simulating a sniffer program.
@exo wrote:
I think I understand but let me restate.
First, I have two machines on a local net; One is a MAC running LabVIEW; The other which creates the files I'm interested in is running Linux (may not important) and not running LabVIEW.
I can send the file from the Linux machine to the MAC using ftp but you are telling that without Ethereal or something similar, I will not be able to use MAC LabVIEW to listen in on the file transfer.
I wasn't suggesting sending a TCP/IP signal. I was suggesting opening a regular TCP/IP connection when the file is ready. In fact, you can use the connection to send a command to the LabVIEW program by just sending character data like "GET FILE xxxxx", and then just close the connection. All you need on the LabVIEW side is a simple listener. There's an example that ships with LabVIEW that's a simple data client. I'm assuming, of course, that the C code on the Linux side is modifiable.
On the hand, you are telling me that I could send a TCP/IP signal to the MAC telling me that file is ready for transfer and I could pull it over from the MAC side.
Right? This sounds good.
Unfortunately, no, as I don't use Linux. However, I'm sure the 'net will be replete with examples, as this is a fairly straightforward operation.
Do you know where I get the Linux TCP/IP commands?
02-14-2008 03:40 PM