You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
logMessage(LOG_WARNING, "Serial read bad checksum, ignoring\n");
Currently seeing 6-7 bad checksum errors per day
Does adding ground wire reduce rate of checksum errors?
Add historical PM counter files in /var to better keep track (monthly folder, day of month file)
reads are byte by byte add inter message timeout that is ~50ms (number to be validated). The checksum errors seem to be the result of a partial message prepended on next valid message.
pi@raspberrypi:~ $ journalctl _PID=9384 | cat
-- Logs begin at Fri 2019-09-06 15:35:06 CDT, end at Wed 2019-09-11 10:08:01 CDT. --
Sep 08 11:30:01 raspberrypi CRON[9384]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 08 11:30:01 raspberrypi CRON[9384]: pam_unix(cron:session): session closed for user root
Sep 10 06:01:20 raspberrypi aqualinkd[9384]: Starting web server on port 80
Sep 10 06:01:20 raspberrypi aqualinkd[9384]: Starting MQTT client to (null)
Sep 10 06:01:20 raspberrypi aqualinkd[9384]: Listening to Aqualink RS8 on serial port: /dev/ttyUSB0
Sep 10 06:01:20 raspberrypi aqualinkd[9384]: AqualinkD is using PDA mode
Sep 10 07:19:15 raspberrypi aqualinkd[9384]: Serial read bad checksum, ignoring
Sep 10 07:19:15 raspberrypi aqualinkd[9384]: Bad receive packet | Jandy | HEX: 0x10|0x02|0x62|0x04|0xf1|0xb5|0x9f|0xac|0x0b|0x12|0x92|0x1c|0xa2|0xe0|0x10|0x02|0x62|0x04|0x01|0x20|0x50|0x44|0x41|0x2d|0x50|0x53|0x34|0x20|0x43|0x6f|0x6d|0x62|0x6f|0x20|0x20|0xc2|0x10|0x03|
Sep 10 07:22:48 raspberrypi aqualinkd[9384]: Serial read bad checksum, ignoring
Sep 10 07:22:48 raspberrypi aqualinkd[9384]: Bad receive packet | Jandy | HEX: 0x10|0x02|0x62|0x04|0x08|0x45|0xfc|0x20|0x4f|0x46|0x46|0x6d|0x10|0x03|
Sep 10 13:00:19 raspberrypi aqualinkd[9384]: Serial read bad checksum, ignoring
Sep 10 13:00:19 raspberrypi aqualinkd[9384]: Bad receive packet | Jandy | HEX: 0x10|0x02|0x62|0x1b|0x00|0x00|0x8f|0x10|0xe3|0x10|0x02|0x62|0x1b|0x00|0x00|0x8f|0x10|0x03|
Sep 10 20:04:38 raspberrypi aqualinkd[9384]: Serial read bad checksum, ignoring
Sep 10 20:04:38 raspberrypi aqualinkd[9384]: Bad receive packet | Jandy | HEX: 0x10|0x02|0x62|0x09|0x64|0x5f|0x40|0x10|0x83|0x10|0x02|0x62|0x04|0x01|0x20|0x50|0x44|0x41|0x2d|0x50|0x53|0x34|0x20|0x43|0x6f|0x6d|0x62|0x6f|0x20|0x20|0xc2|0x10|0x03|
Sep 10 20:55:02 raspberrypi aqualinkd[9384]: Serial read bad checksum, ignoring
Sep 10 20:55:02 raspberrypi aqualinkd[9384]: Bad receive packet | Jandy | HEX: 0x10|0x02|0x62|0x04|0xf9|0x02|0x1e|0x24|0x24|0x48|0x48|0x5d|0x88|0xe0|0x10|0x02|0x62|0x04|0x09|0x41|0x4c|0x4c|0x20|0x4f|0x46|0x46|0x20|0x20|0x20|0x20|0x20|0x20|0x20|0x20|0x20|0x75|0x10|0x03|
Sep 10 23:43:27 raspberrypi aqualinkd[9384]: Serial read bad checksum, ignoring
Sep 10 23:43:27 raspberrypi aqualinkd[9384]: Bad receive packet | Jandy | HEX: 0x10|0x02|0x62|0x04|0x01|0x46|0x49|0xec|0xca|0x94|0x14|0x83|0x34|0xfc|0x10|0x02|0x62|0x04|0x01|0x46|0x49|0x4c|0x54|0x45|0x52|0x20|0x50|0x55|0x4d|0x50|0x20|0x20|0x4f|0x46|0x46|0xbc|0x10|0x03|
Sep 11 04:25:41 raspberrypi aqualinkd[9384]: Serial read bad checksum, ignoring
Sep 11 04:25:41 raspberrypi aqualinkd[9384]: Bad receive packet | Jandy | HEX: 0x10|0x02|0x62|0xfb|0x10|0x02|0x62|0x1b|0x00|0x00|0x8f|0x10|0x03|
Sep 11 07:44:34 raspberrypi aqualinkd[9384]: Serial read bad checksum, ignoring
Sep 11 07:44:34 raspberrypi aqualinkd[9384]: Bad receive packet | Jandy | HEX: 0x10|0x02|0xfa|0x55|0x53|0xa8|0x90|0x20|0x20|0x4f|0x4e|0x9e|0x10|0x03|
Sep 11 09:44:28 raspberrypi aqualinkd[9384]: Serial read bad checksum, ignoring
Sep 11 09:44:28 raspberrypi aqualinkd[9384]: Bad receive packet | Jandy | HEX: 0x10|0x02|0x62|0x1b|0x00|0xc0|0x10|0x02|0x62|0x1b|0x00|0x00|0x8f|0x10|0x03|
pi@raspberrypi:~ $
The text was updated successfully, but these errors were encountered:
AqualinkD/aq_serial.c
Line 561 in 8657b39
Currently seeing 6-7 bad checksum errors per day
The text was updated successfully, but these errors were encountered: