ALL
EFFECTIVITY
© Honeywell International Inc. Do not copy without express permission of Honeywell.
Page 2-13
22 Apr 2019
23-15-49
SYSTEM DESCRIPTION, INSTALLATION, AND MAINTENANCE MANUAL
ASPIRE-400
(a)
The computed average input level is expressed in dBm to the closest 0.1 dB
resolution
(b)
The numeric value to be conveyed is "Numeric Value" = ("computed average
input level (dBm)" - (-45dBm)) / 0.1 dB
(c)
The numeric value is expressed as a 10-bit unsigned binary number.
(11)
For the current ARINC-429 label 350 reporting interval the following applies:
(a)
If any input power sample is greater than or equal to -30 dBm in the reporting
interval then the "RF Power Input" status is reported as "In Range" in ARINC-
429 label 350 HPA Maintenance word.
(b)
If all of the input power samples are < -30 dBm in the reporting interval then the
"RF Power Input" status is reported as "Low Signal" in ARINC-429 label 350 HPA
Maintenance word.
(12)
For the current ARINC-429 label 143 HPA Status word reporting interval the following
applies:
(a)
If all input samples are < -30 dBm in the reporting interval then the "Actual Power
Out Status" status is reported as "Held Power" in ARINC-429 label 143 HPA
Status word.
(b)
If the PA function is disabled throughout the reporting interval then the "Actual
Power Out Status" status is reported as "Held Power" in ARINC-429 label 143
HPA Status word.
(c)
While the PA function is enabled should any input sample be >= - 30 dBm in the
reporting interval then the "Actual Power Out Status" status is reported as "Actual
Power" in ARINC-429 label 143 HPA Status word.
8.
Controller Functions
A.
Single Event Upset
(1)
The HPA is ruggedized against Single/Multiple Event Upset.
(2)
Implementation may employ redundant memory, error correcting hardware memory,
software correction encoding or other suitable techniques in any combination thereof.
Hardware should select memory types that are proven to be more robust against Single
Event Upset (SEU). Non-volatile memory used to retain Event and Fault Logs is not
required to be robust to Single Event Upset.
(3)
If the processor architecture where the resident application code resides does not include
inherent error detection/correction capability then dual application images are retained for
Single Event Upset management.
(4)
The HPA instigates remedial action on detection of single event corruption to restore the
integrity of affected software or firmware.
(5)
If remedial action resulting from detection of single event corruption does not
compromise the functional operation of the HPA then the event should be recorded to the
Event Record log and operation should continue unabated.
(6)
If remedial action resulting from the detection of single event corruption does affect the
functional operation of the HPA then the HPA does the following: (if able)
(a)
Declares the detection as an inhibition cause to the PA function.
(b)
Immediately latches the Reset Reason register corresponding to "Single Event
Upset".
DRAFT
3rd rvw Draft as of:
29 January, 2020
Summary of Contents for 90402651-000
Page 118: ...D R A F T 3rd rvw Draft as of 29 January 2020 ...
Page 120: ...D R A F T 3rd rvw Draft as of 29 January 2020 ...
Page 122: ...D R A F T 3rd rvw Draft as of 29 January 2020 ...
Page 124: ...D R A F T 3rd rvw Draft as of 29 January 2020 ...
Page 126: ...D R A F T 3rd rvw Draft as of 29 January 2020 ...
Page 128: ...D R A F T 3rd rvw Draft as of 29 January 2020 ...
