Professional Documents
Culture Documents
PROGRAMMING
0
PROCEDURE PROGRAMMING
GOAL:
• Purpose of this module is to present the basic philosophy and knowledge for
the procedure programming in SAGEM DS language, in order to know:
• how to read a procedure, SAGEM DS Language,
• how to create very basic computation and event detection,
• how to modify procedures already programmed by SAGEM DS.
TARGETED AUDIENCE:
• AGS users in charge of analysis programming.
• AGS users in charge of flight data analysis who wish to modify some
programming characteristics.
1
AGENDA
2
AGENDA
PARAMETER
PARAMETER (-t)
Local variables
Constant
• 5.3. Test rules
5.3.1. The operators of comparison
5.3.2. The test instructions EXERCISE 3
• 5.4. The basic functions
• 5.5. The enhanced functions EXERCISE 4
DATA_TO_EDIT window
DATA_TO_BASE, DATA_TO_FILE, DATA_TO_REPORT instructions
6. Methodology & Example of Standard Procedures EXERCISE 8
3
1. PROCEDURE PURPOSE & PROGRAMMING METHOD ON AGS
• The procedures are executed during automatic analysis (input and replay) in
order:
- 1. to compute additional parameters (parameters not recorded on board but used to
perform a consistent analysis).
- 2. to monitor flight situations for event detection and for data creation to external application.
4
1. PROCEDURE PURPOSE & PROGRAMMING METHOD ON AGS
5
1. PROCEDURE PURPOSE & PROGRAMMING METHOD ON AGS
PROCEDURE EXECUTION
MEDIA AUTOMATIC ANALYSIS
Procedure for
Additional Parameters
Recorded
Parameters Procedure for
Maintenance:
ALT_FINE - exceedence detection.
ALT_STDC, LATC,
ALT_COARSE - file for external SW. REPORTS
IASC,
LATP (Fine & Coarse) - maintenance
CONF…
FLT_NUM (BCD) parameter storage.
FLIGHT PHASE
DAY
FLIGHT N° FILES for
MONTH
FLIGHT CUT external SW
HOURS Procedure for
DATE
MINUTES
TIME Flight operation:
FLAP AGS
FUEL - Event detection.
FUEL FLOW Database
CONSUPTION... - file for external SW.
IAS
- parameter storage.
VRTG Additional parameters
6
1. PROCEDURE PURPOSE & PROGRAMMING METHOD ON AGS
7
2. ADDITIONAL PARAMETERS COMPUTATION
PURPOSE
Three kinds of additional parameters are computed by AGS from the recorded
parameters:
- 1. Additional parameters from filtering and correction.
- 2. Additional parameters for flight analysis improvements (Derived Parameters).
- 3. Additional parameters for AGS adaptation to the aircraft recording.
These parameters are also called “System Parameters”.
• Thanks to the user interface and to the SAGEM DS language, the user will
define procedures to specify computations that will be performed during the
automatic analysis.
8
2.1. PURPOSE, CLASSIFICATION, EXECUTION
CLASSIFICATION
• User can define up to 1000 procedures for additional parameters (from 0 to 999).
Procedure type Number Description Execution
At analysis
Procedure for initializations and start or stop
0 to 79 Parameter setting At flight start
end of treatments
or stop
Parameter filtering and correction
Procedure for 1st pass of analysis 80 to 99 1 to 32 Hz
Detection of ground touch
Procedure for parameter filtering
100 to 199 Parameter filtering and correction 1 to 32 Hz
and corrections
Procedure to compute parameters 200 to 299 Basic computation 1 to 32 Hz
for flight analysis improvement
300 to 499 Enhanced computation
(not depending on flight phase)
500 Message cut detection 1 to 32 Hz
502 Date & time computation
504 Flight number computation
506 Origin & destination computation
Procedure to compute the system
508 Flight phase computation
parameters for the flight
510 Flight change detection
management
512 Flight identification detection
514 Flight type computation
516 Flight recognition in realized flights
518 Detection of flight in progress
Procedure to compute parameters 600 to 699 Basic computation 1 to 32 Hz
for flight analysis improvement
700 to 899 Enhanced computation
(depending on flight phase)
Miscellaneous treatments 900 to 999 1 to 32 Hz
9
2.1. PURPOSE, CLASSIFICATION, EXECUTION
Execution
order 200 200 200 200
201 201
300 300
540
Time order
0 1/4 1/2 3/4 1 sec.
10
2.2 CORRECTION & FILTERING OF RECORDED PARAMETERS
• For each concerned parameter the user must create a computed parameter
defined by a procedure containing the algorithm to compute the
corresponding correction
11
2.3. COMPUTATION OF NEW PARAMETERS
// IVV COMPUTATION
// IVV = derived from ALTITUDE
// =======================
IVV=ALTITUDE - PREVIOUS_ALTITUDE
12
2.4. TUNING OF THE SYSTEM PARAMETERS FOR FLIGHT MANAGEMENT
13
2.4. TUNING OF THE SYSTEM PARAMETERS FOR FLIGHT MANAGEMENT
14
2.4. TUNING OF THE SYSTEM PARAMETERS FOR FLIGHT MANAGEMENT
15
2.4. TUNING OF THE SYSTEM PARAMETERS FOR FLIGHT MANAGEMENT
16
2.4. TUNING OF THE SYSTEM PARAMETERS FOR FLIGHT MANAGEMENT
17
2.4. TUNING OF THE SYSTEM PARAMETERS FOR FLIGHT MANAGEMENT
18
2.4. TUNING OF THE SYSTEM PARAMETERS FOR FLIGHT MANAGEMENT
19
2.4. TUNING OF THE SYSTEM PARAMETERS FOR FLIGHT MANAGEMENT
20
2.4. TUNING OF THE SYSTEM PARAMETERS FOR FLIGHT MANAGEMENT
Internal Display Procedure Validity
Parameter Description Internal Range Display Procedure Validity
Parameter Description Format Range Format No. Period
Format Format No. Period
Description : Current date (recorded during flight)
Description : Current date (recorded during flight)
User prog. : Must contain the number CCYYMMDD where:
User prog. # :DD:
Must contain
number ofthe number
days CCYYMMDD
per month (1 to 31) where:
# DD: number of days per month (1 to 31) Integer, right 0 to
List of system DATE_R
DATE_R
# MM: number of months per year (1 to 12)
# MM: number of months per year (1 to 12)
# YY: number of years per century (0 to 99)
# #CC:
YY:number
numberofofcenturies
years per(19
century
to 47)(0 to 99)
Integer, right
justified
justified
0 to
47121231
47121231
DATE
DATE
502
502
21
2.4. TUNING OF THE SYSTEM PARAMETERS FOR FLIGHT MANAGEMENT
Internal
Internal Display
Display Procedure
ProcedureValidity
Validity
Parameter
Parameter Description
Description Range
Range Format
Format
Format Format No.
No. Period
Period
Description
Description : : Distance
Distanceon onground Integer,
DIST ground Integer,right
right +/-9999
+/-9999 DECIMAL
DIST AGS justified miles DECIMAL ------
AGS action. : Used for the displayofofcurves
action. : Used for the display curvesy=f(distance)
y=f(distance) justified miles
22
2.4. TUNING OF THE SYSTEM PARAMETERS FOR FLIGHT MANAGEMENT
23
3. EVENT DETECTION PROGRAMMING
PURPOSE
The procedures for maintenance and flight operation allow to define all the treatments to be
performed during the automatic analysis.
• Maintenance Activities:
- EGT, N1, N2, Vibration exceedences…
- Output data files for external Engine Trend Monitoring software (ECM, SAGE, COMPASS),
- Output data files for external Performance Monitoring software (APM, other airline application)
24
3.1. PURPOSE AND CLASSIFICATION
CLASSIFICATION
• The user can define up to 10000 procedures for maintenance and for flight
operation:
- The procedures between 100 and 999 are reserved to compute specific
additional parameters,
- The procedures between 1000 and 9999 are reserved for event monitoring.
• Thanks to the user interface, the user can define the procedures to specify
the monitoring to be performed. Then, these procedures will be executed
during automatic analysis.
25
3.2. ANALYSIS FOR FLIGHT OP. & MAINTENANCE DEPARTMENTS
26
3.2. ANALYSIS FOR FLIGHT OP. & MAINTENANCE DEPARTMENTS
27
3.3. MAIN PRINCIPLES ABOUT EVENT MONITORING
28
3.3. MAIN PRINCIPLES ABOUT EVENT MONITORING
MONITORING PERIOD
EXCEEDENCE
MONITORING
EXCEEDENCE
CHECK
RESET CONDITION
SEVERITY CLASS 3
SEVERITY CLASS 2
SEVERITY CLASS 1
Immediate Storage: the exceedence check is done during the monitoring period.
29
3.3. MAIN PRINCIPLES ABOUT EVENT MONITORING
MONITORING PERIOD
8 CRUISE
9 DESCENT
7 CLIMB 10 APPROACH
13 GO AROUND ->7
6 INITIAL CLIMB 11 FINAL APPROACH
TOUCH AND GO ->3
1 ENGINE STOP 3 TAKE OFF 5 SECOND SEGEMENT EXCEEDENCE 12 LANDING
SEVERITY CLASS 3
SEVERITY CLASS 2
SEVERITY CLASS 1
RESET CONDITION 3
EVENT
2 EXCEEDENCE CHECK
Delayed Storage:
the exceedence check is done after the monitoring period.
30
3.3. MAIN PRINCIPLES ABOUT EVENT MONITORING
1 Monitoring period
3 RESET Condition
11 FINAL APPROACH
14 TAXI IN
In this example,
1. Only one exceedence is memorized during the monitoring period according programming
2. Then, during the check period, the detected event is stored in the database
3. At the end of the flight the procedure is reset to be ready for the next flight
31
4. GRAPHIC USER INTERFACE
32
4.1. THE THREE LISTS OF PROCEDURES
Area to display/modify
the defined limits
33
4.2. THE PROCEDURE PROGRAMMING WINDOW
Selected screen
configuration
The procedure programming window
GREEN-
BLUE
constants
34
4.2. THE PROCEDURE PROGRAMMING WINDOW
• Open procedures and look at all different areas, colors used in procedure code:
- Open Procedure 212, from procedures for additional parameter window,
- Open Procedure 1020, from procedures for Flight Operation.
35
4.2. THE PROCEDURE PROGRAMMING WINDOW
Undo
Right click
Select all
Comment, Uncomment
Help on SAGEM DS
Language
Parameters list
36
4.2. THE PROCEDURE PROGRAMMING WINDOW
37
4.3. HELP WINDOW FOR SAGEM DS LANGUAGE
The procedure programming window Select function and push HELP button
to display:
- Description
- Syntax
- Example
double-click to insert
in procedure code
38
4.4. CHECK OF PROCEDURE SYNTAX
Test of a procedure:
• Green light, the syntax is correct, no error. The procedure can be validated.
• Orange light, warning only. The procedure can be validated.
Automatic
Syntax
Analysis
Manual Syntax
Analysis
39
4.4. CHECK OF PROCEDURE SYNTAX
Test of a procedure:
• Red light, procedure contains an error. The procedure can not be validated.
No flight data analysis will be possible with this database version.
Click on error
message
to jump to bad line
40
5. SAGEM DS LANGUAGE
Introduction
41
5.1. THE BASIC RULES: COMPUTATION AND AFFECTATION
• Example:
- Comparison:
if configuration=2 and speed>250…
- Computation: 3
2=1+1
42
5.2. BASIC RULES, THE VARIABLES
AGS SAGEM DS language allows user to create computation using variables that
can be:
• Parameters,
• Local variables,
• Constants.
PARAMETERS
• Concern the Recorded and Additional Parameters,
• Names used are declared in Parameter list of database version and use always
uppercase letter,
Example: ALT_STD,
• Characteristics of Recorded Parameter are:
- All types except ‘Computed on Ground’ and ‘Constant’.
- To avoid data violation, it is forbidden to affect a value to a Recorded Parameter.
Example: ALT_STD = 0
• Additional Parameter are:
- Types ‘Computed on Ground’.
- It is possible to affect a value: P=2.
Example:N1_AVG= (N11+N12)/2
• Parameter values can be displayed using manual analysis functions (tabular, f(t),…)
43
5.2. BASIC RULES, THE VARIABLES
PARAMETER(-t) , PARAMETER(+t)
44
5.2. BASIC RULES, THE VARIABLES
LOCAL VARIABLES
45
5.2. BASIC RULES, THE VARIABLES
CONSTANT PARAMETERS
46
5.2. BASIC RULES, THE VARIABLES
47
5.2. BASIC RULES, THE VARIABLES
• 2. Compute and memorize average value for N1 on both engines [ parameter: AVG_N1 ].
48
5.2. BASIC RULES, THE VARIABLES
Exercise 2. PART 3/4 – Memorize altitude 2 seconds before the current time
• 2. Memorize average value for standard altitude 2 seconds before the current time
[ parameter: ALT2 ].
Help: refer to chapter 5.2. “VALUE OF A PARAMETER t SECONDS BEFORE/AFTER THE CURRENT TIME”
49
5.2. BASIC RULES, THE VARIABLES
• 2. Memorize your initials (name) [ parameter MYNAME ] (defined with Mode: ASCII ; length <=4 ).
50
5.3. TEST RULES
TEST PURPOSE
• Tests are very important in AGS procedures because all the time something is
done in accordance with the result of a condition only.
• For instance: “if the speed at final approach below 200 ft is too high, flight
situation is abnormal then AGS stores event for statistic analysis”.
TEST SYNTAX
for instance: “if ( the speed is greater than 140 kts ) then…”
51
5.3.1. THE OPERATORS OF COMPARISON
Relational = Equal to “if the speed is greater than 140 kts then…”
# Different from
< Less than
> Greater than Becomes:
<= Equal to or less than
>= Equal to or greater than “if ( speed > 140 ) then…”
52
5.3.2. THE TEST INSTRUCTIONS
ENDIF
Example:
53
5.3.2. THE TEST INSTRUCTIONS
THEN action 1
ELSE action 2
Exemple:
ENDIF
IF ((N21> 40) AND (N22> 40)) THEN
engine_run=1
ELSE
engine_run=0
ENDIF Multiple condition
54
5.3.2. THE TEST INSTRUCTIONS
55
5.3.2. THE TEST INSTRUCTIONS
56
5.3.2. THE TEST INSTRUCTIONS
57
5.3.2. THE TEST INSTRUCTIONS
• 2. Modify procedure 606 to use this constant (in order to modify easily the limit).
58
5.3.2. THE TEST INSTRUCTIONS
• Advice:
- Use LDGL parameter for landing gear position information (AIR or GROUND)
- Use constant parameters AIR and GROUND
59
5.3.2. THE TEST INSTRUCTIONS
60
5.4. THE BASIC FUNCTIONS
Exercise:
Open procedure n° 224 from
Procedures for Additional
Parameter list of version 10385,
Use help on SAGEM DS
Language to understand the
procedure.
61
5.5. THE ENHANCED FUNCTIONS
62
5.5. THE ENHANCED FUNCTIONS
63
5.5. THE ENHANCED FUNCTIONS
• 2. Validate version
64
5.6. THE EVENT STORAGE
PRINCIPLES
• AGS allows user to create procedures to detect particular flight conditions, those flight
conditions can be reported in AGS Database with EVENT instruction.
Each event store in database is identified by the procedure N° used to detect it.
Event can be programmed for FOQA and Maintenance Purpose.
PARTICULAR EFFECT
• To avoid not useful multiple event storage,
AGS stores ONE EVENT PER FLIGHT PER PROCEDURE ONLY.
If EVENT instruction is executed in Procedure X, only the first execution will be edited
and/or stored.
• Note: If necessary, the RESET instruction enables to store more than one event per flight.
65
5.6. THE EVENT STORAGE
EVENT(Time, Edit, Storage, Severity Class, Optional snapshot parameters in analysis report)
where:
Time, defines event dating. Link to System Parameter T.
Edit, equal to EDIT to display event in Analysis report, NOEDIT not
Storage, equal to STAT to store event in Database, NOSTAT not.
Severity Class, from CLASS1 to CLASS9 to indicate importance of event.
Optional Snapshot Parameters, up to 50 parameters to display in analysis report.
66
5.6. THE EVENT STORAGE
EVENTV(Time, Edit, Storage, Severity Class, Limit value, Maximum value, Average gap, Exceedence
duration, Optional Snapshot Parameters in analysis report)
where:
Time, defines event dating. Link to System Parameter T.
Edit, equal to EDIT to display event in Analysis report, NOEDIT not.
Storage, equal to STAT to store event in Database, NOSTAT not.
Severity Class, from CLASS1 to CLASS9 to indicate importance of event.
Limit value, value used in procedure to compare the normal and the abnormal flight situation.
Maximum value, reached at event instant.
Average gap, average value over/under the limit.
Exceedence duration.
Optional Snapshot Parameters, up to 50 parameters to display in analysis report.
EVENTV(T, EDIT, STAT, CLASS1, lim1, max_val, avg_gap, exd_dur, SnPar1, …, SnparX)
Add. Event Characteristics Opt. Snapshot Parameters
Note: The arguments: Limit value, Maximum value, Average gap, Exceedence duration are not computed by EVENTV
instruction, they are input information, they must be computed by another instructions.
67
5.6. THE EVENT STORAGE
EVENT STORAGE IN ANALYSIS REPORT
Event characteristics stored in Database thanks to Event characteristics stored in Database thanks
EVENTV instruction + Snapshot parameters to EVENTV instruction (without snapshot parameters)
Flight Date Time Flt Phase Event Level Limit Max. Durat Avg.Gap ---------- Event Description ----------
0001 07/05/2006 08:05:28 TAKE OFF 1002 3 138 142.6 0 4.625 Speed high at lift off
IASC=142.63 knot VR=123 knot
CONF=3 PITCH=13.36 deg
0001 07/05/2006 08:14:39 CLIMB 2002 1 1.4 1.629 3 0.109 High positive vertical acceleration during flight
0001 07/05/2006 10:07:12 FINAL 3104 1 0 -1.758 27 1.25 Pitch low during final approach, between 1000 and 100 feet
0001 07/05/2006 10:07:40 FINAL 1046 1 185 190.3 7 3.554 Speed high in conf 3 (flap 20 - slat 22)
0001 07/05/2006 10:14:40 APPROACH 1004 3 260 268 21 5.542 Speed high at low altitude, below 10000 feet
ALT_STDC=2520 FEET
0001 07/05/2006 10:17:27 FINAL 6000 3 0 0 5 0 GPWS Warning
HEIGHT=1088 feet IASC=135.00 knot
CONF=4 IVV=-1784 ft/min
0001 07/05/2006 10:18:28 FINAL 4400 1 Landing gear out of sequence
0001 07/05/2006 10:18:32 FINAL 6000 3 0 0 5 0 GPWS Warning
HEIGHT=476 feet IASC=125.75 knot
CONF=4 IVV=-683 ft/min
0001 07/05/2006 10:19:16 GO AROUND 7002 1 Go around
HEIGHT=72 feet
0001 07/05/2006 10:19:19 GO AROUND 3000 2 15 17.58 0 2.578 Pitch high at take off
PITCH=17.58 deg GSC=139.00 knot
0001 07/05/2006 10:19:48 APPROACH 5030 3 95 96 22 0.858 High power during approach
0001 07/05/2006 10:27:16 FINAL 1020 1 134.4 138.6 6 2.736 Speed high during approach at 1000 feet
HEIGHT=992 FEET VAPP=124 KTS
68
5.6. THE EVENT STORAGE
69
5.6. THE EVENT STORAGE
• Note:
- Class 1 if speed>130
- Class 2 if speed>140
- Class 3 if speed>150
70
5.6. THE EVENT STORAGE
• 2. Create a procedure No 3100 for Maintenance in order to detect N2 exceedence during cruise:
- Use TIME_OVER_LIMIT function with:
Limit to check: a constant parameter N2_MAX_CRUISE (90%)
Check on: Both engines (Left and Right: N21 and N22)
Values to memorize: time over limit, maximum value reached, average gap over the limit, limit used
- The higher maximum of N2 between both engines is taken into account to memorize the
CLASS 1 event
- Display memorized value in the analysis report at taxi in
71
5.7. THE DATA MANAGEMENT FUNCTIONS
DATA_TO_REPORT
DATA_TO_BASE
DATA_TO_FILE
72
5.7. THE DATA MANAGEMENT FUNCTIONS
DATA_TO_REPORT function:
• DATA_TO_REPORT instruction enables to store parameters defined in “Data
to Edit” window in:
Analysis Report.
73
5.7. THE DATA MANAGEMENT FUNCTIONS
DATA_TO_BASE function:
• DATA_TO_BASE instruction enables to store parameters defined in “data to
edit” window in:
AGS Database.
74
5.7. THE DATA MANAGEMENT FUNCTIONS
DATA_TO_FILE function:
• DATA_TO_FILE instruction enables to store parameters defined in “data to
edit” window in:
an external File.
75
5.7. THE DATA MANAGEMENT FUNCTIONS
76
5.7. THE DATA MANAGEMENT FUNCTIONS
• 1. Use the help function in order to look at the different data management functions
• 4. Validate version
77
5.7. THE DATA MANAGEMENT FUNCTIONS
• 1. Create a procedure for flight operation No 8004 in version 492 in order to:
Count in seconds the duration of the taxi-out
• 3. Validate version
78
6. METHODOLOGY & EXAMPLE OF STANDARD PROCEDURE
79
6. METHODOLOGY & EXAMPLE OF STANDARD PROCEDURE
80
6. METHODOLOGY & EXAMPLE OF STANDARD PROCEDURE
81
6. METHODOLOGY & EXAMPLE OF STANDARD PROCEDURE
• 2. Note the characteristics of the detected event No 1020 in the analysis report.
• 3. Copy procedure for flight operation No 1020 from DB Version 10385 to DB Version 492.
• 5. Modify procedure 1020 limits to detect a high speed during approach at 1000 feet:
- The limit for a class 3 event is 3 sec at VAPP+15
- The limit for a class 2 event is 3 sec at VAPP+10
- The limit for a class 1 event is 3 sec at VAPP
82
6. METHODOLOGY & EXAMPLE OF STANDARD PROCEDURE
• 9. Note the characteristics of the detected event No 1020 in the analysis report.
83
Would you like to know more ?
84