Need help with getting connected. #381

bmwhd123 · 2025-01-29T22:01:06Z

bmwhd123
Jan 29, 2025

I'm running version 2.5.1 on a Pi 4B with the recommended RS485 USB adapter. I've connected data + and data - as directed.

AqualinkD seems to start correctly and reports:

Notice: AqualinkD: Listening to Aqualink RS8 on serial port: /dev/ttyUSB0
Notice: AqualinkD: Waiting for Control Panel probe
Notice: AqualinkD: Got probe on '0x60' Standard Protocol
Notice: AqualinkD: Starting communication with Control Panel

Web UI shows buttons and the message "Connecting to control panel"

Here's the full output at startup:

Notice: AqualinkD: Aqualink Daemon v2.5.1 (dev)
Notice: AqualinkD: Panel set to PDA-6 Combo Pool/Spa
Notice: AqualinkD: Config log_level = 6
Notice: AqualinkD: Config device_id = 0x60
Notice: AqualinkD: Config rssa_device_id = 0x00
Notice: AqualinkD: Config extra_device_id = 0x00
Notice: AqualinkD: Config extra_device_prog = NO
Notice: AqualinkD: Config serial_port = /dev/ttyUSB0
Notice: AqualinkD: Config socket_port = 8080
Notice: AqualinkD: Config web_directory = /var/www/aqualinkd/
Notice: AqualinkD: Config use_aux_labels = NO
Notice: AqualinkD: Config override frz prot = NO
Notice: AqualinkD: Config mqtt server = (null)
Notice: AqualinkD: Config mqtt DZ sub topic = (null)
Notice: AqualinkD: Config mqtt DZ pub topic = (null)
Notice: AqualinkD: Config mqtt AQ topic = (null)
Notice: AqualinkD: Config mqtt user = (null)
Notice: AqualinkD: Config mqtt passwd = (null)
Notice: AqualinkD: Config mqtt timed update = NO
Notice: AqualinkD: Config mqtt HA dis topic = (null)
Notice: AqualinkD: Config mqtt ID = aqualinkd_d83add20
Notice: AqualinkD: Config PDA Mode = YES
Notice: AqualinkD: Config PDA Sleep Mode = YES
Notice: AqualinkD: Config force SWG = NO
Notice: AqualinkD: Config force PS setpoint = NO
Notice: AqualinkD: Config force Freeze Prot = NO
Notice: AqualinkD: Config deamonize = NO
Notice: AqualinkD: Config enable scheduler = NO
Notice: AqualinkD: Config light_pgm_mode = 0.00
Notice: AqualinkD: Debug RS485 protocol = NO
Notice: AqualinkD: Debug RS485 protocol raw = NO
Notice: AqualinkD: Display warnings in web = NO
Notice: AqualinkD: Keep panel time in sync = YES
Notice: AqualinkD: Read SWG direct = NO
Notice: AqualinkD: Read ePump direct = NO
Notice: AqualinkD: Read vsfPump direct = NO
Notice: AqualinkD: Read JXi heater direct = NO
Notice: AqualinkD: Read LX heater direct = NO
Notice: AqualinkD: Read Chem Feeder direct = NO
Notice: AqualinkD: Start Pump on events = NO
Notice: AqualinkD: Serial FTDI low latency = YES
Notice: AqualinkD: RS485 Frame delay = 1ms
Notice: AqualinkD: Config BTN Filter_Pump = label Filter Pump |
Notice: AqualinkD: Config BTN Spa = label Cleaner |
Notice: AqualinkD: Config BTN Aux_1 = label Low Speed |
Notice: AqualinkD: Config BTN Aux_2 = label Lights |
Notice: AqualinkD: Config BTN Aux_3 = label Aux 4 |
Notice: AqualinkD: Config BTN Aux_4 = label Spa |
Notice: AqualinkD: Config BTN Aux_5 = label Aux 5 |
Notice: AqualinkD: Config BTN Pool_Heater = label Aux 6 |
Notice: AqualinkD: Config BTN Spa_Heater = label Heater |
Notice: AqualinkD: Config BTN Extra_Aux = label Sheer Decent |
Notice: NetService:Starting network services thread
Notice: NetService:Starting web server on port 8080
Notice: NetService:Starting MQTT client to (null)
Notice: RS Serial: Port /dev/ttyUSB0 low latency mode is set
Info: RS Serial: Port /dev/ttyUSB0 set I/O blocking attributes
Notice: AqualinkD: Listening to Aqualink RS8 on serial port: /dev/ttyUSB0
Notice: AqualinkD: Waiting for Control Panel probe
Notice: AqualinkD: Got probe on '0x60' Standard Protocol
Notice: AqualinkD: Starting communication with Control Panel

