TCP control, console message

LegacyUser

I am getting the below messages on the console of an NI-3000. What does it mean? 0:2:1 is a TCP client connection to a media server. The below messages are repeating because the Netlynx program tries to keep the TCP connection open -- it reconnects in the OFFLINE handler. Thing is, something is making it disconnect at 2 second intervals and its not the media server doing it.

Anyone have any thoughts? Is there some kind of socket timeout that could be taking place within Netlynx and disconnecting this?

-J

(0002632018) Exiting TCP Read thread - closing this socket for local port 2
(0002632019) CIpEvent::OffLine 0:2:1
(0002632024) Connected Successfully
(0002632026) CIpEvent::OnLine 0:2:1
(0002653035) Exiting TCP Read thread - closing this socket for local port 2
(0002653036) CIpEvent::OffLine 0:2:1
(0002653041) Connected Successfully
(0002653042) CIpEvent::OnLine 0:2:1
(0002674026) Exiting TCP Read thread - closing this socket for local port 2
(0002674027) CIpEvent::OffLine 0:2:1
(0002674032) Connected Successfully
(0002674033) CIpEvent::OnLine 0:2:1
(0002695032) Exiting TCP Read thread - closing this socket for local port 2
(0002695033) CIpEvent::OffLine 0:2:1
(0002695038) Connected Successfully
(0002695039) CIpEvent::OnLine 0:2:1
(0002716038) Exiting TCP Read thread - closing this socket for local port 2
(0002716039) CIpEvent::OffLine 0:2:1
(0002716044) Connected Successfully
(0002716045) CIpEvent::OnLine 0:2:1
(0002737035) Exiting TCP Read thread - closing this socket for local port 2
(0002737036) CIpEvent::OffLine 0:2:1
(0002737041) Connected Successfully
(0002737043) CIpEvent::OnLine 0:2:1
(0002758052) Exiting TCP Read thread - closing this socket for local port 2
(0002758053) CIpEvent::OffLine 0:2:1
(0002758058) Connected Successfully
(0002758059) CIpEvent::OnLine 0:2:1

LegacyUser

Well, it seems updating the firmware to latest has made this go away. Guess should always start there!

-J

Marc Scheibein

Depending on the device you control, it may be more useful to connect, send and receive data, then disconnect and then parse the data you received.
For example the MAX module is doing it that way.

DHawthorne

It's likely this is normal behavior. If your media server is a MAX, it is definitely normal, and just how they work.

There is a TCP paradigm that essentially comes down to: make your connection, send your packet; the receiving device responds, then closes the connection. It's standard for HTML; for IP controlled devices it's not uncommon, but not exactly "standard." So it is very likely that what you are seeing is your NetLinx polling the media device, it responding and closing the connection, then the next poll going out.

Again, if your media server is a MAX, this is absolutely what is happening, and it is 100% normal operation.

LegacyUser

Hi Guys -

Thanks for the quick replies, definitely! the media server is not a max but I do need to stay connected to it to monitor for unsolicited events. However, since upgrading the firmware on the NI-3000 this issue has completely gone away. TCP connections are staying up and life is good!

Thanks!
-J