Skip to content

Indicate detection of failed PM module on display #294

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nick-4711 opened this issue Mar 27, 2025 · 0 comments
Open

Indicate detection of failed PM module on display #294

nick-4711 opened this issue Mar 27, 2025 · 0 comments

Comments

@nick-4711
Copy link
Collaborator

nick-4711 commented Mar 27, 2025

It can happen that a PM module reports very (unrealistically) high _AE and _SP values. Here an example from the field

PM1_AE{1}: 3661.00
PM25_AE{1}: 3661.00 <--
PM10_AE{1}: 3661.00
PM1_SP{1}: 5492.33
PM25_SP{1}: 5492.33 <--
PM10_SP{1}: 5492.33
PM003_PC{1}: 396.33 <--
PM005_PC{1}: 232.67
PM01_PC{1}: 0.00
PM25_PC{1}: 0.00
PM05_PC{1}: 0.00
PM10_PC{1}: 0.00

normal would be something like

PM1_AE{1}: 27.00
PM25_AE{1}: 44.00 <--
PM10_AE{1}: 51.00
PM1_SP{1}: 32.00
PM25_SP{1}: 55.00 <--
PM10_SP{1}: 55.00
PM003_PC{1}: 521.00 <--
PM005_PC{1}: 478.00
PM01_PC{1}: 104.00
PM25_PC{1}: 10.00
PM05_PC{1}: 0.00
PM10_PC{1}: 0.00

Right now

  • these values are dropped (and not transmitted to the backend)
  • we display "-" on the OLED

With this issue we want to change this behavior and

  • transmit the values to the backend to allow to feed this into fault detection algorithms (e.g. Felipe)
  • discuss if we should also deliver such values on the local HTTP server interface or better drop them / or also indicate the failure somehow
  • display "x"? or some other icon indicating failure if we see a value higher than 999?

Maybe we can then use this approach for all measures.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant