diff --git a/docs/cFE Application Developers Guide.md b/docs/cFE Application Developers Guide.md index dc4c0cb26..302b9fd2e 100644 --- a/docs/cFE Application Developers Guide.md +++ b/docs/cFE Application Developers Guide.md @@ -2365,19 +2365,7 @@ consistent style of writing in all messages. One should consult, if possible, with members of the Flight Operations team and scientists to find what kind of messages are required and how they should be worded. -## 7.6 Event Service Un-registration - -Applications that have registered with the EVS can un-register -themselves. The cFE, however, will automatically un-register an -Application when the Application is terminated. An example of the -function call to perform un-registration from within an Application is -shown below: - -``` -CFE_EVS_Unregister (); -``` - -## 7.7 Best Practices for using Event Services +## 7.6 Best Practices for using Event Services The following are recommended "best practices" for applications using EVS. 1. Event Message IDs should be unique across an application so that an diff --git a/docs/cFE_FunctionalRequirements.csv b/docs/cFE_FunctionalRequirements.csv index 8793bb771..f1f90f1d4 100644 --- a/docs/cFE_FunctionalRequirements.csv +++ b/docs/cFE_FunctionalRequirements.csv @@ -259,14 +259,6 @@ EVS: Register App,cEVS3100,"Upon receipt of Request, the cFE shall register an A EVS: Register App - Create Filter Counter,cEVS3100.1,"Upon receipt of Request to register an Application for event service, the cFE shall create one Application Binary Filter Counter per registered Event ID.",Supports the cFE's Binary Filtering Algorithm. EVS: Register App - Create Sent Message Counter,cEVS3100.2,"Upon receipt of Request to register an Application for event service, the cFE shall create an Application Event Message Sent Counter.",Supports the cFE's dynamic Application model. EVS: Register App - Default Event Enable Status,cEVS3100.3,"Upon receipt of Request to register an Application for event service, the cFE shall use the `` Application Event Type Enable Statuses for each event.","By default each platform should have a standard configuration for each event message type (eg. DEBUGs disable. INFO, ERROR and CRITICAL events DISABLED) that should be applied to all events. Commands are available to modify the settings." -EVS: Unregister App,cEVS3101,"Upon receipt of Request, the cFE shall un-register an Application from using event services, deleting the following Application data: - -- Application Event Message Sent Counter -- Application Event Service Enable Status -- Application Event Type Enable Statuses (one for each Event Type) -- Application Filtered Event IDs -- Application Binary Filter Masks (one per registered Event ID) -- Application Binary Filter Counters (one per registered Event ID)",Supports the cFE's dynamic Application model allowing applications to clean up after themselves. EVS: Message Types,cEVS3102,The cFE shall support the following Event Message Types: Debug Informational Error Critical.,Supports cFE event services. EVS: Create Message,cEVS3103,"Upon receipt of a Request to send an Event Message, the cFE shall create a Short or Long Event Message, as specified by the SB Event Format Mode, ONLY if the following cFE conditions are met: diff --git a/docs/src/cfe_api.dox b/docs/src/cfe_api.dox index b09273272..19c3d99f7 100644 --- a/docs/src/cfe_api.dox +++ b/docs/src/cfe_api.dox @@ -80,7 +80,6 @@
  • \ref CFEAPIEVSReg
  • \ref CFEAPIEVSSend