I've definitely had issues with TCP/IP Clients not reconnecting on a CP4N the way they would on 3-series, and even worse not disconnecting and reconnecting when the Connect line is dropped and raised again.? My current working logic is to send a ping command every 30 seconds, and if it goes more than 10 seconds without a response, drop the Connect line for 5 seconds.? When it only dropped for 1 second it wouldn't reliably reconnect to the TesiraForte or Shure MXA920s.? Current firmware on everything.
Since this topic is being resurrected I¡¯d love to know people¡¯s general thoughts on whether or not the TCP Client, along with other IP issues, has been fixed on 4-series yet.
I still have several issues with:
4-series stopping reconnecting to a port when the connection is remotely dropped even though Connect is tied to 1, requiring a reboot/restart.
4-series to 3-series inter system communication randomly failing.
4-series to TSW-x70 communication stopping.
Ethernet based CCDs that work fine on 3-series failing on 4-series.
In terms of using a S+ emulation of the TCP-Client symbol to work around some issues, is this still recommended? If so, could anyone share a S+ module that can work as a drop-in replacement for the standard TCP Client symbol?
