CORDET Framework - C2 Implementation
|
Implementation of Event Reporting Service (PUS Service 5) More...
Files | |
file | CrPsUtilitiesServEvt.c |
Implementation of the utility functions of the CORDET Framework PUS Extension Service 5 (Event Reporting) | |
file | CrPsUtilitiesServEvt.h |
Interface through which applications can initialize and execute framework PUS extension components. | |
file | CrPsDpServEvt.c |
Interface for accessing data pool items. | |
file | CrPsDpServEvt.h |
Interface for accessing data pool items. | |
file | CrPsEvtDisableCmd.c |
Implementation of TC(5,6) EvtDisableCmd. | |
file | CrPsEvtDisableCmd.h |
Implementation of TC(5,6) EvtDisableCmd. | |
file | CrPsEvtEnableCmd.c |
Implementation of TC(5,5) EvtEnableCmd. | |
file | CrPsEvtEnableCmd.h |
Implementation of TC(5,5) EvtEnableCmd. | |
file | CrPsEvtRepDisabledCmd.c |
Implementation of TC(5,7) EvtRepDisabledCmd. | |
file | CrPsEvtRepDisabledCmd.h |
Implementation of TC(5,7) EvtRepDisabledCmd. | |
file | CrPsEvtRep.h |
Implementation of TM(5,x) EvtRep. | |
file | CrPsEvtRepDisabledRep.c |
Implementation of TM(5,8) EvtRepDisabledRep. | |
file | CrPsEvtRepDisabledRep.h |
Implementation of TM(5,8) EvtRepDisabledRep. | |
file | CrPsCmd5EidStartCreate.c |
Create one instance of the CrPsCmd5EidStart procedure. | |
file | CrPsCmd5EidStartCreate.h |
Create one instance of the CrPsCmd5EidStart procedure. | |
file | CrPsCmd5EidStartFunc.c |
Create one instance of the CrPsCmd5EidStart procedure. | |
file | CrPsPktServEvt.h |
Interface for accessing fields in packets of service "ServEvt". | |
file | CrPsPktServEvtSupp.c |
auxiliary Interface for accessing fields in packets of service "ServEvt". | |
file | CrPsPktServEvtSupp.h |
auxiliary Interface for accessing fields in packets of service "ServEvt". | |
Implementation of Event Reporting Service (PUS Service 5)
The event reporting service provides the capability to report event-like occurrences and to control the generation of event reports by enabling and disabling individual event identifiers.
The PUS recognizes four levels of event reports and associates to each level a service sub- type. Thus, for instance, all event reports of level 1 are carried by reports of type (5,1) and all event reports of level 2 are carried by event reports of type (5,2). All event reports have the same behaviour irrespective of their level. The PUS Extension of the CORDET Framework consequently defines one single component which may encapsulate an event report of any level.
Event reports may carry data. The Event Identifier (EID) determines the format of the data associated to an event report. The PUS Extension accordingly treats the event identifier as a discriminant. The range of discriminants and the data associated to each discriminant are adaptation points which must be defined at application level. No event identifiers are pre-defined at framework level.