IVAO Pilot Software[PDF]

License

The End-User License Agreement ("EULA") is a legal agreement between you and International Virtual Aviation Organisation VZW (“IVAO”).

Please read and comply with the EULA license.

Introduction

This document will describe the IVAO Pilot Software at his initial version:

  • Altitude 1.9.10 BETA
The Pilot Client software is composed of two software components and needs one Web application:
  • The Connector software (CONN)
  • The User Interface (UI) application
  • The Flight Plan System (FPS) Web application

Connector software

The Connector (CONN) software is:
  • a 32bit DLL file for Microsoft flight simulator FSX and FSX Steam Edition
  • a 32bit DLL file for Lockheed Martin P3D V1, V2 and V3
  • a 64bit DLL file for Lockheed Martin P3D V4
  • a 32bit XPL file for the Laminar Research flight simulators : X-plane 10 - 32bits
  • a 64bit XPL file for the Laminar Research flight simulators : X-plane 10 & 11 - 64bits

The connector (CONN) is the file installed inside your flight simulator that reads and writes flight data of your simulator. It enables also the local network Ethernet connection to allow access to these data by the User Interface (UI).

The connector (CONN) also handles communication with IVAO SHARD servers to:

  • send aircraft position to the server
  • receive other user aircraft positions to display MTL/CSL inside your simulator
  • receive and transmit communication text with other Pilots and ATC
  • server information exchange (system messages, answers to pilot text requests, ...)


NOTE: Flight Simulator 2002 and Flight Simulator 2004 are not compatible with the present version of the connector (CONN).
NOTE: X-plane 8 and X-plane 9 32bit have not been tested.

User Interface

The User Interface (UI) is an application which is running outside the flight simulator in your operating system.

It manages the connection with the connector (CONN) software connected directly on the same computer or a computer connected via an internal Ethernet network.

The user Interface (UI) can be run on:
  • All 64bit versions of Microsoft Windows
  • Mac OSX 10.6 and above
  • Linux 64bit

The User Interface (UI) main features are:

  • Display text communication with other IVAO users
  • Manage Communication channels (ATC frequencies, Private communication, ...)
  • Manage transponder code
  • Display ATC connected around your position
  • Retrieve ATIS and weather information
  • Give the possibility to have own TCAS

Flight Plan System (FPS)

The Fligh Plan System (FPS) is a web application that manages all your flight plans for all your flights in IVAO.

The flight plan system main features are:

  • create your flight plan from scratch
  • modify an existing one
  • retrieve and old flight plan from your history
  • manage your preferred aircraft in a virtual hangar


Flightplanserver overview.png
Please consult the documentation of Flight Plan Server in order to learn how to use it.

Launching UI application

Start your simulator and place your aircraft on ground on an airfield or a seaport ( for float aircraft).

When your simulator is running and your aircraft is loaded and waiting, start the User Interface.

  • Windows : launch pilot_ui/win/64/PilotUI.exe
  • MacOS : mount pilot_ui/osx/PilotUI.dmg and start PilotUI.app
  • Linux : launch pilot_ui/lin/PilotUI
The UI application, after start, will show the local Ethernet connection window. Connect the UI to the CONN running in your simulator by using:
  • IP Address = 127.0.0.1, if you are running both the UI and the simulator on the same computer.
  • Password = ivao (lowercase only do not use uppercase IVAO)


Connection.png


Note: If the UI application display remains unchanged after pressing the Connect button, this means that the connector software is not installed or incorrectly installed in your simulator software.
Note: If the UI application is run in a local network, you shall use the Ethernet IP number of the flight simulator computer instead local IP 127.0.0.1.



User Interface - main panel

The User Interface is purposely minimal and is broken down in the following major sections:
  1. The Top bar which includes Flight Plan check area, MTL selection button and pinned button
  2. The Input/Output Communication Text Area
  3. The Output Text scratch pad and the “Auto Unicom” function
  4. The Transponder Panel
  5. The Radio Panel
  6. The Action button Panel (which includes the connection panel)


Swpilot UI main start.png
If the pilot UI COM1 and COM2 frequencies are set to ---.---, this means that:
  • The UI is not connected to the CONN application running in your simulator, OR
  • The UI may be connected to a cold and dark aircraft


For connection to network just jump to action button area below or use right menu.



Top bar

The Top bar contains 3 functions:

  • Flight plan check area
  • MTL selection button
  • Pin button



Flight plan check area

The flight plan check area purpose is to display the active flight plan taken by the IVAO server from the Flight Plan Server.
Note: Flight plan is no longer accessible in the new IVAO pilot software interfaced with the simulator.
By default without a flight plan or before any connection, the Flight Plan checking panel will display the default text “No Flight Plan” against a red coloured background.
Swpilot noflightplan.png


When you click on this banner, the UI (User Interface) will display the default message:

Swpilot noflightplan msg.png


After succesful connection to the IVAO server and flight plan correlation done with your connection callsign, this area will display the following 3 data used in the flight plan:
  • Your aircraft identification callsign
  • The departure airfield ICAO code
  • The destination airfield ICAO code

In the example below, the flight plan is checked with your active connection; the callsign used is VAOTDAM and the flight is from ENGM to LROP.

Swpilot flightplanok.png


If you click on this panel, the flight plan in ICAO text format will be displayed like the example below:


Swpilot flightplan display.png



MTL selection button

When either connected or disconnected, you may change the MTL used without changing your connection status by using the MTL button.

When you click on the MTL button, a popup MTL window appears:

Pilotclient mtl selection.png


You can select the new MTL aircraft or MTL variant in the list provided, or you can type the desired aircraft by using your keyboard also.

Pilotclient mtl change list.png


After selection, you have the choice to select the change by clicking on the CHANGE button or cancel the new selection by clicking on the CANCEL button.

Pilotclient mtl change cancel select.png



Pin and Unpin UI interface on top

At the right of the top bar, next to the MTL button, you will find the pin icon.

This pin icon can be used to force the UI interface to be in front of all other applications on the screen.

The icon animation is created to make sure that you select the desired configuration:

  • If the interface is pinned in front of the screen you will see the white icon like the example below:
Pinned.png
  • If the interface is not pinned in front of the screen you will see the grey icon like the example below:
Unpinned.png
Note: Sometimes the pinning function does not work with some simulator in full screen mode.



Input/Output Communication Text Aera

Communication Text Panel

The Text Panel displays different types of messages: (see image below)
Pilotclient text panel overview.png


In the example above, you can see:

  • the active frequency is 122.800 – the UNICOM frequency
  • one input message from the IVAO Shard Server v0.6
  • the answer to a METAR request for LFRB airfield
  • 1 auto-information message from the pilot who runs the UI (VAOTDAM>)
  • 1 ATC (LFEC_TWR) request to contact
The number between brackets [ and ] in all messages represents the current minutes of the message received in your interface:


Below you will find all the possible types of messages which can be received by the communication text panel.


Server message

