|
181 | 181 | commands as a response to this condition. |
182 | 182 |
|
183 | 183 | Actionpoints can be individually enabled/disabled with the #LC_SET_AP_STATE_CC ground |
184 | | - command. The state of an actionpoint may be set to #LC_APSTATE_ACTIVE, #LC_APSTATE_PASSIVE, |
185 | | - or #LC_APSTATE_DISABLED. These states operate in the same way as the application operating |
186 | | - modes described above. #LC_APSTATE_PASSIVE will just disable RTS requests, while |
187 | | - #LC_APSTATE_DISABLED will stop evaluation of the actionpoint all together. An additional |
188 | | - state #LC_APSTATE_PERMOFF which functions the same as #LC_APSTATE_DISABLED but can only |
| 184 | + command. The state of an actionpoint may be set to #LC_ActionPointState_ACTIVE, #LC_ActionPointState_PASSIVE, |
| 185 | + or #LC_ActionPointState_DISABLED. These states operate in the same way as the application operating |
| 186 | + modes described above. #LC_ActionPointState_PASSIVE will just disable RTS requests, while |
| 187 | + #LC_ActionPointState_DISABLED will stop evaluation of the actionpoint all together. An additional |
| 188 | + state #LC_ActionPointState_PERMOFF which functions the same as #LC_ActionPointState_DISABLED but can only |
189 | 189 | be changed via table load, can be set using the #LC_SET_AP_PERM_OFF_CC ground command |
190 | 190 | (see \ref cfslcfaqs). |
191 | 191 |
|
|
259 | 259 | In the lc_platform_cfg.h file, there are configuration parameters that control use |
260 | 260 | of the Critical Data Store (CDS) and the LC operation mode on application |
261 | 261 | initialization. The default case is not to use the CDS and to set the application |
262 | | - state to #LC_STATE_DISABLED. |
| 262 | + state to #LC_AppState_DISABLED. |
263 | 263 | **/ |
264 | 264 |
|
265 | 265 | /** |
|
302 | 302 | The entire ADT is processed any time a sample request is received that specifies an |
303 | 303 | actionpoint equal to #LC_ALL_ACTIONPOINTS. For this reason, it is important that unused |
304 | 304 | entries are properly marked by setting the ADT parameter DefaultState to |
305 | | - #LC_APSTATE_NOT_USED. |
| 305 | + #LC_ActionPoint_NOT_USED. |
306 | 306 |
|
307 | 307 | When either the WDT or ADT are updated, the corresponding results table (WRT or ART) is |
308 | 308 | reset to initialization values. For each entry in the WRT, WatchResult is set to |
|
523 | 523 | three possible conditions are true: |
524 | 524 |
|
525 | 525 | 1) The actionpoint is unused (the DefaultState in the ADT is set to |
526 | | - #LC_APSTATE_NOT_USED). |
| 526 | + #LC_ActionPoint_NOT_USED). |
527 | 527 |
|
528 | 528 | 2) An actionpoint sample request (#LC_SAMPLE_AP_MID) targeting the AP has not |
529 | 529 | yet been received by LC so the AP has not yet been evaluated. |
|
551 | 551 | </I> |
552 | 552 |
|
553 | 553 | <B> (Q) |
554 | | - How does the Actionpoint state #LC_APSTATE_PERMOFF differ from |
555 | | - #LC_APSTATE_DISABLED? |
| 554 | + How does the Actionpoint state #LC_ActionPointState_PERMOFF differ from |
| 555 | + #LC_ActionPointState_DISABLED? |
556 | 556 | </B> <BR> <BR> <I> |
557 | | - The AP state #LC_APSTATE_PERMOFF is intended to provide a way to disable |
| 557 | + The AP state #LC_ActionPointState_PERMOFF is intended to provide a way to disable |
558 | 558 | an AP so it can not easily be turned back on by mistake. Such actionpoints |
559 | 559 | may not be needed after a seperation sequence or only apply to certain |
560 | 560 | mission phases. |
561 | 561 |
|
562 | 562 | While the two states are treated the same way during actionpoint processing |
563 | 563 | (the AP isn't evaluated), there are a few differences. |
564 | 564 |
|
565 | | - An AP can't be set to #LC_APSTATE_PERMOFF with the #LC_SET_AP_STATE_CC command, |
| 565 | + An AP can't be set to #LC_ActionPointState_PERMOFF with the #LC_SET_AP_STATE_CC command, |
566 | 566 | it must be done with the #LC_SET_AP_PERM_OFF_CC command. |
567 | 567 |
|
568 | | - To set an AP to #LC_APSTATE_PERMOFF with the #LC_SET_AP_PERM_OFF_CC command, the |
569 | | - current AP state must be #LC_APSTATE_DISABLED. |
| 568 | + To set an AP to #LC_ActionPointState_PERMOFF with the #LC_SET_AP_PERM_OFF_CC command, the |
| 569 | + current AP state must be #LC_ActionPointState_DISABLED. |
570 | 570 |
|
571 | 571 | The #LC_SET_AP_PERM_OFF_CC command can only be issued for a single actionpoint, |
572 | 572 | #LC_ALL_ACTIONPOINTS is not valid as an argument for this command. |
573 | 573 |
|
574 | | - Once an AP is set to #LC_APSTATE_PERMOFF, it can only be changed with a new ADT |
| 574 | + Once an AP is set to #LC_ActionPointState_PERMOFF, it can only be changed with a new ADT |
575 | 575 | table load. |
576 | 576 | </I> |
577 | 577 |
|
|
592 | 592 | #LC_HKAR_STATE_NOT_USED, #LC_HKAR_STATE_ACTIVE, #LC_HKAR_STATE_PASSIVE, |
593 | 593 | #LC_HKAR_STATE_DISABLED |
594 | 594 |
|
595 | | - An actionpoint whose current state is #LC_APSTATE_PERMOFF will have it's |
| 595 | + An actionpoint whose current state is #LC_ActionPointState_PERMOFF will have it's |
596 | 596 | state reported in the APResults as #LC_HKAR_STATE_NOT_USED. |
597 | 597 |
|
598 | 598 | The numerical 2 bit values for evaluation results are defined using the |
|
614 | 614 | Will an RTS get requested more than once if an AP stays in the #LC_ACTION_FAIL |
615 | 615 | state? |
616 | 616 | </B> <BR> <BR> <I> |
617 | | - No. Assuming the current state of an actionpoint is #LC_APSTATE_ACTIVE, then |
| 617 | + No. Assuming the current state of an actionpoint is #LC_ActionPointState_ACTIVE, then |
618 | 618 | when the actionpoint fails enough times to trigger an RTS, the state is set |
619 | | - to #LC_APSTATE_PASSIVE. |
| 619 | + to #LC_ActionPointState_PASSIVE. |
620 | 620 |
|
621 | 621 | In the passive state, the AP will continue to be sampled and statistics |
622 | 622 | updated, but no RTS requests will be initiated. |
|
0 commit comments