Midas IV User's Guide M010027en-F

Automated Weather
Observing System
MIDAS IV AWOS
USER'S GUIDE
M010027EN-F
February 2005
PUBLISHED BY
Visit our Internet pages at http://www.vaisala.com/
Vaisala 2005
No part of this manual may be reproduced in any form or by any means,
electronic or mechanical (including photocopying), nor may its contents
be communicated to a third party without prior written permission of the
copyright holder.
The contents are subject to change without prior notice.
Please observe that this manual does not create any legally binding
obligations for Vaisala towards the customer or end user. All legally
binding commitments and agreements are included exclusively in the
applicable supply contract or Conditions of Sale.
Vaisala Oyj Phone (int.): +358 9 8949 1
P.O. Box 26 Fax: +358 9 8949 2227
FIN-00421 Helsinki
Finland
________________________________________________________________________________
VAISALA________________________________________________________________________ 1
Table of Contents
CHAPTER 1
GENERAL INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Contents of This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Structure of the Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Version Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Related Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
General Safety Considerations . . . . . . . . . . . . . . . . . . . . . 23
Regulatory Compliances . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
CHAPTER 2
PRODUCT OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Introduction to MIDAS IV . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
MIDAS IV Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
End-user Software Applications . . . . . . . . . . . . . . . . . . . . . 28
Viewing Current Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Weather View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Editing and Sending Weather Reports . . . . . . . . . . . . . . . . 29
METAR/MET REPORT . . . . . . . . . . . . . . . . . . . . . . . . 29
TAF (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
SIGMET (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
GAMET (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
AIRMET (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
AD WRNG (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . 29
WS WRNG (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . 30
SYNOP (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
SNOWTAM (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . 30
CLIMAT (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Entering Data Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Actuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Data Source Manager . . . . . . . . . . . . . . . . . . . . . . . . . 30
Viewing Past Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
ASCII Log View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
History Monitor (Optional) . . . . . . . . . . . . . . . . . . . . . . 31
Database Reporting Tool (Optional) . . . . . . . . . . . . . . 31
AFTN Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Users Guide ______________________________________________________________________
2 ____________________________________________________________________M010027EN-F
AFTN Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Managing Data Source and Settings . . . . . . . . . . . . . . . . .31
Data Source Manager . . . . . . . . . . . . . . . . . . . . . . . . . 31
METAR/MET REPORT Manager. . . . . . . . . . . . . . . . . 32
Runway in Use Manager . . . . . . . . . . . . . . . . . . . . . . . 32
AFTN Addressee Manager . . . . . . . . . . . . . . . . . . . . . 32
Dial-up Manager (Optional) . . . . . . . . . . . . . . . . . . . . . 32
Monitoring System Operation . . . . . . . . . . . . . . . . . . . . . . .32
Event Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
System Maintenance Software Applications . . . . . . . . . . .33
Event Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Diagnostic Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Sensor Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
SensorIO Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
METAR/MET REPORT Manager . . . . . . . . . . . . . . . . . . . .33
Workstation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
CHAPTER 3
GETTING STARTED WITH MIDAS IV . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Logging In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Starting and Exiting Applications . . . . . . . . . . . . . . . . . . . .37
MIDAS IV User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
MIDAS IV Application Toolbar . . . . . . . . . . . . . . . . . . . . . .39
Note Field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
System Status Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Event Monitor Status Icon . . . . . . . . . . . . . . . . . . . . . . . . .42
Operating MIDAS IV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Selecting MIDAS IV Functions . . . . . . . . . . . . . . . . . . . . . .42
Switching between Applications . . . . . . . . . . . . . . . . . . . . .43
Arranging Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Showing, Hiding, and Moving Toolbars in Applications . . .43
Showing and Hiding Status Bars . . . . . . . . . . . . . . . . . . . .44
Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
CHAPTER 4
WEATHER VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Introduction to Weather View . . . . . . . . . . . . . . . . . . . . . . . .45
Weather View User Interface . . . . . . . . . . . . . . . . . . . . . . . .45
Weather Data Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Identification Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Weather Data Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Data Field Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Wind Rose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Wind Direction Value Selection (Optional) . . . . . . . 51
Graphical Fields (Optional) . . . . . . . . . . . . . . . . . . . . . 51
METAR Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Audiovisual Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Alarm Window (Optional) . . . . . . . . . . . . . . . . . . . . . . . 53
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
________________________________________________________________________________
VAISALA________________________________________________________________________ 3
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Operating Weather View . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Starting and Exiting Weather View . . . . . . . . . . . . . . . . . . 56
Opening and Closing Weather Data Screens . . . . . . . . . . 56
Monitoring Weather Data and Status . . . . . . . . . . . . . . . . . 57
Acknowledging Audiovisual Alarms (Optional) . . . . . . . . . 57
Simultaneous Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . 58
Alarm Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Viewing Stored Alarms. . . . . . . . . . . . . . . . . . . . . . . . . 59
Adjusting Graph Scales . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Using Auto Scale in Graphs. . . . . . . . . . . . . . . . . . . . . 60
Troubleshooting Weather View . . . . . . . . . . . . . . . . . . . . . . 61
CHAPTER 5
METAR/MET REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Introduction to METAR/MET REPORT . . . . . . . . . . . . . . . . 63
METAR/MET REPORT User Interface . . . . . . . . . . . . . . . . . 64
Report Identification Data . . . . . . . . . . . . . . . . . . . . . . . . . 67
Data Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Automatic Data Fields . . . . . . . . . . . . . . . . . . . . . . . . . 67
Manual Data Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Common Data Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Data Fields in METAR/SPECI View . . . . . . . . . . . . . . . . . . 69
Reading Data Field Tables . . . . . . . . . . . . . . . . . . . . . 69
Wind Data Fields in METAR/SPECI . . . . . . . . . . . . . . 70
Visibility Data Fields in METAR/SPECI . . . . . . . . . . . . 70
RVR Data Fields in METAR/SPECI . . . . . . . . . . . . . . . 72
Present Weather Data Fields in METAR/SPECI . . . . . 73
Cloud Data Fields in METAR/SPECI . . . . . . . . . . . . . . 74
Temperature and Pressure Data Fields
in METAR/SPECI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Recent Weather (REWX) Data Field
in METAR/SPECI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
WIND SHEAR Data Field in METAR/SPECI . . . . . . . . 77
RUNWAY STATE Data Field in METAR/SPECI . . . . . 78
TREND Field in METAR/SPECI. . . . . . . . . . . . . . . . . . 78
REMARK Field in METAR/SPECI . . . . . . . . . . . . . . . . 79
FORECASTER REMARK Field in
METAR/SPECI (Optional) . . . . . . . . . . . . . . . . . . . . . . 79
Data Fields in MET REPORT/SPECIAL View (Optional) . . 80
Reading Data Field Tables . . . . . . . . . . . . . . . . . . . . . 80
Wind Data Fields in MET REPORT/SPECIAL. . . . . . . 81
Visibility Data Fields in REPORT/SPECIAL . . . . . . . . 83
RVR Data Fields in MET REPORT/SPECIAL . . . . . . . 83
Present Weather Data Fields in MET
REPORT/SPECIAL . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Cloud Data Fields in MET REPORT/SPECIAL . . . . . . 85
Temperature and Pressure Data Fields in
MET REPORT/SPECIAL . . . . . . . . . . . . . . . . . . . . . . 86
QFE Data Fields in MET REPORT/SPECIAL View. . . 87
Users Guide ______________________________________________________________________
4 ____________________________________________________________________M010027EN-F
Recent Weather (REWX) Data Field in MET
REPORT/SPECIAL . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
WIND SHEAR Data Field in MET REPORT/SPECIAL 88
Other Supplementary Information Data Field in
MET REPORT/SPECIAL . . . . . . . . . . . . . . . . . . . . . . . 90
TREND Field in MET REPORT/SPECIAL . . . . . . . . . . 90
REMARK Field in MET REPORT/SPECIAL . . . . . . . . 90
FORECASTER REMARK Field in MET
REPORT/SPECIAL (Optional) . . . . . . . . . . . . . . . . . . . 91
CODE Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
SPECI Limit Manager Window . . . . . . . . . . . . . . . . . . . . . .92
Buttons in the METAR/MET REPORT Template . . . . . . . .93
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Operating METAR/MET REPORT . . . . . . . . . . . . . . . . . . . .97
Starting and Exiting METAR/MET REPORT . . . . . . . . . . .97
METAR Editing and Sending Times . . . . . . . . . . . . . . . . .97
Editing and Sending Normal METAR and MET
REPORT Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Validations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Requesting TREND from Forecaster . . . . . . . . . . . . . 103
Replying to TREND Request . . . . . . . . . . . . . . . . . . 105
Canceling Current METAR/MET REPORT . . . . . . . . 106
Sending Delayed (Retarded) METAR/MET
REPORT Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
Sending Corrected METAR/MET REPORT Reports . . .108
Sending a Correction to the Last Report . . . . . . . . . . 108
Sending a Correction to an Earlier Report . . . . . . . . 110
Sending Automated METAR Reports (Optional) . . . . . . .111
Editing Automated METAR Report . . . . . . . . . . . . . . 111
Editing and Sending Normal SPECI Reports . . . . . . . . . .112
Accepting and Sending Improvement SPECI Reports 114
Editing and Sending Deterioration SPECI Reports . . 115
Triggering and Sending SPECI Reports . . . . . . . . . . 115
Canceling Current SPECI Report. . . . . . . . . . . . . . . . 115
Sending Corrected SPECI Reports . . . . . . . . . . . . . . . . .116
Sending Automated SPECI Reports (Optional) . . . . . . . .117
Changing SPECI Triggering Limits . . . . . . . . . . . . . . . . .118
Editing and Sending SPECIAL Reports . . . . . . . . . . . . . .119
Canceling Current SPECIAL Report . . . . . . . . . . . . . 120
Viewing Sent Reports . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Changing Font . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
Troubleshooting METAR/MET REPORT . . . . . . . . . . . . . .122
________________________________________________________________________________
VAISALA________________________________________________________________________ 5
CHAPTER 6
TAF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Introduction to TAF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
TAF User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
TAF Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Operating TAF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Starting and Exiting TAF . . . . . . . . . . . . . . . . . . . . . . . . . 127
Sending Normal and Delayed TAF Reports . . . . . . . . . . . 128
Sending Corrected and Amended TAF Reports . . . . . . . 129
Canceling Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Sending NIL TAF Reports . . . . . . . . . . . . . . . . . . . . . . . . 130
Viewing Sent TAF Reports . . . . . . . . . . . . . . . . . . . . . . . . 131
Troubleshooting TAF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
CHAPTER 7
SIGMET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Introduction to SIGMET . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
SIGMET User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
SIGMET Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Operating SIGMET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Starting and Exiting SIGMET . . . . . . . . . . . . . . . . . . . . . . 136
Sending Normal SIGMET Reports . . . . . . . . . . . . . . . . . 137
Sending Corrected SIGMET Reports . . . . . . . . . . . . . . . 137
Canceling Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Viewing Sent SIGMET Reports . . . . . . . . . . . . . . . . . . . . 138
Troubleshooting SIGMET . . . . . . . . . . . . . . . . . . . . . . . . . . 139
CHAPTER 8
GAMET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Introduction to GAMET . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
GAMET User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
GAMET Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Operating GAMET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Starting and Exiting GAMET . . . . . . . . . . . . . . . . . . . . . . 145
Sending Normal and Delayed GAMET Reports . . . . . . . 145
Sending Corrected and Amended GAMET Reports . . . . 146
Viewing Sent GAMET Reports . . . . . . . . . . . . . . . . . . . . 147
Troubleshooting GAMET . . . . . . . . . . . . . . . . . . . . . . . . . . 147
CHAPTER 9
AIRMET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Introduction to AIRMET . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
AIRMET User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
AIRMET Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Users Guide ______________________________________________________________________
6 ____________________________________________________________________M010027EN-F
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Operating AIRMET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153
Starting and Exiting AIRMET . . . . . . . . . . . . . . . . . . . . .153
Sending Normal AIRMET Reports . . . . . . . . . . . . . . . . . .153
Sending Corrected AIRMET Reports . . . . . . . . . . . . . . . .154
Canceling Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155
Viewing Sent AIRMET Reports . . . . . . . . . . . . . . . . . . . .155
Troubleshooting AIRMET . . . . . . . . . . . . . . . . . . . . . . . . .155
CHAPTER 10
AD WRNG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
Introduction to AD WRNG Template . . . . . . . . . . . . . . . . .157
AD WRNG Template User Interface . . . . . . . . . . . . . . . . . .158
AD WRNG Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160
Operating AD WRNG Template . . . . . . . . . . . . . . . . . . . . .161
Starting and Exiting AD WRNG Template . . . . . . . . . . . .161
Sending Normal Aerodrome Warning Reports . . . . . . . .161
Sending Corrected Aerodrome Warning Reports . . . . . .162
Viewing Sent Aerodrome Warning Reports . . . . . . . . . . .163
Troubleshooting AD WRNG Template . . . . . . . . . . . . . . . .163
CHAPTER 11
WS WRNG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165
Introduction to WS WRNG Template . . . . . . . . . . . . . . . . .165
WS WRNG User Interface . . . . . . . . . . . . . . . . . . . . . . . . . .166
WS WRNG Window . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168
Operating WS WRNG Template . . . . . . . . . . . . . . . . . . . . .169
Starting and Exiting WS WRNG Template . . . . . . . . . . . .169
Sending Normal Windshear Warning Reports . . . . . . . .169
Sending Corrected Windshear Warning Reports . . . . . .170
Viewing Sent Windshear Warning Reports . . . . . . . . . . .171
Troubleshooting WS WRNG . . . . . . . . . . . . . . . . . . . . . . . .171
CHAPTER 12
AFTN MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
Introduction to AFTN Monitor . . . . . . . . . . . . . . . . . . . . . .173
AFTN Monitor User Interface . . . . . . . . . . . . . . . . . . . . . . .173
AFTN Monitor Window . . . . . . . . . . . . . . . . . . . . . . . . . .174
AFTN Manager Window . . . . . . . . . . . . . . . . . . . . . . . . . .174
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
Outbound (Sent) Messages . . . . . . . . . . . . . . . . . . . . . . . .177
________________________________________________________________________________
VAISALA________________________________________________________________________ 7
Operating AFTN Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Starting and Exiting AFTN Monitor . . . . . . . . . . . . . . . . . 178
Viewing Outbound (Sent) Messages . . . . . . . . . . . . . . . . 178
Changing AFTN Sequence Number . . . . . . . . . . . . . . . . 178
Using AFTN Addressee Manager . . . . . . . . . . . . . . . . . . 179
Troubleshooting AFTN Monitor . . . . . . . . . . . . . . . . . . . . . 179
CHAPTER 13
AFTN ADDRESSEE MANAGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Introduction to AFTN Addressee Manager . . . . . . . . . . . . 181
AFTN Addressee Manager User Interface . . . . . . . . . . . . 181
AFTN Interfaces Frame . . . . . . . . . . . . . . . . . . . . . . . . . . 183
AFTN Interface Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Addressee Group Frame . . . . . . . . . . . . . . . . . . . . . . . . . 184
Addressee Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Operating AFTN Addressee Manager . . . . . . . . . . . . . . . . 185
Starting and Exiting AFTN Addressee Manager . . . . . . . 185
Adding New Addressee Groups . . . . . . . . . . . . . . . . . . . . 186
Adding New Addressees . . . . . . . . . . . . . . . . . . . . . . . . . 186
Selecting Message Types Sent to the Addressees . . . . . 187
Editing Addressee Groups . . . . . . . . . . . . . . . . . . . . . . . . 187
Troubleshooting AFTN Addressee Manager . . . . . . . . . . 188
CHAPTER 14
AFTN VIEWER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Introduction to AFTN Viewer . . . . . . . . . . . . . . . . . . . . . . . 189
AFTN Viewer User Interface . . . . . . . . . . . . . . . . . . . . . . . . 189
Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Message Status Window . . . . . . . . . . . . . . . . . . . . . . . . . 192
Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Sound Configuration Window . . . . . . . . . . . . . . . . . . . . . 195
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Operating AFTN Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Starting AFTN Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Exiting AFTN Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Viewing Received Messages . . . . . . . . . . . . . . . . . . . . . . 197
Configuring Message Parameters . . . . . . . . . . . . . . . . . . 198
Turning the Pop-Up Feature On and Off . . . . . . . . . . . . . 199
Turning the Beep Feature On and Off . . . . . . . . . . . . . . . 199
Changing the Beep Settings . . . . . . . . . . . . . . . . . . . . . . 200
Changing the Font and Color Settings . . . . . . . . . . . . . . . 200
Troubleshooting AFTN Viewer . . . . . . . . . . . . . . . . . . . . . . 200
Users Guide ______________________________________________________________________
8 ____________________________________________________________________M010027EN-F
CHAPTER 15
EVENT MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201
Introduction to Event Monitor . . . . . . . . . . . . . . . . . . . . . .201
Event Monitor User Interface . . . . . . . . . . . . . . . . . . . . . . .202
Event Monitor Status Icon . . . . . . . . . . . . . . . . . . . . . . . .202
Event Monitor Window . . . . . . . . . . . . . . . . . . . . . . . . . . .203
Event Monitor Window Columns . . . . . . . . . . . . . . . . 204
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207
Operating Event Monitor . . . . . . . . . . . . . . . . . . . . . . . . . .208
Starting and Exiting Event Monitor . . . . . . . . . . . . . . . . . .208
Monitoring and Acknowledging Events . . . . . . . . . . . . . .208
Monitoring Message Notifications . . . . . . . . . . . . . . . 210
Using the Voice Alarm Function . . . . . . . . . . . . . . . . . . . .210
Viewing Events in Bottom Line Mode . . . . . . . . . . . . . . . .211
Turning On Bottom Line Mode. . . . . . . . . . . . . . . . . . 211
Viewing Several Rows in Bottom Line Mode . . . . . . . 212
Turning Off Bottom Line Mode. . . . . . . . . . . . . . . . . . 213
Viewing Event Monitor Always on Top . . . . . . . . . . . . . . .213
Viewing Selected Event Types . . . . . . . . . . . . . . . . . . . . .213
Viewing Events from Selected Sites . . . . . . . . . . . . . . . .214
Viewing Stored Events . . . . . . . . . . . . . . . . . . . . . . . . . . .215
Hiding the Event Monitor Button . . . . . . . . . . . . . . . . . . .216
Troubleshooting Event Monitor . . . . . . . . . . . . . . . . . . . . .217
CHAPTER 16
ASCII LOG VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
Introduction to ASCII Log View . . . . . . . . . . . . . . . . . . . . .219
ASCII Log View User Interface . . . . . . . . . . . . . . . . . . . . .219
ASCII Log View Window . . . . . . . . . . . . . . . . . . . . . . . . .220
Weather Parameter Screens . . . . . . . . . . . . . . . . . . . . . .221
Reports Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223
Events Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227
Operating ASCII Log View . . . . . . . . . . . . . . . . . . . . . . . . .228
Starting and Exiting ASCII Log View . . . . . . . . . . . . . . . .228
Viewing History Files . . . . . . . . . . . . . . . . . . . . . . . . . . . .228
Resizing Panes and Columns . . . . . . . . . . . . . . . . . . . . .230
Scrolling the Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . .230
Viewing Several Windows at the Same Time . . . . . . . . .231
Refreshing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231
Copying Text from History Files . . . . . . . . . . . . . . . . . . .232
Troubleshooting ASCII Log View . . . . . . . . . . . . . . . . . . .232
________________________________________________________________________________
VAISALA________________________________________________________________________ 9
CHAPTER 17
ACTUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Introduction to Actuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Actuals User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Wind Actuals Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Cloud Actuals Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Weather Actuals Window . . . . . . . . . . . . . . . . . . . . . . . . 239
Pressure Actuals Window . . . . . . . . . . . . . . . . . . . . . . . . 240
Pressure Values in Data Source Manager
Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
RVR/Visibility Actuals Window . . . . . . . . . . . . . . . . . . . . . 241
Prevailing Visibility Values in Data Source
Manager Application . . . . . . . . . . . . . . . . . . . . . . . . . 242
Manual Observations Window . . . . . . . . . . . . . . . . . . . . . 242
Data Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Update Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Runway Parameters Window . . . . . . . . . . . . . . . . . . . . . . 246
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Operating Actuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Starting and Exiting Actuals . . . . . . . . . . . . . . . . . . . . . . 252
Using Automatic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Using Backup Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Using Manual Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Entering Background Luminance . . . . . . . . . . . . . . . . . . . 255
Entering Light Intensity Manually . . . . . . . . . . . . . . . . . . . 256
Viewing Light Intensity Status . . . . . . . . . . . . . . . . . . . . . 257
Using Manual Observations Window . . . . . . . . . . . . . . . 257
Activating the Manual Observations Window . . . . . . 257
Defining METAR/SPECI Values as ManObs . . . . . . 258
Entering Manual Observations . . . . . . . . . . . . . . . . . 259
Troubleshooting Actuals . . . . . . . . . . . . . . . . . . . . . . . . . . 260
CHAPTER 18
DATA SOURCE MANAGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Introduction to Data Source Manager . . . . . . . . . . . . . . . . 261
Data Source Manager User Interface . . . . . . . . . . . . . . . . 261
Data Source Manager Window . . . . . . . . . . . . . . . . . . . . 262
Active Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Normal Situations . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Exceptional Situations . . . . . . . . . . . . . . . . . . . . . . . . 264
Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
PV Group Manager Window . . . . . . . . . . . . . . . . . . . . . . 268
Sensor Weight Value. . . . . . . . . . . . . . . . . . . . . . . . . 270
Validity Limit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Operating the Data Source Manager Application . . . . . . 271
Starting and Exiting Data Source Manager . . . . . . . . . . . 271
Changing the Active Data Source . . . . . . . . . . . . . . . . . . 271
Users Guide ______________________________________________________________________
10 ___________________________________________________________________M010027EN-F
Using Manual Values . . . . . . . . . . . . . . . . . . . . . . . . . . . .272
Disabling and Enabling Data Sources for Pressure
Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273
Managing Prevailing Visibility Groups . . . . . . . . . . . . . . .274
Adding New Prevailing Visibility Groups . . . . . . . . . . 274
Editing Prevailing Visibility Groups. . . . . . . . . . . . . . . 275
Editing Validity Limit . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Troubleshooting Data Source Manager . . . . . . . . . . . . . .276
CHAPTER 19
HISTORY MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279
Introduction to History Monitor . . . . . . . . . . . . . . . . . . . . .279
History Monitor User Interface . . . . . . . . . . . . . . . . . . . . . .279
Trend View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282
Table View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282
Event View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283
New Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283
Open Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283
Data Item Selection Window . . . . . . . . . . . . . . . . . . . . . .284
Options Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285
Graph Properties Window . . . . . . . . . . . . . . . . . . . . . . . .287
Extremes Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291
Operating History Monitor . . . . . . . . . . . . . . . . . . . . . . . . .292
Starting and Exiting History Monitor . . . . . . . . . . . . . . . . .292
Creating a New View . . . . . . . . . . . . . . . . . . . . . . . . . . . .292
Opening Saved Views . . . . . . . . . . . . . . . . . . . . . . . . . . .294
Changing Displayed Data Items . . . . . . . . . . . . . . . . . . . .295
Refreshing Data in Views . . . . . . . . . . . . . . . . . . . . . . . . .296
Changing Display Period and Resolution . . . . . . . . . . . . .296
Editing Graphs in Trend Views . . . . . . . . . . . . . . . . . . . . .297
Changing the Scale . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Changing Background and Trend Line Color. . . . . . . 298
Adjusting Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Hiding/Showing Graphs . . . . . . . . . . . . . . . . . . . . . . . 299
Moving and Zooming in Trend Views . . . . . . . . . . . . . . . .300
Moving Around. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Zooming In. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Zooming Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Moving and Sorting in Table Views . . . . . . . . . . . . . . . . .300
Viewing Several Windows at the Same Time . . . . . . . . .301
Troubleshooting History Monitor . . . . . . . . . . . . . . . . . . .302
CHAPTER 20
RUNWAY IN USE MANAGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .303
Introduction to Runway in Use Manager . . . . . . . . . . . . . .303
Runway in Use Manager User Interface . . . . . . . . . . . . . .303
Operating the Runway in Use Manager Application . . . .305
________________________________________________________________________________
VAISALA_______________________________________________________________________ 11
Starting and Exiting Runway in Use Manager . . . . . . . . . 305
Setting Runway in Use Manually . . . . . . . . . . . . . . . . . . . 305
Troubleshooting Runway in Use Manager . . . . . . . . . . . . 306
CHAPTER 21
METAR/MET REPORT MANAGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Introduction to METAR/MET REPORT Manager . . . . . . . . 307
METAR/MET REPORT Manager User Interface . . . . . . . . 308
Measurement Locations for METAR/MET REPORT
Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Runway Landing Directions and Reporting Orders
for Local Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Operating METAR/MET REPORT Manager . . . . . . . . . . . 312
Starting METAR/MET REPORT Manager . . . . . . . . . . . . 312
Exiting METAR/MET REPORT Manager . . . . . . . . . . . . 312
Defining Automatic Data Source . . . . . . . . . . . . . . . . . . . 312
Defining METAR/SPECI Values as Manual . . . . . . . . . . . 313
Defining METAR/MET REPORT Values as ManObs
for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Defining METAR/SPECI Values as ManObs . . . . . . . . . . 314
Defining Runway Landing Direction for Local Reports . . 315
Defining Runway Reporting Order for Local Reports . . . . 316
Troubleshooting METAR/MET REPORT Manager . . . . . . 316
CHAPTER 22
DIAL-UP MANAGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Introduction to Dial-up Manager . . . . . . . . . . . . . . . . . . . . 317
Dial-up Manager User Interface . . . . . . . . . . . . . . . . . . . . . 317
Destinations Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Messages Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Operating Dial-up Manager . . . . . . . . . . . . . . . . . . . . . . . . 320
Starting and Exiting Dial-up Manager . . . . . . . . . . . . . . . 320
Turning on Dial-up Connection . . . . . . . . . . . . . . . . . . . . 320
Calling Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Turning off Dial-up Connection . . . . . . . . . . . . . . . . . . . . 321
Managing Destinations and Phone Numbers . . . . . . . . . 322
Viewing Modem Connections . . . . . . . . . . . . . . . . . . . . . 323
Troubleshooting Dial-up Manager . . . . . . . . . . . . . . . . . . . 324
APPENDIX A
PARAMETER LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
APPENDIX B
GLOSSARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Users Guide ______________________________________________________________________
12 ___________________________________________________________________M010027EN-F
________________________________________________________________________________
VAISALA_______________________________________________________________________ 13
List of Figures
Figure 1 A Typical MIDAS IV System. . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 2 MIDAS IV AWOS User Interface . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 3 MIDAS IV Application Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 4 System Status Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 5 Event Monitor Status Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 6 Weather View: Sample Weather Data Screen. . . . . . . . . . . . . 46
Figure 7 Data Status of Average Values in Problem Situations. . . . . . . 49
Figure 8 Weather View: Wind Rose . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 9 Wind Direction Value Selection (Optional) . . . . . . . . . . . . . . . . 51
Figure 10 A Sample Graphical Field in Weather View. . . . . . . . . . . . . . . 51
Figure 11 Weather View: Graph Scales Window. . . . . . . . . . . . . . . . . . . 52
Figure 12 Weather View: Alarm Window . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 13 Graph Scale Change Warning Window . . . . . . . . . . . . . . . . . . 60
Figure 14 METAR/MET REPORT Template, METAR/SPECI View. . . . . 64
Figure 15 METAR/MET REPORT Template, MET
REPORT/SPECIAL View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure 16 Wind Shear Data Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 17 MET REPORT/SPECIAL Wind Data Window . . . . . . . . . . . . . 82
Figure 18 MET REPORT/SPECIAL Cloud Data Window. . . . . . . . . . . . . 86
Figure 19 Wind Shear Data Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Figure 20 SPECI Limit Manager Window. . . . . . . . . . . . . . . . . . . . . . . . . 92
Figure 21 Example of METAR Editing and Sending Times . . . . . . . . . . . 98
Figure 22 METAR/MET REPORT Editing Procedure . . . . . . . . . . . . . . 102
Figure 23 Example Validation Error Message . . . . . . . . . . . . . . . . . . . . 103
Figure 24 Request TREND Message Window in OWS . . . . . . . . . . . . . 104
Figure 25 Confirm TREND Message Window in OWS . . . . . . . . . . . . . 104
Figure 26 Request TREND Message Window in FWS . . . . . . . . . . . . . 105
Figure 27 TREND Confirmation Message in FWS. . . . . . . . . . . . . . . . . 106
Figure 28 METAR Retarded Message Window . . . . . . . . . . . . . . . . . . . 107
Figure 29 Manual Changes Lost Warning Message Window . . . . . . . . 109
Figure 30 Improvement SPECI Message Window. . . . . . . . . . . . . . . . . 114
Figure 31 Manual Changes Lost Warning Message Window . . . . . . . . 117
Figure 32 TAF Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Figure 33 SIGMET Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Figure 34 GAMET Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Figure 35 AIRMET Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Figure 36 AD WRNG Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Figure 37 WS WRNG Template Window. . . . . . . . . . . . . . . . . . . . . . . . 166
Figure 38 AFTN Monitor Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Figure 39 AFTN Manager Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Figure 40 AFTN Addressee Manager Window. . . . . . . . . . . . . . . . . . . . 182
Figure 41 AFTN Viewer Main Page with Message Descriptions . . . . . . 190
Figure 42 AFTN Viewer: Received Message . . . . . . . . . . . . . . . . . . . . . 191
Figure 43 AFTN Viewer: Message Status Window with
Message Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Users Guide ______________________________________________________________________
14 ___________________________________________________________________M010027EN-F
Figure 44 AFTN Viewer: Message Status Window with no Message . .192
Figure 45 AFTN Viewer: Configuration Window. . . . . . . . . . . . . . . . . . .193
Figure 46 AFTN Viewer: Sound Configuration Window . . . . . . . . . . . . .195
Figure 47 AFTN Viewer: About Window with Help. . . . . . . . . . . . . . . . .197
Figure 48 Received Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198
Figure 49 Event Monitor Status Icon . . . . . . . . . . . . . . . . . . . . . . . . . . .202
Figure 50 Event Monitor Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203
Figure 51 Event Monitor: Bottom Line Mode . . . . . . . . . . . . . . . . . . . . .212
Figure 52 Event Monitor: Bottom Line Mode with Several Rows . . . . . .212
Figure 53 ASCII Log View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . .220
Figure 54 ASCII Log View: Weather Parameter Screen . . . . . . . . . . . .221
Figure 55 ASCII Log View: Reports Screen . . . . . . . . . . . . . . . . . . . . . .223
Figure 56 ASCII Log View: Events Screen. . . . . . . . . . . . . . . . . . . . . . .224
Figure 57 ASCII Log View: Opening History Files . . . . . . . . . . . . . . . . .228
Figure 58 Actuals User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234
Figure 59 Actuals Backup and Manual Modes. . . . . . . . . . . . . . . . . . . .236
Figure 60 Wind Actuals Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237
Figure 61 Cloud Actuals Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238
Figure 62 Weather Actuals Window. . . . . . . . . . . . . . . . . . . . . . . . . . . .239
Figure 63 Pressure Actuals Window . . . . . . . . . . . . . . . . . . . . . . . . . . .240
Figure 64 RVR/Visibility Actuals Window. . . . . . . . . . . . . . . . . . . . . . . .241
Figure 65 Actuals: Manual Observations Window . . . . . . . . . . . . . . . . .243
Figure 66 Runway Parameters Window. . . . . . . . . . . . . . . . . . . . . . . . .246
Figure 67 Data Source Manager Window, Pressure Tab. . . . . . . . . . . .262
Figure 68 Data Source Manager, Prevailing Visibility Tab . . . . . . . . . . .262
Figure 69 Data Source Manager Window, Default Situation . . . . . . . . .263
Figure 70 Data Source Manager Window, Active Sensor Changed. . . .264
Figure 71 PV Group Manager Window. . . . . . . . . . . . . . . . . . . . . . . . . .268
Figure 72 Activate Data Source Window . . . . . . . . . . . . . . . . . . . . . . . .271
Figure 73 Activate Data Source Window, Warning . . . . . . . . . . . . . . . .272
Figure 74 Disable Data Source Window. . . . . . . . . . . . . . . . . . . . . . . . .273
Figure 75 Disable Data Source Window, Warning . . . . . . . . . . . . . . . . .274
Figure 76 Blank History Monitor Main Window. . . . . . . . . . . . . . . . . . . .280
Figure 77 History Monitor with Opened Views . . . . . . . . . . . . . . . . . . . .281
Figure 78 New Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283
Figure 79 Open View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284
Figure 80 Data Item Selection Window . . . . . . . . . . . . . . . . . . . . . . . . .284
Figure 81 Options Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285
Figure 82 Graph Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . . .287
Figure 83 Extremes Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288
Figure 84 The New Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292
Figure 85 Blank Table View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293
Figure 86 Data Items Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293
Figure 87 Save View As Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294
Figure 88 Open View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295
Figure 89 Runway in Use Manager Window . . . . . . . . . . . . . . . . . . . . .304
Figure 90 METAR/MET REPORT Manager Window. . . . . . . . . . . . . . .308
Figure 91 Runway Landing Direction Example, 04L . . . . . . . . . . . . . . .311
Figure 92 Runway Landing Direction Example, 22R . . . . . . . . . . . . . . .311
Figure 93 Selecting Runway Landing Direction . . . . . . . . . . . . . . . . . . .315
Figure 94 Dial-up Manager Window. . . . . . . . . . . . . . . . . . . . . . . . . . . .318
________________________________________________________________________________
VAISALA_______________________________________________________________________ 15
List of Tables
Table 1 Chapter Structure of the Manual . . . . . . . . . . . . . . . . . . . . . . . . . 21
Table 2 Manual Revisions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 3 Related Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 4 International Recommendations Applied to MIDAS IV
AWOS Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 5 MIDAS IV AWOS Applications in Workstations . . . . . . . . . . . . . . 35
Table 6 MIDAS IV AWOS Application Toolbar Buttons . . . . . . . . . . . . . . 40
Table 7 Weather View: Weather Data Field Statuses. . . . . . . . . . . . . . . . 48
Table 8 Weather View: Graph Scales Window Elements . . . . . . . . . . . . . 52
Table 9 Weather View: Alarm Window Elements . . . . . . . . . . . . . . . . . . . 54
Table 10 Weather View: Display Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Table 11 Weather View: Edit Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Table 12 Weather View: View Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Table 13 Weather View: Window Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Table 14 Weather View Toolbar Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Table 15 Troubleshooting Weather View . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Table 16 Wind Data Fields in METAR/SPECI View . . . . . . . . . . . . . . . . . . 70
Table 17 Prevailing Visibility Data Fields in METAR/SPECI View
(Used as Specified by ICAO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Table 18 Visibility Data Fields in METAR/SPECI View (Using
Other than Prevailing Visibility) . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Table 19 RVR Data Fields in METAR/SPECI View . . . . . . . . . . . . . . . . . . 72
Table 20 Present Weather Data Fields in METAR/SPECI View. . . . . . . . . 73
Table 21 Clouds and Vertical Visibility Data Fields in
METAR/SPECI View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Table 22 Temperature and Pressure Data Fields in
METAR/SPECI View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Table 23 REWX (Recent Weather) Data Field in METAR/SPECI View . . . 76
Table 24 Wind Shear Data Window Elements . . . . . . . . . . . . . . . . . . . . . . 77
Table 25 RUNWAY STATE Data Field in METAR/SPECI View. . . . . . . . . 78
Table 26 Wind Data Fields in MET REPORT/SPECIAL View . . . . . . . . . . 81
Table 27 Visibility Data Fields in MET REPORT/SPECIAL View . . . . . . . . 83
Table 28 RVR Data Fields in MET REPORT/SPECIAL View. . . . . . . . . . . 83
Table 29 Present Weather Data Fields in MET
REPORT/SPECIAL View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Table 30 Clouds Data Fields in MET REPORT/SPECIAL View . . . . . . . . . 85
Table 31 Temperature and Pressure Data Fields in MET
REPORT/SPECIAL View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Table 32 QFE Data Fields in MET REPORT/SPECIAL View. . . . . . . . . . . 87
Table 33 Recent Weather in MET REPORT/SPECIAL View . . . . . . . . . . . 88
Table 34 Wind Shear Data Window Elements . . . . . . . . . . . . . . . . . . . . . . 89
Table 35 Other Supp. Info in MET REPORT/SPECIAL View . . . . . . . . . . . 90
Table 36 SPECI Limit Manager Window Elements. . . . . . . . . . . . . . . . . . . 93
Table 37 Buttons in METAR/MET REPORT Template. . . . . . . . . . . . . . . . 93
Table 38 METAR/MET REPORT: Report Menu . . . . . . . . . . . . . . . . . . . . . 94
Users Guide ______________________________________________________________________
16 ___________________________________________________________________M010027EN-F
Table 39 METAR/MET REPORT: Edit Menu . . . . . . . . . . . . . . . . . . . . . . .94
Table 40 METAR/MET REPORT: View Menu . . . . . . . . . . . . . . . . . . . . . .94
Table 41 METAR/MET REPORT: Settings Menu . . . . . . . . . . . . . . . . . . . .95
Table 42 METAR/MET REPORT: Help Menu. . . . . . . . . . . . . . . . . . . . . . .95
Table 43 METAR/MET REPORT Toolbar Buttons . . . . . . . . . . . . . . . . . . .96
Table 44 Improvement and Deterioration SPECI Reports . . . . . . . . . . . . .113
Table 45 Troubleshooting METAR/MET REPORT . . . . . . . . . . . . . . . . . . .122
Table 46 TAF Window Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125
Table 47 TAF: File Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
Table 48 TAF: Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
Table 49 TAF: Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
Table 50 Troubleshooting TAF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131
Table 51 SIGMET Window Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
Table 52 SIGMET: File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136
Table 53 SIGMET: Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136
Table 54 SIGMET: Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136
Table 55 Troubleshooting SIGMET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
Table 56 GAMET Window Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
Table 57 GAMET: File Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144
Table 58 GAMET: Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144
Table 59 GAMET: Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144
Table 60 Troubleshooting GAMET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147
Table 61 AIRMET Window Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151
Table 62 AIRMET: File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Table 63 AIRMET: Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Table 64 AIRMET: Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Table 65 Troubleshooting AIRMET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155
Table 66 AD WRNG Window Elements . . . . . . . . . . . . . . . . . . . . . . . . . . .159
Table 67 AD WRNG: File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160
Table 68 AD WRNG: Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160
Table 69 AD WRNG: Help Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160
Table 70 Troubleshooting AD WRNG Template . . . . . . . . . . . . . . . . . . . . .163
Table 71 WS WRNG Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167
Table 72 WS WRNG: File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168
Table 73 WS WRNG: Edit Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168
Table 74 WS WRNG: Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168
Table 75 Troubleshooting WS WRNG Template . . . . . . . . . . . . . . . . . . . .171
Table 76 AFTN Monitor: File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
Table 77 AFTN Monitor: Edit Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
Table 78 AFTN Monitor: View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
Table 79 AFTN Monitor: Window Menu . . . . . . . . . . . . . . . . . . . . . . . . . . .176
Table 80 AFTN Monitor: Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
Table 81 AFTN Monitor Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
Table 82 Troubleshooting AFTN Monitor . . . . . . . . . . . . . . . . . . . . . . . . . .179
Table 83 AFTN Addressee Manager Window: AFTN Interfaces Frame . . .183
Table 84 AFTN Addressee Manager Window: AFTN Interface Frame. . . .183
Table 85 AFTN Addressee Manager Window: Addressee Group Frame . .184
Table 86 AFTN Addressee Manager Window: Addressee Frame . . . . . . .184
Table 87 AFTN Addressee Manager Window: Buttons. . . . . . . . . . . . . . . .185
Table 88 Troubleshooting AFTN Addressee Manager . . . . . . . . . . . . . . . .188
Table 89 AFTN Viewer: Configuration Window Elements. . . . . . . . . . . . . .193
Table 90 AFTN Viewer: File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196
________________________________________________________________________________
VAISALA_______________________________________________________________________ 17
Table 91 AFTN Viewer: Settings Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Table 92 AFTN Viewer: Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Table 93 Troubleshooting AFTN Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Table 94 Event Monitor Status Icon Colors. . . . . . . . . . . . . . . . . . . . . . . . . 202
Table 95 Event Monitor Window Icon Colors . . . . . . . . . . . . . . . . . . . . . . . 204
Table 96 Event Monitor Window Columns . . . . . . . . . . . . . . . . . . . . . . . . . 204
Table 97 Event Monitor: Quick Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Table 98 Event Monitor: Quick Menu (Site Column). . . . . . . . . . . . . . . . . . 205
Table 99 Event Monitor Type Column. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Table 100 Event Monitor Status Column . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Table 101 Event Monitor: Event Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Table 102 Event Monitor: View Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Table 103 Event Monitor: Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Table 104 Event Monitor Toolbar Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Table 105 Event Statuses, Types, and Needed Action. . . . . . . . . . . . . . . . . 209
Table 106 Examples of Message Notifications in Different Situations . . . . . 210
Table 107 An Example of the Event Chain. . . . . . . . . . . . . . . . . . . . . . . . . . 215
Table 108 Troubleshooting Event Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Table 109 ASCII Log View: Weather Parameter Screen Columns. . . . . . . . 221
Table 110 ASCII Log View: Status Codes . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Table 111 ASCII Log View: Reports Screen Parameters . . . . . . . . . . . . . . . 223
Table 112 ASCII Log View: Events Screen Columns . . . . . . . . . . . . . . . . . . 224
Table 113 ASCII Log View: File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Table 114 ASCII Log View: Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Table 115 ASCII Log View: View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Table 116 ASCII Log View: Window Menu. . . . . . . . . . . . . . . . . . . . . . . . . . 226
Table 117 ASCII Log View: Help Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Table 118 ASCII Log View Toolbar Buttons . . . . . . . . . . . . . . . . . . . . . . . . . 227
Table 119 Sample ASCII Log View File Names . . . . . . . . . . . . . . . . . . . . . . 229
Table 120 Troubleshooting ASCII Log View. . . . . . . . . . . . . . . . . . . . . . . . . 232
Table 121 Elements in the Weather Data Windows . . . . . . . . . . . . . . . . . . . 235
Table 122 Actuals Data Field Colors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Table 123 Manual Observations Window: Present Weather Codes. . . . . . . 244
Table 124 Manual Observations: Cloud Layers Fields . . . . . . . . . . . . . . . . . 244
Table 125 Manual Observations Window: Recent Weather and
Runway State Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Table 126 Manual Observations: Remark and Note Fields . . . . . . . . . . . . . 245
Table 127 Runway Parameters Window, Background
Luminance Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Table 128 Preconfigured Ranges for Background Luminance . . . . . . . . . . . 247
Table 129 Runway Parameters Window, Light Intensity Frame . . . . . . . . . . 248
Table 130 Actuals: Actuals Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Table 131 Actuals: Edit Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Table 132 Actuals: Actions Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Table 133 Actuals: View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Table 134 Actuals: Window Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Table 135 Actuals: Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Table 136 Actuals Toolbar Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Table 137 Troubleshooting Actuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Table 138 Data Source Manager Window Columns and Colors. . . . . . . . . . 264
Table 139 Data Source Manager, Value Columns for Pressure. . . . . . . . . . 266
Users Guide ______________________________________________________________________
18 ___________________________________________________________________M010027EN-F
Table 140 Data Source Manager, Value Columns for Prevailing Visibility . .266
Table 141 Data Source Manager Window Buttons . . . . . . . . . . . . . . . . . . . .267
Table 142 PV Group Manager Window Elements. . . . . . . . . . . . . . . . . . . . .269
Table 143 Troubleshooting Data Source Manager . . . . . . . . . . . . . . . . . . . .277
Table 144 Data Item Selection Window Elements . . . . . . . . . . . . . . . . . . . .285
Table 145 Options Window Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286
Table 146 Extremes Window Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . .288
Table 147 History Monitor: File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289
Table 148 History Monitor: Edit Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289
Table 149 History Monitor: View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289
Table 150 History Monitor: Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . .290
Table 151 History Monitor: Window Menu . . . . . . . . . . . . . . . . . . . . . . . . . .290
Table 152 History Monitor: Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290
Table 153 History Monitor Toolbar Buttons. . . . . . . . . . . . . . . . . . . . . . . . . .291
Table 154 Troubleshooting History Monitor . . . . . . . . . . . . . . . . . . . . . . . . .302
Table 155 Runway in Use Manager Window Elements . . . . . . . . . . . . . . . .304
Table 156 Troubleshooting Runway in Use Manager . . . . . . . . . . . . . . . . . .306
Table 157 METAR/MET REPORT Manager List Boxes . . . . . . . . . . . . . . . .309
Table 158 Typical METAR/MET REPORT Manager List Box Options . . . . .310
Table 159 Troubleshooting METAR/MET REPORT Manager . . . . . . . . . . .316
Table 160 Dial-up Manager Window Elements: Destinations Frame . . . . . .318
Table 161 Dial-up Manager Window Elements: Messages Frame . . . . . . . .319
Table 162 Troubleshooting Dial-up Manager . . . . . . . . . . . . . . . . . . . . . . . .324
Table 163 Parameters in Weather View and Actuals . . . . . . . . . . . . . . . . . .325
Chapter 1 ________________________________________________________ General Information
VAISALA_______________________________________________________________________ 19
CHAPTER 1
GENERAL INFORMATION
This chapter describes the structure of this manual, and provides safety,
contact, and version history information.
About This Manual
This manual contains the information necessary to use the end-user
software applications of the Vaisala Automated Weather Observing
System MIDAS IV AWOS, from version 3.0 onwards. The manual is
mainly intended for air traffic controllers, observers, and forecasters at
the airport.
Contents of This Manual
This manual consists of the following chapters:
- Chapter 1, General Information: This chapter describes the
structure of this manual, and provides safety, contact, and version
history information.
- Chapter 2, Product Overview: This chapter gives an overview of
the MIDAS IV system and its components.
- Chapter 3, Getting Started with MIDAS IV: This chapter describes
logging into the system, starting and exiting the applications, and
the user environment common to all applications.
Users Guide ______________________________________________________________________
20 ___________________________________________________________________M010027EN-F
- Chapter 4, Weather View: This chapter contains instructions for
viewing meteorological data using the Weather View application.
- Chapter 5, METAR/MET REPORT: This chapter describes how to
edit and send METAR, SPECI, MET REPORT, and SPECIAL
reports.
- Chapter 6, TAF: This chapter contains instructions for creating and
sending TAF reports.
- Chapter 7, SIGMET: This chapter contains instructions for
creating and sending SIGMET reports.
- Chapter 8, GAMET: This chapter contains instructions for creating
and sending GAMET reports.
- Chapter 9, AIRMET: This chapter contains instructions for
creating and sending AIRMET reports.
- Chapter 10, AD WRNG: This chapter contains instructions for
creating and sending Aerodrome Warning reports using the AD
WRNG template.
- Chapter 11, WS WRNG: This chapter contains instructions for
creating and sending Windshear Warning reports using the WS
WRNG template.
- Chapter 12, AFTN Monitor: This chapter contains instructions for
viewing reports that have been sent to the AFTN line.
- Chapter 13, AFTN Addressee Manager: This chapter describes
how to set the addressee part of the AFTN message.
- Chapter 14, AFTN Viewer: This chapter describes the AFTN
Viewer application which is used for viewing messages received
from the AFTN line.
- Chapter 15, Event Monitor: This chapter contains instructions for
viewing Event messages in the Event Monitor application.
- Chapter 16, ASCII Log View: This chapter contains instructions
for viewing history files with the ASCII Log View application.
- Chapter 17, Actuals: This chapter contains instructions for using
manual or backup data with the Actuals application.
- Chapter 18, Data Source Manager: This chapter describes how to
select the active data source and enter values manually for pressure
and prevailing visibility data.
- Chapter 19, History Monitor: This chapter describes how to
retrieve and view past measurement data from the database in table
or graphical trend format.
VAISALA_______________________________________________________________________ 21
- Chapter 20, Runway in Use Manager: This chapter describes how
to manually set which runways are in use, and the runway landing
direction.
- Chapter 21, METAR/MET REPORT Manager: This chapter
contains instructions for defining which measurement sites or other
sources provide the automatic data to the METAR/MET REPORT
template.
- Chapter 22, Dial-Up Manager: This chapter describes how to
configure and use the dial-up communication option to send
weather reports.
- Appendix A, Parameter List: This chapter lists typical parameters
displayed in the windows of Weather View and Actuals
applications.
- Appendix B, Glossary: This glossary contains descriptions and
definitions for unique terms and abbreviations used in this manual.
Structure of the Manual
The chapters that introduce end-user applications and provide
instructions for using the applications, are structured in the way
described in Table 1 on page 21.
Table 1 Chapter Structure of the Manual
Section Contents
Introduction to the application Describes what the application is used for
The user interface of the
application
Describes the user interface of the
application and how data is presented in the
application
Operating the application Provides step-by-step instructions on how
to use the application
Troubleshooting the
application
Describes some typical problem situations
and solutions to them
Users Guide ______________________________________________________________________
22 ___________________________________________________________________M010027EN-F
Version Information
Related Manuals
For information on the system architecture and the system maintenance
applications, see the appropriate MIDAS IV Maintenance Manual. For
instructions on installing, using, and maintaining the sensors and other
field devices, see the appropriate field device manuals.
The typical manual set available for the MIDAS IV products is
presented in Table 3 on page 22.
Table 2 Manual Revisions
Manual Code Description
U377en-1.1 Applicable from MIDAS IV AWOS version 1.1
M010027en-A Applicable from MIDAS IV AWOS version 1.2
M210206en-A Updated Applications in MIDAS IV AWOS Version 1.3,
Technical Reference. Applicable for MIDAS IV AWOS
from version 1.3 onwards.
M010027en-B Applicable for MIDAS IV AWOS from version 1.4
onwards.
M010027en-C Applicable for MIDAS IV AWOS from version 1.43
onwards.
M010027EN-D Applicable for MIDAS IV AWOS from version 2.1
onwards.
M010027EN-F This manual. Applicable for MIDAS IV AWOS from
version 3.0 onwards.
Table 3 Related Manuals
Manual Code Manual Name
M010027EN MIDAS IV AWOS Users Guide
M010028EN MIDAS IV AWOS Maintenance Manual
M010033EN MIDAS IV SYNOP Users Guide
M210308EN MIDAS IV SNOWTAM Users Guide
M210611EN MIDAS IV CLIMAT Users Guide
M210519EN MIDAS IV Database Reporting Tool Users Guide
M010003EN MIDAS IV LLWAS Users Guide
M210193EN MIDAS IV LLWAS Maintenance Manual
M210364EN MIDAS IV RVR Users Guide
M210365EN MIDAS IV RVR Maintenance Manual
M210389EN Administrating MIDAS IV in Windows 2000, Technical
Reference
VAISALA_______________________________________________________________________ 23
Feedback
Vaisala Customer Documentation Team welcomes your comments and
suggestions on the quality and usefulness of this publication. If you find
errors or have other suggestions for improvement, please indicate the
chapter, section, and page number. You can send comments to us by e-
mail: manuals@vaisala.com.
Safety
General Safety Considerations
Throughout the manual, important safety considerations are highlighted
as follows:
NOTE
For information concerning the use of data collectors, sensors, or other
installed hardware, refer to the appropriate device manuals.
WARNING
Warning alerts you to a serious hazard. If you do not read and follow
instructions very 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
Note highlights important information on using the product.
Users Guide ______________________________________________________________________
24 ___________________________________________________________________M010027EN-F
Regulatory Compliances
The MIDAS IV system is designed according to the recommendations
of international air traffic authorities as presented in the following
sources.
Trademarks
Microsoft, Windows, Windows NT, Windows 2000, and
Windows XP are registered trademarks of Microsoft Corporation in
U.S. and/or other countries.
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 License
Agreement.
Technical Support
Table 4 International Recommendations Applied to
MIDAS IV AWOS Software
Document Name Year
Meteorological Service for International Air Navigation.
Annex 3. ICAO. 15th edition.
2004
Aeronautical Telecommunications. Annex 10. Vol. II
(Communication procedures). ICAO. 6th edition.
2001
Manual of Runway Visual Range Observing and Reporting
Practices. ICAO. 2nd edition.
2000
Manual of Aeronautical Meteorological Practice (Doc 8896).
ICAO. 5th edition.
1997
Manual on Codes. Volume I.1 (Annex II to WMO Technical
Regulations). WMO No. 306.
1995
For technical questions, contact the Vaisala technical support:
E-mail helpdesk@vaisala.com
Phone (int.) +358 9 8949 2789
Fax +358 9 8949 2790
Chapter 2 __________________________________________________________ Product Overview
VAISALA_______________________________________________________________________ 25
CHAPTER 2
PRODUCT OVERVIEW
This chapter gives an overview of the MIDAS IV system and its
components.
Introduction to MIDAS IV
MIDAS IV AWOS is an automated weather observing system 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 and alerts with the
Weather View application. The values can be stored in the ASCII Log
View application. Event Monitor and Actuals applications are for
monitoring and handling system error situations.
Users Guide ______________________________________________________________________
26 ___________________________________________________________________M010027EN-F
Weather reports can be edited and sent with METAR/MET REPORT
and other weather report applications.
A typical MIDAS IV system is presented in Figure 1 on page 26.
0109-001
Figure 1 A Typical MIDAS IV System
MIDAS IV Versions
MIDAS IV AWOS is part of the Vaisala MIDAS IV product family, an
integrated family of airport weather systems.
The MIDAS IV can be one of the following versions:
- MIDAS IV AWOS (including RVR)
- MIDAS IV AWOS (including RVR) with LLWAS
- MIDAS IV with RVR only (MIDAS IV RVR)
The following numbers refer to Figure 1 on page 26:
1 = Sensor data
2 = Central data unit(s)
3 = Local Area Network
4 = Workstations
VAISALA_______________________________________________________________________ 27
All versions 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
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 the appropriate MIDAS IV
Maintenance Manual.
System Configuration
The MIDAS IV system is 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
Weather View application can be configured according to user
preferences.
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
MIDAS IV. Thus, your MIDAS IV system might differ slightly from
what is presented in this manual.
CAUTION
System configuration is only allowed by authorized Vaisala personnel.
Users Guide ______________________________________________________________________
28 ___________________________________________________________________M010027EN-F
End-user Software Applications
The MIDAS IV 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 MIDAS IV AWOS software focuses on the following aspects of
airport weather observation:
- Displaying current weather data (Weather View)
- Sending weather reports (report applications, for example,
METAR/MET REPORT)
- Ensuring the validity of weather data by monitoring the operation
of the system (Event Monitor).
- In exceptional situations, replacing automatic sensor data with
manual input (Actuals, Data Source Manager).
- Viewing past weather data (ASCII Log View, History Monitor).
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.
Viewing Current Data
Weather View
The Weather View application is used for viewing current
meteorological data in numerical and graphical format. It can also
display the status of sensors and the status of the data. Optionally, the
Weather View application can include the audiovisual alarm function.
VAISALA_______________________________________________________________________ 29
Editing and Sending Weather
Reports
METAR/MET REPORT
The METAR/MET REPORT application is used for editing and
sending METAR/SPECI reports and, depending on the system
configuration, MET REPORT/SPECIAL reports.
The METAR/ MET REPORT template can also include the option for
sending Automated METAR and SPECI reports. In this case, no user
action is needed to send the report to the AFTN line.
TAF (Optional)
The TAF application is used for editing and sending terminal area
forecasts.
SIGMET (Optional)
The SIGMET application is used for editing and sending SIGMET
reports.
GAMET (Optional)
The GAMET application is used for editing and sending GAMET
reports.
AIRMET (Optional)
The AIRMET application is used for editing and sending AIRMET
reports.
AD WRNG (Optional)
The AD WRNG application is used for creating and sending
Aerodrome Warning reports.
Users Guide ______________________________________________________________________
30 ___________________________________________________________________M010027EN-F
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 the separate MIDAS IV
SYNOP User's Guide (M010033EN).
SNOWTAM (Optional)
The SNOWTAM application is used for editing and sending
SNOWTAM reports. For more information on SNOWTAM, see the
separate MIDAS IV SNOWTAM User's Guide (M210308EN).
CLIMAT (Optional)
The CLIMAT application is used for editing and sending CLIMAT
reports. For more information on CLIMAT, see the separate MIDAS IV
CLIMAT User's Guide (M210611EN).
Entering Data Manually
Actuals
The Actuals application is used for entering manual or backup data in
the system when a sensor is being serviced or calibrated. Also manual
observations can be entered for parameters that the system does not
measure automatically.
Data Source Manager
The Data Source Manager application is used for entering manual
values for the pressure and prevailing visibility data in the system. The
application is also used for selecting which data source is used for the
values.
VAISALA_______________________________________________________________________ 31
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.
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 the separate MIDAS
IV Database Reporting Tool Users Guide (M210519EN).
AFTN Monitor
AFTN Monitor is an application for viewing all types of reports sent
from the airport to the AFTN line.
AFTN Viewer
AFTN Viewer is an application for viewing reports of configurable
types received from the AFTN line.
Managing Data Source and Settings
Data Source Manager
In addition to entering manual data, the Data Source Manager
application is also used for managing the data source.
Users Guide ______________________________________________________________________
32 ___________________________________________________________________M010027EN-F
METAR/MET REPORT Manager
METAR/MET REPORT Manager is a tool for defining which
measurement sites the METAR/MET REPORT template uses for the
automatic data. It can also be used for defining that manual input is
used, and for defining the reporting order in MET REPORT.
Runway in Use Manager
Runway in Use Manager is an application for setting the runway in use
information.
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 of MIDAS IV for sending weather reports.
Monitoring System Operation
Event Monitor
The Event Monitor application is a tool for monitoring changes in
meteorological conditions and in the operation of sensors and the CDU.
Event Monitor keeps track of system events, such as sensor problems or
internal problems in the CDU, and displays messages informing of
these events. The situation can be monitored by observing the color of
the Event Monitor Status icon on the taskbar of the Windows
operating system. Optionally, the application can include the voice
alarm function.
VAISALA_______________________________________________________________________ 33
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 the
appropriate MIDAS IV Maintenance Manual.
Event Monitor
Event Monitor is also used for system maintenance purposes, see
section Event Monitor on page 32.
Diagnostic Monitor
The Diagnostic Monitor application is used for monitoring the status of
the CDU(s), internal components (ROA objects and services), and
workstation applications.
Sensor Terminal
The Sensor Terminal application is used for viewing the sensor and
field device data. It can also be used for sending commands to sensors
and other field devices.
SensorIO Monitor
SensorIO Monitor is a tool for checking general sensor status and
individual sensor details. It can also be used for saving technical data in
a file for troubleshooting purposes.
METAR/MET REPORT Manager
METAR/MET REPORT Manager is a tool for defining which
measurement sites the METAR/MET REPORT template uses for the
automatic data. It can also be used for defining that manual input is
used, and for defining the reporting order in MET REPORT.
Users Guide ______________________________________________________________________
34 ___________________________________________________________________M010027EN-F
Workstation Types
The MIDAS IV system typically includes different workstations for the
following groups of users:
- Air traffic controllers (Weather View Workstation, WV)
- Observers (Observer Workstation, OWS)
- Forecasters (Forecaster Workstation, FWS)
- System maintenance personnel (RCM Workstation)
The number of different workstations in the system depends on the
configuration of the system. Each workstation type has a preconfigured
workstation environment. Vaisala configures the user profiles (for
example, OWSUSER, FWSUSER, WVUSER, and RCM user) for the
workstations.
Each workstation includes a different set of applications depending on
the configuration of the system.
This manual covers the applications in WV, OWS, and FWS
workstations. There are separate manuals for some applications. Refer
to the list of related manuals. For information on the RCM workstation
and maintenance applications, see the appropriate MIDAS IV
Maintenance Manual.
VAISALA_______________________________________________________________________ 35
For an example of typical MIDAS IV AWOS applications in each
workstation type, see Table 5 on page 35.
Table 5 MIDAS IV AWOS Applications in Workstations
Application OWS FWS WV RCM
Weather View x x
x
1
1. The Weather View application in a WV workstation used by air traffic
controllers typically differs slightly from the Weather View used in an
OWS workstation.
Event Monitor x x x
ASCII Log View x x
METAR/MET REPORT x
x
2
2. The METAR/MET REPORT application in the FWS workstation includes
only the functionality of editing and sending a Trend forecast and the
Forecaster remark.
Actuals x
METAR/MET REPORT
Manager
x (x)
Diagnostic Monitor x
Sensor Terminal x
SensorIO Monitor x
Data Source Manager x (x)
AFTN Monitor x x
AFTN Viewer x x
AFTN Addressee Manager x (x)
Runway in Use Manager x
History Monitor (Optional) x
SYNOP (Optional) x
CLIMAT (Optional) x
TAF (Optional) x
SIGMET (Optional) x
GAMET (Optional) x
AIRMET (Optional) x
AD WRNG (Optional) x
WS WRNG (Optional) x
SNOWTAM (Optional)
x
3
3. SNOWTAM is typically used in a separate Runway Friction workstation.
Dial-up Manager (Optional)
x
4
4. The user interface in the RCM workstation has more features than the one
in OWS.
x
4
Database Reporting Tool
(Optional)
x
Users Guide ______________________________________________________________________
36 ___________________________________________________________________M010027EN-F
Chapter 3 ________________________________________________ Getting Started with MIDAS IV
VAISALA_______________________________________________________________________ 37
CHAPTER 3
GETTING STARTED WITH MIDAS IV
This chapter describes logging into the system, starting and exiting the
applications, and the user environment common to all applications.
Logging In
Log into the MIDAS IV computer with a valid Windows user name and
password, which depend on your user profile and the configuration of
the system. They include the necessary rights for all MIDAS IV
applications that you need in the daily tasks. If you receive error
messages when trying to log in, contact system maintenance personnel.
When you log in, the MIDAS IV system will start automatically.
Starting and Exiting Applications
Depending on your user profile and the system configuration, some
applications, typically Weather View and Event Monitor, start
automatically on top of each other when you log into a MIDAS IV
workstation. The Event Monitor and Weather View applications have to
be open at all times.
CAUTION
Keep the Weather View and Event Monitor applications open at all
times to be able to view meteorological data, alarms, and system
events. If it is necessary to exit these applications for a special reason,
such as system maintenance, you can do it by pressing ALT + F4.
Users Guide ______________________________________________________________________
38 ___________________________________________________________________M010027EN-F
To start the other applications, click the corresponding buttons on the
MIDAS IV Application Toolbar, or select them from the Start menu:
Start - Programs - Vaisala MIDAS IV and the name of the
application. Most of these applications do not have to be open at all
times. You can close these applications whenever you do not need them
by selecting Exit from the File menu.
MIDAS IV User Interface
When you log in, the MIDAS IV system will start automatically.
Depending on your user profile and system configuration, some
applications open automatically. Others can be opened using the
MIDAS IV Application Toolbar or the Start menu. The application
windows can be resized and arranged to make them visible at a glance.
0208-051
Figure 2 MIDAS IV AWOS User Interface
VAISALA_______________________________________________________________________ 39
MIDAS IV Application Toolbar
The Application Toolbar appears at the Windows desktop. The toolbar
contains the buttons for starting most of the MIDAS IV applications
configured for your user profile and the MIDAS IV system you are
using. Thus, the Application Toolbar might look different depending on
what applications are included in the system. Depending on the system
configuration, some applications may be started from the Start menu.
The Application Toolbar is always on top, that is, always visible on the
Windows desktop. Applications can be started by clicking the
corresponding toolbar button. When an application is open, its icon is
displayed on the taskbar.
0501-054
Figure 3 MIDAS IV Application Toolbar
1 = Application Toolbar
2 = Application windows (METAR/MET REPORT, Weather
View, Event Monitor)
3 = Taskbar
4 = Note field
5 = System Status icon
6 = Event Monitor Status icon
CAUTION
The Application Toolbar must be open at all times. If it is necessary to
close the toolbar for a special reason, such as system maintenance,
consider the operational situation carefully before closing the toolbar.
To close the toolbar, activate the toolbar and press ALT+F4. The
system asks if you want to close all MIDAS IV applications. If you
want to close the Application Toolbar only, click No.
Users Guide ______________________________________________________________________
40 ___________________________________________________________________M010027EN-F
The typical buttons on the MIDAS IV Application Toolbar are
presented in the following table.
Table 6 MIDAS IV AWOS Application Toolbar Buttons
Button Description
Weather View opens the Weather View application.
History Monitor opens the AFTN application (optional).
METAR/MET REPORT Manager opens the METAR/MET
REPORT Manager application.
Actuals opens the Actuals application.
Event Monitor opens the Event Monitor application.
Dial-up Manager opens the Dial-up Manager application
(optional).
Runway in Use opens the Runway in Use Manager application.
ASCII Log View opens the ASCII Log View application.
METAR/MET REPORT opens the METAR/MET REPORT
application.
SYNOP opens the SYNOP application (optional).
CLIMAT opens the CLIMAT application (optional).
TAF opens the TAF application (optional).
SIGMET opens the SIGMET application (optional).
GAMET opens the GAMET application (optional).
AIRMET opens the AIRMET application (optional).
AD WRNG opens the AD WRNG application for sending
aerodrome warning reports (optional).
WS WRNG opens the WS WRNG application for sending
windshear warning reports (optional).
SNOWTAM opens the SNOWTAM application (optional).
AFTN Monitor opens the AFTN Monitor application.
AFTN Viewer opens the AFTN application (optional).
Sends the text in the note field to other MIDAS IV workstations.
VAISALA_______________________________________________________________________ 41
Note Field
At the top of the main window on the right, there is a field for notes.
Short messages to all workstations in the MIDAS IV system can be sent
using the field. To send a message, do the following:
1. Type the message text in the note field.
2. Click the Send button. The message is distributed to all
workstations in the system.
System Status Icon
The System Status icon appears on the taskbar of the Windows
operating system after the Application Toolbar is opened. See Figure 4
on page 41.
0305-055
Figure 4 System Status Icon
The System Status icon indicates two things: which CDU is active and
what the status of that CDU is. The letter in the icon indicates which
CDU is the active CDU: letter A in systems that have one CDU, and
letter A or B in systems that have two CDUs.
In normal situations, the color of the icon is green. Red color indicates
system problems.
CAUTION
If the System Status icon is red, contact system maintenance
immediately.
Users Guide ______________________________________________________________________
42 ___________________________________________________________________M010027EN-F
Event Monitor Status Icon
The Event Monitor Status icon appears when the Event Monitor
application is opened. See Figure 5 on page 42.
0305-056
Figure 5 Event Monitor Status Icon
The Event Monitor Status icon indicates if there are new events in
Event Monitor. When the icon is red or blue, there are new events which
need to be acknowledged in the Event Monitor application.
For more information on monitoring and acknowledging events, see
Chapter 15, Event Monitor, on page 201.
Operating MIDAS IV
This section describes only functions that are common to all MIDAS IV
applications. For detailed descriptions, see the application-specific
chapters.
Selecting MIDAS IV Functions
To select the functions in MIDAS IV applications, do one of the
following:
- Select the menu options from the menu, for example, click File -
Open.
- Use the shortcut key combinations, for example CTRL+O, if
available (indicated in the menu).
- Click the buttons on the toolbar of each application.
VAISALA_______________________________________________________________________ 43
Switching between Applications
Usually there are several applications open simultaneously. To switch
from one application to another, do one of the following:
- In the Application Toolbar, click the icon of the application you
want to switch to. See section MIDAS IV Application Toolbar on
page 39.
- On the taskbar, click the corresponding button.
Arranging Windows
The windows can be resized and moved around on the screen. If all the
data does not fit into the resized windows, use the scroll bars to view the
data.
Showing, Hiding, and Moving
Toolbars in Applications
The toolbars in all MIDAS IV applications can be hidden. This is useful
if you prefer to use menu options for selecting functions, or if you need
more room on the screen.
To show or hide the toolbar of the active application, do the following:
1. Select the View menu. If there is a check mark next to the Toolbar
option on the menu, the toolbar is shown on the screen.
2. Click the Toolbar option to remove the check mark. The toolbar
will not be displayed on the screen.
To move the toolbar to a new location within the application window,
do the following:
1. Move the mouse cursor over the gray background of the toolbar
(not over an icon).
2. Press and hold down the left mouse button and drag the toolbar to
the new location.
3. Release the left mouse button.
Users Guide ______________________________________________________________________
44 ___________________________________________________________________M010027EN-F
Showing and Hiding Status Bars
Each application has a status bar at the bottom of the screen. The status
bar contains general information and short instructions on the
application. To show or hide the status bar of the active application, do
the following:
1. Select the View menu. If there is a check mark next to the Status
Bar option on the menu, the status bar is shown on the screen.
2. Click the Status Bar option to remove the check mark. The status
bar will not be displayed on the screen.
Printing
If the system includes a local or network printer, the active application
window can be printed. Select the Print option, which is on the first
menu of each application.
The printer and paper settings can be changed with the Print Setup
option, which is always on the first menu of each application.
Chapter 4 _____________________________________________________________ Weather View
VAISALA_______________________________________________________________________ 45
CHAPTER 4
WEATHER VIEW
This chapter contains instructions for viewing meteorological data
using the Weather View application.
Introduction to Weather View
The Weather View application shows instant and average values for
weather parameters in graphical and numerical format. The values are
updated several times a minute, as the system collects and processes
new sensor data. Weather View also displays the status of the data.
Optionally, Weather View can also include audiovisual alarms and the
latest weather report sent by MIDAS IV.
Weather View User Interface
The Weather View user interface consists of the menus, the toolbar, and
the weather data screens. The weather data screens typically consist of
identification data, weather data fields, wind rose(s), and graphs.
These elements are briefly explained in the following sections. For
instructions on using Weather View, see section Operating Weather
View on page 56.
Users Guide ______________________________________________________________________
46 ___________________________________________________________________M010027EN-F
Weather Data Screens
Weather View includes several weather data screens that show weather
parameters in various formats. When Weather View is opened, screen 1
appears by default. Other screens can be displayed by clicking the
corresponding button on Weather View toolbar.
The typical elements in the Weather View application are presented in
the following figure. The location of the elements in the screen depends
on the configuration.
0207-012
Figure 6 Weather View: Sample Weather Data Screen
NOTE
Weather data screens are individually configured for each system.
Thus, the screens presented in this chapter might not include the same
components as the ones in your system.
1 = Identification data (runway, time, and date)
2 = Wind rose
3 = Weather data fields
4 = Graphical field
5 = Sent METAR report
VAISALA_______________________________________________________________________ 47
Identification Data
Time, date, and runway information are displayed in the weather data
screens. The location in the screen depends on the configuration of the
system. These fields show the UTC time from the computer clock, the
current date, and the runways for which the data is shown.
Weather Data Fields
Weather View contains data fields for weather parameters, for example,
visibility, cloud, or pressure data.
The data on Weather View 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 recommendations and converted to
appropriate measurement units.
For a list of some typical weather parameters displayed in weather data
fields, see Appendix A, Parameter List, on page 325.
Data Field Status
The background of the data field indicates the status of the weather data.
For explanation of the typical colors, see Table 7 on page 48. In some
special systems the colors may differ from the typical set of colors.
Users Guide ______________________________________________________________________
48 ___________________________________________________________________M010027EN-F
When the data field status is not normal, see section Troubleshooting
Weather View on page 61 for some general instructions for solving
problems. Check also the local practices at the airport.
In Weather View, 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 Weather View 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 Weather View screens turns
to Invalid. The values will disappear from data fields and they are
indicated as missing with slashes.
- For instant values, the transition from invalid to missing happens
very quickly.
- For average values the transition happens more slowly. First, the
background color of average values turns red or white. The data
remains in the data fields until the system reaches the validation
limit. Validation limit is approximately 40 % of the entire average
period. In a 2-minute average, this would be 50 seconds. In a 10-
Table 7 Weather View: Weather Data Field Statuses
Background Status Description
Gray Normal The data is OK.
Red Invalid The data is not valid or it is out of the preset
validation limits. There are problems in sensor
calibration.
White Old The data is not updated. There are problems in
sensor communication.
///// Missing The data is not available because of problems
in the system, or the system has just been
restarted and there is not enough data
available yet.
Light blue Backup Data is coming from a backup sensor, because
of problems with the primary sensor.
Yellow Manual Data is entered manually by the user in the
Actuals application while maintenance is fixing
a sensor problem.
VAISALA_______________________________________________________________________ 49
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 (/////).
Figure 7 on page 49 presents the behavior of average values and their
data status during system restart.
0207-013
Figure 7 Data Status of Average Values in Problem Situations
Wind Rose
Depending on the workstation type and installation, the Weather View
application can also include one or several wind roses for wind data
indication. The wind rose includes several wind parameters in graphical
format, as presented in Figure 8 on page 50.
Background color red or white Background color gray, values missing (/////)
Sensor
disconnected
or out of order
Validation limit
(40% of total average
calculation period)
Total average
calculation
period
Users Guide ______________________________________________________________________
50 ___________________________________________________________________M010027EN-F
0109-006
Figure 8 Weather View: Wind Rose
1 = Runway direction
2 = Wind speed at the threshold, in preconfigured units. This is
normally an instant value.
3 = Wind direction at the threshold, in tens of degrees. This is
normally an average of the wind direction values during the
last 2 minutes. Depending on the system configuration, it can
also be an instant or 10-minute average value. See Figure 9 on
page 51. In this example, the wind direction is 120 degrees.
4 = The range of wind variation during the last 2 minutes, in tens
of degrees (the inner bar).
5 = The range of wind variation during the last 10 minutes, in tens
of degrees (the outer bar).
NOTE
If the system is configured to make a correction for magnetic variation
(the difference between true north and magnetic north), this correction
is shown in the 10-minute wind variation range. The correction is not
shown in the 2-minute wind variation range. Because of this, there
might be a slight difference between the starting points of the 2- and
10-minute wind variation ranges on the wind rose circle.
VAISALA_______________________________________________________________________ 51
Wind Direction Value Selection (Optional)
Some system configurations include the selection for the type of wind
direction value. With this option, it can be selected which wind
direction value is indicated by the wind direction arrow: instant, 2-
minute average, or 10-minute average. See Figure 9 on page 51.
0305-057
Figure 9 Wind Direction Value Selection (Optional)
Graphical Fields (Optional)
Depending on the configuration of the system, Weather View can also
include graphical fields.
0207-077
Figure 10 A Sample Graphical Field in Weather View
If the system includes more than one runway, all runways can be shown
in the same graph.
Users Guide ______________________________________________________________________
52 ___________________________________________________________________M010027EN-F
The scale of graphical fields can be adjusted using the Graph Scales
window which can be accessed by right-clicking the graph. See Figure
11 on page 52.
0207-078
Figure 11 Weather View: Graph Scales Window
The Graph Scales window contains selections for the vertical scale and
the time scale. The elements are described in Table 8 on page 52.
CAUTION
A graph continues collecting data until it is closed. If you close a
screen, the data collected by the graph will be lost. This could be
harmful if the graph collects long-term trend data (for example, 48-
hour trend).
Table 8 Weather View: Graph Scales Window Elements
Element Description
Min The minimum value on the vertical axis
Max The maximum value on the vertical axis
Step The gridline interval for the vertical axis
Auto Scale
1
1. Can be used only if the graph includes one parameter
Automatically adjusts the vertical scale so that all data is
shown in the graph
Hours The value on the horizontal axis, that is, the period for
which the systems collects the data for the graph
VAISALA_______________________________________________________________________ 53
METAR Report
Weather View screens can also display 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.
Audiovisual Alarms
If the system includes the audiovisual alarm function, a blinking alarm
frame is shown around the weather data field and a beeping alarm is
sounded, for example, when a weather parameter value exceeds a
preconfigured limit.
Alarm Window (Optional)
Depending on the system configuration, also an alarm window may be
displayed. The example alarm window presented in the following figure
includes the details of the alarm.
0207-016
Figure 12 Weather View: Alarm Window
The name of the alarm group is displayed in the title bar of the alarm
window, for example, the Observer group.
Users Guide ______________________________________________________________________
54 ___________________________________________________________________M010027EN-F
The Alarm window buttons and fields are explained in Table 9 on page
54.
Menu Bar
The Weather View functions can be selected from the menu bar.
Typical Weather View menus and menu commands are presented in the
following tables.
Table 9 Weather View: Alarm Window Elements
Element Description
Seconds for
automatic alarm ack
Shows the time after which the alarm will be
automatically acknowledged.
Message Shows the detailed alarm message.
Time Shows the time of the alarm.
ACKNOWLEDGE
ALARM
The alarm can be acknowledged by clicking this
button.
Table 10 Weather View: Display Menu
Command Description
Screen 1 (1 - 10) Opens the selected screen
Refresh Refreshes the active screen
Colors (Optional) Selects a color scheme, if configured
Open Opens a new screen
Close Closes the active screen
Print Prints the active screen
Print Setup Opens a window for changing the printer and paper
settings
Table 11 Weather View: Edit Menu
Command Description
Copy As Bitmap Copies the screen as a bitmap image to the
Clipboard
Table 12 Weather View: View Menu
Command Description
Toolbar Shows/Hides the Weather View toolbar
Status Bar Shows/Hides the Weather View status bar
VAISALA_______________________________________________________________________ 55
Toolbar
Toolbar is the fastest way to switch between the weather data screens.
The Weather View can include up to ten screens. Each screen has a
corresponding button. Typical buttons on the Weather View toolbar are
Status Bar
The status bar displays information on the current state of Weather
View. The status bar also shows context-sensitive help texts on Weather
View buttons. When you move the mouse over a button, a short
description of the button is shown on the status bar.
Table 13 Weather View: Window Menu
Command Description
Arrange Icons Arranges minimized window icons
Close All Closes all open screens
Screen 1 (1 - 10) Displays the selected screen
Table 14 Weather View Toolbar Buttons
Button Name and Description
"1" opens the first screen, "2" the second screen and so on.
Print prints the current screen.
Users Guide ______________________________________________________________________
56 ___________________________________________________________________M010027EN-F
Operating Weather View
Starting and Exiting Weather View
The Weather View application starts automatically when you log in to
a MIDAS IV workstation. You must keep it open at all times to ensure
that the system can update the data on the screen.
When you do not need to view the Weather View data, you can
minimize the Weather View application.
Opening and Closing Weather Data
Screens
When Weather View starts, Screen 1 is automatically displayed.
Depending on the configuration of the system, there might be several
weather data screens.
To open other weather data screens, do one of the following:
- Open the Display menu and select the screen you want to open, for
example, Screen 1.
- Click the appropriate toolbar button, for example, for Screen 1.
- Use the numeric keypad on the keyboard. Press the NumLock key
so that the NumLock light on the keyboard is on. Then select the
number for the screen, for example, numeric key 1 for Screen 1.
To close the active screen open the Display menu and select Close.
To close all open screens, open the Window menu and select Close All.
CAUTION
Do not exit the Weather View application unless you have a special
reason, such as system maintenance. If it is necessary to exit Weather
View for a special reason, you can do it by pressing ALT+F4.
CAUTION
When you close a screen that includes graphical data, the data is lost.
This could be harmful in case the graph collects long-term trend data
(for example, 48-hour trend).
VAISALA_______________________________________________________________________ 57
Monitoring Weather Data and Status
To monitor weather data and status, do the following:
1. Monitor the data in data fields, wind roses, and graphs. You can
change the scale of graphs, see section Adjusting Graph Scales on
page 59.
2. Monitor all the needed screens.
3. Monitor the background color of the data fields. If it turns to red,
white, yellow, or light blue, or if there are slashes in the data fields,
contact the maintenance personnel. For more information on the
colors and the procedure in problem situations, see section
Troubleshooting Weather View on page 61.
4. If an alarm window or an alarm frame is displayed, read the alarm
message in the alarm window and acknowledge the alarm.
For explanation of typical weather data parameters, see Appendix A,
Parameter List, on page 325.
Your system might also have been configured to display values on a red
background if the value is out of predefined range.
Acknowledging Audiovisual Alarms
(Optional)
If the system includes the audiovisual alarm function, there is blinking
alarm frame and a beeping alarm sound in Weather View when a
weather parameter value exceeds a preconfigured limit. The alarm will
be acknowledged automatically after a preconfigured time.
Optionally, also an alarm window may be displayed. To acknowledge
the alarm in the alarm window, do the following:
1. When an alarm window appears on the screen, read the message
text in the alarm window.
CAUTION
The Weather View application displays the weather data that the
system is configured to display. The layout, number, and order of data
fields and wind roses, as well as the status colors, are configured
individually for each system. Thus the colors in your system might
differ from the ones presented here.
Users Guide ______________________________________________________________________
58 ___________________________________________________________________M010027EN-F
2. Acknowledge the alarm by clicking the Acknowledge Alarm
button. The alarm window and the blinking frame disappear from
the screen, and the beeping sound ends.
3. Respond to the alarm in accordance with the airport-specific
practices.
4. If there is another alarm window under the acknowledged one,
acknowledge it by clicking its Acknowledge Alarm button.
If you do not acknowledge the alarm, it disappears automatically after
a preconfigured time. The Seconds for automatic alarm ack field
shows the time remaining until the system performs an automatic
acknowledgement.
Simultaneous Alarms
Several alarms can be active simultaneously. If you have not
acknowledged an alarm before a new one appears, values related to both
alarms blink on the screen at the same time. The new alarm window
appears on top of the previous one.
Alarm Groups
Depending on the system configuration, workstations of the same kind
(for example, OWS workstations) can form an alarm group. The name
of the group is displayed on the title bar of the Alarm window. The
alarms are shown on all workstations of the group, and any user
belonging to that group can acknowledge it. When one user
acknowledges the alarm, the alarm window disappears from the screens
of all group members.
CAUTION
The alarm can appear in any of the open weather data screens, not just
the one you are currently viewing.
NOTE
When you acknowledge the latest alarm, remember that there can be
previous alarm windows underneath it. Be sure to read and
acknowledge all the alarms.
VAISALA_______________________________________________________________________ 59
Viewing Stored Alarms
You can view the alarm information in the Event Monitor application.
For more information, see Chapter 15, Event Monitor, on page 201.
Depending on the system configuration, you can view the alarms in the
history files. You can view them with the ASCII Log View application.
For more information, see Chapter 16, ASCII Log View, on page 219.
Adjusting Graph Scales
If the system includes graphical fields, you can adjust the vertical graph
scale, the horizontal time scale, and the gridline steps manually.
To adjust the graph scales, do the following:
1. From the Display menu, select the weather data screen you want to
work with, for example Screen 1.
2. Right-click the graph for which you want to adjust the scale. The
Graph Scales window is displayed with the name of the parameter
at the top of the window.
3. If you wish to keep the original values for later use, copy them from
the window before proceeding.
4. In the Min and Max fields, enter the minimum and maximum
values you want to include in the graph. These are the values on the
vertical axis. If your system includes two runways, both runways
can be shown in the same graph. Adjust the scale so that it is large
enough to fully display both runways.
5. In the Step field, enter the desired gridline interval for the vertical
axis. The minimum step value you can use is (Max-Min)/10. If you
enter a lower value, Weather View corrects the scale automatically
using the minimum step.
6. In the Time Scale list box, select the period (1, 3, 6, 12, 24, 24, or
48 h) for which you want the system to collect data in the same
graph. You can also select a time period by entering it in the field.
This will be the value on the horizontal axis.
7. Close the Graph Scales window by clicking OK.
CAUTION
The system does not check the validity of the graph scale values that
you enter. Make sure the scale is large enough.
Users Guide ______________________________________________________________________
60 ___________________________________________________________________M010027EN-F
8. The system displays a message window informing you that the
original values will be lost. See Figure 13 on page 60.
0207-017
Figure 13 Graph Scale Change Warning Window
- If you are satisfied with the values you have entered, select
Yes and the graph scale will be immediately updated with the
settings you specified. The last entered settings are saved in
the system until you change them again.
- If you want to change the values, select No, and adjust the
values again.
Using Auto Scale in Graphs
If you do not want to adjust the vertical graph scale manually, you can
use the Auto Scale function. When this function is selected, the system
automatically fits the parameter values into the scale. When new data
comes in, the system automatically updates these values so that all data
is always shown in the graph. Auto Scale can be useful for parameters
with great variation, such as visibility.
To use the Auto Scale function, do the following:
1. From the Display menu, select the weather data screen you want to
work with.
NOTE
Auto Scale cannot be used with graphs that include more than one
parameter.
VAISALA_______________________________________________________________________ 61
2. Right-click the graph for which you want to adjust the scale. The
Graph Scales window opens.
3. Select the Auto Scale check box.
4. Close the Graph Scales window by clicking OK.
Troubleshooting Weather View
If you detect problems in Weather View, first check the Event Monitor
messages for more details on the situation. For more information, see
Chapter 15, Event Monitor, on page 201. If there are problems with the
sensors, the name of the sensor is included in the Event Monitor
message. Make a note of the sensor and report the information to
maintenance personnel.
Maintenance personnel will also tell you if you need to set a sensor to
Backup or Manual mode in the Actuals application.
The following table lists some problems that might occur when you are
using Weather View and some typical solutions to the problems. Check
the local practices for more detailed instructions.
NOTE
In Weather View, 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 MIDAS IV data handling routine.
Table 15 Troubleshooting Weather View
Problem Probable Cause Solution
There are slashes (/////)
in data fields.
The data is missing because of
problems in the system.
Check the Event Monitor messages. If
there is no DATA MISSING message,
wait for 10 minutes. The data status
should change back to normal (gray
data field background).
The system has been recently
restarted and there is not enough
data available yet.
If the slashes remain in the fields,
contact maintenance. If instructed to
do so by the maintenance personnel,
set the sensor to Backup or Manual
mode in the Actuals application.
Data field background is
red.
The data is invalid, or out of the
preset validation limits because of
problems in sensor calibration.
Contact maintenance.
Users Guide ______________________________________________________________________
62 ___________________________________________________________________M010027EN-F
white.
The data is not updated by the
system because of problems in
Wait for 5 minutes to see if the
background color of the data field
changes to gray (normal status). If
slashes appear in the data field
(missing status), contact
maintenance.
yellow and values do not
change.
The sensor is in manual mode
because of problems with the
sensor.
Contact maintenance for more
information.
light blue.
The data comes from a backup
sensor, because of problems with
the primary sensor.
Contact maintenance for more
information.
Cloudbase height and
instant cloud height
value is NCD.
NCD (No Clouds Detected)
appears automatically in cloud data
fields when the system has
detected a VER VIS condition.
No action is needed.
There are two or more
alarm windows or alarm
frames blinking on the
screen at the same time.
There are several alarm windows
on top of each other because the
previous alarms have not been
acknowledged.
Read and acknowledge all alarms.
There is an alarm
window on the screen,
but it disappears before
you can acknowledge it.
Your workstation belongs to an
alarm group, and another member
of the group has already
acknowledged the alarm, or the
system has acknowledged the
alarm automatically after the
preconfigured period.
You can view the stored alarms in
Event Monitor and, depending on the
configuration, in ASCII Log View. For
more information, see Chapter 15,
Event Monitor, on page 201, and
Chapter 16, ASCII Log View, on page
219.
There is no curve in the
graph or the curve
appears as a straight
line.
The graph scale is incorrectly
defined.
Right-click the graph and adjust the
scale in the Graph Scales window.
Table 15 Troubleshooting Weather View (Continued)
Chapter 5 _____________________________________________________ METAR/MET REPORT
VAISALA_______________________________________________________________________ 63
CHAPTER 5
METAR/MET REPORT
This chapter describes how to edit and send METAR, SPECI,
MET REPORT, and SPECIAL reports.
Introduction to METAR/MET REPORT
The METAR/MET REPORT application is used in Observer
workstations (OWS) for editing and sending the following weather
reports:
- METAR reports
- SPECI reports, if configured in the system
- local routine reports (MET REPORT), if configured in the system
- local special reports (SPECIAL), if configured in the system
At standard observation times, the METAR/MET REPORT template
appears on the screen. The automatic data has been filled in by the
system. The user has to check the automatic data, fill in the manual
fields, and build the report. The system then validates the data and
displays the final report code. The user can then send the report to
external systems, typically to the AFTN line. Full and half hour reports
can be sent to separate AFTN addresses.
The METAR/MET REPORT template can also include the option for
sending Automated METAR reports. If this option is selected, no user
action is needed to send the report to the AFTN line.
Users Guide ______________________________________________________________________
64 ___________________________________________________________________M010027EN-F
Depending on local practices, the METAR/MET REPORT template
can be used in Forecaster workstations (FWS) for providing the
TREND forecast to the observer and Forecaster remark (part of
METAR reports RMK group).
A separate application related to weather reports is the METAR/MET
REPORT Manager. The application is used for defining the source of
the data field values on the METAR/MET REPORT template. For
more information, see METAR/MET REPORT Manager on page 307.
METAR/MET REPORT User Interface
The METAR/MET REPORT user interface consists of the METAR/
MET REPORT template, the menus, and the toolbar, see Figure 14 on
page 64. These elements are briefly described in the following sections.
The application also includes the SPECI Limit Manager window for
defining the limits for triggering SPECI reports automatically.
0501-004
Figure 14 METAR/MET REPORT Template, METAR/SPECI
View
VAISALA_______________________________________________________________________ 65
For detailed information on the METAR/SPECI data fields, see section
Data Fields in METAR/SPECI View on page 69.
For specific instructions on how to use the application, see section
Operating METAR/MET REPORT on page 97.
MET REPORT/SPECIAL View (Optional)
If the system includes the MET REPORT/SPECIAL option, the
METAR/MET REPORT template has two separate views, the
METAR/SPECI view and the MET REPORT/SPECIAL view. The
views can be selected using the METAR and MET REPORT buttons
on the toolbar. The MET REPORT/SPECIAL view is presented in
Figure 15 on page 66.
1 = Menu bar
2 = Toolbar
3 = Report identification data
4 = Data fields
5 = Buttons for selecting METAR/SPECI or MET REPORT/
SPECIAL view (optional)
6 = Buttons for building and sending the report
7 = CODE field for the coded report
Users Guide ______________________________________________________________________
66 ___________________________________________________________________M010027EN-F
0305-015
Figure 15 METAR/MET REPORT Template, MET REPORT/
SPECIAL View
For detailed information on the MET REPORT/SPECIAL data fields,
see section Data Fields in MET REPORT/SPECIAL View (Optional)
on page 80.
Forecaster Workstation
In Forecaster workstations (FWS) the functionality of the METAR/
MET REPORT template is limited. It can only be used for creating and
sending the TREND forecast to the observer workstation and editing the
FORECASTER REMARK field. Only the TREND field, the BUILD
button, the SEND TO OWS button, and FORECASTER REMARK
field are available. The functionality of the TREND field is also
different from the field in OWS. For more information, see section
Replying to TREND Request on page 105.
VAISALA_______________________________________________________________________ 67
Report Identification Data
Report identification data is located at the top of the METAR/
MET REPORT template. The report identification data include:
- Name: METAR or MET REPORT
- Report code, when applicable: RRA (for retarded METAR) or
CCA, CCB, CCC etc. (for corrected METAR)
- Type: METAR (indicates also MET REPORT), SPECI, SPECIAL,
CORRECTED, RETARDED
- UTC time and date
The time in the UTC field is expressed using the Coordinated Universal
Time format. It is the time when the system has updated the template
data, not the sending time of the report. Thus, the time is not transferred
to the final report.
Data Fields
The METAR/MET REPORT template contains data fields that report
current weather conditions. The type of data fields (automatic or
manual) and measurement sites are specified in the system
configuration and in the METAR/MET REPORT Manager application.
The data on the METAR/MET REPORT template is current weather
data; it is updated by the system when the template appears on the
screen. When the template is being edited, the system does not
automatically update the data.
The data fields for METAR/SPECI reports are described in section Data
Fields in METAR/SPECI View on page 69, and the data fields for MET
REPORT/SPECIAL reports in section Data Fields in MET REPORT/
SPECIAL View (Optional) on page 80.
Automatic Data Fields
The system provides values to most fields on the template
automatically. The source of the data in the automatic fields is one of
the following:
Users Guide ______________________________________________________________________
68 ___________________________________________________________________M010027EN-F
- The sensor site or source specified in the METAR/MET REPORT
Manager application. For details, see Chapter 21, METAR/MET
REPORT Manager, on page 307.
- The corresponding field in the Manual Observations window in
the Actuals application, where it has been entered by a user. For
details, see Chapter 17, Actuals, on page 233.
Slashes in automatic fields may indicate missing data or sensor
communication problems. See section Troubleshooting METAR/MET
REPORT on page 122.
Manual Data Fields
Some data fields are manual, that is, the user has to enter the values
manually in the METAR/MET REPORT template. These fields are
defined as "manual" in the METAR/MET REPORT Manager
application or in the system configuration. Slashes (///) or white
background typically indicate manual fields.
Common Data Fields
If the system includes the MET REPORT/SPECIAL view, some data
fields are common for METAR/SPECI and MET REPORT/SPECIAL
reports. These fields are typically indicated by a darker background
color. Editing these fields will affect both report types. The following
data fields are typically common:
- PRESENT WEATHER
- Temperature (T)
- Dewpoint (DP)
- Pressure (QNH, REG. QNH)
- Recent weather (REWX)
- FORECASTER REMARK
- REMARK
- Clouds, depending on the system configuration
VAISALA_______________________________________________________________________ 69
Present weather codes have to be entered in the METAR report format.
The system automatically converts the data into MET REPORT format
when the report is built. The MET REPORT format is displayed in the
CODE field in MET REPORT/SPECIAL view.
Data Fields in METAR/SPECI View
This section describes the METAR/MET REPORT template data
fields in METAR/SPECI view. See Figure 14 on page 64. The view is
displayed when the METAR/SPECI option is selected from the View
menu.
The data fields in the template are individually configured for each
system. Thus, your template might not include all data fields described
in the following sections. For information on the data fields in the
MET REPORT/SPECIAL view, see section Data Fields in MET
REPORT/SPECIAL View (Optional) on page 80.
Reading Data Field Tables
In the following tables, the Type and Source column contains
information on the data field type and data source, including the
following:
- Data field type: automatic or manual. Automatic fields are filled in
automatically by the system only if the system includes the
appropriate sensor and configuration. The fields can also be
defined as manual depending on the configuration and situation.
- The corresponding element in the METAR/MET REPORT
Manager application, for example:
- "METAR/MET REPORT Manager: RVR 1" means that the
measurement site and data field type for this field has to be
selected in the RVR 1 field in METAR/MET REPORT
Manager.
NOTE
Editing the common fields affects both METAR/SPECI and MET
REPORT/SPECIAL reports. If editing is needed only for METAR/
SPECI or MET REPORT/SPECIAL reports, the data can be edited in
the report code in the CODE field after building the report. For details,
see the following sections.
Users Guide ______________________________________________________________________
70 ___________________________________________________________________M010027EN-F
- The corresponding element in the Manual Observations window
in the Actuals application, for example:
- "Manual Observations window: RWY State" means that
when using the Manual Observations window, the value for
this field has to be entered in the first RWY State field.
Note that when using the Manual Observations window, the correct
selections have to be first made in the METAR/MET REPORT
Manager application. For more information, see section Manual
Observations Window on page 242 and Chapter 21, METAR/MET
REPORT Manager, on page 307.
Wind Data Fields in METAR/SPECI
The first data field group on the template contains wind data. The wind
data fields for METAR/SPECI reports are described in Table 16 on
page 70.
Visibility Data Fields in METAR/SPECI
The second group of data fields on the template contains visibility data
for METAR/SPECI reports as described in the following tables.
Depending on the configuration, the visibility data can be presented and
reported either:
Table 16 Wind Data Fields in METAR/SPECI View
Field Explanation Type and Source
WIND, 1st field Wind direction in degrees, 10-minute
average
Automatic
METAR/MET REPORT Manager:
Wind
WIND, 2nd field Wind speed in knots, m/s, or km/h,
10-minute average
Automatic
Wind
GUST Maximum wind speed during the last
10 minutes
Automatic
Wind
VRB, 1st field Lower limit of wind direction variation
in degrees during the last 10 minutes
Automatic
Wind
VRB, 2nd field Upper limit of wind direction variation
in degrees during the last 10 minutes
Automatic
Wind
VAISALA_______________________________________________________________________ 71
- using the prevailing visibility values as specified by ICAO, see
Table 17 on page 71. For definition of prevailing visibility, see
Glossary on page 329 and ICAO Annex 3.
- or other visibility criteria, for an example, see Table 18 on page 71
Table 17 Prevailing Visibility Data Fields in METAR/SPECI
View (Used as Specified by ICAO)
PREVAILING VIS Prevailing visibility at the airport, 10-
minute average, reported as specified by
ICAO.
Automatic
Prevailing vis
MINIMUM VIS, 1st field The minimum visibility 10-minute
average at the airport, reported only
when needed, as specified by ICAO.
Automatic
Minimum vis
MINIMUM VIS, 2nd field
(list)
Direction of visibility (N, NE, EN, SE, S,
SW, W, NW, /, or NDV with automatic
METAR, if configured).
Manual
Table 18 Visibility Data Fields in METAR/SPECI View
(Using Other than Prevailing Visibility)
VIS, 1st field Depending on the configuration, either:
the 10-minute average visibility from the
selected site,
VIS 1
or the minimum value noted during the
last ten minutes from all of VIS sites, or
from a selected group of visibility
sensors.
VIS 1
VIS, 2nd field (list) Direction of visibility (N, NE, EN, SE, S,
Manual
VIS 2, 1st field Depending on the configuration, either:
the 10-minute average visibility from the
selected site,
VIS 2
or the maximum value noted during the
last ten minutes from all the VIS sites, or
from a selected group of visibility
sensors.
VIS 2
VIS 2, 2nd field (list) Direction of visibility (N, NE, EN, SE, S,
Manual
Users Guide ______________________________________________________________________
72 ___________________________________________________________________M010027EN-F
RVR Data Fields in METAR/SPECI
The third group of data fields on the template contains RVR data. The
RVR values for METAR/SPECI reports can be displayed for up to four
RVR sites, depending on the configuration of the system. For each site
there are five data fields displaying the values as presented in Table 19
on page 72.
Table 19 RVR Data Fields in METAR/SPECI View
RVR, RVR 2, RVR 3,
RVR 4
Measurement site of Runway Visual Range,
sites 1 - 4
1
1. RVR2, RVR3, and RVR4 fields are not reported if their site location is missing.
Entered by the system /
Manual
MNM Minimum 1-minute average RVR value
noted from the site during the last 10
minutes
Automatic
METAR/MET REPORT
Manager: RVR fields
AVG Average RVR during the last 10 minutes Automatic
METAR/MET REPORT
Manager RVR fields
MAX Maximum 1-minute average RVR value
noted from the site during the last 10
minutes
Automatic
METAR/MET REPORT
Manager RVR fields
RVR, 5th field (list) Tendency of RVR from the site during the
last 10 minutes (N=No change, U=Upward,
D=Downward, /=Tendency data missing)
Automatic
METAR/MET REPORT
Manager RVR fields
VAISALA_______________________________________________________________________ 73
Present Weather Data Fields in METAR/SPECI
The present weather data fields are described in Table 20 on page 73.
The system automatically converts the present weather code entered in
METAR format into MET REPORT format when the report is built.
The MET REPORT format is displayed in the CODE field in MET
REPORT/SPECIAL view.
NOTE
Present weather fields are common for METAR/SPECI and
MET REPORT/SPECIAL reports. Editing these fields will also affect
MET REPORT/SPECIAL reports. If editing is needed only for one
report type, the data can be edited in the report code in the CODE field
after building the report.
Table 20 Present Weather Data Fields in METAR/SPECI
View
PRESENT WEATHER,
1st field
First present weather
code
Automatic, if system includes the FD12P sensor
METAR/MET REPORT Manager: Present Weather
Manual Observations window: Present Weather
Codes, first field
PRESENT WEATHER,
2nd field
Second present
weather code
Manual
Codes, second field
PRESENT WEATHER,
3rd field
Third present
weather code
Manual
Codes, third field
Users Guide ______________________________________________________________________
74 ___________________________________________________________________M010027EN-F
Cloud Data Fields in METAR/SPECI
The next group of data fields contains cloud data. The typical template
shows four cloud layers. The first row from the top is for the lowest
cloud layer (cloudbase). Table 21 on page 74 lists the data fields
provided for each layer.
Table 21 Clouds and Vertical Visibility Data Fields in
METAR/SPECI View
CLOUDS, 1st row, 1st
field (list)
Cloud amount (VV, SKC, FEW,
SCT, BKN, OVC).
SKC and VV automatic, if the system
includes a cloud height meter. Other
values manual with basic cloud height
meter, automatic with extended
Ceilometer.
METAR/MET REPORT Manager: Cloud
Manual Observations window: Cloud
Layers, Amount
CLOUDS, 1st row, 2nd
field
Cloud height in meters, feet, or
hundreds of feet
Automatic, if the system includes a cloud
height meter.
METAR/MET REPORT Manager: Cloud
Layers, Height
CLOUDS, 1st row, 3rd
field (list)
Cloud type (CB, TCU, empty =
other than CB/TCU, or /// = type
info not available)
Manual
Layers, Type
CLOUDS, all other rows Like the fields in the first row of
the Clouds group, except the
cloud amount options: are FEW,
SCT, BKN, OVC. The 1st row is
for the lowest cloud layer, the
last row for the highest layer.
See above.
NOTE
When there is a SKC or VV condition, the system automatically
overwrites other data in the CLOUDS fields that may have been
entered manually.
VAISALA_______________________________________________________________________ 75
Temperature and Pressure Data Fields in METAR/
SPECI
The temperature and pressure data fields T, DP, QNH, and REG.QNH
(optional) fields are described in Table 22 on page 75.
NOTE
Temperature and pressure (QNH and REG.QNH) data fields are
common for METAR/SPECI and MET REPORT/SPECIAL reports.
Editing these fields will also affect MET REPORT/SPECIAL reports.
If editing is needed only for one report type, the data can be edited in
the report code in the CODE field after building the report.
Table 22 Temperature and Pressure Data Fields in METAR/
SPECI View
T Temperature in Celsius degrees Automatic
METAR/MET REPORT Manager: Humidity
and temperature
DP Dew point in Celsius degrees Automatic
and temperature
QNH Pressure reduced to the mean sea
level in hectopascals
Automatic
METAR/MET REPORT Manager field:
Pressure
REG. QNH (Optional) The estimated lowest
QNH value for the next 3 hours (the
field may be used for this purpose
only with a special permit from
ICAO)
1
1. Will be added in the final code in the RMK group
Manual
Manual Observations window: Regional QNH
Users Guide ______________________________________________________________________
76 ___________________________________________________________________M010027EN-F
Recent Weather (REWX) Data Field in METAR/
SPECI
The REWX (recent weather) data field is described in Table 23 on page
76.
NOTE
The recent weather (REWX) data field is common for METAR/
SPECI and MET REPORT/SPECIAL reports. Editing the field will
also affect MET REPORT/SPECIAL reports. If editing is needed only
for one report type, the data can be edited in the report code in the
CODE field after building the report.
Table 23 REWX (Recent Weather) Data Field in METAR/
SPECI View
REWX Recent weather code Automatic, if system includes the FD12P sensor
METAR/MET REPORT Manager: Present weather
Manual Observations window: Recent Weather Codes
VAISALA_______________________________________________________________________ 77
WIND SHEAR Data Field in METAR/SPECI
The WIND SHEAR data field can be filled in by entering the value in
the data field, or by using the Wind Shear Data window, which can be
accessed by clicking the WIND SHEAR button.
0305-004
Figure 16 Wind Shear Data Window
For METAR/SPECI reports, you can select the runway(s) where there
is a wind shear, or all runways.
Table 24 Wind Shear Data Window Elements
Element Description
Runways
frame
Select the runway(s) with wind shear for METAR/SPECI
and MET REPORT/SPECIAL reports.
METAR/
SPECI Only
frame
Select wind shear for all runways for METAR/SPECI
reports (overrides the selections for METAR/SPECI in the
Runways frame).
Local Report
Only frame
Select the additional wind shear options for MET REPORT/
SPECIAL reports (overrides the selections made for MET
REPORT/SPECIAL in the Runways frame).
OK Accepts the selections.
Cancel Cancels the selections and closes the window.
Clear all Clears all selections.
Users Guide ______________________________________________________________________
78 ___________________________________________________________________M010027EN-F
RUNWAY STATE Data Field in METAR/SPECI
The RUNWAY STATE data field is described in Table 25 on page 78.
TREND Field in METAR/SPECI
The TREND field is a special data field in which the TREND forecast
is entered. The functionality of the TREND field is different in
Observer (OWS) and FWS (Forecaster) workstations.
In the Observer workstation (OWS) the TREND has to be entered in
METAR format in the TREND field in the METAR/SPECI view. It can
be edited only in METAR/SPECI view. The system converts the data
into MET REPORT/SPECIAL format in the MET REPORT/SPECIAL
view when building the report. If changes are needed only for one report
type, the data can be edited in the report code in the CODE field after
building the report.
In the Forecaster workstation (FWS) the TREND can be entered in both
formats and edited in both views. This can be configured to concern the
Observer as well.
Table 25 RUNWAY STATE Data Field in METAR/SPECI
View
RUNWAY STATE State of runway Manual. Can be automatic if the system includes the
Snowtam workstation with the supporting equipment.
Manual Observations window: RWY State
VAISALA_______________________________________________________________________ 79
REMARK Field in METAR/SPECI
The REMARK field is for additional information. The system adds the
data in the REG QNH (optional) and RUNWAY STATE fields
automatically after the RMK code in the report.
FORECASTER REMARK Field in METAR/SPECI
(Optional)
The FORECASTER REMARK field is for additional information.
Unlike the REMARK field, the FORECASTER REMARK field can
also be accessed from the Forecaster workstation. The system adds the
data in this field automatically to the RMK group in the final report.
NOTE
The REMARK field is common for METAR/SPECI and
MET REPORT/SPECIAL reports. Editing this field will affect both
report types. If editing is needed only for one report type, it can be
done in the report code in the CODE field after building the report.
NOTE
The FORECASTER REMARK field is common for METAR/
SPECI and MET REPORT/SPECIAL reports. Editing this field will
affect both report types. If editing is needed only for one report type,
it can be done in the report code in the CODE field after building the
report.
Users Guide ______________________________________________________________________
80 ___________________________________________________________________M010027EN-F
Data Fields in MET REPORT/
SPECIAL View (Optional)
If configured in the system, the METAR/MET REPORT template
includes a separate view for local MET REPORT/SPECIAL values. See
Figure 15 on page 66. The view is displayed when the MET REPORT/
SPECIAL option is selected from the View menu. This section
describes the data fields in the MET REPORT/SPECIAL view.
The data fields in the template are individually configured for each
system. Thus, the template in your system might not include all data
fields described in the following sections. The data fields in METAR/
SPECI view are described in section Data Fields in METAR/SPECI
View on page 69.
Reading Data Field Tables
In the following tables, the Type and Source column contains
information on the data field type and data source, containing the
following:
- Data field type: automatic or manual. Automatic fields are
automatically filled in by the system only if the system includes the
appropriate sensor and configuration. The fields can also be
defined as manual depending on the configuration and situation.
- The corresponding element in the METAR/MET REPORT
Manager application:
- Most of the values come from the site defined in the Runway
Landing Directions and Reporting Orders for Local
Reports frame.
- Some values are common with METAR/SPECI. For example,
"METAR/MET REPORT Manager: Humidity and
temperature" means that the values come from the sensor site
or source selected in the METAR/MET REPORT Manager
field Humidity and temperature.
- The corresponding element in the Manual Observations window
in the Actuals application, for example:
- "Manual Observations window: Present Weather Codes"
means that when using the Manual Observations window,
VAISALA_______________________________________________________________________ 81
the value for this field has to be entered in the first Present
Weather Codes field.
Note that when using the Manual Observations window, the correct
selections have to be first made in the METAR/MET REPORT
Manager application. For more information, see Chapter 21, METAR/
MET REPORT Manager, on page 307 and section Manual
Observations Window on page 242.
Wind Data Fields in MET REPORT/SPECIAL
The first data field group on the template contains wind data. The wind
data fields for MET REPORT/SPECIAL reports are described in Table
26 on page 81.
Table 26 Wind Data Fields in MET REPORT/SPECIAL
View
WIND, 1st field Wind direction in degrees, 2-
minute average
Automatic
METAR/MET REPORT Manager: Runway
Landing Directions and Reporting Orders
for Local Reports
1
WIND, 2nd field Wind speed in knots, m/s, or
km/h, 2-minute average
Automatic
for Local Reports
1
MAX Maximum wind speed
during the last 10 minutes
Automatic
for Local Reports
1
MNM Minimum wind speed during
the last 10 minutes
Automatic
for Local Reports
1
VRB, 1st field Lower limit of wind direction
variation in degrees during
the last 10 minutes
Automatic
for Local Reports
1
VRB, 2nd field Upper limit of wind direction
variation in degrees during
the last 10 minutes
Automatic
for Local Reports
1
Users Guide ______________________________________________________________________
82 ___________________________________________________________________M010027EN-F
If there are more than one local wind sites, only one site is displayed and
can be edited in the template. This is the site that has been selected as
the first site to be reported in METAR/MET REPORT Manager
application. All sites are displayed in a separate MET REPORT/
SPECIAL Wind Data window, which can be opened by clicking the
All Locations button. The sites are displayed in the reporting order
selected in METAR/MET REPORT Manager. These values can only be
edited in the MET REPORT/SPECIAL Wind Data window, not in
the template.
Depending on the configuration, the sites to be included in the MET
REPORT can be selected using the check boxes on the left. The
selections will be saved and used in the following reports until you
make new selections.
A MET REPORT/ SPECIAL Wind Data window is presented in
Figure 17 on page 82. For explanation of the data fields, see Figure 17
on page 82.
0305-016
Figure 17 MET REPORT/SPECIAL Wind Data Window
All Locations If configured, displays the
MET REPORT/SPECIAL
Wind Data window with the
wind data of other available
wind sites
1. If there are more than one local wind sites, the site that is shown in the template is the one that has been
selected as the first site to be reported in METAR/MET Report Manager application.
Table 26 Wind Data Fields in MET REPORT/SPECIAL View
(Continued)
VAISALA_______________________________________________________________________ 83
Visibility Data Fields in REPORT/SPECIAL
The second group of data fields contains the 1-minute average visibility
data for MET REPORT/SPECIAL reports. See Table 27 on page 83.
The values for all the VIS sites are displayed on the template in the
reporting order specified in the METAR/MET REPORT Manager
application. Each visibility field includes the name of the runway and
runway section depending on the configuration; typically TDZ
(touchdown zone) and END.
REPORT can be selected using the check boxes. The selections will be
saved and used in the following reports until you make new selections.
RVR Data Fields in MET REPORT/SPECIAL
The third group of data fields contains the RVR data for
MET REPORT/SPECIAL reports. See Table 28 on page 83.
The values for all the RVR sites are displayed on the template in the
reporting order specified in the METAR/MET REPORT Manager
application. Each RVR field includes the name of the runway and
runway section depending on the configuration; typically TDZ
(touchdown zone), MID, and END.
Table 27 Visibility Data Fields in MET REPORT/SPECIAL
View
VIS, runway name and
section
Visibility, 1-minute average, for
the specified runway and section
Automatic
Runway Landing Directions and
Reporting Orders for Local Reports
Table 28 RVR Data Fields in MET REPORT/SPECIAL View
RVR, runway name and
section
RVR, 1-minute average, for the
specified runway and section
Automatic
Users Guide ______________________________________________________________________
84 ___________________________________________________________________M010027EN-F
REPORT can be selected using the check boxes. The selections will be
saved and used in the following reports until you make new selections.
Present Weather Data Fields in MET REPORT/
SPECIAL
The present weather data fields are described in Table 29 on page 84.
NOTE
The present weather codes have to be entered in METAR format. The
data will be displayed in MET REPORT format in the CODE field
after the report has been built.
NOTE
Present weather fields are common for METAR/SPECI and
MET REPORT/SPECIAL reports. Editing these fields will also affect
METAR/SPECI reports. If editing is needed only for one report type,
the data can be edited in the report code in the CODE field after
Table 29 Present Weather Data Fields in MET REPORT/
SPECIAL View
PRESENT WEATHER,
1st field
First present weather code Automatic, if the system includes the
FD12P sensor.
Present Weather
Manual Observations window:
Present Weather Codes
PRESENT WEATHER,
2nd field
Second present weather code Manual
PRESENT WEATHER,
3rd field
Third present weather code Manual
VAISALA_______________________________________________________________________ 85
Cloud Data Fields in MET REPORT/SPECIAL
The cloud data fields are described in Table 30 on page 85, which lists
the data fields provided for each layer. The typical template shows four
cloud layers. The first row from the top is for the lowest cloud layer
(cloudbase).
If there are more than one active local cloud sites, only one site is
displayed in the template. This is the site that has been selected as the
first site to be reported in METAR/MET REPORT Manager
application. All sites are displayed in a separate MET REPORT/
SPECIAL Cloud Data window, which can be opened by clicking the
All Locations button. See Figure 18 on page 86. The sites are displayed
in the reporting order selected in METAR/MET REPORT Manager.
These values can only be edited in the MET REPORT/SPECIAL Cloud
Table 30 Clouds Data Fields in MET REPORT/SPECIAL
View
CLOUDS, 1st row, 1st
field
Cloud amount (VV, SKC, FEW,
SCT, BKN, OVC)
SKC and VV automatic, if the system
includes a cloud height meter. Other
values manual with basic cloud height
meter, automatic with extended
Ceilometer.
1
1. If there are more than one active local cloud sites, the site that is shown in the template is the one that
has been selected as the first site to be reported in METAR/MET REPORT Manager application.
CLOUDS, 1st row, 2nd
field
Cloud height in meters, feet, or
hundreds of feet
Automatic
1
CLOUDS, 1st row, 3rd
field
Cloud type (CB, TCU) Manual
CLOUDS, all other rows Like the fields in the first row of
the Clouds group, except the
cloud amount options are: FEW,
SCT, BKN, OVC. The 1st row is
for the lowest cloud layer, the last
row for the highest layer
Automatic
1
All locations If configured, displays the
MET REPORT/ SPECIAL Cloud
Data window with the cloud data
of other available active cloud
sites.
Users Guide ______________________________________________________________________
86 ___________________________________________________________________M010027EN-F
Data window, not in the template. Depending on the configuration, the
sites to be included in the MET REPORT can be selected using the
check boxes.
0305-012
Figure 18 MET REPORT/SPECIAL Cloud Data Window
Temperature and Pressure Data Fields in MET
REPORT/SPECIAL
Temperature and pressure data fields are described in Table 31 on page
87.
NOTE
When there is a SKC or a VV condition, the system automatically
overwrites other data in the CLOUDS fields that may have been
entered manually.
NOTE
Temperature, pressure (QNH, REG QNH), and wind shear data fields
are common for METAR/SPECI and MET REPORT/SPECIAL
reports. Editing these fields will also affect METAR/SPECI reports. If
editing is needed only for one report type, the data can be edited in the
report code in the CODE field after building the report.
VAISALA_______________________________________________________________________ 87
QFE Data Fields in MET REPORT/SPECIAL View
If configured in the system, the next group of data fields contains data
related to QFE, airport level pressure.
If there are more than one active QFE sites, the values for all the
locations are displayed. If configured, the sites to be included in the
MET REPORT/SPECIAL reports can be selected using the check
boxes.
Table 31 Temperature and Pressure Data Fields in
MET REPORT/SPECIAL View
T Temperature in Celsius degrees Automatic
and temperature
DP Dew point in Celsius degrees Automatic
METAR/MET REPORT: Humidity and
temperature
QNH Pressure reduced to the mean sea level in
hectopascals
Automatic
METAR/MET REPORT: Pressure
REG.QNH (Optional) The estimated lowest QNH
value for the next 3 hours (the field may be
used for this purpose only with a special
permit from ICAO)
1
1. Will be added in the final code in the RMK group
Manual
Manual Observations window: Reg QNH
Table 32 QFE Data Fields in MET REPORT/SPECIAL View
QFE Pressure at the airport level in
hectopascals
Automatic
Landing Directions and Reporting
Orders for Local Reports
Users Guide ______________________________________________________________________
88 ___________________________________________________________________M010027EN-F
Recent Weather (REWX) Data Field in MET
REPORT/SPECIAL
Recent weather (REWX) data field is described in Table 33 on page 88.
WIND SHEAR Data Field in MET REPORT/SPECIAL
The WIND SHEAR data field can be filled in by entering the value in
the data field or by using the Wind Shear Data window, which can be
accessed by clicking the WIND SHEAR button.
For MET REPORT/SPECIAL reports, you can select the runway(s)
where the wind shear is, or the in approach or climb-out options.
NOTE
Recent weather (REWX) data field is common for METAR/SPECI
and MET REPORT/SPECIAL reports. Editing the field will also
affect METAR/SPECI reports. If editing is needed only for one report
type, the data can be edited in the report code in the CODE field after
Table 33 Recent Weather in MET REPORT/SPECIAL View
REWX Recent weather code Automatic, if system includes the FD12P sensor.
METAR/MET REPORT Manager: Present weather
Manual Observations window: Recent Weather
Codes
Manual Observations window: Recent Weather
Codes
VAISALA_______________________________________________________________________ 89
0305-004
Figure 19 Wind Shear Data Window
Table 34 Wind Shear Data Window Elements
Element Description
Runways frame Select the runway(s) with wind shear for METAR/SPECI
and MET REPORT/SPECIAL reports.
METAR/SPECI
Only frame
Select wind shear for all runways for METAR/SPECI
reports (overrides the selections for METAR/SPECI in the
Runways frame).
Local Report
Only frame
Select the additional wind shear options for MET
REPORT/SPECIAL reports (overrides the selections
made for MET REPORT/SPECIAL in the Runways
frame).
Cancel Cancels the selections and closes the window.
Clear all Clears all selections.
Users Guide ______________________________________________________________________
90 ___________________________________________________________________M010027EN-F
Other Supplementary Information Data Field in MET
REPORT/SPECIAL
Data for the other supplementary data group can be entered in the
OTHER SUPP. INFO field.
TREND Field in MET REPORT/SPECIAL
The TREND field is a special data field in which the TREND forecast
is entered. The functionality of the TREND field is different in
Observer (OWS) and FWS (Forecaster) workstations.
When making a MET REPORT/SPECIAL report, the TREND has to be
entered in the TREND field in the MET REPORT/SPECIAL view. No
validations are performed in this case.
In the Forecaster workstation (FWS) the TREND can be entered in both
formats and edited in both views. This can be configured to concern the
Observer as well.
REMARK Field in MET REPORT/SPECIAL
The REMARK field is for additional information. The system adds the
data in the REG QNH field automatically in the RMK group in the final
report code.
Table 35 Other Supp. Info in MET REPORT/SPECIAL View
OTHER SUPP. INFO Other significant meteorological data Manual
NOTE
The REMARK field is common for METAR/SPECI and
MET REPORT/SPECIAL reports. Editing this field will affect both
report types. If editing is needed only for one report type, it can be
done in the report code in the CODE field after building the report.
VAISALA_______________________________________________________________________ 91
FORECASTER REMARK Field in MET REPORT/
SPECIAL (Optional)
The FORECASTER REMARK field is for additional information.
Unlike the REMARK field, the FORECASTER REMARK field can
also be accessed from the Forecaster workstation. The system adds the
data in this field automatically to the RMK group in the final report.
CODE Field
The final report code is displayed in the CODE field. It is a combination
of all values in the data fields. Normally the values must be edited in the
data fields, not in the CODE field. In some cases, the text in the CODE
field can be edited by the user, if necessary. This can be useful when the
data field is common to METAR/SPECI and MET REPORT/SPECIAL
reports, but only one report type needs editing.
NOTE
The FORECASTER REMARK field is common for METAR/
SPECI and MET REPORT/SPECIAL reports. Editing this field will
affect both report types. If editing is needed only for one report type,
it can be done in the report code in the CODE field after building the
report.
Users Guide ______________________________________________________________________
92 ___________________________________________________________________M010027EN-F
SPECI Limit Manager Window
In the SPECI Limit Manager window you can define the limits for
triggering SPECI reports. The window is displayed when you select
SPECI Limit Manager from the Settings menu, or click the SPECI
Limit Manager button in the toolbar. See Figure 20 on page 92.
0411-109
Figure 20 SPECI Limit Manager Window
The window displays the pre-defined SPECI limits for several
parameters. You can change the limits, either by entering a new value,
or selecting from the pre-entered values in the lists. You can also add
new values or remove the pre-entered values in the lists. For
instructions on using the window, see section Changing SPECI
Triggering Limits on page 118.
VAISALA_______________________________________________________________________ 93
Buttons in the METAR/MET
REPORT Template
The buttons in the METAR/MET REPORT template are described in
Table 37 on page 93. For description of the METAR/MET REPORT
toolbar buttons, see Table 43 on page 96.
Table 36 SPECI Limit Manager Window Elements
Element Description
Fields for limits Displays the limit used for triggering SPECI for the reason
indicated in the field name. You can enter a new limit, or
select from the pre-defined limits in the lists.
Add Opens the Add window for adding new pre-defined limits in
the lists.
Remove Removes the selected pre-defined limit from the list.
Reset to ICAO Fills in the fields with the values specified by ICAO (Annex
3).
OK Saves the changes and closes the window.
Apply Saves the changes without closing the window.
Cancel Cancels the changes and closes the window.
Table 37 Buttons in METAR/MET REPORT Template
Button Description
BUILD Builds and validates the report (the TREND in FWS).
SEND Sends the report to the external interface, typically AFTN
line.
ACCEPT (Displayed only when improvement SPECI is triggered)
Places the SPECI in the waiting buffer for a preconfigured
period of time before it can be sent.
All Locations (In the WIND group, if configured in the system) Opens the
MET REPORT/SPECIAL Wind Data window for viewing
and editing local wind data for MET REPORT/SPECIAL.
All Locations (In the CLOUDS group, if configured in the system) Opens
the MET REPORT/SPECIAL Wind Data window for
viewing and editing local cloud data for MET REPORT/
SPECIAL.
WIND SHEAR Opens the Wind Shear Data window for selecting the
runways with wind shear.
Old Enters the previous TREND in the TREND field.
SEND TO
OWS
(In Forecaster workstation) Sends the TREND to Observer.
Users Guide ______________________________________________________________________
94 ___________________________________________________________________M010027EN-F
Menu Bar
The METAR/MET REPORT template functions can be selected from
the menu bar. The typical menus and menu commands are presented in
the following tables. Depending on the system configuration, all options
may not be available.
Table 38 METAR/MET REPORT: Report Menu
Command Description
BUILD Builds and validates the report
TREND Sends a TREND request to Forecaster
SEND Sends the report to the external interface, typically
the AFTN line
CORR Displays a template for a corrected METAR with the
data from the previously sent METAR report filled in
(or SPECI if sent after METAR)
SPECI Displays a new SPECI template for editing
SPECIAL Displays a new SPECIAL template for editing
Cancel Report Cancels the report that is being edited: the report is
not sent
Print Prints the template screenshot
Print Preview Displays the preview of the print
settings
Table 39 METAR/MET REPORT: 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
Copy to Clipboard Copies the template as a bitmap image to the
Clipboard
Table 40 METAR/MET REPORT: View Menu
Command Description
METAR/SPECI Displays the template in METAR/SPECI view, that is,
showing with the data fields related to METAR/SPECI
reports
VAISALA_______________________________________________________________________ 95
MET REPORT/
SPECIAL
If configured in the system, displays the template in
MET REPORT/SPECIAL view, that is, showing the
data fields related to MET REPORT/SPECIAL
reports
Toolbar Shows/Hides the toolbar
Status bar Shows/Hides the status bar
Table 41 METAR/MET REPORT: Settings Menu
Command Description
Automated METAR Turns the automated METAR function on: the
system sends the METAR report without user
intervention.
Automated SPECI Turns the automated SPECI function on; the
system sends the SPECI reports without user
intervention.
Minimize After Send Minimizes the template to the task bar after the
report has been sent.
No Consistency
Check
Turns the consistency check off. When selected,
the system does not display validation error
messages when building the report.
Trend Field from
Observer
Defines that observer provides the TREND
forecast.
METAR/MET
REPORT Manager
Opens the METAR/MET REPORT Manager
application.
SPECI Limit Manager Opens the SPECI Limit Manager window for
defining the limits used for triggering SPECI reports
automatically (available only in OWS workstation).
Select Font Opens a window for changing the font used in data
fields.
Table 42 METAR/MET REPORT: Help Menu
Command Description
About METAR/
MET REPORT
Template
Displays software version and copyright
information
Table 40 METAR/MET REPORT: View Menu (Continued)
Command Description
Users Guide ______________________________________________________________________
96 ___________________________________________________________________M010027EN-F
Toolbar
The METAR/MET REPORT toolbar typically contains the buttons
described in Table 43 on page 96. Depending on the system
configuration, some options may not be available.
Table 43 METAR/MET REPORT Toolbar Buttons
CORRECTED displays a template for a corrected METAR
with the data from the previously sent METAR filled in (or
SPECI if sent after METAR).
SPECI displays a new SPECI template for editing.
(In systems with MET REPORT/SPECIAL) SPECIAL
displays a new SPECIAL template for editing.
TREND request sends a TREND request to Forecaster.
Cut removes the selected text.
Copy copies the selected text.
Paste adds the copied or cut text at the cursor location.
Print prints the template.
No consistency check, turns the consistency check off.
When selected, the system does not display validation error
messages when building the report.
Trend field from observer, defines that observer provides
the TREND report.
Automated METAR, turns the automated METAR function
on: the system sends the METAR reports without user
intervention.
Automated SPECI, turns the automated SPECI function on:
the system sends the SPECI reports without user
intervention.
METAR/MET REPORT Manager, opens the application for
defining the source of data in the data fields.
SPECI Limit Manager, opens the application for defining
the limit for SPECI triggering.
METAR/SPECI, displays the template with the data fields
related to METAR/SPECI reports.
MET REPORT/SPECIAL, displays the template with the
data fields related to MET REPORT/SPECIAL reports.
VAISALA_______________________________________________________________________ 97
Status Bar
The status bar displays information on the current state of the METAR/
MET REPORT application and the reason for a SPECI report and
number of SPECIs waiting to be sent. The status bar also shows context-
sensitive help texts on METAR/MET REPORT buttons. When you
move the mouse over a button, a short description of the button is shown
on the status bar.
Operating METAR/MET REPORT
Starting and Exiting METAR/MET
REPORT
MIDAS IV starts the METAR/MET REPORT application
automatically when you log in. The application must be kept open at all
times so that the report templates can appear automatically on the screen
at standard observation times.
When you do not need to view the application window, you can
minimize it.
METAR Editing and Sending Times
METAR editing times and periods depend on the system configuration.
MET REPORT reports are sent at the same times.
Figure 21 on page 98 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.
CAUTION
Do not exit the METAR/MET REPORT application unless there is a
special reason, such as system maintenance. If it is necessary to exit
METAR/MET REPORT for a special reason, you can do it by pressing
ALT+F4. To start the METAR/ MET REPORT again, click the
METAR/MET REPORT button on the application toolbar,
otherwise the METAR/MET REPORT template will not appear
automatically at the predefined intervals.
Users Guide ______________________________________________________________________
98 ___________________________________________________________________M010027EN-F
0108-084
Figure 21 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 the template appears on
the screen. You have a preconfigured time to edit and send the template,
5 minutes in this example. During this time, the automatic values in the
template are not updated by the system.
The time that is shown in the CODE field is the sending time - in this
example, 20 minutes past or 10 minutes to. Note that the time in the
UTC field (at the top of the template) is not transferred to the final
report - it only tells you when the system has updated the template data.
For SPECI reports the time in the UTC and CODE fields is the time
when the system updates the template data. Both these fields have the
same time, unlike in METAR. The UTC time is not updated during
editing of SPECI.
Sending
time
Sending
time
Standard
observation
time
Standard
observation
time
Editing
time
Editing
time
VAISALA_______________________________________________________________________ 99
Editing and Sending Normal METAR
and MET REPORT Reports
The METAR/MET REPORT template appears on the screen
automatically when it is time to send a METAR report. If configured in
the system, a MET REPORT is generated and sent with every METAR
report.
For a detailed explanation of the user interface and the data fields, see
METAR/MET REPORT User Interface on page 64.
To edit, build, and send normal METAR reports when the METAR/
MET REPORT template appears, do the following:
1. When the template pops up, check that there are no slashes in the
automatic data fields and that the values fall within their normal
ranges. If there are slashes or incorrect values, inform the
maintenance personnel and correct the values manually.
2. Fill in the manual data fields and the remarks fields. If needed,
click the WIND SHEAR button to fill in the wind shear
information.
3. Depending on the practices at the airport, enter the TREND in the
TREND field by doing one of the following:
a. If it is your task to enter the TREND:
- Check that the Trend field from observer option is
selected from the Settings menu.
- If you want to retrieve the previous TREND to use it as
the basis for editing, click Old.
- Enter the text in the TREND field of the METAR/SPECI
view in METAR format. The system converts it to MET
REPORT format in the MET REPORT/SPECIAL view
when building the report. The TREND in MET REPORT
can be edited only in the CODE field after building the
report.
b. If it is the forecaster's task to enter the TREND:
- Check that the Trend field from observer option is NOT
selected from the Settings menu.
Users Guide ______________________________________________________________________
100 __________________________________________________________________M010027EN-F
- Request the TREND from the forecaster by clicking the
TREND request button. For details, see section
Requesting TREND from Forecaster on page 103.
4. If configured in the system, check the data and fill in the
MET REPORT/SPECIAL fields.
- Click the MET REPORT/SPECIAL button to display the
template in MET REPORT/SPECIAL view and check and
edit the fields as needed. If configured in the system, you can
select that some sites are not included in the report by
deselecting the check boxes next to the sites.
- If there are more than one sites for wind and cloud values in
MET REPORT/SPECIAL, click the All locations button to
check and edit the data fields for all the sites. If configured in
the system, you can define that some sites are not included in
the report by deselecting the check boxes next to the sites.
5. Build the report by clicking the BUILD button. The system
validates the report. If the system displays error messages, do one
of the following:
- If you click Yes, the report is built. Some data may be marked
with slashes.
- If you click No, the system does not continue building the
report. You can correct the values in the data fields and click
the BUILD button again.
For more information on validations performed by the system, see
section Validations on page 103.
NOTE
Some fields are common for METAR/SPECI and MET REPORT/
SPECIAL views. Editing these fields will affect both report types. If
you need to edit only one report type, edit the report code in the CODE
field after building the report. For more information, see section
Common Data Fields on page 68.
CAUTION
If the No consistency check option in the Settings menu is selected,
the system does not display the error messages. Instead, it replaces the
incorrect values by slashes in the final report code.
VAISALA______________________________________________________________________ 101
6. The system displays the final report text in the CODE field. Check
the report code. If there are errors in the code, do one of the
following:
- Correct the values in the template data fields and click BUILD
again.
- If the field is common for METAR/SPECI and
MET REPORT/SPECIAL reports and you want to correct
only one report type, correct the value in the CODE field and
do not build the report again. See section Common Data Fields
on page 68.
7. When the report is ready for sending, click the SEND button. The
system adds the AFTN headers to the METAR and MET REPORT
reports and sends the reports to the AFTN line and to other
workstations in the system, as configured.
8. If the Minimize after send option is selected from the Settings
menu, the system automatically minimizes the template window.
Users Guide ______________________________________________________________________
102 __________________________________________________________________M010027EN-F
0208-015
Figure 22 METAR/MET REPORT Editing Procedure
Check
automatic
values
OK?
NO
YES
YES
Enter
values in
manual fields
Check
code field
Send
report
Correct
manually
Contact
maintenance
Correct
manually in
data fields
From
Forecaster
?
NO
Add
TREND
Build report
NO
YES
Request
from
Forecaster
Enter
in TREND
field
Error
messages
?
YES
Correct
manually
in data fields
NO
OK?
VAISALA______________________________________________________________________ 103
Validations
When you click the BUILD button, the system performs a set of
validations, depending on the configuration. If the values are valid, the
system builds the report and you can send it. If the system finds invalid
values, it informs you about them with error messages.
The system checks that certain values, for example, temperature, dew
point, and pressure fall within the normal range.
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. An example validation error message in displayed
in Figure 23 on page 103.
0305-011
Figure 23 Example Validation Error Message
Requesting TREND from Forecaster
This section is intended for observers (OWS workstation) who request
the TREND from the forecaster.
NOTE
Some fields are common for METAR/SPECI and MET REPORT/
SPECIAL views. Editing these fields will affect both report types. To
correct the common fields so that the corrections affect only one report
type, select the report type from the View menu and make the
corrections in the CODE field. For details, see section Data Fields on
page 67.
NOTE
The system displays the messages only if the No consistency check
option from the Settings menu is NOT selected.
Users Guide ______________________________________________________________________
104 __________________________________________________________________M010027EN-F
If making the TREND is the forecaster's task at your airport, you need
to send a TREND request to the Forecaster Workstation (FWS).
To request a TREND from the forecaster, do the following:
1. Check that the Trend field from observer option from the
Settings menu is NOT selected.
2. Click the TREND button. A message window appears on the
screen.
0305-005
Figure 24 Request TREND Message Window in OWS
3. Click Yes in the message window. The TREND request is sent to
the forecaster.
4. When the forecaster has sent you the TREND, a message
informing of it will appear on the screen.
0305-006
Figure 25 Confirm TREND Message Window in OWS
5. If you click Yes, the TREND is automatically shown in the
TREND field. If you click No, the TREND sent by the forecaster
will be ignored.
The TREND field cannot be edited in the MET REPORT/SPECIAL
view. If you need to edit only one report type, edit the report code in the
CODE field after building the report.
VAISALA______________________________________________________________________ 105
Replying to TREND Request
This section is intended for forecasters who receive the TREND request
from the observer to the Forecaster workstation (FWS). When a
TREND request message appears on the screen, the observer is asking
you to send a TREND forecast to a METAR report he is currently
editing. To reply to a TREND request, do the following:
1. A message window informing you of the TREND request is
displayed. Click OK to close the window.
0305-007
Figure 26 Request TREND Message Window in FWS
2. In the METAR/MET REPORT template, enter the TREND
forecast in the TREND field. To edit the previous TREND, click
Old.
3. When you have finished writing the TREND, click the BUILD
button. The system builds the TREND text in the CODE field.
4. Click the SEND TO OWS button. A confirmation message
window appears on the screen.
NOTE
If your system includes the MET REPORT/SPECIAL view, the
TREND will be displayed in MET REPORT format in the CODE field
in the MET REPORT/SPECIAL after the report has been built. You
can also enter the TREND separately in METAR/SPECI and MET
REPORT/SPECIAL views.
Users Guide ______________________________________________________________________
106 __________________________________________________________________M010027EN-F
0305-008
Figure 27 TREND Confirmation Message in FWS
5. Click Yes to send the TREND to the Observer Workstation.
Canceling Current METAR/MET REPORT
If you need to cancel the METAR report before sending it, do the
following:
1. Select Cancel Report from the Report menu.
2. In the message window that is displayed, select Yes. The report
will not be sent and the data it contained will be lost.
NOTE
When you select Report - CORR after canceling a report, the last sent
report will be displayed on the template, not the canceled one.
VAISALA______________________________________________________________________ 107
Sending Delayed (Retarded)
METAR/MET REPORT Reports
If you do not send a regular METAR report within the predefined
editing period, the system automatically changes the report type to
retarded.
Edit, build, and send the report as you would a normal METAR report,
see section Editing and Sending Normal METAR and MET REPORT
Reports on page 99. The system adds the letters RRA to the AFTN
header and updates the time in the UTC field. The time in the CODE
field is the scheduled sending time of the original (normal) METAR
report.
If you have edited the report before it became retarded, the system
displays a message window, see Figure 28 on page 107.
0305-009
Figure 28 METAR Retarded Message Window
Do one of the following:
a. To keep the changes you have made, select Yes. The METAR/
MET REPORT template does not update the data with new sensor
values, instead, it appears with the text RETARDED in the TYPE
field, and includes the original values and the changes you have
made.
b. To update the data with new values from the sensors, and lose the
changes you have made, select No. The METAR/MET REPORT
template appears with the text RETARDED in the TYPE field, and
the system has filled in the data fields with new values from the
sensors.
Users Guide ______________________________________________________________________
108 __________________________________________________________________M010027EN-F
A delayed (retarded) METAR can be sent until the editing time of the
next normal report starts. A MET REPORT is always sent with the
delayed METAR reports.
Sending Corrected METAR/MET
REPORT Reports
After sending a normal METAR report, you might notice things that
need to be corrected, for example, typographic errors or missing values.
In such cases, you can generate and send a corrected report. Depending
on which report you want to correct, do one of the following:
a. If you want to correct the last report, the data of the last report can
be retrieved to the template. For details, see section Sending a
Correction to the Last Report on page 108.
b. If you want to correct a report that was sent before the last report,
you have to copy the data from other MIDAS IV applications. For
details, see section Sending a Correction to an Earlier Report on
page 110.
Sending a Correction to the Last Report
You can send a correction to the last sent report. If no other reports have
been sent after the report that you want to correct, the system can
retrieve the data of that report automatically to the template.
To send a corrected METAR/MET REPORT to the last report, do the
following:
1. Open the METAR/MET REPORT template.
NOTE
If the system generates a SPECI report while you are editing a delayed
METAR, the SPECI remains pending until you have sent the delayed
METAR report.
NOTE
If you have sent a report after the METAR/SPECI you wish to correct,
see section Sending a Correction to an Earlier Report on page 110.
VAISALA______________________________________________________________________ 109
2. From the Report menu, select CORR, or click the button on
the toolbar.
3. Click Yes in the window that is displayed. The system changes the
report type to METAR_CORRECTED, displays the data of the last
sent report in the data fields and the CODE field, and has added the
text COR in the report code.
4. Edit the data that needs correcting in the data fields.
5. Click BUILD. Check that the report text in the CODE field is
correct.
6. Click SEND. The system adds the code CCA (or CCB, CCC, CCD
etc. for the next corrected reports) and the abbreviated headers to
the report. It sends the report to the AFTN line and to other
Instead of editing the data fields, you can also make corrections directly
in the CODE field. After editing the CODE field, do not click the
BUILD button after editing, or the manual changes will be lost. If you
click the BUILD button, the system displays an error message as
presented in Figure 29 on page 109.
0208-048
Figure 29 Manual Changes Lost Warning Message Window
In the message window, do one of the following:
- If you select Yes, the system will build the report and the manual
changes you made in the CODE field will be lost.
- If you select No, you can send the report without building it.
A corrected MET REPORT is sent locally with the corrected METAR.
A separate corrected MET REPORT cannot be sent. If you need to
correct the MET REPORT information, you have to send a SPECIAL
report. See section Editing and Sending SPECIAL Reports on page 119.
Users Guide ______________________________________________________________________
110 __________________________________________________________________M010027EN-F
Sending a Correction to an Earlier Report
Corrections can also be made to reports that were sent earlier, before the
last sent report. This can be, for example, when the last sent report is
SPECI and you want to correct the last sent METAR. The system
cannot retrieve the data to the METAR/MET REPORT template. You
need to first retrieve the old report text from other applications.
To send a correction to an earlier METAR, do the following:
1. From the Report menu, select CORR, or click the button.
2. Click the BUILD button.
3. Delete the code in the CODE field.
4. Open the AFTN Monitor or ASCII Log View application, find the
text of the report that you sent earlier and want to correct, and copy
the text.
5. Paste the text in the CODE field in the METAR/MET REPORT
template.
6. Make the corrections in the CODE field and add the COR text.
7. If MET REPORT/SPECIAL is included in the system, repeat the
previous steps in the MET REPORT/SPECIAL view.
8. Click SEND. The system adds the CCA code, and the abbreviated
headers to the report and sends it to the AFTN line as well as to
other workstations in the system.
The correction code for the first correction is CCA. In case you send a
second correction to the same report, the code is CCB, and so on.
A corrected MET REPORT is sent with the corrected METAR. You
cannot send only a corrected MET REPORT. If you need to correct the
MET REPORT information, you have to send a SPECIAL report. See
section Editing and Sending SPECIAL Reports on page 119.
CAUTION
Do not build the report again.
VAISALA______________________________________________________________________ 111
Sending Automated METAR
Reports (Optional)
If the system includes the optional Automated METAR function, you
can define the system to send METAR reports to the AFTN line
automatically without user intervention. The system will fill in the
automatic fields, build, and send the report. TREND cannot be used
with Automated METAR reports.
To select the Automated METAR function, do the following:
1. Open the METAR/MET REPORT application.
2. From the Settings menu, select the Automated METAR option
and remove the selection from the Trend field from observer
option. The No consistency check option is automatically selected
and disabled by the system.
3. Starting from the next scheduled METAR, the METAR/
MET REPORT template will appear on the screen at normal
editing times, and the system will send the report automatically to
the AFTN line. The system also adds the text AUTO automatically
in the code.
Editing Automated METAR Report
In some weather conditions you might want to edit the Automated
METAR report manually. When the system displays the template for
the automated METAR, you can edit the report by doing the following:
1. Remove the Automated METAR selection from the Settings
menu. If the system includes the Automated SPECI function and it
is selected, remove also the Automated SPECI option.
2. Edit the data fields as with a normal METAR.
3. Build the report by clicking BUILD.
4. Delete the word AUTO from the CODE field, because the report
is no longer an Automated METAR.
5. Send the report by clicking SEND.
6. To continue using the Automated METAR function, make the
Automated METAR selections. Do the same with SPECI, if
needed.
Users Guide ______________________________________________________________________
112 __________________________________________________________________M010027EN-F
Instead of editing data fields, you can also make the corrections directly
in the CODE field. If you edit the CODE field, do not click BUILD
after editing, or the manual changes will be lost. The system will display
an error message informing you of this. See Figure 29 on page 109.
changes made in the CODE field will be lost.
Editing and Sending Normal SPECI
Reports
The METAR/MET REPORT template is also used for sending SPECI
reports, if this function is configured in the system. The report type in
the report identification data fields changes to SPECI. The system
shows the reason for the report on the status bar on the bottom of the
template.
The time in the UTC and CODE fields is the time when the system
updates the template data. Both these fields have the same time, unlike
in METAR. The UTC time is not updated during editing of SPECI.
SPECI reports are sent in the following situations:
- If configured, the SPECI template appears on the screen
automatically when the predefined weather changes occur. 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
Manual Observations window in the Actuals application.
- You can trigger a SPECI by clicking the SPECI button
whenever the weather changes require this.
If the METAR editing time starts when you are editing a SPECI report,
one of the following takes place, depending on the configuration of the
system:
- The SPECI report becomes a METAR report and the SPECI cannot
be sent.
- You can send SPECI report first, then edit and send the METAR
report. If you have not sent the SPECI before the METAR editing
time ends, the system will ignore the SPECI and send the METAR
as retarded.
VAISALA______________________________________________________________________ 113
The SPECI can be triggered by the system because of deterioration or
improvement in weather conditions. The system constantly monitors
the measured values and compares them to the previous sent METAR/
MET REPORT report. The procedure of sending SPECI reports differs
slightly depending on whether the weather conditions have improved
and deteriorated.
Improvement SPECI reports triggered by the system are placed in a
waiting buffer for a preconfigured time period, usually 10 minutes (as
specified by ICAO), before the system allows the user to send the
report.
The following SPECI reports are sent straight after the user has built
them and clicked the Send button:
- SPECI reports triggered by the user. For more information, see
section Triggering and Sending SPECI Reports on page 115.
- Deterioration SPECI reports.
- No direction SPECI reports (the phenomenon is not clearly a
deterioration or an improvement).
In these cases, if there is an improvement SPECI pending, the
improvement SPECI report is canceled.
Table 44 on page 113 lists the phenomena that trigger improvement and
deterioration SPECI reports by the system. The amount of increase/
decrease depends on the configuration of the system. The limits can be
checked and defined in the SPECI Limit Manager window. See
section Changing SPECI Triggering Limits on page 118.
Table 44 Improvement and Deterioration SPECI Reports
Improvement Deterioration
Present weather code disappears Present weather code appears
Intensity of present weather code
decreases
Intensity of present weather code
increases
Wind speed decreases Wind speed increases
Cross wind speed decreases Cross wind speed increases or direction
changes to the opposite direction
VERVIS increases VERVIS decreases
Cloud base increases Cloud base decreases
Cloud amount decreases Cloud amount increases
Visibility increases Visibility decreases
RVR increases RVR decreases
Users Guide ______________________________________________________________________
114 __________________________________________________________________M010027EN-F
A SPECIAL report is always sent with a SPECI report, but you can also
send a SPECIAL report only, see section Editing and Sending
SPECIAL Reports on page 119.
Accepting and Sending Improvement SPECI
Reports
If the reason for a SPECI is improvement of weather conditions, do the
following to accept and send the SPECI report:
1. The METAR/MET REPORT template is displayed by the
system. The reason for the report is displayed on the status bar at
the bottom of the template.
2. Click the ACCEPT button. The SPECI is placed in a waiting
buffer for a preconfigured time period, usually 10 minutes.
3. After the waiting period, the SPECI template is displayed again
with the current values and the original reason with a message
window:
0305-010
Figure 30 Improvement SPECI Message Window
4. Select Yes to build the report. If you select No, the SPECI is
ignored and not sent.
5. Build and send the report by clicking the BUILD and SEND
buttons.
If the weather conditions deteriorate during the pending of the
improvement SPECI, the system triggers a new SPECI template and the
improvement SPECI will not be sent. If the conditions improve during
the editing of another improvement SPECI, both reports will be sent.
VAISALA______________________________________________________________________ 115
Editing and Sending Deterioration SPECI Reports
If the reason for a SPECI is deterioration of weather conditions or it is
a no direction SPECI, do the following to edit and send the SPECI:
1. The METAR/MET REPORT template is displayed by the system
and the reason for the report can be seen on the status bar at the
bottom of the template.
2. Check and edit the values as needed.
buttons.
Triggering and Sending SPECI Reports
You can trigger a SPECI by clicking the SPECI button whenever the
weather changes require this. To trigger and send a SPECI report, do the
following:
1. Click the SPECI button on the toolbar. Click Yes in the
message window that is displayed.
2. Edit the values as needed.
buttons.
Canceling Current SPECI Report
If you need to cancel the SPECI report before sending it, do the
following:
will not be sent and the data it contained, will be lost.
NOTE
If you try triggering a SPECI report when there is a METAR report
pending, the system informs you about this with a message window.
Click OK, and build and send the METAR report first.
NOTE
If the weather conditions deteriorate during the editing of a user-
triggered SPECI, the system does not trigger a new SPECI.
Users Guide ______________________________________________________________________
116 __________________________________________________________________M010027EN-F
Sending Corrected SPECI Reports
After sending a normal SPECI report, you might notice things that need
to be corrected, for example, typographic errors or missing values. In
such cases, you can generate and send a corrected report.
If no other reports have been sent after the report that you want to
correct, the system can retrieve the data of that report automatically to
the template.
To send a corrected SPECI report, do the following:
2. From the Report menu, select CORR, or click the button on
the toolbar.
3. Click Yes in the window that is displayed. The system changes the
report type to SPECI_CORRECTED, displays the data of the
previously sent report in the data fields and the CODE field, and
has added the text COR in the code.
4. Edit the data that needs correcting in the data fields.
5. Click BUILD. Check that the report text in the CODE field is
correct.
6. Click SEND. The system adds the code CCA (or CCB, CCC, CCD
etc. for the next corrected reports) and the abbreviated headers to
the report. It sends the report to the AFTN line and to other
Instead of editing the data fields, you can also make corrections directly
in the CODE field. After editing the CODE field, do not click the
BUILD button after editing, or the manual changes will be lost. If you
click the BUILD button, the system displays an error message as
NOTE
NOTE
The system displays the last sent report, thus, if you have sent a
METAR report after the last SPECI, the last sent METAR is displayed,
not SPECI.
VAISALA______________________________________________________________________ 117
0208-048
Figure 31 Manual Changes Lost Warning Message Window
In the message window, do one of the following:
Sending Automated SPECI Reports
(Optional)
If the system includes the optional Automated SPECI function, you can
define the system to send SPECI reports to the AFTN line automatically
without user intervention. The system will fill in the automatic fields,
build, and send the report.
To select the Automated SPECI function, do the following:
1. Open the METAR/MET REPORT application.
2. From the Settings menu, select the Automated SPECI option and
remove the selection from the Trend field from observer option.
The No consistency check option is automatically selected and
disabled by the system.
3. When the system triggers the next SPECI report, the template will
appear on the screen, and the system will send the report
automatically to the AFTN line.
A SPECIAL report is sent with the automated SPECI.
In some weather conditions you might want to edit the Automated
SPECI report. When the system displays the template for the automated
SPECI, you can edit the report by doing the following
Users Guide ______________________________________________________________________
118 __________________________________________________________________M010027EN-F
1. Remove the Automated SPECI selection from the Settings menu.
Also remove the Automated METAR selection, if selected.
2. Edit the data fields as with a normal SPECI.
3. Build the report by clicking BUILD.
4. Delete the word AUTO from the CODE field, because the report
is no longer an Automated SPECI.
5. Send the report by clicking SEND.
6. To continue using the Automated SPECI function, make the
Automated SPECI selections. Do the same with METAR, if
needed.
Instead of editing data fields, you can also make the corrections directly
in the CODE field. If you edit the CODE field, do not click BUILD
after editing, or the manual changes will be lost. The system will display
an error message informing you of this. See Figure 29 on page 109.
Changing SPECI Triggering Limits
You can change the pre-configured limits for automatic SPECI
triggering in the SPECI Limit Manager window by doing the
following:
1. In the METAR/MET REPORT template, select SPECI Limit
Manager from the Settings menu.
2. In the SPECI Limit Manager window, enter the new limits in the
appropriate fields, or select from the pre-defined values in the lists.
You can also add new pre-defined values by clicking the
appropriate Add button.
3. Click the Apply button to save the changes or OK to save the
changes and close the window.
To use the default values specified by ICAO, click the Reset to ICAO
button and then the Apply button.
If no values have been selected, or the values entered exceed the
permitted value range used in METAR or the system for the parameter,
no SPECI is triggered for the parameter.
VAISALA______________________________________________________________________ 119
Editing and Sending SPECIAL
Reports
If configured, SPECIAL reports are sent locally in the following
situations:
- SPECIAL reports are sent with all SPECI reports automatically.
- SPECIAL reports can be sent whenever there is a specific change
in weather.
- If you want to send a correction to the MET REPORT information,
you have to send a SPECIAL report, because a corrected MET
REPORT cannot be sent without a METAR report.
The template used for SPECIAL reports is the same that is used for
METAR/MET REPORT. The report type text on the identification data
row is SPECIAL.
The time in the UTC and CODE fields is the time when the system
updates the template data. Notice that both of these fields have the same
time, unlike in METAR/MET REPORT. The UTC time is not updated
during the period you edit SPECIAL.
To edit and send a SPECIAL report, do the following:
1. Click the SPECIAL button on the toolbar. Click Yes in the
message window that is displayed.
2. Check and edit the values as needed.
3. Build the report by clicking the BUILD button.
4. If needed, enter the TREND in the CODE field after building the
report.
5. Send the report by clicking the SEND button.
NOTE
If you try triggering a SPECIAL report when there is a METAR or
SPECI report pending, the system informs you about this with a
message window. Click OK, and build and send the METAR report
first.
Users Guide ______________________________________________________________________
120 __________________________________________________________________M010027EN-F
Canceling Current SPECIAL Report
If you need to cancel the SPECIAL report before sending it, do the
following:
will not be sent and the data it contained will be lost.
Viewing Sent Reports
All sent weather reports are typically stored by the MIDAS IV system.
Normally, only the sent version of the report is stored. The reports are
saved for a period of one month or one year, depending on the
configuration.
You can view the sent reports in their final format with the ASCII Log
View application. For more information, see Chapter 16, ASCII Log
View, on page 219.
In the AFTN Monitor application, you can view the report in the format
it was sent to the AFTN line. For more information, see Chapter 12,
AFTN Monitor, on page 173. Below is an example of a sent METAR
report as it appears in the AFTN Monitor.
---------- ---------- ---------- ---------- -----------
MGH008
GG EFHKYZYX EFVAYMYX EFKIYMYX EFJYYMYX
311127 EFHKYMYX
SAFI01 EFHK 311130
METAR EFHK 311130Z 09024KT 0100 R22/0200N +RA SCT026
05/M02Q1013=
---------- ---------- ---------- ---------- ----------
NOTE
If you are editing a SPECIAL report and a SPECI or METAR report is
triggered by the system, the SPECIAL becomes a METAR or a SPECI
report.
NOTE
VAISALA______________________________________________________________________ 121
Depending on the configuration, separate AFTN addresses can be used
for half and full hour reports.
When the report has been successfully sent, it is also delivered to other
workstations within the airport. In the Observer Workstation, the sent
METAR report can be displayed in the Weather View application as a
separate field, depending on the configuration of your Weather View
screens.
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
Weather View application, or to be sent to other external systems.
Changing Font
You can change the font used in the METAR/MET REPORT template
fields. The default font is MS Dialog Light, Regular, 8 pt.
To change the font shown on METAR/MET REPORT template fields,
do the following:
2. From the Settings menu, choose Select font. The Font window
opens.
3. In the Font window, define the font, font style, and size, and click
OK to close the Font window. The new font is shown on the
METAR/MET REPORT template immediately. The selection
remains until it is changed again.
Users Guide ______________________________________________________________________
122 __________________________________________________________________M010027EN-F
Troubleshooting METAR/MET REPORT
Table 45 on page 122 lists some typical problem situations.
Table 45 Troubleshooting METAR/MET REPORT
The METAR/MET REPORT
template does not appear on the
screen at the predefined editing
time.
METAR/MET REPORT
application might have been
closed.
Open the application by clicking
the METAR/MET REPORT
button in the Application
Toolbar.
There are no sensor values in the
template.
The measurement site might
be incorrectly defined in the
METAR/MET REPORT
Manager application.
Check the measurement site
selection in the METAR/MET
REPORT Manager application.
There are slashes (////) in the
automatic fields of the template.
There may be a problem in
Contact system maintenance
personnel.
The field might be defined as
manual in METAR/MET
REPORT Manager.
Check the selection in the
METAR/MET REPORT
Manager.
There are slashes in the manual
fields.
This is a normal situation. No action needed.
There are no values and no slashes
in the template. All fields are empty.
The CDU may be out of order. Contact system maintenance.
When you have built the report,
there are slashes in the CODE
field, replacing manual values that
you have entered in the template
data fields.
Manual values that you
entered are incorrect.
Re-enter the values correctly
and build the report again.
You have built the report but you
cannot send it because the SEND
button is not active.
There might be incorrect
values in the data fields
Build the report again and
correct any incorrect values
indicated by the validation error
messages.
The present weather code is shown
in the METAR format in the
MET REPORT/SPECIAL view.
The present weather code will
be converted into MET
REPORT format when the
report is built.
Click the BUILD button.
The values entered in the Manual
Observations window in the
Actuals application are not
displayed in the METAR/
MET REPORT template.
The values have not been
updated after making
changes.
Click the Update button every
time you change the values in
the Manual Observations
window.
defined properly in the
METAR/MET REPORT
See Chapter 21, METAR/MET
REPORT Manager, on page
307.
The Manual Observations
window has not been activated
when used for the first time.
See section Using Manual
Observations Window on page
257.
Chapter 6 _____________________________________________________________________ TAF
VAISALA______________________________________________________________________ 123
CHAPTER 6
TAF
This chapter contains instructions for creating and sending TAF reports.
Introduction to TAF
The MIDAS IV AWOS system includes the optional TAF application
for creating and sending TAF reports (Terminal Aerodrome Forecasts)
to the system, and to the AFTN line, if configured.
Normal TAF reports are scheduled by the MIDAS IV system. The TAF
window appears for editing and sending the report at the predefined
intervals. Corrected and amended TAF reports can be sent whenever
necessary.
The TAF application does not include automatic weather data, except
the report identification data. The report content has to be entered
manually, using the abbreviated plain language specified by ICAO. The
TAF code form can be found in WMO Publication No. 306, Manual on
Codes, Volume I.1, Part A - Alphanumeric Codes.
TAF User Interface
The TAF user interface consists the TAF window. The following
sections describe the elements of the window briefly.
For instructions on using the application, see section Operating TAF on
page 127.
Users Guide ______________________________________________________________________
124 __________________________________________________________________M010027EN-F
TAF Window
An example of the TAF window is presented in Figure 32 on page 124.
0411-097
Figure 32 TAF Window
The TAF window elements are described in Table 46 on page 125.
Chapter 6 _____________________________________________________________________ TAF
VAISALA______________________________________________________________________ 125
Table 46 TAF Window Elements
Element Description
TAF list box The TAF report type: Normal, RRA (retarded), CCA
(corrected), or AAA (amended). The default type is Normal.
If the type is other than normal, the corresponding code will
be added in the abbreviated header of the AFTN message.
FC/FT option
buttons
Select the AFTN abbreviated header data designator that
indicates the length of the report validity period. The length
is configured in accordance with the local practices. FC is a
report with a shorter validity period (typically less than 12
hours), FT has a longer validity period (typically 12 to 24
hours).
Date The date of origin of report, filled in automatically by the
system.
Time The time of origin of report, filled in automatically by the
system. 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.
Period The day and period of validity of the TAF report. The format
is DDHHHH, where DD is the day of the month, the first HH
is the starting hour, and second HH is the ending hour of
the validity period, using 24-hour clock. For example,
180921 means the period on the 18th day of the month,
from 9 AM to 9 PM.
Location
indicator
ICAO location indicator.
Code Enter the TAF report text manually using the abbreviated
plain language specified by ICAO. The minimum length of
the report is 12 characters.
Coded
Message
Shows the complete coded TAF message starting with the
identification data that the system has formed based on the
data in other fields.
Previous Displays the previous TAF report for editing.
New Displays a new TAF template.
Send Sends the report to the system and to the AFTN line, if
configured.
Users Guide ______________________________________________________________________
126 __________________________________________________________________M010027EN-F
Menu Bar
The TAF window functions can be selected from the menu bar. The
typical menus and menu commands are presented in the following
tables.
Table 47 TAF: File Menu
Command Description
New Displays a new TAF template
Previous Displays the previous TAF report for editing
configured
Table 48 TAF: Edit Menu
Command Description
Table 49 TAF: Help Menu
Command Description
About TAF Displays software version and copyright information
Chapter 6 _____________________________________________________________________ TAF
VAISALA______________________________________________________________________ 127
Operating TAF
There are the 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.
- Canceled reports are a form of amended reports that can be
manually created and sent when needed.
- NIL reports can be manually created and sent when the forecast is
missing, that is, when there is no reliable TAF report available.
Starting and Exiting TAF
MIDAS IV starts the TAF application automatically. The application
must be open at all times, so that the automatic report window appears
on the screen at the specified time intervals. When you do not need to
view the application window, you can minimize it.
CAUTION
Do not close TAF unless you have a special reason, such as system
maintenance. If it is necessary to close TAF for a special reason, you
can do it by pressing ALT+F4. To open TAF again, click the TAF
button on the Application Toolbar.
Users Guide ______________________________________________________________________
128 __________________________________________________________________M010027EN-F
Sending Normal and Delayed 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
displayed with the automatic data ready in the report identification data
fields.
Typically, you have 20 minutes to edit and send the FC forecast. For the
FT forecast, the typical editing period is 30 minutes. The exact editing
period depends on the system configuration.
To send a normal TAF report when the TAF window is displayed on the
screen by the system, do the following:
1. The TAF window is displayed on the screen.
2. Click the New button. The system generates the report
identification data automatically. If you want to use the previously
sent TAF as the basis for the editing, click Previous.
3. If you want to change the report validity period, edit the Period
field manually. The format is DDHHHH, where DD is the day of
the month (for example, 18), the first HH is the starting hour (for
example, 09), and the second HH is the ending hour (for example,
21).
4. In the Code field, enter the TAF forecast using the abbreviated
plain language specified by ICAO. You can use the editing
functions on the Edit menu. The minimum text length 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.
5. Click the Send button to send the report to the system. If
configured, the system adds AFTN line headers to the report and
sends the TAF report to the AFTN line.
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).
Chapter 6 _____________________________________________________________________ TAF
VAISALA______________________________________________________________________ 129
Sending Corrected and Amended
TAF Reports
In addition to the regular reports scheduled by the system, additional
TAF reports can be sent whenever necessary. The type of the additional
reports is typically corrected or amended:
- Corrected reports are for situations when you notice a typographic
error in the report that has been sent.
- Amended reports are for situations 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 send a corrected or amended TAF report, do the following:
1. If the template is not already open, click the TAF button in the
Application Toolbar. The TAF window opens.
2. In the TAF window, select the FC or FT radio button depending
on the validity period of the report that you want to correct or
amend.
3. If you want to use the previously sent TAF as the basis for the
editing, click Previous. The system shows the data of the previous
report of the type you specified. However, it updates the UTC time
field to show the current time.
4. If you want to start from scratch, click New. The system clears the
Code field and generates the automatic identification data for the
report.
5. Select the report type from the list box: CCA for the first corrected
report or AAA for the first amended report.
6. If you want to change the validity period, edit the Period field
manually. The format is DDHHHH, where DD is the day of the
month (for example, 18), the first HH is the starting hour (for
example, 12), and the second HH is the ending hour (for example,
21).
7. Edit the Code field as necessary. You can use the editing functions
included in the Edit menu.
8. Click Send to send the report to the system. If configured, the
system adds the AFTN line headers automatically in the beginning
of the report and sends the TAF report to the AFTN line.
Users Guide ______________________________________________________________________
130 __________________________________________________________________M010027EN-F
For corrected reports, the system adds the CCA code to the AFTN
abbreviated headers. In case you send a second correction to the same
report, the code is CCB; for a third correction to the same report, it is
CCC, and so on. For amended reports, the corresponding codes are
AAA, AAB, and AAC. For amended reports, the AMD code is added
in the report after the report name.
Canceling Report
Another type of amended TAF reports is canceled TAF. You can cancel
a TAF report by doing the following:
1. Select the FC or FT option button, depending on the report type
you want to cancel.
2. Click the New button.
3. From the TAF list, select AAA for amended report (or AAB, AAC,
etc. if this is not the first amendment to the report).
4. If needed, edit the validity period of the current TAF report in the
Period field.
5. Type the validity time of the TAF to be canceled and the text CNL
in the Code field, for example, 160624 CNL.
6. Click Send.
For canceled reports, the system adds the AMD code after the report
name. It also adds the AAA code in the AFTN abbreviated headers. If
the canceled TAF is a second amended version of the same report, the
code is AAB; for a third amended report it is AAC, and so on.
Sending NIL TAF Reports
A NIL TAF report can also be sent, for example, when there is no
reliable TAF report available.
To send a NIL TAF report, do the following:
1. When the TAF template appears automatically, and there is no
reliable TAF report available, write the text NIL in the Code field.
2. Click the Send button.
Chapter 6 _____________________________________________________________________ TAF
VAISALA______________________________________________________________________ 131
Viewing Sent TAF Reports
Sent reports are typically stored in the ASCII Log View application. For
more information, see Chapter 16, ASCII Log View, on page 219.
You can also view the report in its final format in the AFTN Monitor
application. For more information, see Chapter 12, AFTN Monitor, on
page 173.
Troubleshooting TAF
Table 50 on page 131 lists some problem situations that might occur
when you are using TAF and some typical solutions to them.
Table 50 Troubleshooting TAF
The TAF window is not displayed at
the editing time.
The TAF application might have
been closed by mistake.
Open the TAF application by
clicking the TAF button in the
Application Toolbar.
There are no report identification
data in the data fields.
There is a system problem. Contact maintenance.
You cannot enter the report in the
Code field. The field background is
gray.
The basis for the report has not
been selected.
Click New or Previous to be
able to enter text.
You have written the report text and
want to send it, but the Send button
is not active.
The entered report or period is
shorter than the required
minimum length (12 characters
for the report, 6 for the period).
Enter a report that is at least
12 characters long and check
the entered period.
Users Guide ______________________________________________________________________
132 __________________________________________________________________M010027EN-F
Chapter 7 _________________________________________________________________ SIGMET
VAISALA______________________________________________________________________ 133
CHAPTER 7
SIGMET
This chapter contains instructions for creating and sending SIGMET
reports.
Introduction to SIGMET
The MIDAS IV AWOS system includes the optional SIGMET
application for creating and sending SIGMET reports to the system, and
to the AFTN line, if configured.
SIGMET reports are not scheduled by the system. They can be sent
whenever there is an occurrence of significant weather phenomena (as
specified by ICAO in Annex 3, Chapter 7) that may affect the safety of
aircraft operations.
The SIGMET application does not include automatic weather data,
other than report identification. The report content has to be entered
SIGMET code format can be found in WMO Publication No. 306,
Manual on Codes, Volume I.1, Part A - Alphanumeric Codes.
Users Guide ______________________________________________________________________
134 __________________________________________________________________M010027EN-F
SIGMET User Interface
The SIGMET user interface consists of the SIGMET window. The
following sections describe the elements of the window briefly.
For instructions on using the application, see section Operating
SIGMET on page 136.
SIGMET Window
An example of the SIGMET window is presented in Figure 33 on page
134.
0411-098
Figure 33 SIGMET Window
Chapter 7 _________________________________________________________________ SIGMET
VAISALA______________________________________________________________________ 135
The window elements are described in Table 51 on page 135.
Table 51 SIGMET Window Elements
Element Description
SIGMET list The report type: Normal or corrected (CCA, CCB, CCC
etc). The default type is Normal. If the type is corrected, the
corresponding code will be added in the abbreviated
header of the AFTN message.
Date Date of origin of report, filled in automatically by the system.
Time Time of origin of the report, filled in automatically by the
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 minutes (for example, 00).
Valid end The end date and time of the validity period of the report, a
manual field that 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
minutes (for example, 00).
Office (MWO) The location indicator of the MWO (Meteorological Watch
Office) originating the message, automatically filled in by
the system.
FIR/CTA The name of the FIR (Flight Information Region), for which
the report is issued, automatically filled in by the system,
can be edited.
Code Enter the SIGMET report text manually using the
abbreviated plain language specified by ICAO.
Coded
Message
Shows the complete coded SIGMET message starting with
the identification data that the system has formed based on
the data in other fields. The identification data includes the
report sequence number within 24 hours.
Previous Displays the previous SIGMET report for editing.
New Displays a new SIGMET template.
configured.
Users Guide ______________________________________________________________________
136 __________________________________________________________________M010027EN-F
Menu Bar
The SIGMET window functions can be selected from the menu bar.
The typical menus and menu commands are presented in the following
tables.
Operating SIGMET
Starting and Exiting SIGMET
To start SIGMET, click the SIGMET button on the Application
Toolbar.
To exit SIGMET, select Exit from the File menu.
Table 52 SIGMET: File Menu
Command Description
New Displays a new SIGMET template
Previous Displays the previous SIGMET report for editing
configured
Exit Exits the SIGMET application
Table 53 SIGMET: Edit Menu
Command Description
Table 54 SIGMET: Help Menu
Command Description
About
SIGMET
Displays software version and copyright information
Chapter 7 _________________________________________________________________ SIGMET
VAISALA______________________________________________________________________ 137
Sending Normal SIGMET Reports
You can create SIGMET reports whenever there is an occurrence of
significant weather phenomena. There are two types of SIGMET
reports: normal and corrected.
To send a normal SIGMET report, do the following:
1. Click the SIGMET button in the Application Toolbar. The
SIGMET window opens.
2. In the SIGMET window, click New. The system generates the
sent SIGMET as the basis for the editing, click Previous.
3. In the Valid begin and Valid end fields, enter the validity period
for the report. 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).
4. In the Code field, enter the SIGMET report text using the
abbreviated plain language specified by ICAO. You can use the
editing functions included on the Edit menu.
5. When you have finished editing, click Send to send the report to
the system. If configured, the system adds AFTN line headers to
the report and sends it to the AFTN line.
Sending Corrected SIGMET Reports
You can send a correction to a previously sent SIGMET report
whenever you notice a typographic error, for example.
To send a corrected SIGMET report, do the following:
1. Click the SIGMET button in the Application Toolbar. The
SIGMET window opens.
2. In the SIGMET window, click Previous. The system displays the
data from the previous report that you have sent.
3. Select the report type from the SIGMET list box, for example,
CCA for first corrected report.
4. Edit the report text in the Code field as necessary. You can use the
Users Guide ______________________________________________________________________
138 __________________________________________________________________M010027EN-F
5. Check the validity period to make sure it is correct for your
corrected report.
configured, the system adds the code CCA to the AFTN
abbreviated headers and sends the SIGMET report to the AFTN
line.
In case you send a second correction to the same report, the code will
be CCB and for a third correction to the same report, CCC, and so on.
Canceling Report
To cancel a SIGMET report, do the following:
2. Edit the validity period of the current SIGMET report in the Valid
begin and Valid end fields.
3. Type the text in the Code field as specified by ICAO and national
regulations and practices. For example, CNL SIGMET 2 101200/
101600, where the times indicated are the validity period of the
canceled report.
4. Click Send.
Viewing Sent SIGMET Reports
page 173.
Chapter 7 _________________________________________________________________ SIGMET
VAISALA______________________________________________________________________ 139
Troubleshooting SIGMET
when you are using SIGMET and some typical solutions to them.
Table 55 Troubleshooting SIGMET
There is no report identification
There is a serious system
problem.
gray.
been selected.
able to enter text.
You have written the report text
and want to send it, but the Send
The validity period has to be
entered before the report can be
sent.
Enter the validity period in the
Valid begin and Valid end
fields.
Users Guide ______________________________________________________________________
140 __________________________________________________________________M010027EN-F
Chapter 8 __________________________________________________________________ GAMET
VAISALA______________________________________________________________________ 141
CHAPTER 8
GAMET
This chapter contains instructions for creating and sending GAMET
reports.
Introduction to GAMET
The MIDAS IV AWOS system includes the optional GAMET
application for creating and sending GAMET reports to the system, and
to the AFTN line, if configured. GAMET reports are area forecasts for
low-level flights.
Normal GAMET reports are scheduled by the MIDAS IV system and
the GAMET window appears for editing and sending the report at the
predefined intervals. Retarded (delayed), corrected, and amended
GAMET reports can be sent whenever necessary.
The GAMET application does not include automatic weather data,
other than report identification data. The report content has to be entered
GAMET code form is contained in WMO Publication No. 306, Manual
on Codes, Volume I.1, Part A - Alphanumeric Codes.
Users Guide ______________________________________________________________________
142 __________________________________________________________________M010027EN-F
GAMET User Interface
The GAMET user interface consists of the menus and the GAMET
window. The following sections describe these elements briefly.
GAMET on page 144.
GAMET Window
An example of the GAMET window is presented in Figure 34 on page
142.
0411-099
Figure 34 GAMET Window
Chapter 8 __________________________________________________________________ GAMET
VAISALA______________________________________________________________________ 143
The elements of the GAMET window are described in Table 56 on
page 143.
Table 56 GAMET Window Elements
Element Description
GAMET list
box
The report type: Normal, RRA (retarded), CCA (corrected),
or AAA (amended). The default type is Normal. If the type is
other than Normal, the corresponding code will be added in
the abbreviated header of the AFTN message.
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 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 minutes (for example, 00).
the system.
the report is issued, automatically filled in by the system.
Sub-area Sub area of the FIR.
SECN1 Enter the section 1 part of the GAMET report text manually
using the abbreviated plain language specified by ICAO.
SECN2 Enter the section 2 part of the GAMET report text manually
using the abbreviated plain language specified by ICAO.
Coded
Message
Shows the complete coded GAMET message starting with
the data in other fields.
Previous Displays the previous GAMET report for editing.
New Displays a new GAMET template.
configured.
Users Guide ______________________________________________________________________
144 __________________________________________________________________M010027EN-F
Menu Bar
The GAMET window functions can be selected from the menu bar.
tables.
Operating GAMET
There are four types of GAMET reports:
- Normal reports are scheduled by the system, and they appear at
predefined intervals, typically every 6 hours.
- Retarded reports: Normal reports automatically turn into Retarded
(delayed) reports after the specified editing time has passed.
- 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.
Table 57 GAMET: File Menu
Command Description
New Displays a new GAMET template
Previous Displays the previous GAMET report for editing
configured
Table 58 GAMET: Edit Menu
Command Description
Table 59 GAMET: Help Menu
Command Description
About GAMET Displays software version and copyright information
Chapter 8 __________________________________________________________________ GAMET
VAISALA______________________________________________________________________ 145
Starting and Exiting GAMET
MIDAS IV starts the GAMET application automatically. The
application must be open at all times, so that the automatic report
window appears on the screen at the specified time intervals. When you
do not need to view the application window, you can minimize it.
Sending Normal and Delayed
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 normal GAMET report, do the following:
1. The GAMET window is displayed on the screen.
2. Click the New button. The system generates the report
sent GAMET as the basis for the editing, click Previous.
3. 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).
4. 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. The keywords "SECN1" and "SECN2" are added
automatically by the system to the final report. You can use the
editing functions on the Edit menu. The minimum text length for
each section is 12 characters. The system checks the length of the
CAUTION
Do not close GAMET unless you have a special reason, such as system
maintenance. If it is necessary to close GAMET for a special reason,
you can do it by pressing ALT+F4. To open GAMET again, click the
GAMET button on the Application Toolbar.
Users Guide ______________________________________________________________________
146 __________________________________________________________________M010027EN-F
report automatically. If the report is shorter than the minimum
length, the report cannot be sent.
5. Edit the sub-area of the FIR in the Sub-area field, if needed.
configured, the system adds AFTN line headers to the report and
sends the GAMET report to the AFTN line.
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).
Sending Corrected and Amended
GAMET Reports
In addition to the regular reports scheduled by the system, corrected and
amended GAMET reports can be sent whenever necessary as follows:
- Corrected reports are for situations when you notice typographic
errors in the sent report.
- Amended reports are for situations when you notice that the sent
report does not correspond with weather developments.
To send a corrected or amended GAMET report, do the following:
1. Click the GAMET button in the Application Toolbar. The
GAMET window opens.
2. If you want to use the previously sent GAMET as the basis for the
editing, click Previous. The system shows the data of the previous
report of the type you specified. However, it updates the UTC time
field to show the current time.
3. If you want to start from scratch, click New. The system clears the
text field and generates the automatic identification data for the
report.
4. Select the report type from the GAMET list box: CCA for first
corrected report or AAA for the first amended report.
5. If you want to change the validity period, edit the validity fields
manually.
Chapter 8 __________________________________________________________________ GAMET
VAISALA______________________________________________________________________ 147
6. Edit the report text fields SECN 1 and SECN 2 as necessary. You
can use the editing functions included on the Edit menu.
the system. If configured, the system adds the AFTN line headers
automatically in the beginning of the report and sends the GAMET
report to the AFTN line.
For corrected reports, the system adds the CCA code to the AFTN
abbreviated headers. In case you send a second correction to the same
report, the code is CCB; for a third correction to the same report, it is
CCC, and so on. For amended reports, the corresponding codes are
AAA, AAB, and AAC.
Viewing Sent GAMET Reports
page 173.
Troubleshooting GAMET
when you are using GAMET and some typical solutions to them.
Table 60 Troubleshooting GAMET
The GAMET window is not
displayed at the editing time.
The GAMET application might
have been closed by mistake.
Open the GAMET application by
clicking the GAMET button in the
problem.
report text fields. The field
background is gray.
been selected.
able to enter text.
The minimum length of the
report text is 12 characters for
each section.
Enter a report that is at least 12
characters long.
Users Guide ______________________________________________________________________
148 __________________________________________________________________M010027EN-F
Chapter 9 _________________________________________________________________ AIRMET
VAISALA______________________________________________________________________ 149
CHAPTER 9
AIRMET
This chapter contains instructions for creating and sending AIRMET
reports.
Introduction to AIRMET
The MIDAS IV AWOS system includes the optional AIRMET
application for creating and sending AIRMET reports to the system, and
if configured, to the AFTN line. 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.
The AIRMET application does not include automatic weather data,
except the report identification. The report content has to be entered
AIRMET code form can be found in WMO Publication No. 306,
Manual on Codes, Volume I.1, Part A - Alphanumeric Codes.
AIRMET User Interface
The AIRMET user interface consists of the menus and the AIRMET
window. The following sections describe these elements briefly.
AIRMET on page 153.
Users Guide ______________________________________________________________________
150 __________________________________________________________________M010027EN-F
AIRMET Window
The AIRMET window is presented in Figure 35 on page 150.
0411-100
Figure 35 AIRMET Window
Chapter 9 _________________________________________________________________ AIRMET
VAISALA______________________________________________________________________ 151
The elements of the AIRMET window are described in Table 61 on
page 151.
Table 61 AIRMET Window Elements
Element Description
AIRMET list
box
Type of AIRMET report, Normal or corrected (CCA, CCB,
CCC, etc). The default type is Normal. If the type is
corrected, the corresponding code will be added in the
abbreviated header of the AFTN message.
Time Time of origin of report, filled in automatically by the system.
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 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 minutes (for example, 00).
the system.
the report is issued, automatically filled in by the system.
Code Enter the AIRMET report text manually using the
abbreviated plain language specified by ICAO.
Coded
Message
Shows the complete coded AIRMET message starting with
the data in other fields. The identification data includes the
report sequence number within 24 hours.
Previous Displays the previous AIRMET report for editing.
New Displays a new AIRMET template.
configured.
Users Guide ______________________________________________________________________
152 __________________________________________________________________M010027EN-F
Menu Bar
The AIRMET window functions can be selected from the menu bar.
tables.
Table 62 AIRMET: File Menu
Command Description
New Displays a new AIRMET template
Previous Displays the previous AIRMET report for editing
configured
Exit Exits the AIRMET application
Table 63 AIRMET: Edit Menu
Command Description
Undo Cancels the last action
Table 64 AIRMET: Help Menu
Command Description
About AIRMET Displays software version and copyright information
Chapter 9 _________________________________________________________________ AIRMET
VAISALA______________________________________________________________________ 153
Operating AIRMET
Starting and Exiting AIRMET
To start AIRMET, click the AIRMET button on the Application
Toolbar.
To exit AIRMET, select Exit from the File menu.
Sending Normal AIRMET Reports
You can create AIRMET reports whenever there is an occurrence of
significant weather phenomena. There are two types of AIRMET
reports: normal and corrected.
To send a normal AIRMET report, do the following:
1. Click the AIRMET button in the Application Toolbar. The
AIRMET window opens.
2. In the AIRMET window, click New. The system generates the
sent AIRMET as the basis for the editing, click Previous.
of the report. The format is DDHHmm, where DD is the day of the
4. In the Code field, enter the AIRMET report text using the
abbreviated plain language specified by ICAO. You can use the
Users Guide ______________________________________________________________________
154 __________________________________________________________________M010027EN-F
Sending Corrected AIRMET Reports
You can send a correction to a previously sent AIRMET report
whenever you notice a typographic error.
To send a corrected AIRMET report, do the following:
1. Click the AIRMET button in the Application Toolbar. The
AIRMET window opens.
2. In the AIRMET window, click Previous. The system displays all
data for the previous report that you have sent. The report sequence
number in the Coded Message field is updated automatically.
3. Select the report type from the AIRMET list box, for example,
CCA for the first corrected report.
4. Edit the report in the Code field as necessary. You can use the
5. Check the validity period to make sure it is correct for the corrected
report.
6. When you have finished editing, click Send. If configured, the
system adds the code CCA to the AFTN abbreviated headers and
sends the AIRMET report to the AFTN line.
In case you send a second correction to the same report, the code would
be CCB and for a third correction to the same report, CCC.
Chapter 9 _________________________________________________________________ AIRMET
VAISALA______________________________________________________________________ 155
Canceling Report
To cancel an AIRMET report, do the following:
2. Edit the validity period of the current AIRMET report in the Valid
begin and Valid end fields.
regulations and practices. For example, CNL AIRMET 2 101200/
101600, where the times indicated are the validity period of the
canceled report.
4. Click Send.
Viewing Sent AIRMET Reports
page 173.
Troubleshooting AIRMET
when you are using AIRMET and some typical solutions to them.
Table 65 Troubleshooting AIRMET
problem.
gray.
been selected.
able to enter text.
is not active.
sent.
validity period fields.
Users Guide ______________________________________________________________________
156 __________________________________________________________________M010027EN-F
Chapter 10 ______________________________________________________________ AD WRNG
VAISALA______________________________________________________________________ 157
CHAPTER 10
AD WRNG
This chapter contains instructions for creating and sending Aerodrome
Warning reports using the AD WRNG template.
Introduction to AD WRNG Template
The MIDAS IV AWOS system includes the optional AD WRNG
template for creating and sending Aerodrome Warning reports to the
system, and if configured, to 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. The report content has to be entered manually,
using the abbreviated plain language specified by ICAO. The code
format can be found in WMO Publication No. 306, Manual on Codes,
Volume I.1, Part A - Alphanumeric Codes.
Users Guide ______________________________________________________________________
158 __________________________________________________________________M010027EN-F
AD WRNG Template User Interface
The user interface consists of the AD WRNG window. The following
For instructions on using the application, see section Operating AD
WRNG Template on page 161.
AD WRNG Window
An example of the AD WRNG window is presented in Figure 36 on
page 158.
0411-101
Figure 36 AD WRNG Window
Chapter 10 ______________________________________________________________ AD WRNG
VAISALA______________________________________________________________________ 159
Table 66 AD WRNG Window Elements
Element Description
AD WRNG list The report type: Normal or corrected (CCA, CCB, CCC
Date Date of origin of report, filled in automatically by the
system.
Time Time of origin of report, filled in automatically by the
Location
indicator
ICAO location indicator of the aerodrome.
Valid end The ending date and time of the validity period of the
Code Enter the Aerodrome Warning report text manually using
the abbreviated plain language specified by ICAO.
Coded
Message
Shows the complete coded Aerodrome Warning message
starting with the identification data that the system has
formed based on the data in other fields. The identification
data includes the report sequence number within 24 hours.
Previous Displays the previous Aerodrome Warning report for
editing.
New Displays a new AD WRNG template.
Send Sends the report to the system and, if configured, to the
AFTN line.
Users Guide ______________________________________________________________________
160 __________________________________________________________________M010027EN-F
Menu Bar
The AD WRNG window functions can be selected from the menu bar.
tables.
Table 67 AD WRNG: File Menu
Command Description
New Displays a new AD WRNG template
Previous Displays the previous Aerodrome Warning report for
editing
AFTN line
Exit Exits the AD WRNG application
Table 68 AD WRNG: Edit Menu
Command Description
Table 69 AD WRNG: Help Menu
Command Description
About AD
WRNG
Chapter 10 ______________________________________________________________ AD WRNG
VAISALA______________________________________________________________________ 161
Operating AD WRNG Template
Starting and Exiting AD WRNG
Template
To start the AD WRNG template, click the AD WRNG button on
the MIDAS IV Application Toolbar.
To exit AD WRNG, select Exit from the File menu.
Sending Normal Aerodrome
Warning Reports
You can create Aerodrome Warning reports whenever there is an
occurrence of significant weather phenomena. There are two types of
Aerodrome Warning reports: normal and corrected.
To send a normal Aerodrome Warning report, do the following:
1. Click the AD WRNG button in the Application Toolbar. The
AD WRNG window opens.
2. In the AD WRNG window, click the New button. The system
generates the identification data automatically. If you want to use
the previously sent Aerodrome Warning as the basis for the editing,
click Previous.
4. In the Code field, enter the Aerodrome Warning report text using
the abbreviated plain language specified by ICAO. You can use the
Users Guide ______________________________________________________________________
162 __________________________________________________________________M010027EN-F
Sending Corrected Aerodrome
Warning Reports
You can send a correction to a previously sent Aerodrome Warning
report whenever you notice a typographic error, for example.
To send a corrected Aerodrome Warning report, do the following:
1. If the template is not open already, click the AD WRNG
button in the Application Toolbar. The AD WRNG window
opens.
2. Click the Previous button. The system displays all data from the
previous report that you have sent.
3. Select the report type from the AD WRNG list, for example, CCA
for the first corrected report.
corrected report.
5. Edit the report as necessary. You can use the editing functions
included on the Edit menu.
6. Click the Send button to send the report. If configured, the system
adds the code CCA to the AFTN abbreviated headers and sends the
Aerodrome Warning report to the AFTN line.
Canceling Report
To cancel an Aerodrome Warning report in the AD WRNG window, do
the following:
2. Edit the validity period of the current report in the Valid begin and
Valid end fields.
regulations and practices. For example, CNL AD WRNG 2
101200/101600, where the times indicated are the validity period
of the canceled report.
4. Click Send.
Chapter 10 ______________________________________________________________ AD WRNG
VAISALA______________________________________________________________________ 163
Viewing Sent Aerodrome Warning
Reports
page 173.
Troubleshooting AD WRNG Template
when you are using AD WRNG Template and some typical solutions to
them.
Table 70 Troubleshooting AD WRNG Template
Report identification data that is
normally filled in automatically in
the data fields is missing.
problem.
gray.
been selected.
able to enter text.
sent.
fields.
Users Guide ______________________________________________________________________
164 __________________________________________________________________M010027EN-F
Chapter 11 ______________________________________________________________ WS WRNG
VAISALA______________________________________________________________________ 165
CHAPTER 11
WS WRNG
This chapter contains instructions for creating and sending Windshear
Warning reports using the WS WRNG template.
Introduction to WS WRNG Template
The MIDAS IV AWOS system includes the optional WS WRNG
application for creating and sending Windshear Warning reports to the
system, and if configured, to 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
wind shear 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. The report content has to be entered manually,
using the abbreviated plain language specified by ICAO. The code
format can be found in WMO Publication No. 306, Manual on Codes,
Volume I.1, Part A - Alphanumeric Codes.
Users Guide ______________________________________________________________________
166 __________________________________________________________________M010027EN-F
WS WRNG User Interface
The user interface consists of the WS WRNG window. The following
For instructions on using the application, see section Operating WS
WRNG Template on page 169.
WS WRNG Window
An example of the WS WRNG window is presented in Figure 37 on
page 166.
0411-102
Figure 37 WS WRNG Template Window
Chapter 11 ______________________________________________________________ WS WRNG
VAISALA______________________________________________________________________ 167
The WS WRNG window elements are described in Table 71 on page
167.
Table 71 WS WRNG Window
Element Description
WS WRNG list The report type: Normal or corrected (CCA, CCB, CCC
Date Date of origin of report, filled in automatically by the
system.
Time Time of origin of report, filled in automatically by the
Location
indicator
ICAO location indicator of the aerodrome.
Valid end The ending date and time of the validity period of the
Code Enter the Windshear Warning report text manually using
the abbreviated plain language specified by ICAO.
Coded
Message
Shows the complete coded Windshear Warning message
starting with the identification data that the system has
formed based on the data in other fields. The identification
data includes the report sequence number within 24 hours.
Previous Displays the previous Windshear Warning report for
editing.
New Displays a new Windshear Warning template.
AFTN line.
Users Guide ______________________________________________________________________
168 __________________________________________________________________M010027EN-F
Menu Bar
The WS WRNG window functions can be selected from the menu bar.
tables.
Table 72 WS WRNG: File Menu
Command Description
New Displays a new WS WRNG template
Previous Displays the previous Windshear Warning report for editing
AFTN line
Exit Exits the WS WRNG application
Table 73 WS WRNG: Edit Menu
Command Description
Table 74 WS WRNG: Help Menu
Command Description
About WS
WRNG
Chapter 11 ______________________________________________________________ WS WRNG
VAISALA______________________________________________________________________ 169
Operating WS WRNG Template
Starting and Exiting WS WRNG
Template
To start the WS WRNG template, click the WS WRNG button on
the Application Toolbar.
To exit the WS WRNG template, select Exit from the File menu.
Sending Normal Windshear
Warning Reports
You can create Windshear Warning reports whenever there is a need for
informing about observed or expected windshear. There are two types
of Windshear Warning reports: normal and corrected.
To send a normal Windshear Warning report, do the following:
1. Click the WS WRNG button in the Application Toolbar. The
WS WRNG window opens.
2. In the WS WRNG window, click the New button. The system
generates the identification data automatically. If you want to use
the previously sent Windshear Warning as the basis for the editing,
click Previous.
mm is the minutes (for example, 00). If you leave the Valid begin
field empty, the coded message will contain the text VALID TL.
4. In the Code field, enter the Windshear Warning report text using
the abbreviated plain language specified by ICAO. You can use the
Users Guide ______________________________________________________________________
170 __________________________________________________________________M010027EN-F
Sending Corrected Windshear
Warning Reports
You can send a correction to a previously sent Windshear Warning
report whenever you notice a typographic error, for example.
To send a corrected Windshear Warning report, do the following:
1. If the template is not already open, click the WS WRNG button
in the Application Toolbar. The WS WRNG window opens.
2. In the WS WRNG window, click Previous. The system displays
all data from the previous report that you have sent.
3. Select the report type from the WS WRNG list box, for example,
CCA for the first corrected report.
corrected report.
5. Edit the report text field as necessary. You can use the editing
functions included on the Edit menu.
6. Click the Send button. If configured, the system adds the code
CCA to the AFTN abbreviated headers and sends the Windshear
Warning report to the AFTN line.
Canceling Report
To cancel a Windshear Warning report in the WS WRNG window, do
the following:
2. Edit the validity period of the current report in the Valid begin and
Valid end fields.
regulations and practices. For example, CNL WS WRNG 2
101200/101600, where the times indicated are the validity period
of the canceled report.
4. Click Send.
Chapter 11 ______________________________________________________________ WS WRNG
VAISALA______________________________________________________________________ 171
Viewing Sent Windshear Warning
Reports
page 173.
Troubleshooting WS WRNG
when you are using WS WRNG template and some typical solutions to
them.
Table 75 Troubleshooting WS WRNG Template
problem.
gray.
been selected.
able to enter text.
is not active.
sent.
fields.
Users Guide ______________________________________________________________________
172 __________________________________________________________________M010027EN-F
Chapter 12 ____________________________________________________________ AFTN Monitor
VAISALA______________________________________________________________________ 173
CHAPTER 12
AFTN MONITOR
This chapter contains instructions for viewing reports that have been
sent to the AFTN line.
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 MIDAS IV
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).
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. For instructions on using the application, see
section Operating AFTN Monitor on page 178.
Users Guide ______________________________________________________________________
174 __________________________________________________________________M010027EN-F
AFTN Monitor Window
The window is displayed when you open AFTN Monitor and select
View - Outbound Messages, or click the Sent Messages button.
0412-090
Figure 38 AFTN Monitor Window
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.
AFTN Manager Window
When you click the button on the AFTN Monitor toolbar, the
AFTN Manager window is displayed.
0412-091
Figure 39 AFTN Manager Window
VAISALA______________________________________________________________________ 175
You can use the AFTN Manager window for changing the AFTN
sequence number (1-999).
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 76 AFTN Monitor: File Menu
Command Description
Print Setup Opens a window for changing the printer and paper settings
Exit Exits the AFTN Monitor application
Table 77 AFTN Monitor: Edit Menu
Command Description
Cut Cuts the selection and copies it to the Clipboard
Copy Copies the selected text to the Clipboard
Paste Pastes the copied text
Table 78 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 MIDAS IV
Users Guide ______________________________________________________________________
176 __________________________________________________________________M010027EN-F
Toolbar
Typical buttons on the AFTN Monitor toolbar are presented in Table 81
on page 176.
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
Table 79 AFTN Monitor: Window Menu
Command Description
Tile
Horizontally
Arranges open windows on top of each other
Tile Vertically Arranges open windows next to each other
Arrange icons Arranges icons of minimized windows
Table 80 AFTN Monitor: Help Menu
Command Description
About AFTN
Monitor
Table 81 AFTN Monitor Toolbar
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. See Chapter 13, AFTN Addressee Manager, on
page 181.
AFTN Manager opens the AFTN Manager window for changing
the AFTN sequence number.
Print prints the current display.
VAISALA______________________________________________________________________ 177
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, the AFTN header and the actual
report code. The AFTN header contains the addresses the report is sent
to and the message indicator. The actual report code 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=
---------- ---------- ---------- ---------- -----------
Users Guide ______________________________________________________________________
178 __________________________________________________________________M010027EN-F
Operating AFTN Monitor
Starting and Exiting AFTN Monitor
To start AFTN Monitor, click the AFTN button on the Application
Toolbar.
To exit AFTN Monitor, select Exit from the File menu.
Viewing Outbound (Sent) Messages
To view the reports that have been sent from the MIDAS IV to the
AFTN line, do the following:
1. Start AFTN Monitor by clicking the AFTN button in the
2. From the View menu, select Outbound Messages.
3. The messages sent to the AFTN line are displayed in the
Outbound Messages window.
4. You can copy the messages to be used in other applications by
selecting Copy from the Edit menu.
5. When you have finished viewing the messages, exit AFTN
Monitor by selecting Exit from the File menu.
Changing AFTN Sequence Number
To change the sequence number in the AFTN Manager window, do the
following:
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 and click Update vai Refresh.
VAISALA______________________________________________________________________ 179
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, you can open the separate
AFTN Addressee Manager application by doing the following:
1. Click the AFTN Addressee Manager button on the AFTN
Monitor toolbar. For instructions on using the application, see
Chapter 13, AFTN Addressee Manager, on page 181.
Troubleshooting AFTN Monitor
when you are using AFTN Monitor and some typical solutions to them.
Table 82 Troubleshooting AFTN Monitor
You cannot find a report
that was sent earlier.
The system can store
1000 data lines, which
means approximately
50 weather reports.
See if the report is in the
ASCII Log View Reports
files. See Chapter 16,
ASCII Log View, on
page 219.
Users Guide ______________________________________________________________________
180 __________________________________________________________________M010027EN-F
Chapter 13 __________________________________________________ AFTN Addressee Manager
VAISALA______________________________________________________________________ 181
CHAPTER 13
AFTN ADDRESSEE MANAGER
This chapter describes how to set the addressee part of the AFTN
message.
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.
AFTN Addressee Manager User Interface
The AFTN Addressee Manager user interface consists of the AFTN
Addressee Manager window. See Figure 40 on page 182.
Users Guide ______________________________________________________________________
182 __________________________________________________________________M010027EN-F
0404-089
Figure 40 AFTN Addressee Manager Window
The elements in the AFTN Addressee Manager window are described
in the following sections.
VAISALA______________________________________________________________________ 183
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. See Table 83 on page 183.
The addressee groups, addressees, and message types that can be sent
using the selected AFTN interface are displayed in the following
frames.
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, see Table
84 on page 183.
Table 83 AFTN Addressee Manager Window: AFTN
Interfaces Frame
Element Description
Interface Shows the available AFTN interfaces to which messages
can be sent.
Table 84 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.
Users Guide ______________________________________________________________________
184 __________________________________________________________________M010027EN-F
Addressee Group Frame
The addressees that belong into an addressee group are displayed in the
Addressee Group frame, see Table 85 on page 184. The addressees, the
address indicators that define the destination of the message, have to be
defined as instructed in ICAO Annex 10, Volume II. For more
information on the format, see section Adding New Addressees on page
186 and ICAO Annex 10, volume 2, section 4.4.3.
Addressee Frame
In the Addressee frame you can select which message types are sent to
the selected addressees. See Table 86 on page 184.
Table 85 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.
Table 86 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.
VAISALA______________________________________________________________________ 185
Buttons
The buttons common to all frames are described in Table 87 on page
185.
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. For a description
of the user interface, see section AFTN Addressee Manager User
Interface on page 181.
Starting and Exiting AFTN
Addressee Manager
To start AFTN Addressee Manager, click the AFTN Addressee
Manager button on the AFTN Monitor toolbar. For more
information on AFTN Monitor, see Chapter 12, AFTN Monitor, on
page 173.
To exit AFTN Addressee Manager and save the changes, click the
Apply button.
To exit AFTN Addressee Manager without saving the changes, click the
Close button.
Table 87 AFTN Addressee Manager Window: Buttons
Element Description
Apply Applies the made selections.
Close Exits the AFTN Addressee Manager application without
saving the changes.
Users Guide ______________________________________________________________________
186 __________________________________________________________________M010027EN-F
Adding New Addressee Groups
To add a new addressee group, do the following:
1. If your system contains several AFTN interfaces, select the correct
interface in the AFTN Interfaces frame.
2. In the AFTN Interface frame, click the Add button. The Add
AFTN addressee group name window is displayed.
3. Type the name of the new addressee group and click OK. The new
group will appear in the list. Do not use special characters in the
names.
4. Click the Apply button, or continue with adding new addressees to
the group in the Addressee Group frame and selecting the
message types to be sent in the Addressee frame. For instructions,
see the following sections.
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.
To add a new addressee, do the following:
1. All addressees belong to an addressee group. In the AFTN
Interface frame, select the addressee group in which you want to
add the addressee. The addressees included in that group will be
displayed in the Addressee Group frame.
2. Click the Add button in the Addressee Group frame. The Add
AFTN addressee name window is displayed.
3. Type the new addressee name. Follow the instructions in ICAO
Annex 10, Volume II, section 4.4.3. 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".
NOTE
If you want the new addressee to make a group of its own, start by
adding a new addressee group first. See section Adding New
Addressee Groups on page 186.
VAISALA______________________________________________________________________ 187
- 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. Click OK in the Add AFTN addressee name window.
5. Click the Apply button, or continue with selecting the message
types in the Addressee frame. For instructions, see the following
section.
Selecting Message Types Sent to
the Addressees
For each addressee, you can define which message types are sent to the
the addressee. Do the following:
1. Select the addressee group and the addressee in the AFTN
Interface and Addressee Group frames. See previous sections for
instructions.
2. In the Addressee frame, select the check boxes next to the message
types. You can also select all message types by clicking the Select
all button. The message types whose check box is selected will be
sent to the selected addressee.
3. Click the Apply button.
Editing Addressee Groups
You can edit the addressee group by doing the following:
1. In the AFTN Interface frame, select the addressee group that you
want to edit.
2. Click the Edit button. In the Edit AFTN addressee group name
window, enter the new name.
3. Click the Apply button.
NOTE
The reports will be sent to the addressee only if the generation of the
report type is included in the system configuration.
Users Guide ______________________________________________________________________
188 __________________________________________________________________M010027EN-F
Troubleshooting AFTN Addressee Manager
when using AFTN Addressee Manager and some typical solutions to
them.
Table 88 Troubleshooting AFTN Addressee Manager
Problem Description Solution
A message type is missing from
the window.
The message type has not been
configured in the system.
Check the system
configuration.
All the available addressees in an
addressee group are not
displayed in the Addressees list.
Another addressee group might
be selected. The Addressees
list contains the addressees of
the group currently selected in
the Addressee groups list.
Select the appropriate
Addressee group from the
Addressee groups list.
Chapter 14 ____________________________________________________________ AFTN Viewer
VAISALA______________________________________________________________________ 189
CHAPTER 14
AFTN VIEWER
This chapter describes the AFTN Viewer application which is used for
viewing messages received from the AFTN line.
Introduction to AFTN Viewer
The AFTN Viewer application displays the messages received from the
AFTN line. The messages can be weather reports, such as METAR and
SPECI, or bulletins of the reports.
Which messages are displayed and their appearance is defined in
system configuration for each delivery. Some features can be adjusted
by the end-user.
AFTN Viewer User Interface
The AFTN Viewer user interface includes the main window, the
Configuration window, the Sound Configuration window, the
Message Status window, and the menus.
Main Window
The main window contains one or two pages of message fields. The
second page can be displayed by clicking on any message on the first
page. Each field contains a separate message. The contents of the pages
Users Guide ______________________________________________________________________
190 __________________________________________________________________M010027EN-F
is configured during system configuration. Possible configurations are,
for example, the following:
- The message fields in the first page show the METAR messages
for all the stations and the second page shows all the TAF messages
for all the stations.
- The message fields in the first page show the all the message types
for the first 12 stations and the second page shows all the message
types for the rest of the stations.
It is also possible to display two separate types of messages in the same
field, for example, METAR and SPECI reports. In that case, the latest
received message type is displayed, and typically the report types are
displayed with different colors.
When no message is displayed or no message is available, the
description of the message is displayed, typically the type and origin of
the message. See Figure 41 on page 190.
0404-084
Figure 41 AFTN Viewer Main Page with Message Descriptions
VAISALA______________________________________________________________________ 191
When the messages arrive, they appear in the message fields. See Figure
42 on page 191. A beeping sound can be configured to sound when a
message arrives.
0404-088
Figure 42 AFTN Viewer: Received Message
A message field can be configured to display a message containing a
certain keyword with a certain color, and a message containing another
keyword with another color, for example, METAR reports in one color
and SPECI reports in another color. The used colors are shared between
all fields.
The messages are removed from the field after a timeout, which is
separately configurable for each field.
Colors
Colors are used for identifying the receiving time and type of the
messages:
- There is a separate color for just received new messages and for
older messages.
- There is also a separate color for the description text, when there is
no message available.
- If the field contains two types of messages, they are typically
displayed with different colors.
The colors are changed in accordance with configurable time-outs.
Users Guide ______________________________________________________________________
192 __________________________________________________________________M010027EN-F
Message Status Window
You can display the Message Status window by clicking the right
mouse button on a message field. The window displays the contents of
the message and the time it was received are displayed.
0404-085
Figure 43 AFTN Viewer: Message Status Window with
Message Details
If there is no message available, the Message Status window contains
the following text.
0404-086
Figure 44 AFTN Viewer: Message Status Window with no
Message
VAISALA______________________________________________________________________ 193
Configuration Window
The message parameters have been configured during system
configuration, but if needed, you can change them in the Configuration
window. The window is displayed when you keep the CTRL button
pressed down and right-click on a message.
0404-082
Figure 45 AFTN Viewer: Configuration Window
Table 89 on page 193 describes the elements of the Configuration
window.
Table 89 AFTN Viewer: Configuration Window Elements
Element Description Comment
Description Defines which text is displayed in the
message field, when no message is
available.
When this field is left empty, the
message field is not displayed at
all.
Bulletin substring Defines a substring which the
message must contain to be displayed.
The substring is considered to be a
part of the AFTN bulletin header.
The parameter is optional and can
be left empty.
Header substring Defines a substring which the
message must contain to be displayed.
The substring is considered to be a
part of the aeronautical report, for
example, METAR or SPECI.
If the bulletin substring is used, the
header substring must be located in
the message after the bulletin
substring. If this substring is found,
the message is displayed using the
New Message Text color.
Users Guide ______________________________________________________________________
194 __________________________________________________________________M010027EN-F
Alt. bulletin substring Defines an alternative substring which
the message must contain to be
displayed. The substring is considered
to be a part of the AFTN bulletin
header. AFTN Viewer first tries to find
the bulletin substring, and if it is not
found or it is empty, it tries to find the
alternative bulletin substring.
1
The parameter is optional and can
be left empty.
Alt. header substring Defines an alternative substring which
the message must contain to be
displayed. The substring is considered
to be a part of the aeronautical report,
i.e. METAR or SPECI. Either the
header substring or this substring must
be found for a message to be
displayed in the field.
1)
If the bulletin substring is used, this
substring must be located in the
message after the bulletin
substring. If this substring is found,
the message is shown using the
New Message Alt. Text color.
End delimiter Defines the character which ends the
received AFTN message.
Required parameter.
Timeout Defines the time after which the
message is no longer displayed in the
field.
The time-out count starts from the
time when the message is
received, using the PC's clock.
Cancel Cancels the selections and closes the
window.
1. The Alt. bulletin substring and Alt. header substring are used, if there are two types of messages
displayed in the same message field. The latest received message of these two types will be displayed.
For example, the field might show METAR and SPECI messages. Thus you would use the Alt fields
for the SPECI messages.
Table 89 AFTN Viewer: Configuration Window Elements
Element Description Comment
VAISALA______________________________________________________________________ 195
Sound Configuration Window
If the Beep on Receive option is selected from the Settings menu, a
beeping sound is played when a message is received. You can configure
the sounds properties by selecting the Configure Beep option from the
Settings menu. In the Sound Configuration window that is displayed,
you can select whether the beep is sounded through the PCs sound card
or the internal speaker, and select other sound properties. The window
contains a Test button which can be used to test the beep before
accepting it. See section Changing the Beep Settings on page 200.
0404-087
Figure 46 AFTN Viewer: Sound Configuration Window
Users Guide ______________________________________________________________________
196 __________________________________________________________________M010027EN-F
Menu Bar
Table 90 AFTN Viewer: File Menu
Command Description
Exit Exits the application.
Table 91 AFTN Viewer: Settings Menu
Command Description
Pop Up On
Receive
Toggles on/off the Pop Up On Receive feature, that is, if the
application will pop up when a new message is received.
Beep On
Receive
Toggles on/off the Beep On Receive feature.
Font Displays the Windows standard Font window for selecting
the font used in the message fields.
Window
Background
Color
Displays the Windows standard color window for selecting
the background color for the application's main window,
including the message fields.
New Message
Text Color
the text color for new messages shown in the fields.
New Message
Alt. Text Color
the alternative text color for new messages shown in the
fields.
Known
Message Text
Color
the text color for known (older/recognized) messages
shown in the fields. A message switches from new to
known state after a configurable timeout.
Unavailable
Message Text
Color
the text color for unavailable messages shown in the fields.
When a message is unavailable, only the description
defined for the field is shown.
Configure
Beep
Displays the Sound Configuration window. See section
Sound Configuration Window on page 195.
Table 92 AFTN Viewer: Help Menu
Command Description
About Displays version and copyright information and a help text
for using the
VAISALA______________________________________________________________________ 197
0404-084
Figure 47 AFTN Viewer: About Window with Help
Operating AFTN Viewer
Starting AFTN Viewer
To start the AFTN Viewer application, select Start - Programs -
Vaisala MIDAS IV - AFTN Viewer, or click the AFTN Viewer
button in the application toolbar.
Exiting AFTN Viewer
To exit the AFTN Viewer application, select Exit from the File menu.
Viewing Received Messages
You can view the received messages in the AFTN Viewer main
window. The messages are shown in the message fields when they
arrive.
NOTE
When you open the application the next time, only the messages
received after starting the application will be displayed.
Users Guide ______________________________________________________________________
198 __________________________________________________________________M010027EN-F
0404-088
Figure 48 Received Message
For detailed information on the main window, message fields, pages,
and colors, see section Main Window on page 189.
Configuring Message Parameters
The message parameters have been configured during system
configuration, but if needed, you can change them in the Configuration
window.
You can configure the following:
- Description of the message in the AFTN Viewer
- Reception parameters that define how the messages are recognized
and thus displayed in the AFTN Viewer (bulletin and header
substring, and end delimiter)
- Timeout after which the message in no longer displayed.
- Define that the message field is not displayed at all (by leaving the
Description field empty)
For detailed description of the parameters, see section Configuration
Window on page 193.
To configure the reception parameters, do the following:
1. Keep the CTRL button pressed down and right-click on the
message whose parameters you want to configure. The
Configuration window for the message is displayed.
2. Change the parameters in the fields as needed. For description of
the window and its fields, see section Figure 45 on page 193.
3. Click the OK button.
VAISALA______________________________________________________________________ 199
To remove the message field, do the following:
1. Keep the CTRL button pressed down and right-click on the
message that you want to hide/remove. The Configuration
window for the message is displayed.
2. Remove the description from the Description field and click the
OK button.
Turning the Pop-Up Feature On and
Off
You can select if the AFTN Viewer main window pops up when a new
message is received.
- To turn the feature on, select Pop Up on Receive from the Settings
menu. The feature is selected, when there is a check mark in front
of the option.
- To turn the feature off, make the same selection again.
Turning the Beep Feature On and
Off
You can select if there is a beep sound when a new message is received.
- To turn the feature on, select Beep on Receive from the Settings
menu. The feature is selected, when there is a check mark in front
of the option.
- To turn the feature off, make the same selection again.
CAUTION
To display the field again, you need to configure the INI files. See
section Troubleshooting AFTN Viewer on page 200.
NOTE
The pop-up feature does not have the almost on top feature.
Users Guide ______________________________________________________________________
200 __________________________________________________________________M010027EN-F
Changing the Beep Settings
If you have the beep feature turned on, you can adjust the settings of the
sound in the Sound Configuration window.
1. Select Configure Beep from the Settings menu. The Sound
Configuration window is displayed.
2. Select an option button:
- If you want to use the standard Windows sounds, select one of
the options in the Sound Card frame. The options are the
same that can be found in the Windows control panel.
- If you want to use the PC's speaker, select the PC speaker
option. You can also configure the details of the PC speaker
sound by filling in the fields in the frame.
3. You can test what your selection sounds like by clicking the Test
button.
4. Accept your changes by clicking the OK button.
Changing the Font and Color
Settings
You can change the font and color settings by selecting the appropriate
option from the Settings menu. For detailed information on the options,
see Table 91 on page 196.
Troubleshooting AFTN Viewer
Table 93 on page 200 describes problem situations that might occur
when using AFTN Viewer and some typical solutions to them.
Table 93 Troubleshooting AFTN Viewer
A message field is
missing from the
template.
The description, header, or
timeout is missing from the
configuration.
Open the configuration file in
C:\Midas\m4aftn.ini in Notepad. Make
sure that the following parameters have
values: ITEMx.TAG, ITEMx.HEADER,
AND ITEMx.TIMEOUT (x is the number
of the field, 1-24). Save the file and
restart the AFTN Viewer application.
Chapter 15 ____________________________________________________________ Event Monitor
VAISALA______________________________________________________________________ 201
CHAPTER 15
EVENT MONITOR
This chapter contains instructions for viewing Event messages in the
Event Monitor application.
Introduction to Event Monitor
The Event Monitor application monitors system events. When a system
event occurs, the color of the Event Monitor Status icon on the taskbar
changes to red and an event message is displayed in Event Monitor. The
user has to acknowledge the event, and based on the type and status of
the event, decide on further action.
Event Monitor can also be used in the Bottom Line mode: instead of
the entire Event Monitor window, a single line that shows one event at
a time at the bottom of the screen can be displayed.
Optionally, Event Monitor can include the voice alarm function. A
speech synthesizer speaks aloud the alarms as they appear. If the system
includes a log printer, all events can be printed automatically as they
occur.
NOTE
Before reading this chapter, find out the event monitoring practices at
your airport. Event Monitor is a tool primarily intended for observers
and maintenance personnel. At some airports, the task of monitoring
events belongs either completely or partially to observers. At some
airports, it belongs to maintenance personnel.
Users Guide ______________________________________________________________________
202 __________________________________________________________________M010027EN-F
Event Monitor User Interface
The Event Monitor user interface consists of the Event Monitor Status
icon on the taskbar, the Event Monitor window, the menus, and the
toolbar. These elements are briefly described in the following sections.
For specific instructions on how to use the application, see section
Operating Event Monitor on page 208.
Event Monitor Status Icon
The Event Monitor Status icon is located on the taskbar of the
Windows operating system, next to the System Status icon. See
0109-009
Figure 49 Event Monitor Status Icon
The color of the icon shows if there are events in Event Monitor and
whether the events have been acknowledged or not. The colors are
explained in the following table.
CAUTION
The Event Monitor icon shows only the status of the events that have
been selected for viewing from the View menu. For example, if you
have selected only View - Technical Events, and the Event Monitor
icon is green, there can be unacknowledged events of another type.
Table 94 Event Monitor Status Icon Colors
Icon Color Explanation
Red There are unacknowledged events.
Yellow All events have been acknowledged by the user.
Green There are no events.
Blue There are only unacknowledged events of the type
Message Notification.
VAISALA______________________________________________________________________ 203
Event Monitor Window
When the Event Monitor application is opened, the Event Monitor
window with messages sent by the system appears. 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.
0412-112
Figure 50 Event Monitor Window
The following sections describe the items in the Event Monitor
window.
NOTE
The figure shows event messages created during software test
conditions. Normally, Event Monitor includes fewer event messages,
and the periods between messages are longer.
Users Guide ______________________________________________________________________
204 __________________________________________________________________M010027EN-F
Event Monitor Window Columns
On the left in the Event Monitor window, there is an icon in front of
each event message. When an event message first appears, the icon is
red. When the event has been acknowledged, the icon turns yellow.
The contents of the Event Monitor window columns are described in
Table 96 on page 204.
When you right-click on the Time or Message column, the following
option is displayed:
Table 95 Event Monitor Window Icon Colors
Icon Color Explanation
Red Unacknowledged event
Yellow Acknowledged event
Blue Unacknowledged event of the type Message Notification
Table 96 Event Monitor Window Columns
Column
Name
Description
Time Shows the time when the event was generated by the
system, or the acknowledgement time of the event. The
events are shown either oldest first, or latest first. Click the
Time column heading to change the order.
Message Shows the actual message text. In case of sensor-related
messages, this column shows a description of the problem
and the name of the problem sensor.
Site Shows the code of the measurement site to which the
message is related. In systems that include data collectors,
the site code refers to a data collector that has several
sensors connected to it.
Type Shows the type of the event message.
Status Shows the status of the event message.
Table 97 Event Monitor: Quick Menu
Command Description
Acknowledge
Selected
Marks the selected event(s) as acknowledged
VAISALA______________________________________________________________________ 205
When you right-click on the Site column, the following options are
displayed:
Each event is caused by a situation that the user needs to notice, or a
problem that must be fixed. The Type column provides further
information on the cause of the message, as presented in the following
table.
The Status column provides information about the status of the event,
as presented in the following table.
Table 98 Event Monitor: Quick Menu (Site Column)
Command Description
Show All Sites Displays events from all sites
Show Empty Sites Displays events that are not connected to any site
Site codes, for
example, 05
Displays events only from the selected site
System Displays system events
Table 99 Event Monitor Type Column
Type Explanation
OPER (Operational) There is a predefined change in weather.
TECH (Technical) There is a communication problem between the
CDU and a sensor, or another unusual technical
problem.
NONE (Internal) There is an unusual serious internal problem, for
example, within the CDU.
MESG (Message
Notifications)
Information on sent weather reports or reason for
triggering a SPECI report.
Table 100 Event Monitor Status Column
Status Explanation
ALARM There is a significant change in weather, a serious
internal problem, a problem in sending reports to the
AFTN line, or a limit for sending a SPECI report has
been reached.
WARNING There is a serious technical problem.
ACKED The user has acknowledged the event. The problem
may still exist.
INFO The user has sent a weather report to the AFTN line.
Users Guide ______________________________________________________________________
206 __________________________________________________________________M010027EN-F
Menu Bar
The Event Monitor functions can be selected from the menu bar.
Typical Event Monitor menus and menu commands are presented in the
following tables.
Table 101 Event Monitor: Event Menu
Command Description
Save As Saves the active screen to a file you specify.
Acknowledge Marks the selected event as acknowledged. If you
have not selected an event, marks the oldest
unacknowledged event as acknowledged (which is
selected by default).
Voice (Optional) Turns the voice alarm function on and
off.
Print Prints the active screen.
settings.
Exit Exits/Closes the Event Monitor application.
Table 102 Event Monitor: View Menu
Command Description
Bottom Line Displays a single event, or selected number of
events (1-20), at the bottom of the screen
All events Displays all events
Internal Events Displays only internal events
Technical Events Displays only technical events
Operational Events Displays only operational events
Message Notifications Displays only message notification events
Toolbar Shows/Hides the Event Monitor toolbar
Status Bar Shows/Hides the Event Monitor status bar
Hide when minimized Hides the Event Monitor button from the taskbar
Table 103 Event Monitor: Help Menu
Command Description
About Event Monitor Displays software version and copyright information
VAISALA______________________________________________________________________ 207
Toolbar
Toolbar is the fastest way of selecting the most frequently needed
functions. Typical buttons on the Event Monitor toolbar are described
in Table 104 on page 207.
Status Bar
The status bar displays information on the current state of Event
Monitor. It also shows context-sensitive help texts on the Event Monitor
buttons. When you move the mouse over a button, a short description of
the button is shown on the status bar.
Table 104 Event Monitor Toolbar Buttons
Save As saves the active screen to a file.
Copy copies the active screen to the Clipboard.
Acknowledge marks the selected event as acknowledged. If
you have not selected an event, marks the oldest
unacknowledged event as acknowledged (which is selected by
default).
Bottom Line displays a single event, or the selected number of
events at the bottom of the screen.
Voice turns the voice alarm function on and off (optional).
Print prints the active screen.
Users Guide ______________________________________________________________________
208 __________________________________________________________________M010027EN-F
Operating Event Monitor
Starting and Exiting Event Monitor
The Event Monitor application starts automatically when you log in.
You must keep the application open at all times to ensure a constant
flow of event messages.
When you do not need to view the Event Monitor window, you can
minimize it or use it in the Bottom Line mode. For more information,
see section Viewing Events in Bottom Line Mode on page 211.
To open a minimized Event Monitor, click the Event Monitor button
or the Event Monitor Status icon on the taskbar.
Monitoring and Acknowledging
Events
When you have read an event message, you must mark it as
acknowledged without delay. This is how you 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 event monitoring procedure is described below. Check the
airport-specific practices for a detailed procedure.
1. Monitor the Event Monitor Status icon on the taskbar. When the
icon turns red or blue, there are unacknowledged events.
2. In the Event Monitor window, select the event that you want to
acknowledge by clicking it with the mouse.
3. Then click the Acknowledge button on the toolbar. The
system marks the selected event as acknowledged and the color of
the icon next to the message turns yellow. The selection bar moves
to the oldest unacknowledged event.
CAUTION
Do not exit Event Monitor unless you have a special reason, such as
system maintenance. If it is necessary to exit Event Monitor for a
special reason, you can do it by selecting Exit from the Event menu.
VAISALA______________________________________________________________________ 209
4. Check the type and status of the event message and act as follows:
- If the message type is OPER, there is a preconfigured change
in weather. Act according to your airport-specific practices.
- If the message type is TECH or NONE (internal), contact
maintenance.
- If the type is MESG, depending on the message content,
consider sending a SPECI report or contact maintenance. For
further information, see section Monitoring Message
Notifications on page 210.
For information on event statuses, types, and needed action, see the
following table.
NOTE
If you do not select an event, the oldest unacknowledged event is
selected by default, and thus, marked as acknowledged when you click
the Acknowledge button.
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.
Table 105 Event Statuses, Types, and Needed Action
Status Type Situation Action
ALARM Internal
(NONE)
There is an unusual, serious internal problem, for
example, problems within the CDU.
Contact
maintenance.
ALARM Operational
(OPER)
There is a preconfigured change in the weather. Act according to
your airport-specific
instructions.
ALARM Message
Notifications
(MESG)
There is a problem with sending a weather report to
the AFTN line or a limit for sending a SPECI report
has been reached.
Contact
maintenance or
consider sending a
SPECI report.
WARNING Technical
(TECH)
There is a communication problem between the
CDU and a sensor, or another unusual, serious
technical problem.
Contact
maintenance.
INFO Message
Notifications
(MESG)
The user has sent a weather report to the AFTN
line.
No action is needed.
ACKED All types The event has been acknowledged. The problem
may still exist.
See other types
above.
Users Guide ______________________________________________________________________
210 __________________________________________________________________M010027EN-F
Monitoring Message Notifications
Message Notifications provide observers with information related to
weather reports. Message Notifications are indicated by the blue Event
Monitor Status icon and the event type MESG.
Message Notifications appear in four kinds of situations. Table 106 on
page 210 lists examples of these situations and provides instructions for
each situation.
Message Notifications remain on the Event Monitor window as long
as the user sends the next message of the kind indicated in the message.
For example, a METAR: SENT TO AFTN message would remain on
your Event Monitor for half an hour, depending on the configuration of
the system.
Using the Voice Alarm Function
If the system includes the optional voice alarm function, a speech
synthesizer reads out the event messages as they appear. When you hear
the message, check the details on the Event Monitor window and
acknowledge the message.
The voice alarm function only reads out the event types that have been
selected for viewing. Every message is only read out once.
Table 106 Examples of Message Notifications in Different
Situations
Situation Sample Event Message Status Action
Weather changes so that
a SPECI limit is reached.
SPECI: RVR LIMIT REACHED ALARM Edit and send SPECI, if
you consider it necessary.
A report is successfully
sent.
METAR: SENT TO AFTN INFO No action is needed.
The observer has
opened the SPECI
template to send a
SPECI report.
SPECI: OBSERVER
TRIGGERED
ALARM Make sure the SPECI
report is justified. This
message disappears when
the SPECI report is sent to
the AFTN line.
The system fails to
generate the report at a
required time.
REQUESTING MSG
GENERATION FROM
SYNOPSRV FAILED
ALARM Contact maintenance.
VAISALA______________________________________________________________________ 211
You can turn the voice alarm function on and off again. When the voice
alarm function is off, event messages appear on the screen normally, but
the speech synthesizer will not read them out.
You can turn the voice alarm function on and off in either of the
following ways:
- Selecting Voice from the Event menu
- Clicking the Voice button on the Event Monitor toolbar
When there is a check mark in front of the Voice option on the Event
menu, the voice alarm function is on.
Viewing Events in Bottom Line
Mode
You can minimize the Event Monitor window into a single event line
at the bottom of the screen. This is referred to as the Bottom Line mode.
You can also select to view more than one row.
Turning On Bottom Line Mode
To turn on the Bottom Line mode, do the following:
1. Open the Event Monitor window and make sure it is not
maximized.
2. Click the Bottom Line button in the Event Monitor toolbar. The
Event Monitor window will be displayed as a single line at the
bottom of the screen, showing only the latest event. An example of
the Bottom Line mode with single event line is presented in Figure
51 on page 212.
NOTE
When you turn the voice alarm function on again, the speech
synthesizer starts reading out the event messages as they appear,
beginning with the first new message. Messages that were displayed
during the time the voice alarm function was turned off, are not
spoken. Instead, you need to check them in the Event Monitor
window.
Users Guide ______________________________________________________________________
212 __________________________________________________________________M010027EN-F
0501-020
Figure 51 Event Monitor: Bottom Line Mode
Bottom Line mode is automatically in the Always on Top mode.
However, if you use the Windows Auto Hide option, the Bottom Line
occasionally disappears under Windows taskbar. To better view the
Bottom Line mode, disable the Windows Auto Hide function. Use the
Windows tools to change the taskbar settings. For more information,
see the operating system manuals.
The menu selections and toolbar buttons are not available in Bottom
Line view. To use them, you have to return to normal mode. However,
if you have selected to view only some event types, only the selected
types will be displayed in Bottom Line view.
Viewing Several Rows in Bottom Line Mode
To select to view more than one row in Bottom Line mode, do the
following:
1. In the Bottom Line view, press the CTRL button down, right-
click, and select the Bottomline Rows option.
2. In the Bottomline Rows window, enter the number of rows (1 - 20)
in the Number of rows field. The Event Monitor window will be
displayed with as many lines you just selected. For an example, see
0501-021
Figure 52 Event Monitor: Bottom Line Mode with Several
Rows
In this mode you can view all messages by scrolling the scroll bar on the
right. You can also sort the messages.
VAISALA______________________________________________________________________ 213
Turning Off Bottom Line Mode
To turn off the Bottom Line mode, do the following:
- Double-click the white area of the Bottom Line mode.
Viewing Event Monitor Always on
Top
To select that the Event Monitor application is always displayed on top
of other windows, do the following:
- On the Event Monitor window, press the CTRL button down,
right-click, and select the Always on Top option.
To get back to normal mode, do the following:
- Press the CTRL button down again, right-click, and remove the
check mark by clicking the Always on Top option.
When you switch to the Bottom Line mode, Event Monitor is
automatically in the Always on Top mode. Also when you get back to
the normal mode, the Always on Top selection is removed.
Viewing Selected Event Types
You can select which event types are displayed in Event Monitor. This
function must be used with care. All events need to be monitored by
some user group at the airport on a regular basis. Which events you need
to view depends on the organization of your airport.
For instance, if maintenance personnel take care of viewing Technical
and Internal events, you can select to view only Operational events.
By default, events of all types are shown. To select the event types you
want to view, do the following:
CAUTION
All event types must be monitored by some user group at the airport.
Otherwise, there is a risk of data loss and incorrect operation of the
MIDAS IV system. The practice of monitoring events may vary by
airport so before you select to view only some event types, make sure
that someone is monitoring all the other event types.
Users Guide ______________________________________________________________________
214 __________________________________________________________________M010027EN-F
1. Open the Event Monitor window.
2. From the View menu, select the type you want to view. A check
mark will appear in front of the selected type. The event list is
immediately updated to only show the event type you selected.
3. Continue until you have selected all the event types you wish to
view.
To view all events again, select All events from the View menu.
Viewing Events from Selected Sites
You can select the sites whose events are displayed in Event Monitor.
This is useful, for example, when troubleshooting problems in a
particular site. This function must be used with care. All sites need to be
monitored by some user group at the airport on a regular basis.
By default, events from all sites are shown. To select the site whose
events you want to view, do the following:
1. Open the Event Monitor window.
2. Right-click on the Site column. From the quick menu that is
displayed, select the site code whose events you want to view. A
check mark will appear in front of the selected site. The event list
is immediately updated to only show the events from the sites you
selected.
3. Continue until you have selected all the sites that you wish to view.
To view system events, select System. To view events from sites
that are not associated with any site, select Show Empty Sites.
4. When you want to view all sites again, right-click on the Site
columns, and select Show All Sites.
CAUTION
The Event Monitor icon shows only the status of the events that have
been selected for viewing from the View menu. For example, if you
have selected only View - Technical Events, and the Event Monitor
icon is green, there can be unacknowledged events of another type.
CAUTION
All operational sites types must be monitored. Otherwise, there is a
risk of data loss and incorrect operation of the MIDAS IV system.
Before you select to view only events from some sites, make sure that
someone is monitoring all the other operational sites.
VAISALA______________________________________________________________________ 215
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
Event Monitor window, the time it was acknowledged, and the time
the problem causing it was fixed.
Technical (TECH) and Internal (NONE) events are displayed on the
Event Monitor window until the problem causing them has been fixed.
Operational (OPER) events are displayed on the Event Monitor
window for as long as the condition causing the event message exists.
Message Notifications (MESG) remain on the Event Monitor window
as long as the user sends the next message of the kind indicated in the
message.
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 Event Monitor window.
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.
An example of the event chain is presented in the following table.
CAUTION
The Event Monitor icon shows only the status of the events from the
sites that have been selected for viewing from the View menu.
Table 107 An Example of the Event Chain
Event Icon Color Event Monitor Message and
Status
ASCII Log View Message
and Status
Communication between
cloud height meter and
and CDU corrupted at
09:38
RED 09:38 CLOUD MESSAGE
MISSING, Status: ALARM
09:38 CLOUD MESSAGE
MISSING, Status: 3
Observer notices and
acknowledges the event
at 09:43
YELLOW 09:43 CLOUD MESSAGE
MISSING, Status: ACKED
09:43 CLOUD MESSAGE
MISSING, Status: 1
Maintenance fixes the
problem at 10:09
- Message disappears from
Event Monitor
10:09 CLOUD MESSAGE
MISSING, Status: 0 (=
over)
Users Guide ______________________________________________________________________
216 __________________________________________________________________M010027EN-F
For more information on using ASCII Log View, see Chapter 16, ASCII
Log View, on page 219.
Hiding the Event Monitor Button
The Event Monitor button is displayed on the Windows taskbar by
default. Because the Event Monitor Status icon is always on the
taskbar, you may wish to hide the Event Monitor button.
To hide the Event Monitor button, do the following:
1. In the Event Monitor window, open the View menu and select
Hide when minimized.
2. Minimize the Event Monitor window. Now the Event Monitor
button does not appear on the taskbar. When you want to open the
Event Monitor window, double-click the Event Monitor Status
icon on the taskbar.
VAISALA______________________________________________________________________ 217
Troubleshooting Event Monitor
when you are using Event Monitor and some typical solutions to them.
Table 108 Troubleshooting Event Monitor
The System Status icon on the
taskbar is red, but there are no
events in the Event Monitor window.
There a serious system problem. Contact maintenance.
The Event Monitor Status icon on
the taskbar is red, but no events are
displayed in the Event Monitor
window.
There are no events for the event
type(s) that have been selected to
be shown in Event Monitor.
View all event types by
selecting All events from
the View menu.
Technical event "BROKEN
CONNECTION TO ALARM
SERVER" is displayed in Event
Monitor.
There is a technical problem in
the CDU or communication.
In the Bottom Line mode, the event
line occasionally disappears.
The Windows Auto hide option
might be selected.
Disable the Windows Auto
Hide option. In Windows
NT, click Start - Settings
- Taskbar and clear the
Auto hide check box. For
more information, see the
operating system manuals.
When you try to turn off the Bottom
Line mode by double-clicking the
event line, the full view of the Event
Monitor window will not be
displayed.
The Event Monitor window might
have been maximized when the
bottom line was turned on.
Double-click the white area
of the event line, or click
the maximize button that
appears in the top right
corner of the Bottom Line
view.
When you minimize the Event
Monitor window, it does not appear
on the taskbar.
The Hide when Minimized option
might be selected.
In the Event Monitor
window, open the View
menu. If the Hide when
minimized option is
checked, remove the check
mark by clicking the option.
Users Guide ______________________________________________________________________
218 __________________________________________________________________M010027EN-F
Chapter 16 __________________________________________________________ ASCII Log View
VAISALA______________________________________________________________________ 219
CHAPTER 16
ASCII LOG VIEW
This chapter contains instructions for viewing history files with the
ASCII Log View application.
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 for a period of one month or one year. After that, they are
automatically overwritten.
ASCII Log View User Interface
The ASCII Log View consists of the ASCII Log View window, the
menus, the toolbar, and the history data screens. The following sections
describe these elements briefly.
For instructions on how to open history files, see section Operating
ASCII Log View on page 228.
Users Guide ______________________________________________________________________
220 __________________________________________________________________M010027EN-F
ASCII Log View Window
Figure 53 on page 220 presents the ASCII Log View window when no
files have been selected for viewing.
0405-030
Figure 53 ASCII Log View Window
When history files have been selected for viewing, the parameters are
displayed in screens inside the ASCII Log View window.
The number and type of parameters that the system stores in history files
depends on the system configuration. Examples of typical screens are
presented in the following sections.
VAISALA______________________________________________________________________ 221
Weather Parameter Screens
An example of a weather parameter screen is presented in Figure 54 on
page 221, RVR data in this example. For a list of typical parameters, see
Appendix A, Parameter List, on page 325, and for the list of parameters
at your airport, the airport-specific documentation.
0207-024
Figure 54 ASCII Log View: Weather Parameter Screen
The weather parameter screen columns show weather parameters for
measurement sites. The content of the files is defined during system
configuration. The typical column names are explained in Table 109 on
page 221.
Table 109 ASCII Log View: Weather Parameter Screen
Columns
Column Description Example
CREATEDATE The date and time of the measurement.
The format is YYYY-MM-DD hh:mm:ss
2001-03-28
12:30:30
SITE The measurement site/runway. 02L
PARAMETER The stored weather parameter and its
identification data. Stored parameters are
always expressed in international units (SI).
RVR_1A
ST The status of the data at the time when the
data was stored.
c
Users Guide ______________________________________________________________________
222 __________________________________________________________________M010027EN-F
Status codes provide you with information on two things: what the
sensor mode (Backup and Manual) and data status (Old, Invalid,
Missing) were at storage time.
Normal status is indicated by an empty status column. All other statuses
have their specific codes as listed in the following table. If the data has
several simultaneous statuses, all these statuses are shown in the status
column. The typical status codes are explained in Table 110 on page
222.
Table 110 ASCII Log View: Status Codes
Status Code Data Status at Storage Time
- (no code) Normal status.
C (Backup) Data is coming 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 is not updated properly due to sensor
communication problems.
I (Invalid) Data is not valid due to an error in sensor calibration.
M or U (Missing) Data is not available due to sensor communication
problems.
VAISALA______________________________________________________________________ 223
Reports Screen
An example of a typical reports screen is presented in Figure 55 on page
223.
0305-058
Figure 55 ASCII Log View: Reports Screen
The typical reports screen column parameters are explained in Table
111 on page 223.
Table 111 ASCII Log View: Reports Screen Parameters
Column Description
CREATEDATE The date and time of the measurement. The format is
YYYY-MM-DD hh:mm:ss
TYPE The report type
MESSAGE METAR report as displayed in Weather View
Users Guide ______________________________________________________________________
224 __________________________________________________________________M010027EN-F
Events Screen
An example of a typical events screen is presented in the following
figure.
0305-059
Figure 56 ASCII Log View: Events Screen
The events file may differ from the one presented in the figure, because
the contents of the files are defined during system configuration. The
typical events screen column parameters are explained in Table 112 on
page 224.
Table 112 ASCII Log View: Events Screen Columns
Column Description Example
Time The date and time of the event. The format is
YYYY-MM-DD hh:mm:ss
2001-08-06
06:50:56
Counter The ordinal number of the event, for example,
number 8 indicates that the event is the eighth
event since the system restart.
8
Site The site of the event. 02L
MSG The event message as displayed in the Event
Monitor window and the Alarm window.
2_WIND_
SENSOR_
MISSING_
DATA
CAT The event type. For more information on Event
types, see the MIDAS IV Maintenance Manual.
TECH
ST The status of the event (0=over, 1=acknowledged,
2=alarm, 3=warning, 4=message notification)
2
VAISALA______________________________________________________________________ 225
Menu Bar
The ASCII Log View functions can be selected from the menu bar.
Typical ASCII Log View menus and menu commands are presented in
the following tables.
Table 113 ASCII Log View: File Menu
Command Description
Open Opens a new history file
Close Closes the history file
Save as Text Saves the file as a .txt file in the same folder where the
.his file is
Automatic
Refresh
Automatically checks every 10 seconds if the file has
changed and updates the data on the screen with the
changed data.
Refresh Immediately checks if the file has changed and updates
the data on the screen with the changed data.
Print Prints the active screen
settings
Exit Exits the ASCII Log View application
Table 114 ASCII Log View: Edit Menu
Command Description
Paste Pastes the copied data
Table 115 ASCII Log View: View Menu
Command Description
Toolbar Shows/Hides the ASCII Log View toolbar
Status bar Shows/Hides the ASCII Log View status bar
Go To First Row Moves to the first row of the file
Go To Last Row Moves to the last row of the file
Users Guide ______________________________________________________________________
226 __________________________________________________________________M010027EN-F
Table 116 ASCII Log View: Window Menu
Command Description
New Window Opens another window for the active screen
Cascade Arranges data screens one on top of the other
Tile Arranges data screens in vertical rows
Split Allows moving the column border to split the file into two
parts
Close All Closes all open windows
Table 117 ASCII Log View: Help Menu
Command Description
About Displays software version and copyright information
VAISALA______________________________________________________________________ 227
Toolbar
The toolbar is the fastest way of selecting the most frequently needed
functions. A typical ASCII Log View toolbar contains the buttons listed
Status Bar
The status bar displays information on the current state of ASCII Log
View. The status bar also shows context-sensitive help texts on ASCII
Log View buttons. When you move the mouse over a button, a short
Table 118 ASCII Log View Toolbar Buttons
Open opens a new file.
Save as Text saves the file as a .txt file in the same folder where
the .his file is.
Copy copies the selected text to the Clipboard.
Print prints the active screen.
Automatic Refresh checks every 10 seconds if the file has
changed and updates the data on the screen with the changed
data.
Go To First Row moves to the first row of the file.
Go To Last Row moves to the last row of the file.
Refresh immediately checks if the file has changed and updates
the data on the screen with the changed data.
Users Guide ______________________________________________________________________
228 __________________________________________________________________M010027EN-F
Operating ASCII Log View
Starting and Exiting ASCII Log View
To start ASCII Log View, click the button on the Application
Toolbar.
To exit ASCII Log View, select Exit from the File menu.
Viewing History Files
By default, the history files are located on the CDU in the
D:\MIDASIV\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.
0211-080
Figure 57 ASCII Log View: Opening History Files
VAISALA______________________________________________________________________ 229
Typical names of different history files are listed in Table 119 on page
229.
To view history files, do the following:
1. Start the ASCII Log View application by clicking the ASCII Log
View button on the Application Toolbar.
2. On the File menu, click Open. A file selection window is
displayed.
3. In the file selection window, open the D:\MIDASIV\HISTORY
folder, or another folder specified for history files in your system.
4. If needed, select the folder you wish to view, for example, a
monthly folder.
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. Click Open. The file is displayed in the ASCII Log View window.
7. To see all the columns, drag the column borders or use the scroll
bar. For an explanation of the column parameters, see the
corresponding screen presentations in section ASCII Log View
User Interface on page 219.
8. You can move in the file by clicking the Go To First Row and Go
to Last Row button in the toolbar.
9. Open all the files you wish to view. Several screens can be open at
the same time.
Table 119 Sample ASCII Log View File Names
Example Path and File Name Stored Data Explanation
MIDASIV\history\(month\)
(PARAMETER)_02L_25.his
Weather data Parameter data for
measurement site 02L
from the 25th day of the
month
REPORTS_25.his
Reports Report data on the 25th
day of the month
EVENTS_25.his
Events Event data on the 25th
day of the month
NOTE
In some systems, history files are stored on 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.
Users Guide ______________________________________________________________________
230 __________________________________________________________________M010027EN-F
10. Close the file by selecting Close from the File menu.
11. Exit ASCII Log View by selecting Exit from the File menu.
Resizing Panes and Columns
You can adjust the screens by resizing the panes and columns. This way,
you can fit more data on one screen or display only some parameters.
To resize columns or panes, do the following:
1. Place the mouse cursor over the pane border or the column border.
2. Click and drag the pane or column border with the mouse to the
location where you want the new border. Three dots after a column
heading indicates that a part of the column is hidden.
Alternatively, you can:
1. Select Split from the Window menu.
2. Drag the pane or column border with the mouse to the location
where you want the new border.
To hide columns, drag the right column border of the column to the left
until the column is hidden.
To show the column again, drag the right column border back to the
right.
Scrolling the Screens
You can also scroll the screen with the vertical scroll bar on the right
side of the screen or the horizontal scroll bar on the bottom of the
screen. The left pane automatically scrolls with the right pane when you
use the right-pane scroll bar.
VAISALA______________________________________________________________________ 231
Viewing Several Windows at the
Same Time
To view several history files at the same time, do the following:
1. Open all the history files you wish to view.
2. From the Window menu, select Cascade or Tile. All the opened
history files will be displayed.
3. Resize and arrange the windows as needed.
When the file is large, it is convenient to view the same file in several
windows. This way, you can view parameters from different periods at
the same time without having to scroll back and forth in the file.
To view one file in several windows, do the following:
1. Open the file and select New Window from the Window menu.
2. The file will be opened in a new window. You can scroll to the
position you want to view without losing the original position in
the first window.
Refreshing Data
Normally the data in the screens is not refreshed. You can, however,
select to either refresh the data manually or automatically with the
changed data in the file.
To refresh the data immediately, do the following:
1. Click the Refresh button or select Refresh from the File menu.
2. The screen is immediately updated with any changed data.
To use automatic refreshing, do the following:
1. Click the Automatic Refresh button or select Automatic Refresh
from the File menu.
2. The system will check every 10 minutes if the data has changed and
will refresh the screen with the new data.
Users Guide ______________________________________________________________________
232 __________________________________________________________________M010027EN-F
Copying Text from History Files
You can copy text from the history files to be used in sending
corrections to earlier METAR reports, for example, or for collecting
data for troubleshooting purposes.
To copy text from the history files, do the following:
1. In ASCII Log View, select the text by clicking the text row you
want to copy.
2. Select Edit - Copy.
3. Select Edit - Paste in the application where you want the text to be
copied to.
To copy several rows, select the first row you want to copy, hold down
the SHIFT key, and select the rows by pressing the DOWN ARROW
key until all rows are selected.
Troubleshooting ASCII Log View
when you are using ASCII Log View and some typical solutions to
them.
Table 120 Troubleshooting ASCII Log View
You cannot find the history files in
the CDU folder
D:\MIDAS\HISTORY.
The history files might be
located on another location
on the CDU or on a network
drive.
Check the location of the history
files from system maintenance,
and check that the drive has been
shared and mapped on your
workstation.
You cannot find history files for the
previous months.
Depending on the
configuration, the history files
might be stored only for one
month.
Check the storage time from
system maintenance or airport-
specific documentation.
When viewing a history file, some
parameters or columns are missing.
The columns might have
been dragged on top of each
other by mistake.
Drag the column borders so that
the hidden columns will appear.
Chapter 17 _________________________________________________________________ Actuals
VAISALA______________________________________________________________________ 233
CHAPTER 17
ACTUALS
This chapter contains instructions for using manual or backup data with
the Actuals application.
Introduction to Actuals
The Actuals application is used for viewing raw sensor data and for
entering manual or backup data. When a sensor is out of order or being
maintained, its mode in MIDAS IV can be set to Backup or Manual.
This can be done in the Actuals weather data windows.
In Backup mode the weather data is provided by a predefined backup
sensor. In manual mode, data has to be entered by the user. Typically
the maintenance personnel will inform the users when to use Actuals for
to change the sensor mode. For some values, manual and backup values
are entered in the Data Source Manager application, which can be
opened from Actuals.
The values entered in the Actuals weather data windows appear in
Weather View and METAR/MET REPORT applications. In Weather
View, the values appear as manual or backup weather data, shown on a
yellow or light blue background. Also manual observation data for
METAR reports can be entered, using the Manual Observations
window.
Actuals can also be used for manually entering the background
luminance and light intensity information using the Runway
Parameters window.
Users Guide ______________________________________________________________________
234 __________________________________________________________________M010027EN-F
Actuals User Interface
The Actuals user interface consists of the several Actuals windows, the
menus, the toolbar, the Manual Observations window, and the
Runway Parameters window. These elements are briefly explained in
the following sections. For instructions on how to use the application,
see section Operating Actuals on page 252.
The Actuals windows are displayed when you select the appropriate
button from the toolbar, or the correct menu item from the Actuals
menu. The windows display raw sensor data for different weather
parameters, and the sensor mode, which can be changed. When the
manual mode is selected the values can be entered by the user in the
windows.
0412-018
Figure 58 Actuals User Interface
Chapter 17 _________________________________________________________________ Actuals
VAISALA______________________________________________________________________ 235
The typical elements on the Actuals weather data windows are
The colors of the data fields in the weather data windows are described
An example of the data fields in backup and manual mode is presented
Table 121 Elements in the Weather Data Windows
Element Description
RWY/POS or
RWY name
Displays the runway/location where the data comes from.
In Backup and Manual mode, changes to N/A to indicate
that the data is not coming from the normal source.
Oper. Mode Operation mode of the sensor: Auto for Automatic, Back
for Backup, or Man for Manual.
Data fields Each weather data screen includes a number of data fields
related to the weather phenomenon in question. See the
following sections and Appendix A, Parameter List, on
page 325.
Edit Allows you to edit the data manually (when in Manual
mode).
Apply Applies the changes made manually (when in Manual
mode).
Cancel Cancels the changes made manually (when in Manual
mode).
Graph Graphical representation of the cloud base (in Cloud
Actuals).
Table 122 Actuals Data Field Colors
Color Explanation
Gray Data is in Automatic mode.
Yellow Data is in Manual mode.
Light blue Data is in Backup mode (not in RVR/Visibility Actuals).
White Data is in Manual mode and can be edited.
Slashes There are sensor or communication line problems.
Users Guide ______________________________________________________________________
236 __________________________________________________________________M010027EN-F
0404-050
Figure 59 Actuals Backup and Manual Modes
The following sections provide a brief description of the Actuals
weather data windows. The windows can be selected using the toolbar
buttons.
1 = RWY/Location, N/A indicates that data is not coming from
the normal source
2 = Operation mode indicator
3 = Data fields in Backup mode (blue background)
4 = Data fields in Manual mode (yellow background)
5 = Data fields in Manual mode (editing mode, white
background)
Chapter 17 _________________________________________________________________ Actuals
VAISALA______________________________________________________________________ 237
Wind Actuals Window
Figure 60 on page 237 presents a typical Wind Actuals window.
0207-029
Figure 60 Wind Actuals Window
The Wind Actuals window contains instant (INS), average (AVG),
minimum (MNM), and maximum (MAX) values for wind parameters.
The XAVG field contains the head wind/cross wind value on the
location indicated. MIDAS IV uses the 2- and 10-minute time periods
for averaging the wind values. For example, the 10MNM data fields are
the 10-minute average values. For detailed explanation of the typical
parameters, see Appendix A, Parameter List, on page 325.
Users Guide ______________________________________________________________________
238 __________________________________________________________________M010027EN-F
Cloud Actuals Window
Figure 61 on page 238 presents a typical Cloud Actuals window.
0305-060
Figure 61 Cloud Actuals Window
On the left in the Cloud Actuals window, there are data fields for cloud
parameters. On the right, there is the cloud hit table, which is a graphical
representation of the cloudbase. Basically, cloudbase is the average
height of the lowest cloud layer measured during the last 20 minutes.
For cloudbase determination, the system divides the sky into altitude
sectors. When the cloud height sensor reports an instant cloud height,
the system records it for the appropriate sector. This forms a hit. The
system continues recording the hits typically for a period of 20 minutes.
After the 20-minute period, the system determines the cloudbase to be
at the height which has the most hits. It also weights the cloud hits that
have been recorded in the end of the 20-minute period.
Chapter 17 _________________________________________________________________ Actuals
VAISALA______________________________________________________________________ 239
Weather Actuals Window
Figure 62 on page 239 presents a typical Weather Actuals window.
0207-031
Figure 62 Weather Actuals Window
The Weather Actuals window contains values typically related to
temperature, dew point, and relative humidity. These values can be
instant (INS), maximum (X), or minimum (M).
Users Guide ______________________________________________________________________
240 __________________________________________________________________M010027EN-F
Pressure Actuals Window
Figure 63 on page 240 presents a typical Pressure Actuals window.
0305-072
Figure 63 Pressure Actuals Window
The Pressure Actuals window contains several fields for pressure data.
These values can be instant (INS), minimum (M), and maximum (X).
Pressure Values in Data Source Manager
Application
If your system contains the Data Source Manager application, it is
typically used for setting the pressure values to manual or backup mode.
Thus, when clicking the Pressure button, or selecting Pressure from the
Actuals menu, the Data Source Manager application is displayed. For
more information on the Data Source Manager application, see Chapter
18, Data Source Manager, on page 261.
Chapter 17 _________________________________________________________________ Actuals
VAISALA______________________________________________________________________ 241
RVR/Visibility Actuals Window
Figure 64 on page 241 presents a typical RVR/Visibility Actuals
window.
0208-014
Figure 64 RVR/Visibility Actuals Window
The RVR/Visibility Actuals window contains average (A), minimum
(M), and maximum (X) data fields for RVR and visibility values.
MIDAS IV calculates 1- and 10-minute values for RVR and visibility.
10-minute values are the values used in METAR/SPECI reports and 1-
minute values in local reports (MET REPORT/SPECIAL).
With visibility values, only Automatic and Manual modes are possible,
since the runway visibility sensor does not have a backup sensor.
Visibility can vary greatly within short distances, so the use of a backup
sensor could result in inaccurate data. However, the background
luminance value can be copied from another sensor and thus the backup
color may be displayed in the fields.
Users Guide ______________________________________________________________________
242 __________________________________________________________________M010027EN-F
Prevailing Visibility Values in Data Source Manager
Application
If your system contains the Data Source Manager application, it is
typically used for setting the prevailing visibility values to manual or
backup mode. Thus, when clicking the Prevailing Visibility button, or
selecting Prevailing Visibility from the Actuals menu, the Data Source
Manager application is displayed. For more information on the Data
Source Manager application, see Chapter 18, Data Source Manager, on
page 261.
Manual Observations Window
The Manual Observations window in the Actuals application is used
for entering manual observations about a weather parameter that is not
measured by any sensor. For the instructions on activating and using the
window, see section Using Manual Observations Window on page 257.
A typical Manual Observations window is presented in Figure 65 on
page 243.
Chapter 17 _________________________________________________________________ Actuals
VAISALA______________________________________________________________________ 243
0412-111
Figure 65 Actuals: Manual Observations Window
Data Fields
The values entered in Manual Observations window will be displayed
in the corresponding fields of the METAR/MET REPORT template.
The following tables explain the meaning of the data fields of the
Manual Observations window and the corresponding fields in the
METAR/MET REPORT template. Depending on the configuration of
the system, the window might not include all the fields listed in the
tables.
The values entered in Present Weather Codes fields affect the present
weather fields in both METAR/SPECI and MET REPORT/SPECIAL
Users Guide ______________________________________________________________________
244 __________________________________________________________________M010027EN-F
view in the METAR/MET REPORT template. See Table 123 on page
244.
The Cloud Layers data fields affect only the data fields in the METAR/
SPECI view in the METAR/MET REPORT template. MET
REPORT/SPECIAL fields are not affected. See Table 124 on page 244.
The first row in the Cloud Layers frame represents the lowest cloud
layer. For the lowest cloud layer, the cloudbase height cannot be
entered. If the system includes a cloud height sensor, the cloudbase
height for the first row is provided automatically to the METAR/
MET REPORT template from the sensor. If the system does not
include a cloud height sensor, the cloudbase height for the lowest cloud
layer must be manually entered in the METAR/MET REPORT
template.
The Recent Weather Codes data fields affect the corresponding fields
in both METAR/SPECI and MET REPORT/SPECIAL view in the
METAR/MET REPORT template. See Table 125 on page 245.
Table 123 Manual Observations Window: Present Weather
Codes
Field Explanation METAR/MET
REPORT Field
1st field First present weather code PRESENT
WEATHER, 1st field
2nd field Second present weather code PRESENT
WEATHER, 2nd field
3rd field Third present weather code PRESENT
WEATHER, 3rd field
Table 124 Manual Observations: Cloud Layers Fields
Field Explanation METAR/MET REPORT Field
Amount Cloud amount (SKC, FEW,
SCT, BKN, OVC)
CLOUDS, 1st field of each row
(only in METAR/SPECI)
Height Cloud height meters, feet,
or hundreds of feet
CLOUDS, 2nd field of each
row (only in METAR/SPECI)
Type Cloud type (CB, TCU,
empty = other than CB/
TCU, /// = type info not
available)
CLOUDS, 3rd field of each row
(only in METAR/SPECI)
Chapter 17 _________________________________________________________________ Actuals
VAISALA______________________________________________________________________ 245
The Runway State data field affects the RUNWAY STATE data field
in the METAR/SPECI view in the METAR/MET REPORT template.
Update Button
The Update button saves the entered data and displays them in Weather
View and other applications, as configured.
Table 125 Manual Observations Window: Recent Weather and
Runway State Fields
Field Explanation METAR/MET REPORT Field
Rew'w' Recent weather code REWX
RWY State State of runway RUNWAY STATE (only in
METAR/SPECI)
Table 126 Manual Observations: Remark and Note Fields
Element Explanation
RMK Free text field. Will be displayed in the REMARK field of the
METAR/MET REPORT template.
Note 1 - 3 Free text fields. The contents can be configured to be
displayed, for example, on Weather View.
Users Guide ______________________________________________________________________
246 __________________________________________________________________M010027EN-F
Runway Parameters Window
The MIDAS IV system uses the Background Luminance parameter to
calculate the RVR value (Runway Visual Range) shown in Weather
View. Normally, this value is measured by a Background Luminance
meter. If the sensor is out of order, or is not included in the system, the
Runway Parameters window can be used for entering the background
luminance values. The window is displayed when Runway
Parameters is selected from the Actuals menu. The window also
displays the light intensity values. For an example of the window, see
0408-026
Figure 66 Runway Parameters Window
For instructions on using the Runway Parameters window, see section
Entering Background Luminance on page 255.
Chapter 17 _________________________________________________________________ Actuals
VAISALA______________________________________________________________________ 247
The typical elements of the Background Luminance frame of the
Runway Parameters window are described in Table 127 on page 247.
The preconfigured ranges for background luminance are typically the
following as specified by ICAO.
Table 127 Runway Parameters Window, Background
Luminance Frame
Element Description
Set manual background luminance frame:
Manual check boxes for
the runways (marked
with, for example, 04R,
RWY 1, or RWY A)
Allows you to select the check box for the runways
whose background luminance you want to enter
manually. The runway names are configurable.
Select touchdown
zones list
If configured, allows you to select the touchdown
zones whose background luminance you want to
enter manually.
Select All If configured, selects all the check boxes in the
Select touchdown zones list.
Clear All If configured, removes the selection from all the
check boxes in the Select touchdown zones list.
Background Luminance
list box
Allows you to select a preconfigured range for
background luminance (NIGHT, INTERMEDIATE,
NORMAL DAY, BRIGHT DAY) for the selected
runways. See Table 128 on page 247.
Value Shows the background luminance value. Also
allows you to enter an exact value for background
luminance. The exact value overrides the selected
preconfigured range.
Apply Saves the background luminance selections and
displays the values in the Manual background
luminance values frame below.
Manual background luminance value frame:
ID column Shows the ID of the runway or touchdown zone.
Manual BL column Shows the background luminance value entered
manually for the runway or touchdown zone.
Close Closes the Runway Parameters window.
Table 128 Preconfigured Ranges for Background Luminance
Condition Illumination Threshold
(lx)
Background
Luminance (cd/m
2
)
Night
8 x 10
-7
50
Intermediate
10
-5
51-999
Normal day
10
-4
1000 - 12000
Bright day (sunlit fog)
10
-3
> 12000
Users Guide ______________________________________________________________________
248 __________________________________________________________________M010027EN-F
Table 129 Runway Parameters Window, Light Intensity Frame
Element Description
Set manual light intensity frame:
Manual check boxes Allows you to select the check box for the runways
whose light intensity you want to enter manually.
Edgelight list box If configured, allows you to select the light
intensity percentage for the edge light on the
runway.
Centerlight list box If configured, allows you to select the light
intensity percentage for the center light on the
runway.
Rwylight list box If configured, allows you to select the light
intensity percentage for the runway light on the
runway.
Apply Saves the light intensity values and displays the
values in the Light intensity values and statuses
frame below.
Light intensity values and statuses frame:
Runway column Shows the runway name.
Status column Shows the status of the light intensity for the
runway (Normal, Missing, Manual). The Normal
status indicates that the automatic input is
available, Missing that there are problems with the
automatic input, and Manual that the values have
been entered manually.
Edge column If configured, shows the light intensity in
percentage for the edge lights.
Center column If configured, shows the light intensity in
percentage for the center lights.
Runway column If configured, shows the light intensity in
percentage for the runway.
Close Closes the Runway Parameters window.
Chapter 17 _________________________________________________________________ Actuals
VAISALA______________________________________________________________________ 249
Menu Bar
The Actuals functions can be selected from the menu bar. Typical
Actuals menus and menu commands are presented in the following
tables.
Table 130 Actuals: Actuals Menu
Command Description
Wind Displays the Wind Actuals window
Cloud Displays the Cloud Actuals window
RVR/Visibility Displays the Visibility Actuals window
Weather Displays the Weather Actuals window
Pressure Displays the Pressure Actuals window, or the
Pressure tab of the Data Source Manager
application
Prevailing Visibility Displays the Prevailing Visibility tab of the Data
Source Manager application
Manual
Observations
Displays the Manual Observations window
Runway Parameters Displays the Runway Parameters window for
manually defining the Background Luminance and
light intensity values
Close Closes the current window
Print Prints the current window
Print setup Opens a window for changing the printer and paper
settings
Exit Exits the Actuals application
Table 131 Actuals: Edit Menu
Command Description
Paste Pastes the copied data
Copy As Bitmap Copies the screen as a bitmap image to the
Clipboard
Users Guide ______________________________________________________________________
250 __________________________________________________________________M010027EN-F
The Actions menu is displayed when the Manual Observations
window is open.
Table 132 Actuals: Actions Menu
Command Description
Update Updates the data
Table 133 Actuals: View Menu
Command Description
Toolbar Shows/Hides the Actuals toolbar
Status bar Shows/Hides the Actuals status bar
Table 134 Actuals: Window Menu
Command Description
Close All Closes all open screens
Table 135 Actuals: Help Menu
Command Description
About Actuals Displays software version and copyright information
Chapter 17 _________________________________________________________________ Actuals
VAISALA______________________________________________________________________ 251
Toolbar
The toolbar is the quickest way of selecting the most frequently needed
functions. The Actuals toolbar buttons are described in Table 136 on
page 251.
Status Bar
The status bar displays information on the current state of Actuals. The
status bar also shows context-sensitive help texts on Actuals buttons.
When you move the mouse over a button, a short description of the
button is shown on the status bar.
Table 136 Actuals Toolbar Buttons
Wind Actuals opens the Wind Actuals window.
Cloud Actuals opens the Cloud Actuals window.
RVR/Visibility Actuals opens the RVR/Visibility Actuals
window.
Weather Actuals opens the Weather Actuals window.
Pressure Actuals opens the Pressure Actuals window or the
Pressure tab of the Data Source Manager application.
Prevailing Visibility Actuals opens the Prevailing Visibility tab
of the Data Source Manager application.
Runway Parameters opens the Runway Parameters window.
Manual Observations opens the Manual Observations window.
Print prints the active window.
Users Guide ______________________________________________________________________
252 __________________________________________________________________M010027EN-F
Operating Actuals
Starting and Exiting Actuals
To start Actuals, click the Actuals button on the Application
Toolbar.
To exit Actuals, select Exit from the Actuals menu.
Using Automatic Mode
During normal operation, data flow from the sensors is in Automatic
mode, producing a constant flow of data from the sensors to the
applications. Current data and values in the Actuals windows are
updated automatically by the system, and no user action is needed.
When a sensor is in Automatic mode, the data is displayed on a gray
background. The text in the Oper. mode field is Auto and the runway
name is shown in the RWY/POS field.
A typical Actuals window in automatic mode is presented, for example,
If your system includes the Data Source Manager application, the
values for Pressure and Prevailing Visibility are displayed in the
Pressure and Prevailing Visibility tabs of the application. For more
information, see section Data Source Manager on page 261.
Using Backup Mode
During sensor problems, or maintenance, when normal data flow from
a sensor to the CDU is interrupted, you might need to set the data to
Backup mode. In Backup mode, the data is provided by a predefined
backup sensor instead of the primary sensor.
In the RVR/Visibility window, the Backup mode is not possible,
because runway visibility sensors do not have a backup sensor. Since
visibility can vary greatly within short distances, the use of a backup
sensor could lead to inaccurate data. However, the background
Chapter 17 _________________________________________________________________ Actuals
VAISALA______________________________________________________________________ 253
luminance value can be copied from another sensor and thus the backup
color may be displayed in the fields.
To set a specific sensor to Backup mode, do the following:
1. Start Actuals. The Actuals main window appears.
2. From the Actuals menu, select the Actuals window (Wind/Cloud/
Visibility/Weather/Pressure) that includes the values of the sensor
you want to set to Backup mode. The selected Actuals window
appears.
3. From the Oper. Mode list box of the appropriate sensor, select
Backup or Back. The background color of the data fields in that
column changes to light blue and the text in the RWY/POS field
changes to N/A. Data is now coming from a preconfigured backup
sensor.
4. Keep the selected Actuals window open. Monitor the sensor
problem with Event Monitor or wait for instructions from
maintenance personnel.
5. When the problem has been fixed, change the sensor mode back to
Automatic by selecting Auto from the Oper. Mode list.
An example of a typical window with sensor data in backup mode is
values for Pressure and Prevailing Visibility are displayed in the
CAUTION
Before changing sensor modes in a problem situation, you need to get
instructions from maintenance personnel. They will tell you when to
set a sensor in Backup mode and when to set it back to Automatic
mode.
Users Guide ______________________________________________________________________
254 __________________________________________________________________M010027EN-F
Using Manual Mode
During sensor problems or maintenance and when there is no backup
sensor available, you might need to set a sensor to Manual mode and
enter values manually.
To set a sensor to Manual mode and edit values, do the following:
1. Start Actuals.
2. From the Actuals menu, select the Actuals window (Wind/Cloud/
Visibility/Weather/Pressure) that includes the values of the sensor
you want to set to Manual mode. The selected Actuals window
appears. For pressure and prevailing visibility values, the Data
Source Manager application opens. See Chapter 18, Data Source
Manager, on page 261.
3. From the Oper. Mode list box of the appropriate sensor, select
Manual or Man. The background color of the data fields in that
column changes to yellow, and the Edit button appears. The text in
the RWY/POS field changes to N/A. Because the internal mode
change updating period is approximately one second, the mode
does not change immediately.
4. Click the Edit button. If the Edit button is not visible, scroll down
the window. The background color of the data fields changes to
white.
5. Edit the values as required or enter new values in the appropriate
fields.
6. When you have finished editing the values for that sensor, click the
Apply button. If you want to cancel the changes you made, click
Cancel.
7. Keep the selected Actuals window open. Update the values
regularly, as there is no data coming from the sensor automatically.
Click Apply after every change.
8. Monitor the sensor problem with Event Monitor or wait for
instructions from the maintenance personnel. When the problem is
fixed, change the sensor mode back to Automatic.
NOTE
Before changing sensor modes in a problem situation, you need to get
instructions from maintenance personnel. They will tell you when to
set a sensor in Backup mode and when to set it back to Automatic
mode.
Chapter 17 _________________________________________________________________ Actuals
VAISALA______________________________________________________________________ 255
An example of a typical window with sensor data in manual mode is
manual values for Pressure and Prevailing Visibility are displayed in the
Entering Background Luminance
The MIDAS IV system uses the Background Luminance parameter to
calculate the RVR value (Runway Visual Range) shown in Weather
View. Normally, this value is measured by a Background Luminance
meter. If the sensor is out of order, or is not included in the system, the
Runway Parameters window can be used for entering the background
luminance values.
To enter Background Luminance value manually, do the following:
1. Open the Actuals application.
2. From the Actuals menu, select Runway Parameters. The
Runway Parameters window appears.
3. In the Runway Parameters window, select the Manual check box
for the appropriate runway(s) in the Background Luminance
frame.
4. In the Select touchdown zones box, select the check boxes for the
appropriate touchdown zones. If the values to be entered are the
same for several touchdown zones, you can select them all at the
same time.
5. From the Background Luminance list box, select the
preconfigured range (NIGHT, INTERMEDIATE, NORMAL
DAY, BRIGHT DAY), see Table 128 on page 247. The exact
value is shown in the Value field below. You can also enter a
specific value manually in the Value field below the list. This
value overrides the preconfigured range you may have selected.
NOTE
In the Cloud Actuals window, when editing the VER VIS field
manually, you must first enter the value NCD (No Clouds Detected) in
the Base field. The system then enters the same value in other cloud
fields.
Users Guide ______________________________________________________________________
256 __________________________________________________________________M010027EN-F
6. Click the Apply button. The values are updated and the manual
values are displayed in the Manual background luminance
values frame below.
7. Repeat for all the runways and touchdone zones whose values you
want to enter manually.
8. Keep the Runway Parameters window open. Monitor and update
the Background Luminance value on a regular basis as long as
manual input is needed.
9. When manual input is no longer needed, remove the selection from
the Manual check box(es), click Apply, and then Close.
Entering Light Intensity Manually
The MIDAS IV system normally receives the light intensity value
automatically from a light setting unit. If the automatic input is not
available, and depending on the configuration, the Runway
Parameters window can be used for entering the light intensity values.
To enter the light intensity value manually, do the following:
3. In the Light Intensity frame, select the Manual check box for the
runway(s) whose light intensity value you want to change.
4. Select the appropriate light intensity from the Edgelight and
Centerlight, or Rwylight list(s) for each runway.
5. Click the Apply button. The values are updated and the manual
values are displayed in the Light intensity values and statuses
frame below. The status of the runways you selected are displayed
as Manual.
6. Keep the Runway Parameters window open. Monitor and update
the light intensity value on a regular basis as long as manual input
is needed.
7. When manual input is no longer needed, remove the selection from
the Manual check box(es), click Apply and then click Close.
Chapter 17 _________________________________________________________________ Actuals
VAISALA______________________________________________________________________ 257
Viewing Light Intensity Status
To view the light intensity status on the runways, do the following:
3. In the Runway Parameters window, the status of light intensity is
displayed in the Light intensity values and statuses frame. Either
the values for Edge and Center, or for the whole runway are
displayed. If the status is Missing, there are problems with the
automatic input of light intensity. You may want to consider
entering the values manually. See section Entering Light Intensity
Manually on page 256.
4. To exit the window, click the Close button.
Using Manual Observations
Window
With the Manual Observations window you can enter manual
observations for a weather parameter that is not measured by any
sensor. Using the Manual Observations window requires covering the
following phases:
1. Activate the Manual Observations window to create a link
between the Manual Observations window and the METAR/
MET REPORT Manager application. For instructions, see section
Activating the Manual Observations Window on page 257.
2. Define the values as ManObs in METAR/MET REPORT
Manager. For instructions, see section Defining METAR/SPECI
Values as ManObs on page 258.
3. Enter the values in the Manual Observations window and click
the Update button. For instructions, see section Entering Manual
Observations on page 259.
Activating the Manual Observations Window
The first time you use the Manual Observations window, you have to
activate the window to create a link between it and the METAR/MET
Users Guide ______________________________________________________________________
258 __________________________________________________________________M010027EN-F
REPORT Manager application. You have to do this also after a system
restart.
To activate the Manual Observations window, do the following:
1. Open the Actuals application and select the Manual Observations
option from the Actuals menu. The Manual Observations
window opens.
2. In the Manual Observations window, click the Update button.
3. Open the METAR/MET REPORT Manager application.
4. From the Present Weather list box, select the ManObs option.
5. Click the Apply button. The link is created and valid from the next
report.
Defining METAR/SPECI Values as ManObs
After you have activated the Manual Observations window you have
to use the METAR/MET REPORT Manager application for defining
the values as ManObs.
To define a METAR/MET REPORT value as ManObs, do the
following:
1. Click the METAR/MET REPORT Manager button on the
Application Toolbar. The METAR/MET REPORT Manager
window is displayed.
2. Select the list box of the weather parameter group that you want to
define as ManObs.
3. Select the ManObs or ManObsRwyRep option from the list. If
the option is not available, see section Activating the Manual
Observations Window on page 257.
4. Click Apply. The changes you made are valid in the next report.
For details on which fields on the METAR/MET REPORT template
are affected by the selection, see Table 157 on page 309.
NOTE
For the Clouds, Remark, Recent Weather Codes, and Regional
QNH fields, select ManObs from the Present Weather list box.
Chapter 17 _________________________________________________________________ Actuals
VAISALA______________________________________________________________________ 259
Entering Manual Observations
To enter manual observations in the Manual Observations window, do
the following:
1. Activate the Manual Observations window. For instructions, see
section Activating the Manual Observations Window on page 257.
2. Define the values in question as ManObs in the METAR/MET
REPORT Manager application. For instructions, see section
Defining METAR/SPECI Values as ManObs on page 258.
3. Start the Actuals application.
4. From the Actuals menu, select Manual Observations. The
Manual Observations window appears.
5. Enter your manual observations as appropriate.
6. Click the Update button. The manual observations you entered are
saved and will be displayed in the next METAR/MET REPORT
template, and/or in other applications.
7. Update the values whenever needed and click the Update button
after each change.
The system distributes the manual observations to METAR/
MET REPORT and SYNOP, and/or Weather View applications,
depending on the system configuration.
An alternative way of entering manual observations is to enter them
directly in the METAR/MET REPORT template. However, you will
have to enter the values in every METAR even if the values remain the
same. When using the Manual Observations window you only have to
update the values if they need to be changed. The values entered and
updated will not be deleted when you close the Manual Observations
window.
manual values for Pressure and Prevailing Visibility are entered in the
Users Guide ______________________________________________________________________
260 __________________________________________________________________M010027EN-F
Troubleshooting Actuals
The following table lists some problem situations that might occur
when you are using Actuals and some typical solutions to them.
Table 137 Troubleshooting Actuals
There are slashes (////) in the data
fields of the Actuals windows.
Communication line may be
broken or there may be sensor
problems.
There are no values and no
slashes in the windows. All fields
are empty.
There may be problems with the
CDU.
The text N/A is in the Actuals
windows instead of the normal
measurement site code.
The sensor is in Manual or
Backup mode due to sensor
problems or maintenance.
If the problem has been fixed,
change sensor mode to
Automatic.
The values you entered in the
Manual Observations window
are not displayed in the METAR/
updated after making changes.
Click the Update button every
time you change the values in
window.
defined as ManObs in the
METAR/MET REPORT
In the METAR/MET REPORT
Manager application, select
the ManObs option in the
appropriate list box (or in the
Present Weather list box for
RMK, Reg QNH, and Rewx).
The Manual Observations
window has not been activated
when used for the first time.
Activate the Manual
Observations window, for
instructions see section
Activating the Manual
Observations Window on page
257.
Values keep coming to METAR/
MET REPORT template from
even though you have not
entered any values in the window
recently.
The values entered and updated
properly in the Manual
Observations window will be
saved and distributed to
METAR/MET REPORT
template even after you close
window.
Define the values other than
ManObs in the METAR/MET
REPORT Manager
application.
Chapter 18 _____________________________________________________ Data Source Manager
VAISALA______________________________________________________________________ 261
CHAPTER 18
DATA SOURCE MANAGER
This chapter describes how to select the active data source and enter
values manually for pressure and prevailing visibility data.
Introduction to Data Source Manager
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.
Data Source Manager User Interface
The user interface consists of the Data Source Manager window and
the PV Group Manager window.
Users Guide ______________________________________________________________________
262 __________________________________________________________________M010027EN-F
Data Source Manager Window
The Data Source Manager window consists of the Pressure tab, the
Prevailing Visibility tab, and the Change window. See Figure 67 on
page 262.
0411-083
Figure 67 Data Source Manager Window, Pressure Tab
0411-048
Figure 68 Data Source Manager, Prevailing Visibility Tab
VAISALA______________________________________________________________________ 263
The following sections briefly describe the elements of these windows.
For instructions on using the application, see section Operating the Data
Source Manager Application on page 271.
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.
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.
For an example, see Figure 69 on page 263.
0407-003
Figure 69 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. For an
example, see Figure 70 on page 264.
Users Guide ______________________________________________________________________
264 __________________________________________________________________M010027EN-F
0407-004
Figure 70 Data Source Manager Window, Active Sensor
Changed
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. For details, see Table 138 on page 264.
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. For details, see Table 138 on page 264.
Columns
The columns and colors common to both tabs of the Data Source
Manager window are described in Table 138 on page 264.
Table 138 Data Source Manager Window Columns and Colors
Column Description
Active Shows the state of the active data source. See section
Active Data Source on page 263. The icons are explained
in the following list:
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.
VAISALA______________________________________________________________________ 265
On the Pressure tab, the middle columns contain the parameter values
for pressure. The typical columns are described in Table 139 on page
266.
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
section Active Data Source on page 263.
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.
NOTE
Missing and invalid values are indicated with one or more / signs in
the value columns.
Table 138 Data Source Manager Window Columns and Colors
(Continued)
Column Description
Users Guide ______________________________________________________________________
266 __________________________________________________________________M010027EN-F
On the Prevailing Visibility tab, the middle columns contain the
parameter values for visibility. The typical columns are described in
Table 139 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.
Table 140 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
VAISALA______________________________________________________________________ 267
Buttons
The buttons in the Data Source Manager window are described in
Table 141 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. See section
Active Data Source on page 263.
Change Opens the Change window for entering manual raw data
values. The validated values will be 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. For more information, see section PV
Group Manager Window on page 268.
Close Closes Data Source Manager. The settings made in the
application will be saved and remain valid until the
application is opened again and new changes made.
Users Guide ______________________________________________________________________
268 __________________________________________________________________M010027EN-F
PV Group Manager Window
The PV Group Manager window is displayed when you click the
Group Manager button on the Prevailing Visibility tab.
0411-082
Figure 71 PV Group Manager Window
VAISALA______________________________________________________________________ 269
Table 142 PV Group Manager Window Elements
Element Description
Groups frame
Displays the configured prevailing visibility
sensor groups and allows you to edit existing
groups and add new groups.
Add button Opens the Add Prevailing Visibility Group
window for adding a new group.
Edit button Opens the Edit Prevailing Visibility Group
window for renaming the selected group.
Remove button Removes the selected group.
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.
Available sensors list Displays the sensors available for selection
(sensor name and location).
Selected sensors list Displays the sensors selected for the group
(sensor name, location, and weight value of the
sensor in this particular group).
Add arrow button Moves the selected sensor(s) to the group.
Remove arrow button Removes the selected sensor(s) from the group.
Sensor frame (sensor
name)
Displays the details of the selected sensor.
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. For more information, see section
Sensor Weight Value on page 270.
Validity limit button Opens the Prevailing Visibility Validity Limit
window for setting the validity limit for prevailing
visibility. The default value is 60 %. For more
information, see section Validity Limit on page
270.
OK button Saves the changes and closes the window.
Apply button Saves the changes without closing the window.
Cancel button Closes the window without saving the changes.
Users Guide ______________________________________________________________________
270 __________________________________________________________________M010027EN-F
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, 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.
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.
VAISALA______________________________________________________________________ 271
Operating the Data Source Manager Application
Starting and Exiting Data Source
Manager
You can start Data Source Manager from the buttons in the Actuals
application. To directly open the Pressure tab, click the button. To
open the Prevailing Visibility tab, click the button.
To exit Data Source Manager, click the Close button. The settings you
made in the application will be saved and remain valid until you open
the application again and make new changes.
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.
For more information, see section Active Data Source on page 263.
To change the active data source, do the following:
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 the Activate button for the data source. Confirm the selection
by selecting Yes in the message window.
0406-026
Figure 72 Activate Data Source 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
Users Guide ______________________________________________________________________
272 __________________________________________________________________M010027EN-F
invalid, or the source is disabled (for pressure values) and no data
is produced from the source.
0406-026
Figure 73 Activate Data Source Window, Warning
Using Manual Values
When all sensors are out of order or being maintained, manual values
can be entered using Data Source Manager. Do the following:
2. To enter or edit the manual values, click the Change button on the
row for the manual values.
3. In the Change window, enter the raw values in appropriate fields
and click the OK button. 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 will contain the text "Invalid".
5. If the manual data source is not active yet, click the Activate button
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.
CAUTION
If you try to activate a data source that is missing, invalid, or disabled,
the system shows a warning message. See Figure 73 on page 272.
Select No and enable the data source first, if possible, or activate
another data source.
VAISALA______________________________________________________________________ 273
7. When the manual values are no longer needed, remember to select
one of the other sources as the active source. See section Changing
the Active Data Source on page 271.
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.
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. Do the following:
2. If the source that you want to disable is active, activate first another
data source by clicking the Activate button of a valid data source.
See section Changing the Active Data Source on page 271.
3. Click the Disable button for the sensor. Confirm the selection by
selecting Yes in the message window.
0406-027
Figure 74 Disable Data Source 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. See Figure 75 on page 274. Select No, and
activate first another data source, if possible.
Users Guide ______________________________________________________________________
274 __________________________________________________________________M010027EN-F
0407-006
Figure 75 Disable Data Source Window, Warning
4. When the sensor has been fixed and its data can be used again,
enable it by clicking the Enable button on its row. After that, if you
want the system to use it as the active data source, activate the
source by clicking the Activate button. See Changing the Active
Data Source on page 271.
Managing Prevailing Visibility
Groups
You can manage the groups available for selecting as sources for
prevailing visibility in the PV Group Manager window.
Adding New Prevailing Visibility Groups
To create a new prevailing visibility sensor group, do the following:
1. In the Data Source Manager window, select the Prevailing
Visibility tab.
2. Click the Group Manager button. The PV Group Manager
3. In the Prevailing Visibility Groups frame, click the Add button.
In the Add Prevailing Visibility Group window, enter the name
of the group that you will create and click the OK button.
4. 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. The weight
values of the sensors in this particular group are displayed next to
the sensor names in the Selected sensors list.
VAISALA______________________________________________________________________ 275
5. 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. For more
information on weight value, see section Sensor Weight Value on
page 270.
6. To save the created group, click the Apply button.
7. If you want to create other groups, continue from step 3.
Editing Prevailing Visibility Groups
To edit existing prevailing visibility groups, do the following:
1. In the Data Source Manager window, select the Prevailing
Visibility tab.
2. Click the Group Manager button. The PV Group Manager
3. In the Prevailing Visibility Groups frame:
- You can rename a selected group by clicking the Edit button,
and in the Edit Prevailing Visibility Group Name window,
entering a new name and clicking OK.
- You can remove a selected group altogether by clicking the
Remove button.
4. In the Prevailing Visibility Group frame:
- You can select more sensors to the selected group by selecting
a sensor from the Available sensors list and clicking the Add
arrow button. The sensor will be displayed in the Selected
sensors list.
- You can remove sensors from the selected group by selecting
the sensor in the Selected sensors list and clicking 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
NOTE
After making changes, always click the Apply button, or the OK
button, which will also close the window.
Users Guide ______________________________________________________________________
276 __________________________________________________________________M010027EN-F
entering a new value in the Weight field. For more information on
sensor weight, see section Sensor Weight Value on page 270.
6. To save the changes, click the Apply button.
Editing Validity Limit
To change the validity limit for all groups, do the following:
1. Open the PV Group Manager window.
2. Click the Validity limit button at the bottom of the window.
3. In the Prevailing Visibility Validity Limit window, enter the new
value in the Validity Limit field. For more information on validity
limit, see section Validity Limit on page 270.
4. Click the OK or Apply button in the PV Group Manager
window.
Troubleshooting Data Source Manager
when using the Data Source Manager and some typical solutions to
them.
VAISALA______________________________________________________________________ 277
Table 143 Troubleshooting Data Source Manager
Red icon (E) is displayed in the
STATUS column.
Data is missing or invalid due to
problems with the sensors or
communication, or the manually
entered value is not valid.
Check the sensor or sensor
communication. If the data
source is active, activate
another data source. If you
are using manual values,
enter a valid value.
The text "Missing" or "Invalid" is
displayed in the INFO column.
See above. See above.
Data is missing from the value
fields.
Red icon (E) is displayed in the
ACTIVE column.
The source is active and used by
the system, but no data is
displayed because the data is
missing or invalid, or the source
is disabled.
See above, or enable the data
source, if possible, or activate
another source that is not
disabled.
Yellow icon (W) is displayed in the
ACTIVE column.
In systems where a default data
source has been defined in
system configuration: the source
is active, but it is not the default
source. Data is produced
normally.
This is to remind you that the
default source is not used.
When the default source can
be used again, enable and
activate it.
Yellow icon (W) is displayed in the
STATUS column.
(Only for pressure values) The
source is disabled and its data is
not used in the system.
If the source is active, enable
the source or activate another
source. If the source is not
active, for example, because
the sensor is being repaired
or calibrated, remember to
enable the sensor when
finished with repair or
calibration.
The text "Disabled" is displayed in
the INFO column.
In the PV Group Manager window,
when selecting sensors from the
Available sensors list for the first
time, the list is empty, or some
sensors are missing.
There is a problem with the
configuration.
Contact Vaisala HelpDesk.
The displays are not updated. There is a problem with the
connection to the CDU.
Check the connections.
There is a problem with the
configuration.
Contact Vaisala HelpDesk.
Users Guide ______________________________________________________________________
278 __________________________________________________________________M010027EN-F
Chapter 19 ___________________________________________________________ History Monitor
VAISALA______________________________________________________________________ 279
CHAPTER 19
HISTORY MONITOR
This chapter describes how to retrieve and view past measurement data
from the database in table or graphical trend format.
Introduction to History Monitor
The History Monitor application is used for retrieving past
measurement and system event 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. They
can create views, for example, for certain parameters for each runway.
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.
The main window is displayed blank when the application is started, see
Users Guide ______________________________________________________________________
280 __________________________________________________________________M010027EN-F
0411-073
Figure 76 Blank History Monitor Main Window
Typically, your first task is to create the views. There can be views, for
example, for each runway or for a set of weather parameters, events, or
reports. The typical types for the views are the following:
- Table View with the parameter data in text format in columns
- Trend View with the parameter data in graph format
- Event View with the Event Monitor events in table format
For an example with created views, see Figure 77 on page 281. The
created views can be saved and later opened for viewing.
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.
VAISALA______________________________________________________________________ 281
0411-046
Figure 77 History Monitor with Opened Views
1 = Menu bar
2 = Toolbar
3 = Trend View window
4 = Table View window
5 = Event View window
Users Guide ______________________________________________________________________
282 __________________________________________________________________M010027EN-F
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. The name of the Trend View is displayed in
the window title bar after the view has been saved. For an example, see
The data items that the view contains are selected when creating the
view, but they can also be edited during viewing by selecting Data Item
Selection from the Edit menu. All data items of a Trend View have to
have the same unit. At the top of the view, the names of the data items
are displayed together with the trend line colors for each item. There are
also check boxes with which you can select whether the selected items
are displayed or not.
The graph can be zoomed in and out and its settings can be adjusted by
selecting Graph Properties from the Edit menu. The display period
and data resolution can be adjusted by selecting Options from the Tools
menu. The graph may be divided into several pages so that only part of
the graph is visible at a time. The default setting is 60 data points (one
hour) per page. You can move from page to another using the
navigation buttons in the toolbar. For more information on using the
view, see section Operating History Monitor on page 292.
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. The name of the view is displayed at the window title bar after
the view has been saved. For an example, see Figure 77 on page 281.
The contents are selected when creating the view, but they can also be
edited during viewing by selecting Data Item Selection from the Edit
menu. The display period and data resolution can be adjusted by
selecting Options from the Tools menu. For more information on using
the view, see section Operating History Monitor on page 292.
VAISALA______________________________________________________________________ 283
Event View Window
The Event View windows contain the timestamp and the events as seen
in the Event Monitor application. The name of the Event View is
displayed at the window title bar after the view has been saved. For an
example, see Figure 77 on page 281.
The contents are selected when creating the view, but they can also be
edited during viewing by selecting Data Item Selection from the Edit
menu. For more information on using the view, see section Operating
History Monitor on page 292.
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.
0411-076
Figure 78 New Window
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. See Figure 79 on page 284.
Users Guide ______________________________________________________________________
284 __________________________________________________________________M010027EN-F
0411-077
Figure 79 Open View Window
Data Item Selection Window
After you have opened an empty new view frame, or you want to edit a
saved view, you can select which data items (parameters) are displayed
in the view. The Data Item Selection window contains the configured
data items available for selecting. The window is displayed when you
select Data Item Selection from the Edit menu.
0411-078
Figure 80 Data Item Selection Window
VAISALA______________________________________________________________________ 285
The elements of the Data Item Selection window are displayed in
Options Window
The Options window contains the display period and data resolution
settings for the view that is currently active. The selected options are
saved for each view separately. The window is displayed when you
select Tools - Options. See Figure 81 on page 285.
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.
0411-074
Figure 81 Options Window
Table 144 Data Item Selection Window Elements
Element Description
Available data
items
Shows the pre-configured available data items that can be
selected to be displayed in the views.
Selected data
items
Shows the data items that have been selected to be
displayed in the view.
Moves the selected items on the left to the Selected data
items list on the right.
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.
Cancel Closes the window without saving the changes.
Users Guide ______________________________________________________________________
286 __________________________________________________________________M010027EN-F
The elements of the Options window are displayed in Table 145 on
page 286.
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.
Table 145 Options Window Elements
Element Description
Sliding When this option is selected, the data will be displayed
from the present moment backwards for the amount of
hours selected from the Hours list.
Hours When the Sliding option is selected, the period for which
the data is shown from this moment backwards: select the
hours from the list or enter another period in hours.
Fixed When this option is selected, the data will be displayed for
the period selected from the Start and End lists.
Start When the Fixed option is selected, the start date and time
of the period: select the date and time from the list. Clicking
the arrow button opens a calendar for selecting the date.
End When the Fixed option is selected, the end date and time
of the period: select the date and time from the list. Clicking
the arrow button opens a calendar for selecting the date.
Data
resolution
Select or enter the interval at which the data is shown, in
minutes.
OK Applies the changed options.
Cancel Closes the window without saving the changes.
VAISALA______________________________________________________________________ 287
Graph Properties Window
In the Graph Properties window you can change several graph
properties in the Trend View graphs, for example, the axis and
background color. The window is displayed when you select Edit -
Graph Properties and a Trend View is active, see Figure 82 on page
287.
0411-051
Figure 82 Graph Properties Window
For instructions on changing some of the properties, see section Editing
Graphs in Trend Views on page 297.
Users Guide ______________________________________________________________________
288 __________________________________________________________________M010027EN-F
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 you select Tools - Extremes and a Trend View is
active, see Figure 83 on page 288.
0501-053
Figure 83 Extremes Window
The elements of the window are described in Table 146 on page 288.
Table 146 Extremes Window Elements
Element Description
Period - Begin
/ End
Shows the begin 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
list
Shows the parameters included in the active Trend View
and allows you to select the item whose extreme values
you want to see.
Results - Min Shows the minimum value of the selected item during the
period and the time when the value occurred.
Results - Max Shows the maximum value of the selected item during the
period and the time when the value occurred.
Results - Avg Shows the average value of the selected item during the
period.
Results - Tend Shows the tendency value of the selected item during the
period.
OK Closes the window.
VAISALA______________________________________________________________________ 289
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 147 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.
Close Closes the active view window.
Save As Opens the Save View As window for saving the created
view for further viewing.
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.
Exit Exits the History Monitor application.
Table 148 History Monitor: Edit Menu
Command Description
Data Item
Selection
Opens the Data Item Selection window for selecting which
parameters the view being created or the saved view will
contain.
Graph
Properties
Opens the Graph Properties window for editing graph
settings in Trend Views (only available when a Trend View
is active).
Table 149 History Monitor: View Menu
Command Description
Refresh Immediately checks if 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.
Users Guide ______________________________________________________________________
290 __________________________________________________________________M010027EN-F
Toolbar Shows/Hides the History Monitor toolbar
Status bar Shows/Hides the History Monitor status bar
Auto Refresh When selected, the data is refreshed automatically at the
preconfigured interval, typically every 60 seconds.
Table 150 History Monitor: Tools Menu
Command Description
Options Opens the Options window for selecting the display period
and the data resolution for the active view.
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).
Table 151 History Monitor: Window Menu
Command Description
Cascade Arranges windows one on top of the other
Tile Arranges windows in vertical rows
Close All Closes all open windows
Table 152 History Monitor: Help Menu
Command Description
About History
Monitor
Table 149 History Monitor: View Menu (Continued)
Command Description
VAISALA______________________________________________________________________ 291
Toolbar
The toolbar is the fastest way of selecting the most frequently needed
functions. A typical toolbar contains the buttons listed in Table 153 on
page 291.
Table 153 History Monitor Toolbar Buttons
New opens the New window for selecting whether to create a
new Table View or Trend View window.
Open opens the Open window for opening the views saved on
the local computer using the user name you are logged in.
Opens the Save View As window for saving the created view
for further viewing
Refresh immediately checks if data has changed and updates
the data in all open views with the changed data.
First moves to the beginning of the 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 the data in the view.
Users Guide ______________________________________________________________________
292 __________________________________________________________________M010027EN-F
Operating History Monitor
Starting and Exiting History Monitor
To start the History Monitor application, click the History Monitor
button on the Application Toolbar.
To exit the application, select Exit from the File menu.
Creating a New View
To create a new view, do the following:
1. In the History Monitor main window, select New Frame from the
File menu, or click the New icon on the toolbar. The New
0411-076
Figure 84 The New Window
2. In the New window, select the view type that you want to create
and click OK. An empty view frame is displayed.
VAISALA______________________________________________________________________ 293
0411-049
Figure 85 Blank Table View
3. To select data items to the view, select Data Item Selection from
the Edit menu of the main window. The Data Item Selection
window displays the configured available data items.
0411-078
Figure 86 Data Items Window
4. Select the data items from the Available Data Items list and click
the arrow button. The selected items are moved to the
Selected Data Items list. Click OK.
5. The selected data items are displayed in the view, either as columns
in Table View and Event View, or graphs in Trend View. See
Figure 77 on page 281. The view does not yet have a name in the
title bar of the window.
Users Guide ______________________________________________________________________
294 __________________________________________________________________M010027EN-F
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.
0411-052
Figure 87 Save View As Window
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,
do the following:
1. First, select which type of a saved view you want to open:
- Select New Frame from the File menu, or click the New
icon on the toolbar. The New window is displayed.
- In the New window, select the view type that you want to open
and click OK. An empty view frame is displayed.
2. Select Open from the File menu, 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.
VAISALA______________________________________________________________________ 295
0411-077
Figure 88 Open View Window
3. Select the view 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.
Changing Displayed Data Items
To change which parameters are displayed in the active view, do the
following:
1. Select Edit - Data Item Selection. The Data Item Selection
window is displayed. See Figure 86 on page 293.
2. Using the arrow buttons, add or remove the items selected and
click OK.
Users Guide ______________________________________________________________________
296 __________________________________________________________________M010027EN-F
Refreshing Data in Views
By default, the data in the views is not refreshed automatically.
However, you can refresh the data manually or select to refresh the data
automatically.
To refresh the data immediately, do the following:
1. Select Refresh from the View menu, or click the Refresh
button.
2. The view is immediately updated with any changed data.
To select automatic refreshing, do the following:
1. Select Auto Refresh from the View menu. 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.
Changing Display Period and
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.
To change the display period, do the following:
1. Select Options from the Tools menu. The Options window is
displayed. See Figure 81 on page 285. The window shows the
settings for the view that is currently active.
2. If you want to display the data a certain period backwards from the
present time, select the Sliding option button. 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.
3. If you want to display data from a fixed period of time, select the
Fixed option. Then click the dates and times in the Start and End
VAISALA______________________________________________________________________ 297
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 the OK button. The settings are used the next time the data
is refreshed. The settings are saved for the active view.
To change the data resolution settings, do the following:
1. Select Options from the Tools menu. The Options window is
displayed. See Figure 81 on page 285. 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 the OK button. The settings are used the next time the data
is refreshed. The settings are saved for the active view.
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, see Figure 82 on page 287. The window is
displayed when you select Edit - Graph Properties.
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
NOTE
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.
NOTE
The Graph Properties window provides also advanced editing
features that may not necessarily be applied to current data.
Users Guide ______________________________________________________________________
298 __________________________________________________________________M010027EN-F
Changing the Scale
1. Select Graph Properties from the Edit menu. The Graph
Properties window is displayed.
2. Select Chart - Axis - Scales.
3. On 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.
5. Click Close.
Changing Background and Trend Line Color
To change the background color of a Trend View, do the following:
2. Select Chart - Panel - Background.
3. On the Background tab, click the Color button and select the new
color for background.
4. Click Close.
To change the color of the trend line, the graph, do the following:
2. Select the Series tab.
3. Select the trend line that you want to edit from the list, and click the
Color button to change the color.
4. Click Close.
NOTE
Make the selections separately for the left and right axis.
VAISALA______________________________________________________________________ 299
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 will spread over multiple pages. To change this
setting, do the following:
2. Select the Chart - Paging.
3. On 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.
4. To show the page numbers, select the Show Page Numbers check
box.
5. Click Close.
Hiding/Showing Graphs
To hide a graph in a Trend View, do the following:
- 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.
To show the graph again, select the check box again.
Users Guide ______________________________________________________________________
300 __________________________________________________________________M010027EN-F
Moving and Zooming in Trend
Views
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.
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.
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.
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
Last button.
To move to the beginning, press CTRL+Home, or click the First
button.
To move upwards or downwards in the view, press the PageUp or
PageDown keys in the keyboard, or click the Previous and
VAISALA______________________________________________________________________ 301
Next 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.
Viewing Several Windows at the
Same Time
To view several views at the same time, do the following:
1. Open 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 as needed.
Users Guide ______________________________________________________________________
302 __________________________________________________________________M010027EN-F
Troubleshooting History Monitor
when using the application and some typical solutions to them.
Table 154 Troubleshooting History Monitor
The New icon and menu item is
not available.
The system has just been
started and is still reading the
parameters.
Wait for a while until the button
becomes active.
The Open window does not
contain the view that you want to
open.
The window shows only the type
of views selected in the New
window, and views created and
saved in the local computer
using the user name you have
logged on with.
Select another view type in the
New window, or log in with a
different user name.
When trying to open a new view
the following message is
displayed: "Server rejected the
connection." There is no data
source displayed in the status
bar.
There are too many database
users, the maximum amount of
users is typically five.
Wait until the users quit their
sessions and try again.
The message "Communication
Link Failure" or "Operation timed
out" is displayed, and the
parameter values are replaced
with the text "ERR" in Table
Views.
The data is not refreshed, for
example, because of connection
problems or temporary capacity
problems with the database.
Close the History Monitor
application and after the
database is available again,
restart it.
Some of the parameter columns
are not visible.
The columns may have been
hidden because they have been
dragged over each other.
To see all columns, press
Ctrl+W.
Chapter 20 ___________________________________________________ Runway in Use Manager
VAISALA______________________________________________________________________ 303
CHAPTER 20
RUNWAY IN USE MANAGER
This chapter describes how to manually set which runways are in use,
and the runway landing direction.
Introduction to Runway in Use Manager
The Runway in Use Manager application 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. Depending on the airport, the
changes made in the application affect the Weather View displays, and
if configured, the reporting of the MET REPORT reports.
Runway in Use Manager User Interface
The user interface consists of the Runway in Use Manager window.
See Figure 89 on page 304.
Users Guide ______________________________________________________________________
304 __________________________________________________________________M010027EN-F
0406-015
Figure 89 Runway in Use Manager Window
There is a frame for each runway, for example, 04L/22R. In the example
above, runway 04L is selected to be used for landing, and runway 33 for
take-off. Other runways are not in use.
The elements of the window are described in Table 155 on page 304.
Table 155 Runway in Use Manager Window Elements
Element Description
Manual check
box
Select the check box to change the use of the runway
manually. Otherwise, the default value is used.
Lists Select the correct option for each runway end: Landing/
Take-off/ Not in use/ Closed or Landing/Take-off
Apply Applies the changes and updates other applications to
correspond the selections.
Reset Ignores the changes you have made.
Close Closes the window.
Chapter 20 ___________________________________________________ Runway in Use Manager
VAISALA______________________________________________________________________ 305
Operating the Runway in Use Manager
Application
Starting and Exiting Runway in Use
Manager
To start Runway in Use Manager, click the Runway in Use button
on the Application Toolbar.
To exit and save the changes, click the Apply button(s) and the Close
button.
To exit without saving the changes, click the Reset button and then the
Close button.
Setting Runway in Use Manually
To manually set which runways are used and the runway landing
direction, do the following:
1. Open the Runway in Use Manager application.
2. Select the Manual check box for the runways as needed.
3. 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 has to have the selection "Not in use". See the caution
below.
4. For each changed runway, click the Apply button.
5. Click the Close button to close the window.
For MET REPORTs, the runway landing direction follows the runway
landing direction set by the ATC using the Runway in Use Manager
application. However, if no valid data is available from the ATC, the
observer can set the reporting order for MET REPORTs in the METAR/
CAUTION
If you select a cross-operation, there is a warning displayed at the
bottom of the window. However, the system lets you make these
selections in case they are needed for special situations.
Users Guide ______________________________________________________________________
306 __________________________________________________________________M010027EN-F
MET REPORT Manager application. The selection overrides the
selection made in Runway in Use Manager.
Troubleshooting Runway in Use Manager
when using the Runway in Use Manager application and some typical
solutions to them.
Table 156 Troubleshooting Runway in Use Manager
There is a warning text at the
bottom of the window, for example,
"Warning: RWY 04L/22R cross-
operation!"
Warns you about a non-
standard selection you have
made.
Make sure the selection is valid
at the current situation at the
airport. Normally, one end of the
runway should have the
selection "Not in use" or
"Closed", or both ends should
have the text "Closed".
Chapter 21 _____________________________________________ METAR/MET REPORT Manager
VAISALA______________________________________________________________________ 307
CHAPTER 21
METAR/MET REPORT MANAGER
This chapter contains instructions for defining which measurement sites
or other sources provide the automatic data to the METAR/
Introduction to METAR/MET REPORT Manager
The METAR/MET REPORT Manager application is used for changing
the measurement sites or other sources that provide the automatic data
to the METAR/MET REPORT template. This might be necessary, for
example, in sensor problem situations or when the runway in use is
changed.
Some data can be defined as manual which means that the
corresponding METAR/MET REPORT template fields will not be
automatically filled in by the system. The values must be entered
manually in the METAR/MET REPORT template.
Some values can be defined as ManObs which means that the values
have to be entered in the Manual Observations window in the Actuals
application.
At some airports the METAR/MET REPORT Manager is primarily a
tool for maintenance personnel. Check the airport-specific practices.
Users Guide ______________________________________________________________________
308 __________________________________________________________________M010027EN-F
METAR/MET REPORT Manager User Interface
The METAR/MET REPORT Manager user interface consists of the
METAR/MET REPORT Manager window. A typical window is
METAR/MET REPORT Manager on page 312.
0501-005
Figure 90 METAR/MET REPORT Manager Window
Measurement Locations for METAR/
MET REPORT Template
The list boxes in the METAR/MET REPORT Manager are used for
defining which measurement sites or other sources provide the data to
METAR/MET REPORT template. Each list box refers to one value or
a group of values in the METAR/MET REPORT template. For
example, the Pressure list box refers to pressure-related values.
VAISALA______________________________________________________________________ 309
Most of the selections affect only METAR/SPECI values. Pressure,
Humidity and temperature, and Present weather affect also
MET REPORT/SPECIAL values.
Table 157 on page 309 lists the fields in METAR/MET REPORT
Manager and their corresponding fields in the METAR/
MET REPORT template. Depending on the configuration of the
system, also other options may be available.
The Present Weather list box is also used for creating a link between
the METAR/MET REPORT Manager and the Manual Observations
window in the Actuals application so that the ManObs options can be
selected. See section Defining METAR/MET REPORT Values as
ManObs for the First Time on page 314. The Present Weather list box
is also used for selecting the ManObs option for the Clouds, Remark,
REWX (Recent Weather Codes), and Reg QNH fields.
The list box options are either measurement sites or alternative ways of
providing the data. Table 158 on page 310 explains some typical list box
options in the METAR/MET REPORT Manager. However, depending
Table 157 METAR/MET REPORT Manager List Boxes
List Box METAR/MET REPORT
Template Fields
Report Type Affected
Wind Wind METAR/SPECI
Pressure Pressure (QNH) METAR/SPECI and
MET REPORT/SPECIAL
Humidity and
temperature
Humidity and
temperature (T, DP)
METAR/SPECI and
MET REPORT/SPECIAL
RVR 1 RVR METAR/SPECI
RVR 2 RVR 2 METAR/SPECI
RWY State RUNWAY STATE METAR/SPECI
Prevailing vis Prevailing vis METAR/SPECI
Minimum vis MInimum vis METAR/SPECI
Present weather Present weather and
recent weather (REWX)
METAR/SPECI and
MET REPORT/SPECIAL
Cloud Clouds fields METAR/SPECI
Users Guide ______________________________________________________________________
310 __________________________________________________________________M010027EN-F
on the system configuration, your options may differ from the ones
listed in the table.
Initially, the ManObs option is not displayed. To view the option, a link
has to be created between the applications by activating the Present
Weather list box and the Manual Observations window. See section
Defining METAR/MET REPORT Values as ManObs for the First Time
on page 314.
The values for the parameter entered in the Manual Observations
window are transferred to the METAR/MET REPORT template if the
option ManObs or ManObsRwyRep is selected in the list box of the
parameter.
Table 158 Typical METAR/MET REPORT Manager List Box
Options
List Box Option Explanation
Site or runway
number, for
example, 02R
The values come to the METAR/MET REPORT
template from the specified sensor site.
- manual The values must be entered manually in the METAR/
Active, or other pre-
configured text
template from the link or list defined as the active
source in the Data Source Manager.
All, or other pre-
configured text
template from the preconfigured link or list, depending
on the configuration and the selection in Data Source
Manager.
ManObs The values come to the METAR/MET REPORT
template from the Manual Observations window in
the Actuals application.
ManObsRwyRep The values come to the METAR/MET REPORT
template from the Manual Observations window in
the Actuals application (Rwy State field).
N/A The system cannot detect the measurement site of a
parameter because the sensor in question is set to
Manual mode in the Actuals application. The values
have to entered manually in an Actuals application
window, for example, in the Wind Actuals window.
VAISALA______________________________________________________________________ 311
The Runway Landing Directions and Reporting Orders for Local
Reports frame contains selections for sites used in MET REPORT/
SPECIAL reports in METAR/MET REPORT template. The
following is defined in this frame:
- Runway landing direction. This selection also affects the reporting
order of the sensors/sites along the runway if there are more than
one sites for the runway.
- Runway reporting order if there are more than one runways.
Typically the runway landing direction follows the selections made in
the Runway in Use Manager application. However, if no valid selection
is available, you can change the runway landing direction for MET
REPORT/SPECIAL reports by selecting first the Manual option in the
Runway Landing Directions and Reporting Orders for Local
Reports frame.
The runway landing direction is indicated by the selected option button
next to the runway name. For example, if the runway used for landing
is 04L, the 04L option button is selected. If there are more than one sites
for the runway, the site reporting order of the site is 04L TDZ, 04L
END. See Figure 91 on page 311.
0407-026
Figure 91 Runway Landing Direction Example, 04L
If the runway is used for landing in the opposite direction, the 22R
option button is selected. If there are more than one site for the runway,
the reporting order is 22R TDZ, 22R END. See Figure 92 on page 311.
0407-027
Figure 92 Runway Landing Direction Example, 22R
The runway reporting order is indicated by the number in the list box.
For example, when "3" is selected as in Figure 92 on page 311, the
Users Guide ______________________________________________________________________
312 __________________________________________________________________M010027EN-F
runway is reported as the third runway. You can change this without
selecting the Manual option.
The order selections affect the order of appearance of sites and runways
both in the METAR/MET REPORT template (in the MET REPORT/
SPECIAL view) and in the MET REPORT/SPECIAL reports.
Operating METAR/MET REPORT Manager
Starting METAR/MET REPORT
Manager
To start METAR/MET REPORT Manager, click the METAR/MET
REPORT Manager button on the Application Toolbar or on the
METAR/MET REPORT template.
Exiting METAR/MET REPORT
Manager
To exit METAR/MET REPORT Manager, click the Exit button on the
bottom right corner of the window.
Defining Automatic Data Source
To change the automatic measurement site, or other data source, for a
group of METAR/MET REPORT template values, do the following:
Application Toolbar or on the METAR/MET REPORT template.
The METAR/MET REPORT Manager window is displayed.
2. Select the list box of the weather parameter group for which you
want to change the measurement site, for example, Pressure.
3. From the list, select one of the data sources defined in
configuration, in most cases the sensor site location. For examples,
see Table 158 on page 310.
VAISALA______________________________________________________________________ 313
5. Click Exit to close METAR/MET REPORT Manager.
Defining METAR/SPECI Values as
Manual
You can define a group of values on the METAR/MET REPORT
template as manual. This means that the system does not fill in that data
field automatically, but the observer must enter the values manually in
the METAR/MET REPORT template.
To define a group of METAR/MET REPORT template values as
manual, do the following:
Application Toolbar. The METAR/MET REPORT Manager
2. Select the list box of the weather parameter group that you want to
define as manual.
3. From the list, select the -manual option.
5. Click Exit to close METAR/MET REPORT Manager.
Users Guide ______________________________________________________________________
314 __________________________________________________________________M010027EN-F
Defining METAR/MET REPORT
Values as ManObs for the First Time
Initially, the ManObs option is not automatically available in the list
boxes. To make this option available, you have to create a link between
the Manual Observations window in the Actuals application and
METAR/MET REPORT Manager application by activating the
Present Weather field. Use the Manual Observations window in the
Actuals application to do this. You have to do this also after a system
restart.
To activate the Present Weather list box do the following:
1. Open the Actuals application and select the Manual Observations
option from the Actuals menu. The Manual Observations
2. In the Manual Observations window, click the Update button.
3. Open the METAR/MET REPORT Manager application.
4. From the Present Weather list box, select the ManObs option.
5. Click the Apply button. The link is created and valid from the next
report.
Defining METAR/SPECI Values as
ManObs
After you have activated the Manual Observations window you can
define some to be entered manually from the Manual Observations
window in the Actuals application.
To define a METAR/MET REPORT value as ManObs, do the
following:
1. In the METAR/MET REPORT Manager window, select the list
box of the weather parameter group that you want to define as
ManObs.
2. Select the ManObs or ManObsRwyRep option from the list. If
the option is not available, see section Defining METAR/MET
REPORT Values as ManObs for the First Time on page 314.
VAISALA______________________________________________________________________ 315
Defining Runway Landing Direction
for Local Reports
Typically the runway landing direction follows the selections made in
the Runway in Use Manager application. However, if no valid selection
is available, you can change the runway landing direction for MET
REPORT/SPECIAL reports by doing the following:
1. Select the Manual check box. This will override the selection
made in the Runway in Use Manager application.
2. Use the option buttons next to the runway names. For example, if
the runway used for landing is 22R, select the 22R button. If there
are more than one site on that runway, the selection automatically
defines the site reporting order on the runway to 22R TDZ, 22R
END. See Figure 93 on page 315.
0407-027
Figure 93 Selecting Runway Landing Direction
NOTE
For the Clouds, Remark, Recent Weather Codes, and Regional
QNH fields, select ManObs from the Present Weather list box.
Users Guide ______________________________________________________________________
316 __________________________________________________________________M010027EN-F
Defining Runway Reporting Order
for Local Reports
To change the runway reporting order, do the following:
- Select the order number from the list box. For example, when "3"
is selected as in Figure 92 on page 311, the runway is reported as
the third runway.
The order selections affect the order of appearance of sites and runways
both in the METAR/MET REPORT template (in the MET REPORT/
SPECIAL view) and in the MET REPORT/SPECIAL reports.
Troubleshooting METAR/MET REPORT
Manager
when using METAR/MET REPORT Manager and some typical
solutions to them.
Table 159 Troubleshooting METAR/MET REPORT Manager
The ManObs options are not
displayed in the list boxes.
The Manual Observations window
has not been activated when used
for the first time.
Activate the Manual
Observations window, for
instructions see section
Defining METAR/MET
REPORT Values as ManObs
for the First Time on page
314.
There is no list box for Recent
weather, Remarks, or Regional
QNH.
These values are linked to the
through the Present Weather list
box.
Select ManObs from the
Present Weather list box.
The location option shows N/A
even if a site has been defined
earlier.
The source site in question may have
been defined as manual in the
Actuals application.
When the manual mode is no
longer needed, switch the
sensor back to automatic in
Actuals.
Chapter 22 _________________________________________________________ Dial-Up Manager
VAISALA______________________________________________________________________ 317
CHAPTER 22
DIAL-UP MANAGER
This chapter describes how to configure and use the dial-up
communication option to send weather reports.
Introduction to Dial-up Manager
The Dial-up Manager application is a tool for configuring and using the
dial-up communication in MIDAS IV. 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.
Dial-up Manager User Interface
The Dial-up Manager user interface consists of the Dial-up Manager
window.
The Dial-up Manager window is presented in Figure 94 on page 318.
Users Guide ______________________________________________________________________
318 __________________________________________________________________M010027EN-F

Figure 94 Dial-up Manager Window
The elements in the Dial-up Manager window are described in the
following sections.
Destinations Frame
The elements of the Destinations frame of the Dial-up Manager
window are described in Table 160 on page 318.
Table 160 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.
VAISALA______________________________________________________________________ 319
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.
Messages Frame
The elements of the Messages frame of the Dial-up Manager window
are described in Table 161 on page 319.
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.
Table 161 Dial-up Manager Window Elements: Messages
Frame
Element Description
Dial-up messages enabled Enables the dial-up connection for the
selected report types.
Report types (for example,
METAR, SPECI, and TAF)
Allows you to select the report types being
sent, from a preconfigured set of reports.
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.
NOTE
The selections made in the Dial-up Manager window take effect only
after clicking the OK button.
Table 160 Dial-up Manager Window Elements: Destinations
Frame (Continued)
Element Description
Users Guide ______________________________________________________________________
320 __________________________________________________________________M010027EN-F
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.
Starting and Exiting Dial-up
Manager
To start Dial-up Manager, click the Dial-up Manager button on
the Application Toolbar.
To exit Dial-up Manager without saving the changes, click the Close
button.
To exit Dial-up Manager and save the changes, click the Apply button.
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, do the following:
1. Open the Dial-up Manager application. The Dial-up Manager
2. Check that the destination and phone numbers are correct, if
needed.
3. In the Messages frame, select the Dial-up messages enabled
check box.
4. Select the check boxes for all the report types that you want to send
with the dial-up connection. To select all types, click the Select all
button.
5. Click the OK button. The dial-up connection will be used to send
the selected weather reports to the listed destinations.
VAISALA______________________________________________________________________ 321
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
Event Monitor application.
If the sending does not succeed, an event message is displayed in the
Event Monitor application. Windows Event Viewer logs all calling
events.
Turning off Dial-up Connection
To turn off the dial-up connection, do the following:
1. Open the Dial-up Manager application by clicking the Dial-up
Manager icon in the Application Toolbar. The Dial-up
Manager window is displayed.
2. In the Messages frame, remove the check mark from the Dial-up
messages enabled check box.
3. Click the OK button. The dial-up connection will not be used to
send the reports any more.
NOTE
Before turning off the dial-up connection, make sure another method
is used for sending the weather reports.
Users Guide ______________________________________________________________________
322 __________________________________________________________________M010027EN-F
Managing Destinations and Phone
Numbers
To add a new destination, add the destination name and the phone
number(s) by doing the following:
1. Click the Add button 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 the Add button 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, check the
modem documentation.
6. Click OK.
7. The new phone number is displayed in the Phone numbers list,
when the destination is selected.
8. Add other phone numbers in the same way, if needed.
To edit a destination name, do the following:
1. Select the destination from the Destination name list.
2. Click the Edit button 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.
To edit a phone number, do the following:
2. Select the phone number to be edited from the Phone numbers list
and click the Edit button 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.
VAISALA______________________________________________________________________ 323
To delete a destination (destination name and phone numbers), do the
following:
2. Click the Remove button below the Destination name list. The
destination name and the phone numbers are removed from the list.
To delete a phone number, do the following:
2. Select the phone number to be removed from the Phone numbers
list and click the Remove button below the numbers. The selected
phone number is removed from the list.
To change the order in which the phone numbers are called to, delete
and add the numbers in the correct order.
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 Event Monitor application displays a technical event message when
sending a report fails.
Users Guide ______________________________________________________________________
324 __________________________________________________________________M010027EN-F
Troubleshooting Dial-up Manager
when using Dial-up Manager and some typical solutions to them.
Table 162 Troubleshooting Dial-up Manager
An event message in the Event
Monitor application indicates
that a message was not sent.
There is a fault in the modem,
the modem configuration, or
the connection.
Check that the modem is connected,
the power is on, and 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 end.
Contact the receiving end to check.
Appendix A ___________________________________________________________ Parameter List
VAISALA______________________________________________________________________ 325
APPENDIX A
PARAMETER LIST
This chapter lists typical parameters displayed in the windows of
Weather View and Actuals applications.
Because the parameters are defined during system configuration, your
system might include different parameters.
For the typical parameters in METAR/MET REPORT data fields, see
section METAR/MET REPORT User Interface on page 64.
Table 163 Parameters in Weather View and Actuals
Parameter Explanation Source
BASE 20-minute average of the
1st cloud layer height
Calculated from 1st
instant cloud height
BGL Background luminance
(illumination)
Measured by a
background luminance
meter, for example, LM11
CBASE See BASE
CH1, CH1 INS Instant value of 1st cloud
layer
Measured by a cloud
height meter, for
example, CT25K
CH2, CH2 INS Instant value of 2nd cloud
layer
Measured by a cloud
height meter, for
example, CT25K
CH3, CH3 INS Instant value of 3rd cloud
layer
Measured by a cloud
height meter, for
example, CT25K
DIR 10A 10-minute average of wind
direction
Calculated from instant
wind direction value
DIR 10X 10-minute maximum of
wind direction
Users Guide ______________________________________________________________________
326 __________________________________________________________________M010027EN-F
DP Dew point Calculated from TA and
RH values
GD Direction from which GS is
detected during the last 10
minutes
GS Maximum wind speed
during the last 10 minutes
Calculate from instant
PAINS Instant barometric pressure Measured by a
barometer, for example,
PTB220
P0 See PAINS
PR min Precipitation during the last
minute
Measured by a rain
gauge, for example,
RG13
QFE, OFEINS Local pressure in a height
above/below airport
elevation (normally on
touch down zone) based on
local barometric station
pressure
Calculated from PA value
QFEM 10-minute minimum of QFE Calculated from QFE
value
QFEX 10-minute maximum of
QFE
Calculated from QFE
value
QFF, QFFINS Atmospheric pressure
reduced to the mean sea
level using real atmosphere
conditions (temperature
and/or humidity and/or
vapor pressure) and local
station pressure in a
function of station height
Calculated from PAINS
value
QNH, QNHINS Atmospheric pressure
reduced to mean sea level
using ICAO atmosphere
(15 degrees) and local
station pressure in a
function of station height
Calculated from PA value
RA 24h Rain amount during 24
hours (mm or inch)
Measured by an
automated weather
station
RAIN Rain indicator (ON/OFF) Measured by a
precipitation detector, for
example, DRD11
RH, RHINS Relative humidity Measured by a humidity
probe, for example,
HMP45
Appendix A ___________________________________________________________ Parameter List
VAISALA______________________________________________________________________ 327
RVR Runway Visual Range Calculated by RVR
calculation module
RVR 1a/1 ave 1-minute average of RVR Calculated from RVR
RVR 10a/10ave 10-minute average of RVR Calculated from RVR
RVR 10m/10 min 10-minute minimum of RVR Calculated from RVR
RVR 10x/10 max 10-minute maximum of
RVR
Calculated from RVR
SPEED 10A 10-minute average of wind
speed
wind speed value
SPEED 10X 10-minute maximum of
wind speed
wind speed value
SUN Sun indicator (ON/OFF) Measured by a sunshine
duration sensor, for
example, DSU12
SUN 24 Sun duration during 24
hours
Calculated by an
automated weather
station
T, TAINS Air temperature Measured by a humidity
probe, for example,
HMP45
TA10M 10-minute minimum of air
temperature
Calculated from TA value
TA10X 10-minute maximum of air
temperature
Calculated from TA value
TD, TDINS See DP
VER VIS Instant value of vertical
visibility
Measured by a cloud
height meter, for
example, Ceilometer
VIS Instant visibility Calculated by RVR
calculation module
VIS 1A 1-minute average visibility Calculated from VIS
VIS 10A 10-minute average visibility Calculated from VIS
VIS 10M 10-minute minimum
visibility
Calculated from VIS
VIS 10X 10-minute maximum
visibility
Calculated from VIS
WD Instant wind direction Measured by a wind
sensor
Users Guide ______________________________________________________________________
328 __________________________________________________________________M010027EN-F
Appendix B ________________________________________________________________ Glossary
VAISALA______________________________________________________________________ 329
APPENDIX B
GLOSSARY
This glossary contains descriptions and definitions for unique terms and
abbreviations used in this manual.
The highlighted words in the explanation indicate that the words have
their own glossary entry.
acknowledge To click the Acknowledge button in order to inform the system that
you have seen an event message (in the Event Monitor application).
Actuals MIDAS IV application for setting sensor modes and entering weather
data manually. Mostly needed in problem situations and when
entering manual observations.
AD WRNG Optional MIDAS IV application for sending Aerodrome Warning
reports.
AFTN line Aeronautical Fixed Telecommunication Network line.
AFTN Addressee
Manager
MIDAS IV application for configuring the addressee part of the
AFTN address and which reports are sent to the addressees.
AFTN Monitor MIDAS IV application for viewing reports in the format they were
sent to the AFTN line.
AFTN Viewer MIDAS IV application for viewing messages received from the
AFTN line.
AIRMET Optional MIDAS IV application for editing and sending AIRMET
reports.
Users Guide ______________________________________________________________________
330 __________________________________________________________________M010027EN-F
alarm message An Event Monitor message with ALARM or WARNING status. A
sign of serious system problems.
Application Toolbar A toolbar that contains the buttons for most MIDAS IV applications.
It is displayed at the top of the desktop when MIDAS IV is started.
ASCII Log View MIDAS IV application for viewing data in text files.
audiovisual alarms Optional function. Sound and color signals activated in the Weather
View application when there is a predefined change in weather.
automatic data fields Data fields that the system fills in automatically in METAR/
MET REPORT template. See also manual data fields.
Automatic mode See sensor mode.
backup data status A data status shown in Weather View data fields with a light blue
background color. It indicates that data is provided by a backup
sensor. See also invalid data status, manual data status, missing
data status, normal data status, and old data status.
Backup mode See sensor mode.
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.
Bottom Line mode An alternative way of displaying Event Monitor: a single event line at
the bottom of the screen.
calculated data Weather parameters that the central data unit 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. A
MIDAS IV system can include one or two CDUs.
configuration See system configuration.
current data Weather data measured by sensors and shown in MIDAS IV
applications as contrasted with stored data.
Database Reporting
Tool
Optional MIDAS IV application for creating reports and graphs from
weather data that is saved in the optional database.
Data Source Manager A MIDAS IV application for selecting the data source for pressure
and prevailing visibility values.
data status The source and quality of weather data, indicated in Weather View
by colors. Data status in Weather View can be Backup, Invalid,
Manual, Missing, Normal, Old. In METAR/MET REPORT, data
status can be normal or missing.
VAISALA______________________________________________________________________ 331
event A system event notified by MIDAS IV with a message in Event
Monitor. An event can be, for example, a problem in the system or a
notice of a sent weather report.
Event Monitor MIDAS IV application for viewing events. See event.
Event Monitor Status
icon
An icon shown on the status area of the taskbar of the Windows
operating system. The color of the icon indicates the status of Event
Monitor messages. When there are new messages, the icon is red or
blue. When all messages are acknowledged by the user, the icon is
yellow. When there are no event messages, the icon is green.
FWS Forecaster Workstation in MIDAS IV.
GAMET MIDAS IV application for editing and sending GAMET reports.
Optional application.
History Monitor Optional MIDAS IV application for viewing archived data from the
database.
Internal event A message type in the Event Monitor application.
invalid data status A data status displayed in the weather data fields in the Weather
View application. The background color of the field is red. This status
indicates that the data is not valid due to a sensor or system problem.
See also backup data status, manual data status, missing data
status, normal data status, and old data status.
maintenance
personnel
Personnel at the airport responsible for taking care of the general
functioning of the MIDAS IV system. At some airports, observers
might take part in the maintenance tasks.
manual data fields Data fields that are filled in manually in METAR/MET REPORT,
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 Weather View 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. See also backup data
status, invalid data status, missing data status, normal data
status, and old data status.
Manual mode See sensor mode.
manual observations Weather observations entered manually in the Actuals application
when the system does not include the sensor for measuring the data.
Users Guide ______________________________________________________________________
332 __________________________________________________________________M010027EN-F
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 Event Monitor.
METAR/
MET REPORT
MIDAS IV application for editing and sending METAR/SPECI and
MET REPORT/SPECIAL reports.
METAR/MET
REPORT Manager
MIDAS IV application for defining which measurement sites
provide the values in the METAR/MET REPORT template.
missing data status A data status displayed in the weather data fields in the Weather View
application with slashes in the data fields. This status indicates that
there is no data coming from a sensor due to sensor or system
problems. See also backup data status, invalid data status, manual
data status, normal data status, and old data status.
normal data status A data status displayed in the weather data fields in the Weather View
application. The background color of the field is gray. This status
indicates that the data is valid and the system is functioning normally.
See also backup data status, invalid data status, manual data
status, missing data status, and old data status.
old data status A data status displayed in the weather data fields in the Weather View
application. The background color of the field is white. This status
indicates problems in sensor communication. See also backup data
status, invalid data status, missing data status, and normal data
status.
operation mode See sensor mode.
Operational event A message type in Event Monitor.
optional application Optional application or function in MIDAS IV that is not included in
the standard configuration.
OWS Observer Workstation in MIDAS IV.
prevailing visibility Visibility value used, for example, in METAR as defined in ICAO
Annex 3, in Chapter "Definitions". 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.
VAISALA______________________________________________________________________ 333
processed data Weather data that is measured by sensors and processed before it is
shown in MIDAS IV applications, in contrast to raw sensor data.
raw sensor data Weather data measured by sensors and shown in MIDAS IV without
significant modifications, in contrast to processed data.
RCM workstation Workstation in MIDAS IV, contains the system maintenance
applications.
Runway in Use
Manager
A MIDAS IV application for changing the runway in use information.
Runway Parameters A window in the Actuals application for entering the Background
Luminance range or value needed for calculating the RVR values.
sensor mode In Actuals, you can define the operation mode of sensor data. In
Automatic mode data is provided to the applications by primary
sensors. In Backup mode, the data is provided by a secondary sensor.
In Manual mode, data flow from sensors is interrupted and the
values entered by the user.
SIGMET Optional MIDAS IV application for editing and sending SIGMET
reports.
site The runway and location where a sensor is placed at the airport.
SNOWTAM Optional MIDAS IV application for editing and sending SNOWTAM
reports. See MIDAS IV SNOWTAM User's Guide.
standard observation
time
In METAR/MET REPORT, the moment when the system feeds
measurement data into the METAR/MET REPORT 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.
SYNOP Optional MIDAS IV application for editing and sending SYNOP
reports. See MIDAS IV SYNOP User's Guide.
system configuration The way MIDAS IV is customized during system delivery.
system delivery The installation and configuration of the MIDAS IV system by
Vaisala. During the delivery, the system is customized to meet with
the local requirements.
System Status icon An icon on the taskbar of the Windows operating system showing
the status of the MIDAS IV system. Green icon indicates that the
system is functioning normally. Red icon indicates system problems.
TAF Optional MIDAS IV application for editing and sending TAF reports.
Users Guide ______________________________________________________________________
334 __________________________________________________________________M010027EN-F
Technical event A message in the Event Monitor application indicating sensor
problems in the system.
voice alarms An optional feature in the Event Monitor application. The event
messages are read out by the speech synthesizer as they appear in the
Event Monitor window.
weather data Weather parameter values in Weather View, Actuals, and METAR/
MET REPORT applications, in contrast to system data.
weather data screen A screen in Weather View displaying weather data that is updated
several times a minute.
Weather View MIDAS IV application for viewing current weather data.
workstation A PC with a set of applications. Different workstations include
different applications and functions. See also WV, FWS, OWS, and
RCM workstation.
WS WRNG Optional MIDAS IV application for sending windshear warning
reports.
WV Weather View Workstation in MIDAS IV.
____________________________________________________________________________ Index
VAISALA______________________________________________________________________ 335
INDEX
A
Actuals, description
automatic mode 252
background luminance 246
backup mode 252
Cloud Actuals window 238
data field colors 235
introduction 233
light intensity 246
manual mode 254
Manual Observations window 242
menu bar 249
parameters 325
Pressure Actuals window 240
Pressure in Data Source Manager 240
Prevailing Visibility in Data Source
Manager 242
Runway Parameters window 246
RVR/Visibility Actuals window 241
toolbar 251
user interface 234
Weather Actuals window 239
weather data windows 234
Wind Actuals window 237
Actuals, how to
activate Manual Observations window 257
deal with problem situations 260
define METAR/MET REPORT
values as ManObs 258
enter background luminance 255
enter light intensity 256
enter manual observations in Manual
Observations window 259
enter manual observations in the
Actuals windows 254
exit application 252
start application 252
use automatic mode 252
use backup mode 252
use manual mode 254
use Manual Observations window 257
use Runway Parameters window 255
view light sensor status 257
AD WRNG (Aerodrome Warning), description
introduction 157
menu bar 160
user interface 158
AD WRNG (Aerodrome Warning), how to
cancel reports 162
deal with problems situations 163
send corrected reports 162
send normal reports 161
view sent reports 163
AFTN Addressee Manager, description
introduction 181
user interface 181
AFTN Addressee Manager, how to
add addressees 186
add new addressee groups 186
edit addressee groups 187
edit addressees 186
select message types 187
AFTN Manager window 174
AFTN Monitor, description
introduction 173
menu bar 175
message formats 177
toolbar 176
user interface 173
AFTN Monitor, how to
change sequence number 178
copy report text 178
AFTN Viewer, description
introduction 189
user interface 189
AFTN Viewer, how to
change font and color settings 200
change sound settings 200
configure message parameters 198
Users Guide ______________________________________________________________________
336 __________________________________________________________________M010027EN-F
turn beep feature on/off 199
turn pop-up feature on/off 199
view received messages 197
AIRMET, description
introduction 149
user interface 149
AIRMET, how to
cancel reports 155
Air-traffic controllers
software applications 28
Weather View, user interface 45
Weather View, using 56
Workstation types 34
Alarms
alarms groups in Weather View 58
audiovisual alarms in Weather View 53, 57
simultaneous alarms in Weather View 58
viewing stored alarms 59
voice alarms in Event Monitor 210
Application toolbar 39
Applications
end-user 28
maintenance 33
Archived files 219
Arranging windows 43
ASCII Log View, description
ASCII Log View window 220
events screen 224
history file names 228
introduction 219
menu bar 225
reports screen 223
status 222
user interface 219
weather parameter screen 221
ASCII Log View, how to
copy text from history files 232
refresh data 231
resize panes and columns 230
scroll the screens 230
view history files 228
view several windows at the same time 231
Audiovisual alarms in Weather View 53, 57
Auto Scale in graphs 60
Automated METAR 111
B
Background luminance 255
Backup data in Weather View 47
Bottom line mode (in Event Monitor) 211
C
Cloud data
in Actuals 238
in MET REPORT/SPECIAL 85
in METAR/SPECI 74
Configuration 27
Contact information 24
Contents of the manual 19
D
Data field colors in Weather View 47
Data field status in Weather View 47
Data fields in Weather View 47
Data Source Manager, description
Data Source Manager window 262
introduction 261
PV Group Manager window 268
Sensor weight 270
user interface 261
validity limit 270
Data Source Manager, how to
change active data source 271
disable/enable data source 273
manage prevailing visibility groups 274
use manual values 272
Delivery 27
Dew point data
in METAR/MET REPORT 75
Dial-up Manager, description
introduction 317
user interface 317
Dial-up Manager, how to
add destinations 322
add phone numbers 322
________________________________________________________________________________
VAISALA______________________________________________________________________ 337
delete destinations 322
delete phone numbers 322
edit destinations 322
edit phone numbers 322
manage destinations 322
select reports to be sent 320
turn off dial-up 321
turn on dial-up 320
E
Editing reports. See Reports
Event Monitor Status icon 42
Event Monitor, description
Bottom Line mode 211
Event Monitor window 203
icon colors 204
introduction 201
menu bar 206
message status 205
message type 205
SPECI limits 210
stored events 215
toolbar 207
user interface 202
voice alarm 210
Event Monitor, how to
acknowledge events 208
hide the Event Monitor button 216
monitor events 208
monitor message notifications 210
use the Voice alarm function 210
view events in Bottom Line mode 211
view selected message types 213, 214
view stored Event messages 215
Exiting applications 37
F
Feedback 23
Font in METAR/MET REPORT 121
Forecaster remarks
in MET REPORT/SPECIAL 79, 91
in METAR/SPECI 79, 91
Forecasters
AD WRNG, user interface 158
AD WRNG, using 161
AFTN Monitor, user interface 173
AFTN Monitor, using 178
AIRMET, user interface 149
AIRMET, using 153
ASCII Log View, user interface 219
ASCII Log View, using 228
GAMET, user interface 142
GAMET, using 144
METAR/MET REPORT, sending
TREND 105
METAR/MET REPORT, user interface 66
METAR/MET REPORT, using 105
SIGMET, user interface 134
SIGMET, using 136
Software applications 28
TAF, user interface 123
TAF, using 127
WS WRNG, user interface 166
WS WRNG, using 169
FWS (Forecaster) workstation 34
G
GAMET, description
introduction 141
menu bar 144
report types 144
user interface 142
GAMET, how to
send amended reports 146
send delayed reports 145
Getting help 24
Glossary of terms 329
Graph scales in Weather View 52, 59
Graphical fields in Weather View 51
H
Helpdesk 24
History files 219
Users Guide ______________________________________________________________________
338 __________________________________________________________________M010027EN-F
History Monitor, description
Data Item Selection window 284
Event View 283
Extremes window 288
Graph Properties window 287
introduction 279
menu bar 289
New window 283
Open window 283
Options window 285
Table View 282
Trend View 282
user interface 279
History Monitor, how to
change display period 296
change displayed data items 295
change resolution 296
create new views 292
edit graphs 297
move in Table Views 300
move in Trend Views 300
open saved views 294
refresh data in views 296
view several windows at the same time 301
zoom in/out in Trend Views 300
I
ICAO recommendations 24
Internal Event messages
description 205
International recommendations 24
Introduction to MIDAS IV 25
Invalid data in ASCII Log View 222
Invalid data in Weather View 47
L
License agreement 24
Light intensity 256
Light intensity sensor status 257
Local routine reports 63
Logging in 37
M
Magnetic variation 50
Maintenance applications 33
Maintenance workstation 34
Manual data in Weather View 47
Manual mode 254
Manual Observations window 242, 257
Manual revisions 22
Manual structure 21
Message Notifications description 205
MET REPORT reports 63
METAR report in Weather View 53
METAR reports 63
METAR/MET REPORT Manager, description
introduction 307
list box options 309
list boxes 308
measurement location selection 308
reporting order, local reports 311
runway landing directions, local reports 311
user interface 308
METAR/MET REPORT Manager, how to
activate ManObs option 314
define automatic measurement sites 312
define runway landing direction
for local reports 315
define runway reporting order
for local reports 316
define site reporting order 315
define values as ManObs 314
define values as manual 313
METAR/MET REPORT template 64
METAR/MET REPORT, data fields
Clouds 74, 85
CODE field 91
Dew point (DP) 75, 86
Forecaster Remark 79, 91
Other Supp. Info 90
Present weather 73, 84
Pressure (QNH, REG. QNH) 75, 86
Prevailing visibility 70
QFE 87
Recent weather (REWX) 76, 88
Remarks 79, 90
Runway state 78
RVR 72, 83
supplementary information
(MET REPORT/SPECIAL) 88
Temperature 75, 86
TREND 78
TREND field 90
Visibility 70, 83
Wind 70, 81
________________________________________________________________________________
VAISALA______________________________________________________________________ 339
Wind shear 77, 88
METAR/MET REPORT, description
automated METAR 111
automatic data fields 67
buttons 93
CODE field 91
common data fields 68
data fields 67, 80
data fields, MET REPORT/SPECIAL 80
data fields, METAR/SPECI 69
editing and sending times 97
introduction 63
manual data fields 68
menu bar 94
MET REPORT/SPECIAL view 65
METAR/SPECI view 64
Remarks field 79, 90
report identification data 67
report type 67
SPECI Limit Manager window 92
status bar 97
stored data 120
template for forecasters 66
template for observers 64
time 67
toolbar 96
TREND 78
TREND request (Forecaster) 105
TREND request (Observer) 103
user interface 64
validations 103
METAR/MET REPORT, how to
accept and send improvement SPECIs 114
build reports 99
cancel reports 106
cancel SPECI reports 115
cancel SPECIAL reports 120
change font 121
change SPECI limits 118
define automatic measurement sites 312
define values as ManObs 314
define values as manual 313
exit application 97
reply to Observers TREND request 105
request TREND from Forecaster 99, 103
send automated METAR reports 111
send automated SPECI reports 117
send corrected MET REPORT 119
send corrected MET REPORT reports 108
send corrected METAR reports 108
send corrected SPECI reports 116
send corrected SPECIAL reports 116
send delayed MET REPORT reports 107
send delayed METAR reports 107
send deterioration SPECIs 115
send normal MET REPORT reports 99
send normal METAR reports 99
send SPECI reports 112
send SPECIAL reports 119
trigger SPECI reports 115
MIDAS IV versions 26
Missing data in ASCII Log View 222
Missing data in Weather View 47
N
Names of history files 228
Normal data in Weather View 47
Note field 41
O
Old data in ASCII Log View 222
Old data in Weather View 47
Opening weather data screens 56
Operating MIDAS IV 42
Operating, general
arranging windows 43
exiting applications 37
logging in 37
printing 44
selecting functions 42
showing and hiding status bars 44
showing and hiding toolbars 43
starting applications 37
switching between applications 43
user interface 38
Optional applications 29
Outbound messages in AFTN Monitor 177
OWS (Observer) workstation 34
P
Parameter list 325
Present weather data
in METAR/SPECI 73
Pressure data
in Actuals 240
in Data Source Manager 261
Users Guide ______________________________________________________________________
340 __________________________________________________________________M010027EN-F
in METAR/SPECI 75
Prevailing visibility data
in METAR/SPECI 70
Printing 44
Problem situations. See Troubleshooting
Q
QFE data in MET REPORT/SPECIAL 87
R
RCM (Maintenance) workstation 34
Recent weather data
in METAR/SPECI 76
Regulatory compliances 24
Related manuals 22
Remarks
in METAR/SPECI 79, 90
Reports
Aerodrome Warning, corrected 162
Aerodrome Warning, normal 161
AIRMET, corrected 154
AIRMET, normal 153
GAMET, amended 146
GAMET, corrected 146
GAMET, delayed 145
GAMET, normal 145
MET REPORT, corrected 108
MET REPORT, delayed 107
MET REPORT, normal 99
METAR, automated 111
METAR, canceled 106
METAR, corrected 108
METAR, delayed 107
METAR, normal 99
SIGMET, corrected 137
SIGMET, normal 137
SPECI 112
SPECI, automated 117
SPECI, canceled 115
SPECI, corrected 116
SPECIAL 119
SPECIAL, corrected 116
TAF, amended 129
TAF, corrected 129
TAF, delayed 128
TAF, NIL 130
TAF, normal 128
Windshear Warning, corrected 170
Windshear Warning, normal 169
Runway in Use Manager, description
introduction 303
user interface 303
Runway in Use Manager, how to
set Runway in Use manually 305
Runway Parameters window 246
Runway state data in METAR/SPECI 78
RVR data
in Actuals 241
in METAR/SPECI 72
S
Safety 23
Selecting functions 42
Sending notes between workstations 41
Sending reports. See Reports
Sensor data in Weather View 47
Sensor safety 23
Sensors
automatic mode 252
backup mode 252
manual mode 254
Showing and hiding status bars 44
Showing and hiding toolbars 43
SIGMET, description
introduction 133
menu bar 136
user interface 134
SIGMET, how to
cancel reports 138
Software applications on workstations 34
SPECI Limit Manager window 92
SPECI reports 63
SPECIAL reports 63
Starting applications 37
Status bars 44
Stored data in ASCII Log View 219
Supplementary information
________________________________________________________________________________
VAISALA______________________________________________________________________ 341
Switching between applications 43
System configuration 27
System delivery 27
System maintenance applications 33
System Status icon 41
System types 26
T
TAF, description
introduction 123
menu bar 126
report types 127
user interface 123
TAF, how to
cancel report 130
send amended reports 129
send delayed reports 128
send NIL report 130
Technical Event messages
description 205
Technical support 24
Temperature data
in Actuals 239
in METAR/SPECI 75
Toolbars
Actuals 251
AFTN Monitor 176
ASCII Log View 227
Event Monitor 207
History Monitor 291
METAR/MET REPORT 96
moving 43
showing and hiding 43
Weather View 55
TREND
replying to TREND request 105
requesting from forecaster 103
TREND field
in MET REPORT/SPECI 90
in METAR/SPECI 78
Troubleshooting
Actuals 260
AD WRNG 163
AFTN Addressee Manager 188
AFTN Monitor 179
AFTN Viewer 200
AIRMET 155
ASCII Log View 232
Data Source Manager 276
Dial-up Manager 324
Event Monitor 217
GAMET 147
History Monitor 302
METAR/MET REPORT 122
METAR/MET REPORT Manager 316
Runway in Use Manager 306
SIGMET 139
TAF 131
Weather View 61
WS WRNG 171
U
User interface 38
Actuals 234
AD WRNG (Aerodrome Warning) 158
AFTN Addressee Manager 181
AFTN Monitor 173
AIRMET 149
ASCII Log View 219
Data Source Manager 261
Dial-up Manager 317
Event Monitor 202
GAMET 142
general 38
History Monitor 279
METAR/MET REPORT 64
METAR/MET REPORT Manager 308
Runway in Use Manager 303
SIGMET 134
System Status icon 41
TAF 123
Weather View 45
WS WRNG (Windshear Warning) 166
User profiles 34
V
Version information on this manual 22
Versions 26
Viewing history files in ASCII Log View 228
Viewing reports in AFTN Monitor 178
Visibility data
Users Guide ______________________________________________________________________
342 __________________________________________________________________M010027EN-F
in Actuals 241
in METAR/SPECI 70
Voice alarms in Event Monitor 210
W
Weather data fields 47
Weather data screens 46
Weather View, description
alarm groups 58
alarm window 53
average values 48
data field colors 47
data field status 47
graph scales 52
graphical fields 51
identification data 47
instant values 48
introduction 45
latest sent METAR 53
menu bar 54
missing values 48
parameters 325
toolbar 55
user interface 45
weather data fields 47
weather data screens 46
wind rose 49
Weather View, how to
acknowledge audiovisual alarms 57
adjust graph scales 59
close weather data screens 56
deal with simultaneous alarms 58
exit application 56
monitor weather data 57
monitor weather data status 57
open weather data screens 56
use Auto Scale in graphs 60
view stored alarms 59
Wind data
in Actuals 237
in ASCII Log View 221
in METAR/SPECI 70
in Weather View 49
Wind rose 49
Wind shear data
in METAR/SPECI 77
Windshear Warning, description
menu bar 168
WMO recommendations 24
WS WRNG, description
introduction 165
user interface 166
WS WRNG, how to
cancel reports 170
WV (Weather View) workstation 34

Midas IV User's Guide M010027en-F

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

Midas IV User's Guide M010027en-F

Uploaded by

Copyright:

Available Formats

Automated Weather

You might also like