|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: TCP Error reporting
I believe what you want to do is to set the timeout on the TCP read to 1500. Then wire the error out to a switch statement. If you don't get an error, cast the string as shown in your attachment. If you get an error, specifically an error 56, then call the subVI.
Greg McKaskle |
|
#2
|
|||
|
|||
|
Re: TCP Error reporting
Should I be worried that LabView might throw error 66 before error 56? Or should I just provide a sub-VI for both errors?
|
|
#3
|
|||
|
|||
|
Re: TCP Error reporting
I think that 66 means that the refnum isn't valid because the other side closed the connection. In that case, I usually close my refnum and reopen the session.
Greg McKaskle |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|