-
Notifications
You must be signed in to change notification settings - Fork 198
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
CFE_ES_OneAppTlm_Payload_t telemetry struct contains non mission-scoped-sized array #705
Comments
Yes, this is an issue! Not intended. I would call it a bug because it creates an unintended/invalid dependency on |
skliper
added a commit
to skliper/cFE
that referenced
this issue
Sep 22, 2020
skliper
added a commit
to skliper/cFE
that referenced
this issue
Oct 2, 2020
astrogeco
added a commit
that referenced
this issue
Oct 2, 2020
Fix #705, Use cFE defines to size arrays
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Unsure if this is intentional, but
CFE_ES_AppInfo_t
is directly used byCFE_ES_OneAppTlm_Payload_t
which is ground visible.CFE_ES_AppInfo_t
usesOS_MAX_*
, whereas all other ground-visible telemetry uses the mission-scopedCFE_MISSION_MAX_*
.Describe the solution you'd like
CFE_ES_OneAppTlm_Payload_t
should be structured such that the size is dependent solely on mission-scoped constants and consistent amongst all CPUs.This is an enhancement as opposed to a bug report since in practice both constants are likely to be same.
Describe alternatives you've considered
None
Additional context
None
Requester Info
John N Pham, Northrop Grumman
The text was updated successfully, but these errors were encountered: