Summary
openplotter-pypilot-read intermittently appears to stop or fail publishing attitude updates for short periods, then resumes. In Grafana / Signal K history this shows up as repeated short gaps and sometimes as roll/pitch spikes or decaying artifacts in downstream consumers such as Advanced Wind.
This was observed with the original, unmodified openplotter-pypilot-read, not with a locally modified version.
Environment
- Platform: Raspberry Pi / OpenPlotter
- Service:
openplotter-pypilot-read
- pypilot version seen on system:
pypilot==0.70
- IMU: ICM-20948 / pypilot IMU setup
- Signal K server: local network, port
3000
- Data consumed by:
- Signal K
- Grafana
- Advanced Wind plugin
Symptoms
The attitude is not being updated regularly for multiple seconds, this can be seen especially well in grafana.
In Grafana, navigation.attitude.roll and navigation.attitude.pitch show intermittent short interruptions every few seconds/minutes. The values are normally stable near zero, but the time series has repeated discontinuities/gaps.
Actual behavior
The Signal K websocket connection is eventually lost with:
Connection to remote host was lost.
timed out
Then openplotter-pypilot-read reconnects and continues.
Suspected cause
The websocket send path appears to publish data but does not continuously drain/read from the websocket.
Summary
openplotter-pypilot-readintermittently appears to stop or fail publishing attitude updates for short periods, then resumes. In Grafana / Signal K history this shows up as repeated short gaps and sometimes as roll/pitch spikes or decaying artifacts in downstream consumers such as Advanced Wind.This was observed with the original, unmodified
openplotter-pypilot-read, not with a locally modified version.Environment
openplotter-pypilot-readpypilot==0.703000Symptoms
The attitude is not being updated regularly for multiple seconds, this can be seen especially well in grafana.
In Grafana,
navigation.attitude.rollandnavigation.attitude.pitchshow intermittent short interruptions every few seconds/minutes. The values are normally stable near zero, but the time series has repeated discontinuities/gaps.Actual behavior
The Signal K websocket connection is eventually lost with:
Connection to remote host was lost.
timed out
Then openplotter-pypilot-read reconnects and continues.
Suspected cause
The websocket send path appears to publish data but does not continuously drain/read from the websocket.