This is more of an informational post rather than a question... but I don't believe that all versions of the newer Laird chipset transceiver cards (part 520946z) are compatible with all Easytouch firmware versions.
TLDR - I could not set the wireless address using 3 different 2.030 firmware transceivers and an Easytouch running firmware 2.160, 2.180 or 2.190, but it worked with 2.140. if you have an Easytouch system and are buying a spare 520946z transceiver card... make sure the transceiver has 2.040 or above if your UOC and UWC (outdoor and wireless remote) firmware is over 2.140 or you won't be able to pair! And if you've got this mismatched firmware and think your transceiver is broken, it may not be!!
I had just finished updating an Easytouch 8 outdoor board and wireless remote from 2.130 to 2.180, and I could no longer set the wireless address (I use poolclown's steps: Pentair Easy Touch help). [SIDE NOTE: I didn't need to reset the address because the old one was still stored in the eeproms of both units... but I forgot, and once you start the process it clears them so you HAVE to reset it]
Anyway... this compatibility issue is something that was kicked around in some earlier posts and I think I've finally confirmed the issue. It was originally thought that the UOC and UWC had to be at certain levels of firmware, but in reality it seems to be the transceiver's firmware that matters!! See Easytouch Wireless Remote Issues, Pentair Easytouch 8 - No communication with Wireless Controller (UWC)
After a little testing and a lot of firmware updating, I discovered that with these Laird-based (520946z) transceiver cards running 2.030 firmware - I could not set the wireless address if the UOC had firmware after 2.140 (I tried with 2.160, 2.180 and 2.190... there is no 2.170 and I didn't have 2.150 files). However, I CAN set the address on a UOC board running 2.130-2.190 if the transceiver card is running 2.040 firmware... and weirder yet, once the address is set using the 2.040 card (which saves it to the eeprom of the UOC and UWC), I can pop the 2.030 card back in and it can control the system just fine!! I'll track down the 2.150 ET firmware to test... but once I changed the firmware from 2.180 to 2.140 on both the UOC and UWC, I could set the address on a 2.030 transceiver card.
If anybody has a 2.030 card and is running > 2.140 on their UOC/UWC and CAN pair... I'd love to hear about it
TLDR - I could not set the wireless address using 3 different 2.030 firmware transceivers and an Easytouch running firmware 2.160, 2.180 or 2.190, but it worked with 2.140. if you have an Easytouch system and are buying a spare 520946z transceiver card... make sure the transceiver has 2.040 or above if your UOC and UWC (outdoor and wireless remote) firmware is over 2.140 or you won't be able to pair! And if you've got this mismatched firmware and think your transceiver is broken, it may not be!!
I had just finished updating an Easytouch 8 outdoor board and wireless remote from 2.130 to 2.180, and I could no longer set the wireless address (I use poolclown's steps: Pentair Easy Touch help). [SIDE NOTE: I didn't need to reset the address because the old one was still stored in the eeproms of both units... but I forgot, and once you start the process it clears them so you HAVE to reset it]
Anyway... this compatibility issue is something that was kicked around in some earlier posts and I think I've finally confirmed the issue. It was originally thought that the UOC and UWC had to be at certain levels of firmware, but in reality it seems to be the transceiver's firmware that matters!! See Easytouch Wireless Remote Issues, Pentair Easytouch 8 - No communication with Wireless Controller (UWC)
After a little testing and a lot of firmware updating, I discovered that with these Laird-based (520946z) transceiver cards running 2.030 firmware - I could not set the wireless address if the UOC had firmware after 2.140 (I tried with 2.160, 2.180 and 2.190... there is no 2.170 and I didn't have 2.150 files). However, I CAN set the address on a UOC board running 2.130-2.190 if the transceiver card is running 2.040 firmware... and weirder yet, once the address is set using the 2.040 card (which saves it to the eeprom of the UOC and UWC), I can pop the 2.030 card back in and it can control the system just fine!! I'll track down the 2.150 ET firmware to test... but once I changed the firmware from 2.180 to 2.140 on both the UOC and UWC, I could set the address on a 2.030 transceiver card.
If anybody has a 2.030 card and is running > 2.140 on their UOC/UWC and CAN pair... I'd love to hear about it
Last edited: