During long writes the remotelink 2 can time out while the ISY is still writing. Apparently pressing the set button for 3 seconds to reenter link mode immediately gets it going again before the ISY times out trying to write...

 

In my system it takes about 35 link writes before the remotelinc 2 times out.

Are other devices being updated at the same time?

 

In theory a device should not timeout as long as the reads or writes to the device continue. It sounds like other devices are being updated at the same time allowing a gap between reads/writes to the RemoteLinc2 allowing it to timeout.

Nope... In fact it happened when I deleted and re-added the device with the option to "remove all links" So really the only other devices link which should have been written would be the PLM

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Trace adding the RemoteLinc2 to the ISY. The only way the RL2 should have timed out would be comm issues where some of the commands fail to reach the device or the ACK does not make it back to the PLM. If there is a gap in time where the ISY is waiting 9 seconds (the 9 seconds is from memory) between commands because the RL2 did not ACK a command, the RL2 could time out after the 4 minute default timeout has expired.

Can't. Once I deleted it, now it only writes a few links so it doesn't have to go that long anymore...

Hi andrew67,

 

LeeG is 100% correct. The main question is whether or not ISY is still writing to the RL2. This is indicated by a green --> Writing icon on the node.

 

With kind regards,

Michel