02-22-2008 09:43 PM
02-25-2008 11:29 AM
Datasocket can span either a network or the internet, to allow for communication within the same building or halfway around the world. The general URL format for this protocol is dstp://ServerName/Numeric. ServerName is the computer where the DataSocket Server is currently running and Numeric is an arbitrary name for the memory whereat the published data is located. You can also find the URL by running the DataSocket Select URL.vi, found in the DataSocket pallette. This will allow you to browse for your URL.
When using the DataSocket read and write VIs, make sure to pass the Connection ID (teal wire) from the DataSocket Open VI into the Connection In input, rather than the URL. I would suggest looking at some of our basic DataSocket Examples, found in the NI Example Finder under Help. Within the example finder, try doing a search for DS Reader and DS Writer. I would also suggest taking a look at the article linked below on using DataSocket. Hope this helps, thanks!
02-25-2008 02:08 PM
Thanks for your response!
I think I see where my problem lies and it brings me to my next question. How do I put the datasocket server on the internet or somewhere that is equally accessible for both publishers and subscribers? I think that is the root of my problem because originally when I would run the DataSocket server it would be on my machine which is inaccessible to those outside of my network. How can I put the server on the internet so I can write information to it and the data be read by those outside of my network?
02-25-2008 03:19 PM
02-25-2008 03:44 PM
I originally tried something like that using my personal desktop and relaying information to a remote desktop on a distant network. I first used the URL format
dstp://'server name'/'data tag'
And the error out on the client side was Error 42: General Error. So if instead of using the 'server name' I provided my IP to the client, it should work? Also, during testing I had gone into my OS services (services.msc) and manually turned off my firewall and instructed the client to do the same. Is there something I'm missing that could be stopping the data transfer other than using the IP instead of the server name? Thanks again!
02-25-2008 04:14 PM
02-26-2008 07:34 PM
02-28-2008 03:17 PM
02-29-2008 12:47 PM
03-03-2008 06:21 PM