Labview 6.1 telnet session - garbled text

[Hank Walters]

I am running the example Telnet Line Client.vi in Labview 6.1 and get some miscellaneous text mixed in with my replies from the host. This does not happen when using Labview 6.1

[JRA]

I can try running this on my machine, but I'm not sure where this Telnet Line Client.vi is. I have the Internet Toolset, so maybe it's there. Let me know when you get a chance and I'll test this.

[BrandonS]

Where did you find the Telnet Line Client VI. I have been looking for the VI but unable to find it. I have LabVIEW 6.1. Additionally, you state that you are running this in LabVIEW 6.1 and get mixed text and they you say it does not happen when using LabVIEW 6.1 One of these statements is obviously wrong. Feel free to respond to this post and I will see if I can help you out.

[Hank Walters]

I got the telnet line client.vi as part of the Labview Internet Developers Toolkit, version 5.0, part no. 500540B which is sold by NI as catalog number 777343-01 at $495.00

I was comparing Version 6.1 with version 6.i (also known as 6.0). The toolkit has not been updated for Labview 6.1, only the behavior when used with the new Labview version.

The folks at NI tech support are still working on an answer.

Hank

[Anonymous]

In article <50650000000800000046710000-1042324653000@exchange.ni.com>,
"Hank Walters" wrote:

> I am running the example Telnet Line Client.vi in Labview 6.1 and get
> some miscellaneous text mixed in with my replies from the host. This
> does not happen when using Labview 6.1

I don't have the TLC.vi but I'm sure all that it does is use a series of
TCP writes and reads. I wrote an email client that simply telnets to a
smtp server and sends an email message. For a basic telnet connection,
all you need is 'TCP Open Connection', a loop that accepts commands from a
user interface to send to 'TCP Write', a 'TCP Read' to see what the
server's reply was, and finally a 'TCP Close Connection' when you exit the
loop. You're literally dumping text into the
'TCP Write' primitive. Just
make sure you tack on EOL after each text string. A SMTP server provides
all kinds of cool info. Just use port 25.

You have to find a server you can practice this on, preferably a public
one or better yet, your own machine (got linux?).

- Kevin

[madphoenix]

There is an issue with LabVIEW 6.1 where if you read more than 56 bytes at a time, you will read in some bad characters. The workaround is to read in 56 or less bytes every time you call Telnet Read.vi

LabVIEW 6 does not exhibit this problem.

[Hank Walters]

You are right! I got a reply from NI tech support and they admit to the problem and say they are working on a solution for the next release of Labview.

Thanks

[David Duffey]

This is an issue with LabVIEW 6.1 and the VI "Telnet Buffered Read.vi" from the Internet Toolkit.

I created a VI that doesn't affect LabVIEW.

• Download the attached VI, Telnet Buffered Read.vi and open in LabVIEW 6.1.
  
• Once loaded, go to File -> Save As, browse to Program Files\National Instruments\LabVIEW 6.1\vi.lib\addons\internet\telnet and open telnet.llb.
  
• This will open the telnet.llb, save the "Telnet Buffered Read.vi" in the telnet.llb to overwrite the old VI.
  

You should now be able to read more than 56 bytes at a time.

[Anonymous]

Is this a problem with just the LV Telnet client? Or with LabVIEW TCP
reads greater than 56 bytes?

Adam