Issue getting anything to return to the UI on an AquaLink RS4 about aqualinkd HOT 5 CLOSED

That’s really strange, it looks like the control panel is not accepting the ack from AqualinkD, I’ve never seen this before. Can you set logging from debug-serial to just debug, then start AqualinkD again, leave for a minute then connect to the web ui (not homebridge / HomeKit) and post the logs from that?

It’s an older rev board than I have seen before, so maybe that has something to do with it. (6475 rev E). That’s what’s on your board in the pic, can you check that’s also what the keypad displays (it’s common for the chip to be changed on the board, giving a different version than what’s written on the board).

from aqualinkd.

@sfeakes so I couldn't find a pool control that would display the REV in the wall control. I looked at the circuit board on the key pad and there is a PLCC 44 pin chip with 6700 Rev B1 printed on it.

Here is the aqualinkd.log after I put it into just debug mode. I did turn on and off some components from the UI and the wall control that I am hooked into. Pool responded to the wall control but not the UI and UI was likewise unresponsive...

aqualinkd.log.txt

from aqualinkd.

6700 Rev B1 is the correct version, and that should work.
It looks like it's the ACK that AqualinkD sends that the RS control panel doesn't seem to like, and the ACK is used for every single command we need to send. So there are two things to try just to see if we can figure this out.

• First is to use the exact same ID as your current RS4 keypad.

disconnect the RS4 keypad from the buss.
set aqualinkD to ID of 0x08.  (device_id=0x08) in config file.
fire it up, see if you get anything in the logs / web UI.

if that works, connect the RS4 panel back and try id's 0x0a and 0x0b see if they work for you.

• Second (if #1 didn't work) log all the commands to and from RS4 keypad to RS control panel. and send me a copy, that way I can see it there is anything different in your setup.

We need to run the below command as the RS4 keypad boots up.
sudo ./release/serial_logger /dev/ttyUSB0 -I 0x08 -p 1000

So, pull one of the power wires from the RS4 keypad (#1 or #4), run the above command, plug the wire back, wait for command to finish and post output.

I'll start digging up any information I can find on the particular rev# you have, see if Jandy have anything documented.

BTW, In the AqualinkD log, if you turn on serial debugging again what you're looking for is some kind of response after AqualinkD sends the initial ACK to the Probe the control panel sends out. So, below is what you are getting.

Dec-30-18 17:10:49 PM Debug:  RS received packet of type Probe length 7
Dec-30-18 17:10:49 PM Debug:  Send 11 bytes to serial
Dec-30-18 17:10:49 PM Debug:  Sent  | HEX: 0x00|0x10|0x02|0x00|0x01|0x00|0x00|0x13|0x10|0x03|0x00|
Dec-30-18 17:10:49 PM Debug:  RS Received duplicate, ignoring.

What you should see when it's all working correctly is. Notice the RS Received STATUS length 12 a few lines after AqualinkD sent a reply (ACK) to the PROBE command.

Debug:  Serial read 7 bytes
Debug:  RS received packet of type Probe length 7
Debug:  Send 11 bytes to serial
Debug:  Sent  | HEX: 0x00|0x10|0x02|0x00|0x01|0x00|0x00|0x13|0x10|0x03|0x00|
Debug:  RS Received PROBE length 7.
Debug:  Serial read 12 bytes
Debug:  Serial read 9 bytes
Debug:  Serial read 12 bytes
Debug:  RS received packet of type Status length 12
Debug:  Send 11 bytes to serial
Debug:  Sent  | HEX: 0x00|0x10|0x02|0x00|0x01|0x00|0x00|0x13|0x10|0x03|0x00|
Debug:  RS Received STATUS length 12.
Debug:  Serial read 24 bytes
Debug:  RS received packet of type Message length 24
Debug:  Send 11 bytes to serial
Debug:  Sent  | HEX: 0x00|0x10|0x02|0x00|0x01|0x00|0x00|0x13|0x10|0x03|0x00|
Info:   RS Message :- '8157 REV MMM'
Notice: Control Panel 8157 REV MMM

from aqualinkd.

@sfeakes no joy on the disconnecting of the RS4 wall control and impersonating the 0x08 address. I get the same behavior originally. I went ahead and restarted the control panel with serial logging enabled. Results are attached...

serial_logger_RS4_PanelStart.log.txt

One thing to note that is a tad weird was I found this document online:http://www.pleasurepoolsno.com/wp-content/uploads/2017/02/AquaLink-Troubleshooting-Manual.pdf. And pressed the Microcontroller reset to display the software installed and it first displays 6453 Rev B01 followed by 6522 Rev E. I would have expected 6700 REV C to be displayed instead of 6453 Rev B01 based on the chip label. Am I misinterpreting something?

I apologize for the noob questions and appreciate any help you can provide.

I have also retried these steps after reassigning my controller to 0x09 address by pulling the W2 jumper on the Wall Control unit. Same thing.

from aqualinkd.

Ok so... just wanted to update everyone. I think my PowerCenter PCB control board was slowly dying. I went ahead and installed the iAquaLink 2.0 upgrade kit and now everything is syncing. I appreciate everyone's assistance in this.

Cheers!
Ron

from aqualinkd.