Checksum errors when PDA is turned on #277
Replies: 5 comments 10 replies
-
|
PDA only boards can only handle one device at a time unfortunately. There is a setting in aqualinkd.conf for this. Your description does sound like the PDA wire termination is conflicting some how with the RS485 termination. |
Beta Was this translation helpful? Give feedback.
-
|
My panel has two RS485 blocks, and I used the empty one....I suppose the other is for the remote. So I didn't have to wire it on top of another, should be just on the bus. sleep_mode is set to yes, and I made sure no browsers were open. Output using the -d option looks like below, and continues even when remote is turned off. Warning: RS Serial: Serial read bad Jandy checksum, ignoring Attached is a picture of the RS485 connection.
|
Beta Was this translation helpful? Give feedback.
-
|
Your connection looks good. What version of AqualinkD are you using? |
Beta Was this translation helpful? Give feedback.
-
|
Have you got a Salt Water Generator connected to the RS485 bus? Can you post AqualinkD version and config file you are using. |
Beta Was this translation helpful? Give feedback.
-
|
Aqualink Daemon v2.3.3 Output from serial logger with remote on: Notice: RS Serial: Suggested aqualinkd.conf values Now if I run without the remote turned on: Notice: RS Serial: Suggested aqualinkd.conf values |
Beta Was this translation helpful? Give feedback.
-
|
Also, I do have an SWG installed. |
Beta Was this translation helpful? Give feedback.
-
|
I’m sorry can you post the full output from serial_logger, (maybe run it standalone if you aren’t already). I’m looking to see if you get any checksum errors with just using the serial_logger, and also looking to see if serial_logger can pull the panel info. Nothing to do with your current problem, but what’s very interesting here is it looks like your panel can also communicate on 0x33 which is a OneTouch ID. I’ve never seen any PDA only panel that can use anything other than 0x60, the PDA id. And I see a bug in serial_logger due to this, the recommended settings it’s telling you are wrong. Extended_device_id is invalid for PDA only panels at the moment, but if that truely is available, I could make PDA only panels a far more stable in AqualinkD |
Beta Was this translation helpful? Give feedback.
-
|
AqualinkD serial_logger V2.0 Notice: RS Serial: RS485 interface received 1000 packets in 30 seconds (~33.33 Msg/Sec) Notice: RS Serial: Suggested aqualinkd.conf values |
Beta Was this translation helpful? Give feedback.
-
|
This is with the remote on: Notice: RS Serial: RS485 interface received 1000 packets in 24 seconds (~41.67 Msg/Sec) Notice: RS Serial: Suggested aqualinkd.conf values |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for all the details, I'm not seeing anything out of the ordinary here. I'm not sure this is a wiring issue, but since it's the only device on that block. Try Terminate the RS485, you can do this by connecting Brown / Green wires together on the end of the adapter. If that doesn't improve, try changing the timing of the RS485 connection in aqualinkd.conf change |
Beta Was this translation helpful? Give feedback.
-
|
@keith-alphonso I used to have an older PDA-4 combo board (FW version 1.2). With that controler I could use a PDA and aqualinkd at the same time. It would pobe for multiple PDAs (0x60, 0x61,0x62, 0x63). So I configured aqualinkd at 0x62 and left PDA configured to 0x60. When aqualinkd 0x62 was active it would not probe 0x60 but when it went to sleep (stopped acking messages from control panel) the control panel would probe for all the PDA device IDs and the PDA could start a session. Basically the RS485 is a party line where everyone sees the messages for everyone else you ignore the messages that are not for your device ID. I just had to replace my control panel with a newer zodiac board PDA-PS6 Combo FW ver 7.1.0. I noticed this controller only probes one PDA ID 0x60 so I had to change my aqualinkd config to use this ID. I don't think you can have aqualinkd running and use a PDA with this board because I'm not aware of a state machine in aqualinkd that knows if to ignore messages sent to it's ID if it wakes up and has not seen a probe since it woke up. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, so same problem here. I don't need the remote very often, but when I do need it I want to make it fairly easy. I created a workaround (hack). I used xinetd to create 2 services, one to stop aqualinkd and one to start it, and run each on a different port. The stop service stops aqualinkd and outputs a small html file that provides a link to the start service. The start service starts the aqualinkd and outputs a small html file that redirects the user to the original page. I then edited controller to add a small button that calls the stop service. So I now have a button on my phone remote to enable the PDA remote for when I need to use it. Problem solved. A far more elegant solution would be to add a button to disable the RS485 processing, but leave everything else running, then a button to re-enable it. I just don't have time to figure out how to do that at the moment. |
Beta Was this translation helpful? Give feedback.
-
|
for reference I found where I originally got this working in 2019 #40 but this was with a control panel supporting multiple PDA ids. The fix for this issue on my fork will get you closer to working - ballle98#26 need to rework the pda_shouldSleep() function so that when it's about to wake up it sets _pda_first_probe_recvd to false when loop count is set to 0 and return true. might be able to do a dev branch that you could try. I didn't hook up my PDA when I replaced the panel. I use https://github.com/earlephilhower/aquaweb when I need to configure the panel. After I got aqualinkd connected to openhab and then to alexa and google no one ever used the pda it was faster to say "alexa turn on filter pump". I see there is new simulor pages added to aqualinkd but they don't work on PDA panels yet :( |
Beta Was this translation helpful? Give feedback.
-
|
Try this dev branch. Make sure not to have a web browser open to aqualinkd as that will keep it awake. Also make sure "pda_sleep_mode = yes" is set in /etc/aqualinkd.conf. When aqualinkd is sleeping for 30 sec between refreshes if you turn your physical PDA on aqualinkd should stay asleep until the physical PDA is off. You can test it like so If it works otherwise |
Beta Was this translation helpful? Give feedback.
-
|
What I have now will probably work for me, as you say since i have the phone remote I should not need the PDA very often. Once I get the scheduler setup on aqualinkd the only thing I would need the PDA for is to change the color of the lights. One other wish that I have is to show the messages sent by the system to the PDA, as this can clear some confusion that occurs. for example, trying to turn off the filter pump while the heater is on will return "Pump to remain on during cooldown" and when switching to spa mode the message "Pump will turn on after delay". Not having these messages can confuse the user as they think it is non-responsive. |
Beta Was this translation helpful? Give feedback.
-
I've got pretty much everything working on my (unfortunate) PDA-only board (PDA PS-8 combo). The only problem I have is that I cannot use the original PDA. As soon as I turn on the PDA I get a string of bad checksum errors, which then never stop even if I turn off the remote. I'm thinking some thing to do with the RS485 wiring, but I'm not sure how to test or resolve. I'm using a raspberry pi zero W with the RS485 adapter suggested in the wiki (FTDI USB-RS485-WE-1800-BT Cable, USB to RS485 Serial, 1.8M, Wire END). I connected the data+ and data- wires only. I tried also connecting the ground (black) wire to common, but that didn't help anything.
Any help appreciated!!
Beta Was this translation helpful? Give feedback.
All reactions