feat: CCS & ARINCs 429, 664 #14
Draft
Conversation
This file contains 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.
Problem
Currently the only method of communicating data between aircraft systems is simvars, we have no way of checking data validity or transfer speeds.
Solution
Model the aircraft communications "brain" known as the Common Core System (CCS) to serve as the single source of truth for simvar distribution. The goal of this PR is to have the CCS serve as the center for initializing current LVars, as well as setting and getting as needed through the current LVar interface.
Non C++ aircraft systems/components
Some aircraft components will remain in Typescript and other languages may be added down the line. To interface with the CCS directly, LVars can be queried until a proper ARINC interface for each language is built.