Closed
Conversation
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.
I have done a test implementation, but first of all we must find out, if adding more broadcast address is a adequate solution for use with param_publish.
The feature is implemented by extending the number of nodes allocated for broadcast on selected nodes (typically OBCs)
AOCS OBC requirements
Listening for typically small unsolicited packets, coming with high frequency
HK/FDIR OBC requirements
Cover larger incoming packets, coming with a lower frequency
Will often collect data published for AOCS also
Broadcast size 1 (default, and only option today) is used for most nodes, to allow a client to request all nodes to reply to e.g. an ident request.
Broadcast size 2 will be used by the Space Inventor AOCS processing nodes, which will allow unsolicited data messages from sensors to arrive at multiple AOCS instances without requiring an explicit data request, and without having the sensor data multiplied on the bus for each recipient.
Broadcast size 3 will be used by the Space Inventor OBCs responsible for collecting log and health data. Nodes will send messages for expected or unexpected events (e.g. MCU reboot, undervoltage). The OBC collecting this data, will implicitely also receive sensor data intended for AOCS usage.