DataSocket Steptypes in NI code library

[Sunny]

Hi,

I found this example in the code library but it theems not to work. I tried to use DataSocket Write with the following syntax URL:"telnet:\\ip-adress:port\"

Questions:
Has anyone used these Stetypes?

Regards,
Sunny

[Elaine_R.]

Hello Sunny -

The TestStand steptypes in that example are meant to funnel any DataSocket URL supported by the environment. As far as I am aware, "telnet" is not one of them. I think perhaps you meant to use "ftp:"?

For more information about DataSockets, you may want to check out the discussion "What URL does DataSocket Use?" for basic handling. Or ask the LabVIEW forums for additional assistance.

--Regards
Elaine R.
National Instruments
http://www.ni.com/ask

[Sunny]

Hi Elaine,

My goal is to implement Steptypes in TestStand for transfering XML-Strings to a Server realized with LabVIEW. If i use telnet and hyperterminal there is no problem to contact this server and transfer data to it.
My conclusion is that the problem can not be the implementation of DataSocket in LabVIEW but the realization of the dll in this example.

I wonder how these two steptypes can be used and why there are no Steptypes to open and close a connection?

Regards,
Sunny

[SachaE]

Hi Sunny,
transfering the data useing LabVIEW is not going to be a problem. Useing telnet as part of the datasocket specifier is though - it's not supported as far as I'm aware. (Check out the Datasocket help for supported formats).
I would suggest that you use internet toolkit for LabVIEW to get the Telnet capability, and create some custom step types to wrap around these, but there maybe some licensing issues with distributing code built with the internet developer's toolkit (part of the enterprise connectivity toolkit, but can be got separately) - contact your sales representative to check to be on the safe side.

On the subject of no - open or close connection - up to LabVIEW 6.1 there's never been a Datasocket open .vi, so the DLL use coul
dn't wrap one anyway. This may be changeing in the future as it's on the request for future versions list - watch the website
for updates.

Hope this helps

Sacha.