So the first trick to getting Crestron to reconnect to a device is for it to realize the connection has dropped in the first place.? Sending a regular command to the device is the best way to make sure lost connections are detected promptly.? The second thing to know is that with a 1 on the Connect, Crestron will use an exponential backoff time where it waits 1 second to retry, then 2 seconds, 4 seconds, etc., up to 128 seconds between retries.? This can feel broken if you're not expecting it, or if you need to see a device as soon as it comes back online.? Most of my TCP clients have a 1 on the connect and send a query command of some sort every 30 seconds.??
Posting here to see what others use to connect an IP client and keep it connected.
Over the years, I've seen different methods, from something as simple as putting a '1' on the connect line to using a Set/Reset that gets triggered when the device falls offline.
It was my understanding that the program would continue to try and connect to a device as long as the logic was high. This has always worked, but recently I've had some Philips displays that are fairly uncooperative. I could connect to them, but during testing, we'd pull the network cable or disconnect power, Even though the program logic to connect was high, after a few minutes, it would give up and stop trying to initiate the connection. My solution was once the connection feedback went low, it would trigger an oscillator, which would continue to connect the client indefinitely.
This worked, but this feels like a bit of overkill.
What do you all do?
Thanks,
g
