Post Install Instability about aqualinkd HOT 12 CLOSED

At first quick glance, it looks like you have a control panel on the same ID as you have AqualinkD set to.
The serial logging tool will log a number of packets quietly, then spit out the result. So maybe that’s why you think it isn’t doing anything. Leave it running for a minute or two and see it it spits out a result. You can also put it in debug mode to print out evey packet rather than being quiet (look at the wiki for instructions).

I’ll give it some more thought, but please try that first.
--edit--
I wrote the above quickly, as I had just glanced at the log and didn't have much time.
Try this, it will print every packet.
sudo ./release/serial_logger /dev/ttyUSB0 -d

Then can you post the result. With the "serial packet too small" errors it will never work correctly. Once you post the above, it may give me a better understanding of what's going on.

from aqualinkd.

Thanks for such a quick response. I started working on it again after work. I changed the AqualinkD to another ID (0X09), but am still seeing a lot "serial read too small" errors. I cleared the log and attached a new one one after I made the change. It does seem to be working with the exception of the Freeze Protection Info only showing up randomly.

aqualinkd2.log

I was also not able to recreate the issues I was having earlier today with the serial logger. Earlier, I tried it multiple times through multiple reboots and it would hang for over 15 minutes every time until I killed the process and then it would give one line of output after that. It ran perfectly every time I ran it tonight and I copied the output with the -d flag to this file. I guess I will chalk that up to user error, but I don't know what I was doing wrong.

serial_logger_output.txt

Again, it is functional and I ran it for several hours tonight and everything seems to work. I do have a 2-speed filter pump and it behaves a little quirky with the low-speed button enabled, but I figure you did not have this setup to test. Just for you feedback, the normal behavior for this is you push the low-speed button on the panel with the filter pump running, the filter LED turns off and the low-speed LED turns on. Then if you push the low-speed button again the pump goes back to full speed. Therefore, the main filter pump LED is off when the filter pump is running in low speed. This all works as expected in AqualinkD, but the Pool Water Temperature reading flickers on and off (mainly off) in the AqualinkD web interface. I doubt there are many of us using 2-speed pool pumps and it does not bother me at all, but I just wanted to let you know what I was seeing with it.

Thanks again for looking helping me with this and let me know if you can make sense of those errors from the log.

from aqualinkd.

I’m away on business at the moment, I’ll need to put some time aside and go over this in more detail. I’ll try to find time at the weekend. But ultimately we need to stop the serial read issues for this to be stable. As long as you’re not running aqualinkd and the serial logging tool at the same time I’m not sure what would be causing this and I’ll need to write some code to see what’s going on.

from aqualinkd.

Ok. I currently have it hooked up to a controller in the house. I may take it outside and hook it directly to the main unit and see if I get less errors there just to eliminate the possibility of cable issues somewhere along the line. Let me know if you find anything when you get a chance.

from aqualinkd.

Out of interest, What distribution & version of Linux are you using?

It’s looks like the serial logger is not getting the packet too small errors, which is very strange, could you try running it over a longer period and see what happens, maybe with -d -p 2000

from aqualinkd.

I've mad a few small changes, please download the latest and see what the logs look like. I simply increased the timeout to wait longer to receive a complete RS485 packet. Don't think it will fix your problem (although it could), but it'll help rule out a few things.

from aqualinkd.

Sorry I was out of town and could not work on this for a few days. I updated software and seem to be having the same errors. I am attaching the new log file and serial logger output to see if that gives you any insight.
aqualinkd.log
Serial_Output.txt

from aqualinkd.

Looks like the serial logger is the new one, but aqualinkd is the old exe. Just checking you ran the install script?

from aqualinkd.

Sorry - I downloaded it, but did not run the script. I just re-downloaded it again and ran the script this time. Here are the new logs after running it again. Thanks for taking the time to look at this.
aqualinkd.log
Serial_logger.txt

from aqualinkd.

Thanks for the logs. Think I've found the problem, and fixed it in the latest update. Please get latest and try again.

from aqualinkd.

I think that did it! I am no longer seeing errors. I am attaching the log after a re-ran it with the latest update just in case you wanted to look at it. But it looks good to me. Thanks again.
aqualinkd.log

from aqualinkd.

Log looks good, it didn’t miss / duplicate or re-read any message. I’ll close this out, thanks for testing.

from aqualinkd.