When I connect to the Web UI and press the Filter button, I see this:

Info: NetService:URI request: : '/ '
Info: NetService:URI request: : '/api/dynamicconfig '
Info: NetService:2: MATCH Filter_Pump to topic Filter_Pump/set
Info: NetService:ri1=Filter_Pump/set, length=11 char at len=/
Info: Panl&Prog: Device request type 'OnOff' for deviceindex 0 'Filter Pump' of value 1 from 'WebSocket'
Info: Panl&Prog: received 'ON' for 'Filter_Pump', turning 'ON'
Notice: Panl&Prog: Starting programming thread 'Switch PDA device on/off'
Info: Panl&Prog: Programming: Switch PDA device on/off, 18
Info: PDA: PDA Device On/Off, device 'Filter Pump', state 0
Info: AllButton: Queue send '0x02' to controller (programming)

Pump doesn't start.

After that, nothing.

Answered by bmwhd123

Feb 3, 2025

This has been resolved by replacing with a higher rev control panel as described in this thread. The old PDA panel I had just couldn't hack it.

View full answer

sfeakes · 2025-01-29T22:43:20Z

sfeakes
Jan 29, 2025
Maintainer

How long did you leave it connecting? It will take some time to connect (up to 2 minutes depending on if the control panel has seen that ID before) as it has to wait for the control panel to start the connection.

Otherwise, set debug output in aqualinkd.conf and post the output. That will give some more information. Also I'm assuming you ran serial_logger and got the output from that?

0 replies

bmwhd123 · 2025-01-29T23:05:27Z

bmwhd123
Jan 29, 2025
Author

With DEBUG turned on, I get a fast flowing stream of RS Timing messages. When I press the Filter button, I see:

Debug: RS Timings:Time between packets (0.115 sec)
Debug: RS Timings:Time between packets (0.121 sec)
Debug: RS Timings:Time between packets (0.114 sec)
Debug: NetService:WS: Message - Key 'command' Value 'Filter_Pump'
Debug: NetService:WS: Message - Key 'uri' Value 'Filter_Pump/set'
Debug: NetService:WS: Message - Key 'value' Value '1'
Debug: NetService:WS: URI Request 'Filter_Pump/set': value 1.00
Info: NetService:2: MATCH Filter_Pump to topic Filter_Pump/set
Info: NetService:ri1=Filter_Pump/set, length=11 char at len=/
Info: Panl&Prog: Device request type 'OnOff' for deviceindex 0 'Filter Pump' of value 1 from 'WebSocket'
Info: Panl&Prog: received 'ON' for 'Filter_Pump', turning 'ON'
Notice: Panl&Prog: Starting programming thread 'Switch PDA device on/off'
Info: Panl&Prog: Programming: Switch PDA device on/off, 18
Debug: Panl&Prog: Thread 18,0x7fa4003f10 is active (Switch PDA device on/off)
Info: PDA: PDA Device On/Off, device 'Filter Pump', state 0
Debug: PDA: PDA Device programmer request for menu 19
Debug: AllButton: Queue empty!
Info: AllButton: Queue send '0x02' to controller (programming)
Debug: PDA: waitForPDAMessageType 0x09
Debug: PDA: waitForPDAMessageType 0x09, last message type was 0x00 (1 of 10)
Debug: RS Timings:Time between packets (0.117 sec)
Debug: RS Timings:Time between packets (0.113 sec)

And then nothing but the RS Timings messages after that.

0 replies

sfeakes · 2025-01-29T23:16:45Z

sfeakes
Jan 29, 2025
Maintainer

With debug, do you get anything like the below in the messages?

PDA panel is slow and will take time to respond to anything.

