ATA 27 EFCS Troubleshooting Tipspdf

A320FAM.
qxp:ASMA-Booklet cover
17/03/11
10:40
Page 1
Aircraft System Maintenance Aids

Reference: SEEL5 SA27TM1100002 - 02/2011
A320 Family
Electrical Flight Control System
ELAC/SEC/FCDC/Wiring Interface
TROUBLE SHOOTING TIPS
FOR MAINTENANCE USE
Aim of this handbook
Purpose:
Prevent unnecessary removals of ELAC and SEC thanks to a

better understanding of:
o
o
ELAC and SEC systems (EFCS)

ATA 27 Failure message and ECAM Warning
generation
Provide guidelines and tips to the Maintenance team for a

quicker and more efficient fault resolution
Please note:
This handbook is valid for the A320 Family aircraft.
These instructions do not amend or supersede any

information contained in Trouble Shooting Manual and
Aircraft Maintenance Manual.
This document will not be updated on regular basis.
Enquiries related to this handbook should be addressed to:
Airbus Customer Services

Flight Control Systems A320 Family
SEEL5
DL-CE-DPT-SEEL5@airbus.com
CONTENT
This booklet contains:
A reminder on how to find the adequate TSM task corresponding to

a given fault (Chapter 2.)
A method/guideline to maximise efficiency of the ELAC/SEC system

trouble-shooting (Chapter 3.)
Recommendations applying in case of difficult and lengthy troubleshooting (Chapter 4).
Many examples of typical failure cases illustrating these general

advices (See Index of Examples in page 6)
Detailed content
Page
0 Index of examples
1 Introduction
1.1 EFCS architecture
1.2 Maintenance feature
10
1.3 Available maintenance information
11
1.4 Glossary
13
2 Find the correct TSM task

2.1 Howto proceed
o IdentificationofthecorrectTSMtask
16
o Tips
17
2.2 Fault Examples

o FailureMessage potentialtroublemakers
19
IR1Failure
Elevatorservocontrolfaults
o CorrelationwiththeadequateE/W
21
F/CTLELAC2PITCHFAULT&F/CTLELEVSERVOFAULT
CHECKPRIORITYWIRING
o FlightControlpage displayandTroubleShooting
23
CONTENT
Page
3 Advanced Trouble-Shooting guidelines

3.1 Advanced T/S procedure
o Whyan advancedT/Sprocedure?
26
o Advancedprocedureflowchart
27
3.2 Typical cases and situations

o SpecificcasesnotrequiringT/S
29
Discriminateresetversusgenuinefailure
ACCLRMfaultwithELAC1/SEC2/SEC1underMEL
F/CTLELEVSERVOFAULTwithSEC2underMELduringtaxiwithoneengine running
AFS: ELACx
o HowtousePLRandAIRMAN
33
Descriptions
Example:Faultlinkedtoelevatorservocontrol
Example:Faultlinkedtospoilerservocontrol
Example:MultipleXDCRfailures
o TFUlinkedtoa TSMtask
39
o Faultswithout FailureMessage
40
PressureSwitchissue
4 Difficult Trouble-Shooting
4.1 General recommendations
o Intermittent failure
44
o Wiring check
45
4.2 Typical faults

o Discrete interface / grounded signal
47
o F/CTL ALTN LAW & F/CTL DIRECT LAW
49
o Damaging failure
51
4.3 Useful tool for T/S

o Swapping tool (bundle)
54
0
Index of examples
Index of examples
E/W or Maint. Status
F/ CTL Maint. Status
F/ CTL ELAC2 PITCH FAULT

F/ CTL maint. status
F/CTL ELEV SERVO FAULT
Failure Message
ELAC/SEC x COM/MON OR BUS3/2 FROM
IR1/2/3
IR1/2/3 - BUS3/2
R1/2/3
ELAC2 OR WIRING FROM L G ELEV POS
XDCR 34CE1
SEC2 OR WIRING FROM L G ELEV POS
XDCR 34CE1
L G ELEV POS XDCR 34CE1
Refer to page:
P19
p20
p21
L B ELEV MODE XDCR 34CE3
p34
F/CTL SIDESTICK PRIORITY

Or
F/CTL maint. Status
F/CTL SIDESTICK PRIORITY +
F/CTL maint. Status
CHECK PRIORITY WIRING
p22
p22
F/CTL ELAC/SEC x FAULT

F/CTL maint. status
ELAC/SEC x
SEC1 OR WIRING FROM ACCLRM 1 12CE1
ELAC1 COM/MON OR WIRING FROM
ACCLRM 2 12CE2
ELAC2 COM/MON OR WIRING FROM
ACCLRM 4 12CE4
p28
p30
F/CTL ELEV SERVO FAULT with No failure message but L G/R Y servo is
SEC2 under MMEL and only one boxed on status display
engine running
AFS: ELAC x
F/ CTL Maint. Status
ELAC/SEC x COM/MON OR BUS3/2 FROM
ADR1/2/3
ADR1/2/3 - BUS3/2
ADR1/2/3
F/CTL SPLR FAULT
L (R) SPLRx POS ERROR 31CEx
p31
F/CTL SPLR FAULT
L (R) SPLRx POS XDCR 31CEx
p36
F/ CTL ELAC2 PITCH FAULT
ELAC1 OR WIRING FROM L B ELEV POS

XDCR 34CE3
ELAC1 OR WIRING FROM R ELEV POS
MON XDCR
No Failure message
p38
F/CTL ELACy PITCH FAULT
CHECK PITCH CHANGE OVER OF ELAC1
p48
F/CTL ALTN LAW

F/CTL DIRECT LAW
F/CTL AIL SERVO FAULT
multiple failure message

multiple failure message
L B AIL MODE VLV 33CE3
F/CTL ELACx FAULT

F/CTL ELACy PITCH FAULT
p32
p36
p36
p40
p41
p49/50/51
p49/50/51
p52/53
1
Introduction
EFCS Description
EFCS architecture
EFCS Description
Maintenance features
ELAC
1
ELAC
EFCS 1 FCDC
ELAC
2
ELAC
1
SEC
FCDC
EFCS 2
DMC, FWC, CFDIU, FDIU
ECAM Warning
(E/W) generation
Failure message
generation
Failure Message and ECAM Warning (E/W) are

defined by each FCDC (in parallel) based on
information from all ELACs and SECs.
Failure Message and E/W are different whether the FAULT is
detected by one or more computers.
This correlation is enabled by the FCDCs.
10
Available Maintenance Information
Fault Symptoms
A fault is characterized by two levels of information (symptoms):

E/W and status display: The purpose of those indications is
to inform the flight crew about system failure. They are
not designed for Trouble Shooting purpose.
Failure Message: They are intended to the maintenance
staff. Maintenance staff has to focus on Failure
Message to initiate the Trouble Shooting, not on the
E/W.
Trouble Shooting shall preferably be initiated using

the Failure Message and not using the E/W or
information from the lower ECAM F/CTL page.
NOTE
ECAM Warnings could be useful for maintenance

team providing that they are adequately correlated
with Failure Messages.
11
Available Maintenance Information
Trouble Shooting Data (TSD)

Background:
For many systems, analysis of the TSD enables to provide
complementary information on the failure. However, EFCS has
been built so as to provide the most accurate level of information
in the failure message.
Example of EFCS TSD decoding:
TROUBLESHOOTINGDATA
1435279334
FAIL0110020A.3F.36
INP1xxxx xxxx xxxx xxxx
INP2xxxx xxxx xxxx xxxx
STS1xxxx xxxx xxxx xxxx
UTC / ATA chapter number

FAIL (failure details):
-01: failure number within the last flight leg
-1: failure counter (number of occurrence)
-0: external failure
-02: FWC flight phase
-0A.3F.36: byte1.byte2.byte3 of failure code
Decoding of the failure code: 0A.3F.36
ELAC1 OR WIRING FROM L B ELEV POS XDCR 34CE3
The failure code is the exact translation of the failure message in

a coded language. It does not contain additional data.
The best and sufficient entry point to trouble-shoot an EFCS fault

is the failure message (PFR, PLR, LLR) properly correlated with
the applicable ECAM Warning.
12
Glossary
ACCLRM
ACS
ADR
AFS
AIL
CFDIU
CFDS
DMC
E/W
EFCS
ELAC
ELEV
F/CTL
FCDC
FDIU
FWC
IR
LRU
MEL
P/B
P/SW
PFR
PLR
PTU
SEC
SERVO
SV
T/S
TFU
TSD
TSM
VLV
XDCR
Accelerometer
Alternating Current Supply
Air Data Reference
Automatic Flight System
Aileron
Centralized Fault Display Interface Unit
Centralized Fault Display System
Display Management Computer
ECAM Warning
Electrical Flight Control System
Elevator Aileron Computer
Elevator
Flight Control
Flight Control Data Concentrator
Flight Data Interface Unit
Flight Warning Computer
Inertial Reference
Line Replaceable Unit
Minimum Equipment List
Push Button
Pressure Switch
Post Flight Report
Previous Leg Report
Power Transfer Unit
Spoiler Elevator Computer
Servo control
Solenoid Valve
Trouble Shooting
Technical Follow-up
Trouble Shooting Data
Trouble Shooting Manual
Valve
Transducer
13
2
Find the correct TSM
task
14
Find the correct TSM task
2.1
Identification of the
correct TSM task
15

2.1)Howtoproceed
Identification of the correct TSM task
Enter the Failure Message

in AirN@v
If necessary, select the

TSM task corresponding to
the Class of the Failure
Message
Refer to: Failure

Message =
potential troublemakers p19-20
Refer to: p17
Make sure the Failure

Message is associated with
the correct E/W
Find the appropriate TSM

task
This enables to take advantage of

the FCDC correlation capabilities.
(each couple Failure Message +
E/W has a specific TSM task)
Refer to: Correlation with the
adequate E/W p17 / p21-22
How to use AirN@v
In AirN@v, use the advanced tools: Start Troubleshooting

and open the submenu CFDS Fault Messages or Fault
Pattern. Then follow the above procedure.
16

2.1)Howtoproceed
Tips
Differentiate class1 an class2 messages:
A same failure message might be either:
Class 1 Failure Messages associated with an ECAM Warning
Class 2 Failure Messages associated with a maintenance status F/CTL
Check failure symptoms of the selected TSM task:
Fault
symptoms
17
2.2
Fault examples
This paragraph aims at illustrating why it is essential to make
sure TSM task applies to the reported fault symptoms. This
enables to direct maintenance crew towards the most probable
trouble-makers.
Failure message potential trouble makers

o IR1 Failure
o Elevator servocontrol faults
Correlation with the adequate E/W

o F/CTL ELAC2 PITCH FAULT & F/CTL ELEV SERVO FAULT
o CHECK PRIORITY WIRING
Flight Control page and trouble-shooting
18

2.2)Faultexamples:FailureMessage potentialtroublemakers
IR1 Failure
If there is a failure of the IR1 or IR1 wiring, three different Failure Messages
can be elaborated by the FCDC depending on where the Fault is located
and which computers detect the fault.
IR1 network structure:

ELAC 1
SEC 1
ELAC 2
SEC 2
COM
COM
COM
COM
MON
MON
MON
MON
SEC 3
First terminal
block
BUS 3
BUS 2
IR1
Failure messages built by the FCDC:

Case
IR1Faultdetected by
FailureMessage
Onecomputerunit
Ex:ELAC1COM
ELAC1COMOR
BUS3 FROMIR1
Two computerunitsonthesame
BUS
Ex:ELAC1COM&SEC1COM
IR1 BUS3
Twocomputers onBUS3andtwo
computeronBUS2
IR1
Mostprobablecomponent
involved
Computerorwiringto
firstterminalblock
IR1orwiringtofirst
terminalblock
IR1
Each Failure Message incriminates the LRU and/or the wiring

which is the most likely at the origin of the FAULT.
19

2.2)Faultexamples:FailureMessage potentialtroublemakers
Elevator servocontrol faults

Failure messages associated with L G servocontrol piston rod transducer
Fault
detected by
FailureMessage
ELAC2
ELAC2ORWIRING
FROMLGELEV
POSXDCR34CE1
LGELEV
SERVOXDCR
ELAC 2
SEC2
SEC2ORWIRING
FROMLGELEV
POSXDCR34CE1
LGELEV
SERVOXDCR
ELAC 2
ELAC2and
SEC2
LGELEVPOSXDCR
34CE1 COME2/S2
LGELEV
SERVOXDCR
ELAC 2
Case
Mostprobablecomponentinvolved
SEC2
SEC 2
SEC 2
ELAC2orwiring
tofirstterminal
block
SEC2orwiringto
firstterminal
block
Servocontrolor
wiringtofirst
terminalblock
Note: L G ELEV SERVO XDCR = Left Green Servocontrol Transducer
NOTE
If ELAC2 and SEC2 detect the same FAULT (case 3), the FAULT
comes from the servo transducer or the common part of the wiring.
Avoid computer removal.
In general, each failure message incriminates the LRUs and/or

the wiring which is the most likely at the origin of the FAULT.
20

2.2)Faultexamples:CorrelationwiththeadequateE/W
F/CTL ELAC2 PITCH FAULT & F/CTL ELEV SERVO FAULT

Fault
detected by
FailureMessage
ELAC2
F/CTLELAC2PITCH
FAULT
LGELEV
SERVOXDCR
ELAC2
SEC2
E/W:F/CTL
LGELEV
SERVOXDCR
ELAC2
ELAC2and
SEC2
Case
E/W:F/CTLELEV
SERVOFAULT
LGELEV
SERVOXDCR
SEC2
SEC2
ELAC2
SEC2
ELAC2orwiring
tofirstterminal
block
SEC2orwiringto
firstterminal
block
Servocontrolor
wiringtofirst
terminalblock
These logics and design principles have been used to elaborate applicable
TSM tasks. Each fault symptom corresponds to a specific TSM task
NOTE
1.
2.
In case of F/CTL ELEVATOR SERVO FAULT, no computer

shall be removed (in accordance with TSM).
If the PFR shows F/CTL ELAC2 PITCH FAULT E/W
followed by F/CTL ELEV SERVO FAULT E/W, this indicates
SEC2 has subsequently detected a FAULT on the same
servo. Accordingly, fault comes from the servocontrol or the
common part of the wiring.
For FAULT correlation, use preferably the F/CTL ELEV
SERVO FAULT E/W as this will lead you to a more accurate
Trouble Shooting task.
Correlating failure message with the corresponding ECAM

Warning aims at identifying the best T/S task.
21

2.2)Faultexamples:CorrelationwiththeadequateE/W
Case
Detectedby
FailureMessage
Atleast, one
ELAC
CHECKPRIORITY
WIRING
F/CTLSIDESTICK
PRIORITY
Atleast, one
SEC
CHECKPRIORITY
WIRING
F/CTL
Atleast, one
ELACandone
SEC
CHECKPRIORITY
WIRING
F/CTLSIDESTICK
PRIORITYand F/CTL
In this case,
ELAC removal
shall be avoided
ECAMWarning
Probablecause
ELAC1,ELAC2,wiring
SEC1,SEC2,SEC3,
wiring
Common wiring,push
button
In this case, all components of the system

can be involved. But it is more probable that
the FAULT comes from the common part of
the system: push button or common wiring.
These logics and design principles have been used to elaborate applicable
TSM tasks. Each fault symptom corresponds to a specific TSM task
Correlating failure message with the corresponding ECAM

Warning aims at identifying the best T/S task.
22

2.2)Faultexamples:FlightControlpagedisplayandTroubleShooting
Mode monitoring on pitch axis

Interpretation of the information
supplied by the F/CTL page
UTCPHATAWARNING
140602270000F/CTLELEVSERVOFAULT
UTCPHATAFAULTMESSAGE
140602279334LBELEVMODEXDCR 34CE3
Left Green Elevator Servo

Control boxed on the F/CTL
page status display
Failure Message
incriminating the Left Blue
Elevator mode transducer
Failure message provides the correct information for Trouble Shooting (L B

Servo faulty). However the L G servo is boxed on the F/CTL page.
Why L G servo is boxed on the F/CTL page?
Due to the failed L B Elev mode transducer, ELAC2 and SEC2
are not able to check that the L B servo is correctly in damping
mode. As per design, it has been chosen not to actuate the L G
servo to avoid possible force fighting with the L B servo.
Trouble-shooting shall not be initiated using Status display on the

F/CTL page. The maintenance staff has to use the failure message.
23
3
Advanced TroubleShooting guidelines
24
AdvancedTroubleShootingguidelines
3.1
Advanced T/S
procedure
Why an Advanced T/S procedure?

Advanced procedure flowchart
25
3.1)AdvancedT/Sprocedure
Whyanadvancedprocedure?
Some failures, particularly intermittent ones, might lead to
different fault patterns notably depending on their duration,
nature, etc ...
For instance, an intermittent failure may not be systematically
detected by all the involved computers inducing inaccurate fault
correlation and thus rendering trouble-shooting more difficult.
Also, opportunity has been taken to document specific fault
symptoms that might cause incorrect interpretation/action of
maintenance team.
This booklet section details an advanced T/S procedure
permitting to increase the trouble-shooting efficiency.
Adherence to these guidelines will:
facilitate identification of the most pertinent TSM task
permit to fix more quickly a fault
prevent useless computers/parts removals that might
result from lengthy trouble-shooting
26
3.1)AdvancedT/Sprocedure
Advancedprocedureflowchart
Identify failure
symptoms
(E/W & Failure
Message)
Is the failure due

to specific
conditions?
yes
no
Dedicated TSM
tasks
yes
no
no
No need of T/S
Refer to: Specific
cases not requiring
T/S p29 to 32
no
E/W associated with a
Failure Message
Specificconditions
mean:MEL,reset,AFS
Failure incriminating the

same LRU in PFR/PLR
/AIRMAN ?
yes
Refer to: Faults

without Failure
Message p40 to 41
Failure incriminating the

several XDCR in PFR/PLR
/AIRMAN ?
yes
Identify if possible
more accurate
failure symptoms
by correlation
Refer to: How to

use PLR and
AIRMAN p33 to 38
Use AirN@v to find

an appropriate
TSM task
Refer to: TFU

linked to a TSM
task p39
Adhere to TFU T/S advices

block when appropriate.
27
3.2
Typical cases and
situations
Specific cases not requiring T/S
oDiscriminate reset & genuine failure
oACCLRM fault with ELAC1 / SEC2 / SEC1 under MEL
oF/CTL ELEV SERVO FAULT with SEC2 under MEL
with one engine running
o AFS: ELAC x
How to use PLR and AIRMAN

oDescriptions
oExample 1: Fault linked to elevator servocontrol
oExample 2: Fault linked to ADR
oExample 3: Fault linked to spoiler servocontrol
oExample 4: Multiple XDCR failures
TFU linked to a TSM task

Faults without Failure Message
oPressure switch issue
28
3.2)Typicalcasesandsituations:SpecificcasesnotrequiringT/S
Discriminate reset versus genuine failure

Background:
Signature of an ELAC or SEC reset (via Push Button) is similar to a genuine failure.
Accordingly, reset can only be identified by an analysis of the PFR.
Resetof
E/W
FailureMessage
ELACx
F/CTL ELACxFAULT
ELACx
SECy
F/CTLSECyFAULT
SECy
How to identify a reset:

Above mentioned FAULTs when occurring subsequently to another ATA27 E/W are
very likely attributable to a reset.
Example:
associated with
UTCPHATAWARNING
Failure Message
235102270000F/CTLELAC1PITCHFAULT
235902270000F/CTLELAC1FAULT
2351 02279334ELAC1COMORWIRINGTOLBELEVSERVOVLV34CE3
235902279334ELAC1
signature of an ELAC1
a few minute after
reset
the original fault
T/S has to be performed based on the earlier Failure Message. In this example: ELAC1
COM OR WIRING TO L B ELEV SERVO VLV 34CE3
If the maintenance staff identifies a FAULT due to a reset, there is no

need of further maintenance action for this specific failure entry.
Furthermore, the failure shall not be used to substantiate a computer
removal.
29
Accelerometer fault with ELAC1 / SEC2 / SEC1

under MEL
data
SEC 1
ACCLRM 1
ELAC 1 under MEL

data
ELAC 1
supply
Circuit Breaker
If ELAC1 is under MEL, applicable Circuit Breaker

is opened. Accelerometer 1 is no longer powered
due to system architecture.
SEC1 that acquires the accelerometer data will
subsequently detect a loss of accelerometer
signal.
The PFR will show Failure Message SEC1 OR
WIRING FROM ACCLRM 1 12CE1
POWER SUPPLY
ACCLRMwithout
powersupply
Case
MEL
ELAC1
ACCLRM1
E/W:F/CTL
FailureMessage:SEC1ORWIRINGFROMACCLRM112CE1
SEC1
ACCLRM2
E/W:F/CTL
FailureMessage:ELAC1COM/MONORWIRINGFROM
ACCLRM212CE2
ACCLRM4
E/W:F/CTL
FailureMessage:ELAC2COM/MONORWIRINGFROM
ACCLRM412CE4
SEC2
FaultthatdoesnotrequiresT/S
Accelerometer fault mentioned here-above does not requires T/S if the

corresponding computer is under MEL.
30
F/CTL ELEV SERVO FAULT with SEC2 under MEL

during taxi with one engine running
Background:
F/CTL ELEV SERVO FAULT warning might appear on ECAM when SEC2 is under MEL
during taxi if:
PTU is inhibited
only one engine is operating
.
Example:
Engine 1 > GREEN
hydraulics
Engine 2 > YELLOW
hydraulics
SEC 2 under MEL
Situation
Consequence
1.SEC2underMEL
SEC2notabletoservotheRYand
theLGservo
2.Engine2off
3.PTUinhibited
Yhydraulicnotavailable
ELAC2notabletotakeoverthe
pitchaxis
LGServoisboxedonthestatusdisplayandtheECAM
WarningF/CTLELEVSERVOFAULTappears
Explanation
ELACsarecapabletoachievepitch
controlifbothELEVs&THSAare
available
Neither SEC2norELAC2can
controltheLGSTCLdespitethe
availabilityoftheGhydraulic
Note: same type of rationale can be built whether engine 1 is off.
ECAM Warning F/CTL ELEV SERVO FAULT will disappear as soon as

PTU operates or 2nd engine is operative.
This failure symptom does not require T/S.
NOTE
This is covered by a note in the Operational Procedure of the MEL

31
AFS: ELAC x
Design principle
As long as the ELACs are capable to achieve the Auto Pilot (AP) order, they send to
Auto Flight System (AFS) computers a discrete signals which allows the AP
engagement.
AFS: ELAC x indicates that one of the computers belonging to the Auto Flight System
does not receive anymore its AP engagement discrete inputs from the ELAC.
This might be an indication of:
a genuine failure of the discrete input interface
or the consequence of the inability for ELAC to perform AP order.
Examples: inability for ELAC to perform the pitch servo loop:

1.
UTCPHATAWARNING
1403 06290000HYDBSYSLOPR
1403 06290000HYDBELECPUMPLOPR
1403 02279334AFS:ELAC1
2.
UTCPHATAWARNING
1316 02270000F/CTLELEVSERVOFAULT
1316 02273451LBELEVSERVOVLV34CE3
1316 02279334AFS:ELAC1
On the two above examples, ELAC1 cannot take over the pitch axis leading to the
inability of the ELAC1 to correctly perform the AP order. Consequently AP
authorization discrete inputs are not sent by the ELAC1 and AFS: ELAC1 is
displayed.
TSM content:
AP Engagement Authorization discrete inputs are monitored by the ELAC (wrap up).
An ELAC discrete input emission failure would be self-detected by the ELAC leading
to ELAC FAULT. AFS: ELAC1 failure message is thus unlikely attributable to the
ELAC.
Do not use AFS: ELAC1 or AFS: ELAC2 Failure Messages to substantiate

an ELAC removal.
If Failure Message is confirmed on ground, apply corresponding TSM task.
32
3.2)Typicalcasesandsituations:HowtousePLRandAIRMAN

Descriptions
If the aircraft is experiencing recurring fault symptoms, analysis of previous PFR,
PLR and AIRMAN data might provide valuable information to increase T/S
efficiency.
In particular, this review might enable:
to identify if different failure modes have been experienced
and, whenever possible, to select a more appropriate TSM task.
How to proceed:
a. Find failure messages incriminating same LRU in
PFR/PLR/AIRMAN
b. Find failure messages incriminating other XDCR
Refer to:
Example 1
Example 2
Example 3
Example 4
Fault linked to elevator servocontrol

Fault linked to ADR
Fault linked to spoiler servocontrol
Multiple F/CTL XDCR failures
p34
p35
p36
p37-38
NOTE
Exploring the aircraft fault history (previous PFR / PLR / AIRMAN)

also enables to check trouble-shooting already accomplished and
avoid repeating same step of the TSM task.
If a similar fault has already occurred, the maintenance staff:

shall avoid repeating the same step of TSM task
may try to find a more accurate TSM task using the other Failure
messages present in PFR / PLR / AIRMAN.
33

Example 1
Fault linked to elevator servocontrol:
Elevator servocontrols are controlled and monitored by one ELAC & one SEC.
It might happen that intermittent failures at the level of the servocontrol be not detected
by both computers.
Example:
For background & principle refer to:

elevator servocontrol faults in chapter 2.
p20 and p21
Original fault symptoms:
F/CTL ELAC 2 PITCH FAULT

ELAC2 OR WIRING FROM L B ELEV MODE XDCR 34CE3
If in previous PFR / PLR / AIRMAN, one of the following fault has already occurred:
maintenance status F/CTL
SEC2 OR WIRING FROM L B ELEV MODE XDCR 34CE3
SEC2 OR WIRING FROM L B ELEV MODE XDCR 34CE3
L B ELEV MODE XDCR 34CE3
It can be concluded that the component at the origin of the fault is certainly the
common LRU (in this case L B ELEV MODE XDCR 34CE3) or the common wiring.
Using the Failure Message L B ELEV MODE XDCR 34CE3 will lead you to a more
accurate TSM task.
When several Failure Messages involving the same LRU are shown
in PFR/PLR/AIRMAN... comparison of the TSM task content enables
to identify more precisely the common point.
34

Example 2
Fault linked to ADR
ELAC 1
SEC 1
ELAC 2
SEC 2
COM
COM
COM
COM
MON
MON
MON
MON
SEC 3
First terminal
block
BUS 3
BUS 2
ADR1
For background & principle

refer to: p19
Example:
Original fault symptoms
ELAC1 COM OR BUS3 FROM ADR1

If previous PFR / PLR / AIRMAN show one of the following faults:
ADR1 BUS3
ADR1
It can be concluded that the component at the origin of the fault is certainly the
common LRU (in this case ADR1) or the common wiring.
Using the Failure Message ADR1 or ADR1 BUS3 will lead you to a more
accurate TSM task.
35

Example 3
Fault linked to spoiler servocontrol:
SEC
SV
Spoiler
servocontrol
XDCR
Fault symptoms A:
F/CTL SPLR FAULT
L (R) SPLRx POS ERROR 31CEx
Possible causes:
SEC,
Wiring from SEC to servovalve
Wiring from position transducer to SEC
Spoiler servocontrol
Fault symptoms B:
F/CTL SPLR FAULT
L (R) SPLRx POS XDCR 31CEx
Possible causes:
SEC,
Wiring from position transducer to SEC
Spoiler servocontrol
Analysis
The comparison of the possible causes listed in the TSM tasks enables to rule
out the Wiring from SEC to servovalve. It incriminates more precisely the
spoiler servocontrol transducer interface.
36

Example 4
Multiple XDCR failures - Description:
Each ELAC & SEC supplies their corresponding XDCR. These power supply
circuitries are called Alternating Current Supplies (ACS). If an ACS fault occurs, the
affected ELAC/SEC XDCRs are no longer powered. They are declared faulty by the
concerned computers.
Case
NumberofXDCR
FailureMessages
reportedonPFR
/PLR/AIRMAN
SingleXDCR
FailureMessage
ELAC
XDCR1
ACS Wiring
XDCR2
Feedback
Wiring
ELAC
2
Two ormoreXDCR
FailureMessage
XDCR,feedback
wiring,orACS
wiringtofirst
terminalblock
XDCR3
XDCR1
XDCR2
ComputerorACS
wiringtofirst
terminalblock
XDCR3
If there is more than one Failure Message ELAC/SEC x or WIRING TO

XDCR in PFR, an ACS fault can be suspected. TSM (as shown hereafter) enables to identify the most appropriate TSM task
37

Examples 4
Multiple XDCR failures Typical PFR:
UTCPHATAWARNING
131302270000F/CTLELAC1PITCHFAULT
1313 02279334ELAC1ORWIRINGFROMLBELEVPOSXDCR34CE3
131302279334ELAC1ORWIRING FROMRELEVPOSMONXDCR
When two XDCR Failure
Messages fed by the same ACS
are displayed in the PFR, TSM
enables to identify a specific
TSM task.
Taken independently these

failure messages lead you to
different TSM tasks.
Extract of TSM task 27-90-00-810-813:

TSM already proposes such failure message correlation:
NOTE
Review of the PLR and AIRMAN enables to make sure that no other
XDCR fault linked to the same ACS has been previously experienced.
38
3.2)Typicalcasesandsituations:TFUlinkedtoaTSMtask
TFU linked to a TSM task

Background:
A TFU might be linked to a particular fault symptoms in AirN@v. Maintenance
advice block might contain useful information for trouble-shooting.
How to find a TFU linked to a TSM task:
TFU linked to the

ECAM Warning F/CTL
ELAC 1 PITCH FAULT
TFU linked to the CFDS

Fault Message ELAC1 OR
WIRING TO L G ELEV
SERVO VLV 34CE1
If a TFU is linked to the TSM task, follow, if applicable, the

recommendations contained in the Maintenance advice paragraph
of the TFU.
39
3.2)Typicalcasesandsituations:FaultswithoutFailureMessage
T/S procedure if there is no Failure Message

associated to a given E/W
Dedicated TSM tasks permitting to address E/W not associated

with a Failure Message can be found in AirN@v.
Some of these tasks are incriminating Pressure Switches and
FWCs as a possible cause.
Refer to the next page, for

further explanations
NOTE
It is advisable to check if the E/W has already occurred in PLR /

AIRMAN. If E/W was previously associated with a failure
message, trouble shooting procedure related to this maintenance
message has to be carried out.
40
3.2)Typicalcasesandsituations:FaultswithoutFailureMessage
Pressure Switch issue

Design & Principle:
ELAC:
For each hydraulic system, the ELACs acquire the hydraulic status
using three different sensors: two pressure switches (P/SW) and
one pressure transmitter (P/XMTR).
Hydraulic status built by the ELACs is voted using the three pieces
of information.
FWC:
Flight Warning Computer (FWC) hydraulic information is based on

one P/SW information.
Spurious E/W caused by erroneous P/SW information:

ELAC not available for pitch
(due to low pressure detected by the ELAC)
P/SW1
Highpress.
ELAC
FCDC
Per design: no
Failure Message
ELAC
senses a
Low press.
P/SW 2
Lowpress.
FWC
FWC sees:
High press.
ELAC not
available for pitch
Generation of the E/W

F/CTL ELAC PITCH
FAULT.
P/XMTR
Lowpress.
Proper identification of the fault symptoms and adherence to the TSM will
direct trouble-shooting towards the failed P/SW or FWC.
41
4
Difficult TroubleShooting
42
Difficult Trouble-Shooting
4.1
General
recommendations
Intermittent failure
Wiring Check
43
4.1)Generalrecommendations:Intermittentfailure
Intermittent failure
Some failures are intermittent and thus not reproducible on
ground.
Trouble-shooting accomplishment is rendered more difficult as
efficiency of the corrective action cannot be confirmed.
In these cases, it is necessary to properly follow-up and monitor
the aircraft in order to make sure that the fault has been properly
cured.
NOTE
If an intermittent failure occurred three times, it is advisable to

apply the fault isolation of the corresponding TSM task step by
step until final resolution.
Tight follow up of the aircraft (including review of the

maintenance record, PLR, AIRMAN) enables to avoid
same step of the TSM repeating (for instance, multiple
ELAC or SEC removals).
Intermittent failure requires an accurate follow up of the aircraft.

44
4.1)Generalrecommendations:Wiringcheck
Wiring check
Wiring check:
It consists of:
1. Continuity check,
2. Quality of the connections,
3. Short circuit / Insulation tests,
4. Resistance check.
How to interpret resistance measurement:
Resistance check has to be preferred for intermittent failure (better
than continuity). It may highlight possible corrosion, improper
contact or improper connector locking, contamination, moisture
ingress, etc
Compare the resistance of the adjacent wires (Two adjacent

wires have in general the same length and same gauge)
A discrepancy of a few ohms can be a valid indication / positive

finding for an intermittent failure (For calculation of the normal
resistance value, refer to Standard Manual : resistance per meter).
Do not hesitate to shake moderately the wires while performing

the test. The resistance value should not fluctuates.
NOTE
To see the resistance fluctuations prefer use an analogical

ohmmeter with a needle (a digital ohmmeter may reduce
these fluctuations and make them invisible on the screen).
45
4.2
Typical faults
Discrete interface / grounded signal

F/CTL ALTN LAW & F/CTL DIRECT LAW
Damaging failure
46
4.2)Typicalfaults: Discreteinterface/groundedsignal

Background:
Computers send (receive) discrete signals to (from) other computers. Some failures
mode might be such that an erroneous information can be spread in the concerned
discrete network.
Principle:
LRUx
MON
COM
Ground sent by the

faulty SEC2 COM
Open circuit signal received

Ground signal received
DSO x
DSI x
MON
DSO y
DSI y
COM
ELAC2
Ground detected by
ELAC2 COM
DSI x
MON
DSI y
COM
SEC2
Removing SEC2 will remove the
ground point
For the concerned DSI, ELAC2 detects a COM/MON discrepancy. Failure message
will incriminate ELAC2 or wiring from LRUx while SEC2 is at fault.
Most of the time the failure is not detected by the faulty computer (SEC2 in this case).
If a failure of the discrete links is suspected, TSM task is 31-32-00-810932 is cross-referenced in the applicable TSM task.
This task consists in removing one by one all possibly involved computers
to identify the faulty one (see example here-after).
NOTE
1. In case of an intermittent failure of the discrete links, the fault may

not be reproduced on ground. In this case replace one by one the
involved computers.
2. As far as F/CTL computers are concerned, discrete inputs corrupted
by internal computer fault are more frequently caused by SECs (failure
of lightning diodes located on discrete inputs).
47
4.2)Typicalfaults:Discreteinterface/groundedsignal

Example of TSM task:
TSM task 31-3200-810-932 crossreferenced
DSO 09 of ELAC1 is
connected to SEC1 & SEC2
As per TSM task 31-32-00-810-932, SEC1 & SEC2 must be removed from their
rack and the effect on the failure verified.
48
4.2)Typicalfaults:F/CTLALTNLAW&F/CTLDIRECTLAW
F/CTL ALTN LAW & F/CTL DIRECT LAW

F/CTL ALTN LAW and F/CTL DIRECT LAW ECAM
Warnings are a consequence of multiple failures.
These E/W are displayed to inform the pilot on the level
of Flight Control protection available to control the
aircraft.
They do not bring valuable information for T/S purpose.
Correlation with E/W F/CTL ALTN / DIRECT LAW might
not be possible as all possible failure configurations
leading to Law reversion have not been documented in
the TSM.
When F/CTL ALTN / DIRECT LAW are reported, PFR shall be

reviewed and faults at the origin of the law reversion have to be
identified and troubleshot individually.
NOTE
A description of the failure combination leading to F/CTL ALTN /

DIRECT LAW reversion can be found in the in FCOM Volume 1
Chapter 27 Section 30.
A copy of this table is provided in the next page.
49
Extract of FCOM
Volume 1 Chapter 27
Section 30
4.2)Typicalfaults:F/CTLALTNLAW&F/CTLDIRECTLAW
50
4.2)Typicalfaults: Damagingfailure
Damaging failure
Some failures (in particular failures - short-circuit - on wiring

involving solenoid supply) can damage computers.
Consequently, computer swapping may temporally fix the
failure until the new computer get damaged.
When a failure can possibly damage computers, TSM task
contains a caution requesting not to swap computers. Also,
first step of the TSM task consists in checking that there is no
short circuit in the wiring interface
Refer to the next page
depicting an example of
TSM Task involving
solenoid.
When instructed by TSM, checking the wiring for a possible short

circuit before replacing the computer is highly recommended. This
enables to prevent multiple and useless computer replacements.
51
4.2)Typicalfaults: Damagingfailure
Damaging failure
Example of a TSM task involving solenoid:
Caution: to avoid
swapping.
First step of the TSM

task is a check of
resistances for a
possible short circuit.
52
4.3
Useful tool for T/S
53
4.3)UsefultoolforT/S
The Swapping tool

Principle
The swapping tool is an equipment developed by Airbus which simulates on
ground a swapping between two Servo Controls. The swapping tools swap all
Inputs / Outputs from one servocontrol to another servocontrol.
Computer1
Servo1
Swapping
tool
Computer2
Servo2
Applicable references:
Elevators AMM 27-34-00-860-079
Ailerons AMM 27-14-00-760-001
Like a computer swapping which can prove that a computer is or not at the
origin of a fault, the swapping tool can enable to identify if a Servo Control or
the wiring is at the origin of a Fault.
Advantages of using the swapping tool:

avoid servocontrol removal task while Trouble Shooting
minimize/optimize wiring check
54
4.3)UsefultoolforT/S
The Swapping tool

Examples
55
56

ATA 27 EFCS Troubleshooting Tipspdf

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

ATA 27 EFCS Troubleshooting Tipspdf

Diunggah oleh

Hak Cipta:

Format Tersedia

A320FAM.

Aircraft System Maintenance Aids

Aim of this handbook

Prevent unnecessary removals of ELAC and SEC thanks to a

ELAC and SEC systems (EFCS)

Provide guidelines and tips to the Maintenance team for a

This handbook is valid for the A320 Family aircraft.

These instructions do not amend or supersede any

This document will not be updated on regular basis.

Enquiries related to this handbook should be addressed to:

Airbus Customer Services

A reminder on how to find the adequate TSM task corresponding to

A method/guideline to maximise efficiency of the ELAC/SEC system

Recommendations applying in case of difficult and lengthy troubleshooting (Chapter 4).

Many examples of typical failure cases illustrating these general

1.2 Maintenance feature

1.3 Available maintenance information

2 Find the correct TSM task

2.2 Fault Examples

3 Advanced Trouble-Shooting guidelines

3.2 Typical cases and situations

4.2 Typical faults

o F/CTL ALTN LAW & F/CTL DIRECT LAW

4.3 Useful tool for T/S

F/ CTL ELAC2 PITCH FAULT

F/CTL ELEV SERVO FAULT

L B ELEV MODE XDCR 34CE3

F/CTL SIDESTICK PRIORITY

CHECK PRIORITY WIRING

CHECK PRIORITY WIRING

F/CTL ELAC/SEC x FAULT

F/CTL SPLR FAULT

L (R) SPLRx POS XDCR 31CEx

F/ CTL ELAC2 PITCH FAULT

ELAC1 OR WIRING FROM L B ELEV POS

F/CTL ELACy PITCH FAULT

CHECK PITCH CHANGE OVER OF ELAC1

F/CTL ALTN LAW

multiple failure message

F/CTL ELACx FAULT

DMC, FWC, CFDIU, FDIU

Failure Message and ECAM Warning (E/W) are

Available Maintenance Information

A fault is characterized by two levels of information (symptoms):

Trouble Shooting shall preferably be initiated using

ECAM Warnings could be useful for maintenance

Available Maintenance Information

Trouble Shooting Data (TSD)

UTC / ATA chapter number

Decoding of the failure code: 0A.3F.36

ELAC1 OR WIRING FROM L B ELEV POS XDCR 34CE3

The failure code is the exact translation of the failure message in

The best and sufficient entry point to trouble-shoot an EFCS fault

Find the correct TSM task

Find the correct TSM task

Identification of the correct TSM task

Enter the Failure Message

If necessary, select the

Refer to: Failure

Refer to: p17

Make sure the Failure

Find the appropriate TSM

This enables to take advantage of

How to use AirN@v