References to connection ID

[DeepMind]

How can I refer to socket, that has been created with UDP Open VI, in my own DLL?
So far I have created sockets in own DLL, but it would be easier to handle errors, if I could use labviews UDP Open.

[THailey3]

Hi DeepMind!

I'm not sure exactly how to do this, but there are some other posts that might give you some insight. Search the forums for "shared memory dll". This will bring up a few posts about accessing shared memory from a dll. A good starter is probably: "Shared memory function call NEED HELP"

Hope this helps,

[Johnner]

I didn't get the sense that shared memory was related to the problem here. I think DeepMind is trying to pass the socket descriptor to a DLL after UDP Open has been called in LabVIEW.

My understanding is that LabVIEW provides the following utility VIs to return OS-specific socket descriptors associated with TCP or UDP Connection IDs in LabVIEW:

UDP Get Raw Net Object.vi
TCP Get Raw Net Object.vi

Both are available here:
[labview]\vi.lib\Utility\tcp.llb

I've never done socket programming outside of LabVIEW, but I'm interested whether this is the correct assessment of these VIs, and whether the values they provide actually work when passed to various Winsock functions.

--John

[DeepMind]

That is exactly what I am doing. Thanks.

I assume that it is impossible to get socket descriptor to LabView connection ID?

By the way, LabView help doesn't give any references to those vi:s declared in these llb files. How this kind of information can be found?