IVAO server system messages from the network (#!>) displayed in white colour just after a successful connection.
Pilotclient system text.png


If you have tuned your frequency to an ATC station, the selected ATC station and frequency will be displayed instead of the UNICOM channel like the figure above.


New icon.jpg

In case of Altitude software detects lower framerate when using X-plane that may have a high impact on ATC management or other traffic separation, a specific message is displayed like this one below:
Rule: This message is displayed at the rate of 20seconds until ratio is below 70%.
Swpilot framerate low.png

Received message on selected frequency from other pilots

Text messages from nearby Pilots are displayed in white colour (frequency which you are currently tuned to) with their call-sign displayed as prefix before message with the “>” separator.

Example: Message sent by AFR88ZW at 18:32 UTC: auto-information message in Unicom

Pilotclient pilot rx com.png



Received message on selected frequency from ATC

Text messages from ATCs sent on the active frequency and directed to you are displayed in green colour (frequency which you are currently tuned to) with their call-sign displayed as prefix before message with the “>” separator.
Text messages from ATC in service on the frequency and not directed to you are displayed in white colour (frequency which you are currently tuned to) with their call-sign displayed as prefix before message with the “>” separator.

Example: Message sent by LFRR_CTR at 11:38 UTC: clearance from ATC in current frequency

Pilotclient atc rx com.png



Your messages sent on active frequency

Your own text messages sent on the active frequency which are displayed with your connected callsign in green.

Example: message sent by VAOTDAM at 15:04 UTC: auto-information message on frequency

Pilotclient tx com.png


Note: your callsign is automatically sent. No need to type it.



ATC Request Contact messages

ATC invitation to contact is received only for you and sent by an active ATC. The message is displayed in orange.
This message invites you to join/connect the ATC frequency in order to make a controlled flight.

Example: Invitation to contact LFEC_TWR ATC received by the pilot:

Pilotclient atc forceact.png


ATC invitation to contact is received by using an oceanic SELCAL request paired with dual DTMF tune signals. The message is displayed in orange.
This message invites you to join/connect the ATC frequency in order to make a controlled flight.

Example: Selcal call received by the pilot.

Pilotclient atc selcal.png



Incomping Private messages

New icon.jpg

Incomping Private messages is received for you. The message is displayed in grey with the prefix tag [MSG].


Altitude msg private.png

At the same time, you received the incoming message, UI remind you to consult the message by blinking the MSG button in Red.

Altitude MSG tab RED.png

Weather messages

METAR and TAF messages can be received from the network after the server has received a manual request from yourself.
The messages are displayed in light blue.


Example: METAR information received by the user after a METAR request to the server:

Pilotclient metar.png



Broadcast

All IVAO Broadcast messages are displayed in Red colour. They are received by all users in the network and issued by IVAO supervisors or administrators.


Example: Broadcast message sent by Supervisor IVAO-MA1 for an ATC exam:

Pilotclient broadcast.png



Scratch pad

Behind Text Panel, there is the usual text input scratch-pad. The scratch-pad is followed by a SEND button. When you click on SEND, the entire text written in scratch-pad is sent on the current frequency.
Swpilot scratchpad.png


RULE: When sending any message on the main selected frequency, you should use standard phraseology in English having regard to the Self announcing procedure and Phraseology text abbreviation. You may use also the onboard Auto-Unicom module to help you make these announcements on the frequency.

Example: Scratch-pad with the text message ready to be sent on the frequency in: “your text shall be written here”.

Swpilot scratchpad example.png



Specific commands (dot commands)

In the scratchpad or in message tabs, you can also send commands. Commands will not be sent on the current frequency as text but commands will be converted by the User Interface as server requests or UI request.

Available commands are:
Command Description Example
.x <Mode_A_Code> sets your transponder Mode A code to the specified value .x 2000
.c1 <frequency> sets the COM1 frequency to the chosen frequency in the command .c1 126.450
.c2 <frequency> sets the COM2 frequency to the chosen frequency in the command .c2 122.000
.metar <ICAO>
.wx <ICAO>
Request a METAR of ICAO code airfield (weather information) .metar LFRS
.wx EDDL
.taf <ICAO> Request a TAF of ICAO code airfield (weather information) .taf KJFK
.wallop <Request help message> Request help in IVAO network from supervisors .wallop I cannot contact EDDF_APP with my client.
.chat <Callsign> Initiate a private message with a pilot, an ATC, an observer, a supervisor identified by its own Callsing .chat LEMD_APP
.atis <ATC callsing> get Datalink ATIS from the ATC callsign connected .atis SBBR_TWR
.help display the onboard command help in the text command window .help


A built in help command is available by typing command .help in the scratchpad.


Example of METAR command in scratchpad area to be sent by user: (please read article about METAR coding for more information)

Swpilot req metar.png


Example of a WALLOP call (a wallop call is a message for a supervisor in order to request help)

Swpilot req wallop.png


All commands can be typed on the scratch pad or in any scratch pad of private messages.

The Auto-Unicom Feature

The button “AU” is the Auto Unicom feature which it is an onboard tool for auto information on the Unicom frequency tool.

It contains a list of predefined messages for each phase of flight.
The Auto-Unicom feature opens after pressing the "AU" button.

Swpilot scratchpad.png


Note: When the Button is light grey like the example above, the function is not available. You should connect and file a flight plan in order to activate it.

Example: Auto Unicom specific window opens for the first time (all fields empty):

Pilotclient auto unicom.png


Please consult the Auto UNICOM Module documentation to get more details about each phase of flight and its usage.



Transponder panel

Below the Text panel, there is the Transponder panel (XPDR).

In the transponder panel, you will see the following information:
  • 4 digits Mode A Transponder code (named squawk code)
  • 2 position Transponder Mode
    • Mode STDBY ( standby mode)
    • Mode TX (transmission mode which is sometimes TA or TA/RA mode in some aicraft)
  • ID button: which starts an IDENT procedure requested by ATC.
Pilotclient sqtx2000.png


On the image above, you can see that the transponder code is 2000 and transponder mode is set to TX mode and the ID button is inactive.

Pilotclient sqtx4641.png


On the image above, you can see that the transponder code is 4641 and transponder mode is set to TX mode and the ID button is inactive.

Pilotclient sqstby2000.png


On the image above, you can see, that the transponder code is 2000 and transponder mode is set to STBY and the ID button is active (it has been pressed for the IDENT procedure requested by an ATC).

Note: When starting the UI, the transponder code is always set to 2000.

If you want more information about transponders, please consult the Transponder Use article.
Rules: Please set transponder mode according to your phase of flight.
  • transponder mode = STBY when you are on ground on apron or taxiing.
  • transponder mode = TX when you are flying, or taking-off or landing on a runway.
Note that in some countries, the transponder should be set to TX mode when taxiing. Always follow ATC orders in this case.
RULE: Be careful: all values are in octal: there is no 8 and no 9 digit. RULE: Please set mode A transponder code = 2000 before any flight and during a non controlled flight when you do not know the exact rules of transponder codes in your area of flight.



Radio panel

Below the transponder panel, you will find the radio panel.

The radio panel displays your current active COM1 and COM2 frequencies, as well as their associated ATC station names (if available).

The communication channel (COM) status is indicated by the RX/TX button colour:
  • A green RX mark indicates which COM channel is currently used to listen to the network frequency programmed on its channel.
  • A grey RX mark indicates that the COM channel is in Standby.
  • A green TX mark indicates which COM channel is currently used for communication by text and voice to the ATC and/or UNICOM.
  • A grey TX mark indicates that the COM channel is on the standby frequency. You will neither be able to transmit on this frequency by text nor by voice.

Example: COM1 and COM2 are set to 122.800 (UNICOM) and COM1 is the active RX and TX channel with the green marks.

Swpilot com panel unicom.png



Changing frequency on COM channels

When connected to the network, left-clicking on a frequency in each COM in the Radio Panel opens the Quick Tune panel. This action allows you to quickly pick a frequency for the selected COM from the list of known nearby ATC stations.

Example: COM1 frequency is tuned to 119.825 MHz which is the LFRR_CTR ATC frequency:

Swpilot com panel.png


If you left-click on the frequency number, you will open a pop-up menu for automatic tuning by selecting a nearby station:
  • If there is no nearby ATC station, you will find only the UNICOM frequency (see bottom left image)
  • If there are nearby ATC stations, you will find a selection list where you can choose the desired ATC or frequency including UNICOM (see bottom right image)

Example: 2 possible selection lists on COM1 : on the left without any ATC, on the right with one ATC connected:

Swpilot ATC selection list COM1.png


The ATC list is sorted by ATC distance with UNICOM as first selection.
It displays only an ATC list in the reception range of your aircraft in function of its position. (you should not contact New York tower if you are in London!)

If you click the COM1 and COM2 frequency to change it, you will have the same list of ATC available.

Example: Below you can select when connected on ground at Budapest LHBP the following ATC:

Swpilot ATC selection list COM1 COM2.png


Note that when you have tuned to an ATC station, the Selected ATC station will appear on top of the text panel.
Pilotclient top atc selected display.png



Switching frequency between COM channels

By clicking on the TX icon on the frequency panel, you can switch from COM1 to COM2 or from COM2 to COM1.

Example: Before changing COM1 to COM2 frequencies, your radio panel may display two different stations like in the example below:

  • LHBP_E_APP selected as primary frequency
  • LHCC_CTR selected in standby frequency
Swpilot ATC switch step1.png


After switching COM1 and COM2, by clicking the greyed TX on COM2, you will have this configuration:

Swpilot ATC switch step2.png


You can also change the frequency from your cockpit.
Note: Pay attention to the 8.33kHz specific frequencies. Some cockpits inside your simulator are not compatible with these new frequencies. Pay attention that changing frequency by using the UI is mandatory in order to join the adequate ATC. We have implemented a translation module, but it has its limitations.
If the frequency entered in your cockpit does not match with any active ATC in the reception area of your aircraft, no call sign will be displayed (see example below).

Example: the COM2 frequency is selected (122.300) and no ATC is detected on this frequency. Absolutely nobody will hear your text message if you transmit on this frequency:

Swpilot COM2 no ATC in range.png


In this case, no ATC is connected on this frequency or the station is currently too far from your position.

2 different selectable Receiving COM channels

You may have dual RX channels if your simulator and aircraft allows it. You need to click on the second RX button to highlight it in green like in the image below:
Swpilot com panel dual.png


Note that dual RX feature is only available for text messages only due to technical limitations. Dual RX voice is not possible.
Note: Sometimes you may select dual reception inside your cockpit to enable this function.
Aircraft panel dual com.png


Example of a secondary text message received on RX only COM (text only mode):

Swpilot com dual rx.png



Action button panel

The popup button panel is at the bottom of the UI (User Interface).

You will find the following buttons:

  • Connection button
  • ATC selection and information button
  • Private message button
  • Settings button
  • TCAS button
  • Datalink ATIS button


Swpilot online.png



Connection button

When you are not connected, the UI displays the first button with OFFLINE in red.
Swpilot offline.png


When you are connected to the IVAO network, the UI will display the first button with ONLINE in green.
Swpilot online.png


Connecting to the network

You must click on the OFFLINE button in order to connect to the IVAO network.

The popup “CONNECT TO NETWORK” appears and you must fill your information in this window:

  • Your own callsign for the IVAO network
  • Your own VID given by IVAO (example is 100000)
  • Your IVAN password given by IVAO
  • Your real name (Name + Surname)
  • Your selected IVAO server and its port (use default one = 6809)
  • Your voice activation plugin
  • Your aircraft representation for other players connected to the network
  • Your airline or texture representation of previous aircraft available in the database.
Swpilot connection.png

There are also 2 options :

  • Hide ADM/SUP Rating : only works for supervisors (do not select this option if you are not a supervisor)
  • Connect as Observer : only for monitoring the IVAO network or connecting to the network as second pilot for cockpit sharing.

Disconnecting from the network

If you click on the ONLINE button, a disconnect popup is displayed:

  • If you click No, you will remain connected to the network.
  • If you click Yes, you will be disconnected without delay.
Swpilot disconnect fr network.png



Cockpit sharing connection to IVAO

You must respect the procedure for cockpit sharing flights:
  • The first aircraft shall connect to IVAO as a normal flight with the chosen callsign (Example BAX567)
  • The second pilot shall connect as Observer with the same callsign with one more letter ‘M’ as multiplayer. (Example, BAX567M)

Example of a second aircraft connection with BAX567M:

Swpilot connect share cockpit.png
With that specific connection, the MTL/CSL of the main connection is hidden.
Pay attention that the second pilot connection is considered as observer in the IVAO network. His connection hours will not be increased and his connection is never seen by ATC.

ATC popup

When you are online and connected to the IVAO Network, you will have the following menu:
Swpilot online.png


When your are ONLINE, if you click on the ATC button, the ATC popup window opens with the “NEARBY ATC STATIONS” title:
  • If there is no ATC station nearby your position, you will find only the UNICOM channel on this popup like the first image on the bottom left.
  • If there are ATC stations nearby your position, you will find the UNICOM channel, and all ATC channels listed below sorted by distance like the second image on the bottom right.
Swpilot nearby atc station.png
Note: If you are not online (offline), you will never see any ATC.
When you select an active ATC in the list, you can choose one of the following actions:
  • initiate a private chat by clicking on MESSAGES
  • set ATC frequency to COM1 by clicking TUNE COM1
  • set ATC frequency to COM2 by clicking TUNE COM2
  • get ATC ATIS by selecting the REQ. ATIS
Swpilot ATC nearby station selection.png
See Datalink-ATIS area for the output result of the REQ ATIS command.


If you want to know more about the ATC position responsibilities, please read the Air traffic control position documentation.

The private message popup window (CHAT)

When you click on the MSG button, you will open the private message popup window.
This messages popup window allows you to visualize and exchange private messages with other members of the network.
Each time you receive a new private message, a specific sound is played and the MSG button is blinking in red, in order to indicate that you have received new message(s):

New icon.jpg

Altitude MSG tab RED.png



When you click on the MSG button, it will display the channel of the last private message received automatically (in my example IVAO-DM1):
Pilotclient private message DM1.png


The drop-down panel of the message popup window lists all your current private conversations, and allows to select one for reading and/or sending messages to that conversation.

If you click on the white triangle or inside the selection bar, you will display a list of open channels with you (see image below):

  • each line will correspond to one private chat or communication channel
  • the communication channel can be established with an active pilot, an active ATC, an observer or an IVAO staff member who are connected to the network.
  • the 'X' sign in front of each callsign is the closing communication switch (meaning that if you press the 'X', you will lose all the history of the chat).
  • the dot sign in front of each callsign represents the activity of the channel. If the dot colour is light blue, it means that this channel has received one new communication that you have not read yet.

On the example below, we have a chat open with:

  • IVAO-DM1 (Observer Staff) (callsing starting with IVAO are HQ IVAO staff people)
  • AFR220 (Pilot) (channel has a non read message received and is ready to be read)
  • BAW8549 (Pilot)
  • KIKK_TWR (ATC)
Pilotclient chat list.png
In order to select one specific channel, just click on the desired callsign to communicate with, then it opens the chat window with this specific callsign.
Pilotclient private message DM1.png


Note : You can initiate a new chat manually by using the dot .CHAT <Callsign> command in the Scratchpad of the Text panel.
All private messages will follow the same rules as those for the text panel (prefix usage).
Note : When receiving an incoming message, the UI interface will switch automatically to the incoming message channel after pressing the MSG button.

Communication Text displayed inside the simulator

The messages received on your main frequency, all the private messages and system messages are also received inside your flight simulator.

If you fly FSX / P3D, the messages are displayed with a green bar by default.

If you fly X-plane, the messages will be displayed in a transparent window which must be activated first through the following process:

  • Activate the window
Swpilot xplane settings.png


  • Verify that the window is displayed
Swpilot xplane output text.png



Settings popup window

The settings popup window is the area to set up your User Interface for specific actions, display or configuration.

There is only one setting available : the tagging setting which drives the aircraft callsign above or below the MTL / CSL. This setting is not real but it can help to communicate with pilots on the UNICOM frequency.


TCAS button

When pressing the TCAS button, the TCAS window popup will appear.
The TCAS is the onboard Traffic Collision Avoidance System provided by the UI interface.

Example: By default the TCAS system is disabled (STBY mode):

Pilotclient tcas off.png


The TCAS modes, selected on the bottom left, are:

  • Standby mode - STBY ( TCAS is deactivated )
  • Traffic Advisory mode - TA ( This mode alerts the pilot through a collision alert sound only )
  • Traffic Advisory and Resolution Advisory mode - TA/RA ( This mode alerts the pilot through collision information and gives resolution clearances that the pilot shall comply with without delay)

Example: After clicking on the STBY button, the TCAS system is set to the TA mode:

Pilotclient tcas on.png

Example: After clicking on the TA button, the TCAS system is set to the TA/RA mode:

Pilotclient tcas tara.png

Note in both images above, traffic is displayed at -200ft from your vertical position (relative altitude)



There are 2 button for display configuration for this TCAS:
  • Top left button = Horizontal Visibility Range  : Available ranges are 3NM, 5NM, 10NM, 15NM, 20NM or 40NM
  • Top Right Button = Vertical Visibility Range  : Available ranges are NORM, ABV, BLW , ALL
The Vertical Visibility Range definition is:
  • NORM: traffic at +/- 2700 ft is displayed
  • ALL: all traffic within the TCAS range is displayed
  • ABV: traffic within the interval (-2700, +9000) ft is displayed
  • BLW: traffic within the interval (-9000, +2700) ft is displayed

New icon.jpg

There is one sound mute function available for TCAS by using the bottom right button.
More information about TCAS can be read in our documentation center this documentation

Datalink ATIS

When pressing the D-ATIS button, a new window opens the Datalink ATIS (automatic terminal information service ) feature to manage ATIS messages like in some aircraft systems.


If you want to know more about ATIS, please read the ATIS article first.
Note : At IVAO we only have text ATIS for the moment, as voiced ATIS is not implemented and ATIS is not associated by a separate frequency today. So the IVAO pilot software implements the Datalink ATIS for all aircraft.

After you pressed the D-ATIS button, the Datalink ATIS window is displayed like the image below, which represents the Datalink ATIS when you do not have any active flight plan or you are disconnected.

Pilotclient datis offline.png


After you have been connected to the IVAO server, and the flight plan was correlated with your callsign and flight plan server, the Datalink ATIS will show the windows like in the example below:
Note: At the top, you may find 2 to 4 ICAO airfield codes from your flight plan:
  • First airfield is the departure airfield
  • Second airfield is the arrival airfield
  • Third airfield is the first alternate airfield
  • Fourth airfield is the second alternate airfield

Example: flight plan OJAI to OBBI with 2 alternate airfields OEDF and OTHH:

Pilotclient datis fpl ok.png


Example: A flight plan LFMP to LEBL without alternate airfields declared:

Pilotclient datis no alternate.png


If you click on one of the departure, arrival or alternate ICAO codes, there are 2 cases:
Case 1: If there is no ATC connected on this selected airfield, then it displays an empty ATC list.
Pilotclient datis atcstation empty.png


Then you cannot request any ATIS from this ICAO airfield. You should check for another ATC position which can take your departure, or start your flight by using auto-information on UNICOM if there is no other ATC station (check METAR for weather information).
Case 2: There are one or several ATC stations connected on this selected airfield, then it displays an ATC station list and you can choose the desired ATC from the list displayed:
Pilotclient datis lirp atisrequest.png


After selecting the chosen ATC in the list, the Datalink ATIS will display the ATIS information:
Pilotclient DATIS LIRP ATIS catched.png


Note that the ATIS of each station is displayed after a separation line "---------------------".
In order to get one ATIS from any desired ATC station, you should write in the scratch-pad area of the Airport ICAO, the desired ATC position:

Example: Step 1: You want to request any ATC connected on SBXS:

Pilotclient datis ICAO req.png


Example: Step 2: After ICAO code validation, the UI will display the ATC list available on this position (here is one ATC station only = SBXS_APP):

Pilotclient datis ICAO req2.png


Example: Step 3 : After selecting the SBXS_APP position, the UI will display the SBXS_APP ATIS after the separator line.

Pilotclient datis ICAO req3.png


Note: You can browse all the Datalink ATIS data with your mouse central wheel.
If you type the dot command .ATIS on the main frequency scratch-pad, the ATIS will be displayed in the Datalink ATIS area.
After command validation, the D-ATIS button is blinking if there is any output available. The button is blinking until you click and select the D-ATIS window.
Pilotclient DATIS button.png
After clicking the D-ATIS button, you can read your desired ATIS (see example SBXS_APP).
If there is no ATC station connected on this position, D-ATIS will not blink and there is no input.

Customize the UI sounds

New icon.jpg

To customize UI Sounds, put a new .wav file with following name in the subdirectory \sounds where PilotUI.exe is located:
Note: The sounds sample rate shall be set maximum to 24bit. Altitude is not compatible with 32bit sample rate.
  • connect.wav: connected sound
  • disconnect.wav: disconnected sound
  • freq.wav: incoming frequency message
  • freqme.wav: incoming frequency message directed to me
  • private.wav: private messsage
  • wallop.wav: wallop
  • forceact.wav: force ATC notice
  • broadcast.wav: broadcast sound
Note: If you want to deactivate one sound (example: incoming message on frequency not for me), with you notepas just create an empty text file and rename or save it as the chosen name above (example: freq.wav)



Supervisor commands

Supervisor commands are implemented in the IVAO Pilot software.

  • All wallop messages will be received in a separate private chat named [WALLOP] (see below).
  • Each new incoming wallop message will produce a specific sound, different from private messages.
  • Every message written in this specific WALLOP tab will automatically send wallops without typing the specific command .wallop
Swpilot supervisor.png


Here is the list of available commands for supervisors:

Command Description
.info <Callsign> request connection information from a member connected as Callsign
.kill <Callsign> <Reason message string text> kill a member connected as Callsign with a reason inserted (reason is mandatory)
.broad <Message> Send a broadcast message to all members
.wallop Send to other supervisors a message for chatting to all supervisors or acknowledge a wallop.


Warning: If you type the .kill command without inserting a reason, an error popup is displayed:
Swpilot kill error.png


The option Hide SUP/ADMIN Rating is available in the connection window in order to show you as Supervisor online in Webeye.



See also

Reference

Author

  • VID 150259 - Creation

DATE OF SUBMISSION

  • 11:42, 10 March 2020

COPYRIGHT

  • This documentation is copyrighted as part of the intellectual property of the International Virtual Aviation Organisation.

DISCLAIMER

  • The content of this documentation is intended for aviation simulation only and must not be used for real aviation operations.