Load OEB REMINDER Data into FWCs using MCDUs.
TASK 31-51-00-610-001-A
Load OEB REMINDER Data into FWCs using MCDUs.
Load OEB REMINDER Data into the FWC database in one operation or data by data.
2. Job Set-up Information
A. Work Zones and Access Panels
B. Referenced Information
3. Job Set-up
Subtask 31-51-00-860-050-B
Subtask 31-51-00-610-050-B
Subtask 31-51-00-860-052-B
[Rev.10 from 2021]
2026.04.01 00:37:18 UTC
Load OEB REMINDER Data into FWCs using MCDUs.
ZONE: 210
1. Reason for the JobLoad OEB REMINDER Data into the FWC database in one operation or data by data.
2. Job Set-up Information
A. Work Zones and Access Panels
| ZONE/ACCESS | ZONE DESCRIPTION |
|---|---|
| 210 | CKPT,FWD COMPT BHD TO FLT COMPT BULKHEAD |
| 824 |
| REFERENCE | DESIGNATION |
|---|---|
| TASK 24-41-00-861-002-A | Energize the Aircraft Electrical Circuits from the External Power |
| TASK 24-41-00-861-002-A-01 | Energize the Aircraft Electrical Circuits from the APU |
| TASK 24-41-00-861-002-A-02 | Energize the Aircraft Electrical Circuits from Engine 1(2) |
| TASK 24-41-00-862-002-A | De-energize the Aircraft Electrical Circuits Supplied from the External Power |
| TASK 24-41-00-862-002-A-01 | De-energize the Aircraft Electrical Circuits Supplied from the APU |
| TASK 24-41-00-862-002-A-02 | De-energize the Aircraft Electrical Circuits Supplied from the Engine 1(2) |
| TASK 31-51-00-610-002-A | Delete OEB REMINDER Data from FWCs using MCDUs. |
| TASK 31-51-00-610-003-A | Crossload OEB REMINDER Data into FWCs using MCDUs. |
| TASK 31-60-00-860-001-A | EIS Start Procedure |
| TASK 31-60-00-860-002-A | EIS Stop Procedure |
Subtask 31-51-00-860-050-B
A. Aircraft Maintenance Configuration
Energize the aircraft electrical circuits
(Ref. AMM TASK 24-41-00-861-002)
Subtask 31-51-00-010-050-B Energize the aircraft electrical circuits
(Ref. AMM TASK 24-41-00-861-002)
B. Get access to the avionics compartment.
(1) Put the access platform in position below the access door 824.
(2) Open the access door 824.
Subtask 31-51-00-865-050-A (1) Put the access platform in position below the access door 824.
(2) Open the access door 824.
C. Make sure that this(these) circuit breaker(s) is(are) closed:
Subtask 31-51-00-860-051-B 4. Procedure| PANEL | DESIGNATION | FIN | LOCATION |
|---|---|---|---|
| ** ON A/C NOT FOR ALL | |||
| 49VU | AUTO FLT/MCDU/1 | 11CA1 | B01 |
| ** ON A/C ALL | |||
| 49VU | FWS/FWC1/SPLY | 3WW | F01 |
| ** ON A/C NOT FOR ALL | |||
| 49VU | AUTO FLT/MCDU/1 | 11CA1 | H07 |
| ** ON A/C NOT FOR ALL | |||
| 121VU | CFDS/CFDIU/SPLY | 2TW | J18 |
| 121VU | CFDS/CFDIU/BACK/UP | 8TW | J17 |
| ** ON A/C ALL | |||
| 121VU | AUTO FLT/MCDU/2 | 11CA2 | N20 |
| 121VU | EIS/FWC2/SPLY | 2WW | Q07 |
| ** ON A/C NOT FOR ALL | |||
| 121VU | CFDS/CFDIU/SPLY | 2TW | J41 |
| 121VU | CFDS/CFDIU/BACK/UP | 8TW | J40 |
Subtask 31-51-00-610-050-B
A. Access to the ECAM OEB DATABASE UPDATE Menu
Subtask 31-51-00-610-051-B NOTE: The procedure below is applicable to each MCDU. The actions and results of this procedure occur on the MCDU used.
NOTE: If the response time of the FWCs is more than 1 second a IN PROGRESS message comes into view.
(1) Access to the ECAM OEB DATABASE UPDATE menu and update CODE | ACTION | RESULT |
|---|---|
| | On the MCDU: |
| 1.on one of the MCDUs, turn the OFF/BRT knob. |
|
| 2.on the MCDU, push the MCDU MENU mode key. |
|
| 3.on the MCDU, push the line key to the CFDS indication. |
|
| 4.on the MCDU, push the line key adjacent to the SYSTEM REPORT/TEST indication. |
|
| 5.on the MCDU, push the line key adjacent to the INST indication. |
|
| 6.on the MCDU, push the line key adjacent to the ECAM indication. |
NOTE: For FWC1 database updating enter in the ECAM 1 menu. For the FWC2 database enter in the ECAM 2 menu. |
| 7.on the MCDU, push the line key adjacent to the OEB DATABASE indication. |
NOTE: If the data base of the FWC1 or FWC2 is not valid, the VERSION is replaced by XXX and the check sum is replaced by XXXXX adjacent to the FWC1 or FWC2 indication. NOTE: If the opposite FWC does not respond, the NO RESPONSE message comes into view adjacent to the FWC1 or 2 indication. |
| 8.on the MCDU, with the MCDU keyboard, enter the code TWIN. NOTE: The loading of the FWC data base is possible only if the UPDATE CODE is entered. |
|
| 9.on the MCDU, push the line key adjacent to the UPDATE CODE indication. |
NOTE: If the code is not valid, the INVALID DATA message comes into view on the ECAM- 1 or 2/OEB DATABASE page. |
B. Uploading of the OEB REMINDER Data into FWC1 or 2
Subtask 31-51-00-740-050-B NOTE: It is possible to upload the FWC database only if you enter the UPDATE CODE (Ref. Para. 4.A.7.).
NOTE: It is necessary to upload each OEB REMINDER Data manually on an MCDU.
The OEB REMINDER Data includes:
- Warning code: ATA Chapter (two digits)/Sub ATA Section (two digits)/ Order number (three digits)/algorithmic key (three digits)
- Effect on Warning (EFFECT ON WARN : YES or NO)
- Effect on Status (EFFECT ON STS : YES or NO).
The OEB REMINDER Data includes:
- Warning code: ATA Chapter (two digits)/Sub ATA Section (two digits)/ Order number (three digits)/algorithmic key (three digits)
- Effect on Warning (EFFECT ON WARN : YES or NO)
- Effect on Status (EFFECT ON STS : YES or NO).
| ACTION | RESULT |
|---|---|
| | On the MCDU: |
| 1.On the MCDU, push the line key adjacent to the CREATE indication. |
|
| 2.On the MCDU, with the MCDU keyboard, enter the warning code. |
|
| 3.On the MCDU, push the line key adjacent to the CODE indication. |
NOTE: If the syntax is not correct, the FORMAT ERROR message comes into view. |
| 4.On the MCDU, below the EFFECT ON WARN indication, push the line key adjacent to the YES (or NO) indication. |
NOTE: The line keys adjacent to the YES or NO indications do not operate, if you did not enter the warning code. |
| 5.On the MCDU, below the EFFECT ON STS indication, push the line key adjacent to the NO (or YES) indication. |
NOTE: The line keys adjacent to the YES or NO indications do not operate if you did not enter warning code. |
| 6.On the MCDU, push the line key adjacent to the INSERT indication. NOTE: The line key adjacent to the INSERT information does not operate if you did not enter all the necessary data was not entered. |
NOTE: If the algorithmic key is not correct, the CHECK ENTRY message comes into view (then, it is necessary to enter the OEB DATA REMINDER again, refer to steps 2, 3, 4, 5). NOTE: If the FWC1 or 2 database is full (127 data), the UNABLE TO INSERT message comes into view. |
| 7.On the MCDU, push the line key adjacent to the RETURN information. |
|
| 8.On the MCDU, with the MCDU keyboard, enter a new VERSION reference. NOTE: The VERSION reference must be different from the one that is already entered. You must enter it only when all the modifications are completed. |
|
| 9.On the MCDU, push the line key adjacent to the VERSION indication. |
|
| 10.On the MCDU, push the line key adjacent to the CONFIRM indication. NOTE: The line key adjacent to the CONFIRM indication is does not operate if there is no loading or if the VERSION reference is not entered. |
NOTE: The INVALID DATA message comes into view if the loading is incorrect. NOTE: If you push the line key adjacent to the RETURN indication before you do an action on the line key adjacent to the CONFIRM indication the UPDATE WILL BE LOST message comes into view. If you do a new action on the line key adjacent to the RETURN indication, all the modifications are ignored. NOTE: If it is necessary to update the opposite FWC, you can do a crossloading (Ref. AMM TASK 31-51-00-610-003). |
C. Check of the Loaded OEB Data with the Flight Crew Operating Manual (FCOM) "OEB Operations Engineering Bulletins" Section
(1) Print the OEB REMINDER lists
(2) Do a check of the printed OEB list with the ECAM warnings and their codes given in the FCOM Preliminary Pages (List of Effective Operations Engineering Bulletin) or with the ECAM alert title (if displayed) and the Quick Reference Handbook (QRH).
(a) Make sure that the printed OEB data agrees with the data in the FCOM "OEB Operations Engineering Bulletins" section.
If the data does not agree, do the applicable procedure:
- loading (Ref. Para 4. B of this procedure), or
- deletion (Ref. AMM TASK 31-51-00-610-002), or
- crossloading (Ref. AMM TASK 31-51-00-610-003).
(b) When the check is correct, keep the OEB REMINDER list in the QRH, in the cockpit.
5. Close-up(1) Print the OEB REMINDER lists
| ACTION | RESULT |
|---|---|
| | On the MCDU: |
| 1.on the MCDU, push the line key adjacent to the RETURN indication until the ECAM-1 or 2/OEB DATABASE page comes into view. |
|
| 2.on the MCDU, push the line key adjacent to the LIST FWC1 or LIST FWC2 indication. |
|
| 3.on the MCDU, push the line key adjacent to the PRINT indication. |
NOTE: If there is more than one page, it is necessary on the MCDU:
|
(a) Make sure that the printed OEB data agrees with the data in the FCOM "OEB Operations Engineering Bulletins" section.
If the data does not agree, do the applicable procedure:
- loading (Ref. Para 4. B of this procedure), or
- deletion (Ref. AMM TASK 31-51-00-610-002), or
- crossloading (Ref. AMM TASK 31-51-00-610-003).
(b) When the check is correct, keep the OEB REMINDER list in the QRH, in the cockpit.
Subtask 31-51-00-860-052-B
A. Put the aircraft back to its initial configuration.
(1) On the MCDU, push the line key adjacent to the RETURN indication until the CFDS MENU page comes into view.
(2) Do the EIS stop procedure (Ref. AMM TASK 31-60-00-860-002)
(3) De-energize the aircraft electrical circuits
(Ref. AMM TASK 24-41-00-862-002)
(4) Put the system back to the serviceable condition.
(5) Put the aircraft back to the serviceable condition.
(1) On the MCDU, push the line key adjacent to the RETURN indication until the CFDS MENU page comes into view.
(2) Do the EIS stop procedure (Ref. AMM TASK 31-60-00-860-002)
(3) De-energize the aircraft electrical circuits
(Ref. AMM TASK 24-41-00-862-002)
(4) Put the system back to the serviceable condition.
(5) Put the aircraft back to the serviceable condition.