Page 1 MAINTENANCE MANUAL Vaisala AviMet® Low-Level Windshear Alert System M210886EN-G...
Page 2 English versions are applicable, not the translations. The contents of this manual are subject to change without prior notice. This manual does not create any legally binding obligations for Vaisala towards customers or end users. All legally binding obligations and...
Page 3: Table Of Contents
AviMet® Product Platform ........
Page 4 AviMet Application Icons ........
Page 5 System Status for External Usage ........89 VAISALA ________________________________________________________________________ 3...
Page 6 Maintenance Manual________________________________________________________________ CHAPTER 6 IO TERMINAL ..............91 Introduction to IO Terminal .
Page 7 SOFTWARE END USER LICENSE AGREEMENT ........135 Vaisala AviMet® Software End User License Agreement ....135 INDEX .
Page 8 Maintenance Manual________________________________________________________________ 6 ___________________________________________________________________ M210886EN-G...
Page 9 Figure 1 A Typical Vaisala AviMet System ....... . 18 Figure 2 Single-CDU System with Workstations .
Page 10 Maintenance Manual________________________________________________________________ 8 ___________________________________________________________________ M210886EN-G...
Page 11 Software Applications in Workstations ......25 Table 5 Vaisala AviMet LLWAS System Components ..... . . 27 Table 6 Example ROA System Processes .
Page 12 Maintenance Manual________________________________________________________________ Table 47 IO Terminal: Help Menu ........97 Table 48 IO Terminal: Checklist before Connecting to Field Devices .
Page 13: General Information
AviMet system and its components. Chapter 3, Functional Description: This chapter describes the typical hardware components of the AviMet systems and the basic principles and components of the ROA software architecture. Chapter 4, Getting Started: This chapter describes logging into the system, starting and exiting the applications, and the user environment common to all applications.
Page 14: Structure Of The Manual
Maintenance Manual________________________________________________________________ Chapter 6, IO Terminal: This chapter contains instructions for monitoring sensors and other field devices. Chapter 7, ASCII Log View: This chapter contains instructions for viewing history files with the ASCII Log View application. Chapter 8, Sensor Selector: This chapter contains instructions for disabling and enabling sensors with the Sensor Selector application.
Page 15: Version Information
M210886EN-G This manual. Applicable for Vaisala AviMet® Low-Level Windshear Alert System from software version 6.2 onwards. Related Manuals The typical manual set available for the AviMet products is presented in Table 3 on page Table 3 Related Manuals Manual Code...
Page 16: Documentation Conventions
Vaisala assumes no liability for the customer's failure to comply with safety precautions presented in field device manuals. 14 __________________________________________________________________ M210886EN-G...
Page 17: Esd Protection
Always hold the boards by the edges and avoid touching the component contacts. Regulatory Compliances The AviMet systems are designed according to the recommendations of international air traffic authorities as presented in the following sources. The algorithm used for calculations in the Vaisala AviMet® Low-Level Windshear Alert System (LLWAS) is the latest version of the phase III windshear algorithm developed for the U.S.
Page 18: Trademarks
Maintenance Manual________________________________________________________________ Trademarks AviMet® is a registered trademark of Vaisala Oyj. Microsoft®, Windows®, Windows® Server 2008, Windows® 7, Windows® XP, and Windows® Vista are registered trademarks of Microsoft Corporation in U.S. and/or other countries. Technical Support For technical questions, contact the Vaisala technical support: E-mail helpdesk@vaisala.com...
Page 19: Chapter 2 Product Overview
Chapter 2 __________________________________________________________ Product Overview CHAPTER 2 PRODUCT OVERVIEW This chapter gives an overview of the AviMet system and its components. System Introduction Vaisala AviMet® Low-Level Windshear Alert System (LLWAS) is a ground-based low-level windshear alert system. It provides visual and audio alerts on calculated windshear and microburst conditions for air traffic controllers and other airport personnel.
Page 20: Avimet® Product Platform
Central data unit(s) Local Area Network Workstations AviMet® Product Platform Vaisala AviMet® Low-Level Windshear Alert System (LLWAS) is part of the AviMet technology platform. Other major systems based on the platform are: Vaisala AviMet® Automated Weather Observing System (AWOS) Vaisala AviMet® Runway Visual Range System (RVR) The LLWAS system can be an independent system or fully integrated into the AviMet®...
Page 21: Single-Cdu System With Workstations
Single-CDU System with Workstations 0207-035 Single-CDU System without Workstations A single-CDU system without workstations contains a CDU without separate workstations. The CDU serves as a workstation. FIELD DATA (WORKSTATION) SENSORS COLLECTOR Figure 3 Single-CDU System without Workstations 0109-020 VAISALA _______________________________________________________________________ 19...
Page 22: Duplicated System
Maintenance Manual________________________________________________________________ Duplicated System A duplicated system contains two CDUs (CDU A and CDU B) which both receive the same data from the sensors and perform the same parameter calculations, independently of each other. Both CDUs use the same configuration. They share and store the operational parameters to ensure continuous operation in switch-over or active CDU shutdown.
Page 23: System Configuration
Vaisala about using any anti-virus software. When AviMet system is in operational use, software anti-virus functionalities, especially automatic updates and blocking, cannot be used. AviMet software has been designed to be run on closed and secured networks. Although typically the AviMet software runs on computers that have anti- virus software running, it is known that anti-virus software can have functions that significantly consume computer resources.
Page 24: End-User Software Applications
The following sections include brief descriptions of what each end-user application is used for. For detailed information, refer to the appropriate AviMet system User’s Guide. The AviMet LLWAS software focuses on the following aspects of airport weather observation: Displaying wind data (Weather View and Graphical Windshear Display).
Page 25: Graphical Windshear Display
Monitoring System Operation Diagnostics The Diagnostics application is typically a tool for maintenance personnel for monitoring the overall AviMet system operation. Depending on system configuration, also observers can use it for viewing relevant system events. 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.
Page 26: Io Terminal
Playback is a feature that allows the user to replay data from a specific period of time in the past as it was displayed on the screen. The feature can be integrated with an AviMet application, typically with a Weather View screen.
Page 27: Table 4 Software Applications In Workstations
This manual covers the maintenance applications in the RCM workstation. For information on the WV, OWS, and FWS workstations and end-user applications, see the appropriate AviMet system User’s Guide. For an example of typical software applications in each workstation type,...
Page 28 Maintenance Manual________________________________________________________________ 26 __________________________________________________________________ M210886EN-G...
Page 29: Functional Description
Chapter 3 ______________________________________________________ Functional Description CHAPTER 3 FUNCTIONAL DESCRIPTION This chapter describes the typical hardware components of the AviMet systems and the basic principles and components of the ROA software architecture. System Components Vaisala AviMet® systems are configured individually for each airport.
Page 30: Sensors
Maintenance Manual________________________________________________________________ Sensors The AviMet LLWAS system is based on wind sensor sites located around the approach and departure corridors of an airport. Each sensor site includes a wind speed and a wind direction sensor. The standard configuration for phase III algorithm requires an array of 12 sensors, but the number of sensors included in the array may be anything from 10 to 52.
Page 31: Cdu Software Components
AviMet system programs (Processes and applications) AviMet configuration files (INI files) TCP/IP Protocol network software To ensure maximum system reliability, an AviMet system can also be duplicated. A duplicated system contains two CDUs. For more information on duplicated systems, see section...
Page 32: Workstations
Data Output to External Systems (Optional) Most AviMet system data can be sent to an external system for further use. Vaisala can provide a serial output or TCP/IP connection as an optional feature. The standard data output format is specified in a separate METDATA specification document.
Page 33: Figure 5 Typical Roa Architecture
Chapter 3 ______________________________________________________ Functional Description For each principal AviMet function, there is a separate ROA process. ROA processes are system services that run within the CDU(s) and have no user interface. These processes start automatically when the CDU is started and require no logging in.
Page 34: Components In Roa Architecture
If this number differs from the one defined in your system configuration files (.ini files), the AviMet system generates an event message. The status of processes and objects can be viewed with the Diagnostics applications.
Page 35: System Processes
The following sections contain tables with examples of the processes. The full name of the process starts with "Vaisala", which is excluded from the examples to avoid redundancy. For example, "Vaisala Remote Object Server" is presented in the table in the format "Remote Object Server.
Page 36: Meteorological Processes
Maintenance Manual________________________________________________________________ Meteorological Processes The ROA meteorological processes receive sensor data from SensorIO Service and process it to generate final weather data. For examples, see the following table. Table 7 Meteorological Processes Process Name Function Wind Service Calculates wind values. LLWAS Service Calculates LLWAS alarms.
Page 37: Roa Objects
Sensor objects Meteorological objects Alarm objects External system objects A regular AviMet system can include 50 to 400 objects depending on the size and configuration of the system. The objects described in the following sections are only a sample. NOTE The objects listed in the following sections are only a sample of all the objects.
Page 38: Sensor Objects
Maintenance Manual________________________________________________________________ Sensor Objects The ROA sensor objects contain the sensor data received by the SensorIO Service. For examples, see the following table. Table 11 Sensor Objects Object name Function WIND_SENSOR_SITE1 Contains the data measured by the wind sensor. LLWAS_WIND_SENSOR Contains the data measured by the LLWAS _SITE1 wind sensor (if there are separate sensors for...
Page 39: External System Objects
Chapter 3 ______________________________________________________ Functional Description External System Objects The ROA external system objects are related to external systems (optional) that use AviMet system data. They are created by the corresponding external system service. For examples, see the following table. Table 14...
Page 40: Sensor Data Processing
The object name for an LLWAS wind sensor can be, for example, WIND_SENSOR_SITE1. If the AviMet LLWAS system is integrated with AviMet AWOS the LLWAS wind sensor might be called, for example, LLWAS_WIND_SENSOR_SITE1 to separate it from other wind sensors. This object then moves on to the corresponding...
Page 41: Figure 6 Roa Architecture: Meteorological Data
Chapter 3 ______________________________________________________ Functional Description Figure 6 ROA Architecture: Meteorological Data 1111-034 NOTE Sensor data processing is involved in all functions that use sensor data. The phase described above is not repeated in the following charts. VAISALA _______________________________________________________________________ 39...
Page 42: Alarm Data Processing
Maintenance Manual________________________________________________________________ Alarm Data Processing The system event messages that are displayed in the Diagnostics application are a result of alarm data processing. Some of the messages indicate problems, whereas others are merely intended to provide information. The principal service in alarm data processing is the Remote Object Events process, which gathers the alarm objects created by other processes.
Page 43: Figure 7 Roa Architecture: Alarm Data
Chapter 3 ______________________________________________________ Functional Description FIELD DATA COLLECTOR (optional) ALARM ROAPERS OBJECT ALARM ROASERV OBJECT ALARM SENSORIO OBJECT WIND_ WIND_ SENSOR_SITE1 SENSOR_SITE2 ALARM WIND OBJECT WINDAVE_SITE1 WINDAVE_SITE2 REMOTE OBJECT EVENTS ROAALARM WEATHER DIAGNOSTICS VIEW Figure 7 ROA Architecture: Alarm Data 1111-036 VAISALA _______________________________________________________________________ 41...
Page 44: History Data Processing
Maintenance Manual________________________________________________________________ History Data Processing History data is data that the AviMet system stores in ASCII files for a period of one month or one year depending on the configuration of the system. The stored data can be meteorological values that were shown in Weather View and system events that were shown in the Diagnostics application.
Page 45: Figure 8 Roa Architecture: History Data
Chapter 3 ______________________________________________________ Functional Description FIELD DATA COLLECTOR SENSORIO WIND_I.AlarmA REMOTE OBJECT EVENTS MESSAGE_ ROAALARM SENT ASCIIDB LLWAS_WIND_DATA_06.HIS LLWAS_REPORTS_1.HIS LLWAS_EVENT_1.HIS ASCII LOG VIEW Figure 8 ROA Architecture: History Data 0109-025 VAISALA _______________________________________________________________________ 43...
Page 46 Maintenance Manual________________________________________________________________ 44 __________________________________________________________________ M210886EN-G...
Page 47: Chapter 4 Getting Started
Logging In Log into the AviMet system with the RCMUSER user name (the user name for system maintenance personnel) and the password given to you during system installation. When you log in, the AviMet system will start automatically.
Page 48: User Interface
To solve the problem, log on with the RCMUSER profile. See also section Starting and Exiting Applications on page The typical icons used for AviMet applications are listed in the following table. 46 __________________________________________________________________ M210886EN-G...
Page 49: Typical Daily Maintenance Tasks
Chapter 4 ____________________________________________________________ Getting Started Table 16 Vaisala AviMet Application Buttons (RCM Workstation) Button Description Diagnostics opens the Diagnostics application. The following applications can typically be opened from the Diagnostics application: ASCII Log View IO Terminal Sensor Selector Weather View, if configured.
Page 50: Checking Log Printer (Optional)
Maintenance Manual________________________________________________________________ Checking Log Printer (Optional) Some systems include an optional log printer. Normally, the log printer prints system events displayed in the Diagnostics application. Check that the printer is always switched on and that paper feeding is working correctly. If the printer is offline for a period of time or there is a paper jam that goes undetected for several hours, print jobs in queue may fill the print buffer of the Windows®...
Page 51: Chapter 5 Diagnostics
It shows the status of the CDU(s), enables changing the switch-over mode and the active CDU. It displays system events. It displays the status of all AviMet processes, applications, and ROA objects. It provides access to other AviMet maintenance applications.
Page 52: Diagnostics User Interface
Maintenance Manual________________________________________________________________ Diagnostics User Interface The Diagnostics user interface can consist of the following main elements: Figure 9 Diagnostics Application (Showing All Options) 1204-053 System Status panel, with access to object browser CDU selection and switch-over mode selection buttons Events panel Buttons for acknowledging events and stopping sound alarm Overview panel (Optional) Buttons for zooming Overview (Optional)
Page 53: System Status Panel
System Status Panel The System Status panel displays the identification data and status of the CDU(s) in the AviMet system. In duplicated systems there is a status row for each CDU, in single-CDU system there is only one status row.
Page 54: Table 18 System Status Panel Columns
See section List of Objects: Object Browser on page All processes Total number of AviMet processes in the CDU. A list of processes can be displayed by clicking the number. See section Lists of Processes on page Active processes Number of active AviMet processes in the CDU.
Page 55: Lists Of Processes
The lists provide basic information on the processes, see the table below. Table 20 List of Processes Columns Columns Description Name Name of process. Status Status of process. See Table 21 on page 54 Address IP address of the CDU where the process is running. VAISALA _______________________________________________________________________ 53...
Page 56: List Of Applications
Maintenance Manual________________________________________________________________ Table 20 List of Processes Columns (Continued) Columns Description Port Port used for communication by the process. Version Software version. Table 21 List of Processes: Statuses Status Description Obligatory Normal situation in single-CDU systems: One item exists. Missing An obligatory item does not exist.
Page 57: List Of Objects: Object Browser
A list of all objects on the CDU is displayed when you click the number in the All Objects column for the corresponding CDU. A list of missing objects on the CDU is displayed when you click the number in the Missing Objects column for the corresponding CDU. VAISALA _______________________________________________________________________ 55...
Page 58: Figure 13 Diagnostics: Object Browser Example (All Objects)
Maintenance Manual________________________________________________________________ Figure 13 Diagnostics: Object Browser Example (All Objects) 1204-061 The lists provide basic information on the objects, see the tables below. Table 24 Object Browser Columns Columns Description Name Name of object. Status Status of object. See Table 25 on page 56 Address IP address of the CDU where the object is running.
Page 59: Figure 14 Diagnostics: Selecting Server For Object Details
By right-clicking the object in the Object browser, you can select from which server (Active, Server A, Server B) the object details are displayed in the Object details panel: Figure 14 Diagnostics: Selecting Server for Object Details 1204-062 VAISALA _______________________________________________________________________ 57...
Page 60: Object Details Panel
Maintenance Manual________________________________________________________________ If you select Details from this menu, an information screen is displayed about the services that handle the object: Figure 15 Diagnostics: Object Details Information 1204-063 The following buttons are available in the Object browser. Table 28 Object Details Panel: Buttons Button Description Searches for the objects that contain the string entered in the...
Page 61: Figure 16 Diagnostics: Object Details Panel In Object Browser
You can open Object details panels for several objects and view the panels in tabbed, tiled, or cascaded format using the buttons at the bottom of the window. See Figure 17 on page Figure 17 Tiled Object Details Panels in Object Browser 1205-056 VAISALA _______________________________________________________________________ 59...
Page 62: Table 29 Object Details Panel: Columns
Type Contains programming information intended mainly for Vaisala internal use. A data item with the type "List" indicates the status of the whole data item list. Other types are String, Int (Integer), and Real (real number).
Page 63: Events Panel
AWOS system. Normally, the Events panel includes fewer event messages, and the periods between messages are longer. The following sections describe the items in the Events panel. For instructions on their use, see section Operating Diagnostics Application on page VAISALA _______________________________________________________________________ 61...
Page 64: Events Panel Tabs/Event Types
Maintenance Manual________________________________________________________________ Events Panel Tabs/Event Types The system events are displayed on several tabs, the number and type of which depends on the system configuration and the user profile. The following describes the typical tabs. Table 31 Events Panel Tabs /Event Types Type Explanation Operational/...
Page 65: Events Panel Columns
Overview Panel (Optional) If configured in your AviMet system, the Diagnostics application includes the Overview panel. It provides an overview of the system at a glance by displaying symbols of all devices in the system. The status of each device is indicated with the color of the device symbol and with alarm and warning symbols.
Page 66: Figure 19 Diagnostics: Overview Panel
Maintenance Manual________________________________________________________________ Figure 19 Diagnostics: Overview Panel 1204-074 Figure 20 Diagnostics: Overview Panel with Device Details Panel 1301-012 NOTE The figures and examples in this chapter display situations that have been artificially created during software test conditions. In normal operation, the number of missing or faulty items and event messages is smaller and the periods between messages longer.
Page 67: Table 34 Overview Panel Icons And Buttons
Zooms out so that the whole image can be seen at a glance. Zoom in Zooms in the image Zoom out Zooms out the image Keep fit view When selected, the Fit View setting will stay on even when the size of the overview panel is changed. VAISALA _______________________________________________________________________ 65...
Page 68: Device Details Panel (In Overview Panel)
Maintenance Manual________________________________________________________________ Device Details Panel (In Overview Panel) As part of the Overview panel, the Device details panel displays the system events and other details for the sensor or other device that is selected in the Overview panel. Figure 21 Diagnostics: Device Details Panel (In Overview Panel) 1301-013 The upper part of the Device details panel displays the same information...
Page 69: Tools Panel
Normal state: no technical alarms exist for this device. Tools Panel The Tools panel contains buttons that provide access to other AviMet maintenance applications, for example, to IO Terminal. Typically, there is also a button for the ASCII Log View application for archived data. Other system-specific buttons may be available.
Page 70: Monitoring Cdu Status
Maintenance Manual________________________________________________________________ Monitoring CDU Status You can monitor the status of the CDU(s) from the System Status panel. Green heartbeat icon: System is operating normally. Red heartbeat icon: The heartbeat signal has not been received from the CDU because a persistent CDU failure has been detected. For example, the CDU has been turned off or it has crashed, or there is a failure in the connection to the CDU.
Page 71: Manually Changing The Active Cdu
CDU selection and change the active CDU again when switch-over conditions occur. If you want to keep your CDU selection regardless of the situation, change the switch-over mode to "Manual" first; see section Changing the Switch-over Mode to Manual on page VAISALA _______________________________________________________________________ 69...
Page 72: Changing The Switch-Over Mode To Manual
Maintenance Manual________________________________________________________________ Changing the Switch-over Mode to Manual In duplicated systems, the system controls automatically which CDU is active. This is called Automatic switch-over mode. See section Duplicated System on page You can change the active CDU by clicking the Switch CDU button, see section Manually Changing the Active CDU on page If need to change the active CDU more permanently, you have to first...
Page 73: Monitoring Roa Processes And Applications
To display all objects in a duplicated system, click the All objects button. The Object browser with a list of the selected objects is displayed. The list contains, for example, status information on the objects. See List of Objects: Object Browser on page VAISALA _______________________________________________________________________ 71...
Page 74 Maintenance Manual________________________________________________________________ Scroll down the object list to see which object has problems. You can also search for a particular object(s) by typing its name, or part of it, in the Search field. This will filter the object list and display only the objects containing that particular string.
Page 75: Monitoring Sensor Data Status And Value
If the status is "Invalid", the connection is working properly, but the measured value is out of the defined validity range. To troubleshoot technical problems with the sensor, refer to the appropriate field device manuals. VAISALA _______________________________________________________________________ 73...
Page 76: Monitoring With The Overview Panel (Optional)
Monitoring System Status in Overview Panel If configured in your system, the Overview panel provides a quick glance to the overall status of your AviMet system. The Overview panel gives a graphical presentation of all the CDU(s), sensors, workstations, and other devices of the system. All devices are represented by symbols displayed on an image of the system.
Page 77: Displaying Whole Image
Viewing Device Details in Overview Panel If configured in your system, the Overview panel provides a quick glance to the overall status of your AviMet system, including device details. To get more information on the devices displayed in the Overview panel, do the following: Select a device by clicking the device symbol on the image.
Page 78: Viewing Events From Selected Device In Overview Panel
Maintenance Manual________________________________________________________________ Viewing Events from Selected Device in Overview Panel If your system includes the Overview panel, you can use it when you want to pay special attention to the events related to a specific device. Do the following: In the Overview panel, find the site or device that you want to monitor.
Page 79: Viewing Stored Events
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. VAISALA _______________________________________________________________________ 77...
Page 80: Dealing With Technical Event Messages (Tech)
Vaisala assumes no liability for the customer’s failure to comply with the safety precautions presented in field device manuals.
Page 81: Table 38 Example Technical Events
CDU are in abnormal state. To CORRECT STATE get more information, use the Services application of the Windows system. In the Diagnostics application, the objects ROAMONITORA_INFO and ROAMONITORB_INFO provide the name of the first service that is not in the correct state. VAISALA _______________________________________________________________________ 79...
Page 82: Event Messages Related To Missing Field Device Data
Check the cables and refer to the FAILURE AT LLWAS SITE X solar battery and transmitter documentation. TCP/IP SERVICE: Link NNNN AviMet LLWAS TCP/IP Service failed to failed to connect to remote host connect to remote computer. The network xxx.xxx.xxx.xxx, port yyyy.
Page 83: Device-Specific Event Messages
This is a preliminary warning. You should make more disk space available in the history folder (by default, the file is located in Avimet\HISTORY). ASCII DATABASE SERVICE: OUT OF DISK SPACE This is a final warning. It indicates that the free disk space allocated for history files has decreased to half of the specified amount.
Page 84: Ascii Database Service: Output Directory Error
ASCII DATABASE SERVICE: OUTPUT DIRECTORY ERROR This message indicates that the history folder does not exist and the related service is unable to create it. Contact Vaisala Helpdesk. Dealing with Messages Related to CDU(s) This section lists some event messages related to CDU(s) or communication between CDU(s) and other devices, that is, a LAN problem.
Page 85: Abnormal Server Status, Missing Roa Server Or Network Problem Detected By Server X
The following sections list some of these event messages and give instructions for solving problems indicated by these messages. Note that you may need to use other AviMet maintenance applications, for example, IO Terminal, to solve the problems. For more information on the other maintenance applications, see the appropriate chapters in this manual.
Page 86: Object Conflict Detected By Server X
The message indicates that there is an incorrect number of ROA objects in the AviMet system. The parent process for the object is not running, or is unable to create and manage the object. To find out more, do the following: Use the System Status panel to find out which object is missing.
Page 87: Remote Object Monitor Fault Or Error Reason For Switchover Detected By Server X
SPEED 52, MINIMUM 0.0, MAXIMUM 50.0”). These messages can indicate, for instance, that the sensor needs calibration or that there is a physical obstruction preventing the normal operation of the sensor. Weather-related messages appear, for instance, when wind values are changing as preconfigured. VAISALA _______________________________________________________________________ 85...
Page 88: Dealing With Message Notifications (Mesg)
There is a microburst alert. Dealing with Message Notifications (MESG) If the AviMet LLWAS system is integrated with the AviMet AWOS system, the Events panel in the Diagnostics application also displays Message Notifications. These event messages are related to weather reports.
Page 89: Checking Network Connection
Check the list again to verify that the process has started. NOTE On some rare occasions, the status of the process might remain "Missing" although you start the process repeatedly. In such cases, restart the system. See section Restarting the System on page VAISALA _______________________________________________________________________ 87...
Page 90: Restarting The System
Make sure that the operative situation at your airport allows an interruption in the automatic data flow. Inform the AviMet users at your airport about the system restart. Log in to the CDU where the problem with the service is.
Page 91: System Status For External Usage
Device Details Panel (In Overview Panel) on page 66 describes the available device information. The AviMet system can work as an SNMP agent and transmit the device status information. The SNMP interface can be set on even if the optional Device details panel would not be included.
Page 92 Maintenance Manual________________________________________________________________ 90 __________________________________________________________________ M210886EN-G...
Page 93: Chapter 6 Io Terminal
CAUTION When the IO Terminal connection to sensors or other field devices is open through an active CDU, no sensor data is usable further in the AviMet system. In duplicated systems, connecting through the server enables viewing sensor data without interrupting the data flow.
Page 94: Io Terminal User Interface
Maintenance Manual________________________________________________________________ IO Terminal User Interface The IO Terminal user interface consists of the following main elements: Connection control panel for connecting to devices and viewing communication settings. Terminal panel for viewing and sending messages to devices. Menu bar for exiting and logging data. Figure 22 on page 92 below shows the IO Terminal user interface.
Page 95: Connection Control Panel
Shows the port settings for the selected device and the port settings. See Table 42 on page Click the Connect button to connect to the selected device, through the server selected from the list next to the button. VAISALA _______________________________________________________________________ 93...
Page 96: Table 42 Io Terminal: Port Settings
Maintenance Manual________________________________________________________________ Table 41 IO Terminal: Connection Control Panel Elements Element Description Server selection drop- Available in duplicated systems only. Select which down list server is used for connecting: Active, CDU A, or CDU B. Note that when you connect to a device through data line using the active server, you interrupt the flow of automatic weather data from sensors to the end- user applications.
Page 97: Terminal Panel
ASCII character ETX (3), End Of Text ASCII character EOT (4), End Of Transmission ASCII character ENQ (5), Enquiry ASCII character ACK (6), Acknowledgement ASCII character LF (10), Line Feed ASCII character CR (13), Carriage Return ASCII character CAN (24), Cancel VAISALA _______________________________________________________________________ 95...
Page 98: Menu Bar
Maintenance Manual________________________________________________________________ You can modify the terminal display settings by selecting the options in the Settings frame of the Terminal panel. The settings define the way sensor messages and commands are displayed in the Terminal panel. See Table 44 on page Table 44 IO Terminal: Terminal Display Settings Option...
Page 99: Status Bar
Operating IO Terminal Starting IO Terminal To open the IO Terminal application, click the IO Terminal button in the Diagnostics application. Exiting IO Terminal To exit IO Terminal, select Exit from the File menu. VAISALA _______________________________________________________________________ 97...
Page 100: Field Device Connection Options
Some systems include two communication channels from the CDU to the sensors, or from the CDU to the data collector: data line and maintenance line. The data line is used for transmitting the weather data to the AviMet system CDU. The maintenance line is intended for maintenance and troubleshooting purposes.
Page 101: Connection Via Active Or Hot Standby Server
CDU. You can see this flow of sensor messages in the Terminal panel when you connect to a port that is connected to an auto-send sensor or a data collector. VAISALA _______________________________________________________________________ 99...
Page 102: Check List Before Connecting
Maintenance Manual________________________________________________________________ Check List before Connecting Before opening a connection to a field device, study carefully the check list presented in Table 48 on page 100. Table 48 IO Terminal: Checklist before Connecting to Field Devices Question Source of Information Action Is there a separate Airport-specific...
Page 103: Opening And Closing Connection To Devices
Terminal panel. Enter the commands as described in section Sending Commands to Devices on page 102. You can close the connection by clicking the Disconnect button in the Connection control panel. VAISALA ______________________________________________________________________ 101...
Page 104: Opening And Closing Connection Via A Data Collector
Maintenance Manual________________________________________________________________ Opening and Closing Connection via a Data Collector If your system includes data collector(s), for example, a weather station, the procedure for connecting is similar to the one described in section Opening and Closing Connection Directly to Field Device on page 101, but note the following order in connecting and closing: Open the connection from the CDU to the data collector.
Page 105: Saving Field Device Messages (Logging)
To include timestamps in log files, select the option If logging use timestamps from the Log menu. To disable logging, clear the Log to file selection from the Log menu. Logging ends automatically when you close IO Terminal. VAISALA ______________________________________________________________________ 103...
Page 106: Modifying Terminal Display Settings
Maintenance Manual________________________________________________________________ Modifying Terminal Display Settings You can modify the terminal settings with the selections in the Settings frame of the Terminal panel. The settings define the way sensor messages and commands are displayed in the Terminal panel. You can make the following selections: Select Visible symbols for binary to show the non-printable characters (binary values) as symbols.
Page 107: Ascii Log View
ASCII Log View User Interface The following sections describe these elements of the ASCII Log View briefly. For instructions on how to open history files, see section Operating ASCII Log View on page 111. VAISALA ______________________________________________________________________ 105...
Page 108: Ascii Log View Main Window
Maintenance Manual________________________________________________________________ ASCII Log View Main Window Figure 25 on page 106 presents the ASCII Log View main window when no files have been selected for viewing. Figure 25 ASCII Log View Main Window 1204-048 When history files have been selected for viewing, the files are displayed either in Tab or Tile mode inside the ASCII Log View main window.
Page 109: Figure 26 Ascii Log View: Weather Parameter Files (Tile Mode)
(When applicable) The status of the data at the time when the data was stored. Status codes provide you with information on two things: what the sensor mode (Backup and Manual) and data status (Old, Invalid, Missing, Undefined) were at storage time. VAISALA ______________________________________________________________________ 107...
Page 110: Reports Files
Normal status. Data comes from a sensor and is valid. C (Backup/ (For optional weather data when LLWAS is integrated with Copied) AviMet AWOS) Data comes from a backup sensor due to a problem with the original sensor. m (Manual) (For optional weather data when LLWAS is integrated with AviMet AWOS) Data is entered manually by the user due to a problem with the original sensor.
Page 111: Table 52 Ascii Log View: Llwas Reports Processing Status Codes
METAR, as displayed in the Weather View application. Table 53 ASCII Log View: Reports File 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 VAISALA ______________________________________________________________________ 109...
Page 112: Events Files
2_WIND_ panel of the Diagnostics application. SENSOR_ MISSING_ DATA The event type. For more information on Event TECH types, see the AviMet system Maintenance Manual. ST/Status The status of the event (0=over, 1=acknowledged, 2=alarm, 3=warning, 4=message notification) 110 _________________________________________________________________ M210886EN-G...
Page 113: Toolbar Buttons
To start ASCII Log View, click the ASCII Log View button , typically located in the Windows taskbar or in the Tools panel of the Diagnostics application. To exit ASCII Log View, click the Close button at the top right corner of the application. VAISALA ______________________________________________________________________ 111...
Page 114: Opening And Viewing History Files
Windows taskbar or the Tools panel in the Diagnostics application. Click the Open button in the toolbar. A file selection window is displayed. In the file selection window, open the D:\Avimet\HISTORY folder, or another folder specified for history files in your system. 112 _________________________________________________________________ M210886EN-G...
Page 115: Viewing Several Files At The Same Time
Use the arrow buttons next to the tab headers to view more files: Use the scroll bars to view more data. To close a tab, click the Close icon at the Tab header. An example of files in Tab mode is presented in Figure 27 on page 110. VAISALA ______________________________________________________________________ 113...
Page 116: Refreshing Data
Maintenance Manual________________________________________________________________ In the Tile mode, several open files are displayed simultaneously. You can do the following: If the files do not fit the screen, drag the file window borders to resize and arrange the files to suit your needs. Use the scroll bars to view more data.
Page 117: Troubleshooting Ascii Log View
When viewing a history file, some The columns might have Drag the column borders so that parameters or columns are been dragged on top of each the hidden columns will appear. missing. other by mistake. VAISALA ______________________________________________________________________ 115...
Page 118 Maintenance Manual________________________________________________________________ 116 _________________________________________________________________ M210886EN-G...
Page 119: Chapter 8 Sensor Selector
Data from the disabled sensor will not be published for use in other system processes. Sensor Selector User Interface Sensor Selector lists all sensors and connection interfaces of the system, including sensor name, sensor location, message type, and sensor status. VAISALA ______________________________________________________________________ 117...
Page 120: Figure 29 Sensor Selector User Interface
Maintenance Manual________________________________________________________________ Figure 29 Sensor Selector User Interface 1205-016 The following table describes the Sensor Selector elements. Table 58 Sensor Selector Columns Column Description Name Name of the sensor in the system. Mode Shows if the sensor is disabled or enabled. When the mouse pointer is placed over a row, a list with the following options is displayed: Enabled: Data from an enabled sensor is used in the system...
Page 121: Operating Sensor Selector
Move the mouse pointer over the row for the sensor that you want to enable. The list for selecting Disabled or Enabled is displayed: Select Enabled. This will change its status to "Online" and the data from it will be published for other system processes. VAISALA ______________________________________________________________________ 119...
Page 122 Maintenance Manual________________________________________________________________ 120 _________________________________________________________________ M210886EN-G...
Page 123: Chapter 9 Playback
Introduction to Playback Playback is a feature that allows you to replay data from a specific period of time in the past. The feature can be integrated with an AviMet application, typically with a Weather View screen. During playback, you will see exactly the same sequence of data updates on the screen that were originally displayed on the screen.
Page 124: Figure 30 Playback Feature As Part Of Weather View Application
Maintenance Manual________________________________________________________________ Figure 30 Playback Feature as Part of Weather View Application 1012-220 The controls include selections for the start time and end time, the Play/ Pause/Stop buttons, a status icon, the information pane, and the slider tool. Figure 31 Playback Controls 1012-221 The status icon colors are explained in...
Page 125: Operating Playback
To access the slider tool, first click the Pause button. The status icon turns to yellow. You can now click the slider tool and scroll to the desired point in time to enable more closer inspection of the displayed data. VAISALA ______________________________________________________________________ 123...
Page 126: Troubleshooting Playback
Maintenance Manual________________________________________________________________ Troubleshooting Playback Red status icon indicates problems with playback, typically a faulty time selection or missing data. The information pane next to the playback controls shows error messages related to playback, see Table 60 on page 124. Table 60 Error States Error Text Explanation...
Page 127: Chapter 10 Remote Monitoring
Introduction to Remote Monitoring Software When agreed in a service agreement, the Vaisala remote monitoring software enables Vaisala Service Center to establish a secure connection to your system via Internet and to perform remote diagnostics, updates, and repair. The remote monitoring software is preinstalled in all AviMet systems.
Page 128: Disabling Remote Monitoring Software
Maintenance Manual________________________________________________________________ Move to the folder where the Axeda Agent has been installed, by default c:\Axeda\Connector. Execute the following commands: eKernel.exe -register net start "AxedaConnector" Move to the folder where the Axeda Desktop server has been installed, by default c:\Axeda\Desktop\Server. Execute the following command: AxedaDesktopServer.exe -register Do the same in all servers (CDUs).
Page 129: Troubleshooting Remote Monitoring
Troubleshooting Remote Monitoring When making the service agreement, the settings needed for remote monitoring have been defined together with Vaisala Service Center. If there are problems with starting the remote monitoring services or using remote monitoring, check that the settings are as agreed. For examples, see the following: Check that Axeda services are running.
Page 130 Maintenance Manual________________________________________________________________ 128 _________________________________________________________________ M210886EN-G...
Page 131: Glossary
Weather parameters that the Central Data Unit (CDU)produces through calculations, in contrast to measured data. Calculated data is based on measured data. Central data unit, a computer that processes sensor data. An AviMet system can include one or two CDUs. VAISALA ______________________________________________________________________ 129...
Page 132 LLWAS processing status and support LLWAS processing status. Diagnostics An AviMet application for monitoring system status and events. duplicated system An AviMet system that has two CDUs: one active and one passive (hot standby). Other system types are single-CDU system with or without workstations. end-users Observers, forecasters, and air traffic controllers that use the AviMet system for their daily observing and reporting tasks.
Page 133 Local Area Network. The AviMet system computers are connected via LAN. In duplicated systems, the two CDUs communicate via LAN. LLWAS algorithm The algorithm used in the AviMet LLWAS system for calculating the windshear conditions. The LLWAS phase III windshear algorithm developed by NCAR for the U.S.
Page 134 See also data status. Operational event A message type in the Diagnostics application. optional application An optional application or function in the AviMet system that is not included in the standard configuration. Observer workstation in the AviMet system.
Page 135 A component of the ROA architecture. A system service that creates and manages ROA objects. service mode See command mode. single-CDU system An AviMet system with one CDU, with or without workstations. See also duplicated system. site The location at which weather data is measured. In other words, the location of a sensor in the field, or the location of a data collector with several sensors connected to it.
Page 136 Based on horizontal wind speed and wind direction measurements, the conditions AviMet LLWAS system uses the LLWAS phase III algorithm to compare the current wind situation differences to airport-specific threshold values to determine if possible windshear conditions exist. These calculated conditions are referred to as windshear conditions. See also windshear alert, windshear, and LLWAS algorithm.
Page 137: Software End User License Agreement
SOFTWARE END USER LICENSE AGREEMENT All rights to any software are held by Vaisala or third parties. The customer is allowed to use the software only to the extent that is provided by the applicable supply contract or Software End Used License Agreement.
Page 138 UNDERSTANDING BETWEEN THE PARTIES. Product. The Software means a single copy, in object code format, of the AviMet® software used with or to control Vaisala sensors and created by Vaisala for use on a single computer. The Software can include IBM Program(s) as specified in IBM License Information Document ("LI") and this License and its terms and conditions shall...
Page 139 Vaisala equipment that may be operated, controlled, and/or displayed by the Software. You agree that, in the event and at such time as you no longer own any Vaisala equipment that may be controlled by the Software, or in the event of other...
Page 140 Maintenance Manual________________________________________________________________ ERASURE, MISHANDLING, OR THE LIKE OF YOUR DATA OR OTHER SOFTWARE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY LICENSOR OR AN AUTHORIZED LICENSOR REPRESENTATIVE SHALL CREATE A WARRANTY OR IN ANY WAY INCREASE THE SCOPE OF THIS WARRANTY.
Page 141 Contracts for the International Sale of Goods (CISG) shall be excluded. Any dispute, controversy or claim arising out of or relating to this Contract between Vaisala and the customer, which cannot be solved by amicable means shall be submitted to arbitration. Any...
Page 142 Maintenance Manual________________________________________________________________ 13. Intellectual Property. Licensor represents and you agree that the Software, including source and object code, is confidential and proprietary to Licensor. All confidentiality and proprietary notices, including but not limited to copyright notices displayed on the Software, shall remain intact and unaltered and shall be included on any documents, media, printouts, visualizations, or on any other electronic or tangible expressions associated with, related to, or derived from the Software.
Page 143: Index
Contents of the manual Applications, end-user not running unlicensed 84, 85 Applications, maintenance Daily maintenance tasks Architecture of AviMet systems Data collectors 28, 99 Archived files Data collectors, connecting ASCII Log View, description Data output to external systems ASCII Log View window...
Page 144 71 list of move overview image troubleshooting show whole Overview image International recommendations start application Introduction to AviMet view device details Invalid data in ASCII Log View view events from selected sites IO Terminal, description view object details auto-send/polled sensors...
Page 145 Stand-alone system external Starting applications meteorological Stored data in ASCII Log View Switch-over mode System architecture System components RCM (Maintenance) workstation System configuration Regulatory compliances System delivery Related manuals System maintenance applications Remote monitoring System types VAISALA ______________________________________________________________________ 145...
Page 146 Maintenance Manual________________________________________________________________ duplicated restarting process/service single-CDU with workstations sensor problems single-CDU without workstations services Technical events (TECH) TCP/IP connection to external systems Technical Event messages UPS (Uninterrupted Power Supply) dealing with User interface description Application icons list of ASCII Log View troubleshooting Diagnostics Technical support...
Page 147 ________________________________________________________________________________ VAISALA ______________________________________________________________________ 147...
Page 148 *M210886EN*...

Vaisala AviMet Maintenance Manual

Chapter 2 Product Overview

Chapter 4 Getting Started

Chapter 5 Diagnostics

Chapter 6 Io Terminal

Chapter 8 Sensor Selector

Chapter 9 Playback

Chapter 10 Remote Monitoring

Quick Links

Troubleshooting

Need help?

Questions and answers

Summary of Contents for Vaisala AviMet

Table of Contents