Skip to content
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

Uplink Payload Formatter: Implement handling of invalid data #34

Closed
matthias-bs opened this issue May 23, 2024 · 0 comments · Fixed by #40
Closed

Uplink Payload Formatter: Implement handling of invalid data #34

matthias-bs opened this issue May 23, 2024 · 0 comments · Fixed by #40
Assignees
Labels
enhancement New feature or request Prio 2

Comments

@matthias-bs
Copy link
Owner

matthias-bs commented May 23, 2024

Currently, invalid signals transmitted in the uplink message are decoded like any other data.
PayloadBresser.cpp now uses special values to indicate invalid data:

// Encoding of invalid values
#define INV_FLOAT 0x3FFFFFFF 
#define INV_UINT32 0xFFFFFFFF
#define INV_UINT16 0xFFFF
#define INV_UINT8 0xFF
#define INV_TEMP 327.67

The Uplink Payload Formatter shall omit output data in the JSON message for any input data encoded as invalid.

@matthias-bs matthias-bs self-assigned this May 23, 2024
@matthias-bs matthias-bs added enhancement New feature or request Prio 2 labels May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Prio 2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant