-
Notifications
You must be signed in to change notification settings - Fork 49
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
include multiple encoding errors in OPEN_DRONE_ID_ARM_STATUS message #102
include multiple encoding errors in OPEN_DRONE_ID_ARM_STATUS message #102
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it would be good to use strncat() instead of strcat() in case we end up with enough to overflow
should we use shorter names? like "SYS" for system?
Implemented a new PR with the requested changes.
|
needs a rebase, sorry |
6075f00
to
a302b59
Compare
did a rebase and squashed the commits. |
a302b59
to
e0fd917
Compare
Seems to be ready for merge, see comment April 3. |
e0fd917
to
ca64a22
Compare
@BluemarkInnovations i've cleaned up the string handling a bit |
In the current implementation, the check_parse fails on the first error whenit encounters bad data in one of the RID packets.
In this PR, the function will collect all bad data errors and include the packets that fail in in the ARM status error field. This is useful in case the data stream has multiple errors. For instance if the system message has an error and the operator ID too, the current implementation would only return that the system message fails.