Easytouch 520946z Transceiver card compatibility issues

ogdento

Bronze Supporter
Mar 30, 2015
1,169
Chico, CA
Pool Size
10000
Surface
Plaster
Chlorine
Salt Water Generator
SWG Type
Hayward Aqua Rite (T-15)
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
 
Last edited:
  • Like
Reactions: guinness
hey thanks Jim...

one thing I forgot to mention is that while we can update the firmware on the outdoor board and wireless remote, we can't update the firmware on the transceiver cards - or at least I haven't been able to yet. The update would be simple with a pic-kit 2 or greater programmer, but the transceiver firmware is not available and I can't pull the code off a board because the eeprom block is protected :(
 
  • Like
Reactions: Jimrahbe
Just wanted to post an update to this, I was testing some of my "dead" transceiver cards and it turns out they aren't all dead...

The first post here stated that I was unable to pair an ET wireless remote running 2.180 firmware to an outdoor board with 2.180fw using a transceiver with 2030fw. (That same 2.180fw wireless/outdoor combo pairs in a second or two using a transceiver with 2040fw)

but, I was wrong...

The 2030fw transceiver WILL pair, but it may take 40-70 seconds to find an address! I discovered this while testing a card with 2020 firmware... after 60 seconds the power-saver shut off the remote, so I cleared the eeprom, shut off the backlight and changed the power-off timeout to 5 minutes. Note: when you clear the eeprom and power up the UWC you will see a message asking you if you want to get an address or abort.

My 2020 card still couldn't find an address - so one was never set - and I happened to try a 2030 card next. Powering up gave me the same "do you want to get an address or abort" prompt, and after a few seconds it hadn't paired - as I expected. But I got distracted, and after about a minute I noticed an "address found" message had appeared! It took another 30-45 seconds for it to sync and then it was working normally.

I then tried this with remotes and outdoor boards at different firmware versions (2.100, 2.130, 2.140, 2.160, 2.190 etc., mixed and matched) - with a couple different 2030fw transceiver cards - and I got the same results (40-70 seconds to pair). So to anyone having issues pairing a UWC with a transceiver running 2030, try clearing your UWC eeprom first, and be patient while it searches for an address.

Never did get my 2020fw transceivers working with Easytouch or Mobiletouch 2 (Intellitouch) remotes so they might be toast, along with the cards that flash both 485 and rf leds in a 6-flash-then-pause repeating pattern.
 
  • Like
Reactions: Jimrahbe
Thread Status
Hello , This thread has been inactive for over 60 days. New postings here are unlikely to be seen or responded to by other members. For better visibility, consider Starting A New Thread.