Fix #103, add option to configure base tick rate #104
Merged
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.
Describe the contribution
SCH_LAB was fixed at 1Hz because it bound to the 1Hz tick from CFE_TIME. This creates an OSAL timer instead, which posts a semaphore, and this can serve as a much more flexible time source, with configurable rate.
This still binds to 1Hz and the SCH does not start its first message until the first 1Hz is received, thereby keeping some form of 1Hz sync.
Fixes #103
Testing performed
Used this feature to send wakeup events to CF at 10hz instead of 1hz. (Locally configurable - other items in the table got changed from 4 to 40 to compensate and keep those at 0.25 Hz.)
Expected behavior changes
More configuration flexibility.
System(s) tested on
Ubuntu
Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.