Info:    PDA:       PDA Menu Line 0 =      Wed 5:11PM 
Info:    PDA:       PDA Menu Line 1 = Air         Pool
Info:    PDA:       PDA Menu Line 2 = 72`          65`
Info:    PDA:       PDA Menu Line 3 = 
Info:    PDA:       PDA Menu Line 4 = Pool Mode     ON
Info:    PDA:       PDA Menu Line 5 = Pool Heater  OFF
Info:    PDA:       PDA Menu Line 6 = Spa Mode     OFF
Info:    PDA:       PDA Menu Line 7 = Spa Heater   ENA
Info:    PDA:       PDA Menu Line 8 = Menu            
Info:    PDA:       PDA Menu Line 9 = Equipment ON/OFF

It might be easier to see what's going on if you post the full log. Make sure your real PDA remote is in sleep mode, Restart AqualinkD (with debug mode), leave it for a minute or two, goto aqmanager.html and download 1k lines the log.

1 reply

bmwhd123 Jan 29, 2025
Author

I do not see those Info: PDA lines at all.

Here is the output you requested (Note - I cut out a bunch of the RS Timings lines for brevity):

Notice: AqualinkD: Aqualink Daemon v2.5.1 (dev)
Notice: AqualinkD: Panel set to PDA-4 Combo Pool/Spa
Notice: AqualinkD: Config log_level = 7
Notice: AqualinkD: Config device_id = 0x60
Notice: AqualinkD: Config rssa_device_id = 0x00
Notice: AqualinkD: Config extra_device_id = 0x00
Notice: AqualinkD: Config extra_device_prog = NO
Notice: AqualinkD: Config serial_port = /dev/ttyUSB0
Notice: AqualinkD: Config socket_port = 8080
Notice: AqualinkD: Config web_directory = /var/www/aqualinkd/
Notice: AqualinkD: Config use_aux_labels = NO
Notice: AqualinkD: Config override frz prot = NO
Notice: AqualinkD: Config mqtt server = (null)
Notice: AqualinkD: Config mqtt DZ sub topic = (null)
Notice: AqualinkD: Config mqtt DZ pub topic = (null)
Notice: AqualinkD: Config mqtt AQ topic = (null)
Notice: AqualinkD: Config mqtt user = (null)
Notice: AqualinkD: Config mqtt passwd = (null)
Notice: AqualinkD: Config mqtt timed update = NO
Notice: AqualinkD: Config mqtt HA dis topic = (null)
Notice: AqualinkD: Config mqtt ID = aqualinkd_d83add20
Notice: AqualinkD: Config PDA Mode = YES
Notice: AqualinkD: Config PDA Sleep Mode = YES
Notice: AqualinkD: Config force SWG = NO
Notice: AqualinkD: Config force PS setpoint = NO
Notice: AqualinkD: Config force Freeze Prot = NO
Notice: AqualinkD: Config deamonize = NO
Notice: AqualinkD: Config enable scheduler = NO
Notice: AqualinkD: Config light_pgm_mode = 0.00
Notice: AqualinkD: Debug RS485 protocol = NO
Notice: AqualinkD: Debug RS485 protocol raw = NO
Notice: AqualinkD: Display warnings in web = NO
Notice: AqualinkD: Keep panel time in sync = YES
Notice: AqualinkD: Read SWG direct = NO
Notice: AqualinkD: Read ePump direct = NO
Notice: AqualinkD: Read vsfPump direct = NO
Notice: AqualinkD: Read JXi heater direct = NO
Notice: AqualinkD: Read LX heater direct = NO
Notice: AqualinkD: Read Chem Feeder direct = NO
Notice: AqualinkD: Start Pump on events = NO
Notice: AqualinkD: Serial FTDI low latency = YES
Notice: AqualinkD: Config BTN Filter_Pump = label FILTER PUMP |
Notice: AqualinkD: Config BTN Spa = label SPA |
Notice: AqualinkD: Config BTN Aux_1 = label POOL HEAT |
Notice: AqualinkD: Config BTN Aux_2 = label SPA HEAT |
Notice: AqualinkD: Config BTN Aux_3 = label CLEANER |
Notice: AqualinkD: Config BTN Pool_Heater = label LOW SPEED |
Notice: AqualinkD: Config BTN Spa_Heater = label LIGHTS |
Notice: AqualinkD: Config BTN Extra_Aux = label NOT USED |
Notice: NetService:Starting network services thread
Notice: NetService:Starting web server on port 8080
Notice: NetService:Starting MQTT client to (null)
Debug: RS Serial: Openeded serial port /dev/ttyUSB0
Notice: RS Serial: Port /dev/ttyUSB0 low latency mode is set
Info: RS Serial: Port /dev/ttyUSB0 set I/O blocking attributes
Notice: AqualinkD: Listening to Aqualink RS8 on serial port: /dev/ttyUSB0
Notice: AqualinkD: Waiting for Control Panel probe
Debug: RS Timings:Time between packets (1738193920.000 sec)
Debug: RS Timings:Time between packets (0.100 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: RS Timings:Time between packets (0.095 sec)
Debug: RS Timings:Time between packets (0.095 sec)
Notice: AqualinkD: Got probe on '0x60' Standard Protocol
Notice: AqualinkD: Starting communication with Control Panel
Debug: RS Timings:Time between packets (0.100 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.097 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.095 sec)
Debug: RS Timings:Time between packets (0.095 sec)
Debug: RS Timings:Time between packets (0.100 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Info: NetService:URI request: : '/aqmanager.html '
Debug: NetService:Served WEB request
Info: NetService:URI request: : '/ '
Debug: NetService:Served WEB request
Info: NetService:URI request: : '/api/dynamicconfig '
Debug: NetService:API: URI Request 'dynamicconfig': value 0.00
Debug: NetService:Served WEB request
Debug: RS Timings:Time between packets (0.096 sec)
Debug: RS Timings:Time between packets (0.095 sec)
Debug: RS Timings:Time between packets (0.095 sec)
Debug: RS Timings:Time between packets (0.093 sec)
Debug: RS Timings:Time between packets (0.097 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: PDA: PDA Aqualink daemon in sleep mode
Debug: RS Timings:Time between packets (0.100 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: RS Timings:Time between packets (0.100 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: RS Timings:Time between packets (0.100 sec)
Debug: RS Timings:Time between packets (0.093 sec)
Debug: NetService:++ Websocket joined
Debug: NetService:WS: Message - Key 'uri' Value 'devices'
Debug: NetService:WS: URI Request 'devices': value -999.00
Debug: NetService:JSON: web used 1714 of 5120
Debug: NetService:WS: Message - Key 'uri' Value 'status'
Debug: NetService:WS: URI Request 'status': value -999.00
Debug: NetService:++ Websocket joined
Debug: RS Timings:Time between packets (0.097 sec)
Debug: NetService:WS: Message - Key 'uri' Value 'aqmanager'
Debug: NetService:WS: URI Request 'aqmanager': value -999.00
Debug: NetService:Started AqualinkD Manager
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: RS Timings:Time between packets (0.100 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: NetService:WS: Message - Key 'command' Value 'Filter_Pump'
Debug: NetService:WS: Message - Key 'uri' Value 'Filter_Pump/set'
Debug: NetService:WS: Message - Key 'value' Value '1'
Debug: NetService:WS: URI Request 'Filter_Pump/set': value 1.00
Info: NetService:2: MATCH Filter_Pump to topic Filter_Pump/set
Info: NetService:ri1=Filter_Pump/set, length=11 char at len=/
Info: Panl&Prog: Device request type 'OnOff' for deviceindex 0 'FILTER PUMP' of value 1 from 'WebSocket'
Info: Panl&Prog: received 'ON' for 'Filter_Pump', turning 'ON'
Notice: Panl&Prog: Starting programming thread 'Switch PDA device on/off'
Info: Panl&Prog: Programming: Switch PDA device on/off, 18
Debug: Panl&Prog: Thread 18,0x7fa8003660 is active (Switch PDA device on/off)
Info: PDA: PDA Device On/Off, device 'FILTER PUMP', state 0
Debug: PDA: PDA Device programmer request for menu 19
Debug: AllButton: Queue empty!
Info: AllButton: Queue send '0x02' to controller (programming)
Debug: PDA: waitForPDAMessageType 0x09
Debug: PDA: waitForPDAMessageType 0x09, last message type was 0x00 (1 of 10)
Debug: RS Timings:Time between packets (0.100 sec)
Debug: RS Timings:Time between packets (0.093 sec)
Debug: RS Timings:Time between packets (0.097 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.097 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: PDA: PDA can't sleep as thread 18,0x7fa8003660 is active
Debug: RS Timings:Time between packets (0.100 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: RS Timings:Time between packets (0.095 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: RS Timings:Time between packets (0.095 sec)
Debug: NetService:WS: Message - Key 'command' Value 'Spa'
Debug: NetService:WS: Message - Key 'uri' Value 'Spa/set'
Debug: NetService:WS: Message - Key 'value' Value '1'
Debug: NetService:WS: URI Request 'Spa/set': value 1.00
Info: NetService:2: MATCH Spa to topic Spa/set
Info: NetService:ri1=Spa/set, length=3 char at len=/
Info: Panl&Prog: Device request type 'OnOff' for deviceindex 1 'SPA' of value 1 from 'WebSocket'
Info: Panl&Prog: received 'ON' for 'Spa', turning 'ON'
Notice: Panl&Prog: Starting programming thread 'Switch PDA device on/off'
Debug: Panl&Prog: Thread 0x7fa8011090 (Switch PDA device on/off) sleeping, waiting for thread 0x7fa8003660 (Switch PDA device on/off>
Debug: RS Timings:Time between packets (0.095 sec)
Debug: RS Timings:Time between packets (0.100 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.097 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.095 sec)
Debug: RS Timings:Time between packets (0.100 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.097 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.095 sec)
Debug: Panl&Prog: Thread 0x7fa8011090 (Switch PDA device on/off) sleeping, waiting for thread 0x7fa8003660 (Switch PDA device on/off>
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: RS Timings:Time between packets (0.100 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: Panl&Prog: Thread 0x7fa8011090 (Switch PDA device on/off) sleeping, waiting for thread 0x7fa8003660 (Switch PDA device on/off>
Debug: RS Timings:Time between packets (0.100 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: RS Timings:Time between packets (0.100 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: Panl&Prog: Thread 0x7fa8011090 (Switch PDA device on/off) sleeping, waiting for thread 0x7fa8003660 (Switch PDA device on/off>
Debug: RS Timings:Time between packets (0.100 sec)
Debug: RS Timings:Time between packets (0.094 sec)
Debug: RS Timings:Time between packets (0.096 sec)
Debug: RS Timings:Time between packets (0.094 sec)

sfeakes · 2025-01-29T23:59:18Z

sfeakes
Jan 29, 2025
Maintainer

it looks like the panel is not replying to the PDA messages. But without seeing the time information, it's hard to tell. If you export the logs using aqmanger.html then that will give the time information.

What output did you get when you ran serial_logger?

5 replies

bmwhd123 Jan 30, 2025
Author

Thank you for the prompt responses. I will rerun serial_logger and do another debug capture with full timings and output later this evening.

bmwhd123 Jan 30, 2025
Author

Output of serial_logger:
serial_logger.txt

bmwhd123 Jan 30, 2025
Author

Output to log file from aqualinkd:
aqualinkd.log

bmwhd123 Jan 30, 2025
Author

My config file:
aqualinkd.conf.txt

bmwhd123 Jan 30, 2025
Author

Are those what you need?

sfeakes · 2025-01-30T23:54:53Z

sfeakes
Jan 30, 2025
Maintainer

The log file you sent was still terminal output, not the downloaded one. I can see you downloaded a log, but looks like you attached the wrong one to the post.

It looks like AqualinkD is going into PDA sleep mode too soon, but I can't really tell since the times are missing.
Can you edit aqualink.conf and set pda_sleep_mode = no and let me know if that makes a differance.

1 reply

bmwhd123 Jan 31, 2025
Author

Ok. This time for sure. I started the daemon, waited 2 min, then hit the Filter Pump button. Should all be in this file.
aqualinkd.log

sfeakes · 2025-01-31T03:59:39Z

sfeakes
Jan 31, 2025
Maintainer

The panel is not replying to the messages AqualinkD is sending. I don't think this is a wiring problem, since the communication is bidirectional over the same wires.
I've seen this on 2 occasions before, one time it was a bad RS485 adapter, the other time the RS485 interface on the panel itself was bad.
Do you have a working PDA remote? If so then it's not the panel.

The OS/kernel needs to send a command to the USB2RS485 adapter to change it from receive mode to send mode, so potentially this could be some OS problem, but I've never seen that before.
On the USB adapter, make sure only A and B wires are connected (Data + and Data -), and make sure no other of the spare wires are touching each other / anything else.

Can you turn on serial_debugging and post output? Just incase their is something I'm missing.

9 replies

bmwhd123 Jan 31, 2025
Author

This is the one I got:

sfeakes Jan 31, 2025
Maintainer

That image didn't come through.

bmwhd123 Jan 31, 2025
Author

Try now.

sfeakes Jan 31, 2025
Maintainer

Perfect. That's an RS panel, not PDA only panel. (Rev JJ). That's a worthwhile upgrade irrelevant of any other problems. That revision doesn't support color lights or variable speed pumps though.

There is good information here on what panel versions support.
https://www.troublefreepool.com/wiki/index.php?title=Jandy_Aqualink_RS#How_to_Determine_the_Revision_of_an_Aqualink_System

bmwhd123 Jan 31, 2025
Author

That should work then since we've only got 4 devices, a 2 speed pump, regular lights, a spa heater, and the Aquapure salt system. Even if it won't support my old PDA, hopefully if I can get this software to work, I can use the simulators to program it.

sfeakes · 2025-01-31T20:07:03Z

sfeakes
Jan 31, 2025
Maintainer

Thinking about the overcurrent error. In the extras directory there is a script called pi_health.sh, run that and if that shows the Pi has has an undervolt issue. Then it means your power supply is not providing enough power. That might be the cause of the OS not setting the USB adapter into TX mode.

5 replies

bmwhd123 Jan 31, 2025
Author

I'll look at that but this Pi and it's OEM power supply have been fine for over a year. Formerly running part of my home network. We'll see what the new RS485 cable does when it arrives tomorrow. If that doesn't work, the eBay panel may have to go in.

sfeakes Jan 31, 2025
Maintainer

The OEM raspberry PI power supplies are very stable, so I doubt that's the issue.

A Pi 4 is also too fast for a PDA only panel, so you should set rs485_frame_delay = 4 in aqualinkd.conf. BUT that won't change the issue you are currently facing.

bmwhd123 Jan 31, 2025
Author

Thank you. I'll update after testing the new RS485 cable tomorrow.

bmwhd123 Feb 1, 2025
Author

No joy with the new serial cable. Attached log file from a couple of runs with this cable just in case you see something different.

aqualinkd(2).log

bmwhd123 Feb 2, 2025
Author

Can you look at the last 2 lines of this snippet of log file? Is it possible that my guess for the panel type is wrong? My chip is a PDA PS6 8272 but I'm not sure what that translates to in terms of what the panel type variables should be set to.

Feb 01 16:17:56 Debug: RS Timings:Time between packets (0.106 sec)
Feb 01 16:17:56 Debug: NetService:WS: Message - Key 'command' Value 'Filter_Pump'
Feb 01 16:17:56 Debug: NetService:WS: Message - Key 'uri' Value 'Filter_Pump/set'
Feb 01 16:17:56 Debug: NetService:WS: Message - Key 'value' Value '1'
Feb 01 16:17:56 Debug: NetService:WS: URI Request 'Filter_Pump/set': value 1.00
Feb 01 16:17:56 Info: NetService:2: MATCH Filter_Pump to topic Filter_Pump/set
Feb 01 16:17:56 Info: NetService:ri1=Filter_Pump/set, length=11 char at len=/
Feb 01 16:17:56 Info: Panl&Prog: Device request type 'OnOff' for deviceindex 0 'FILTER PUMP' of value 1 from 'WebSocket'
Feb 01 16:17:56 Info: Panl&Prog: received 'ON' for 'Filter_Pump', turning 'ON'
Feb 01 16:17:56 Notice: Panl&Prog: Starting programming thread 'Switch PDA device on/off'
Feb 01 16:17:56 Info: Panl&Prog: Programming: Switch PDA device on/off, 18
Feb 01 16:17:56 Debug: Panl&Prog: Thread 18,0x7f7c007fc0 is active (Switch PDA device on/off)
Feb 01 16:17:56 Info: PDA: PDA Device On/Off, device 'FILTER PUMP', state 0
Feb 01 16:17:56 Debug: PDA: PDA Device programmer request for menu 19
Feb 01 16:17:56 Debug: AllButton: Queue empty!
Feb 01 16:17:56 Info: AllButton: Queue send '0x02' to controller (programming)
Feb 01 16:17:56 Debug: PDA: waitForPDAMessageType 0x09
Feb 01 16:17:56 Debug: PDA: waitForPDAMessageType 0x09, last message type was 0x00 (1 of 10)

sfeakes · 2025-02-02T16:04:10Z

sfeakes
Feb 2, 2025
Maintainer

The only thing that matters in the config to establish the initial connection & protocol is device_id=0x60. The panel type will be defined as PDA since you use 0x60, and the size is unimportant at the moment, that's simply to know the number of circuits the panel has. So your config is ok.

I didn't see any change in your logs, AqualinkD is still sending a reply message but the panel is not acknowledging that, so no connection is being established.

Maybe try rs485_frame_delay = 10 in the config to slow the reply message down. Also please check any undervolt status by running the script pi_health.sh in the extras directory. If that does show an undervolt, you should try to fix that issue as that means the USB2RS485 is not getting enough power. (first thing the PI does in undersold situation is remove and/or reduce power from USB devices)

1 reply

bmwhd123 Feb 2, 2025
Author

Output of pi_health.sh

CPU temperature: 34.6
CPU Voltage: 0.9360
Undervolt : OK
Undervolt history : OK
Throttled : OK
Throttled history : OK
Frequency Capped : OK
Frequency Capped history : OK

bmwhd123 · 2025-02-03T19:39:20Z

bmwhd123
Feb 3, 2025
Author

This has been resolved by replacing with a higher rev control panel as described in this thread. The old PDA panel I had just couldn't hack it.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Need help with getting connected. #381

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 9 comments 22 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Need help with getting connected. #381

bmwhd123 Jan 29, 2025

Replies: 9 comments · 22 replies

sfeakes Jan 29, 2025 Maintainer

bmwhd123 Jan 29, 2025 Author

sfeakes Jan 29, 2025 Maintainer

bmwhd123 Jan 29, 2025 Author

sfeakes Jan 29, 2025 Maintainer

bmwhd123 Jan 30, 2025 Author

bmwhd123 Jan 30, 2025 Author

bmwhd123 Jan 30, 2025 Author

bmwhd123 Jan 30, 2025 Author

bmwhd123 Jan 30, 2025 Author

sfeakes Jan 30, 2025 Maintainer

bmwhd123 Jan 31, 2025 Author

sfeakes Jan 31, 2025 Maintainer

bmwhd123 Jan 31, 2025 Author

sfeakes Jan 31, 2025 Maintainer

bmwhd123 Jan 31, 2025 Author

sfeakes Jan 31, 2025 Maintainer

bmwhd123 Jan 31, 2025 Author

sfeakes Jan 31, 2025 Maintainer

bmwhd123 Jan 31, 2025 Author

sfeakes Jan 31, 2025 Maintainer

bmwhd123 Jan 31, 2025 Author

bmwhd123 Feb 1, 2025 Author

bmwhd123 Feb 2, 2025 Author

sfeakes Feb 2, 2025 Maintainer

bmwhd123 Feb 2, 2025 Author

bmwhd123 Feb 3, 2025 Author

bmwhd123
Jan 29, 2025

Replies: 9 comments 22 replies

sfeakes
Jan 29, 2025
Maintainer

bmwhd123
Jan 29, 2025
Author

sfeakes
Jan 29, 2025
Maintainer

bmwhd123 Jan 29, 2025
Author

sfeakes
Jan 29, 2025
Maintainer

bmwhd123 Jan 30, 2025
Author

bmwhd123 Jan 30, 2025
Author

bmwhd123 Jan 30, 2025
Author

bmwhd123 Jan 30, 2025
Author

bmwhd123 Jan 30, 2025
Author

sfeakes
Jan 30, 2025
Maintainer

bmwhd123 Jan 31, 2025
Author

sfeakes
Jan 31, 2025
Maintainer

bmwhd123 Jan 31, 2025
Author

sfeakes Jan 31, 2025
Maintainer

bmwhd123 Jan 31, 2025
Author

sfeakes Jan 31, 2025
Maintainer

bmwhd123 Jan 31, 2025
Author

sfeakes
Jan 31, 2025
Maintainer

bmwhd123 Jan 31, 2025
Author

sfeakes Jan 31, 2025
Maintainer

bmwhd123 Jan 31, 2025
Author

bmwhd123 Feb 1, 2025
Author

bmwhd123 Feb 2, 2025
Author

sfeakes
Feb 2, 2025
Maintainer

bmwhd123 Feb 2, 2025
Author

bmwhd123
Feb 3, 2025
Author