custom storage feature added to Plane:4.6.2#13
Open
Dineshborse wants to merge 1 commit intoairbound-develop-4.6from
Open
custom storage feature added to Plane:4.6.2#13Dineshborse wants to merge 1 commit intoairbound-develop-4.6from
Dineshborse wants to merge 1 commit intoairbound-develop-4.6from
Conversation
…e handler to plane version 4.6.2
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi, This feature is "Custom Storage and Custom Mavlink Message Handler"
Its same as for plane:4.5.7x version but now added for Plane:4.6.2 version
Documentation Notion Link: link
Summary:
Goal: To give a drone a persistent, unique identity (UUID and Password) for fleet management.
Core Feature: Stores the UUID and Password in flash memory so they survive reboots.
Control: A Ground Control Station can remotely read and write this data using a custom MAVLink message (ID 15222).
Setup: Requires enabling a specific build flag (--enable-custom-storage) and a one-time hardware configuration.
Limitation: The initial version does not encrypt data; it is stored and sent as plaintext.