listening on open ports

[exo]

My network utility (MAC) tells me I have open ports but LabVIEW won't let me listen to them.
What's going on?

[smercurio_fc]

You really need to learn to provide more details in your questions if you want to get accurate help as opposed to shot in the dark guesses. Like, the code, or perhaps the error that you're getting.

[exo]

I can't begin to tell you how frustrated I am.
And you're right about my posts. Sorry. Different, more to the point question:
Shouldn't the attached vi open a data socket. It keeps crashing LabVIEW. Once I get iy to work, what port to I tell the software on 198.202.125.164 to use for the data socket.

Thanks

[exo]

Sorry left off the dstp://
Now I get a serial port buffer overflow error.

[exo]

actually it may have failed because:
buffer overflow
connection refused

[smercurio_fc]

Unfortunately, I don't have LabVIEW 8.5 so I can't look at the VI. I'm sure others can look at it, or you can post a screenshot.

As an aside, I'm a tad confused. I'm assuming this is a continuation of this earlier thread, though you may be working on a different problem. You also said your network utility listed open ports. I'm assuming you're referring to TCP/IP ports. If that's the case, why are you trying to use the data socket VIs as opposed to the TCP/IP VIs? Do you have 2 LabVIEW applications trying to talk to each other? 'Cause that's the intended use for the DataSocket VIs.

[exo]

I have a computer that acquires images, processes them and sends them to my MAC. I would like to know when this happens cleanly. i.e. Not looking for extra files in a directory. I want to do it directly over my local net. The tools at my disposal are LabVIEW on the MAC and whatever is normally found on a Linux machine using REDHAT. I now have a program on the LINUX which in principle is send a signal out on a data socket of my choosing. I can also ftp to the MAC.

Thanks for your time and patience.
Doug

[exo]

Was able to save in 7.1

[smercurio_fc]

I think you may have misinterpreted the term "data socket" as used on the Linux side. There's a difference between "data socket" and "Data Socket". The former is a generic term, the latter is something that's specific to LabVIEW.  Unless you have a Data Socket server running you're not going to get very far. You said "I now have a program on the LINUX which in principle is send a signal out on a data socket of my choosing." Did you write this program, or did you get it someplace else? Do you have the source code? My suspicion is that the Linux side is simply using a standard TCP/IP open connection method. For this you just need to use the TCP/IP functions on the LabVIEW/Mac side.

[exo]

The code is at work; I could get it to you sometime Monday. However, your comment about TCP goes back to my original terse post.  The c code on my Linux machine needs a port number; for some numbers it runs and supposely sends a message to my MAC; For other port numbers, it says connection refused. On the LabVIEW side, it will only allow certain IP/port combinations.  So I got smart. I put the TCP/IP in a loop varying the port number until I got a valid port number. Then I put that port number into my C code on the Linux machine. Then I couldn't make the connection. I'm pretty sure that the port number the code wanted was on the MAC side. Was that wrong? Whatelse could be wrong?

Thanks
Doug