Aviation metrology Training
description
Transcript of Aviation metrology Training
Maintenance training
AviMet®
Page 2 / date / name / ©Vaisala
Training content
� Introduction� Common tools
� System tools
Page 3 / date / name / ©Vaisala
AviMet® User groups
LAN / Ethernet
Observerworkstation
(OWS)
Forecasterworkstation
(FWS)
Maintenanceworkstation
(RCM)
ATC Displays(WV)
AviMet®CDU Servers(Duplicated)
Sensor datafrom aerodrome There are 4 different user groups in
AviMet system
•Observer (OWS)
•Forecaster (FWS)
•Weather viewer (VW)
•Maintenance (RCM)
Page 4 / date / name / ©Vaisala
User privileges
� User groups have different privileges.
� E.g. forecaster cannot open the METAR/MET REPORT Manager for METAR.
� Privileges are configurable.� Implemented with active
directory of Windows operating system.
Observerworkstation
(OWS)
Forecasterworkstation
(FWS)
METAR Manager
Page 5 / date / name / ©Vaisala
Data flow in AviMet®� Sensor or weather station� Short term averaging (up to 1 minute)
and other high-frequency tasks� Basic data validation� For serial data generated by sensor,
weather station acts only as gateway
� CDU� Low-frequency sampling and long
term averaging� Meteorological calculations
� Applications� Unit conversions and data formatting
Sensor I/O
Sensor /Weather Station
Calculations
Application Application
Page 6 / date / name / ©Vaisala
Training content
� Introduction� Common tools� System tools
Page 7 / date / name / ©Vaisala
Application Toolbar
� Provides access to other AviMet applications
� Some buttons may be disabled depending on the workstation role� Note field can be used to broadcast messages to other AviMet
workstations� Displays a small color icon in lower right corner of the screen
� green: OK (server A or B)� red: problem (server A or B)
METAR / SPECI
METREP / SPECIAL
METAR / MET REP Manager
Weather View
Actuals
ASCII Log View
SYNOP
TAF
SIGMET
GAMET
AIRMET
AFTN Monitor
Page 8 / date / name / ©Vaisala
Training content
� Introduction� Common tools
� System tools
Page 9 / date / name / ©Vaisala
SensorIO Monitor� SensorIO
Monitor is used to view the status of sensors.
� Sensor communication can be logged on screen or into a file.
RCM application
Page 10 / date / name / ©Vaisala
Sensor Terminal (1/2)� Sensor Terminal is a low
level tool for listening selected I/O port.
� Shows all data received by port.
� Cuts normal data flow from port to rest of the AviMet system when port is opened.
� Used also for maintenance connections to sensors.
RCM application
Page 11 / date / name / ©Vaisala
Sensor Terminal (2/2)
� Listen port� Select port from list� Open port (cuts of data flow into rest
of AviMet system.)� Close port when ready
� Open maintenance connection� Select port from list� Open port� Type appropriate commands to
sensor (Open sensor maintenance mode, give commands and close the maintenance mode.)
� Close port
Port selection
Log to fileIncoming data
Open / closeport
Page 12 / date / name / ©Vaisala
Diagnostic Monitor (1/4)� Diagnostic
Monitor is used to view system status, applications connected to servers and data in the system.
RCM application
Page 13 / date / name / ©Vaisala
Diagnostic Monitor (2/4)
� AviMet system status is indicated with “traffic lights”.
� If everything is ok, all colors are green. If there is malfunction in the system it is indicated with red color.
� In duplicated systems user can also activate another server by force.
Heartbeatblinking
Switchover modeselection
CDUselection
Page 14 / date / name / ©Vaisala
Diagnostic Monitor (3/4)
� All data produced by services is stored into objects.
� An object is basically a list of data values with labels, types and statuses.
� E.g. 1_WIND_SENSOR object contains all relevant data received from wind sensor 1 (SensorIO service).
Objects 1_WIND_SENSORobject
Instant windspeed
Instant winddirection
Page 15 / date / name / ©Vaisala
Diagnostic Monitor (4/4)
� All system users (applications and services) are listed in user list.
� At this point a user is any software module that is connected to core ROA system.
Systemusers
Page 16 / date / name / ©Vaisala
Event Monitor
� Alarms in AviMet are viewed with Event Monitor.
� Alarms can be acknowledged in occurrence order.� Alarms are logged into file.� Application is mainly a tool for maintenance personnel.
OWS, FWS, RCM application
Page 17 / date / name / ©Vaisala
Event Monitor: Alarm types� TECH (Technical)
� There is a communication problem between the CDU and a sensor, or another unusual technical problem.
� OPER (Operational)� There is a predefined change in
weather.
� MESG (Message Notifications)� Information on sent weather
reports or reason for triggering a SPECI/SPECIAL report.
� NONE (Internal)� There is an unusual serious
internal problem, for example, within the CDU.
Page 18 / date / name / ©Vaisala
Event Monitor: Technical alarms
� Communication problems� bad message
� noise, signaling problems� message missing
� noise, signaling problems, cable problems
� Sensor problems� sensor powered off or defective
� sensor indicating internal error status
� Cross-checker alarms� inconsistent sensor values� value out of bounds
Page 19 / date / name / ©Vaisala
Event Monitor: Operational alarms
� Changing weather conditions � Limit alarm
� wind speed
� e.g. wind > 20 KT, RVR < 800 m
� Rate of change alarm� too rapid change of a parameter
Page 20 / date / name / ©Vaisala
Event Monitor: Message notifications
� Sent standard messages� Standard observation time
� METAR
� MET REPORT
� Special conditions� SPECI
� SPECIAL
Page 21 / date / name / ©Vaisala
Event Monitor: Internal alarms� Software self-diagnostics� Conflicting object information
� problem in the system configuration
� Conflicting user information� there are unlicensed applications in the
system� i.e. if there are multiple instances of
ACTUALS application
� Conflicting duplication information� the system could not determine which
CDU was the primary server
� Database error� AviMet tried to read or write data to the
database but did not succeed
Page 22 / date / name / ©Vaisala
Event Monitor: Statuses 1/2
� The Event Monitor Status icon is located on the taskbar of the Windows®operating system, next to the System Status icon.
� The color of the icon shows if there are events in Event Monitor and whether the events have been acknowledged or not.
Event Monitor Status Icon Colors� Red = There are unacknowledged events.
� Yellow = All events have been acknowledged by the user.� Green = There are no events.
� Blue = There are only unacknowledged events of the type Message Notification.
� CAUTION: The Event Monitor icon shows only the status of the events that have been selected for viewing from the View menu. For example, if you have selected only View - Technical Events , and the Event Monitor icon is green, there can be unacknowledged events of another type.
Page 23 / date / name / ©Vaisala
Event Monitor: Statuses 2/2� On the left in the Event Monitor window, there is an icon in front of each
event message. When an event message first appears, the icon is red. When the event has been acknowledged, the icon turns yellow.
Icon Color Explanation� Red = Unacknowledged event� Yellow = Acknowledged event� Blue = Unacknowledged event of the type Message Notification
Page 24 / date / name / ©Vaisala
Event Monitor: Bottom Line mode
� Event Monitor can also be used in the Bottom Line mode: instead of the entire Event Monitor window, a single line that shows one event at a time at the bottom of the screen can be displayed.
� Application can again be viewed in full by double-clicking the event area
Page 25 / date / name / ©Vaisala
Event Viewer (1/2)� Operating system tool.� Opened with Start /
Settings / Control Panel / Administrative Tools / Event Viewer.
� Shows events of AviMet system.
� available on main servers and with administrator user rights
OWS, FWS, RCM application
Page 26 / date / name / ©Vaisala
Event Viewer (2/2)
� Application log shows AviMet events (among other events).
� Three type of events:� Errors
� malfunction in system� require actions
� Warnings� system may work inadequately
� may require actions
� Information� informative only� no actions required
Errors
Information
Warnings
Page 27 / date / name / ©Vaisala
Data Source Manager (1/2)
� Data Source Manager is used to select the source data for pressure calculations.
� If Data Source Manager is used the pressure page in Actuals is not used.
OWS, (RCM) application
Page 28 / date / name / ©Vaisala
Data Source Manager (2/2)
� Source for prevailing visibility is also selected with Data Source Manager.
� Prevailing visibility is new ICAO Annex 3 Amendment 73 requirement.
OWS, (RCM) application
Page 29 / date / name / ©Vaisala
Actuals (1/7)� Actuals application is used
to view real time data and to set it manually if necessary.
� MANUAL\BACKUP setting is recommended only in case of a sensor malfunction.
� Select Actuals program by pressing A-icon in the application toolbar.
OWS application
Page 30 / date / name / ©Vaisala
Actuals (2/7)
� Actuals allows the user to enter data values manually and set the backup data source.
� Data content varies depending on installed instruments.
� Units can be KT or MPS, ft or m.
� Supported entries include:� Wind� Cloud� RVR and visibility� Temperature� Manual observations� Background luminance
Page 31 / date / name / ©Vaisala
Actuals : wind data (3/7)� INS - Instant wind direction and
speed in kt� 2AVG - 2 minute mean average
wind direction and speed in kt� 2MNM - 2 minute minimum wind
direction and speed in kt� 2MAX - 2 minute maximum wind
direction and speed in kt� 2XAVG - Tail\head and Cross
wind in kt� 10AVG - 10 minute mean
average wind direction and speed in kt
� 10MNM - 10 minute minimum wind direction and speed in kt
� 10MAX - 10 minute maximum wind direction and speed in kt
Mode selection
Page selection
Page 32 / date / name / ©Vaisala
Actuals : cloud data (4/7)
� CH1 INS - Instant lowest cloud height in feet
� CH2 INS - Instant second cloud height in feet
� CH3 INS - Instant third cloud height in feet
� BASE - Calculated lowest cloudbase based on CH1ins
� VER VIS - Vertical visibility in case VV conditions are detected
Page 33 / date / name / ©Vaisala
Actuals : RVR and visibility data (5/7)� RVR 1A - Runway visual
range, one minute average� RVR 10A - Runway visual
range, 10 minute average� RVR 10M - Runway visual
range, minimum of 10 minute� RVR 10X - Runway visual
range, maximum of 10 minute� VIS 1A - Visibility, one minute
average� VIS 10A - Visibility, 10 minute
average� VIS 10M - Visibility, minimum
of 10 minute� VIS 10X - Visibility, maximum
of 10 minute
Page 34 / date / name / ©Vaisala
Actuals : temperature and humidity data (6/7)� TAINS - Instant air temperature� TA10M - Temperature minimum
of 10 minute� TA10X - Temperature maximum
of 10 minute� TDINS - Dew point� RHINS - Relative humidity %
Page 35 / date / name / ©Vaisala
Actuals : manual observation data (7/7)
� METAR\SPECI template can use the manually entered values for
� Present weather codes
� Recent weather codes
� Runway State
� Cloud amounts and types. exception: first cloudbase
� Remark
� Note: remember to define measurement site “present weather” and select location “ManObs” in METAR/MET REPORT Manager program so that the manual values affect the next triggered report
Page 36 / date / name / ©Vaisala
Training content
� Introduction� Common tools
� System tools Thank you.
Any Questions?