LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

telnet read problem

While doing telnet read, if the operation times out, I don't get an error.

I am using telnet read in line mode. My line separator is my prompt char
"cli>". Timeout is set to 10seconds. If I turn of power to my device after I
logged in successfully, my telnet read operation should fail, but telnet
read return OK.


vishi
0 Kudos
Message 1 of 4
(3,047 Views)
I just checked the version of the Internet Toolkit that I have just to check, and that is apparently the intended behaviour. For some reason, NI tends to not see timeouts as an error.

The thing to do is open up the read icon and follow the error clusters through. In the version I have, there are several places where there is a small icon labled "NO TO" on the error cluster that (you guessed it) filters out any timeout errors that occur.

The simple fix is to rename the read VI and then go through it and remove all the timeout filters--which really shouldn't be there in the first place.

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 2 of 4
(3,044 Views)
Thanks Mike for your help.

I should have put my own error checking by explicitly looking for the line
terminator chars in the data out which comes out of telnet read, but when I
read the telnet help file, it clearly said that it will return an error in
case of timeout.

I will modify VIs based on your input.



"mikeporter" wrote in message
news:50650000000500000041EA0000-1042324653000@exchange.ni.com...
> I just checked the version of the Internet Toolkit that I have just to
> check, and that is apparently the intended behaviour. For some reason,
> NI tends to not see timeouts as an error.
>
> The thing to do is open up the read icon and follow the error clusters
> through. In the version I have, there are several places where there
> is a
small icon labled "NO TO" on the error cluster that (you guessed
> it) filters out any timeout errors that occur.
>
> The simple fix is to rename the read VI and then go through it and
> remove all the timeout filters--which really shouldn't be there in the
> first place.
>
> Mike...
0 Kudos
Message 3 of 4
(3,044 Views)

Vishi,

You're using LabView now?

Nick

btw, my new email address is nick_scalero@hansenmedical.com

 

 

0 Kudos
Message 4 of 4
(2,783 Views)