EasyManua.ls Logo

Thales ADS-B - Page 170

Thales ADS-B
282 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
AS 680/682
Record and Replay Description, Operation and Maintenance
ADS−B
4−70 Ed. 10.07
4.6.5.1.1 RAC I/O Parameter: Logging to File and Standard Output
The logging to file and to standard output is rather easy. Only the ASTERIX output data can be logged.
File logging of raw data is not necessary, because the input file contains the raw data or, if read from
standard input, the raw data can be logged by the ’Raw Data Record’ tool (refer to section 4.6.2.4)
providing the input.
In case of logging to a file the ’Automatic file increment’ feature can be enabled. More information
about this feature is found in section 4.6.3.1.5 . The logged ASTERIX data can be read from the ’Re-
play Asterix Data’ tool described in section 4.6.7.
The following proprietary format is used for the ASTERIX output.
If logging to a file is enabled, the first row is a comment line starting with a ‘#’. The next item in the
comment line indicates the ASTERIX category, that is ‘CAT21’. Subsequently the ASTERIX fields and
subfields are assigned to positions to be able to locate ASTERIX field values. In the following (non−
comment) lines, all ASTERIX fields and subfields are listed, set to the position described in the first
comment line.
Logging to standard output does not output the comment line, because, in general, the first line to
standard output is not catched by tools reading the output. However, every logfile must get the first
comment line.
The actual logged ASTERIX records, being the values of the ASTERIX fields and subfields, are listed
‘|’ separated in the sequence described in the first comment line. If no values are available a ‘−‘ is
required instead.
Example of ASTERIX logging:
# CAT21 1:ds_sac 2:ds_sic 3:trd_dcr 4:trd_gbs 5:trd_sim 6:trd_tst 7:trd_rab 8:trd_saa 9:trd_spi 10:trd_vn
11:trd_atp 12:trd_arc 13:tod 14:wgs_lat 15:wgs_lon 16:add 17:galt 18:fom_ac 19:fom_mn 20:fom_dc
21:fom_pa 22:lt_mds 23:lt_uat 24:lt_vdl 25:lt_otr 26:roll 27:fl 28:as_im 29:as_as 30:tas 31:head 32:barvr
33:geovr 34:gv_gs 35:gv_ta 36:rot_ri 37:rot_rot 38:tid 39:vac 40:toda 41:ts 42:ec 43:mr_ind 44:mr_ws
45:mr_wd 46:mr_tmp 47:mr_trb 48:issa_sas 49:issa_src 50:issa_alt 51:fssa_mv 52:fssa_ah 53:fssa_am
54:fssa_alt 55:ti_ind 56:ti_nav 57:ti_nvb 58:ti_rep 59:ti0_tca 60:ti0_nc 61:ti0_tcp 62:ti0_alt 63:ti0_lat 64:ti0_lon
65:ti0_pt 66:ti0_td 67:ti0_tra 68:ti0_toa 69:ti0_tov 70:ti0_ttr 71:ti1_tca 72:ti1_nc 73:ti1_tcp 74:ti1_alt 75:ti1_lat
76:ti1_lon 77:ti1_pt 78:ti1_td 79:ti1_tra 80:ti1_toa 81:ti1_tov 82:ti1_ttr 83:sigam 84:m3a 85:m3a_gc
86:m3a_cne 87:m3a_m3a
96|7|0|0|0|0|0|0|0|0|1|0|49559.391|−|−|400A55|38000.00|−|−|−|−|1|0|0|0|−|370.00|−|−|−
|−|−|62.50|0.141052|128.7653|−|−|−|0|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|
−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|
96|7|0|0|0|0|0|0|0|0|1|0|49559.508|−|−|3C6666|−|−|−|−|−|1|0|0|0|−|220.25|1|0.553000|35
6|−|−62.50|−|−|−|−|−|−|0|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|
−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|
Logging ASTERIX data means the logging of output data, i.e. only successfully decoded and checks
passing telegrams are considered. To be able to reconstruct the processing (from reading raw data
to sending ASTERIX data) performed by the tool, it is necessary to trace the telegrams. The tracing
of the replay is possible by enabling the ’Detailed Telegram Decomposition’ mode (refer to section
4.6.5.2 and to following section 4.6.5.1.2 )

Table of Contents