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
When I upgraded from an older pi 1 B to a pi 4 things became unstable. Not just with aqualinkd but also with aquaweb. What I would see on aquaweb is while attempting to navigate the panel would go back to the version screen but there were no bad packets coming from the panel. When I turned on debug the problem would go away.
No spec for aqualink protocol but looking at similar RS-485 protocol https://www.tascam.eu/en/docs/MX-8A_RS-485_protocol.pdf there is a min frame to frame time of 4 ms. I instrumented aqualinkd and could see frame to frame times consistently of 0.02 ms turning on debug brought the time up to ~0.1 ms
When I upgraded from an older pi 1 B to a pi 4 things became unstable. Not just with aqualinkd but also with aquaweb. What I would see on aquaweb is while attempting to navigate the panel would go back to the version screen but there were no bad packets coming from the panel. When I turned on debug the problem would go away.
No spec for aqualink protocol but looking at similar RS-485 protocol https://www.tascam.eu/en/docs/MX-8A_RS-485_protocol.pdf there is a min frame to frame time of 4 ms. I instrumented aqualinkd and could see frame to frame times consistently of 0.02 ms turning on debug brought the time up to ~0.1 ms
See Also
ballle98#87
ballle98/aquaweb#7
stdout-20231114_1231.txt
The text was updated successfully, but these errors were encountered: