AviMet AWOS - User's Guide - English - M210881EN-V

M210881EN-V
User Guide
â
Vaisala AviMet
Automated Weather Observing System
PUBLISHED BY
Vaisala Oyj
Vanha Nurmijärventie 21, FI-01670 Vantaa, Finland
P.O. Box 26, FI-00421 Helsinki, Finland
+358 9 8949 1
Visit our Internet pages at www.vaisala.com.
© Vaisala 2020
No part of this document may be reproduced, agreements are included exclusively in the
published or publicly displayed in any form or by applicable supply contract or the General
any means, electronic or mechanical (including Conditions of Sale and General Conditions of
photocopying), nor may its contents be modified, Service of Vaisala.
translated, adapted, sold or disclosed to a third This product contains software developed by
party without prior written permission of the Vaisala or third parties. Use of the software is
copyright holder. Translated documents and governed by license terms and conditions
translated portions of multilingual documents are included in the applicable supply contract or, in
based on the original English versions. In the absence of separate license terms and
ambiguous cases, the English versions are conditions, by the General License Conditions of
applicable, not the translations. Vaisala Group.
The contents of this document are subject to This product may contain open source software
change without prior notice. (OSS) components. In the event this product
contains OSS components, then such OSS is
Local rules and regulations may vary and they governed by the terms and conditions of the
shall take precedence over the information applicable OSS licenses, and you are bound by the
contained in this document. Vaisala makes no terms and conditions of such licenses in
representations on this document’s compliance connection with your use and distribution of the
with the local rules and regulations applicable at OSS in this product. Applicable OSS licenses are
any given time, and hereby disclaims any and all included in the product itself or provided to you
responsibilities related thereto. on any other applicable media, depending on
This document does not create any legally each individual product and the product items
binding obligations for Vaisala towards customers delivered to you.
or end users. All legally binding obligations and
Table of contents
Table of contents
1. About This Document.................................................................................... 13
1.1 Version information........................................................................................... 13
1.2 Related manuals.................................................................................................13
1.3 Documentation conventions............................................................................ 14
1.4 Trademarks......................................................................................................... 15
2. Product Overview............................................................................................16
2.1 System Introduction.......................................................................................... 16
2.2 AviMetâ Product Platform................................................................................17
2.3 System Configuration........................................................................................ 18
2.4 Use of Anti-Virus Software............................................................................... 18
2.5 End-user Software Applications...................................................................... 18
2.5.1 Viewing Current Data..................................................................................19
2.5.2 Editing and Sending Weather Reports..................................................... 19
2.5.3 Entering Data Manually............................................................................. 20
2.5.4 Viewing Past Data...................................................................................... 20
2.5.5 Managing Data Source and Settings......................................................... 21
2.5.6 Monitoring System Operation................................................................... 22
2.6 System Maintenance Software Applications................................................. 22
2.7 User Profiles....................................................................................................... 23
2.8 Regulatory Compliances.................................................................................. 24
3. Getting Started................................................................................................ 26
3.1 Logging In.......................................................................................................... 26
3.2 Starting and Exiting Applications................................................................... 26
3.3 Simultaneous Users.......................................................................................... 26
3.4 User Interface.....................................................................................................27
3.4.1 AviMet Application Icons........................................................................... 27
4. WeatherView.................................................................................................... 28
4.1 Introduction to WeatherView.......................................................................... 28
4.2 WeatherView User Interface............................................................................28
4.2.1 ATC Displays................................................................................................29
4.2.2 Observer Displays...................................................................................... 30
4.2.3 Weather Data Fields....................................................................................31
4.2.4 Wind Options.............................................................................................. 35
4.2.5 Reports and Notifications Pane................................................................ 37
4.2.6 Radar Warnings...........................................................................................37
4.2.7 Sensor Control Feature.............................................................................. 39
4.2.8 Graph Fields................................................................................................40
4.2.9 Lightning Display........................................................................................42
4.2.10 MET Display.................................................................................................42
4.2.11 Runways Display........................................................................................ 44
4.2.12 WeatherView Buttons................................................................................44
4.2.13 Day and Night Display Modes...................................................................45
4.3 Operating WeatherView.................................................................................. 46
4.3.1 Switching between Views......................................................................... 46
4.3.2 Switching between Day/Night Display Mode......................................... 46
4.3.3 Monitoring Weather Data and Status.......................................................47
4.3.4 Acknowledging Weather Data Field Alerts.............................................47
4.3.5 Acknowledging Reports Notifications..................................................... 47
4.3.6 Viewing Reports......................................................................................... 48
4.3.7 Viewing Current System Data and Reported Data.................................48
1
Automated Weather Observing System User Guide M210881EN-V
4.3.8 Adjusting Graph Fields.............................................................................. 48

4.3.9 Configuring Graph Properties...................................................................48
4.3.10 Setting Runway-in-use Manually..............................................................50
4.3.11 Entering Light Intensity Value Manually................................................... 51
4.4 Troubleshooting WeatherView.........................................................................51
5. Runway Configuration.................................................................................. 53
5.1 Introduction to Runway Configuration...........................................................53
5.2 Selecting Predefined Runway Configurations...............................................53
5.3 Defining a Non-standard Runway Configuration..........................................54
5.4 Defining Runway Availability...........................................................................54
6. Lightning Display............................................................................................56
6.1 Introduction to Lightning Display................................................................... 56
6.2 Lightning Display User Interface.....................................................................56
6.2.1 Sound Alarm................................................................................................57
6.2.2 Lightning View............................................................................................ 58
6.2.3 Electric Field View...................................................................................... 59
6.2.4 Active Alarms View....................................................................................60
6.3 Defining Settings.............................................................................................. 60
6.3.1 Configuring Lightning Alarms.................................................................. 60
6.3.2 Editing Lightning Alarms...........................................................................62
6.3.3 Defining Activity Level Settings................................................................63
6.3.4 Configuring Connection Settings............................................................. 63
6.4 System Configuration.......................................................................................64
7. METAR/SPECI...................................................................................................65
7.1 Introduction to METAR/SPECI.........................................................................65
7.2 METAR/SPECI User Interface.......................................................................... 66
7.2.1 Application Header.....................................................................................67
7.2.2 Report Template Tabs................................................................................ 68
7.2.3 Coded Data Fields in Report Tabs............................................................ 68
7.2.4 Data Input Windows.................................................................................. 69
7.2.5 Data Source Selection Lists in Report Tabs.............................................. 71
7.2.6 Final Coded Report Field............................................................................ 71
7.2.7 Validator Field (Optional).......................................................................... 72
7.2.8 Airport-Specific Elements (Optional)...................................................... 73
7.2.9 Buttons on Report Tabs............................................................................. 73
7.2.10 Notifications Pane (Optional)....................................................................75
7.2.11 METAR/SPECI Setup Tab........................................................................... 75
7.2.12 Audio Notification Settings Page............................................................. 79
7.2.13 Manual Observations Tab.......................................................................... 80
7.3 Operating METAR/SPECI Template................................................................80
7.3.1 METAR Editing and Sending Times..........................................................80
7.3.2 Editing and Sending Normal Reports...................................................... 82
7.3.3 Canceling Current Report..........................................................................84
7.3.4 Editing and Sending Delayed (Retarded) Reports................................ 84
7.3.5 Sending Corrected Reports.......................................................................85
7.3.6 Sending Automatic Reports (Optional)...................................................86
7.3.7 Sending SPECI Reports..............................................................................86
7.3.8 Changing Data Sources..............................................................................87
7.3.9 Changing Audio Notification Settings..................................................... 87
7.3.10 Switching between Day/Night Display Mode......................................... 88
7.3.11 Viewing Sent METAR/SPECI Reports.......................................................88
7.4 Troubleshooting METAR/SPECI Application................................................. 89
2
Table of contents
8. TAF.........................................................................................................................91
8.1 Introduction to TAF............................................................................................91
8.2 TAF User Interface............................................................................................. 91
8.2.1 Application Header.................................................................................... 93
8.2.2 TAF Report Tabs......................................................................................... 93
8.2.3 TAF Notifications Pane.............................................................................. 95
8.2.4 TAF Setup Tab.............................................................................................96
8.3 Operating TAF................................................................................................... 96
8.3.1 Starting and Exiting Report Templates................................................... 96
8.3.2 Sending Normal TAF Reports................................................................... 97
8.3.3 Sending Corrected Reports.......................................................................98
8.3.4 Canceling Current Report..........................................................................99
8.3.5 Canceling Sent TAF Report....................................................................... 99
8.3.6 Viewing Sent Reports................................................................................ 99
8.4 Troubleshooting TAF...................................................................................... 100
9. SIGMET............................................................................................................... 101
9.1 Introduction to SIGMET................................................................................... 101
9.2 SIGMET User Interface..................................................................................... 101
9.2.1 SIGMET Data Fields and Source Selection.............................................102
9.2.2 SIGMET Template Buttons....................................................................... 103
9.3 Operating SIGMET.......................................................................................... 104
9.3.1 Sending SIGMET Reports.........................................................................104
9.3.2 Canceling Current Report........................................................................ 105
9.3.3 Viewing Sent Reports...............................................................................105
9.4 Troubleshooting SIGMET................................................................................105
10. GAMET...............................................................................................................106
10.1 Introduction to GAMET...................................................................................106
10.2 GAMET User Interface.................................................................................... 106
10.2.1 GAMET Window........................................................................................ 107
10.2.2 GAMET Menu Bar......................................................................................108
10.3 Operating GAMET........................................................................................... 109
10.3.1 Sending GAMET Reports......................................................................... 109
10.4 Troubleshooting GAMET................................................................................. 110
11. AIRMET................................................................................................................ 111

11.1 Introduction to AIRMET.................................................................................... 111
11.2 AIRMET User Interface...................................................................................... 111
11.2.1 AIRMET Data Fields and Source Selection..............................................112
11.2.2 AIRMET Template Buttons........................................................................ 113
11.3 Operating AIRMET............................................................................................113
11.3.1 Sending AIRMET Reports..........................................................................113
11.3.2 Canceling AIRMET Report.........................................................................114
11.3.3 Viewing Sent Reports................................................................................114
11.4 Troubleshooting AIRMET................................................................................. 115
12. AD WRNG..........................................................................................................116
12.1 Introduction to AD WRNG Template..............................................................116
12.2 AD WRNG Template User Interface............................................................... 116
12.2.1 Application Header.................................................................................... 117
12.2.2 AD WRNG Data Fields and Source Selection......................................... 117
12.2.3 Final Coded Report Field.......................................................................... 118
12.2.4 AD WRNG Template Buttons....................................................................118
3
12.3 Operating AD WRNG Template...................................................................... 118

12.3.1 Sending Aerodrome Warning Reports.................................................... 119
12.3.2 Canceling AD WRNG Report.................................................................... 119
12.4 Troubleshooting AD WRNG Template.......................................................... 120
13. WS WRNG......................................................................................................... 121

13.1 Introduction to WS WRNG Template............................................................. 121
13.2 WS WRNG User Interface................................................................................ 121
13.2.1 WS WRNG Data Fields and Source Selection........................................122
13.2.2 Final Coded Report Field......................................................................... 123
13.2.3 WS WRNG Template Buttons.................................................................. 123
13.3 Operating WS WRNG Template.....................................................................123
13.3.1 Sending Windshear Warning Reports.................................................... 123
13.3.2 Canceling WS WRNG Report...................................................................124
13.3.3 Viewing Sent Reports............................................................................... 124
13.4 Troubleshooting WS WRNG...........................................................................125
14. AFTN Monitor..................................................................................................126

14.1 Introduction to AFTN Monitor........................................................................126
14.2 AFTN Monitor User Interface......................................................................... 126
14.2.1 AFTN Monitor Window ............................................................................126
14.2.2 AFTN Manager Window........................................................................... 127
14.2.3 AFTN Monitor Menu Bar........................................................................... 127
14.2.4 AFTN Monitor Toolbar.............................................................................. 128
14.2.5 AFTN Monitor Status Bar......................................................................... 129
14.3 Outbound (Sent) Messages........................................................................... 129
14.4 Operating AFTN Monitor................................................................................130
14.4.1 Viewing Outbound (Sent) Messages......................................................130
14.4.2 Changing AFTN Sequence Number....................................................... 130
14.4.3 Using AFTN Addressee Manager............................................................130
14.5 Troubleshooting AFTN Monitor...................................................................... 131
15. AFTN Addressee Manager.........................................................................132

15.1 Introduction to AFTN Addressee Manager...................................................132
15.2 AFTN Addressee Manager User Interface.................................................... 133
15.2.1 AFTN Interfaces Frame............................................................................ 134
15.2.2 AFTN Interface Frame.............................................................................. 134
15.2.3 Addressee Group Frame.......................................................................... 134
15.2.4 Addressee Frame...................................................................................... 135
15.2.5 AFTN Addressee Manager Buttons.........................................................135
15.3 Operating AFTN Addressee Manager........................................................... 135
15.3.1 Starting and Exiting AFTN Addressee Manager................................... 135
15.3.2 Adding New Addressee Groups.............................................................. 135
15.3.3 Adding New Addressees..........................................................................136
15.3.4 Selecting Message Types Sent to the Addressees................................136
15.3.5 Editing Addressee Groups........................................................................137
15.4 Troubleshooting AFTN Addressee Manager................................................ 137
16. AMHS Monitor.................................................................................................138

16.1 Introduction to AMHS Monitor.......................................................................138
16.2 AMHS Monitor User Interface.........................................................................138
16.3 Troubleshooting AMHS Monitor....................................................................140
17. Diagnostics....................................................................................................... 141

17.1 Introduction to Diagnostics.............................................................................141
4
Table of contents
17.2 Diagnostics User Interface...............................................................................141

17.2.1 Events Panel.............................................................................................. 142
17.3 Operating Diagnostics Application...............................................................144
17.3.1 Starting and Exiting Diagnostics............................................................ 144
17.3.2 Monitoring and Acknowledging Events.................................................144
17.3.3 Viewing Stored Events............................................................................. 145
17.4 Troubleshooting Diagnostics......................................................................... 146
18. ASCII Log View...............................................................................................147

18.1 Introduction to ASCII Log View..................................................................... 147
18.2 ASCII Log View User Interface....................................................................... 147
18.2.1 ASCII Log View Main Window................................................................. 148
18.2.2 Weather Parameter Files......................................................................... 149
18.2.3 Reports Files..............................................................................................150
18.2.4 Events Files................................................................................................150
18.2.5 ASCII Log View Toolbar Buttons.............................................................. 151
18.3 Operating ASCII Log View.............................................................................. 152
18.3.1 Opening and viewing history files...........................................................152
18.3.2 Viewing Several Files at the Same Time.................................................154
18.3.3 Refreshing Data Automatically................................................................155
18.3.4 Refreshing Data Manually........................................................................ 155
18.3.5 Hiding Rows............................................................................................... 155
18.3.6 Showing Hidden Rows..............................................................................156
18.3.7 Exporting history files.............................................................................. 156
18.3.8 Backing up History Files...........................................................................156
18.4 Troubleshooting ASCII Log View................................................................... 157
19. Actuals............................................................................................................... 158

19.1 Introduction to Actuals View..........................................................................158
19.2 Actuals View User Interface........................................................................... 158
19.3 Activating Backup Sensor.............................................................................. 159
19.4 Entering Manual Data......................................................................................159
20. Sensor Selector............................................................................................... 161

20.1 Introduction to Sensor Selector......................................................................161
20.2 Sensor Selector User Interface........................................................................161
20.3 Operating Sensor Selector............................................................................. 162
20.3.1 Disabling Data Use....................................................................................162
20.3.2 Enabling Data Use.....................................................................................162
21. Data Source Manager.................................................................................. 163

21.1 Introduction to Data Source Manager...........................................................163
21.2 Data Source Manager User Interface............................................................ 163
21.2.1 Data Source Manager Window................................................................163
21.2.2 Active Data Source................................................................................... 164
21.2.3 Normal Situations..................................................................................... 164
21.2.4 Exceptional Situations.............................................................................. 165
21.2.5 Data Source Manager Window Columns............................................... 165
21.2.6 Data Source Manager Buttons.................................................................167
21.3 PV Group Manager Window...........................................................................168
21.3.1 Sensor Weight Value................................................................................ 169
21.3.2 Validity Limit..............................................................................................170
5
21.4 Operating the Data Source Manager Application....................................... 170

21.4.1 Starting and Exiting Application.............................................................170
21.4.2 Starting and Exiting Data Source Manager........................................... 170
21.4.3 Changing the Active Data Source............................................................ 171
21.4.4 Using Manual Values.................................................................................. 171
21.4.5 Disabling and Enabling Data Sources for Pressure Values...................172
21.4.6 Managing Prevailing Visibility Groups.................................................... 173
21.5 Troubleshooting Data Source Manager........................................................ 175
22. History Monitor...............................................................................................176

22.1 Introduction to History Monitor..................................................................... 176
22.2 History Monitor User Interface....................................................................... 176
22.2.1 Trend View Window.................................................................................. 177
22.2.2 Table View Window...................................................................................178
22.2.3 Query View Window................................................................................. 178
22.2.4 New Window............................................................................................. 178
22.2.5 Open Window............................................................................................179
22.2.6 Data Item Selection Window................................................................... 179
22.2.7 Options Window....................................................................................... 180
22.2.8 Graph Properties Window........................................................................182
22.2.9 Extremes Window.....................................................................................183
22.2.10 History Monitor Menu Bar........................................................................ 184
22.2.11 History Monitor Toolbar............................................................................185
22.3 Operating History Monitor............................................................................. 186
22.3.1 Starting and Exiting Application.............................................................186
22.3.2 Creating New View................................................................................... 186
22.3.3 Opening Saved Views...............................................................................188
22.3.4 Changing Displayed Data Items.............................................................. 189
22.3.5 Displaying Data from Previous Day........................................................ 189
22.3.6 Refreshing Data in Views......................................................................... 190
22.3.7 Changing Display Period......................................................................... 190
22.3.8 Changing Display Resolution....................................................................191
22.3.9 Editing Graphs in Trend Views.................................................................192
22.3.10 Moving and Zooming in Trend Views..................................................... 194
22.3.11 Moving and Sorting in Table Views.........................................................194
22.3.12 Printing Views........................................................................................... 194
22.3.13 Viewing Several Windows at the Same Time........................................ 195
22.4 Troubleshooting History Monitor.................................................................. 196
23. Dial-Up Manager............................................................................................ 197

23.1 Introduction to Dial-up Manager................................................................... 197
23.2 Dial-up Manager User Interface..................................................................... 197
23.2.1 Destinations Frame...................................................................................198
23.2.2 Messages Frame........................................................................................198
23.3 Operating Dial-up Manager........................................................................... 199
23.3.1 Turning on Dial-up Connection............................................................... 199
23.3.2 Turning off Dial-up Connection...............................................................199
23.3.3 Adding New Destinations.......................................................................200
23.3.4 Editing Destination Names.....................................................................200
23.3.5 Editing Phone Numbers..........................................................................200
23.3.6 Deleting Destination Name and Phone Number................................. 200
23.3.7 Deleting Phone Numbers.........................................................................201
23.3.8 Viewing Modem Connections..................................................................201
23.4 Troubleshooting Dial-up Manager................................................................ 201
6
Table of contents
Appendix A: Software End User License Agreement.......................... 202

A.1 Vaisala AviMetâ Software End User License Agreement......................... 202
Glossary........................................................................................................... 207
Index.................................................................................................................. 212
Technical support........................................................................................... 217
Warranty........................................................................................................... 217
Recycling.......................................................................................................... 217
7
List of figures
Figure 1 Typical Vaisala AviMet AWOS System......................................................... 17
Figure 2 WeatherView: Example Display for ATC.................................................... 29
Figure 3 WeatherView: Example Display for Observers........................................ 30
Figure 4 WeatherView: Data Field Example............................................................... 31
Figure 5 WeatherView: Example Dimmed Data....................................................... 33
Figure 6 WeatherView: Example Visual Alert............................................................33
Figure 7 WeatherView: Tendency Indicators.............................................................34
Figure 8 Head/Tail and Crosswind in Numerical Format........................................35
Figure 9 Head/Tail and Crosswind in Graphical Format in the RWY
Ends and RWY Mid Point................................................................................35
Figure 10 Head/Tail and Crosswind in Graphical Format for the RWY
Touchdown Zones............................................................................................ 35
Figure 11 Windrose with Runway Graphic in North View........................................36
Figure 12 Windrose with Runway Graphic in Tower View (Line
Indicating North Direction)............................................................................36
Figure 13 Wind Rose with Wind Values Above...........................................................37
Figure 14 Notifications Pane with Acknowledge Button..........................................37
Figure 15 Radar Warnings in WeatherView................................................................. 38
Figure 16 Sensor Control Window..................................................................................39
Figure 17 Graph Field Example.......................................................................................40
Figure 18 Graph: Trace View............................................................................................ 40
Figure 19 Graph Configuration Window........................................................................ 41
Figure 20 Lightning Display..............................................................................................42
Figure 21 MET Display........................................................................................................43
Figure 22 Runways Display Example.............................................................................44
Figure 23 WeatherView: Night Display Mode............................................................. 46
Figure 24 Runway Configuration View.......................................................................... 53
Figure 25 Lightning Display..............................................................................................56
Figure 26 Settings Page.....................................................................................................57
Figure 27 Lightning View.................................................................................................. 58
Figure 28 Electric Field View............................................................................................59
Figure 29 Active Alarms View..........................................................................................60
Figure 30 Reports Application, METAR Template...................................................... 66
Figure 31 Reports Application, MET REPORT Template...........................................67
Figure 32 Visibility Input Window.................................................................................. 69
Figure 33 Cloud Input Window........................................................................................70
Figure 34 Present Weather Input Window...................................................................70
Figure 35 Recent Weather Input Window..................................................................... 71
Figure 36 Final Coded Report Field with Mode, State, and Time Left
Indicators............................................................................................................ 72
Figure 37 Validator Field....................................................................................................73
Figure 38 Notifications Pane with Acknowledge Button..........................................75
Figure 39 Setup Tab, Typical Report Mode Settings Page....................................... 76
Figure 40 Setup Tab, Default Input Settings Page......................................................77
Figure 41 Setup Tab, Limit Criteria Settings Page......................................................78
Figure 42 Setup Tab, Audio Notifications Page.......................................................... 79
Figure 43 Example of METAR Editing and Sending Times........................................81
Figure 44 Normal Report Editing Procedure............................................................... 84
Figure 45 TAF FC Tab......................................................................................................... 92
Figure 46 Final Coded Report Field with Mode, State, and Time Left
Indicators............................................................................................................ 93
Figure 47 Notifications Pane with Acknowledge Button......................................... 95
8
List of figures
Figure 48 TAF Setup Tab................................................................................................... 96

Figure 49 SIGMET User Interface....................................................................................101
Figure 50 Final Coded Report Field with Mode and State Fields......................... 103
Figure 51 GAMET Window.............................................................................................. 107
Figure 52 AIRMET User Interface.....................................................................................111
Figure 53 AD WRNG Template........................................................................................ 117
Figure 54 WS WRNG Template Window..................................................................... 122
Figure 55 AFTN Monitor Window..................................................................................126
Figure 56 AFTN Manager Window................................................................................ 127
Figure 57 AFTN Addressee Manager Window...........................................................133
Figure 58 Example AMHS Monitor Window............................................................... 138
Figure 59 Diagnostics Application (Observer User Profile)................................... 142
Figure 60 ASCII Log View Main Window..................................................................... 148
Figure 61 ASCII Log View: Weather Parameter File Examples (Tile Mode)...... 149
Figure 62 ASCII Log View: Example Events Files (Tab Mode)................................ 151
Figure 63 ASCII Log View: Opening history files.......................................................153
Figure 64 Actuals View Example Page.........................................................................158
Figure 65 Sensor Selector User Interface.....................................................................161
Figure 66 Data Source Manager Window, Pressure Tab..........................................163
Figure 67 Data Source Manager, Prevailing Visibility Tab.......................................164
Figure 68 Data Source Manager Window, Default Situation..................................165
Figure 69 Data Source Manager Window, Active Sensor Changed..................... 165
Figure 70 PV Group Manager Window........................................................................ 168
Figure 71 Activate Data Source Window, Warning................................................... 171
Figure 72 Blank History Monitor Main Window......................................................... 176
Figure 73 History Monitor with Opened Views.......................................................... 177
Figure 74 New Window.................................................................................................... 178
Figure 75 Open View Window........................................................................................179
Figure 76 Data Item Selection Window....................................................................... 179
Figure 77 Options Window............................................................................................. 180
Figure 78 Graph Properties Window............................................................................ 182
Figure 79 Extremes Window...........................................................................................183
Figure 80 Printing Trend View........................................................................................ 195
Figure 81 Dial-up Manager Window............................................................................. 197
9
List of tables
Table 1 Document versions (English)........................................................................... 13
Table 2 AviMetâ manuals................................................................................................ 13
Table 3 User Groups and Corresponding User Profiles...........................................23
Table 4 Typical Software Applications by User Profile............................................23
Table 5 International Recommendations Applied to AviMet Software.............. 25
Table 6 Vaisala AviMet Application Buttons.............................................................. 27
Table 7 WeatherView: Data Field Status Colors........................................................ 31
Table 8 Alarm Types......................................................................................................... 34
Table 9 Tendency Indicators...........................................................................................34
Table 10 Sensor Control Window....................................................................................39
Table 11 Graph Configuration Window Tabs............................................................... 42
Table 12 WeatherView Example Buttons..................................................................... 44
Table 13 Troubleshooting WeatherView....................................................................... 52
Table 14 Coded Data Field Frame Colors..................................................................... 68
Table 15 Typical Data Source Selection List Options..................................................71
Table 16 Typical State Options.........................................................................................72
Table 17 Buttons on Report Tabs.................................................................................... 73
Table 18 Report Mode Settings Options....................................................................... 76
Table 19 Limit Criteria Settings Page Elements.......................................................... 78
Table 20 Audio Notifications Page Elements...............................................................79
Table 21 Troubleshooting METAR/SPECI......................................................................89
Table 22 Typical State Options........................................................................................ 93
Table 23 Buttons on TAF Report Tabs........................................................................... 94
Table 24 Troubleshooting TAF....................................................................................... 100
Table 25 SIGMET Report Type Buttons........................................................................ 102
Table 26 SIGMET Data Fields.......................................................................................... 102
Table 27 SIGMET Data Source Selection Options..................................................... 103
Table 28 Typical State Options.......................................................................................103
Table 29 Typical SIGMET Template Buttons............................................................... 103
Table 30 Troubleshooting SIGMET................................................................................ 105
Table 31 GAMET Window Elements............................................................................. 107
Table 32 GAMET: File Menu.............................................................................................108
Table 33 GAMET: Edit Menu............................................................................................ 108
Table 34 GAMET: Help Menu...........................................................................................108
Table 35 Troubleshooting GAMET..................................................................................110
Table 36 AIRMET Data Fields........................................................................................... 112
Table 37 AIRMET Data Source Selection Options...................................................... 112
Table 38 State Options.......................................................................................................113
Table 39 AIRMET Template Buttons...............................................................................113
Table 40 Troubleshooting AIRMET................................................................................. 115
Table 41 AD WRNG Data Fields...................................................................................... 117
Table 42 AD WRNG Data Source Selection Options................................................. 118
Table 43 AD WRNG Template Buttons..........................................................................118
Table 44 Troubleshooting AD WRNG Template........................................................ 120
Table 45 WS WRNG Data Fields.....................................................................................122
Table 46 WS WRNG Data Source Selection Options................................................123
Table 47 WS WRNG Template Buttons........................................................................ 123
Table 48 Troubleshooting WS WRNG Template........................................................ 125
Table 49 AFTN Manager Data Fields.............................................................................127
Table 50 AFTN Monitor: File Menu.................................................................................127
Table 51 AFTN Monitor: Edit Menu................................................................................128
Table 52 AFTN Monitor: View Menu..............................................................................128
10
List of tables
Table 53 AFTN Monitor: Window Menu....................................................................... 128

Table 54 AFTN Monitor: Help Menu...............................................................................128
Table 55 AFTN Monitor Toolbar......................................................................................128
Table 56 Troubleshooting AFTN Monitor......................................................................131
Table 57 AFTN Addressee Manager Window: AFTN Interfaces Frame.............. 134
Table 58 AFTN Addressee Manager Window: AFTN Interface Frame................ 134
Table 59 AFTN Addressee Manager Window: Addressee Group Frame............ 134
Table 60 AFTN Addressee Manager Window: Addressee Frame......................... 135
Table 61 AFTN Addressee Manager Window: Buttons............................................135
Table 62 Troubleshooting AFTN Addressee Manager..............................................137
Table 63 AMHS Monitor Connection Status................................................................139
Table 64 Sent, Received, and Delivery Report Tab Details..................................... 139
Table 65 Troubleshooting AMHS Monitor................................................................... 140
Table 66 Events Panel Tabs /Event Types................................................................... 143
Table 67 Events Panel Statuses and Colors................................................................ 143
Table 68 Events Panel Columns and Buttons............................................................. 143
Table 69 An Example of the Event Chain.................................................................... 146
Table 70 Troubleshooting Diagnostics Application..................................................146
Table 71 ASCII Log View: Status Codes.......................................................................150
Table 72 ASCII Log View toolbar buttons.....................................................................151
Table 73 Sample ASCII Log View file names...............................................................153
Table 74 Troubleshooting ASCII Log View.................................................................. 157
Table 75 Sensor Selector Columns................................................................................. 161
Table 76 Data Source Manager Window Columns and Colors.............................. 165
Table 77 Data Source Manager, Value Columns for Pressure.................................166
Table 78 Data Source Manager, Value Columns for Prevailing Visibility............. 167
Table 79 Data Source Manager Window Buttons......................................................167
Table 80 Elements on Prevailing Visibility Groups Pane......................................... 168
Table 81 Elements on Prevailing Visibility Group Pane........................................... 169
Table 82 Elements on Prevailing Visibility Sensor Pane..........................................169
Table 83 Buttons on PV Group Manager Window.................................................... 169
Table 84 Troubleshooting Data Source Manager.......................................................175
Table 85 Data Item Selection Window Elements...................................................... 180
Table 86 Options Window Elements..............................................................................181
Table 87 Extremes Window Elements..........................................................................183
Table 88 History Monitor: File Menu ............................................................................ 184
Table 89 History Monitor: Edit Menu.............................................................................184
Table 90 History Monitor: View Menu...........................................................................184
Table 91 History Monitor: Tools Menu...........................................................................185
Table 92 History Monitor: Window Menu.....................................................................185
Table 93 History Monitor: Help Menu ...........................................................................185
Table 94 History Monitor Toolbar Buttons...................................................................185
Table 95 Troubleshooting History Monitor..................................................................196
Table 96 Dial-up Manager Window Elements: Destinations Frame.....................198
Table 97 Dial-up Manager Window Elements: Messages Frame.......................... 198
Table 98 Troubleshooting Dial-up Manager................................................................201
11
12
Chapter 1 – About This Document
1. About This Document

1.1 Version information
This manual contains the information necessary to use the end-user software applications of
the Vaisala AviMetâ Automated Weather Observing System (AWOS). The manual is mainly
intended for air traffic controllers, observers, and forecasters at the airport.
Table 1 Document versions (English)
Document Code Date Description
M210881EN-V April 2020 This manual. Applicable for Vaisala AviMetâ Automated
Weather Observing System from software version 8.6.7
onwards.
M210881EN-U April 2019 Applicable for Vaisala AviMetâ Automated Weather

Observing System from software version 8.6 onwards.
M210881EN-T August 2018 Applicable for Vaisala AviMetâ Automated Weather

Observing System from software version 8.2 onwards.
1.2 Related manuals
Table 2 AviMetâ manuals
Document Code Name
M210881EN Vaisala AviMetâ Automated Weather Observing System User Guide
M210882EN Vaisala AviMetâ Automated Weather Observing System Maintenance Manual
M210885EN Vaisala AviMetâ Low-Level Windshear Alert System User Guide
M210886EN Vaisala AviMetâ Low-Level Windshear Alert System Maintenance Manual
M210887EN Vaisala AviMetâ Runway Visual Range System User Guide
M210888EN Vaisala AviMetâ Runway Visual Range System Maintenance Manual
M210842EN Vaisala AviMetâ Synoptic Observations Software SYNOP User Guide
M210851EN Vaisala AviMetâ Runway Friction Application (SNOWTAM) User Guide
M210848EN Vaisala AviMetâ Climatological Observations Software (CLIMAT) User Guide
M210849EN Vaisala AviMetâ Database Reporting Tool User Guide
M211032EN Vaisala AviMetâ Vertical Windshear Detection System User Guide
13
For information on the system architecture and the system maintenance applications, see
Vaisala AviMetâ Automated Weather Observing System Maintenance Manual. For
instructions on installing, using, and maintaining the sensors and other field devices, see the
appropriate field device manuals.
For information concerning the use of data collectors, sensors, or other installed
hardware, see the appropriate device manuals.
1.3 Documentation conventions
WARNING! Warning alerts you to a serious hazard. If you do not read and follow
instructions carefully at this point, there is a risk of injury or even death.
CAUTION! Caution warns you of a potential hazard. If you do not read and follow
instructions carefully at this point, the product could be damaged or important data
could be lost.
Note highlights important information on using the product.
Tip gives information for using the product more efficiently.
Lists tools needed to perform the task.
Indicates that you need to take some notes during the task.
14
Chapter 1 – About This Document
1.4 Trademarks
Vaisalaâ and AviMetâ are registered trademarks of Vaisala Oyj. IRIS™ and Total Lightning
Processor™ are trademarks of Vaisala Oyj. TSS928™ is a trademark of Vaisala Inc.
Microsoftâ, Windowsâ, and Internet Explorerâ are either registered trademarks or
trademarks of Microsoft Corporation in the United States and/or other countries.
All other product or company names that may be mentioned in this publication are trade
names, trademarks, or registered trademarks of their respective owners.
15
2. Product Overview
2.1 System Introduction
Vaisala AviMetâ Automated Weather Observing System (AWOS) is designed for the needs
of air traffic controllers, observers, forecasters, and other airport personnel.
The system measures, processes, displays, stores, and distributes meteorological
information. It consists of sensors located along the runway, one or two central data unit
computers (CDUs), and one or several workstations.
The sensors are located along the runways at specific measurement sites and communicate
with the central data units (CDUs), which distribute the data to the workstations. The system
can be single-CDU or duplicated, that is, it can include one or two CDUs. The CDU validates
the measurement data, calculates the values based on the data, and distributes the weather
data and alarms to user workstations.
In user workstations, users can view weather data, trends, and alerts with the WeatherView
application. Historical values can be viewed in the ASCII Log View application. The
Diagnostics application is for monitoring and handling system error situations.
Weather reports can be edited and sent using the METAR/SPECI template and other
weather report applications (for example, TAF). The basic report templates are typically part
of the Reports application.
The system supports dissemination of data reported in METAR/SPECI and TAF using the
IWXXM XML schema. IWXXM (ICAO meteorological information exchange model) is
designed to be globally interoperable information exchange model to exchange
meteorological data in digital form in addition to current code forms. The availability of
aeronautical meteorological information in a globally interoperable digital format is seen as
a key enabler for global air traffic management within a system wide information
management (SWIM) environment. For more information, see Manual on the Digital
Exchange of Aeronautical Meteorological Information and Manual on System Wide
Information Management (SWIM) Concept.
16
Chapter 2 – Product Overview
Figure 1 Typical Vaisala AviMet AWOS System
2.2 AviMet Product Platform

Vaisala AviMetâ Automated Weather Observing System (AWOS) is part of the AviMet
technology platform. Other major systems based on the platform are:
• Vaisala AviMetâ Low-Level Windshear Alert System (LLWAS)
• Vaisala AviMetâ Runway Visual Range system (RVR)
The LLWAS and RVR systems can be easily upgraded to a full-scale Vaisala AviMetâ AWOS
system. They can also be fully integrated into an existing AviMetâ AWOS system.
The systems can be one of the following types:
• A single-CDU system with workstations
• A single-CDU system without workstations
• A duplicated system with two CDUs with workstations
• A duplicated system with two CDUs without workstations
In a duplicated system both central data units process the same data. If one of the CDUs
fails, the other CDU continues working transparently to users and without any disruption to
system performance. A CDU may be used as an end-user workstation, too.
For more information on the CDU types, see Vaisala AviMetâ Automated Weather
Observing System Maintenance Manual.
17
2.3 System Configuration
Vaisala AviMet systems are always configured individually for each airport to meet the local
requirements. During system delivery, Vaisala personnel will define the system parameters
and the layout of some application windows. This is typical especially with end-user
applications. For instance, the content of the weather data screens in the WeatherView
application can be configured according to user preferences.
CAUTION! System configuration is only allowed by authorized Vaisala personnel.
This manual provides a description of the end-user applications and functions of the system.
Your system might not include all the applications that are available in AviMet systems. Thus,
your system might differ slightly from what is presented in this manual.
2.4 Use of Anti-Virus Software

WARNING! To ensure proper functioning of the AviMet software, always consult
Vaisala about using any anti-virus software. When AviMet system is in operational use,
software anti-virus functionalities, especially automatic updates and blocking, cannot
be used.
AviMet software has been designed to be run on closed and secured networks.
Although typically the AviMet software runs on computers that have anti-virus software
running, it is known that anti-virus software can have functions that significantly consume
computer resources. This may affect the AviMet software performance and some of the anti-
virus software functionalities cannot be used when AviMet system is in operational use. Also
functions that block vital AviMet software functionalities cannot be used.
Especially if anti-virus software updates itself after AviMet system installation, no guarantee
of the AviMet software functionality and performance can be given.
2.5 End-user Software Applications

The AviMet software consists of two sets of applications: end-user applications and system
maintenance applications, which are the tools needed for system troubleshooting.
The following sections include brief descriptions of what each end-user application is used
for.
The AviMet AWOS software focuses on the following aspects of airport weather observation:
• Displaying current weather data (WeatherView)
• Sending weather reports (for example, METAR/SPECI)
18
• Viewing past weather data (ASCII Log View, History Monitor)

• Ensuring the validity of weather data by monitoring the operation of the system
(Diagnostics)
In addition, there are applications for managing the report and weather data contents,
source, and sending.
For more information, see the following brief introductions and the separate chapters later
in this manual.
2.5.1 Viewing Current Data

WeatherView
The WeatherView application is used for viewing current meteorological data in numerical
and graphical format. It can also display the status of the data. Optionally, the WeatherView
application can include the audiovisual alarm function.
If Vaisala IRIS™ Focus weather radar software is integrated to the Vaisala AviMet AWOS
system, the radar warnings can be displayed in WeatherView.
If the AviMet system contains a local lightning warning sensor, such as Vaisala Thunderstorm
Local Lightning Sensor TSS928™, or receives data from a lightning detection network, for
example, Vaisala Total Lightning Processor (TLP), the lightning warning data can be
displayed in the Lightning display.
Vertical Windshear Detection System (Optional)

Vertical Windshear Detection System is for viewing Wind profiler data and vertical
windshear warnings.
2.5.2 Editing and Sending Weather Reports

METAR/SPECI (MET REPORT/SPECIAL)
The METAR/SPECI template is used for editing and sending METAR/ SPECI reports and,
depending on the system configuration, also local routine reports (MET REPORT) and local
special reports.
Optionally, automated reports can be sent with no user action.
Additionally, the application can also be used for changing the SPECI triggering limits and
the source for the data in the reports.
Typically, the METAR/SPECI template is part of the Reports application, together with other
weather reports in your system.
TAF (Optional)
The TAF template is used for editing and sending terminal area forecasts. Typically, the TAF
template is part of the Reports application.
19
SIGMET (Optional)
The SIGMET template is used for editing and sending SIGMET reports. Typically, the SIGMET
template is part of the Reports application.
GAMET (Optional)
The GAMET template is used for editing and sending GAMET reports.
AIRMET (Optional)
The AIRMET template is used for editing and sending AIRMET reports.
AD WRNG (Optional)
The AD WRNG template is used for creating and sending Aerodrome Warning reports.
Typically, the AD WRNG template is part of the Reports application.
WS WRNG (Optional)
The WS WRNG template is used for creating and sending Windshear Warning reports.
SYNOP (Optional)
The SYNOP application is used for editing and sending SYNOP reports. For more
information on SYNOP, see Vaisala AviMetâ Synoptic Observations Software SYNOP User
Guide.
SNOWTAM (Optional)
The SNOWTAM application is used for editing and sending SNOWTAM reports. For more
information on SNOWTAM, see Vaisala AviMetâ Runway Friction Application (SNOWTAM)
User Guide.
CLIMAT (Optional)
The CLIMAT application is used for editing and sending CLIMAT reports. For more
information on CLIMAT, see Vaisala AviMetâ Climatological Observations Software (CLIMAT)
User Guide.
2.5.3 Entering Data Manually

In addition to automatic values from the sensors and the system, manual observations can
be entered and displayed. Depending on your system configuration, you can enter manual
data with the Manual Observations feature that is typically part of the Reports application,
or the Actuals view that is typically part of WeatherView.
2.5.4 Viewing Past Data

ASCII Log View
The ASCII Log View application is used for viewing history files that contain stored
meteorological data, weather reports, and events.
20
History Monitor (Optional)

History Monitor is an application for viewing archived weather data from the database in
table or graph format.
Database Reporting Tool (Optional)

The Database Reporting Tool application is used for creating reports and graphs from
weather data that is stored in the optional database. For more information on Database
Reporting Tool, see Vaisala AviMetâ Database Reporting Tool User Guide.
AFTN Monitor
AFTN Monitor is an application for viewing all types of reports sent from the airport to the
AFTN line.
AMHS Monitor
AMHS Monitor is an application for viewing reports sent/received from the airport.
2.5.5 Managing Data Source and Settings

Reports
The weather report templates in your system are typically part of the Reports application.
Reports is mainly a tool for editing and sending weather reports, but it is also used for
defining the data source for the reports and SPECI/SPECIAL triggering limits.
Sensor Control (Optional)

The Sensor Control feature can be used for selecting which of the available sensors is used
as the source for the automatic data. The feature can be accessed, for example, from the
WeatherView application.
Data Source Manager (Optional)

In some systems, the Data Source Manager application can be used for managing the data
source.
Actuals View (Optional)

In some systems, the Actuals view can be used for activating a preconfigured backup sensor
or for entering the data manually. The Actuals view is typically part of the WeatherView
application.
Sensor Selector (Optional)

With Sensor Selector you can disable a faulty sensor or a sensor that is being maintained.
Data from the disabled sensor will not be published for use in other system processes.
Runways Display for Runway-in-Use

When the automatic runway-in-use information from an external system is temporarily not
available, the ATC supervisor can set the runway-in-use information and runway landing
direction with the Runways display in WeatherView.
21
Runway Configuration (Optional)

In the AviMet systems in which the runway-in-use information is not provided by an external
system, the information can be set and selected in the Runway Configuration view.
AFTN Addressee Manager

AFTN Addressee Manager is an application for configuring the addressee part of the AFTN
address and which weather reports are sent to which addressee.
Dial-up Manager (Optional)

The Dial-up Manager application is used for turning on and off the dial-up connection for
sending weather reports.
2.5.6 Monitoring System Operation

Diagnostics
The Diagnostics application is typically a tool for maintenance personnel for monitoring the
overall AviMet system operation. Depending on system configuration, also observers can use
it for viewing relevant system events.
2.6 System Maintenance Software

Applications
The system maintenance software applications are used for performing daily system
monitoring tasks and for troubleshooting tasks that are needed less frequently. These
applications are tools for maintenance and administrator level users.
For detailed information, see Vaisala AviMetâ Automated Weather Observing System
Maintenance Manual.
Diagnostics
The Diagnostics application is the main tool for system maintenance personnel. The
Diagnostics application is used for monitoring the status of the CDU(s), internal components
(ROA processes/objects), workstation applications, sensors, and other devices in the
system, and for viewing system events.
Depending on system configuration, other AviMet maintenance applications, such as ASCII
Log View and IO Terminal, can be accessed directly through Diagnostics.
IO Terminal
The IO Terminal application is used for connecting to sensors and field devices through a
communication port. When there is an open terminal connection to the device, you can
monitor the messages it sends and send commands to check and modify the device status.
22
Sensor Selector (Optional)

Playback Feature (Optional)

Playback is a feature that allows the user to replay data from a specific period of time in the
past as it was displayed on the screen. The feature can be integrated with an AviMet
application, typically with a WeatherView screen.
2.7 User Profiles
The Vaisala AviMet systems typically include workstations for using the AviMet software. The
number of different workstations in the system depends on the configuration of the system.
Vaisala configures the user profiles for the system. The applications available for each user
profile depends on the configuration of the system. To access the applications, the user must
log in to the workstation with the appropriate user profile.
Table 3 User Groups and Corresponding User Profiles
User Group User Profile
Air traffic controllers ATC
Observers Observer
Forecasters Forecaster
System maintenance personnel Maintenance
This manual covers the applications for the ATC, Observer, and Forecaster user profiles.
There are separate manuals for some applications. Refer to the list of related manuals. For
information on the applications for the Maintenance user profile, see Vaisala AviMetâ
Automated Weather Observing System Maintenance Manual.
For an example of typical software functionalities and applications for each user profile, see
the following table.
Table 4 Typical Software Applications by User Profile
Application / Functionality Observer Forecaster ATC Maintenance
WeatherView x x x 1) x
Diagnostics x x x
ASCII Log View x x x
Reports: METAR/SPECI, MET REPORT/SPECIAL x x 2)
Reports: TAF, SIGMET, AD WRNG (Optional) x
WS WRNG (Optional) x
23
Application / Functionality Observer Forecaster ATC Maintenance
GAMET (Optional) x
AIRMET (Optional) x
Manual Observations (Optional) x
Data Source Manager (Optional) x x
Sensor Control x
IO Terminal x
AFTN Monitor x x
AMHS Monitor x x
AFTN Addressee Manager x x
Runways display (runway-in-use) x
Runway Configuration display (Optional) x
Lightning display (Optional)
History Monitor (Optional) x
SYNOP (Optional) 3) x
CLIMAT (Optional) 4) x
SNOWTAM (Optional) 5) x 6)
Dial-up Manager (Optional) x 7) x 7)
Database Reporting Tool (Optional) 8) x
Sensor Selector (Optional) x x
Playback (Optional) x
1) The WeatherView application for the ATC user profile typically differs slightly from the WeatherView application for the
Observer user profile.
2) The METAR/SPECI application for the Forecaster user profile only allows editing and sending a Trend forecast and the
Forecaster remark.
3) See Vaisala AviMetâ Synoptic Observations Software SYNOP User Guide.
4) See Vaisala AviMetâ Climatological Observations Software (CLIMAT) User Guide.
5) See Vaisala AviMetâ Runway Friction Application (SNOWTAM) User Guide.
6) SNOWTAM is typically used in a separate Runway Friction workstation.
7) The Diagnostics user interface for the Maintenance user profile has more features than the one for Observer user profile.
8) See Vaisala AviMetâ Database Reporting Tool User Guide.
2.8 Regulatory Compliances
The AviMet systems are designed according to the recommendations of international air
traffic authorities as presented in the following sources.
24
Table 5 International Recommendations Applied to AviMet Software
Document Name Year
Meteorological Service for International Air Navigation. Annex 3. ICAO. 20th edition. 2018
Aeronautical Telecommunications. Annex 10. Vol. II (Communication procedures). ICAO. 2016

7th edition.
Manual of Runway Visual Range Observing and Reporting Practices (Doc 9328). ICAO. 2005
3rd edition.
Manual of Aeronautical Meteorological Practice (Doc 8896). ICAO. 12th edition. 2019
Manual on Codes. International Codes Volume I.1 (Annex II to WMO Technical 2018
Regulations). WMO No. 306. 2011 edition, updated in 2018.
Manual on Automatic Meteorological Observing Systems at Aerodromes (Doc 9837). 2011

ICAO. 2nd edition.
Manual on the Digital Exchange of Aeronautical Meteorological Information (Doc 10003). 2014
ICAO. 1st edition 2014.
Manual on System Wide Information Management (SWIM) Concept (Doc 10039). ICAO. –
Interim advanced edition (unedited).
25
3. Getting Started
3.1 Logging In
Log in to your computer with your Windows user name and password. The AviMet system
starts and applies your profile automatically, giving you all the AviMet application rights that
you need in your daily tasks.
If you receive error messages when trying to log in, contact system maintenance personnel.
3.2 Starting and Exiting Applications

Depending on your user profile and the system configuration, some applications, for
example, WeatherView, start automatically when you log into an AviMet workstation. These
applications also need to be open at all times.
If the AviMet applications do not start, the software license may not be available or
activated. Contact your system maintenance personnel.
CAUTION! To view meteorological data and alarms, keep the WeatherView application
and the Notifications pane open at all times.
To start the applications that do not start automatically, click the corresponding icon on the
desktop, or for example, in the WeatherView application. Depending on system
configuration other options may be available.
3.3 Simultaneous Users
In systems where several users can access a report template simultaneously, only one user
can edit the template at a time. The name of the user that is editing is displayed in the
application header.
If another user is already using the editing mode and you click the Release button in the
application header, you will get a message indicating that the user has opened the
application for editing. There is an option of taking the editing access by force, but typically
you should not do that.
26
Chapter 3 – Getting Started
3.4 User Interface
3.4.1 AviMet Application Icons
The icons available in your system and workstation may differ from the one listed below
because AviMet applications are configured for each user profile and system separately.
If the icons for the applications you need are not visible when you log in to the workstation,
you are perhaps trying to log in with a username that does not have the appropriate user
profile.
Some software functionalities are part of other applications and their location depends on
the system configuration. For example, the Sensor Control functionality may be part of
WeatherView application, or another application, as configured.
The following table shows the typical icons used for AviMet applications.
Table 6 Vaisala AviMet Application Buttons
Button Description
Opens the WeatherView application.
Opens the Reports application, which contains the basic reports templates included in the
system, for example, METAR/SPECI, MET REPORT/SPECIAL, TAF, SIGMET, GAMET, AIRMET,
AD WRNG, and WS WRNG, depending on your system configuration.
Opens the AFTN application (optional).
Opens the Diagnostics application (optional).
Opens the Dial-up Manager application (optional).
Opens the ASCII Log View application.
Opens the SYNOP application (optional).
Opens the CLIMAT application (optional).
Opens the SNOWTAM application (optional).
Opens the AFTN Monitor application.
More information
‣ Starting and Exiting Applications (page 26)
27
4. WeatherView
4.1 Introduction to WeatherView
The WeatherView application shows real-time instant and average values for weather
parameters in numerical and graphical format. The values are updated several times a
minute, as the system collects and processes new sensor data. The values are shown
according to the ICAO recommendations unless otherwise specified. WeatherView also
displays the status of the data.
There are standard WeatherView displays available for the ATC, Observer, and Forecaster
user profiles, with selectable pre-configured options. However, the exact screen layout, the
number of displays, the content of the data fields, and the units used vary depending on the
individual system configuration. This chapter describes the typical basic and optional
features included in the standard displays.
Optionally, AviMet AWOS can take the runway landing direction into account, and adjust the
reporting order of the meteorological sites accordingly. The ATC supervisor can set the
runway in use information and runway landing direction with the Runways display in
WeatherView.
4.2 WeatherView User Interface

There are standard display options available for different user profiles. In addition, optional
features may be selected and customized displays designed. The following sections describe
the typical elements and options.
WeatherView displays are individually configured for each system. Thus, the display
elements and functionalities presented in this chapter may differ from the ones in your
system. Always refer to your system-specific documentation or training material to get the
most accurate information corresponding to your system.
More information
‣ Operating WeatherView (page 46)
28
Chapter 4 – WeatherView
4.2.1 ATC Displays
The typical WeatherView display for ATC contain the following display with some variation
depending on the option(s) selected and the system configuration.
Figure 2 WeatherView: Example Display for ATC
1 Button for printing the screen

2 Button for selecting between day and night display mode
3 Runway in use indication
4 UTC time
5 Buttons for navigating between views
6 Wind frame for each runway location
7 Cloud Base and RVR frame
8 Pressure frame
9 Active Runway in Use frame
10 Prevailing Visibility frame
11 Aerodrome Cloud frame
12 Temperature frame
13 Text field displaying the latest sent weather report
29
4.2.2 Observer Displays
Typical WeatherView display for Observers contains the Main view:
Figure 3 WeatherView: Example Display for Observers
1 Button for printing the screen

2 Button for selecting between day and night display mode
3 Active Runway in Use frame
4 UTC time
5 Buttons for navigating between views, or in some systems, for accessing other
applications
6 Cloud/Sky Condition frames
7 Wind frames
8 Precipitation frame
9 Visibility frame
10 Humitemp frame
11 Reports notification area
12 Sky aerodrome frame
13 Present weather frame
14 Latest sent weather report
15 Pressure frame
30
In addition to the Main view, other typical elements in the WeatherView display set for
Observers include other views containing data in numeric and text format, Graph views, and
other views depending on system configuration. For example, Thunderstorm, ROSA, LLWAS,
and Wind profiler displays may be included if the corresponding sensors are included in the
system.
4.2.3 Weather Data Fields

WeatherView contains data fields for weather parameters, for example, visibility, cloud, or
pressure data. The location and number of the data fields depend on the standard option
selected and the system configuration.
Figure 4 WeatherView: Data Field Example
The data on WeatherView screens come from the sensors that are located along the runway,
and it is updated automatically several times a minute. Some of the values are instant, which
means that they come from a sensor without delay. Some are average values, which means
that the system first collects data (typically for a 2- or 10‑minute period) and then calculates
the average value from that data.
The data is processed data, not raw sensor data. This means that when values come from
sensors to the CDU, the system checks that values fall within the specified range for that
sensor. Values are also rounded and displayed according to ICAO specifications and
recommended practices (SARP) and converted to appropriate measurement units.
4.2.3.1 Data Status Indication

The color of the data values indicates the data status. Depending on the configuration, the
data status indication may be disabled (for each user/user group) or different colors may be
used. For an explanation on the standard colors used, see the following table.
Table 7 WeatherView: Data Field Status Colors
Data Color Data Color Status Description

(Day) (Night)
Black White Normal The data is OK.
Red Modified red Invalid The data is not valid, or it is out of the preset
validation limits.
Brownish yellow Modified Old The latest expected data update(s) have not arrived,
brownish yellow but data is still valid for use.
Red slashes Modified red Missing The data is not available because of problems in the
slashes system, or the system has just been restarted and
there is not enough data available yet.
31
Data Color Data Color Status Description

(Day) (Night)
Blue Modified blue Backup Data is coming from a backup source.
Purple in italics Modified purple Manual Data is entered manually by the user using the manual
in italics observations feature, for example, while maintenance
is fixing a sensor problem.
If the data field status is other than normal, see the troubleshooting instructions for some
general problem solving instructions. Check also the local practices at the airport.
More information
‣ Day and Night Display Modes (page 45)
‣ Troubleshooting WeatherView (page 51)
4.2.3.2 Missing Values
In WeatherView, slashes in the data fields indicate missing data. Normally, missing values are
a sign of system problems. However, if the system has been restarted, for example, after
system maintenance, missing average values are a part of normal operation. When the CDUs
have been restarted, the statuses are as follows:
• Instant values appear immediately in WeatherView data fields, and their data status is
normal.
• Average values remain missing until the system has collected enough data to calculate
valid average values.
When the connection between a sensor and the CDU is broken, or when a sensor is out of
order, the data status on WeatherView screens turns first to "old".
Later the values will disappear from data fields and they are indicated as "missing" with
slashes.
• For instant values, the transition from "old" to "missing" happens very quickly.
• For average values the transition happens more slowly. The data remains in the data
fields until the system reaches the validation limit. Typically, the validation limit is
approximately 40 % of the entire average period. In a 2‑minute average, this would be
50 seconds. In a 10‑minute average, the validation limit would be 4 minutes. After the
validation limit is passed, values disappear from data fields. The system replaces them
with slashes (///).
4.2.3.3 Reported or System Data

If configured in your system, the WeatherView application may include the option of
comparing the current automatic system data and the data reported in the last METAR
report, including the manual changes.
4.2.3.4 Dimmed Data in Accordance with Runway-in-use Activity

Depending on system configuration, the data for the runway that is not in use can be
configured to be "dimmed" (grayed out). The displays will follow the runway-in-use status
and automatically gray out the data when needed. This option can be typically selected for
Wind, RVR, and Pressure values.
32
In the following example, RWY24 is dimmed, because RWY06 is in use (simulated data):
Figure 5 WeatherView: Example Dimmed Data
4.2.3.5 Audiovisual Alerts
If the audiovisual alerts option has been selected, the system can be configured to include
alert frames and sound alerts. This is typically available for wind, cloudbase and RVR,
pressure, temperature, and prevailing visibility fields.
An alert frame is displayed around the weather data field, for example, when a weather
parameter value exceeds a preconfigured, customer-specified limit.
Typically, there are three different alert types: Alarm, Warning, and Notification. Depending
on system configuration, sound alerts may be added.
For example, wind direction and speed variation can be framed with orange color:
Figure 6 WeatherView: Example Visual Alert
The following table describes the typical alert types and colors.
CAUTION! Depending on your system configuration, other principles and colors may be
used. The following presents only some typical examples.
33
Table 8 Alarm Types
Type Frame Color Description
Alarm Red When an alarm is raised the frame is blinking.
After acknowledgement the red frame remains, but blinking stops. Alarm
frame disappears only when the alarm reason vanishes.
Warning Orange When a warning is raised the frame is orange, but it is not blinking.
Acknowledgement makes the color disappear.
Notification Green When a notification is raised the frame is colored, but it is not blinking.
Acknowledgement makes the color disappear.
If different types of alerts are linked to the same data field alert frame then only the most
severe alert is shown. Alarm overrides warning and notification, warning overrides
notification.
Depending on the system configuration, the alerts can be automatically acknowledged or an
ACK button is included for acknowledging them. Depending on system configuration and
the notification type, the acknowledging will, for example, stop the flashing.
Alarms, warnings, and notifications may be emphasized with audio sounds. The possible
sound configuration settings are: the type of sound, the continuation of the sound, and the
acknowledging logic.
4.2.3.6 Tendency Indicators
The data fields can also contain tendency indicators indicating whether the value has been
recently increasing, decreasing or has not changed.
Figure 7 WeatherView: Tendency Indicators
The following table describes the standard colors. Depending on the configuration, different
colors may be used.
Table 9 Tendency Indicators
Indicator Description
Green (arrow up) Increasing
Red (arrow down) Decreasing
A dot in the same color as the value Not changed
34
4.2.4 Wind Options
4.2.4.1 Headwind, Tailwind, and Crosswind According to Runway in Use
Information
Typically, the headwind/tailwind and crosswind values are always displayed according to the
magnetic orientation. For example:
• Runway 33-15 with RWY15 in Use
• Headwind/tailwind and crosswind: T07/L08 (according to magnetic declination, not
RWY in use information)
Optionally, the winds can be displayed according to the runway in use information. For
example:
• Runway 33-15 with RWY15 in Use
• Headwind/tailwind and crosswind: H07/R08 (according to RWY in use information)
This applies to numerical and graphical presentations.
4.2.4.2 Headwind, Tailwind, and Crosswind Presentation Options

Depending on your system configuration, the wind components relative to the runway
direction, that is, headwind, tailwind, and crosswind values can be displayed in numerical or
graphical format, presented either from the tower view or the north view.
The wind direction is marked with the following letters:
• T = Tailwind
• H= Headwind
• R = Crosswind from right
• L = Crosswind from left and depending on the configuration, also with arrows
The wind speed values are in alpha-numeric format.
Figure 8 Head/Tail and Crosswind in Numerical Format
Figure 9 Head/Tail and Crosswind in Graphical Format in the RWY Ends and RWY Mid Point
Figure 10 Head/Tail and Crosswind in Graphical Format for the RWY Touchdown Zones
35
4.2.4.3 Wind Rose Options

WeatherView includes wind roses for wind data indication. The following elements are
typically included:
• Arrow indicates 2‑minute average wind direction.
• Colored pegs on the circle perimeter indicate the 10‑minute wind direction variation.
Typically, the variation is always displayed. Optionally, it is possible to display the
variation only when the ICAO rules apply (ICAO Annex 3).
• Runway graphic indicates the runway direction, either from north or tower view.
• Optionally, wind values may also be displayed in the middle of the windrose.
Depending on user needs the wind direction can be displayed either based on magnetic
or true north.
Depending on your system configuration, the runway graphic inside the windrose can
indicate the runway direction either in the north view or in the tower view:
Figure 11 Windrose with Runway Graphic in

North View
Figure 12 Windrose with Runway Graphic in

Tower View (Line Indicating North Direction)
36
Depending on your system configuration, wind direction and wind speed values may be
displayed above the wind rose:
Figure 13 Wind Rose with Wind Values Above
4.2.5 Reports and Notifications Pane

WeatherView screens can also display text fields containing, for example, the text of the
latest METAR report that has been sent from the airport. This field is automatically updated
whenever a new report is sent.
The Notifications pane can be configured to be displayed as an informative field in the
WeatherView displays. There may be a notification informing you that METAR editing time
has started, or that a METAR report has been sent.
In addition to the notification text, the notification can contain a colored frame, which may
be flashing, and a sound alert. The colors, flashing, and sounds have been defined in system
configuration. You can acknowledge the notifications by clicking the ACK button.
Depending on system configuration and the notification type, the acknowledging will, for
example, stop the flashing.
Figure 14 Notifications Pane with Acknowledge Button
When there are active notifications in the Notifications pane, the button of the application
that the notification concerns flashes in the Windows Taskbar.
4.2.6 Radar Warnings
Vaisala IRIS™ Focus weather radar software can be integrated to the Vaisala AviMet AWOS
system. Depending on the level of integration in the system, the following features can be
available:
37
• The IRIS Focus user interface can be embedded in the WeatherView application.
• The WeatherView application can show warnings from the radar. The following figure
shows an example of the warnings.
Figure 15 Radar Warnings in WeatherView
The following cloud types generate the warnings:

• TCU = Towering cumulus
• CB = Cumulonimbus
• SH = Showers
• GR = Hail
The first value shows the distance of the cloud from the airport reference point (in
kilometers).
The second value shows the compass point of the cloud from the airport reference point. If a
compass point is not shown, the cloud is on top of the airport.
An orange frame around the value means that the cloud is forming. A red frame means that
the cloud has formed.
The user profile for accessing radar data depends on the system configuration.
For more information on the IRIS Focus software, see IRIS Focus User Guide.
38
4.2.7 Sensor Control Feature

If configured, the Sensor Control feature can be opened with the WeatherView buttons.
With Sensor Control you can select which of the available sensors is used as the source for
the automatic data.
Figure 16 Sensor Control Window
Table 10 Sensor Control Window
Element Explanation
Selection Status Shows the status of the sensor selection:

• Auto: The system selects the sensor automatically in priority order.
• Manual: The user selects the sensor manually from the Selection list.
Selection Shows the sensors available in the system in priority order.
Current Shows the currently used sensor.
Apply changes Saves the changes.
Reset changes Cancels the changes.
39
4.2.8 Graph Fields
Typically, the WeatherView displays for Observers include graph fields. A graph field can
contain several plot lines indicated with different colors.
Figure 17 Graph Field Example
1 Legend: Plot line colors and check boxes for hiding/showing

2 Plot lines
3 Trace view selection check box
4 Time span selection buttons
When the Trace check box is selected and the mouse pointer is placed over the graph, the
graph name, the exact values at the pointer location, and the units for all the displayed
graphs are shown on top of the graph.
Figure 18 Graph: Trace View
In addition, you can hide and show the plot lines, change the time span, and display the
exact values at the pointer location.
More information
‣ Adjusting Graph Fields (page 48)
40
4.2.8.1 Graph Configuration Window

You can adjust the graph properties in the configuration window. The available adjustable
options depend on user rights. The configuration window can be accessed by right-clicking
on the graph and then selecting the Configure option. The configuration is made
individually for each graph.
The window has tabs with selections for changing the properties of the axes, grids, and plot
lines.
Depending on the system configuration and your user profile, the configuration window
may contain only one tab (Axes), two tabs (Axes and Grids), or all three tabs (Axes,
Grids, and Plots).
Figure 19 Graph Configuration Window
When the WeatherView application is closed and restarted, the graph default settings will
override the changes made in the Configuration window.
41
Table 11 Graph Configuration Window Tabs
Tab Description
Axes Allows the user to change the unit axis and the step, that is, how many graph grid lines
are drawn.
Grids Allows the user to change in what style the graph grid lines are drawn, for example,
whether they are visible and what color is used.
Plots Allows the user to choose how many plot lines are shown on the graph and to select the
data source and the text labels for the plot lines.
4.2.9 Lightning Display
If the AviMet system contains a local lightning warning sensor, such as Vaisala Thunderstorm
Local Lightning Sensor TSS928™, or receives data from a lightning detection network, for
example, Vaisala Total Lightning Processor (TLP), the lightning data can be displayed in the
Lightning display.
Figure 20 Lightning Display
More information
‣ Introduction to Lightning Display (page 56)
4.2.10 MET Display
The typical WeatherView Met display contains the following meteorological data with some
variation depending on the option(s) selected and the system configuration.
42
Figure 21 MET Display
RWY
Runway
WDINS
Instant Wind Direction
WSINS
Instant Wind Speed
Raw MOR
Raw Meteorological Optical Range
MOR1A
One minute average Meteorological Optical Range
Raw RVR
Raw Runway Visual Range
RVR1A
One minute average Runway Visual Range
RWY Lights
Runway lights intensity setting
BLINS
Instant Background Luminance
TEMP
Temperature
DP
Dew point
RH
Relative Humidity
QNHINS
Instant QNH
QFEINS
Instant QFE
43
4.2.11 Runways Display
Typically AviMet receives the runway-in-use information automatically from an external
system. If this information is temporarily not available, the Runways display in WeatherView
is used for setting which runways are in use and their runway landing direction, that is, if the
runways are used for landing or take-off.
The changes affect the WeatherView displays, and if configured, the reporting of the MET
REPORT reports.
Also the light intensity values can be entered manually using the Runways display when the
automatic values from a light setting unit are not available.
Figure 22 Runways Display Example
If the AviMet system does not receive the runway-in-use information automatically from an
external system, see section Introduction to Runway Configuration (page 53).
More information
‣ Setting Runway-in-use Manually (page 50)
‣ Entering Light Intensity Value Manually (page 51)
4.2.12 WeatherView Buttons
The WeatherView displays typically contain some or all of the buttons listed in the following
table. Other buttons may be included depending on the system configuration.
Table 12 WeatherView Example Buttons
Button Description
Button for selecting between the predefined day and night display modes.
Button for printing the screen.
44
Button Description
Buttons for accessing the different WeatherView tabs. The arrow indicates the selected tab. The number and
content of the buttons depend on the system configuration:
Opens the Main view.
Opens the Graph view.
Opens the Met view.
Opens the ATC view.
Opens the Reports view.
Opens the Runways display.
Button for toggling between different available values, for example, instant, 2‑minute
average, and 10‑minute average values. Typical in Observer displays.
(Optional) Buttons for selecting the displayed unit. Typically, primary reported units are
defined in the system and used in WeatherView.
Acknowledges the notifications in the Notifications pane.
Buttons for accessing other applications or features, for example, Sensor Control. The number and content
of the buttons depend on the system configuration. For icons on the Graph view, refer to Figure 17 (page 40).
4.2.13 Day and Night Display Modes

If configured in the system, the WeatherView screens can be displayed in two different
modes depending on the lighting conditions, the day mode and the night mode. The modes
can be switched using the day/night button.
The day mode is used in conditions with a lot of background light, when the screen also
needs to be illuminated well to be visible, for example, during day time. The night mode is
useful when there is not much light available, and the reflections should be minimized, for
example, during night time.
45
Figure 23 WeatherView: Night Display Mode
More information
‣ Switching between Day/Night Display Mode (page 46)
4.3 Operating WeatherView
More information
‣ WeatherView User Interface (page 28)
4.3.1 Switching between Views

When WeatherView starts, a view specified in configuration is automatically displayed.
Depending on the configuration of the system, there might be several weather data views
available.
1. To navigate between the available views in the WeatherView application, click one of
the navigation buttons.
4.3.2 Switching between Day/Night Display Mode

1. Click the day/night button in the application header once.
2. To switch back, click the button again.
46
More information
‣ Application Header (page 67)
4.3.3 Monitoring Weather Data and Status

1. Monitor the color of the data field values. There may be problems in the system if one
of the following takes place:
• Value color turns to red, brownish yellow, purple, or blue.
• Red slashes appear in the data fields: Values are missing.
• Red alert frame appears around the value.
CAUTION! The status colors are configured individually for each system. Thus the
colors in your system might differ from the ones presented here.
2. Monitor the data in all the needed screens.
More information
‣ Weather Data Fields (page 31)
4.3.4 Acknowledging Weather Data Field Alerts

Your system may include alerts in the weather data fields, typically alert frames and/or
sound alerts.
Depending on system configuration, the alerts may be automatically acknowledged after a
preconfigured time, or you have to click the ACK button to acknowledge them. Clicking the
button will, for example, stop the flashing and/or sound alert.
More information
‣ Weather Data Fields (page 31)
4.3.5 Acknowledging Reports Notifications

Your WeatherView may contain the Notifications pane informing you about issues related to
weather reports.
As a standard, you have to acknowledge the notifications by clicking ACK. Clicking the
button stops the flashing and the sound alert.
More information
‣ Reports and Notifications Pane (page 37)
47
4.3.6 Viewing Reports
If available in your system, you can view the latest reports by clicking the Reports icon in
WeatherView.
4.3.7 Viewing Current System Data and Reported Data

If configured in your system, the WeatherView application may include the option of
comparing the current automatic system data and the data reported in the last METAR
report, including the manual changes. Select the appropriate tab, for example, System, to
view the system data.
4.3.8 Adjusting Graph Fields

Some WeatherView screens contain graph fields. You can adjust how the graph fields look in
the following two ways:
• You can adjust the graphs using the default configuration available, see the sections
below.
• You can configure the graph settings.
More information
‣ Configuring Graph Properties (page 48)
4.3.8.1 Changing Time Span
1. Select one of the time span buttons, for example, 1 h.

The system changes the time span and the plot lines are adjusted accordingly.
4.3.8.2 Hiding/Showing Plot Lines
1. To hide a plot line, remove the selection from the check box next to its name in the
legend.
The plot line will be hidden.
2. To show the plot line again, select the check box for that plot line.
4.3.8.3 Viewing Exact Values (Trace View)

To display the exact values in the mouse pointer location:
1. Select Trace.
2. Move the mouse pointer over the graph.
The Trace view is displayed with the graph name, the values, and the units for all displayed
graphs.
4.3.9 Configuring Graph Properties

Some WeatherView screens contain graph fields. You can adjust how the graph fields look in
the following two ways:
48
• You can configure the graph settings in the Configuration window, see sections below.
• You can adjust the graph appearance using the default configuration available.
Depending on the system configuration and your user profile, the configuration window
may contain only one tab (Axes), two tabs (Axes and Grids), or all three tabs (Axes,
Grids, and Plots).
The configuration must be changed individually for each graph.
When the WeatherView application is closed and restarted, the graph default settings will
override the changes made in the Configuration window.
More information
‣ Adjusting Graph Fields (page 48)
4.3.9.1 Configuring Unit and Axis Appearance
1. Right-click on the graph you want to configure and select Configure.

The Configuration window is displayed.
2. On the Axes tab, enter the unit, minimum, and maximum values for the leftside and the
rightside axis separately. To determine how many graph grid lines are drawn, enter the
value in the Step field.
3. Select the time scale from the Time scale drop-down list.
The changes are valid immediately.
When you close the WeatherView application, the default configuration will be used
again.
4.3.9.2 Configuring Grid Line Color and Style

2. On the Grids tab, click Color to select the color for each grid line separately (left, right,
bottom).
3. Select the line style for each grid line from the drop-down lists, for example, Solid.
4. Select for each grid line whether they are visible or not.
When the Visible option is selected, the grid line is drawn.
49
again.
4.3.9.3 Configuring Plot Lines

2. On the Plots tab, enter the text for the plot line name (displayed in the legend, for
example).
3. Select for each plot line whether they are visible or not.
When the Visible option is selected, the grid line is drawn.
4. Click Color to select the color for each plot line.
5. Click Object/Field to select the data source for each plot line.
again.
4.3.10 Setting Runway-in-use Manually

The AviMet system normally receives the runway-in-use information automatically from an
external system. If the automatic data is not available, you can manually set which runways
are used and the runway landing direction for them in the Runways display view.
1. Open the WeatherView application.
2. Select the Runways view.
3. For the runway in question, use the slider to change the selection into Manual mode.
4. For each runway end, select an option from the list.
For example, Landing, Take-off, or Not in use. Normally, one end of the runway must
have the selection Not in use. See the caution below.
CAUTION! If you select a cross-operation, there is a warning displayed below the

runway. However, the system lets you make these selections in case they are
needed for special situations.
5. To save the changes, select Apply. To cancel the changes, select Discard.
REPORT reports.
50
More information
‣ Runways Display (page 44)
4.3.11 Entering Light Intensity Value Manually

The AviMet system normally receives the light intensity value automatically from a light
setting unit. If the automatic input is not available, you can enter the light intensity values
manually.
1. Open the WeatherView application.
2. Select the Runways view.
3. For the runway in question, use the slider to change the Light intensity selection into
Manual mode.
4. Select the appropriate light intensity value for the runway from the list.
5. To save the changes, select Apply. To cancel the changes, select Discard.
More information
‣ Runways Display (page 44)
4.4 Troubleshooting WeatherView
If you detect problems in WeatherView, first check the Diagnostics application for more
details on the situation. If there are problems with the sensors, the name of the sensor is
included in the event message. Make a note of the sensor and report the information to
maintenance personnel.
The following table lists some problems that might occur when you are using WeatherView
and some typical solutions to the problems. Check the local practices for more detailed
instructions.
In WeatherView, slashes in data fields indicate missing data. Normally, missing values are a
sign of system problems. However, right after the system has been restarted, missing
average values are a part of normal data handling routine.
51
Table 13 Troubleshooting WeatherView
Problem Probable Cause Solution
There are slashes (///) in data The data is missing because of Check the Diagnostics application
fields. problems in the system. for DATA MISSING message. If
there is no DATA MISSING
message, wait for 10 minutes. The
data status should change back to
normal.
The system has been recently If the slashes remain in the fields,
restarted and there is not enough contact maintenance.
data available yet.
Data field value is red. The data is invalid, or out of the Contact maintenance.
preset validation limits.
Data field value is brownish yellow. The data is not updated by the Wait for 5 minutes to see if the
system because of problems in data field color changes to normal.
sensor communication. If slashes appear in the data field
(missing status), contact
maintenance.
Data field value is purple and The data is inserted manually Contact observer or maintenance
values do not change. because of problems with the for more information.
sensor.
Data field value is blue. The data comes from a backup Contact maintenance for more
source. information.
Cloudbase height and instant cloud NCD (No Clouds Detected) appears No action is needed.
height value is NCD. automatically in cloud data fields
when the system has detected a
VER VIS condition.
More information
‣ Introduction to Diagnostics (page 141)
52
Chapter 5 – Runway Configuration
5. Runway Configuration
5.1 Introduction to Runway Configuration
If the runway-in-use information is not provided by an external system, you can set and
select the runway-in-use information in the Runway Configuration view.
Figure 24 Runway Configuration View
If the AviMet system receives the runway-in-use information automatically from an external
system, see section Runways Display (page 44).
5.2 Selecting Predefined Runway

Configurations
Standard runway configurations are combinations of runways-in-use that have been defined
in the local procedures of an air traffic control unit, and configured in AviMet during system
configuration.
1. Open the Runway Configuration view.
2. Select Use standard configuration.
3. Select a suitable standard configuration from the Presets list.
53
4. Select Apply.
The runway image reflects your selections. Check that the image matches the
intended configuration.
REPORT reports.
5.3 Defining a Non-standard Runway

Configuration
Non-standard runway configurations are combinations of runways-in-use that have not been
defined in the local procedures. They can be used in exceptional situations, for example,
when a runway is closed due to maintenance work.
2. Select Use non-standard configuration.
3. Select the arrival and departure runways from the lists.
CAUTION! There are no warnings for using opposite or crossing runways.
4. Select Apply.
The runway image reflects your selections. Check that the image matches the
intended configuration.
REPORT reports.
5.4 Defining Runway Availability

You can define if the runways are available for use.
54
Chapter 5 – Runway Configuration
2. Under Runway Availability, select which runways are closed and which open:
Open
The runway is available for use.
Closed
The runway is not available for use, for example, because of maintenance work.
3. Select Apply.
55
6. Lightning Display
6.1 Introduction to Lightning Display
Lightning display is used for monitoring the lightning strikes and electric field intensity for
the airport. Lightning events are presented as numerical values in a circular area that is
further divided into overhead, near, and distant areas. The near and the distant areas are
divided into 8 sectors. Users can configure alarms for the monitored regions, which can be
any of the areas or the sectors.
The lightning data is received from a local lightning warning sensor, such as Vaisala
Thunderstorm Local Lightning Sensor TSS928™, or from a lightning detection network, for
example, Vaisala Total Lightning Processor (TLP).
6.2 Lightning Display User Interface

The user interface of the Lightning display consists of the Lightning Display page and the
Settings page.
Figure 25 Lightning Display
56
Chapter 6 – Lightning Display
Figure 26 Settings Page
More information
‣ Defining Settings (page 60)
6.2.1 Sound Alarm
When an alarm is activated, a sound alarm is played. You can mute the sound alarm by
clicking the icon at the top right corner:
When you mute the sound, you cannot turn it on again. The sound turns on automatically
when a new alarm is raised.
The alarm sound is a wav. format file defined during system configuration.
57
6.2.2 Lightning View
The Lightning view displays the lightning activity levels and active alarms on a map. The
map is configured during system configuration.
Figure 27 Lightning View
Lightning events are presented as numerical values in a circular area that is further divided
into overhead, near, and distant areas. The distance ranges and the distance unit of the areas
are configured during system configuration. The near and the distant areas are divided into
8 sectors.
Data source
Select the data source for the displayed lightning data: Lightning Detection Network
or Local Lightning Warning Sensor.
58
Zoom level
Select the zoom level. The used unit is defined during system configuration as
kilometers (KM) or nautical miles (NM).
Data period
The data period for which the data is shown, from current time backwards. The period
is defined during system configuration.
Show map
Toggle to show and hide the map.
Cloud lightning events
Shows the number of cloud lightning events. You can adjust the lightning activity
levels and alarm settings in the Settings page.
Legend
Explains the colors indicating the lightning activity levels and alarms. The colors are
defined during system configuration.
You can adjust the lightning activity levels and alarm settings in the Settings page.
6.2.3 Electric Field View

The Electric Field view displays data from the available electric field mills (EFM). The data is
updated in real time.
Figure 28 Electric Field View
59
The time period shown in the graph can be selected above the graph. The graph line colors
indicate the electric field mills listed below the graph.
Electric Field Mill (EFM)
The electric field mill names and their colors in the graph. You may need to use the
scroll bar to see all of them. The names and colors are defined in system configuration.
Current value
The current value from the electric field mills, in kV/m. If the value exceeds the limits
set in the Settings page, the current value is highlighted with a frame. The color of the
frame is defined during system configuration.
6.2.4 Active Alarms View

The Active Alarms view displays the alarms that are currently active. The list shows active
alarms from both data sources, independent from the selection made in the Data source list.
Figure 29 Active Alarms View
The number in the heading indicates the total number of active alarms. Typically you must
scroll down to see all alarms.
To see all the configured alarms, to edit the alarms, or to create new alarms, go to the
Settings page.
6.3 Defining Settings
You can define several settings on the Settings page in the Lightning display.
Advanced settings are performed during system configuration.
More information
‣ Lightning Display User Interface (page 56)
‣ System Configuration (page 64)
6.3.1 Configuring Lightning Alarms

You can configure the alarms displayed in the Lightning view. This includes, for example, the
alarm-triggering and alarm-clearing conditions and the relays that are activated when
alarms are triggered.
1. Select Settings.
60
2. Under Alarm Settings, select Add New. The New Alarm window is displayed.
3. In the Alarm name field, type a unique name for the alarm.
61
4. Under Triggering Condition, define the conditions for raising an alarm. The alarms can
be raised based on the number of lightning events, on the electric field mill (EFM)
values, or both.
Lightning
Select this option to use the number of lightning events to trigger alarms. Then
define the details:
Lightning data source
Select the source of lightning data: Lightning Detection Network or Local
Lightning Warning Sensor.
Lightning threshold
Enter the number of lightning events that must be exceeded to trigger the
alarm. The number includes all lightning events from all the selected
regions.
Monitored regions
Select the regions from which the lightning events will be counted for this
alarm.
Electric Field Mills (EFM)
Select this option to use the EFM values to trigger alarms. Values between EFM
positive and negative thresholds define the safe value range. All monitored EFM
values must fall out of this safe range for the alarm to be triggered. Define the
threshold values:
EFM positive threshold
Enter the threshold value that the monitored EFM value must exceed for
the alarm to be triggered. The range of acceptable values is 0.3 to 5
kilovolts per meter.
EFM negative threshold
Enter the threshold value beneath which the monitored EFM value must be
for the alarm to be triggered. The range of acceptable values is - 0.3 to -5
kilovolts per meter.
Monitored EFMs
Select which EFMs are monitored for this alarm.
5. Under Relays, select the external relays that are activated when the triggering
conditions are met. External relays can control, for example, warning horns or warning
lights, as configured during system configuration.
6. Under Clearing Condition, enter the time period that the system waits before clearing
the alarm. The time period starts when the triggering conditions are no longer met. If
the triggering conditions are met during the waiting time, the alarm remains active.
7. Select Apply.
If there is a message about changes not being applied, scroll up to the indicated fields,
correct the fields, and select Apply again.
6.3.2 Editing Lightning Alarms

1. In the Lightning display, select Settings > Alarm Settings, and find the alarm you want
to edit. You may need to scroll down the page to see it.
62
2. Select Edit.
3. Make the changes in the Edit Alarm page.
4. Select Apply.
If you want to cancel the changes you have made, select Discard Changes or scroll
to the top of the window and click the x to close the window.
Remember to select Apply when you want to save the changes.
6.3.3 Defining Activity Level Settings

To define the limits for the lightning activity levels displayed in the Lightning view, you can
set the limits for the activity level Moderate. The other activity levels are automatically
adjusted based on the settings of this level.
1. In the Lightning display, select Settings.

2. Under Activity Level Settings, enter the upper and lower limit of Moderate lightning
activity for each area.
3. Select Apply. The Occasional and Frequent activity level limits are automatically
adjusted.
6.3.4 Configuring Connection Settings

1. In the Lightning display, select Settings.
2. Under Connection Settings, enter the IP address and the port number of Total
Lightning Processor (TLP) in format: <IP ADDRESS>:<PORT NUMBER>.
3. Select Apply.
63
6.4 System Configuration
The Lightning display is always configured individually to meet the local requirements.
During system delivery, Vaisala personnel have configured the system parameters and the
basic content of the views, including the following:
• Map and other display components, such as the used colors
• Distance ranges of the overhead, near, and distant areas
• Distance unit: kilometer (KM) or nautical mile (NM).
• Electric Field Mills (EFM)
• Relays
• Detection time interval
• Alarm sound file
CAUTION! System configuration is only allowed by authorized Vaisala personnel.
CAUTION! Unauthorized editing of configuration files (.INI files) can result in data loss
and incorrect operation of the AviMet system. Vaisala assumes no liability for system
errors caused by unauthorized editing of the configuration files.
More information
‣ Defining Settings (page 60)
64
Chapter 7 – METAR/SPECI
7. METAR/SPECI
7.1 Introduction to METAR/SPECI
The Reports application contains the METAR/SPECI template for editing and sending the
METAR and SPECI weather reports. If configured in your system, the templates for local
routine reports (MET REPORT) and local special reports (SPECIAL) are also included.
At the beginning of the standard observation time the system notifies the user, updates the
automatic data, and creates the code for the sub-groups. The user checks the automatic
data, fills in the manual data, and builds the report. The system then validates the data and
displays the final report code. Finally, the system publishes the report for further use, for
example, sends it to the AFTN line, or to other applications in the system.
Only one user at a time can edit the template. When a user reserves a template for editing,
any existing editing session is interrupted.
During the editing process, the user can also change the data sources for the report and
update the automatic data with the most recent data.
The reports can also be edited before the standard observation time and placed in a buffer
waiting for the official sending time. If weather conditions change before the official sending
time, the report can be recalled for editing.
The Reports application typically contains all the basic report templates included in the
system. For example, the TAF template is typically part of the Reports application. For
information on the other report templates, see their relevant chapters in this manual.
In the Setup tab, the user can adjust the settings related to the reports, for example, default
data sources and SPECI triggering limits.
The system supports dissemination of data reported in METAR/SPECI using the IWXXM XML
schema. For more information, see Manual on the Digital Exchange of Aeronautical
Meteorological Information and Manual on System Wide Information Management (SWIM)
Concept.
65
7.2 METAR/SPECI User Interface

The user interface of the METAR/SPECI template consists of the report template tabs for all
the available report types and the SETUP tab for defining the settings. The following figure
presents the typical elements.
Figure 30 Reports Application, METAR Template
1 Tabs for selecting report templates and setup

2 Coded data fields
3 Fields for MODE, STATE, and Time left before sending time
4 Final coded report field
5 The name of the user who is currently editing the template
6 Application header, including, for example, button for selecting day/night display mode
and toggling the editing mode on/off
7 Set CAVOK button
8 Data source selection lists
9 Buttons for editing, building, and sending the reports
10 VALIDATOR field (Optional)
In addition, the user interface can contain the Notifications pane. The Notifications pane
can also be integrated as part of another AviMet application, for example, WeatherView.
When you have to interact with the system, the buttons at the lower right-hand corner are
replaced by a question field and Yes and No buttons.
66
The following figure presents a typical MET REPORT tab.
Figure 31 Reports Application, MET REPORT Template
In addition to the typical elements, the MET REPORT template includes data fields for
multiple runways.
SPECI and SPECIAL template tabs look similar to METAR and MET REPORT template tabs.
As each AviMet system is individually configured, system-specific elements can be added

and some of the typical elements presented here can be excluded during system
configuration.
More information
‣ Notifications Pane (Optional) (page 75)
‣ Simultaneous Users (page 26)
7.2.1 Application Header
The application header at the top of the Reports application can contain the station name,
current time, and the name of the editing user. Typically it also contains buttons for releasing
the template from the editing state and for toggling between the day/night mode.
67
7.2.2 Report Template Tabs

The type and number of report tabs varies depending on the system configuration. The
following report tabs are described in this chapter:
• METAR tab for editing and sending METAR reports.
• SPECI/COR tab for editing and sending SPECI reports and corrections to METAR and
SPECI reports.
• MET REPORT tab for editing and sending MET REPORT reports.
• SPECIAL tab for editing and sending SPECIAL reports.
• SETUP tab for defining the default data sources, changing the report mode, and
defining the SPECI/SPECIAL limits.
• MANOBS tab for entering manual data.
The typical elements on the tabs are described in the following sections.
7.2.3 Coded Data Fields in Report Tabs

The coded data fields contain the current weather data in the coded format. The data is
coded in the correct report format, for example, 10010KT.
The number and the content of the data fields and the coding practices used correspond to
the ICAO and WMO recommendations. Depending on the system configuration and local
practices, other regulations may be used.
The sources for the data in these fields depend on the system configuration. The data source
selection list shows the current data sources.
Typically, most of the data fields are automatic, that is, the data is based on sensor or system
data and generated automatically by the system. Slashes in automatic fields may indicate
missing data or sensor communication problems.
Some data fields are defined as manual, that is, the data is entered by the user in the code
field in the coded report format. The manual data is valid for the report being edited only.
For more permanent manual data, the MANOBS tab or the Actuals view can be used,
depending on the system configuration.
When building the report, the system collects the codes from the individual coded data
fields and builds the final report code in the final report field. After report building, a red
frame around the data fields indicates wrong code syntax. Any other invalid items are
displayed in the VALIDATOR field.
CAUTION! The code validator is designed to check code consistency. However, the
check is never complete, but finds typical inconsistencies according to Vaisala
implementation. The user has always the final responsibility to evaluate and accept the
code that he publishes.
Table 14 Coded Data Field Frame Colors
Color Description
Red Indicates wrong code syntax after building the report.
68
Color Description
Green Indicates that the field is manual.
More information
‣ Regulatory Compliances (page 24)
‣ Data Source Selection Lists in Report Tabs (page 71)
‣ Manual Observations Tab (page 80)
7.2.4 Data Input Windows

If available in your system, you can view and enter values for some data in separate input
windows.
7.2.4.1 Visibility Input Window

When available in your system, the Visibility Input window enables you to view the
automatic visibility data values, or enter the visibility data manually.
The window is displayed when you click the plus (+) button next to the VIS data field.
Figure 32 Visibility Input Window
7.2.4.2 Cloud Input Window (Optional)

When available in your system, the Cloud Input window enables you to view the automatic
raw data values for clouds, or enter the cloud data manually. You can also select the input
unit.
The window is displayed when you click the plus (+) button next to the Cloud data field.
69
Figure 33 Cloud Input Window
7.2.4.3 Present Weather Input Window

When available in your system, the Present Weather Input window enables you to enter the
present weather codes by selecting them from lists. You can also select the intensity.
The window is displayed when you click the plus (+) button next to the present weather
data field.
Figure 34 Present Weather Input Window
7.2.4.4 Recent Weather Input Window

When available in your system, the Recent Weather Input window enables you to enter the
recent weather codes by selecting them from lists.
The window is displayed when you click the plus (+) button next to the recent weather data
field.
70
Figure 35 Recent Weather Input Window
7.2.5 Data Source Selection Lists in Report Tabs

The data sources can be changed individually for each report with the drop-down lists next
to the coded data fields. The selections are valid for the current report only.
The available data source options vary between systems.
Table 15 Typical Data Source Selection List Options
Source Description
MANUAL User enters data manually in the coded data field in the coded format. When this
option is selected, the field will be empty by default and a green frame will be
added around the field.
Site id, for example, System generates data automatically in the coded data field, based on the
RWY28 corresponding system data from the site.
MANOBS System generates the data automatically in the coded data field, based on the raw
data entered by the user in the MANOBS tab.
RWY_IN_USE System generates the data automatically in the coded data field, based on the
Runway in use selection in the Runways display in the WeatherView application.
PREV_REPORT System retrieves data automatically from the previous sent report.
AUTOMATIC System generates the data automatically in the coded data field, based on sensor
or system data.
AERODROME System generates the data automatically in the coded data field, taken from the
site that has been defined as representative of the airport in general.
More information
‣ Default Input Settings Page (Data Source) (page 77)
‣ Changing Data Sources (page 87)
7.2.6 Final Coded Report Field

After building the report, the system displays the final report code in the final coded report
field. The final report code is a combination of the values in the coded data fields. An orange
frame is displayed when user edits the data in report template.
71
The report mode and state are displayed above the final code field. Also the time left before
the next routine report sending time is displayed (in minutes).
Figure 36 Final Coded Report Field with Mode, State, and Time Left Indicators
Table 16 Typical State Options
State Description
Idle The state between the previous sent report and the start of the next editing time.
However, user can enter editing mode by clicking the corresponding report button.
Editing The editing state when user can make changes to the report before sending it.
Immediate Editing state indicating that the official publishing time is over. If report is sent from this
editing state, it will not be placed in the buffer, but instead it is published immediately.
Retarded Editing state indicating that the report is retarded. If the report is sent from this state, it
will not be placed in the buffer but instead it is published immediately. When the
preconfigured editing time for the next report arrives, new report editing starts and the
old retarded report cannot be sent any more.
Immediate idle State indicating that the official publishing time is over and report editing has not even
been started. This is not seen during normal operation, only in special cases, for
example, when the report has been canceled before the official publishing time. If report
editing is started from this state, state changes to Immediate editing.
Edited The report has been edited and built and is ready to be sent.
Ready The report is ready to be sent (for example, the user has clicked Send), but it is still in
the buffer waiting for the official sending time.
Inactive Safe state used when the system cannot ensure that routine report and SPECI or
SPECIAL report sending order would be logical with the report observation time.
Automatic SPECI/SPECIAL trigger events will not cause notifications or automatic
SPECI/SPECIAL sending. If the user wants to start editing and clicks the appropriate
button, the system will ask for confirmation.
If configured, the system validates the data during building and shows any discrepancies in
the VALIDATOR field.
7.2.7 Validator Field (Optional)

If included in your system, the VALIDATOR field displays the results of the validity checks
that the system performs when building METAR and SPECI reports.
72
When you click Build, the system performs a set of validations, depending on the
configuration. Typically, the system checks that certain values, for example, temperature,
dew point, and pressure, fall within the normal range. With the optional METAR cross-
checker, the system also checks that present weather codes and numeric data are consistent
and that you have entered cloud amount data together with the cloud height data.
If the system finds invalid values, it informs you about them in the VALIDATOR field. You can
either continue with sending the report, or, if needed, correct the data in the coded data
fields and build the report again.
Figure 37 Validator Field
implementation. The user has always the final responsibility to evaluate and accept the
code that he publishes.
7.2.8 Airport-Specific Elements (Optional)

The template may contain optional buttons that reveal airport-specific data, for example,
current weather data from the sensor sites. Typically, the data is for information only, it
cannot be edited or updated. This part of the template can be shown and hidden using the
buttons provided and the contents of these data fields depend on the system configuration.
7.2.9 Buttons on Report Tabs

The typical buttons on the report tabs are described in the following table. Some of the
buttons are located in the application header.
Table 17 Buttons on Report Tabs
Button Description
METAR Activates the template for editing a METAR report. (Available on the METAR tab.)
SPECI Activates the template for editing a SPECI report. (Available on the SPECI/COR
tab.)
73
Button Description
MET REPORT Activates the template for editing a MET REPORT. (Available on the MET REPORT
tab.)
SPECIAL Activates the template for editing a SPECIAL report. (Available on the SPECIAL
tab.)
SETUP Opens the Setup tabs for defining the default data sources, changing the report
mode, defining the SPECI/SPECIAL limits and the notification settings.
Update Updates the template with current data during editing. Example use: During
METAR editing, a SPECI is triggered, and you want to update also the METAR
report with the changed data.
Build Builds and checks the validity of the report. Also copies the manually entered
values from the report that is being edited to other report templates in the editing
state. Copies only the preconfigured set of manually changed data that is common
between report types, for example, temperature data, and converts the code into
the target report format.
COR Corrected: Activates the template for sending a correction to the last sent report.
(Available on the SPECI/COR tab.)
Cancel Cancels the report being edited.
Recall Recalls the pending report for editing. (Applicable when the routine report has
been sent before the official sending time and is waiting in the buffer for the
actual sending.) Example use: There is a change in weather (SPECI) and you want
to edit the pending METAR report as well: this command recalls it from the buffer
for editing.
Send Will be activated after building the report. Sends the report to the external
interface, typically the AFTN line (METAR/SPECI), or to the weather displays and
other internal systems. SPECI and SPECIAL will be sent immediately, while routine
reports will first wait in a buffer for the official sending time. If needed, the
pending reports can be recalled for editing. If the official sending time is over, the
reports will be sent immediately.
Yes/No (Located in place of the building and sending buttons) Available when the system
asks you to confirm your actions.
ACK Acknowledges the notifications in the Notifications pane. Acknowledging stops

any flashing and beeping, but the notification texts remains.
(Optional) Opens the input windows, for example, for entering cloud value
manually.
Changes the display mode, which can be used depending on the lighting
conditions. The day mode is used in conditions with a lot of background light. The
Day / Night Display night mode is useful when there is not much light available, and the reflections
need to be minimized.
Prints the current screen.
Print
Toggles the editing mode on (Edit) and off (Release). When in editing mode, the
name of the editing user is displayed in the application header.
Edit / Release
74
Button Description
Takes a snapshot image of the current template. Select the snapshot time from the
list next to the button. The snapshot is placed on the clipboard and you can paste
Snapshot it into another program.
7.2.10 Notifications Pane (Optional)

The Notifications pane can be displayed on all the report tabs. In addition, it can be
configured to be displayed as part of other AviMet applications, for example, as an
informative field in the WeatherView application.
The Notifications pane shows information about important actions, warnings, and system
states. The content, type, and number of notifications depend on the system configuration.
For example, there may be a notification informing you that METAR editing time has started,
or that a METAR report has been sent.
be flashing, and a sound alarm. The colors, flashing, and sounds have been defined in system
configuration. Typically, there are separate sounds and colors for different alarm groups (for
example, notifications, warnings, and alarms). For example, alarm notifications that require
immediate user action may have a specific sound and a flashing frame attached to them,
while other notifications may appear only as text.
You can acknowledge the notifications by clicking the ACK button. Depending on system
configuration and the notification type, the acknowledging will, for example, stop the
flashing and the sound alarm, or the notification frame will disappear.
More information
‣ Audio Notification Settings Page (page 79)
7.2.11 METAR/SPECI Setup Tab

The Setup tab contains pages for defining the settings, for example, for default data sources
and SPECI/SPECIAL limits.
75
7.2.11.1 Report Mode Settings Page

On the Report Mode Settings page, you can set the following settings.
Table 18 Report Mode Settings Options
Element Description
Operation mode Manual: This is the normal, most typical mode used: the user activates the
template, edits the code fields as needed, builds, and sends the report. The user
also reacts to the notifications and/or validator messages generated by the
system.
Auto: Automatic mode is for situations where the report has to be sent without
any user intervention. When the Auto option is selected the system will send the
report automatically and add the appropriate automatic mode coding in the
report code. The mode change will be valid starting from the next scheduled
routine report or the next time the SPECI/SPECIAL limits are reached.
CAVOK mode System: System selects if the CAVOK situation is coded, based on ICAO
specifications.
CAVOK not allowed: CAVOK is not coded, instead, the VIS, RVR, and cloud groups
are coded as such.
System but report manually entered high clouds: System selects if the CAVOK
situation is coded, based on ICAO specifications, but if you enter manually clouds
that are above the minimum sector altitude, the manually entered high clouds are
reported instead of CAVOK.
Noise abatement In use: (If available) Select this when the noise abatement procedures are in use in
procedures the airport and you want the SPECIAL Gust trigger thresholds to be in accordance
with the noise abatement procedures.
Not in use: (If available) Select this when the noise abatement procedures are NOT
in use in the airport.
Optimum light intensity Set the optimum runway light intensity that would be appropriate for the
prevailing conditions. This value will be used in RVR (runway visual range)
calculation when:
• lights are switched on and the light intensity is 3 per cent or less.
• lights are switched off (or at the lowest setting pending the resumption of
operations)
Figure 39 Setup Tab, Typical Report Mode Settings Page
More information
‣ Sending Automatic Reports (Optional) (page 86)
76
7.2.11.2 Default Input Settings Page (Data Source)

On the Default Input Settings page, you can change the default data sources that provide
the data to the reports. The change may be needed, for example, in sensor problem
situations, when the runway in use has been changed, or the report mode has been
changed.
Figure 40 Setup Tab, Default Input Settings Page
The changes are saved when you click Apply.
More information
‣ Changing Data Sources (page 87)
77
7.2.11.3 Limit Criteria Settings Page

On the Limit Criteria Settings page, you can edit and select the limits used for triggering
SPECI and SPECIAL reports.
Figure 41 Setup Tab, Limit Criteria Settings Page
Table 19 Limit Criteria Settings Page Elements
Element Description
Limit fields Displays the limits used for triggering SPECI and SPECIAL reports for the reason
indicated in the field name. The limits can be edited. Several limits are separated with
a comma.
Check boxes Select the check box to enable/disable the trigger. When the check box is selected
the trigger is in use.
Apply Saves the changes.
Cancel Cancels the changes, recalls the latest saved limit criteria.
Reset to ICAO Resets the values to the pre-configured limits, for example, those specified by ICAO.
78
7.2.12 Audio Notification Settings Page

On the Notification Settings > Audio Notifications page, you can enable and disable audio
notifications and select what triggers the audio notifications.
Figure 42 Setup Tab, Audio Notifications Page
Table 20 Audio Notifications Page Elements
Element Description
Enable Audio Notifications Select this to enable the audio notifications.
User Profile Shows the profile that the changes will be applied to, for
example, Observer.
Play Audio Notifications Select the check box for the action and report types that you
want to trigger the audio notification.
Apply Saves the changes.
Cancel Cancels the changes and recalls the latest saved settings.
Reset to defaults Resets the values to the pre-configured default settings.
79
More information
‣ Notifications Pane (Optional) (page 75)
‣ Changing Audio Notification Settings (page 87)
7.2.13 Manual Observations Tab

If configured in your system, the MANOBS tab is used for entering manual data, for example,
when a sensor is out of order or being maintained, or about a weather parameter that is not
measured by any sensor. The data is entered in the coded format or as raw data, depending
on the system configuration. Depending on system configuration, this feature may be part of
another application.
7.3 Operating METAR/SPECI Template

Depending on system configuration, typically the following reports can be edited and sent
using the report templates:
• METAR reports (normal, delayed, corrected, automated)
• MET REPORT reports (normal, delayed, automated)
• SPECI reports (normal, corrected, automated)
• SPECIAL reports (normal, automated)
The following describes the typical workflow of editing, building, and sending a normal
METAR report. However, you can use the same general procedure for other the report
types: just replace "METAR" in the instructions with the report type in question and
"editing time" with limit criteria trigger for SPECI and SPECIAL.
7.3.1 METAR Editing and Sending Times

METAR and MET REPORT editing times and periods are defined in the system configuration.
80
The following figure shows an example of the editing sequence in an airport where a METAR
report is sent twice an hour and the editing period is 5 minutes.
Figure 43 Example of METAR Editing and Sending Times
In this example, METAR sending times are 20 minutes past and 10 minutes to the hour. At
15 minutes past and 15 minutes to, the system updates the values in the METAR template
and displays a notification stating that it is the start of the editing time. You have a
preconfigured amount of time to edit and send the report, in this example, 5 minutes. During
this time, the automatic values in the template are not updated by the system, unless you
prompt an update.
More information
‣ Editing and Sending Normal Reports (page 82)
7.3.1.1 Starting Editing before Editing Time

You can also start editing a report before the start of the editing time. For example, if you
want to edit the METAR report, activate the template by clicking the METAR button and
start editing. When the official editing time starts, the system will ask you if you want to
replace the automatic data with current automatic data.
You can also send the report before the actual sending time. The report will be placed in a
waiting buffer until the official sending time. During the pending time it can be recalled for
editing, if needed.
81
7.3.2 Editing and Sending Normal Reports
The following describes the typical workflow of editing, building, and sending a normal
METAR report. However, you can use the same general procedure for other the report
types: just replace "METAR" in the instructions with the report type in question and
"editing time" with limit criteria trigger for SPECI and SPECIAL.
1. When the notification about the start of the editing time is displayed in the
Notifications pane, select ACK.
This stops any flashing and sound.
2. Open the METAR tab, if not already open.
3. Check the code in the automatic coded data fields. If needed, change the data source
from the source selection list.
4. If there are slashes (///) or incorrect values in automatic fields, correct the value:
a. Select Edit at the top of the METAR view.
b. If you want to use the automatic data as basis, click the data field. The source
changes to MANUAL, retaining the previous text as basis. Otherwise, select
MANUAL from the source selection list.
c. Correct the value manually in the coded data field.
d. Inform the maintenance personnel, if needed.
If the manually corrected values deviate from the automatic values, a SPECI
report may be triggered after the report has been sent. To prevent this, select
Setup > Default Input Settings, and change the data source for that value to
MANUAL.
5. Fill in the manual data fields in the coded format. If available in your system, you can
also click the + button to edit cloud and visibility data manually, or to select present
and recent weather codes from lists.
6. When finished editing, select Build.
The system builds and validates the report and displays the final code in the METAR
field.
The manually edited values will be automatically copied to other active reports in
the editing mode and converted into the target report format. This concerns only
preconfigured set of manually changed data that is common between report types,
for example, temperature data.
82
7. If the system finds invalid values during building METAR and SPECI, it informs you
about them in the VALIDATOR field and with a red flashing box around the data fields
with incorrect syntax. You can either:
• Continue with sending the report.
• Correct the data in the coded data fields and select Build again.
implementation. The user has always the final responsibility to evaluate and accept
the code that he publishes.
8. When the report is ready to be sent, click Send.

The system publishes the report for further use in external or internal systems. For
example, the system adds the AFTN headers to the METAR report and sends the report
to the AFTN line and/or to other workstations or internal system, as configured.
If a routine report is sent before the official sending time, it will be pending in a
buffer until the sending time. During that time the report can be recalled for
changes. SPECI and SPECIAL reports are always sent immediately.
9. If other users need to use the template, select Release in the application header to
enable this.
83
Figure 44 Normal Report Editing Procedure
7.3.3 Canceling Current Report

1. To cancel the report before sending it, click Cancel.
The report is not sent and the data contained in the report is lost. The template is no longer
in editing mode.
7.3.4 Editing and Sending Delayed (Retarded) Reports

If you do not send a regular report within the predefined editing period, the system
automatically changes the report type to Retarded.
84
You can do one of the following:

• You can finish editing the report, and then build and send it. The system adds the
letters RRA to the METAR AFTN header and updates the AFTN sending time. The time
in the CODE field is the scheduled sending time of the original (normal) METAR report.
• If you want to update the data with the current automatic data, click Update first. This
updates the automatic data, but keeps the manual changes made.
A delayed (retarded) METAR can be sent until the editing time of the next METAR report
starts. If at that time the report has not been sent, the template goes into editing mode for
the new report and the old one is not sent at all.
7.3.5 Sending Corrected Reports

After sending a report, you might notice things that need to be corrected, for example,
typographic errors or missing values. In such cases, you can check the status of the report
from the Notifications pane, the STATE field, and the Time left field, and do one of the
following:
• If the report is in the Ready state (waiting in buffer for sending) and there is sufficient
time left before the official sending time, you can recall the report and send it as a
normal report.
• If the report has already been sent, you can generate and send a corrected report.
7.3.5.1 Recalling Pending Report

If you sent the report before the official sending time, the report is waiting in the buffer. In
that case, you can recall the report for corrections by doing the following:
1. Check from the Time left field if there is sufficient time to make the corrections.
If there is not enough time, the report may go to the retarded state.
2. Click Recall.
The system retrieves the report from the buffer.
3. Edit, build, and send the report as a normal report.
7.3.5.2 Correcting Sent METAR/SPECI Report

To correct a report that has actually been sent:
1. Select SPECI/COR at the top of the page.
2. To retrieve the last sent report for correction, click COR.
3. In the data fields, edit the data that needs correcting.
The system builds the report and displays the final code in the final report code field.
5. Check the report carefully. If needed, correct the data, and rebuild the report.
6. When the report is ready to be sent, select Send.
If configured, the system adds the code COR to corrected reports after the report name. If
configured, for the AFTN line, the system adds the code CCA (or CCB, CCC, and so on to the
next correction of the same report) to the AFTN headers.
85
7.3.6 Sending Automatic Reports (Optional)

If the system includes the automatic report sending functionality, you can define the system
to send reports automatically without user intervention. The system will fill in the automatic
fields, build, and send the report.
To enable the automatic sending:
1. Click the Setup tab.
2. On the Report Mode Settings page, select the Auto option under the appropriate
report type.
3. On the Default Input Settings page, select the data sources that are suitable for
automatic reports.
Starting from the next scheduled report, or the next SPECI/SPECIAL limit criteria trigger, the
system will send the report automatically. The system also adds the text AUTO automatically
in the code when applicable.
More information
‣ Report Mode Settings Page (page 76)
7.3.7 Sending SPECI Reports

For SPECI report sending, the previous general instructions generally apply. The following
provides some additional information about sending SPECI reports.
SPECI reports can be sent in the following situations:
• When the predefined weather changes occur (compared with the previous sent report),
the system informs you about it in the Notifications pane. Activate, edit, and send the
SPECI report on the SPECI/COR tab.
If needed, the SPECI triggering limits can be changed on the Setup tab.
The weather changes can be either automatic data from the sensor or, if configured in
the system, manual data entered by the user in the MANOBS tab.
• Whenever otherwise required, you can manually create a SPECI report on the SPECI/
COR tab.
If there is no valid sent METAR/SPECI report, the SPECI reports are not triggered by the
system. If in such a situation you create a SPECI manually, the system will ask you to confirm
that you want to edit SPECI. If so, select Yes.
If the METAR editing time starts when you are editing a SPECI, you can send the SPECI
report first. However, when a METAR report is published, any SPECI being edited is
cancelled.
If a SPECI is triggered when a METAR report is in the buffer waiting for the official sending
time, you can recall the METAR report for editing, update its data with the changed data,
and send the updated METAR instead of SPECI.
More information
‣ Limit Criteria Settings Page (page 78)
86
7.3.7.1 Changing SPECI/SPECIAL Triggering Limits

The default limits for automatic SPECI/SPECIAL triggering have been defined in system
configuration. However, you can change the pre-configured default limits on the Setup tab
by doing the following:
1. If not already in editing mode, click Edit in the application header.
2. Select Setup > Limit Criteria Settings.
3. On the Limit Criteria Settings page, enter the new limits in the appropriate fields.
Separate several limits with a comma (,).
4. Make sure the check boxes have been selected for all the criteria that you want to use
for triggering SPECI.
You can retrieve the latest saved limit criteria by clicking Cancel.
5. Click Apply to save the changes.

You can reset the values to the pre-configured set of limits by clicking Reset to ICAO.
More information
‣ Limit Criteria Settings Page (page 78)
7.3.8 Changing Data Sources

You can change the preconfigured data sources, or default inputs, for a specific report or for
all reports.
1. To change the source only for a specific report being edited: In the report template,
select the input from the drop-down lists.
2. To change the source for all reports:
a. If not already in editing mode, click Edit in the application header.
b. Select Setup > Default Input Settings.
c. Under the appropriate report type, select the data source from the drop-down list.
d. Click Apply.
More information
‣ Default Input Settings Page (Data Source) (page 77)
7.3.9 Changing Audio Notification Settings

You can enable and disable audio notifications and select what triggers the audio
notifications.
87
1. If not already in editing mode, click Edit in the application header.

2. Select Setup > Notification Settings.
3. On the Audio Notifications page, select Enable Audio Notifications.
4. Select the action and report types that you want to trigger the audio notification:
Create
Notification is played at the start of the editing time for the selected report types.
Published
Notification is played when the selected reports types have been published.
Retarded
Notification is played when the selected reports types become retarded.
5. Click Apply. The changes are applied to all users with the same user profile, for
example, Observer.
More information
‣ Audio Notification Settings Page (page 79)
7.3.10 Switching between Day/Night Display Mode

1. Click the day/night button in the application header once.
2. To switch back, click the button again.
More information
7.3.11 Viewing Sent METAR/SPECI Reports

The AviMet system typically stores all sent weather reports. Normally, only the sent version
of the report is stored. The reports are saved for a period of one year or more, depending on
the configuration.
In the AFTN Monitor application, you can view the report in the format it was sent to the
AFTN line. Below is an example of a sent METAR report as it appears in the AFTN Monitor.
88
---------- ---------- ---------- ---------- -----------
MGH008
GG EFHKYZYX EFVAYMYX EFKIYMYX EFJYYMYX
311127 EFHKYMYX
SAFI01 EFHK 311130
METAR EFHK 311130Z 09024KT 0100 R22/0200N +RA SCT026
05/M02Q1013=
---------- ---------- ---------- ---------- ----------
When the report has been successfully sent, it is also delivered to other workstations within
the airport. Depending on the configuration of the WeatherView screens, users logged in
with the Observer user profile may see the sent METAR report in the WeatherView
application as a separate field.
The MET REPORT and SPECIAL reports are local reports that are not sent to the AFTN line.
They can be configured to be displayed in the WeatherView application, or to be sent to
other external systems.
More information
‣ Introduction to AFTN Monitor (page 126)
7.4 Troubleshooting METAR/SPECI
Application
Table 21 Troubleshooting METAR/SPECI
There are no sensor values in the The data source site might be Check the source selection.
template. incorrectly defined.
There are slashes (///) in the The option Missing is selected Check the data source selection.
automatic data fields. from the data source list.
There may be a problem in sensor Contact system maintenance

communication. personnel.
There are no values and no slashes The CDU may be out of order. Contact system maintenance.
in the template. All fields are
empty.
89
The values entered in the MANOBS The MANOBS option is not selected Check the data source selection.
tab are not displayed in the data from the data source list.
fields.
There is a flashing red frame Invalid syntax has been used in the Check the code.
around a data field. code.
There is a flashing, colored frame The system informs you of an Read the notification and react as
around the Notifications pane, important event or action that needed.
and/or a beeping sound. should be taken. Typically,
notifications that require
immediate user action have sound
and flashing attached to them,
while other notifications may
appear only as text.
90
Chapter 8 – TAF
8. TAF
8.1 Introduction to TAF
The optional TAF application is used for creating and sending TAF reports (Terminal
Aerodrome Forecasts) to the Vaisala AviMet system, and for further use external systems, if
configured.
The TAF template is typically part of the Reports application, together with other reports,
such as METAR/SPECI.
Normal TAF reports are scheduled by the AviMet system. The TAF window is activated for
editing at the predefined intervals. Corrected and amended TAF reports can be sent
whenever necessary.
The header data is filled in automatically by the system. The report content has to be
entered manually, using the abbreviated plain language specified by ICAO. For the code
format, see WMO Publication No. 306, Manual on Codes, Volume I.1, Part A - Alphanumeric
Codes.
The TAF application can be used for creating and sending TAF reports to several airports at
the same time.
The system supports dissemination of data reported in METAR/SPECI using the IWXXM XML
schema. For more information, see Manual on the Digital Exchange of Aeronautical
Meteorological Information and Manual on System Wide Information Management (SWIM)
Concept.
8.2 TAF User Interface

The TAF user interface consists of tabs for short validity TAF (TAF FC) and long validity TAF
(TAF FT), and setup (TAF SETUP). The tabs are identical. Your system may include either
one or both of the TAF tabs.
91
Figure 45 TAF FC Tab
1 Tabs for the reports and setup

2 Coded data fields
3 Fields for MODE, STATE, and Time left before sending time
4 Final coded report field
5 The name of the user who is currently editing the template
6 Application header, including, for example, button for selecting day/night display mode
and toggling the editing mode on/off
8 Buttons for editing, building, and sending the reports
In addition, the user interface can contain the Notifications pane. The Notifications pane
can also be integrated as part of another AviMet application, for example, WeatherView.
As each AviMet system is individually configured, system-specific elements can be added

and some of the typical elements presented here can be excluded during system
configuration.
More information
‣ Operating TAF (page 96)
92
Chapter 8 – TAF
8.2.2 TAF Report Tabs

The TAF user interface consists of the following tabs:
• TAF FC tab for editing and sending short validity TAF reports.
• TAF FT tab for editing and sending long validity TAF reports.
• TAF SETUP tab for defining the default data sources.
The typical elements on the tabs are described in the following sections.
8.2.2.1 Final Coded Report Field

After building the report, the system displays the final report code in the final report field.
The final report code is a combination of the values in the coded data fields.
The report mode and state are displayed above the final report field. Also the time left
before the next routine report sending time is displayed (in minutes).
Figure 46 Final Coded Report Field with Mode, State, and Time Left Indicators
State Description
Idle The state between the previous sent report and the start of the next editing time.
However, user can enter editing mode by clicking the corresponding report
button.
Editing The editing state when user can make changes to the report before sending it.
Editing COR The editing state for corrected report.
Editing AMD The editing state for amended report.
Immediate editing Editing state indicating that the official publishing time is over. If the report is sent
from this state, it will not be placed in the buffer, but instead it is published
immediately.
Retarded Editing state indicating that the report is retarded. If the report is sent from this
state, it will not be placed in the buffer but instead it is published immediately.
When the preconfigured editing time for the next report arrives, new report
editing starts and the old retarded report cannot be sent any more.
93
State Description
Immediate idle State indicating that the official publishing time is over and report editing has not
even been started. This is not seen during normal operation, only in special cases,
for example, when the report has been canceled before the official publishing
time. If report editing is started from this state, state changes to Immediate
editing.
Ready The report is ready to be sent (for example, the user has clicked Send), but it is still
in the buffer waiting for the official sending time.
Inactive The AMD and COR buttons will be inactive in this state. One minute after report
sending time, or if there is no valid previously sent report present, the new/
modified report cannot be sent.
8.2.2.2 Buttons on TAF Report Tabs

The typical buttons on the TAF report tabs are described in the following table.
Table 23 Buttons on TAF Report Tabs
Button Description
TAF Activates the template for editing a TAF report.
AMD Activates the template for editing and sending an amended report. The system
generates the data automatically based on the previous report.
Build The system collects the codes from the data fields and builds the final report code
in the final report field.
COR Corrected: Activates the template for sending a correction to the last sent report.
Recall Recalls the pending report for editing. (Applicable when a report has been sent
before the official sending time and is waiting in the buffer for the actual sending.)
Send Sends the report to the external interface, typically the AFTN line or to the
weather displays and other internal systems. If sent before the official sending
time, the reports will first wait in a buffer for the sending time. If needed, the
pending reports can be recalled for editing during the waiting time.
Changes the display mode, which can be used depending on the lighting
conditions. The day mode is used in conditions with a lot of background light. The
Day / Night Display night mode is useful when there is not much light available, and the reflections
need to be minimized.
Prints the current screen.
Print
Toggles the editing mode on (Edit) and off (Release). When in editing mode, the
name of the editing user is displayed in the application header.
Edit / Release
94
Chapter 8 – TAF
8.2.3 TAF Notifications Pane

The Notifications pane can be displayed on the TAF report tabs. Or, it can be configured to
be displayed as part of other AviMet applications, for example, as an informative field in the
WeatherView application.
The Notifications pane shows information about important actions, warnings, and system
states. The content, type, and number of notifications depend on the system configuration.
For example, there may be a notification informing you that TAF editing time has started, or
that a TAF report has been sent.
be flashing, and a sound alarm. The colors, flashing, and sounds have been defined in system
configuration. Typically, there are separate sounds and colors for different alarm groups (for
example, notifications, warnings, and alarms). For example, alarm notifications that require
immediate user action may have a specific sound and a flashing frame attached to them,
while other notifications may appear only as text.
You can acknowledge the notifications by clicking the ACK button. Depending on system
configuration and the notification type, the acknowledging will, for example, stop the
flashing and the sound alarm, or the notification frame will disappear.
95
8.2.4 TAF Setup Tab

On the TAF SETUP page, you can change the default data sources that provide the data to
the reports. The change may be needed, for example, in sensor problem situations or when
the runway in use has been changed.
Figure 48 TAF Setup Tab
The changes are saved when you click Apply.
8.3 Operating TAF
There are following types of TAF reports:
• Normal reports are scheduled by the system, and they appear at specified intervals.
• Retarded reports: Normal reports automatically turn into Retarded (delayed) reports
after the specified editing time is over.
• Corrected reports are typically sent when typographic errors have been noticed in the
sent report.
• Amended reports are sent when the weather changes so that the sent report does not
correspond to the weather developments.
• CNL (canceled) reports are a form of amended reports that can be manually created
and sent when needed.
• NIL reports: If a TAF report has not been sent during the preconfigured waiting time,
the system automatically sends a NIL TAF report.
More information
‣ TAF User Interface (page 91)
8.3.1 Starting and Exiting Report Templates

Depending on the system configuration, the templates or the Report application either
starts automatically when you log in the Vaisala AviMet AWOS system, or you can open the
application, for example, by clicking its icon on the desktop or in the WeatherView
application.
96
Chapter 8 – TAF
CAUTION! Do not close the templates unless you have a special reason, such as system
maintenance.
8.3.2 Sending Normal TAF Reports

TAF reports are sent at regular intervals depending on local practices. When it is time to
send a normal TAF report, the TAF window is activated and the header data filled in by the
system.
The editing period depends on the system configuration. Typically, you have:
• 20 minutes to edit and send the FC forecast
• 30 minutes to edit and send the FT forecast
To send a normal TAF report during the editing time:
1. When the notification about the start of the editing time is displayed in the
Notifications pane, select ACK.
This stops any flashing and sound.
2. Open the TAF FC or TAF FT tab, if not already open.
3. Check the code in the automatic coded data fields. If needed, change the data source
from the source selection list.
4. If there are slashes (///) or incorrect values in an automatic fields, correct the value:
a. Select Edit at the top of the METAR page.
b. If you want to use the automatic data as basis, click the text field. The source
changes to MANUAL, retaining the previous text as basis.
Otherwise, select MANUAL from the source selection list.
c. Correct the value manually in the coded data field.
d. Inform the maintenance personnel, if needed.
6. If the system finds incorrect syntax, it shows a red flashing box around the data field.
You can either:
• Correct the data in the coded data fields and build the report again.
The system publishes the report for further use in external or internal systems. If configured,
the system adds AFTN line headers to the report and sends the report to the AFTN line.
If the report is sent before the official sending time, it will be pending in a buffer until the
sending time. During that time the report can be recalled for editing.
97
8.3.2.1 Sending Delayed TAF Reports

If you fail to edit and send the TAF report during the specified editing period, you can
continue editing the report and send it as a delayed TAF report. The system automatically
changes the report type to RRA (delayed).
8.3.2.2 NIL TAF Reports

If a TAF report has not been sent during the preconfigured waiting time, the system
automatically sends a NIL TAF report.
8.3.3 Sending Corrected Reports

After sending a report, you might notice things that need to be corrected, for example,
typographic errors or missing values. In such cases, you can check the status of the report
from the Notifications pane, the STATE field, and the Time left field, and do one of the
following:
• If the report is in the Ready state (waiting in buffer for sending) and there is sufficient
time left before the official sending time, you can recall the report and send it as a
normal report.
• If the report has already been sent, you can generate and send a corrected report.
8.3.3.1 Recalling Pending Report

If you sent the report before the official sending time, the report is waiting in the buffer. In
that case, you can recall the report for corrections by doing the following:
1. Check from the Time left field if there is sufficient time to make the corrections.
If there is not enough time, the report may go to the retarded state.
2. Click Recall.
The system retrieves the report from the buffer.
3. Edit, build, and send the report as a normal report.
8.3.3.2 Correcting Sent TAF Report

To correct a report that has actually been sent, you can send either of the following:
• A corrected report when you notice a typographic error in the report that has been
sent.
• An amended report when you notice that the report that has been sent does not
correspond with weather developments (for example, if there is an unexpected change
in weather).
To correct or amend a sent report:
1. Click the TAF FC or TAF FT tab.
2. Open the report for editing.
• To retrieve the last sent report for correction, click COR or AMD.
• To start with empty fields, select MANUAL from the source selection list.
3. In the data fields, edit the data that needs correcting.
98
Chapter 8 – TAF

If configured, the system adds the code COR to corrected reports after the report name. If
configured, for the AFTN line, the system adds the code CCA (or CCB, CCC, and so on to the
next correction of the same report) to the AFTN headers.
If configured, the system adds the AMD code to amended reports after the report name. If
configured, for the AFTN line, the system adds the code AAA (or AAB, AAC, and so on to the
next amendment of the same report) to the AFTN headers.

in editing mode.
8.3.5 Canceling Sent TAF Report

Another type of amended TAF reports is canceled TAF. To cancel a sent TAF report:
1. Select the TAF FC or TAF FT tab, depending on the report type you want to cancel.
2. Click AMD.
3. If needed, edit the validity period of the current TAF report in the HEADER field.
4. Type the validity time of the TAF to be canceled and the text CNL in the final coded
report field, for example, 1606/1624 CNL.
If configured, the system adds the AMD code to amended reports after the report name. If
configured, for the AFTN line, the system adds the code AAA (or AAB, AAC, and so on to the
next amendment of the same report) to the AFTN headers.
8.3.6 Viewing Sent Reports

Sent reports are typically stored in the ASCII Log View application.
You can also view the report in its final format in the AFTN Monitor application.
More information
‣ Introduction to ASCII Log View (page 147)
99
8.4 Troubleshooting TAF
Table 24 Troubleshooting TAF
There is a flashing red frame Invalid syntax has been used in the Check the code.
around a data field. code.
The HEADER information is There is a system problem. Contact maintenance.

missing.
There is a flashing, colored frame The system informs you of an Read the notification and react as
around the Notifications pane, important event or action that needed.
and/or a beeping sound. should be taken. Typically,
notifications that require
immediate user action have sound
and flashing attached to them,
while other notifications may
appear only as text.
The notification of a scheduled TAF The WeatherView window may Open the WeatherView window.
is not displayed/sounded at the have been closed.
editing time.
100
Chapter 9 – SIGMET
9. SIGMET
9.1 Introduction to SIGMET
The optional SIGMET application is used for creating and sending SIGMET reports to the
Vaisala AviMet system and if configured, to external systems, such as the AFTN line.
SIGMET reports are not scheduled by the system. They can be sent whenever there is an
occurrence of significant weather phenomena that may affect the safety of aircraft
operations, as specified by ICAO in Meteorological Service for International Air Navigation.
Annex 3.
SIGMET header is automatically generated by the AviMet system. The sequence number and
validity period can be generated automatically by the AviMet system. The area and message
body elements can have predefined texts. The report content must follow the abbreviated
plain language specified by ICAO. For the code format, see WMO Publication No. 306,
Manual on Codes, Volume I.1, Part A - Alphanumeric Codes.
9.2 SIGMET User Interface

The SIGMET user interface consists of the SIGMET window. The following sections describe
the elements of the window briefly.
Figure 49 SIGMET User Interface
1 Data fields for header, sequence, validity, area, and message

2 Fields for mode and state
3 Final report field
5 Buttons for selecting report type and for editing, building, and sending the report
101
More information
‣ Operating SIGMET (page 104)
9.2.1 SIGMET Data Fields and Source Selection

There are separate data fields for the SIGMET header and other parts of the SIGMET
message.
Before filling in the data fields, the report type has to be selected using the buttons at the
bottom of the template. Depending on the selection, the system adds the report-specific
codes in the AFTN message, see the following table.
Table 25 SIGMET Report Type Buttons
Button Report Type Type in AFTN Code
TS SIGMET Thunderstorm SIGMET WS
VA SIGMET Volcanic Ash SIGMET WV
TC SIGMET Tropical Cyclone SIGMET WC
You fill in data fields manually, using the abbreviated plain language specified by ICAO.
When building the report, the system uses the data to create the final report code.
Table 26 SIGMET Data Fields
Field Description
HEADER Location indicator and report type as specified by ICAO, for example, YUDD
SIGMET. If configured, preconfigured text may be provided.
SEQUENCE Report sequence number as specified by ICAO, for example, 2. If configured, the
sequence number can be automatically added by the system. Depending on the
configuration, the automatic sequence number can be reset, for example, daily or
annually.
VALID Validity time as specified by ICAO, including start and end time, for example,
VALID 081200/091200. (The format is DDHHmm/DDHHmm, where DD is the day
of the month (for example, 08), HH is the hour, (for example, 12), and mm is the
minutes (for example, 00).
If configured, preconfigured text may be provided.
AREA Area as specified by ICAO for example, YUSO. If configured, preconfigured text
may be provided.
MESSAGE SIGMET message as specified by ICAO.
If previous reports are available, you can use the previous sent report as basis for the new
report by choosing PREV_REPORT from the lists.
102
Table 27 SIGMET Data Source Selection Options
Source Description
MANUAL User enters data manually in the data field, or data retrieved from the previous
report is being edited.
PREV_REPORT System retrieves automatically the data from the last sent report and displays it in
the data fields.
NEXT_REPORT System uses a predefined, system-generated message option.
When building the report(s), the system collects the codes from the data fields and builds
the final report code in the final report field.
Final Report Field

The final report code is a combination of the values in the coded data fields. If editing is
needed, do it in the data fields and build the report again.
Figure 50 Final Coded Report Field with Mode and State Fields
The report mode and state are displayed above the final report field. The mode is always
manual and the following state options are available.
Example State Text Description
Idle_TS No report is being edited, shows the type of the previous sent report, in
this case TS.
Editing_TS Shows which report type is being edited, in this case, TS.
Editing_VA_from_TS Shows last sent report used as basis, in this case TS, and the report type
being created, in this case VA.
9.2.2 SIGMET Template Buttons
Table 29 Typical SIGMET Template Buttons
Button Description
TS SIGMET Activates the template for creating Thunderstorm SIGMET.
VA SIGMET Activates the template for creating Volcanic Ash SIGMET.
103
Button Description
TC SIGMET Activates the template for creating Tropical Cyclone SIGMET.
Build The system collects the codes from the data fields and builds the final report code
in the final report field.
Send Sends the report to the external interface, typically the AFTN line or to the
weather displays and other internal systems.
More information
‣ SIGMET Data Fields and Source Selection (page 102)
9.3 Operating SIGMET
More information
‣ SIGMET User Interface (page 101)
9.3.1 Sending SIGMET Reports

You can create SIGMET reports whenever there is an occurrence of significant weather
phenomena.
1. In the SIGMET template, select the report type by clicking one of the buttons at the
bottom of the template:
• Thunderstorm: TS SIGMET
• Volcanic Ash: TC SIGMET
• Tropical Cyclone: TC SIGMET
This selection determines the code in the AFTN header.
2. In the data fields, enter the header, sequence, validity time and area as specified by
ICAO.
• If configured, the sequence number can be automatically added by the system.
• If configured, preconfigured text fields may be provided for the other fields.
3. Enter the message as specified by ICAO.
4. If you want to use the previously sent report as the basis for the editing, select
PREV_REPORT from the source selection list. To edit the data from the previous report,
click the text field.
104
More information
‣ SIGMET Data Fields and Source Selection (page 102)

in editing mode.

More information
9.4 Troubleshooting SIGMET
Table 30 Troubleshooting SIGMET
You cannot edit the data fields. You may not have not activated the To activate the fields, select Edit at
report fields. the top of the report page and the
correct SIGMET button in the
report template, for example,
TC SIGMET.
The header is not automatically There is a system or configuration Contact maintenance.

generated. problem.
105
10. GAMET
10.1 Introduction to GAMET
The optional GAMET application is used for creating and sending GAMET reports for further
use in internal or external systems, as configured. GAMET reports are area forecasts for low-
level flights.
Normal GAMET reports are scheduled by the AviMet system and the GAMET window
appears for editing and sending the report at the predefined intervals.
The report content has to be entered manually, using the abbreviated plain language
specified by ICAO. For the code format, see WMO Publication No. 306, Manual on Codes,
Volume I.1, Part A - Alphanumeric Codes. When configured, preconfigured text fields can be
provided for section 1 and 2.
10.2 GAMET User Interface

The GAMET user interface consists of the menus and the GAMET window. The following
sections describe these elements briefly.
More information
‣ Operating GAMET (page 109)
106
Chapter 10 – GAMET
10.2.1 GAMET Window
Figure 51 GAMET Window
Table 31 GAMET Window Elements
Element Description
Date Date of origin of report, filled in automatically by the system.
Time Time of origin of report. The time is updated during the editing period. Thus, the
time that appears in the abbreviated header of sent AFTN message is the time
when the report was actually sent, not when the system generated the report.
Location indicator The ICAO location indicator of the ATS (Air Traffic Services unit) serving the FIR
(Flight Information Region) to which the forecast refers, filled in automatically by
the system.
Valid begin The starting date and time of the validity period of the report, a manual data field
which must be filled in by the user. The format is DDHHmm, where DD is the day of
the month (for example, 26), HH is the hour, (for example, 12), and mm is the
Valid end The ending date and time of the validity period of the report, a manual data field
which must be filled in by the user. The format is DDHHmm, where DD is the day of
the month (for example, 26), HH is the hour, (for example, 18), and mm is the
Office (MWO) The location indicator of the MWO (Meteorological Watch Office) originating the
message, automatically filled in by the system.
107
Element Description
FIR/CTA The name of the FIR (Flight Information Region), for which the report is issued,
automatically filled in by the system.
Sub-area Sub area of the FIR.
SECN 1 Enter the section 1 part of the GAMET report text manually using the abbreviated
plain language specified by ICAO. When configured, preconfigured text fields may
be provided, for example, ICE:.
SECN 2 Enter the section 2 part of the GAMET report text manually using the abbreviated
plain language specified by ICAO. When configured, preconfigured text fields may
be provided, for example, PSYS:.
Coded Message Shows the complete coded GAMET message starting with the identification data
that the system has formed based on the data in other fields.
Previous Displays the previous GAMET report for editing.
New Displays a new GAMET template.
Send Sends the report to the system and to the AFTN line, if configured.
10.2.2 GAMET Menu Bar

The GAMET window functions can be selected from the menu bar. The typical menus and
menu commands are presented in the following tables.
Table 32 GAMET: File Menu
Command Description
New Displays a new GAMET template.
Previous Displays the previous GAMET report for editing.
Send Sends the report to the system and to the AFTN line, if configured.
Table 33 GAMET: Edit Menu
Command Description
Undo Cancels the last editing action.
Cut Removes the selected text.
Copy Copies the selected text.
Paste Adds the copied or cut text at the cursor location.
Table 34 GAMET: Help Menu
Command Description
About GAMET Displays software version and copyright information.
108
Chapter 10 – GAMET
10.3 Operating GAMET
GAMET reports are scheduled by the system, and they appear at predefined intervals,
typically every 6 hours.
More information
‣ GAMET User Interface (page 106)
10.3.1 Sending GAMET Reports

GAMET reports are sent at regular intervals depending on local practices. When it is time to
send a normal GAMET report, the GAMET window is displayed with the automatic data
ready in the report identification data fields.
GAMET reports are typically sent every 6 hours. Typically, you have 20 minutes to edit and
send the report. The exact editing period depends on the system configuration.
To send a GAMET report, do the following:
1. In the GAMET window, click New.
The system generates the report identification data automatically. If you want to use
the previously sent report as the basis for the editing, click Previous.
2. If you want to change the report validity period, edit the Valid begin and Valid end
fields manually.
The format is DDHHmm, where DD is the day of the month (for example, 26), HH is the
hour, (for example, 12), and mm is the minutes (for example, 00).
3. In the SECN 1 and SECN 2 fields, enter the section 1 and 2 of the GAMET forecast using
the abbreviated plain language specified by ICAO.
• If configured, preconfigured text fields may be provided, for example, ICE:.
• The keywords SECN1 and SECN2 are added automatically by the system to the final
report.
• You can use the editing functions in the Edit menu.
• The minimum text length for each section is 12 characters. The system checks the
length of the report automatically. If the report is shorter than the minimum length,
the report cannot be sent.
4. Edit the sub-area of the FIR in the Sub-area field, if needed.
If you fail to edit and send the GAMET report during the specified editing period, you can
continue editing the report and send it as a delayed GAMET report. The system
automatically changes the report type to RRA (delayed).

109
More information
10.4 Troubleshooting GAMET
Table 35 Troubleshooting GAMET
There is no report identification There is a serious system problem. Contact maintenance.

data in the data fields.
You cannot enter the report in the The basis for the report has not Click New or Previous to be able to
report text fields. The field been selected. enter text.
background is gray.
You have written the report text The minimum length of the report Enter a report that is at least
and want to send it, but the Send text is 12 characters for each 12 characters long.
button is not active. section.
110
Chapter 11 – AIRMET
11. AIRMET
11.1 Introduction to AIRMET
The optional AIRMET application is used for creating and sending AIRMET reports for
further use in internal or external systems, as configured. AIRMET reports are low-level
reports that describe the occurrence or expected occurrence of en-route weather
phenomena which have not been included in the GAMET report.
AIRMET header is automatically generated by the AviMet system. The sequence number and
validity period can be generated automatically by the AviMet system and area and message
body elements can have predefined texts. The report content must follow the abbreviated
plain language specified by ICAO. For the code format, see WMO Publication No. 306,
Manual on Codes, Volume I.1, Part A - Alphanumeric Codes.
11.2 AIRMET User Interface

The AIRMET user interface consists of the AIRMET window. The following sections describe
these elements briefly.
Figure 52 AIRMET User Interface
1 Data fields for header, sequence, validity, area, and message

5 Buttons for editing, building, and sending the report
111
More information
‣ Operating AIRMET (page 113)
11.2.1 AIRMET Data Fields and Source Selection

There are separate data fields for the AIRMET header and other parts of the AIRMET
message.
Table 36 AIRMET Data Fields
Field Description
HEADER Location indicator and report type as specified by ICAO, for example, YUDD
AIRMET.
SEQUENCE Report sequence number as specified by ICAO, for example, 2.
VALID 081200/091200. The format is DDHHmm/DDHHmm, where DD is the day
AREA Area as specified by ICAO for example, YUSO.
MESSAGE AIRMET message as specified by ICAO.
report by choosing PREV_REPORT from the lists. You can also use predefined, system-
generated options.
Table 37 AIRMET Data Source Selection Options
Source Description
the data fields.
NEXT_REPORT_1, System uses a predefined, system-generated message option, for example, YUCC
NEXT_REPORT_2 AMSWELL FIR or YUCC SHANLON FIR/2
Final Report Field

needed, you can do it in the data fields and build the report again.
112
The report mode and state are displayed above the final report field. The mode is always
manual and the following state options are available.
Table 38 State Options
Example State Text Description
Idle No report is being edited or ready to be sent.
Editing User has triggered the report and edits the contents.
Edited User has finished editing the contents and has built the report. The report
is ready to be sent.
11.2.2 AIRMET Template Buttons
Table 39 AIRMET Template Buttons
Button Description
AIRMET Activates the template for editing.
Build Builds and checks the validity of the report.
Cancel Cancels the report being edited before sending it.
Send Will be activated after building the report. Sends the report to the configured
external interfaces.
11.3 Operating AIRMET
More information
‣ AIRMET User Interface (page 111)
11.3.1 Sending AIRMET Reports

You can create AIRMET reports whenever there is an occurrence of significant weather
phenomena.
1. Open the AIRMET template.
2. At the top of the page, select Edit.
3. In the AIRMET template, select the AIRMET button to activate the fields. The system
generates the header data automatically.
4. Select the source for each data field:
• If you want to use the previously sent AIRMET report as the basis for the editing,
select PREV_REPORT from the list.
• If you want to use predefined, system-generated message options, select one of the
NEXT_REPORT options.
• If you want to enter data manually, select MANUAL.
113
5. Edit the data fields, if needed:

SEQUENCE
The sequence number of the report, as specified by ICAO, for example, 1.
VALID
The validity period of the report in the following format: DDHHmm, where DD is the
day of the month (for example, 26), HH is the hour, (for example, 12), and mm is
the minutes (for example, 00).
AREA
Area as specified by ICAO for example, YUSO.
MESSAGE
The AIRMET report text using the abbreviated plain language specified by ICAO.
7. If the system finds incorrect syntax, it shows a red flashing box around the field. You
can either:
11.3.2 Canceling AIRMET Report

1. Open the AIRMET template.
2. To show the content of the last sent report, select PREV_REPORT from the source
selection list.
3. In the Message field, type the text of the cancelled report as specified by ICAO and
national regulations and practices.
For example, CNL AIRMET 2 101200/101600, where the times indicated are the
validity period of the canceled report.

114
More information
11.4 Troubleshooting AIRMET
Table 40 Troubleshooting AIRMET
You cannot edit the data fields. You may not have not activated the To activate the fields, select Edit at
report fields. the top of the report page and
select the AIRMET button in the
report template.
The header is not automatically There is a system or configuration Contact maintenance.

generated. problem.
115
12. AD WRNG
12.1 Introduction to AD WRNG Template
The optional AD WRNG template is used for creating and sending Aerodrome Warning
reports to the system, and if configured, to external systems, such as the AFTN line. The
warnings are issued in accordance with local arrangements.
Aerodrome Warning reports are not scheduled by the system. They can be sent whenever
there is a need to inform, for example, the operators or aerodrome services about such
meteorological conditions that would adversely affect aircraft on the ground, including
parked aircraft, and the aerodrome facilities and services.
The application does not include automatic weather data, other than report identification.
Volume I.1, Part A - Alphanumeric Codes. If configured, the sequence number can be
automatically added by the system.
12.2 AD WRNG Template User Interface

The user interface consists of the AD WRNG template. The following sections describe the
elements of the template briefly.
116
Chapter 12 – AD WRNG
Figure 53 AD WRNG Template
1 Data fields for header, sequence, validity, and message

5 Buttons for activating the fields and for editing, building, and sending the report
More information
‣ Operating AD WRNG Template (page 118)
12.2.2 AD WRNG Data Fields and Source Selection

Table 41 AD WRNG Data Fields
Field Description
HEADER Location indicator of the aerodrome and report type as specified by ICAO, for
example, YUDD AD WRNG.
SEQUENCE Report sequence number as specified by ICAO, for example, 2. If configured, the
sequence number can be automatically added by the system. Depending on the
configuration, the automatic sequence number is reset daily or annually.
117
Field Description
MESSAGE The aerodrome warning message as specified by ICAO.
report by choosing PREV_REPORT from the data source selection lists.
Table 42 AD WRNG Data Source Selection Options
Source Description
NEXT_REPORT System uses a predefined, system-generated option.
the data fields. To edit the data, click the text field. The data source selection
changes to MANUAL.

12.2.4 AD WRNG Template Buttons
Table 43 AD WRNG Template Buttons
Button Description
AD WRNG Activates the template for editing.
12.3 Operating AD WRNG Template

More information
‣ AD WRNG Template User Interface (page 116)
118
Chapter 12 – AD WRNG
12.3.1 Sending Aerodrome Warning Reports

You can create Aerodrome Warning reports whenever there is an occurrence of significant
weather phenomena.
1. Open the AD WRNG template.
2. Select Edit at the top of the page.
3. In the AD WRNG view, click AD WRNG to activate the fields.
The system generates the header data automatically.
If you want to use the previously sent Aerodrome Warning as the basis for the editing,
select PREV_REPORT from the list. Click the text field to edit the content.
4. Enter the sequence number of the report, as specified by ICAO, for example, 1. If
configured, the sequence number can be automatically added by the system.
5. In the Valid field, enter the validity period of the report.
6. In the Message field, enter the Aerodrome Warning report text using the abbreviated
plain language specified by ICAO.
You can either:
12.3.2 Canceling AD WRNG Report

1. Open and activate the template as described in Sending Aerodrome Warning Reports
(page 119).
selection list.
For example, CNL AD WRNG 2 101200/101600, where the times indicated are the
119

More information
12.4 Troubleshooting AD WRNG Template

Table 44 Troubleshooting AD WRNG Template
You cannot edit the fields. The template is not in editing Select Edit at the top of the page.
mode.
The Header information is missing. There is a system problem. Contact maintenance.
You have written the report text You have to build the report first. Select Build.
and want to send it, but the Send
button is not active.
There is a flashing red frame Invalid syntax has been used in the Check and correct the code, then
around a data field. code. build the report again.
120
Chapter 13 – WS WRNG
13. WS WRNG
13.1 Introduction to WS WRNG Template
The optional WS WRNG application is used for creating and sending Windshear Warning
reports to the system, and if configured, to external systems such as the AFTN line. The
warnings are issued in accordance with local arrangements.
Windshear Warning reports are not scheduled by the system. They can be sent whenever
there is a need to inform about observed or expected windshear which could adversely
affect aircraft on the approach or take-off path, or during circling approach between runway
level and 500 meters above that level, and aircraft on the runway during the landing roll or
take-off run.
The application does not include automatic weather data, other than report identification.
Volume I.1, Part A - Alphanumeric Codes.
13.2 WS WRNG User Interface

The user interface consists of the WS WRNG template. The following sections describe the
elements of the window briefly.
121
Figure 54 WS WRNG Template Window
1 Data fields for header, sequence, validity, and message

5 Buttons for selecting report type and for editing, building, and sending the report
More information
‣ Operating WS WRNG Template (page 123)
13.2.1 WS WRNG Data Fields and Source Selection

Table 45 WS WRNG Data Fields
Field Description
HEADER Location indicator and report type as specified by ICAO, for example, YUDO WS
WRNG.
SEQUENCE Report sequence number as specified by ICAO, for example, 2.
MESSAGE The Windshear Warning Message as specified by ICAO.
122
Table 46 WS WRNG Data Source Selection Options
Source Description
MANUAL User enters data manually in the data field.
the data fields. To edit the data, click the text field. The data source selection
changes to MANUAL.

13.2.3 WS WRNG Template Buttons
Table 47 WS WRNG Template Buttons
Button Description
WS WRNG Activates the template for editing.
13.3 Operating WS WRNG Template

More information
‣ WS WRNG User Interface (page 121)
13.3.1 Sending Windshear Warning Reports

You can create Windshear Warning reports whenever there is a need for informing about
observed or expected windshear.
To send a Windshear Warning report:
1. Open the WS WRNG template.
2. Select Edit at the top of the page.
3. In the WS WRNG view, select WS WRNG to activate the fields.
The system generates the header data automatically.
If you want to use the previously sent Windshear Warning as the basis for the editing,
select PREV_REPORT from the list. Click the text field to edit the content.
123
4. Enter the sequence number of the report, as specified by ICAO, for example, 1.
5. In the Valid field, enter the validity period of the report.
6. In the Message field, enter the Windshear Warning report text using the abbreviated
plain language specified by ICAO.
You can either:
13.3.2 Canceling WS WRNG Report

1. Open and activate the template as described in Sending Windshear Warning Reports
(page 123).
selection list.
For example, CNL WS WRNG 2 101200/101600, where the times indicated are the

More information
124
13.4 Troubleshooting WS WRNG
Table 48 Troubleshooting WS WRNG Template
You cannot edit the fields. The template is not in editing Select Edit at the top of the page.
mode.
The PREV_REPORT option is Select the MANUAL option or click

selected from the source selection the text field to edit the content
list. from the previous report.
The Header information is missing. There is a system problem. Contact maintenance.
You have written the report text You have to build the report first. Select Build.
and want to send it, but the Send
button is not active.
There is a flashing red frame Invalid syntax has been used in the Check and correct the code, then
around a data field. code. build the report again.
125
14. AFTN Monitor
14.1 Introduction to AFTN Monitor
With the AFTN Monitor application, all reports that have been sent to the AFTN line can be
viewed in the format they were sent. The report texts can be copied to a separate file and
used in other Vaisala AviMet applications, for example, when sending corrections to old
METAR reports.
Depending on the configuration, AFTN Monitor shows messages in ITA‑2 or IA5 formats as
specified by ICAO in Aeronautical Telecommunications, Annex 10, Vol. II (Communication
procedures).
14.2 AFTN Monitor User Interface

The AFTN Monitor user interface consists of the AFTN Monitor window, menus, and the
toolbar. These elements are briefly explained in the following sections.
More information
‣ Operating AFTN Monitor (page 130)
14.2.1 AFTN Monitor Window

When you open AFTN Monitor and select View > Outbound Messages, or click the Sent
Messages button, the following window is displayed.
Figure 55 AFTN Monitor Window
126
Chapter 14 – AFTN Monitor
The reports that have been sent from the airport to the AFTN line are displayed in the
window. The system can store 1000 data lines, which is approximately 50 weather reports.
14.2.2 AFTN Manager Window

Clicking the button on the AFTN Monitor toolbar opens the AFTN Manager window. You
can use the window for changing the AFTN sequence number (1-999). The AFTN sequence
number resets to 1 at midnight.
Figure 56 AFTN Manager Window
Table 49 AFTN Manager Data Fields
Data Field Description
Used AFTN Sequence Number The sequence number of the last sent weather report.
Next AFTN Sequence Number The sequence number of the next weather report.
14.2.3 AFTN Monitor Menu Bar

The AFTN Monitor functions can be selected from the menu bar. Typical menus and menu
commands are presented in the following tables.
Table 50 AFTN Monitor: File Menu
Command Description
Print Setup Opens a window for changing the printer and paper settings.
Exit Exits the AFTN Monitor application.
127
Table 51 AFTN Monitor: Edit Menu
Command Description
Undo Cancels the last editing action.
Cut Removes the selected text.
Copy Copies the selected text.
Paste Adds the copied or cut text at the cursor location.
Table 52 AFTN Monitor: View Menu
Command Description
Toolbar Shows/Hides the AFTN Monitor toolbar.
Status bar Shows/Hides the AFTN Monitor status bar.
Inbound Messages If configured, displays messages with predefined addresses received from the
AFTN line.
Outbound Messages Displays messages sent to the AFTN line from AviMet system.
Table 53 AFTN Monitor: Window Menu
Command Description
Tile Horizontally Shows/Hides the AFTN Monitor toolbar.
Tile Vertically Shows/Hides the AFTN Monitor status bar.
Arrange icons Arranges icons of minimized windows.
Table 54 AFTN Monitor: Help Menu
Command Description
About AFTN Monitor Displays software version and copyright information.
14.2.4 AFTN Monitor Toolbar
Table 55 AFTN Monitor Toolbar
Button Name and Description
Received messages shows messages received from the AFTN line.
Sent Messages shows messages sent to the AFTN line.
AFTN Addressee Manager opens the AFTN Addressee Manager application for setting
the addressee part of the AFTN message and specifying which report types are sent to
which addressee.
128
AFTN Manager opens the AFTN Manager window for changing the AFTN sequence
number.
Print prints the current display.
More information
‣ Introduction to AFTN Addressee Manager (page 132)
14.2.5 AFTN Monitor Status Bar

The status bar displays information on the current state of AFTN Monitor. It also shows
context-sensitive help texts on the AFTN Monitor buttons. When you move the mouse over a
button, a short description of the button is shown on the status bar.
14.3 Outbound (Sent) Messages

Depending on the configuration, AFTN Monitor shows messages in ITA‑2 or IA5 formats as
specified by ICAO in Aeronautical Telecommunications, Annex 10, Vol. II (Communication
procedures).
AFTN messages consist of two parts:
• AFTN header that contains the addresses the report is sent to and the message
indicator.
• The actual report code that begins with a plain language message indicator (for
example, METAR).
The following presents an example of a METAR report in the IA5 format.
---------- ---------- ---------- ---------- -----------
MGH008
GG EFHKYZYX EFVAYMYX EFKIYMYX EFJYYMYX
311127 EFHKYMYX
SAFI01 EFHK 311130
METAR EFHK 311130Z 09024KT 0100 R22/0200N +RA SCT026
05/M02Q1013=
---------- ---------- ---------- ---------- -----------
129
14.4 Operating AFTN Monitor

To start AFTN Monitor, click the AFTN button on the Application Toolbar.
To exit AFTN Monitor, select File > Exit.
More information
‣ AFTN Monitor User Interface (page 126)
14.4.1 Viewing Outbound (Sent) Messages

To view the reports that have been sent from the AviMet system to the AFTN line:
1. Open the AFTN Monitor application.
2. Select View > Outbound Messages.
The messages sent to the AFTN line are displayed in the Outbound Messages window.
3. You can copy the messages to be used in other applications by selecting Edit > Copy.
4. When you have finished viewing the messages, exit AFTN Monitor by selecting File >
Exit.
14.4.2 Changing AFTN Sequence Number

1. Click the AFTN Manager button on the AFTN Monitor toolbar.
2. In the AFTN Manager window, enter the new number in the Next AFTN Sequence
Number field.
3. Click Update.
14.4.3 Using AFTN Addressee Manager

To set the addressee part of the AFTN message or to specify which report types are sent to
a specific addressee, open the separate AFTN Addressee Manager application:
1. Click the AFTN Addressee Manager button on the AFTN Monitor toolbar.
More information
‣ Introduction to AFTN Addressee Manager (page 132)
130
14.5 Troubleshooting AFTN Monitor

Table 56 Troubleshooting AFTN Monitor
You cannot find a report that was The system can store 1000 data See if the report is in the reports
sent earlier. lines, which means approximately files in the ASCII Log View
50 weather reports. application.
More information
131
15. AFTN Addressee Manager

15.1 Introduction to AFTN Addressee
Manager
The AFTN Addressee Manager application is a tool for setting the addressee part of the
AFTN message. It can also be used to specify which report types are sent to a specific
addressee. For example, the METAR reports sent every hour and the ones sent every half
hour can be defined to be sent to separate AFTN addressees.
132
Chapter 15 – AFTN Addressee Manager
15.2 AFTN Addressee Manager User

Interface
The AFTN Addressee Manager user interface consists of the AFTN Addressee Manager
window.
Figure 57 AFTN Addressee Manager Window
The elements in the AFTN Addressee Manager window are described in the following
sections.
More information
‣ Operating AFTN Addressee Manager (page 135)
133
15.2.1 AFTN Interfaces Frame

Your system may include more than one AFTN interfaces that are used for sending the
messages to the AFTN line. The available interfaces are listed in the AFTN Interfaces frame.
Table 57 AFTN Addressee Manager Window: AFTN Interfaces Frame
Element Description
Interface Shows the available AFTN interfaces to which messages can be sent.
15.2.2 AFTN Interface Frame

The AFTN addressees, that is, the destination of the messages, can be grouped under
addressee groups. Separate AFTN addressee groups can be defined for each AFTN
interface. The AFTN Interface frame contains the AFTN addressee groups defined for the
interface.
Table 58 AFTN Addressee Manager Window: AFTN Interface Frame
Element Description
Addressee Groups Displays the available addressee groups defined for the selected AFTN interface.
Add Opens a window for adding a new AFTN addressee group for the selected AFTN
interface.
Edit Opens a window for editing the name of the selected AFTN addressee group.
Remove Removes the selected AFTN addressee group.
15.2.3 Addressee Group Frame

The addressees that belong into an addressee group are displayed in the Addressee Group
frame. The addressees, the address indicators that define the destination of the message,
have to be defined as instructed in ICAO Annex 10, Volume II.
Table 59 AFTN Addressee Manager Window: Addressee Group Frame
Element Description
Addressees Displays the available addressees defined for the selected AFTN addressee group.
Add Opens a window for adding a new AFTN addressee for the selected addressee
group.
Edit Opens a window for editing the name of the selected addressee.
Remove Removes the selected addressee.
More information
‣ Adding New Addressee Groups (page 135)
134
15.2.4 Addressee Frame
In the Addressee frame, you can select which message types are sent to the selected
addressees.
Table 60 AFTN Addressee Manager Window: Addressee Frame
Element Description
Message types Displays the available message types that can be selected to be sent to the
selected addressee.
Select all Selects all the available message types to be sent to the selected addressee.
Unselect all Deselects all message types.
15.2.5 AFTN Addressee Manager Buttons
Table 61 AFTN Addressee Manager Window: Buttons
Element Description
Apply Applies the made selections.
Close Exits the AFTN Addressee Manager application without saving the changes.
15.3 Operating AFTN Addressee Manager

You can use the AFTN Addressee Manager application for defining the AFTN addressees for
different message types. You can also add, edit, or delete the AFTN addressees and
addressee groups.
More information
‣ AFTN Addressee Manager User Interface (page 133)
15.3.1 Starting and Exiting AFTN Addressee Manager

To start AFTN Addressee Manager, click the AFTN Addressee Manager button on the
AFTN Monitor toolbar.
To exit AFTN Addressee Manager and save the changes, click Apply.
To exit AFTN Addressee Manager without saving the changes, click Close.
15.3.2 Adding New Addressee Groups

1. If your system contains several AFTN interfaces, select the correct interface in the
AFTN Interfaces frame.
2. In the AFTN Interface frame, click Add.
135
3. In the Add AFTN addressee group name window, type the name of the new addressee
group. Do not use special characters in the names.
4. Click OK.
The new group appears in the list.
5. Click Apply, or continue with adding new addressees. For instructions, see the
following sections.
15.3.3 Adding New Addressees

An AFTN addressee contains the location, organization, and division indicator, as defined by
ICAO Annex 10, Volume II. Multiple addressees can be used in a single message.
All addressees belong to an addressee group.
1. In the AFTN Interface frame, select the addressee group in which you want to add the
addressee.
The addressees included in that group are displayed in the Addressee Group frame.
If you want the new addressee to make a group of its own, start by adding a new
addressee group first.
2. In the Addressee Group frame, click Add.

3. In the Add AFTN addressee name window, type the new addressee name.
Follow the instructions in ICAO Annex 10, Volume II. The addressee can be, for example,
in the following format: LGATYMYF, which consists of the following indicators:
• Four-letter location indicator of the place of destination, in this case LGAT.
• Three-letter indicator of the organization or function that is being addressed, in this
case YMY for Meteorological Office.
• One-letter indicator of the department/function within the organization, in the
example, F for section F.
4. In the Add AFTN addressee name window, click OK.
5. Click Apply or continue with selecting the message types in the Addressee frame.
More information
‣ Adding New Addressee Groups (page 135)
‣ Selecting Message Types Sent to the Addressees (page 136)
15.3.4 Selecting Message Types Sent to the Addressees

For each addressee, you can define which message types are sent to the addressee:
1. Select the addressee group and the addressee in the Interface and Addressee Group
frames. See previous sections for instructions.
136
2. In the Addressee frame, select the check boxes next to the message types. You can also
select all message types by clicking Select all.
The message types whose check box is selected will be sent to the selected addressee.
The reports will be sent to the addressee only if the generation of the report type is
included in the system configuration.
3. Click Apply.
15.3.5 Editing Addressee Groups

1. In the Interface frame, select the addressee group that you want to edit.
2. Click Edit.
3. In the Edit AFTN addressee group name window, enter the new name.
4. Click Apply.
15.4 Troubleshooting AFTN Addressee

Manager
Table 62 Troubleshooting AFTN Addressee Manager
Problem Description Solution
A message type is missing from The message type has not been Check the system configuration.
the window. configured in the system.
All the available addressees in an Another addressee group might be Select the appropriate addressee
addressee group are not displayed selected. The Addressees list group from the Addressee Groups
in the Addressees list. contains the addressees of the list.
group currently selected in the
Addressee Groups list.
137
16. AMHS Monitor
16.1 Introduction to AMHS Monitor
The AviMet AMHS service creates report messages in the message format that the ATS
Message Handling System (AMHS) specifies, delivers the messages to an AMHS Server using
P3 protocol, and receives delivery reports and incoming messages from the AMHS server.
The AMHS Monitor application displays the latest reports sent to and received from the
AMHS server and the status of the server and connection. AMHS Monitor is typically part of
the Reports application.
16.2 AMHS Monitor User Interface

The AMHS Monitor application displays the status of the connection to the AMHS server, the
status of the AMHS server, the last sent and received messages to and from the AMHS
server, and the report from the AMHS server about delivering the messages further.
Figure 58 Example AMHS Monitor Window
138
Chapter 16 – AMHS Monitor
The following connection status information is typically displayed in the AMHS Monitor
window:
Table 63 AMHS Monitor Connection Status
Status Type Description
Probe status If configured, the AviMet AMHS service checks the status of the recipient from the
server by sending probe messages at a preconfigured frequency:
• OK = AMHS server connection is established and the probe was sent successfully.
• Failure = Connection to the server was rejected or the recipient address or the
credentials were invalid.
Sending status • OK = Message has been sent successfully.

• Failure = Message could not be sent.
Receiving status • OK = AviMet AMHS service is able to successfully poll for incoming messages from
AMHS server.
• Failure = Server did not receive the message because the AMHS server address
information is incorrect or the AMHS server connection is not available.
The following details are typically displayed in the AMHS Monitor window:
Table 64 Sent, Received, and Delivery Report Tab Details
Element Description
Sent Time when the message was sent to the AMHS server. If the message could not be sent,
slashes (///) are displayed.
Received Time when the message was received from the AMHS server. If the message could not
be received, slashes (///) are displayed.
Delivered Time when the message was delivered further by the AMHS server.
Status Status of sending/receiving:

• Success
• Failed
From Address of the sending part.
To Address of the receiving part.
Subject Subject of the message, as configured.
Type Type of the delivery report:

• Positive = Message was delivered.
• Negative = Message was not delivered.
Depending on the configuration, the AMHS server tries to deliver the message to the
recipient, for example, for 24 hours, after which it sends a negative delivery report
indicating the failure.
Message ID The AMHS message ID.
Message The actual content of the message that was sent /received, for example, a METAR
report.
139
16.3 Troubleshooting AMHS Monitor

Table 65 Troubleshooting AMHS Monitor
The AMHS Monitor view is not AMHS Monitor is not part of the Contact system administrator.
displayed. system configuration for your user
profile.
Probe status is constantly Problems with the connection to Contact system administrator.
Failure. the server.
Sending/Receiving fails constantly. Problems with the connection or Contact system administrator.
with the account details, for
example, invalid recipient address
or invalid credentials.
140
Chapter 17 – Diagnostics
17. Diagnostics
17.1 Introduction to Diagnostics
The Diagnostics application monitors the overall status of the AviMet system. The
application is mainly a tool for maintenance personnel who use it for monitoring and
troubleshooting the CDU(s) and other equipment in the system. However, the observers
may have a simplified version of the Diagnostics application which allows them to view the
system events related to their work.
When a system event occurs, an event message is displayed in the Diagnostics application.
The user has to acknowledge the event, and based on the type and status of the event,
decide on further action.
If the system includes a log printer, all events can be configured to be printed automatically
as they occur. Optionally, the Diagnostics application can include the sound alarm function.
Before reading this chapter, find out the system event monitoring practices at your
airport. Diagnostics is a tool primarily intended for maintenance personnel. At some
airports, the task of monitoring events belongs either completely or partially to observers.
More information
17.2 Diagnostics User Interface

The figures and examples in this chapter display situations that have been artificially
created during software test conditions. In normal operation, the number of missing or
faulty items and event messages is smaller and the periods between messages longer.
141
The Diagnostics user interface for observers typically consists of the Events panel. The
Diagnostics application for the maintenance personnel contains several additional features,
such as the System Status panel. For more information, see Vaisala AviMetâ Automated
Weather Observing System Maintenance Manual.
Figure 59 Diagnostics Application (Observer User Profile)
The elements of the Diagnostics application are briefly described in the following sections.
More information
‣ Operating Diagnostics Application (page 144)
17.2.1 Events Panel
The Events panel displays the messages sent by the system. The messages inform the users
of system events, such as changed weather conditions and problems in the system. These
messages have different types and statuses.
The figures show event messages created during software test conditions using an AWOS
system. Normally, the Events panel includes fewer event messages, and the periods
between messages are longer.
The following sections describe the items in the Events panel.
The Diagnostics application for observers may contain only some of the elements
described below.
More information
‣ Operating Diagnostics Application (page 144)
‣ Monitoring and Acknowledging Events (page 144)
142
17.2.1.1 Events Panel Tabs/Event Types

The system events are displayed on several tabs, the number and type of which depends on
the system configuration and the user profile.
Table 66 Events Panel Tabs /Event Types
Type Explanation
Operational/OPER Shows preconfigured operational messages, for example, messages related to

predefined changes in weather.
Technical/TECH Shows preconfigured technical messages, for example, about a sensor problem, or
a communication problem between a sensor and the CDU.
All Shows all event messages configured in the system.

The All tab may contain events of the type NONE. This indicates events that have
not been classified under the main types, for example, some customer-specific
events.
17.2.1.2 Events Panel Statuses and Colors
Table 67 Events Panel Statuses and Colors
Status Color Description
ALARM Red An unacknowledged event informing about a fault that prevents

the system from working properly, or a critical operational
change. Typically requires immediate action.
ACKNOWLEDGED Red status column An acknowledged alarm event.

ALARM only
WARNING Orange/Yellow An unacknowledged event about a situation that, if persisting,

may lead into the system not working properly. Typically requires
at least monitoring.
ACKNOWLEDGED Orange/Yellow An acknowledged warning event.

WARNING status column
INFO Blue Notification of a change in the system state or in the operational

situation. Typically does not require any action.
Any of the above Blue frame Selected event. A selected unacknowledged alarm or warning
will be acknowledged when clicking the ACK button.
17.2.1.3 Events Panel Columns
Table 68 Events Panel Columns and Buttons
Element Name Description
Time Shows the time when the event was generated by the system, or the
acknowledgement time of the event.
Status The status of the event message. See Events Panel Statuses and Colors (page 143).
143
Element Name Description
Priority (Optional) Displays the priority of the alarm if the system has priority classification
capability.
Type The type of the event message. See Events Panel Tabs/Event Types (page 143).
Device The sensor, or other piece of equipment, that the event is related to.
Site The measurement site or other logical entity that the message is related to.
Server The server that the message is related to.
Message The actual message text, for example, a description of the problem and the name
of the problem sensor.
This button marks the selected event as acknowledged. The system stores the
event in a history file, together with the time of acknowledgement. The Status
column stays red until an OVER event for the same reason happens.
If the system includes the optional sound alarm, clicking this button will turn off
the alarm sound for the current alarms. A new alarm event will activate the sound
alarm again.
This button does not acknowledge the alarm.
17.3 Operating Diagnostics Application

17.3.1 Starting and Exiting Diagnostics
Depending on your user profile and system configuration, the application may start
automatically when you log in to an AviMet workstation, or you can open it using the
corresponding shortcut icon, for example, in the desktop.
CAUTION! If your system includes the optional sound alarm and you minimize the
Diagnostic application, make sure that the volume is ON so that you will be able to hear
the sound alarms when they occur.
CAUTION! Do not close the application unless you have a special reason, such as
system maintenance.
17.3.2 Monitoring and Acknowledging Events

The Events panel displays all the system events configured to be displayed for your user
group. Depending on the configuration, the events typically appear on several tabs, for
example, in accordance with event type.
144
When you have read an event message, acknowledge it to inform the system that you have
seen the message. The system then stores the event in a history file, together with the time
of acknowledgement.
A typical system event monitoring procedure is described below. Check the airport-specific
practices for a detailed procedure.
1. Monitor the events in the Events panel.
When a new unacknowledged event appears, a new event row is displayed, with red
status column.
2. If configured, the system also gives a preconfigured sound alarm. To turn off the sound
alarm, click Stop alarm sound.
This button does not acknowledge the alarm.
3. Find and select the event you want to acknowledge by clicking the row with the mouse.
The selected event row will have a blue frame around it.
4. Click ACK.
Note the following:
• The system marks the selected event as acknowledged and stores the event in a
history file, together with the time of acknowledgement.
• The Status column stays red until the reason for the event has disappeared.
• You may need to click on another tab to reveal all unacknowledged events.
• You may not have the rights to acknowledge all events (notifications) that you see.
• If the sound alarm starts again, there are new unacknowledged events (If sound
alarm is configured).
5. Depending on the type and status of the event message, act according to your airport-
specific local practices.
CAUTION! Acknowledging an event indicates that you have seen the message and
marked it. However, if the event was caused by a problem, the problem condition
continues even after you have acknowledged the event until maintenance has fixed it.
More information
‣ Events Panel (page 142)
17.3.3 Viewing Stored Events

All statuses of a single event are stored in history files, which you can view with the ASCII
Log View application. In the history files, the entire event chain can be seen: the time the
event was first shown in the Events panel in the Diagnostics application, the time it was
acknowledged, and the time the problem causing it was fixed.
145
When the problem has been fixed or the condition causing the event has passed, the event
status changes to OVER and the event message disappears from the Events panel.
The OVER status is shown only in the history files, which you can view with the ASCII Log
View application. You can use the history files to track, for example, how long it took for a
problem to be solved.
The following table shows an example of the event chain.
Table 69 An Example of the Event Chain
Event Color System Event Message and ASCII Log View Message and
Status Status
Communication Red event row 09:38 CLOUD MESSAGE 09:38 CLOUD MESSAGE
between cloud height in Diagnostics MISSING, Status: ALARM MISSING, Status: 2
meter and CDU
corrupted at 09:38
Observer notices and Red Status 09:43 CLOUD MESSAGE 09:43 CLOUD MESSAGE
acknowledges the column in MISSING, Status: MISSING, Status: 1
event at 09:43 Diagnostics ACKNOWLEDGED ALARM
Maintenance fixes the - Message disappears from 10:09 CLOUD MESSAGE

problem at 10:09 Events panel MISSING, Status: 0 (= over)
More information
17.4 Troubleshooting Diagnostics
Table 70 Troubleshooting Diagnostics Application
The Heartbeat icon is static green, The Diagnostics application is Restart the application.
not blinking. down.
146
Chapter 18 – ASCII Log View
18. ASCII Log View

18.1 Introduction to ASCII Log View
ASCII Log View is an application for viewing the history files. Depending on the
configuration of the system, the history files are stored either for a period of one year or
several years. The files are either overwritten after one year or deleted when the defined
disk storage limit has been reached.
The content of history files are adapted according to system functionality and requirements.
Typically the history files contain sensor data, meteorological calculation results, sent
reports and technical alarms, warnings and notifications. The history files can contain
practically any ASCII formattable data that has been available in the system during
operation. For example, external interface output, server to display output, data sources and
changes during report preparation, and more detailed system status information can be
stored to the history files.
More information
‣ Viewing Stored Events (page 145)
18.2 ASCII Log View User Interface

The following sections describe these elements of the ASCII Log View briefly.
More information
‣ Operating ASCII Log View (page 152)
147
18.2.1 ASCII Log View Main Window

The following figure presents the ASCII Log View main window when no files have been
selected for viewing.
Figure 60 ASCII Log View Main Window
When history files have been selected for viewing, the files are displayed either in Tab or Tile
mode inside the ASCII Log View main window. See Figure 61 (page 149) and Figure 62
(page 151).
The number and type of parameters that the system stores in history files depends on the
system configuration. Some examples of typical files are presented in the following sections.
148
18.2.2 Weather Parameter Files

The weather parameter files show weather parameters for the measurement sites, as
defined during system configuration. For a list of typical parameters at your airport, refer to
the airport-specific documentation.
Figure 61 ASCII Log View: Weather Parameter File Examples (Tile Mode)
Some typical columns in weather parameter files:

CREATEDATE
The date and time of the measurement. The format is YYYY-MM-DD hh:mm:ss. For
example, 2001-03-28 12:30:30.
SITE
The measurement site or runway, for example, 02L.
Parameter name
The stored weather parameter name and its identification data, for example, RVR_1A.
ST
(When applicable) The status of the data at the time when the data was stored. Status
codes provide you with information on two things: Sensor mode (Backup and
Manual) and data status (Old, Invalid, Missing, Undefined).
149
If the data has several simultaneous statuses, all these statuses are shown in the status
column.
Table 71 ASCII Log View: Status Codes
Status Code Data Status at Storage Time
- (no code) Normal status. Data comes from a sensor and is valid.
C (Backup/Copied) Data comes from a backup sensor due to a problem with the original sensor.
m (Manual) Data is entered manually by the user due to a problem with the original sensor.
O (Old) Data has not been updated for a certain timeout period due to sensor
communication problems, but it is still considered to be valid.
I (Invalid) Data is invalid or out of range, and should not be used. Can occur because of a
sensor or data line malfunction.
M (Missing) Data is not available due to sensor communication problems. Data has not been
updated and is considered as being missing.
U (Undefined) When data has been measured or calculated, but the numerical value cannot be
determined, the status is Undefined. For example, cloud layers have been
measured but there are no clouds. Data value may be available, but it should not
be used.
18.2.3 Reports Files
History files can include the created weather reports, for example, METAR, as displayed in
the WeatherView application. Typical parameters in the reports files are the following:
TIME
The date and time of the measurement. The format is YYYY-MM-DD hh:mm:ss.
TYPE
The report type.
REPORT
The report as displayed in WeatherView.
18.2.4 Events Files
The history files can contain events files, which typically show the events as they are
displayed in the Diagnostics application.
150
Figure 62 ASCII Log View: Example Events Files (Tab Mode)
The contents of the files are defined during system configuration, thus the events file may
differ from the ones presented here. Examples of some typical events file column
parameters:
TIME
The date and time of the event. The format is YYYY-MM-DD hh:mm:ss.
Site
The site of the event. For example, 02L.
MSG
The event message as displayed in the Events panel of the Diagnostics application.
CAT
The event type, for example, TECH. For more information on event types, see Vaisala
AviMetâ Automated Weather Observing System Maintenance Manual.
ST/Statustext
The status of the event:
0 = over
1 = acknowledged
2 = alarm
3 = warning
4 = message notification
18.2.5 ASCII Log View Toolbar Buttons

The buttons available in the toolbar at the top of the application:
Table 72 ASCII Log View toolbar buttons
Button Description
Arranges the opened history files in tab format.
151
Button Description
Arranges the opened history files in tile format. You can view several files
simultaneously and resize and arrange the windows.
Opens a new file.
Saves the active file.
Prints the active screen. The button is enabled only when there is at least one file
open.
Checks every 10 seconds if the file has changed and updates the data on the
screen with the changed data.
Immediately checks if the file has changed and updates the data on the screen
with the changed data.
Moves to the first row of the file.
Moves to the last row of the file.
Shows the non-printable characters (binary values) as symbols.
Wraps long text into several rows.
Enables backing up the files. Available typically for Observer, Maintenance and
administrator users.
Displays software version and copyright information.
18.3 Operating ASCII Log View

More information
‣ ASCII Log View User Interface (page 147)
18.3.1 Opening and viewing history files

By default, the history files are located in the CDU in the D:\Avimet\history\month
folder. The files can be viewed on the workstations by sharing the drive and mapping it on
the workstation.
In some systems, the CDU stores the history files on a network drive which can be accessed
by sharing the drive and mapping it on the workstation. In some systems, the access is
restricted to certain directory paths only.
152
Figure 63 ASCII Log View: Opening history files
Table 73 Sample ASCII Log View file names
Example Path and File Name Stored Data Explanation
Avimet\history\(month\) Weather data Parameter data for measurement site 02L

(PARAMETER)_02L_25.his from the 25th day of the month.
Avimet\history\(month\) Reports Report data on the 25th day of the month.

REPORTS_25.his
Avimet\history\(month\) Events Event data on the 25th day of the month.

EVENTS_25.his
To open and view history files:

1. Start the ASCII Log View application.
2. Select Open in the toolbar.
153
3. In the file selection window, open the D:\Avimet\history folder, or another folder
specified for history files in your system.
In some systems, history files are stored in the CDU and mapped to the last network
drive (for example, H:\). In such a case, look for the appropriate folder when you
want to open history files.
In some systems, the access is restricted to certain directory paths and folders only.
4. If needed, select the folder you wish to view, for example, a monthly folder. This
location is saved and opened by default the next time.
5. Find the file with the date and type you wish to view, for example, EVENTS_20.his
for the events on the 20th day of the month.
6. Select Open.
The file is displayed in the ASCII Log View window.
7. Open all the files you wish to view and select either tab mode or tile mode, see Viewing
Several Files at the Same Time (page 154).
8. When files are open, you can do the following:
• To see all the columns, drag the column borders or use the horizontal scroll bar.
• If longer texts are not displayed, select Wrap Text to make the text flow into several
lines.
• You can move inside the file by selecting First Row and Last Row in the toolbar.
9. You can close a file by selecting at the tab header or the tile corner.
18.3.2 Viewing Several Files at the Same Time

1. Open all the history files you wish to view, see Opening and viewing history files
(page 152).
2. Select the display mode by clicking Tabs or Tile.
3. In the Tab mode, you can do the following:
• Click the tab titles to change which file is displayed.
• Use the arrow buttons next to the tab headers to view more files.
• Use the scroll bars to view more data.
• To close a tab, click at the Tab header.
• An example of files in Tab mode is presented in Figure 62 (page 151).
154
4. In the Tile mode, several open files are displayed simultaneously. You can do the
following:
• If the files do not fit the screen, drag the file window borders to resize and arrange
the files to suit your needs.
• Use the scroll bars to view more data.
• To close a tiled file, click in the right corner of the tiled window.
• To make more space for a tiled file you can minimize another file by clicking in
the left corner of the tiled window.
• An example of files in Tile mode is presented in Figure 61 (page 149).
18.3.3 Refreshing Data Automatically

Normally, the data in the screens is not refreshed. To automatically refresh the data:
1. Click Auto Refresh in the toolbar.
The system checks every 10 minutes if the data has changed and refreshes the screen with
the new data.
18.3.4 Refreshing Data Manually

Normally the data in the screens is not refreshed. To manually refresh the data:
1. Click Refresh in the toolbar.
The screen is immediately updated with any changed data.
18.3.5 Hiding Rows
When a history file is open, you can hide rows as needed.
1. Select the row or rows that you want to hide:
• To select one row:
Click the row number in the first column to select the row.
• To select consecutive rows (for example rows 5 to 20):
Click the row number in the first column of the first row that you want to hide.
Hold down the SHIFT key and click the row number of the last row that you
want to hide.
• To select non-consecutive rows (for example rows 5, 10 and 25):
Click the row number in the first column of the first row that you want to hide.
Hold down the CTRL key and click the row numbers of the other rows that you
want to hide.
The selected rows are displayed with blue background color.
2. To hide the selected rows, right-click on any of the rows and select Hide.
You can also use the shortcut key for hiding: CTRL+ 9.
155
18.3.6 Showing Hidden Rows
To check if there are hidden rows, look at the row numbers in the first column. Missing row
numbers indicate that rows are hidden.
To unhide hidden rows:

1. Right-click anywhere on the open file.
2. Select Unhide All. All hidden rows are shown again.
You can also use the shortcut key for unhiding: CTRL + SHIFT + 9.
18.3.7 Exporting history files

Depending on the system configuration, the history files are standard comma separated or
tab separated ASCII characters. You can use the history files for troubleshooting or other
post-processing purposes such as finding, filtering, sorting, or graphical presentation of the
data.
Use the import functionality of, for example, the spreadsheet application of your office tool
kit.
You can also save the active file by selecting Save As in the toolbar. You can select the
location, for example, a USB drive, and change the file name, if needed. In some systems the
access is restricted and only certain predefined locations and file extensions can be used.
18.3.8 Backing up History Files

If available for your user profile, you can back up the ASCII database history files on an
external drive.
The history folder structure must be in format year/month/day (for example,

2018/Aug/09) and the history folder must be shared.
1. In ASCII Log View, select Back Up at the top of the application.

2. In the backup window, select the appropriate CDU, if available.
3. Click the date to select the day that you want to back up and click OK.
4. Select the destination folder for the files on the external drive.
5. Select Copy. The files are copied to the selected location.
6. Repeat for other days, as needed.
156
18.4 Troubleshooting ASCII Log View

Table 74 Troubleshooting ASCII Log View
You cannot find the history files in The history files might be located Check the location of the history
the CDU folder D:\Avimet on another location in the CDU or files from system maintenance, and
\HISTORY. on a network drive. check that the drive has been
shared and mapped on your
workstation.
You cannot find history files for the Depending on the configuration, Check the storage time from
previous months. the history files might be stored system maintenance or airport-
only for one month. specific documentation.
When viewing a history file, some The columns might have been Drag the column borders so that
parameters or columns are missing. dragged on top of each other by the hidden columns will appear.
mistake.
When viewing a history file, some The rows might have been hidden. Right-click and select Unhide All.
rows are missing.
You cannot access some locations Your system is configured to allow Use only the locations
when opening or saving the files. access only to certain predefined preconfigured for your system.
locations.
You cannot rename, overwrite, or Your system is configured to allow Use only the original files and file
delete the files. only restricted file handling. names.
157
19. Actuals
19.1 Introduction to Actuals View
If the normal data flow from the primary sensor is interrupted, for example, when the sensor
is out of order or being maintained, you can define that a backup sensor provides the data
instead. Or if a backup sensor cannot be used, you can enter the data manually. You can
make these selections in the Actuals view, which is typically part of the WeatherView
application.
The available options depend on the system configuration.
The backup sensors must be preconfigured during system configuration.
19.2 Actuals View User Interface

The Actuals view lists the primary sensors in your system and the preconfigured backup
sensors, when available. Depending on the system configuration, you can activate a backup
sensor to provide the data when the normal data flow from the primary sensor is
interrupted, or enter the data manually.
Figure 64 Actuals View Example Page
158
Chapter 19 – Actuals
More information
‣ Data Status Indication (page 31)
19.3 Activating Backup Sensor

When normal data flow from the primary sensor is interrupted, for example, during sensor
problems or maintenance, you can activate a preconfigured backup sensor to provide the
data.
1. Before activating a backup sensor, you must get instructions from the maintenance
personnel. They will tell you when to activate a backup sensor, and when you can
activate the primary sensor again.
2. Open the Actuals view, typically in the WeatherView application.
3. Select the location from the Location list, for example, RWY 04R/22L.
4. Select the sensor type from the Sensor type list, for example, Wind.
5. If applicable, select the runway zone using the tabs, for example, TDZ 04R.
6. Find the backup sensor that you want to activate and select Activate on that sensor
row.
The color of the data values in the Actuals view and in the WeatherView data fields
changes to indicate that the data is coming from a preconfigured backup sensor.
19.4 Entering Manual Data

If the manual input option is configured, you can provide the data manually when
applicable. This option is useful when the normal data flow from the primary sensor is
interrupted and a preconfigured backup sensor cannot be used.
1. Before activating the manually entered data, you must get instructions from the
maintenance personnel. They will tell you when to activate manual data and when you
can activate the primary sensor again.
2. Open the Actuals view, typically in the WeatherView application.
3. Select the location from the Location list, for example, RWY 04R/22L.
159
4. Select the sensor type from the Sensor type list, for example, Wind.
5. If applicable, select the runway zone using the tabs, for example, TDZ 04R.
6. In the Manual row, enter the manual data as needed.
If needed, you can revert back to the previous manual values by selecting Reset.
7. To take the manual values into use, select Activate.

The color of the data values in the Actuals view and in WeatherView data fields
changes to indicate that the data has been entered manually.
160
Chapter 20 – Sensor Selector
20. Sensor Selector
20.1 Introduction to Sensor Selector
20.2 Sensor Selector User Interface

Sensor Selector lists all sensors and connection interfaces of the system, including sensor
name, sensor location, message type, and sensor status.
Figure 65 Sensor Selector User Interface
Table 75 Sensor Selector Columns
Column Description
Name Name of the sensor in the system.
Mode Shows if the sensor is disabled or enabled.
Enabled (= Enabled checkbox selected): Data from an enabled sensor is used in the
system and its status is Online.
Disabled (= Enabled checkbox not selected): Data from a disabled sensor is not used in
the system and its status is Offline.
State The current status of data (Manual/Automatic).
Type Type: sensor or interface
Model Sensor model, for example, CT25K.
161
Column Description
Location Location of the sensor, for example, runway 10L.
Status Status of the sensor:

• Online: Sensor is working normally and its data is used in the system.
• Unavailable: Sensor is offline/unavailable and its data is not used in the
system.
• Faulty: Sensor is enabled and used in the system but it is not working properly.
You should disable the sensor and use alternative sources for data.
• Degraded: Sensor data is degraded but used in the system. You should
investigate the situation, disable the sensor and use alternative sources for data.
20.3 Operating Sensor Selector

20.3.1 Disabling Data Use
If a sensor is faulty, or being maintained, you can disable the sensor by doing the following:
1. Move the mouse pointer over the row for the sensor that you want to disable.
2. Deselect the Enabled checkbox.
This will change its status to Offline and the data from it will not be published for other
system processes.
20.3.2 Enabling Data Use

1. Move the mouse pointer over the row for the sensor that you want to enable.
2. Select the Enabled checkbox.
This will change its status to Online and the data from it will be published for other system
processes.
162
Chapter 21 – Data Source Manager
21. Data Source Manager

21.1 Introduction to Data Source Manager
In some systems, the Data Source Manager application displays the available data sources
for pressure and prevailing visibility values, and the values produced by the sources. The
available sources can be sensors, sensor groups, and manual values. One of the sources is
always selected as the active data source that best represents the general conditions at the
airport. You can change which data source is active, enter manual values, and monitor the
status of the sensors and calculation.
Another part of the application is the PV Group Manager window. In this window, the
groups available as the data source for the Prevailing Visibility values can be created and
edited. Normally, the groups are set in the system configuration, but when the groups have
to be updated, for example, when a new sensor is added to the airport, the adjustments can
be made in this window.
21.2 Data Source Manager User Interface

The user interface consists of the Data Source Manager window and the PV Group Manager
window.
21.2.1 Data Source Manager Window

The Data Source Manager window consists of the Pressure tab, the Prevailing Visibility tab,
and the Change window.
Figure 66 Data Source Manager Window, Pressure Tab
163
Figure 67 Data Source Manager, Prevailing Visibility Tab
The following sections briefly describe the elements of these windows.
More information
‣ Operating the Data Source Manager Application (page 170)
21.2.2 Active Data Source

The NAME column displays a list of all the available data sources in the system. One of the
sources has to be selected as the Active data source, which means that it best represents
the general conditions at the airport. It is the data source selected when only one source is
used. Usually, for example, the METAR template uses the active data source. The active
source is indicated in the INFO column by the text Active.
Other sources are also producing data which can be used as the source in applications.
More information
‣ Changing the Active Data Source (page 171)
21.2.3 Normal Situations
The normal situation before any manual changes have been made and the active sensor is
producing valid data, is the following:
• The active data source is marked with the text Active in the INFO column.
• The default source, if defined in system configuration, is marked with the text Default
in the INFO column.
• The icons in the ACTIVE and STATUS columns are green for the active source.
164
Figure 68 Data Source Manager Window, Default Situation
One of the sources may have been defined as the default source in system configuration.
The source is marked with the text Default in the INFO column. If this sensor is not
selected as the active source, the ACTIVE column icon is yellow (with the letter W). This
indicates that the data is valid, but not coming from the default source.
Figure 69 Data Source Manager Window, Active Sensor Changed
21.2.4 Exceptional Situations
If a source is marked with the text Disabled in the INFO column, the data cannot be used
from that source.
If one of the icons is red, it means that the data is missing or invalid, or that an active source
has been disabled and the data from the active source is not available.
A yellow icon in the STATUS column indicates that the source has been disabled. If the
disabled source is active, the icon in the ACTIVE column is red to warn that no data is used
in the system from the active source.
More information
‣ Data Source Manager Window Columns (page 165)
21.2.5 Data Source Manager Window Columns

The columns and colors common to both tabs of the Data Source Manager window are
described in the following table.
Table 76 Data Source Manager Window Columns and Colors
Column Description
ACTIVE Shows the state of the active data source. See Active Data Source (page 164). The icons
are the following:
• Green = The default data source is active and producing valid data.
• Yellow (W) = The data source is active, and producing valid data, but it is not the
default source (only in systems where a default source has been defined in the
system configuration).
• Red (E) = The data source is active, but the data is missing or invalid, or the source is
disabled (only with pressure values). No data is produced from the source.
• None (-) = The source is not the active data source.
165
Column Description
STATUS Shows the status of the data source:

• Green = The data source is producing data.
• Yellow (W) = The source is disabled. Data is produced, but not used in the system.
• Red (E) = The data from the source is missing or invalid.
NAME The name of the data source: sensor or sensor group name, or the name of a manual
data list.
INFO Shows a combination of the following data and data source status indicators:
• Active = The data source is selected as the active source that best represents the
conditions at the airport. See Active Data Source (page 164).
• Default = The data source is defined as the default data source in system
configuration.
• Disabled = (Only with pressure data) The data source has been manually disabled,
data cannot be used. 1)
• Invalid = The data source is producing data that does not pass the validation
checks.
• Manual = The data source is for manual entry of raw data.
• Missing = The data source is not producing any data.
1) All sources are by default enabled, that is, data from them can be used if the source is producing valid data.
Missing and invalid values are indicated with one or more slashes (/) in the value columns.
On the Pressure tab, the middle columns contain the parameter values for pressure. The
typical columns are described in the following table.
Table 77 Data Source Manager, Value Columns for Pressure
Column Description
PARAW Last processed pressure value received from the sensor (raw value). This value is
provided only for diagnostic use, it will not be used by calculations.
PAINS Instant pressure (hPa) measured at the data source altitude.
QFEREF Pressure reduced to the airport reference altitude (hPa).
QNHI2NS Pressure reduced to sea level using ICAO standard atmosphere (hPa).
CORR The correction added to raw data source pressure in order to get the PAINS value (hPa).
This is displayed only if the system is configured to support the calibration of pressure
sensors.
HEIGHT Height of the data source (m). This is relative to the airport reference altitude.
166
On the Prevailing Visibility tab, the middle columns contain the parameter values for
visibility. The typical columns are described in the following table.
Table 78 Data Source Manager, Value Columns for Prevailing Visibility
Column Description
PV Prevailing visibility at the airport, in meters.
MINVIS Minimum visibility from the sensor, in meters.
MINDIR Direction of minimum visibility (cardinal points, /, or ND for non-directional).
MAXVIS Maximum visibility from the sensor, in meters.
MAXDIR Direction of maximum visibility.
More information
‣ Exceptional Situations (page 165)
21.2.6 Data Source Manager Buttons
Table 79 Data Source Manager Window Buttons
Button Description
Disable (Only on the Pressure tab) Disables the use of the data source. No data will be available
from a disabled data source.
Enable (Only on the Pressure tab) Enables a data source that was disabled.
Activate Makes the data source the active source.
Change Opens the Change window for entering manual raw data values. The validated values
are displayed in the manual list row. To make the system use the manual data, activate
the manual source after setting the values.
For pressure values, if the system has been configured to support the calibration of
pressure sensors, the new correction factors will be calculated for pressure sensors
when the manual value is changed to a new valid value.
Group Manager Opens the PV Group Manager window for creating and editing the groups of sensors
that produce the prevailing visibility values.
Close Closes Data Source Manager. The settings made in the application are saved and remain
valid until the application is opened again and new changes made.
More information
‣ Active Data Source (page 164)
‣ PV Group Manager Window (page 168)
167
21.3 PV Group Manager Window

The PV Group Manager window is displayed when you click the Group Manager button on
the Prevailing Visibility tab.
Figure 70 PV Group Manager Window
Table 80 Elements on Prevailing Visibility Groups Pane
Element Description
Prevailing Visibility Displays the configured prevailing visibility sensor groups and allows you to edit
Groups existing groups and add new groups.
Add Opens the Add Prevailing Visibility Group window for adding a new group.
Edit Opens the Edit Prevailing Visibility Group window for renaming the selected
group.
Remove Removes the selected group.
168
The Prevailing Visibility Group frame displays the sensors of the group that is selected in
the Prevailing Visibility Groups frame, and allows you to edit the group.
Table 81 Elements on Prevailing Visibility Group Pane
Element Description
Available sensors Displays the sensors available for selection (sensor name and location).
Selected sensors Displays the sensors selected for the group (sensor name, location, and weight
value of the sensor in this particular group).
Add Moves the selected sensor(s) to the group.
Remove Removes the selected sensor(s) from the group.
The Prevailing Visibility Sensor frame displays the details of the selected sensor.
Table 82 Elements on Prevailing Visibility Sensor Pane
Element Description
Name Name of the sensor.
Location Location of the sensor.
Weight Shows the weight value that the sensor has among other sensors in the group, the
default value is 1.0. You can edit the value. If you enter the value 0.0, the sensor
is not included in the calculations.
The following table explains the buttons at the bottom of the PV Group Manager window.
Table 83 Buttons on PV Group Manager Window
Element Description
Validity limit Opens the Prevailing Visibility Validity Limit window for setting the validity limit
for prevailing visibility. The default value is 60 %.
OK Saves the changes and closes the window.
Apply Saves the changes without closing the window.
Cancel Closes the window without saving the changes.
More information
‣ Sensor Weight Value (page 169)
‣ Validity Limit (page 170)
21.3.1 Sensor Weight Value

The sensor weight value is used in average and validity limit calculations. The bigger the
weight value, the more weight, or importance, the sensor has in the calculation among other
sensors in the group. Typically the weight represents the proportional area that the
individual sensor has of the total area. If each sensor covers an equal proportion of the area,
169
each sensor has the weight value of 1.0. If one sensor represents a larger area of the total, its
weight value is bigger, for example, 1.1, while the sensors that cover a smaller area have a
smaller weight value, for example, 0.8. In addition to the proportional area, there might be
other reasons for emphasizing a sensor more than another.
The default value is 1.0 for all the sensors. If the sensor weight value is 0.0, the sensor is not
included in the calculations at all. The weight value can be entered in the Weight field of the
PV Group Manager window. A sensor can have different values in different prevailing
visibility groups. The weight value of the sensors in a particular group are displayed in the
Selected sensors list.
21.3.2 Validity Limit
The prevailing visibility value is calculated only if enough valid data is available for the
calculation. The validity of the prevailing visibility value represents the proportion of the
valid data weight to the total data weight. The validity limit defines the acceptable level of
validity. For example, if a sensor is missing, the amount of valid data weight is reduced by
the weight of the sensor. If the proportion of the valid data weight to the total data weight
becomes less than the validity limit, the prevailing visibility value is not calculated at all,
instead, it is displayed as a missing value.
The default validity limit is 60 %. The limit can be set in the PV Group Manager window by
clicking the Validity limit button.
21.4 Operating the Data Source Manager

Application
More information
‣ Data Source Manager Window (page 163)
21.4.1 Starting and Exiting Application

To exit the application, select File > Exit.
21.4.2 Starting and Exiting Data Source Manager

You can start Data Source Manager using the corresponding shortcut icon, for example, in
the desktop.
To exit Data Source Manager, click Close. The settings you made in the application will be
saved and remain valid until you open the application again and make new changes.
170
21.4.3 Changing the Active Data Source

You can select which data source (sensor, sensor group, or manual value list) is used as the
active data source. The active data source is the source that is selected as best to represent
the conditions at the airport.
1. Open the Data Source Manager application.
2. In the INFO column, check that the sensor you want to select is not invalid, missing, or
in case of pressure values, disabled.
3. Click Activate for the data source. Confirm the selection by selecting Yes in the
message window.
4. After the change, the STATUS column icon should be green and the ACTIVE column
icon should be green (or yellow if the source is not the default source). If the color is
red, the data is missing or invalid, or the source is disabled (for pressure values) and no
data is produced from the source.
CAUTION! If you try to activate a data source that is missing, invalid, or disabled,
the system shows a warning message. Select No and enable the data source first, if
possible, or activate another data source.
Figure 71 Activate Data Source Window, Warning
More information
‣ Active Data Source (page 164)
21.4.4 Using Manual Values

When all sensors are out of order or being maintained, manual values can be entered using
Data Source Manager.
171
2. To enter or edit the manual values, click Change on the row for the manual values.
3. In the Change window, enter the raw values in appropriate fields and click OK.
The values are validated and processed using the same algorithms used when
calculating the values in the sensor list columns. The processed values are displayed in
the columns for the manual source list in the main window.
4. Check that the processed values are valid. If the value you entered is not valid, the INFO
column contains the text Invalid.
5. If the manual data source is not active yet, click Activate on the row for the manual
values.
Now the entered value will be used by the system. There will be a yellow icon in the
ACTIVE column to remind you that the used source is not the default source.
6. When the value needs to be updated, repeat the previous steps.
7. When the manual values are no longer needed, remember to select one of the other
sources as the active source.
For pressure values, the system will also calculate the difference between the sensor value
and the manual value reduced to sensor altitude. This correction is shown in the CORR
column. The correction will be used by the system for calculating other values based on the
pressure value.
More information
21.4.5 Disabling and Enabling Data Sources for Pressure Values

With pressure values, when the sensor is out of order or being calibrated, you can disable
the sensor so that its data will not be used in the system.
2. If the source that you want to disable is active, activate first another data source by
clicking Activate of a valid data source.
172
3. Click Disable for the sensor. Confirm the selection by selecting Yes in the message
window.
CAUTION! If you select to disable a data source that is active, the system shows a
warning message indicating that no data will be shown from the active source if
you proceed. Select No, and activate first another data source, if possible.
4. When the sensor has been fixed and its data can be used again, enable it by clicking
Enable on its row.
After that, if you want the system to use it as the active data source, activate the source
by clicking Activate.
More information
21.4.6 Managing Prevailing Visibility Groups

You can manage the groups available for selecting as sources for prevailing visibility in the
PV Group Manager window.
21.4.6.1 Adding New Prevailing Visibility Groups
1. In the Data Source Manager window, select the Prevailing Visibility tab.
2. Click Group Manager.
3. In the PV Group Manager window, in the Prevailing Visibility Groups frame, click Add.
4. In the Add Prevailing Visibility Group window, enter the name of the group that you
will create and click OK.
5. With the group selected, go to the Prevailing Visibility Group frame, select the sensors
from the Available sensors list, and click the Add arrow button, or double-click on the
sensor. Do this for all the sensors you want to include in the group.
The sensors you have selected will be displayed in the Selected sensors list.
173
6. In the Prevailing Visibility Sensor frame, the name, location, and weight value of the
sensor selected in the Selected sensors list are displayed. By default, the weight 1.0 is
always used with new sensors. You can change the weight of the sensor in the selected
group by entering a new value in the Weight field.
7. To save the created group, click Apply.
More information
21.4.6.2 Editing Prevailing Visibility Groups
1. In the Data Source Manager window, select the Prevailing Visibility tab.
2. Click Graph Properties.
3. In the PV Group Manager window, in the Prevailing Visibility Groups frame:
• To rename a selected group, click Edit, and in the Edit Prevailing Visibility Group
Name window, enter a new name and click OK.
• To remove a selected group altogether, click Remove.
4. In the Prevailing Visibility Group frame:
• To add more sensors to the selected group, select a sensor from the Available
sensors list and click the Add arrow button. The sensor is displayed in the Selected
sensors list.
• To remove a sensor from the selected group, select the sensor in the Selected
sensors list and click the Remove arrow button.
5. In the Prevailing Visibility Sensor frame, you can change the weight value of the sensor
selected in the Selected sensors list by entering a new value in the Weight field.
6. To save the changes, click Apply.
More information
21.4.6.3 Editing Validity Limit
1. Open the PV Group Manager window.

2. Click Validity limit at the bottom of the window.
3. In the Prevailing Visibility Validity Limit window, enter the new value in the Validity
limit field.
4. Click OK or Apply in the PV Group Manager window.
More information
‣ Validity Limit (page 170)
174
21.5 Troubleshooting Data Source

Manager
Table 84 Troubleshooting Data Source Manager
Red icon (E) is displayed in the Data is missing or invalid due to Check the sensor or sensor
STATUS column. problems with the sensors or communication. If the data source
communication, or the manually is active, activate another data
The text Missing or Invalid is entered value is not valid. source. If you are using manual
displayed in the INFO column. values, enter a valid value.
Data is missing from the value
fields.
Red icon (E) is displayed in the The source is active and used by See above, or enable the data
ACTIVE column. the system, but no data is source, if possible, or activate
displayed because the data is another source that is not disabled.
missing or invalid, or the source is
disabled.
Yellow icon (W) is displayed in the In systems where a default data This is to remind you that the
ACTIVE column. source has been defined in system default source is not used. When
configuration: the source is active, the default source can be used
but it is not the default source. again, enable and activate it.
Data is produced normally.
Yellow icon (W) is displayed in the (Only for pressure values) The If the source is active, enable the
STATUS column. source is disabled and its data is source or activate another source.
not used in the system. If the source is not active, for
The text Disabled is displayed in example, because the sensor is
the INFO column. being repaired or calibrated,
remember to enable the sensor
when finished with repair or
calibration.
In the PV Group Manager window, There is a problem with the Contact Vaisala helpdesk.
when selecting sensors from the configuration.
Available sensors list for the first
time, the list is empty, or some
sensors are missing.
The displays are not updated. There is a problem with the Check the connections.
connection to the CDU.
There is a problem with the Contact Vaisala helpdesk.

configuration.
175
22. History Monitor
22.1 Introduction to History Monitor
The History Monitor application is used for retrieving past measurement data from the
database and viewing the data in table or graphical format. With the application, observers
and forecasters can monitor trends in weather from a selected period, including real-time
data. They can create views, for example, for certain parameters for each runway.
Preconfigured SQL queries are also available for viewing.
22.2 History Monitor User Interface

The user interface of the application consists of the History Monitor main window, its menus
and the toolbar, and the views that can be created and opened from the main window. In
addition, there are windows needed when creating the views and adjusting the settings.
These elements are briefly explained in the following sections.
The main window is displayed blank when the application is started.
Figure 72 Blank History Monitor Main Window
Typically, the first task is to create the views and save them for future viewing. Views can be
created, for example, for each runway, or for a set of weather parameters, events, or reports.
The typical view types are the following:
• Table View, which shows the parameter data in text format arranged in columns.
176
Chapter 22 – History Monitor
• Trend View, which shows the parameter data in graph format.

• Query View, which shows the results of simple preconfigured queries from the database
in table format.
The views display data from the pre-configured default period, typically, 1‑hour period with
the default resolution. These options can be adjusted in the Options window.
Figure 73 History Monitor with Opened Views
1 Menu bar
2 Toolbar
3 Table View window
4 Trend View window
5 Query View windows
More information
‣ Operating History Monitor (page 186)
22.2.1 Trend View Window

The Trend View windows contain the time scale, the parameter value scale of the selected
data items (sensors or sites), and the trend line (graph) for each data item. For an example
view, see Figure 73 (page 177).
The data items are selected when creating the view, but they can also be edited during
viewing. All parameters of a Trend View must have the same unit. The view can be saved for
future viewing, and the name of the saved view is displayed in the window title bar.
At the top of the Trend View window, a legend is displayed showing the data item names,
the trend line colors, and check boxes for selecting whether the items are displayed or not.
177
A graph may be divided into several pages. The default setting is 60 data points (one hour)
per page. The pages can be scrolled using the navigation buttons in the toolbar.
The graph can be zoomed in and out. The graph settings can be adjusted, including the
display period and data resolution.
More information
22.2.2 Table View Window

The Table View windows contain the timestamp and the parameters of the selected sensors
or sites, for example, MOR_12R, WIND_12R, TT_12R. For an example view, see Figure 73
(page 177).
The contents are selected when creating the view, but they can also be edited during
viewing. The view can be saved for future viewing, and the name of the saved view is
displayed in the window title bar.
The display period and data resolution can be adjusted.
More information
22.2.3 Query View Window

The Query View shows the results of a simple preconfigured SQL query from the database.
For an example view, see Figure 73 (page 177).
The contents of the query views have been selected in system configuration. The user
selects a query to be displayed from a preconfigured list.
More information
22.2.4 New Window
The New window displays the view types that you can create or open. The window is
displayed when you select File > New Frame. Once the view type is selected, an empty
frame opens for the selected view type.
Figure 74 New Window
178
22.2.5 Open Window
The Open window displays the views that have been saved in the local computer using the
same user name that you have logged on with. The window displays the views of the same
type as the active open view, or the type that you selected in the New window. The window
name includes the type of view. The Open window is displayed when you select File > Open.
Figure 75 Open View Window
22.2.6 Data Item Selection Window

The Data Item Selection window contains the preconfigured data items available for
selecting to be displayed in the views. The window is displayed when you select Edit > Data
Item Selection.
Figure 76 Data Item Selection Window
179
Table 85 Data Item Selection Window Elements
Element Description
Available Data Items Shows the pre-configured data items that can be selected to be displayed in the
views.
Selected Data Items Shows the data items that you have selected to be displayed in the view.
Moves the items selected from the Available Data Items list to the Selected Data
Items list.
Select all Selects all items from the Available Data Items list.
Removes the selected items from the Selected Data Items list.
Clear all Removes all items from the Selected Data Items list.
OK Applies the made selections.
More information
‣ Changing Displayed Data Items (page 189)
22.2.7 Options Window
The Options window contains the display period and data resolution settings for the view
that is currently active. The window is displayed when you select Tools > Options.
If you do not adjust the settings, the views display data from the pre-configured default
period, typically, one hour with the 1‑minute default resolution.
Figure 77 Options Window
180
Table 86 Options Window Elements
Element Description
Sliding When this option is selected, the data will be displayed from the present moment
backwards for the time period selected from the Hours list.
Hours The time period for which the data is shown from this moment backwards (when
the Sliding option is selected). The hours can be selected from the list, or another
time period can be entered in hours.
Fixed When this option is selected, the data will be displayed for the period selected
from the Start and the End lists.
Start The start date and time of the period (when the Fixed option is selected). The
date and time can be edited, or a date can be selected from the calendar that
opens when you click the arrow button.
End The end date and time of the period (when the Fixed option is selected). The date
and time can be edited, or a date can be selected from the calendar that opens
when you click the arrow button.
Data resolution The interval at which the data is shown, in minutes. The interval can edited or
selected from the list.
OK Applies the changed options.
For Trend View, the maximum period that can be opened with 1‑minute resolution is
24 hours.
The period available in the database depends on system configuration and the resolution
that has been used for saving data in the database.
181
22.2.8 Graph Properties Window

In the Graph Properties window you can change several graph properties for the Trend View
graphs, for example, the axis and background color. The window is displayed when a Trend
View is active and you select Edit > Graph Properties.
Figure 78 Graph Properties Window
More information
‣ Editing Graphs in Trend Views (page 192)
182
22.2.9 Extremes Window
In the Extremes window you can view the minimum and maximum values over the period
selected in the active Trend View. The window is displayed when a Trend View is active, and
you select Tools > Extremes.
Figure 79 Extremes Window
Table 87 Extremes Window Elements
Element Description
Period
Begin / End Shows the start and end of the period selected in the active Trend View. If you
have zoomed in in the window, this shows the period of the zoomed-in period.
Results
Item Shows the parameters included in the active Trend View and allows you to select
the item whose extreme values you want to see.
Min Shows the minimum value of the selected item during the period and the time
when the value occurred.
Max Shows the maximum value of the selected item during the period and the time
when the value occurred.
Avg Shows the average value of the selected item during the period.
Tend Shows the tendency value of the selected item during the period.
OK Closes the window.
183
22.2.10 History Monitor Menu Bar

The History Monitor functions can be selected from the menu bar in the main window.
Typical menus and menu commands are presented in the following tables. The items in the
menus differ depending on what kind of view is currently active.
Table 88 History Monitor: File Menu
Command Description
New Frame Opens the New window for selecting whether to create or open a new Table View,
Trend View, or Event View.
Open Opens the Open window for opening the type of view selected in the New
window. The window shows the views of the selected type, saved on the local
computer using the user name you have logged on with.
Save As Opens the Save View As window for saving the created view for further viewing.
Close Closes the active view window.
Delete Opens the Delete window for deleting created views. The window shows the
views of the selected type, saved on the local computer using the user name you
have logged in.
Restore layout Opens the saved arrangement of several view windows.
Save layout Saves the current arrangement of open view windows (the views must have been
saved first).
Print Prints the active table or query. Trend view has a separate print functionality in
Edit > Graph Properties.
Exit Exits the History Monitor application.
Table 89 History Monitor: Edit Menu
Command Description
Data Item Selection Opens the Data Item Selection window for selecting which parameters the view
contain.
Graph Properties Opens the Graph Properties window for editing graph settings in Trend Views
(only available when a Trend View is active).
Table 90 History Monitor: View Menu
Command Description
Refresh Immediately checks if real-time data has changed and updates the data in all open
views with the changed data.
First Moves to the beginning of data in the view.
Previous Moves to the previous page in the view.
Next Moves to the next page in the view.
Last Moves to the end of data in the view.
184
Command Description
Toolbar Shows/Hides the History Monitor toolbar
Status bar Shows/Hides the History Monitor status bar
AutoRefresh When selected, the real-time data is refreshed automatically at the preconfigured
interval, typically every 60 seconds.
Table 91 History Monitor: Tools Menu
Command Description
Options Opens the Options window for selecting the display period and the data
resolution.
Extremes Opens the Extremes window for viewing the minimum and maximum values for
the period shown in the active Trend View (only available when a Trend View is
active).
Yesterday Opens a window for selecting the data item for which the previous day’s data will
be displayed.
Table 92 History Monitor: Window Menu
Command Description
Cascade Arranges windows one on top of the other.
Tile Arranges windows in vertical rows.
Arrange icons Arranges minimized window icons.
Close All Closes all open windows.
Table 93 History Monitor: Help Menu
Command Description
About History Monitor Displays software version and copyright information.
22.2.11 History Monitor Toolbar

The toolbar is the fastest way of selecting the most frequently needed functions. A typical
toolbar contains the buttons listed in the following table.
Table 94 History Monitor Toolbar Buttons
Opens the New window for selecting whether to create a new Table View or Trend View
window.
Opens the Open window for opening the views saved on the local computer using the user
name you are logged in.
185
Opens the Save View As window for saving the created view for further viewing.
Immediately checks if data has changed and updates the data in all open views with the
changed data.
Moves to the beginning of the data in the view.
Moves to the previous page in the view.
Moves to the next page in the view.
Moves to the end of the data in the view.
22.3 Operating History Monitor

More information
‣ History Monitor User Interface (page 176)
22.3.1 Starting and Exiting Application

To exit the application, select File > Exit.
22.3.2 Creating New View

1. In the History Monitor main window, select File > New Frame, or click New on the
toolbar.
The New window is displayed.
186
2. In the New window, select the view type that you want to create and click OK.
An empty view frame is displayed.
3. To select which preconfigured query or data items are displayed in the view, in the main
window, select Edit > Data Item Selection.
The Data Item Selection window displays the configured available data items, or the
preconfigured queries.
4. In the Available Data Items list, select the data items or a preconfigured query, and
click the arrow button.
The selected items are moved to the Selected Data Items list. Click OK.
187
5. The selected data items are displayed in the view, either as columns in Table View and
Query View, or graphs in Trend View.
The following figure shows an example of Table view.
6. To save the view, select File > Save View As. In the Save View As window, enter a name
for the view and click OK.
The name appears in the title bar of the view window.
22.3.3 Opening Saved Views

You can open views that have been saved in the local computer using the same user name
that you are logged in with. To open a saved view:
1. Select File > New Frame, or click on the toolbar.
The New window is displayed.
2. In the New window, select the view type you want to open and click OK.
An empty view frame is displayed.
188
3. Select File > Open, or click the Open icon on the toolbar.
The Open window is displayed. The window displays the saved views of the type you
selected, and which have been saved on the local computer with the user name you
have logged on with.
4. Select the view or query that you want to open and click OK.
The selected view is displayed.
You can edit the opened view and save it with another name by selecting File > Save As. The
Save View As window opens displaying the old name. Enter the new name in the field and
click OK. For instructions on editing the view, see the following sections.
22.3.4 Changing Displayed Data Items

1. Select Edit > Data Item Selection. The Data Item Selection window is displayed.
2. Using the arrow buttons, add or remove the items selected and click OK.
3. If you want to save the view with the changed settings, select File > Save View As.
22.3.5 Displaying Data from Previous Day

When viewing "real-time" data in a Trend View, you can select to view the corresponding
data from the previous day next to the current data as reference. To open the data from the
previous day:
1. With the Trend View open, select Tools > Yesterday.
An item selection window is displayed.
2. In the window, select the parameter to be displayed and click OK.
The data from the previous day is displayed in the Trend View, using a dotted line and
different color from the original data. The name of the data item at the top of the view
contains the text REF, for example, MOR_12R_REF.
189
22.3.6 Refreshing Data in Views

By default, the data in the "real-time" views is not refreshed automatically. However, you can
refresh the data manually or select to refresh the data automatically.
To select automatic refreshing:
1. To automatically refresh the data, select View > Refresh.
When there is a selection mark next to this option, the views are refreshed
automatically at the pre-configured interval. Typically the interval is 60 seconds.
2. To manually refresh the data, select View > Refresh, or click the Refresh button.
The view is immediately updated with any changed data.
22.3.7 Changing Display Period

By default, data is displayed in the views from a preconfigured default period at the
preconfigured resolution, typically for one hour backwards with a 1‑minute resolution. You
can change the settings in the Options window. You can select to view data from either a
sliding period for a certain amount of time backwards from the present time, or for a fixed
period of time.
1. Select Tools > Options.

The Options window is displayed. The window shows the settings for the view that is
currently active.
2. If you want to display the data as "real-time", that is, a certain period backwards from
the present time, select Sliding. Then select the hours from the Hours list. You can also
enter another amount in hours.
The data will be updated during viewing so that it will always be from the selected
amount of hours backwards.
190
3. If you want to display data from a fixed period of time, select Fixed. Then click the
dates and times in the Start and End lists and using the up and down arrow buttons of
the keyboard select the desired date and time. You can also click the arrow button in
the lists which will open a calendar for selecting the date.
4. Click OK.
The settings are used the next time the data is refreshed.
22.3.8 Changing Display Resolution

By default, data is displayed in the views from a preconfigured default period at the
preconfigured resolution, typically for one hour backwards with a 1‑minute resolution. You
can change the settings in the Options window. You can select to view data from either a
sliding period for a certain amount of time backwards from the present time, or for a fixed
period of time.
1. Select Tools > Options.

The Options window is displayed. The window shows the settings for the view that is
currently active.
2. Select the data resolution from the Data resolution list or enter another resolution in
the field.
3. Click OK.
The settings are used the next time the data is refreshed.
191
For Trend Views the maximum period of time that can be displayed with 1‑minute
resolution is 24 hours. If this selection is exceeded, the system displays a warning
message. Select either a shorter period or lower resolution.
22.3.9 Editing Graphs in Trend Views

You can use several editing options for editing the appearance of the graphs in Trend Views.
Most of the options can be selected in the Graph Properties window. The window is
displayed when you select Edit > Graph Properties.
The Graph Properties window provides also advanced editing features that may not
necessarily be applied to current data.
When saving a Trend View after editing, the following is saved:

• Scale (minimum and maximum values shown)
• Axis colors (Trend line colors are not saved)
• Selected data items
• Paging selections
More information
‣ Graph Properties Window (page 182)
22.3.9.1 Changing the Scale
1. Select Edit > Graph Properties.

The Graph Properties window is displayed.
192
2. Select Chart > Axis > Scales.

3. In the Scales tab, remove the selection from the Automatic check box.
4. Click the Change buttons and enter new values for the maximum and/or minimum
values.
Make the selections separately for the left and right axis.
5. Click Close.
22.3.9.2 Changing Background Color

2. Select Chart > Panel > Background.
3. In the Background tab, click Color and select the new color for background.
4. Click Close.
22.3.9.3 Changing Trend Line Color

2. Select the Series tab.
3. Select the trend line that you want to edit from the list, and click Color to change the
color.
4. Click Close.
22.3.9.4 Adjusting Paging
By default, 60 data samples are plotted on each page in the Trend View. This means that for
any period longer than 1 hour (using 1‑minute resolution), the graph spreads over multiple
pages. To change this setting:
2. Select Chart > Paging.
3. in the Paging tab, select the amount of data points displayed in a page from the Points
per Page list.
For example:
• The default selection is 60 points, which means that with 1 minute resolution and
2 hour period, the data is divided into 2 pages.
• If you want the same data to be displayed in one page, select 120 points per page.
• If you want any data to be displayed in one page, select 0 points per page. However,
this selection does not often provide a clear presentation.
193
4. To show the page numbers, select Show Page Numbers.

5. Click Close.
22.3.9.5 Hiding/Showing Graphs
To hide a graph in a Trend View:
1. At the top of the Trend View, remove the selection from the check box next to the
graph name that you want to hide.
The graph will be hidden.
2. To show the graph again, select the check box again.
22.3.10 Moving and Zooming in Trend Views

22.3.10.1 Panning (Moving Around)
To move around the trend view area, click the right-hand button, keep it pressed down, and
move the mouse around the area.
If the data is divided between several pages in the view, you can move from one page to
another by clicking the navigation buttons in the toolbar. Clicking the Next button takes
you one step to the right and the Previous button to the left.
22.3.10.2 Zooming In
To zoom in, press down the mouse button, hold it down, and drag the pointer starting from
the upper left-hand corner across the area that you want to zoom in.
22.3.10.3 Zooming Out
To zoom out, press down the mouse button, hold it down, and drag the pointer starting from
the lower right-hand corner of the area.
22.3.11 Moving and Sorting in Table Views

You can use the keyboard keys and the navigation buttons in the toolbar to move in the
view.
• To move to the end of the view, press CTRL + END, or click the button.
• To move to the beginning, press CTRL + HOME, or click the button.
• To move upwards or downwards in the view, press the PAGEUP or PAGEDOWN key in
the keyboard, or click the and buttons in the toolbar. This provides a smoother
movement than using the scroll bars.
The items in the table view are displayed by default from the latest to the earliest. To sort
the items so that the earliest items are displayed first, click the Timestamp column.
22.3.12 Printing Views
1. To print a Table View or a Query View, select File > Print.
194
2. To print a Trend View:

a. In a Trend View, select Edit > Graph Properties.
b. In the Graph Properties window, select the Print tab.
c. In the Print tab, change the print settings as needed and click Print.
Figure 80 Printing Trend View
22.3.13 Viewing Several Windows at the Same Time

1. Open and/or create all the views that you wish to view.
2. From the Window menu, select Cascade or Tile.
All the opened views will be displayed.
3. Resize and arrange the windows to your liking. You can also save the layout.
More information
‣ Saving and Restoring Window Layout (page 195)
22.3.13.1 Saving and Restoring Window Layout

If you have opened several views and have resized and arranged them to your liking, you can
save the window layout by doing the following:
1. Make sure you have saved all the views in the arrangement.
2. Select File > Save layout.
The window layout is saved. Only one layout can be saved at a time.
3. If you close the windows or exit History Monitor, you can get back to the window
arrangement by selecting File > Restore layout.
195
22.4 Troubleshooting History Monitor

Table 95 Troubleshooting History Monitor
The New icon and menu item is not The system has just been started Wait for a while until the button
available. and is still reading the parameters. becomes active.
There is no connection to the Check the database settings and

database. contact system maintenance.
The Open window does not The window shows only the type of Select another view type in the
contain the view that you want to views selected in the New window, New window, or log in with a
open. and views created and saved in the different user name.
local computer using the user
name you have logged on with.
When trying to open a new view There are too many database Wait until the users quit their
the following message is displayed: users. The maximum amount of sessions and try again.
Server rejected the users is typically 5.
connection. There is no data
source displayed in the status bar.
Some of the parameter columns The columns may have been To see all columns, press CTRL + W.
are not visible. hidden because they have been
dragged over each other.
196
Chapter 23 – Dial-Up Manager
23. Dial-Up Manager
23.1 Introduction to Dial-up Manager
The Dial-up Manager application is a tool for configuring and using the dial-up
communication in the AviMet system. Dial-up Manager is included in the system only if the
optional dial-up communication feature is configured in the system.
Depending on the configuration, dial-up communication can be the default mechanism for
sending weather reports, either alone or with another data link. It can also be an option that
you can turn on, for example, when the primary communication link to send weather reports
fails.
23.2 Dial-up Manager User Interface

The Dial-up Manager user interface consists of the Dial-up Manager window.
Figure 81 Dial-up Manager Window
The elements in the Dial-up Manager window are described in the following sections.
197
The selections made in the Dial-up Manager window take effect only after clicking OK.
23.2.1 Destinations Frame
Table 96 Dial-up Manager Window Elements: Destinations Frame
Element Description
Destination name Shows the available destination names./Allows you to select the destination for
editing or removing it.
Phone numbers Shows the available phone numbers of the destination that is selected in the
Destination name box. / Allows you to select a phone number for editing or
removing it.
Add Opens the Add destination name or Add phone number window for adding a
destination or a phone number.
Edit Opens the Edit destination name or Edit phone number window for editing the
selected destination or phone number.
Remove Removes the selected destination name and/or phone number. Removing a
destination name removes all the numbers for that destination.
The phone numbers has to be in direct format, that is, the format that the modem dials, not
in international format with + sign. The use of special characters is dependent on the
modem used.
23.2.2 Messages Frame
Table 97 Dial-up Manager Window Elements: Messages Frame
Element Description
Dial-up messages Enables the dial-up connection for the selected report types.
enabled
Report types (for Allows you to select the report types being sent, from a preconfigured set of
example, METAR, SPECI, reports.
and TAF)
Select all Selects all report types to be sent using dial-up.
Unselect all Selects none of the report types to be sent using dial-up.
198
23.3 Operating Dial-up Manager

The Dial-up Manager application is used for turning on and off the dial-up communication
for sending weather reports. The destinations and their phone numbers can also be
managed with the application.
23.3.1 Turning on Dial-up Connection

Depending on the configuration, sending weather reports with the dial-up connection is
enabled or disabled by default. To turn the dial-up connection on:
1. In the Dial-up Manager application, check that the destination and phone numbers are
correct.
2. In the Messages frame, select Dial-up messages enabled.
3. Select the check boxes for all the report types that you want to send with the dial-up
connection. To select all types, click Select all.
4. Click OK.
The dial-up connection will be used to send the selected weather reports to the listed
destinations.
23.3.1.1 Calling Principles
Weather reports are sent to all the destinations displayed in the destination list. The phone
numbers for each destination are called in the order they are shown in the list until data
transmission to one of the numbers succeeds. By default, if none of the calls succeed, the
system starts calling the numbers again. The number of calling rounds depends on the
configuration of the system. The default number of rounds is three. If the calls do not
succeed, an event message is displayed in the Events panel in the Diagnostics application.
If the sending does not succeed, an event message is displayed in the Events panel in the
Diagnostics application. Windows Event Viewer logs all calling events.
23.3.2 Turning off Dial-up Connection

1. In the Messages frame, remove the check mark from the Dial-up messages enabled
check box.
2. Click OK.
The dial-up connection will not be used to send the reports any more.
Before turning off the dial-up connection, make sure another method is used for sending
the weather reports.
199
23.3.3 Adding New Destinations

1. Click Add below the Destination name list.
The Add destination name window is displayed.
2. Type the name of the new destination and click OK.
3. Select the new destination name that is displayed in the Destination name list.
4. Click Add below the Phone numbers list.
The Add phone number window is displayed.
5. Type the new phone number.
Use the direct format that the modem dials, do not use the international format with
the + sign. For information on special characters that can be used, see the modem
documentation.
6. Click OK.
The new phone number is displayed in the Phone numbers list, when the destination is
selected.
7. Add other phone numbers in the same way, if needed.
23.3.4 Editing Destination Names

1. Select the destination from the Destination name list.
2. Click Edit below the Destination name list. The Edit destination name window is
displayed.
3. Edit the name and click OK.
The new name is displayed in the Destination name list.
23.3.5 Editing Phone Numbers

2. Select the phone number to be edited from the Phone numbers list and click Edit
below the numbers.
The Edit phone number window is displayed.
3. Edit the number and click OK.
The new number is displayed in the Phone numbers list when the destination is selected.
23.3.6 Deleting Destination Name and Phone Number

2. Click Remove below the Destination name list.
The destination name and the phone numbers are removed from the list.
200
23.3.7 Deleting Phone Numbers

2. Select the phone number to be removed from the Phone numbers list and click
Remove below the numbers.
The selected phone number is removed from the list.
23.3.8 Viewing Modem Connections

You can view the dialing time, phone number, status, sent message type, and completion
time of the calls in the Windows Event Viewer. For more information, see the operating
system manuals or ask the system administrator.
The Events panel in the Diagnostics application displays a technical event message when
sending a report fails.
23.4 Troubleshooting Dial-up Manager

Table 98 Troubleshooting Dial-up Manager
A system event message in the There is a fault in the modem, the Check that the modem is
Diagnostics application indicates modem configuration, or the connected, the power is on, and
that a message was not sent. connection. the telephone line is working.
Contact system administrator for

checking the modem and dialing
properties.
Check Windows Event Viewer for

the cause for the fault or contact
maintenance.
There is a problem in the receiving Contact the receiving end to check.

end.
201
Appendix A. Software End

User License Agreement
All rights to any software are held by Vaisala or third parties. The customer is allowed to use
the software only to the extent that is provided by the applicable supply contract or
Software End Used License Agreement.
A.1 Vaisala AviMet Software End User

License Agreement
IMPORTANT!
READ THIS LICENSE AGREEMENT ("LICENSE") CAREFULLY BEFORE ACCESSING,
DOWNLOADING AND/OR USING THE SOFTWARE AND RELATED DOCUMENTATION, IF
ANY, (COLLECTIVELY, "SOFTWARE"). THIS LICENSE CONSTITUTES A LEGALLY BINDING
AGREEMENT BETWEEN YOU AND VAISALA ("LICENSOR" OR "VAISALA").IF YOU ACCESS,
DOWNLOAD OR USE THIS SOFTWARE, INCLUDING BY INSTALLING OR REQUESTING THE
INSTALLATION OF THE SOFTWARE, YOU ARE DEEMED TO HAVE ACCEPTED THIS
LICENSE AND AGREE TO BE BOUND BY ITS TERMS. IF YOU DO NOT AGREE TO THE
TERMS OF THIS LICENSE, YOU ARE NOT AUTHORIZED TO ACCESS, DOWNLOAD AND/OR
USE THIS SOFTWARE. THIS LICENSE REPRESENTS THE COMPLETE AGREEMENT
CONCERNING THE SOFTWARE, AND IT SUPERSEDES ANY PRIOR AGREEMENT,
REPRESENTATION, OR UNDERSTANDING BETWEEN THE PARTIES.
1. Product. The Software means a single copy, in object code format, of the AviMetâ
software used with or to control Vaisala sensors and created by Vaisala for use on a
single computer.
2. Grant. This Software is licensed, not sold, to you by Licensor. Licensor grants to you,
and you hereby accept, a nonexclusive, nontransferable limited right to access, obtain,
download, install, and use a copy of this Software only for the purpose of operating,
collecting data from, displaying, and controlling Vaisala equipment that you possess.
You are not permitted, under this License, to copy, distribute, make generally available,
sublicense or transfer, in any manner, in whole or in part, the Software, except as
otherwise provided herein. You are authorized to make one copy of the Software only
for archival purposes and for no other purposes. The Software is the subject of
international copyright laws and treaties and of this License. All notices included in the
Software shall remain intact and unaltered and shall be included on all copies of the
Software that you make. Licensor specifically reserves all rights and interests not
expressly granted in this License.
202
Appendix A – Software End User License Agreement
3. Restrictions. You may not copy, modify, alter, change, create derivative works or
incorporate this Software with any other software, products, services or systems,
except as authorized herein. You may not rent, lease, loan, time share, license, disclose,
disseminate, distribute or otherwise make accessible or available or network the
Software to any third party. You agree not to reverse engineer, reverse compile,
decompile or disassemble or otherwise translate the Software. If you breach any term
or condition of this License, this License shall immediately terminate and you shall
immediately erase the Software and any copies thereof, from all computers and devices
on which the Software has been installed and immediately cease any further use or
possession of the Software. You agree that Licensor shall have right to audit your use of
the Software.
4. Term and Consideration. This License is effective upon your acceptance of this License
as demonstrated by your accessing, downloading and/or using the Software, and shall
continue in effect unless earlier terminated due to your breach or entering into another
agreement with Licensor for so long as you or your successor continues to possess
Vaisala equipment that may be operated, controlled, and/or displayed by the Software.
You agree that, in the event and at such time as you no longer own any Vaisala
equipment that may be controlled by the Software, or in the event of other termination,
you shall immediately erase the Software and any copies thereof from all computers
and devices on which the Software has been installed and immediately cease any
further use or possession of the Software. You agree that if you fail to comply the terms
and conditions of this License, Licensor may terminate the License and you shall return
or destroy all copies of the Software, as requested by the Licensor.
5. Disclaimers and Limited Warranty. THE SOFTWARE IS PROVIDED "AS IS" AND
LICENSOR DISCLAIMS ANY AND ALL WARRANTIES AND CONDITIONS, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO, ANY WARRANTIES OF
NONINFRINGEMENT, THE IMPLIED WARRANTIES AND CONDITIONS OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE OF THE SOFTWARE.
LICENSOR DOES NOT WARRANT THAT THE SOFTWARE IS FREE OF CLAIMS FOR
INFRINGEMENT, THAT THE FUNCTIONS CONTAINED IN THE SOFTWARE WILL MEET
YOUR REQUIREMENTS, OR THAT IT IS SUITABLE FOR ANY LICENSED APPLICATION.
FURTHER, LICENSOR DOES NOT WARRANT THAT THE OPERATION OF THE
SOFTWARE WILL BE UNINTERRUPTED OR ERROR-FREE, THAT IT IS FREE OF ANY
OMISSION, INACCURACY, DEFECT, COMPUTER VIRUS, OR OTHER OPERATIONAL OR
PERFORMANCE PROBLEM, OR THAT DEFECTS IN THE SOFTWARE WILL BE
CORRECTED. YOU WILL BE RESPONSIBLE FOR ADEQUATELY SAFEGUARDING (SUCH
AS BY BACKING UP) YOUR DATA AND OTHER SOFTWARE USED IN CONJUNCTION
WITH THE SOFTWARE. LICENSOR ASSUMES NO LIABILITY FOR ANY CORRUPTION,
ERASURE, MISHANDLING, OR THE LIKE OF YOUR DATA OR OTHER SOFTWARE. NO
ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY LICENSOR OR AN
AUTHORIZED LICENSOR REPRESENTATIVE SHALL CREATE A WARRANTY OR IN ANY
WAY INCREASE THE SCOPE OF THIS WARRANTY. SOME JURISDICTIONS DO NOT
ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY
NOT APPLY TO YOU. ADDITIONALLY, YOU ACKNOWLEDGE RECEIVING NO
WARRANTY, EXPRESS OR IMPLIED, FROM ANY THIRD PARTY, INCLUDING THE
OWNER OF THE SOFTWARE, AS TO THE SOFTWARE OR THIS LICENSE.
203
6. Limitation of Liability. THE DISCLAIMER OF WARRANTIES RECITED ABOVE IS FOR THE

PURPOSE OF LIMITING LICENSOR'S LIABILITY FOR ANY DAMAGES OR HARM
SUFFERED BY YOU OR A THIRD PARTY, WHETHER FOR BREACH OF CONTRACT, AN
ACTION IN TORT (INCLUDING STRICT LIABILITY), NEGLIGENCE, INFRINGEMENT, OR
UNDER ANY OTHER CAUSE OF ACTION OR CAUSED BY ANY THIRD PARTY
SUPPLIERS OF ASSOCIATED SOFTWARE AND/OR SOFTWARE COMPONENTS
INCLUDED IN THE SOFTWARE. LICENSOR SHALL NOT BE HELD LIABLE FOR ANY
SUCH CLAIMS OR ACTIONS, AND THE RISK OF HARM FROM THE FOREGOING RESTS
ENTIRELY WITH YOU. FURTHER, IN NO EVENT WILL LICENSOR BE LIABLE FOR ANY
DAMAGES, INCLUDING, WITHOUT LIMITATION, INCIDENTAL, SPECIAL, INDIRECT,
PUNITIVE OR CONSEQUENTIAL DAMAGES, INCLUDING WITHOUT LIMITATION, LOST
PROFITS OR REVENUES OR LOSS OF BUSINESS ARISING OUT OF OR RELATING TO
THE USE OF OR INABILITY TO USE THE SOFTWARE EVEN IF LICENSOR HAS BEEN
INFORMED OF THE POSSIBILITY OF SUCH LOSSES. SOME JURISDICTIONS DO NOT
ALLOW SUCH LIMITATION OF DAMAGES, SO THE ABOVE EXCLUSION MAY NOT
APPLY TO YOU. IN NO EVENT SHALL LICENSOR'S LIABILITY TO YOU FOR ANY CLAIM
OF DAMAGES, LOSSES AND CAUSES OF ACTIONS WHETHER IN CONTRACT, TORT
(INCLUDING LICENSOR'S OWN NEGLIGENCE), INFRINGEMENT, OR UNDER ANY
OTHER LEGAL THEORY (INCLUDING STRICT LIABILITY) EXCEED THE PURCHASE/
LICENSE PRICE OF THE SOFTWARE. YOU ACKNOWLEDGE THAT THE FOREGOING
CONSTITUTES YOUR SOLE AND EXCLUSIVE REMEDY FOR BREACH BY LICENSOR OF
THIS LICENSE OR ANY WARRANTIES MADE HEREUNDER.
7. Damages for Breach. In the event of breach of any of the proprietary rights or interests,
Licensor shall be entitled to pursue all appropriate legal and equitable relief and shall
be entitled to recover, in addition to any other relief granted, reasonable attorney fees
and expenses of litigation.
8. Third Party Software. To the extent any software or other technology that is owned by a
third party is accessed or used in combination with the Software, you shall be obligated
to obtain a license or rights to such third-party software or technology before Software
access, delivery, or use and you assume the entire responsibility and liability therefore,
including any associated costs and expenses. Licensor shall not be obligated to obtain
on your behalf any rights or licenses to such third-party software or technology.
9. Export Law Assurances. You agree to comply with all applicable export laws, including
those of the jurisdiction in which the Software was obtained.
10. Controlling Law and Severability. These Conditions shall be construed, governed and
interpreted in accordance with the laws of Finland, excluding its conflict of laws rules
thereof. It is expressly agreed that the application of United Nations Convention on
Contracts for the International Sale of Goods (CISG) shall be excluded. Any dispute,
controversy or claim arising out of or relating to this Contract between Vaisala and the
customer, which cannot be solved by amicable means shall be submitted to arbitration.
Any dispute, controversy or claim arising out of or relating to this Contract, or the
breach, termination or validity thereof shall be finally settled by arbitration in
accordance with the Arbitration Rules of the Finnish Central Chamber of Commerce.
The Arbitral Tribunal shall consist of one (1) arbitrator. The arbitrator shall be appointed
in accordance with the Arbitration Rules of the Finnish Central Chamber of Commerce.
The award shall be final and enforceable in any court of competent jurisdiction. The
arbitration shall be held in Helsinki, Finland, and be conducted in English.
204
Appendix A – Software End User License Agreement
11. Support, Maintenance, Releases. Licensor shall not be obligated to provide you with
any support, consulting or maintenance for the Software under this License. Licensor,
further, shall not be obligated to provide you with any Modifications under this License.
In the event that Licensor, at its sole discretion, provides Modifications, the terms and
conditions of this Agreement shall apply to both the Modifications and the modified
Software. If the withdrawal from Software is based on an infringement claim, or if
Licensor no longer has the rights to use or distribute the Software, you will suspend
from further use of the Software.
12. Transfer. You shall not transfer, assign or hypothecate, in whole or in part, this License
or any rights or obligations hereunder. If you transfer the rights against this License, the
assignees and successors shall be bound by the terms and conditions herein.
13. Intellectual Property. Licensor represents and you agree that the Software, including
source and object code, is confidential and proprietary to Licensor. All confidentiality
and proprietary notices, including but not limited to copyright notices displayed on the
Software, shall remain intact and unaltered and shall be included on any documents,
media, printouts, visualizations, or on any other electronic or tangible expressions
associated with, related to, or derived from the Software. You acknowledge that
Licensor has the full right, title, and interest in and to all associated, related, and
resultant intellectual property, which includes but is not limited to patents, trade
secrets, trademarks, or copyrights, including any and all derivative works thereof, to the
Software and Modifications. You acknowledge that the licensing of the Software does
not grant to you, either implicitly or explicitly, a license to any patent, copyright,
trademark, or other intellectual property interest.
205
Glossary
Glossary
acknowledge
Clicking the ACK button in order to inform the system that you have seen an event
message in the Diagnostics application.
AD WRNG
An optional AviMet application for sending Aerodrome Warning reports.
AFTN Addressee Manager
An AviMet application for configuring the addressee part of the AFTN address and
which reports are sent to the addressees.
AFTN line
Aeronautical Fixed Telecommunication Network line.
AFTN Monitor
An AviMet application for viewing reports in the format they were sent to the AFTN
line.
AIRMET
An optional AviMet application for editing and sending AIRMET reports.
alarm message
A Diagnostics system event message with ALARM or WARNING status. A sign of
serious system problems.
AMHS
ATS Message Handling System
AMHS Monitor
An optional AviMet application for viewing the latest report sent to the AMHS server
and the status of the server and connection.
ASCII Log View
An AviMet application for viewing stored data in text files.
audiovisual alarms
Optional function. Sound and color signals activated in the WeatherView application
when there is a predefined change in the weather.
automatic data fields
Data fields that the system fills in automatically in METAR/SPECI template. See also
manual data fields.
backup data status
A data status shown in WeatherView data fields with a yellow background color. It
indicates that the data is provided by a backup sensor.
backup sensor
A sensor that can be used to provide the system with weather data when the primary
sensor is out of order or being calibrated.
207
calculated data
Weather parameters that the Central Data Unit (CDU) produces through calculations,
in contrast to measured data. Calculated data is based on measured data.
CDU
Central data unit, a computer that processes sensor data. The AviMet system can
include one or two CDUs.
configuration
See system configuration.
current data
Weather data measured by sensors and shown in AviMet applications, in contrast to
stored data.
Database Reporting Tool
An optional AviMet application for creating reports and graphs from weather data that
is saved in the optional database.
Data Source Manager
An AviMet application for selecting the data source for pressure and prevailing
visibility values.
data status
The source and quality of weather data, indicated in WeatherView by colors. Data
status in WeatherView can be Backup, Invalid, Manual, Missing, Normal, or Old. In the
METAR/SPECI template, data status can be normal or missing.
Diagnostics
An AviMet application for monitoring system status and events.
duplicated system
An AviMet system that has two CDUs: one active and one passive (hot standby). Other
system types are single-CDU system with or without workstations.
event
A system event notified by the AviMet system with a message in the Diagnostics
application. An event can be, for example, a problem in the system or a notice of a
sent weather report.
FWS
Forecaster workstation in the AviMet system.
GAMET
An optional AviMet application for editing and sending GAMET reports.
History Monitor
An optional AviMet application for viewing archived data from the database.
invalid data status
A data status displayed in the weather data fields in the WeatherView application. The
background color of the field is red. This status indicates that the data is not valid due
to sensor or system problems.
208
Glossary
IWXXM
ICAO meteorological information exchange model. The Vaisala AviMet AWOS system
supports dissemination of data reported in METAR/SPECI and TAF using the IWXXM
XML schema.
Lightning display
An AviMet view displaying the lightning warning data.
maintenance personnel
Personnel at the airport responsible for taking care of the general functioning of the
AviMet system. At some airports, observers may take part in the maintenance tasks.
manual data fields
Data fields that are filled in manually in the METAR/SPECI template in contrast to
automatic data fields which are filled in by the system. Used when there is no sensor
available for measuring the data, or when the sensor is out of order and no backup
sensor is available.
manual data status
A data status shown in in the WeatherView application with a yellow background
color in data fields. Indicates that the data is not coming from a sensor, but is updated
manually by the user.
manual observations
In some systems weather observations can be entered manually in the Manual
observations tab, which is typically part of the Reports application, when the system
does not include the sensor for measuring the data.
measured data
Weather parameters that the sensors measure directly, in contrast to calculated data.
Measured data can be used as the basis of producing calculated data.
measurement site
See site.
Message Notification
A message type in the Diagnostics application.
METAR/SPECI template
Template in the Reports application for editing and sending METAR/ SPECI reports.
missing data status
A data status displayed in the weather data fields in the WeatherView application with
slashes in the data fields. Indicates that there is no data coming from the sensor due
to sensor or system problems.
normal data status
background color of the field is gray. Indicates that the data is valid and the system is
functioning normally.
209
old data status

background color of the field is white. This status indicates problems in sensor
communication.
operational event
A message type in the Diagnostics application.
optional application
An optional application or function in the AviMet system that is not included in the
standard configuration.
OWS
Observer workstation in the AviMet system.
prevailing visibility
Visibility value used, for example, in METAR as defined in ICAO Annex 3. If prevailing
visibility is calculated using automatic sensor values, each measurement is handled as
representing a certain area of the aerodrome. Weight values are used for defining the
proportional area that the individual sensor has of the total area.
primary sensor
The sensor that provides the system with weather data in normal conditions. See also
backup sensor.
processed data
Weather data that is measured by sensors and processed before it is shown in AviMet
applications, in contrast to raw sensor data.
raw sensor data
Weather data measured by sensors and shown in the AviMet system without
significant modifications, in contrast to processed data.
Reports application
An AviMet application that typically contains the weather report templates, for
example, METAR/SPECI reports, and MET REPORT/SPECIAL.
Runway Configuration
An AviMet view for setting and selecting the runway-in-use information when it is not
provided by an external system.
Runways display
A view in the WeatherView application for changing the runway-in-use information
when the automatic runway-in-use information from an external system is temporarily
not available.
SIGMET
An optional AviMet application for editing and sending SIGMET reports.
site
Observation site, such as an automatic weather station or an airport site. Alternatively,
the location at which weather data is measured.
210
Glossary
SNOWTAM
An optional AviMet application for editing and sending SNOWTAM reports. See
Vaisala AviMetâ Runway Friction Application (SNOWTAM) User Guide.
sound alarms
An optional feature in several AviMet applications.
standard observation time
In the METAR/SPECI template, the moment when the system feeds measurement data
into the METAR/SPECI template. Standard observation time + editing time = METAR
sending time.
stored data
Data that the system stores in ASCII Log View, in contrast to current data.
SWIM
System wide information management.
SYNOP
An optional AviMet application for editing and sending SYNOP reports. See Vaisala
AviMetâ Synoptic Observations Software SYNOP User Guide.
system configuration
The way AviMet systems are customized during system delivery.
system delivery
The installation and configuration of the AviMet system by Vaisala. During the delivery,
the system is customized to meet the local requirements.
system maintenance applications
Applications used by maintenance personnel for their tasks, mainly Diagnostics and IO
Terminal.
TAF
An optional AviMet application for editing and sending TAF reports.
technical event
A message in the Diagnostics application indicating sensor problems in the system.
weather data
Weather parameter values in WeatherView and METAR/SPECI template, in contrast to
system data.
weather data screen
A screen in the WeatherView application displaying weather data that is updated
several times a minute.
WeatherView
An AviMet application for viewing current weather data.
workstation
A PC with a set of AviMet applications. Different workstations may include different
applications and functions.
WS WRNG
An optional AviMet application for sending windshear warning reports.
211
Index
A send AIRMET reports....................................................113
Actuals view....................................................................... 158 air-traffic controllers
Actuals view, description software applications.................................................... 18
introduction................................................................... 158 using WeatherView.......................................................46
user interface.................................................................158 WeatherView user interface....................................... 28
Actuals view, how to workstation types.......................................................... 23
activate backup sensor...............................................159 AMHS Monitor
enter manual data........................................................ 159 troubleshooting............................................................140
AD WRNG (Aerodrome Warning) AMHS Monitor, description
troubleshooting............................................................ 120 introduction................................................................... 138
AD WRNG (Aerodrome Warning), description user interface.................................................................138
introduction.................................................................... 116 application icons................................................................. 27
user interface..................................................................116 applications, end-user........................................................18
AD WRNG (Aerodrome Warning), how to applications, maintenance............................................... 22
cancel reports.................................................................119 archived files.......................................................................147
send reports....................................................................119 ASCII Log View
AFTN Addressee Manager troubleshooting.............................................................157
troubleshooting.............................................................137 ASCII Log View, description
AFTN Addressee Manager, description ASCII Log View window............................................. 148
introduction....................................................................132 events screen................................................................ 150
user interface................................................................. 133 history file names......................................................... 152
AFTN Addressee Manager, how to introduction................................................................... 147
add addressees............................................................. 136 status............................................................................... 149
edit addressee groups.................................................137 user interface.................................................................147
edit addressees.............................................................136 weather parameter screen........................................ 149
exit application..............................................................135 ASCII Log View, how to
select message types.................................................. 136 back up files...................................................................156
start application............................................................135 hide rows.........................................................................155
AFTN Addressee Manager user interface...................133 refresh data automatically......................................... 155
AFTN Monitor refresh data manually..................................................155
troubleshooting............................................................. 131 select rows......................................................................155
AFTN Monitor, description show rows ......................................................................156
introduction................................................................... 126 unhide rows ...................................................................156
message formats.......................................................... 129 view history files........................................................... 152
user interface.................................................................126 view several windows at the same time................ 154
AFTN Monitor, how to ATC displays.........................................................................29
change sequence number......................................... 130
copy report text............................................................130 C
view sent reports..........................................................130 compliance........................................................................... 24
AIRMET configuration........................................................................ 18
troubleshooting............................................................. 115
AIRMET, description D
buttons............................................................................. 113 data fields in WeatherView...............................................31
data fields........................................................................ 112 data input windows........................................................... 69
final report field............................................................. 112 data source in Actuals view............................................158
introduction..................................................................... 111 Data Source Manager
source............................................................................... 112 troubleshooting............................................................ 175
user interface...................................................................111 Data Source Manager, description
AIRMET, how to Data Source Manager window..................................163
cancel reports.................................................................114 introduction................................................................... 163
PV Group Manager window...................................... 168
sensor weight................................................................ 169
212
Index
user interface.................................................................163 software applications.................................................... 18

validity limit................................................................... 170 TAF user interface...........................................................91
Data Source Manager, how to using AD WRNG (Aerodrome Warning).................118
change active data source.......................................... 171 using AFTN Monitor.................................................... 130
disable or enable data source................................... 172 using AIRMET................................................................. 113
exit application............................................................. 170 using ASCII Log View.................................................. 152
manage prevailing visibility groups.........................173 using GAMET.................................................................109
start application............................................................170 using SIGMET................................................................ 104
use manual values......................................................... 171 using TAF......................................................................... 96
data status in ASCII Log View....................................... 149 using WS WRNG (Windshear Warning)................ 123
data status in WeatherView..............................................31 workstation types.......................................................... 23
delivery...................................................................................18 WS WRNG (Windshear Warning) user interface..121
Diagnostics FWS (forecaster) workstation.........................................23
troubleshooting............................................................ 146
Diagnostics, description G
Events panel.................................................................. 142 GAMET
event types............................................................ 142, 143 troubleshooting.............................................................110
introduction.................................................................... 141 GAMET, description
stored events................................................................. 145 introduction...................................................................106
user interface..................................................................141 menu bar........................................................................ 108
Diagnostics, how to report types...................................................................109
acknowledge events................................................... 144 user interface................................................................ 106
exit application............................................................. 144 GAMET, how to
monitor events..............................................................144 send delayed reports.................................................. 109
start application........................................................... 144 send normal reports....................................................109
view stored event messages..................................... 145 GAMET user interface......................................................106
Diagnostics user interface............................................... 141 graphical fields in WeatherView.................................... 40
Dial-up Manager
troubleshooting............................................................ 201 H
Dial-up Manager, description history files..........................................................................147
introduction................................................................... 197 History Monitor
user interface................................................................. 197 troubleshooting............................................................ 196
Dial-up Manager, how to History Monitor, description
add new destinations................................................ 200 Data Item Selection window..................................... 179
deleting destination name and phone number..200 Extremes window.........................................................183
deleting phone numbers............................................201 Graph Properties window.......................................... 182
editing destination names........................................200 introduction................................................................... 176
editing phone numbers.............................................200 menu bar........................................................................ 184
select reports to be sent............................................ 199 New window.................................................................. 178
turn off dial-up..............................................................199 Open window................................................................ 179
turn on dial-up.............................................................. 199 Options window........................................................... 180
Query View.....................................................................178
E Table View...................................................................... 178
editing reports, see reports Trend View......................................................................177
exiting applications............................................................26 user interface................................................................. 176
History Monitor, how to
F change displayed data items.................................... 189
forecasters change display period................................................ 190
AD WRNG (Aerodrome Warning) user interface. 116 change resolution..........................................................191
AFTN Monitor user interface.....................................126 create new views.......................................................... 186
AIRMET user interface...................................................111 display data from previous day................................189
ASCII Log View user interface...................................147 edit graphs..................................................................... 192
GAMET user interface................................................. 106 move in Table Views.................................................... 194
SIGMET user interface..................................................101 open saved views......................................................... 188
213
refresh data in views................................................... 190 stored data...................................................................... 88

restore window layout................................................ 195 user interface.................................................................. 66
view several windows at the same time................ 195 METAR/SPECI, how to
change data sources..................................................... 87
I change SPECI limits.......................................................87
ICAO recommendations................................................... 24 correct reports................................................................85
international recommendations..................................... 24 edit before editing time................................................ 81
introduction to AviMet....................................................... 16 send automated reports.............................................. 86
send delayed reports....................................................84
L send METAR reports..................................................... 82
license agreement............................................................202 send SPECIAL reports.................................................. 82
light intensity........................................................................ 51 send SPECI reports.................................................82, 86
lightning display................................................................. 56 troubleshooting..............................................................89
Lightning display, description view sent reports........................................................... 88
Active Alarms view....................................................... 60 METAR reports.................................................................... 65
configuration.................................................................. 64 MET Data View.................................................................... 42
EFM view.......................................................................... 59 MET Display..........................................................................42
Electric Field view..........................................................59 MET REPORT reports........................................................ 65
introduction.....................................................................56
Lightning View................................................................58 N
sound alarm..................................................................... 57 names of history files....................................................... 152
user interface.................................................................. 56
Lightning display, how to O
configure alarms............................................................60 observer displays............................................................... 30
configure connection settings....................................63 opening weather data screens....................................... 46
define activity levels..................................................... 63 operating
define settings................................................................60 exiting applications....................................................... 26
edit lightning alarms..................................................... 62 logging in......................................................................... 26
lightning warning............................................................... 56 starting applications..................................................... 26
local routine reports.......................................................... 65 operating, general
logging in..............................................................................26 user interface...................................................................27
outbound messages in AFTN Monitor........................ 129
M OWS (observer) workstation...........................................23
maintenance applications................................................ 22
maintenance workstation.................................................23 R
METAR/SPECI radar warnings.....................................................................37
buttons..............................................................................73 RCM (maintenance) workstation....................................23
data fields........................................................................ 68 regulatory compliances.................................................... 24
final code field................................................................. 71 related manuals....................................................................13
input selection................................................................. 71 reports
source selection...............................................................71 Aerodrome Warning.....................................................119
validator field.................................................................. 72 AIRMET.............................................................................113
METAR/SPECI, description GAMET, delayed........................................................... 109
audio notifications.........................................................79 GAMET, normal............................................................. 109
editing and sending times.......................................... 80 METAR, automated....................................................... 86
input selection................................................................ 77 METAR, delayed............................................................. 84
introduction.....................................................................65 METAR, normal............................................................... 82
manual observations.................................................... 80 MET REPORT, automated............................................86
notifications pane.......................................................... 75 MET REPORT, delayed..................................................84
report tabs.......................................................................68 MET REPORT, normal....................................................82
settings............................................................................. 76 SIGMET............................................................................104
Setup tab..........................................................................75 SPECI, automated..........................................................86
SPECIAL limits................................................................ 78 SPECI, normal.......................................................... 82, 86
SPECI limits......................................................................78 SPECIAL, automated.................................................... 86
214
Index
SPECIAL, normal............................................................ 82 S
TAF, canceled..................................................................99 sending reports, see reports
TAF, delayed....................................................................98 Sensor Selector, description
TAF, normal......................................................................97 introduction.................................................................... 161
Windshear Warning..................................................... 123 user interface..................................................................161
Reports application............................................................ 91 Sensor Selector, how to
buttons..............................................................................73 disable data use............................................................162
data fields........................................................................ 68 enable data use.............................................................162
final code field................................................................. 71 SIGMET
input selection................................................................. 71 troubleshooting............................................................105
source selection...............................................................71 SIGMET, description
troubleshooting..............................................................89 buttons............................................................................103
validator field.................................................................. 72 final report field............................................................ 102
Reports application, description introduction.................................................................... 101
audio notifications.........................................................79 source.............................................................................. 102
editing and sending times.......................................... 80 user interface..................................................................101
input selection................................................................ 77 SIGMET, how to
introduction.....................................................................65 send reports.................................................................. 104
manual observations.................................................... 80 SIGMET user interface...................................................... 101
notifications pane.......................................................... 75 software applications on workstations.........................23
report tabs................................................................ 68, 93 SPECIAL reports................................................................. 65
settings............................................................................. 76 SPECI reports.......................................................................65
Setup tab..........................................................................75 starting applications..........................................................26
SPECIAL limits................................................................ 78 stored data in ASCII Log View....................................... 147
SPECI limits......................................................................78 system configuration..........................................................18
stored data...................................................................... 88 system delivery.................................................................... 18
user interface............................................................ 66, 91 system maintenance applications..................................22
Reports application, how to
change audio notification settings........................... 87 T
change data sources..................................................... 87 TAF
change SPECI limits.......................................................87 troubleshooting............................................................100
correct reports................................................................85 TAF, description
disable/enable audio notifications............................87 buttons............................................................................. 94
edit before editing time................................................ 81 final report field..............................................................93
recall pending report............................................. 85, 98 introduction......................................................................91
send automated reports.............................................. 86 notifications pane.......................................................... 95
send corrected reports..........................................85, 98 Report tab........................................................................93
send delayed reports....................................................84 report types.....................................................................96
send METAR reports..................................................... 82 Setup tab......................................................................... 96
send MET REPORT reports..........................................82 user interface................................................................... 91
send SPECI reports.................................................82, 86 TAF, how to
view sent reports........................................................... 88 cancel reports................................................................. 99
Runway Configuration, description correct reports................................................................98
introduction..................................................................... 53 send delayed reports....................................................98
user interface.................................................................. 53 send normal reports......................................................97
Runway Configuration, how to TAF user interface............................................................... 91
define non-standard configuration...........................54 trademarks............................................................................ 15
define runway availability............................................54 troubleshooting
select predefined configuration.................................53 AD WRNG (Aerodrome Warning)........................... 120
runway-in-use....................................................... 44, 50, 53 AFTN Addressee Manager......................................... 137
Runways display.................................................................44 AFTN Monitor................................................................. 131
AIRMET.............................................................................115
AMHS Monitor...............................................................140
ASCII Log View..............................................................157
215
Data Source Manager.................................................. 175 display modes.................................................................45

Diagnostics.................................................................... 146 graphs.........................................................................40, 41
Dial-up Manager........................................................... 201 instant values.................................................................. 32
GAMET............................................................................. 110 introduction.....................................................................28
History Monitor............................................................. 196 light intensity..................................................................44
METAR/SPECI................................................................. 89 lightning display.............................................................42
Reports application.......................................................89 missing values.................................................................32
SIGMET............................................................................105 night mode...................................................................... 45
TAF...................................................................................100 notifications.....................................................................37
WeatherView....................................................................51 observer displays...........................................................30
WS WRNG (Windshear Warning)............................125 radar warnings................................................................ 37
reports...............................................................................37
U runway-in-use..........................................................32, 44
user interface....................................................................... 27 Runways display............................................................ 44
AD WRNG (Aerodrome Warning)............................ 116 tendency indicators...................................................... 34
AFTN Addressee Manager, description..................133 thunderstorm graph......................................................42
AFTN Monitor................................................................ 126 user interface.................................................................. 28
AIRMET..............................................................................111 wind components.......................................................... 35
AMHS Monitor............................................................... 138 wind rose..........................................................................36
application icons............................................................ 27 WeatherView, how to
ASCII Log View..............................................................147 acknowledge alerts....................................................... 47
Data Source Manager..................................................163 acknowledge notifications.......................................... 47
Diagnostics......................................................................141 adjust graph fields.........................................................48
Dial-up Manager........................................................... 197 change time span.......................................................... 48
GAMET............................................................................ 106 configure graph properties.........................................48
general.............................................................................. 27 enter light intensity manually......................................51
History Monitor............................................................. 176 hide graph lines..............................................................48
METAR/SPECI................................................................. 66 monitor weather data...................................................47
Reports application.................................................66, 91 set runway-in-use manually....................................... 50
Sensor Selector..............................................................161 switch between views.................................................. 46
SIGMET.............................................................................101 use trace...........................................................................48
TAF......................................................................................91 view exact values in graphs........................................ 48
WeatherView...................................................................28 wind rose.............................................................................. 36
WS WRNG (Windshear Warning).............................121 WMO recommendations.................................................. 24
user profiles..........................................................................23 workstation types...............................................................23
WS WRNG (Windshear Warning)
V troubleshooting............................................................ 125
viewing history files in ASCII Log View....................... 152 WS WRNG (Windshear Warning), description
viewing reports in AFTN Monitor................................. 130 introduction.................................................................... 121
user interface..................................................................121
W WS WRNG (Windshear Warning), how to
weather data fields............................................................. 31 cancel reports................................................................124
WeatherView send reports................................................................... 123
troubleshooting...............................................................51 WS WRNG (Windshear Warning) user interface...... 121
WeatherView, description WV (WeatherView) workstation.................................... 23
alert frame........................................................................33
ATC displays.................................................................... 29
average values................................................................ 32
buttons............................................................................. 44
crosswinds....................................................................... 35
data status........................................................................ 31
data status colors............................................................31
day mode......................................................................... 45
dimmed data................................................................... 32
216
Technical support
Contact Vaisala technical support at helpdesk@vaisala.com. Provide at least the following
supporting information as applicable:
• Product name, model, and serial number
• Software/Firmware version
• Name and location of the installation site
• Name and contact information of a technical person who can provide further
information on the problem
For more information, see www.vaisala.com/support.
Warranty
For standard warranty terms and conditions, see www.vaisala.com/warranty.
Please observe that any such warranty may not be valid in case of damage due to normal wear and tear,
exceptional operating conditions, negligent handling or installation, or unauthorized modifications. Please
see the applicable supply contract or Conditions of Sale for details of the warranty for each product.
Recycling
Recycle all applicable material.
Follow the statutory regulations for disposing of the product and packaging.
217
www.vaisala.com

AviMet AWOS - User's Guide - English - M210881EN-V

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AviMet AWOS - User's Guide - English - M210881EN-V

Uploaded by

Copyright:

Available Formats

M210881EN-V

Visit our Internet pages at www.vaisala.com.

4.3.8 Adjusting Graph Fields.............................................................................. 48

11. AIRMET................................................................................................................ 111

12.3 Operating AD WRNG Template...................................................................... 118

13. WS WRNG......................................................................................................... 121

14. AFTN Monitor..................................................................................................126

15. AFTN Addressee Manager.........................................................................132

16. AMHS Monitor.................................................................................................138

17. Diagnostics....................................................................................................... 141

17.2 Diagnostics User Interface...............................................................................141

18. ASCII Log View...............................................................................................147

19. Actuals............................................................................................................... 158

20. Sensor Selector............................................................................................... 161

21. Data Source Manager.................................................................................. 163

21.4 Operating the Data Source Manager Application....................................... 170

22. History Monitor...............................................................................................176

23. Dial-Up Manager............................................................................................ 197

Appendix A: Software End User License Agreement.......................... 202

Technical support........................................................................................... 217

Figure 48 TAF Setup Tab................................................................................................... 96

Table 53 AFTN Monitor: Window Menu....................................................................... 128

1. About This Document

Table 1 Document versions (English)

Document Code Date Description

M210881EN-U April 2019 Applicable for Vaisala AviMetâ Automated Weather

M210881EN-T August 2018 Applicable for Vaisala AviMetâ Automated Weather

Document Code Name

M210881EN Vaisala AviMetâ Automated Weather Observing System User Guide

M210882EN Vaisala AviMetâ Automated Weather Observing System Maintenance Manual

M210885EN Vaisala AviMetâ Low-Level Windshear Alert System User Guide

M210886EN Vaisala AviMetâ Low-Level Windshear Alert System Maintenance Manual

M210887EN Vaisala AviMetâ Runway Visual Range System User Guide

M210888EN Vaisala AviMetâ Runway Visual Range System Maintenance Manual

M210842EN Vaisala AviMetâ Synoptic Observations Software SYNOP User Guide

M210851EN Vaisala AviMetâ Runway Friction Application (SNOWTAM) User Guide

M210848EN Vaisala AviMetâ Climatological Observations Software (CLIMAT) User Guide

M210849EN Vaisala AviMetâ Database Reporting Tool User Guide

M211032EN Vaisala AviMetâ Vertical Windshear Detection System User Guide

Note highlights important information on using the product.

Tip gives information for using the product more efficiently.

Lists tools needed to perform the task.

Figure 1 Typical Vaisala AviMet AWOS System

2.2 AviMet Product Platform

CAUTION! System configuration is only allowed by authorized Vaisala personnel.

2.4 Use of Anti-Virus Software

2.5 End-user Software Applications

• Viewing past weather data (ASCII Log View, History Monitor)

2.5.1 Viewing Current Data

Vertical Windshear Detection System (Optional)

2.5.2 Editing and Sending Weather Reports

2.5.3 Entering Data Manually

2.5.4 Viewing Past Data

History Monitor (Optional)

Database Reporting Tool (Optional)

2.5.5 Managing Data Source and Settings

Sensor Control (Optional)

Data Source Manager (Optional)

Actuals View (Optional)

Sensor Selector (Optional)

Runways Display for Runway-in-Use

Runway Configuration (Optional)

AFTN Addressee Manager