[{"content":"Installation Download and run the vatSys installer, which is available here.\nThe vatSys installer will download and install the any missing required Microsoft .NET Framework and Visual Studio Redistributables.\nIn addition to the required core files, vatSys will create a new folder in My Documents that will be the home of all user customisable data (Navigraph Navdata, Profiles, Sounds).\nSelect a Profile The first time you run vatSys, you will be asked to select a profile. A profile for Australia is included by default. Select the desired Profile.XML file when prompted.\nvatSys will then load all the data associated with that profile.\nThe Main Menu Bar  Settings | Windows | Maps | Tools | Messages | Info\n The menu bar is used to access and configure vatSys. The first menu you will wish to use is Settings.\nConfigure Audio Configure your audio by selecting devices for your Headset, Speakers and Microphone in the Audio Setup Window:\n Settings -\u0026gt; Audio\n Select a Position Each \u0026ldquo;Air Situation Display\u0026rdquo; is linked to a particular control position. Positions are defined in the profile data and make your life easier by loading the appropriate Maps, Frequencies, Callsign and more.\nTo select a position:\n Settings -\u0026gt; Position -\u0026gt; (Position Name)\n Connect to VATSIM You are now ready to connect to VATSIM:\n Settings -\u0026gt; Connection\n ","id":0,"tag":"","title":"Quick Start","url":"/docs/quickstart/"},{"content":"Overview This page will walk you through the Human-Machine-Interface (HMI) interactions required for processing a typical flight. To keep it simple, we\u0026rsquo;ll assume you\u0026rsquo;re operating a Centre position providing top down coverage to a few airports.\nThe basic steps will look like this:\n Pilot Submits Flight Plan -\u0026gt; vatSys creates a flight data record (FDR)\n  Pilot calls for clearance -\u0026gt; controller \u0026ldquo;activates\u0026rdquo; the flight data record (FDR) and enters clearance data\n  Pilot departs -\u0026gt; if on radar, the FDR will automatically couple. If not - controller records departure\n  Flight proceeds -\u0026gt; controller keeps the FDR up to date with any changes to cleared level, route, SID/STAR, etc.\n  Pilot arrives -\u0026gt; if on radar, the FDR will automatically finish on landing. If not - controller \u0026ldquo;finishes\u0026rdquo; FDR\n Flight Data Record (FDR) and Strips The flight data record is a record of extrapolated information which is derived from the pilots Flight Plan.\nFDRs are not mandatory for the processing of traffic, however they ensure that everyone is operating on the same page by synchronising data related to the flight plan.\nYour main interaction with FDRs will be through flight progress strips. The more comprehensive (and slower) way to interact with an FDR is through the Flight Plan Window.\nWhenever an FDR is created, vatSys checks to see if that flight may be relevant to the airspace you are responsible for. If it is relevant, you will be shown a Strip for that FDR. The strip will start \u0026ldquo;Preactive\u0026rdquo; (white colour).\n When a pilot calls for the first time, these are the strips you should look at.\n Activating a FDR When a pilot calls for clearance, find the corresponding Preactive strip.\nFor APP/DEP positions, this will normally be in a \u0026ldquo;ADEP XXXX\u0026rdquo; window corresponding to the main aerodrome serviced. For a CTR position, this will be in the \u0026ldquo;Preactive\u0026rdquo; window.\n To activate the FDR, either left click on the \u0026ldquo;State\u0026rdquo; indicator bottom left of strip or select the \u0026ldquo;activate\u0026rdquo; option from the callsign dropdown menu.\n Should you accidentally activate a FDR, you may revert the FDR to Preactive in the Flight Plan Window.\nActive FDRs Once an FDR is active, it changes from Preactive state (white) to Announced (blue). Announced is used to show aircraft that will be of concern to you. These may be aircraft that haven\u0026rsquo;t departed yet (for instance, you\u0026rsquo;ve provided them a clearance but they are still on the ground) or they may be aircraft coming from another sector under the control of another controller.\n Active FDRs are eligible to couple to a radar track should one squawking the correct code be seen in the right spot.\n Clearances may be entered through the strip, the label or the flight plan window. Clicking the various boxes of the strip will reveal options for recording SID, RWY and CFL for a departure.\nOn departure, if the aircraft is in your volume of airspace, it will automatically become your \u0026ldquo;Jurisdiction\u0026rdquo; (Green). Jurisdiction is used to show aircraft that you are in control of directly.\nHandoffs Propose a handoff to another controller by selecting \u0026ldquo;Handoff\u0026rdquo; from the callsign drop down menu. Handoffs out of your airspace will be solid orange. Handoffs in to your airspace will flash orange.\nFinishing FDRs If an FDR is coupled when the pilot lands, it may automatically finish. Finished FDRs will no longer provide you with a strip, however you can still access their FDR through the Flight Plan Window.\n To manually finish an FDR, select \u0026ldquo;Finish\u0026rdquo; from the callsign drop down menu.\n ","id":1,"tag":"","title":"Flight Thread","url":"/docs/flightthread/"},{"content":"Overview This page will walk you through the various information and options presented to you through the main menu bar at the top of the vatSys screen.\nClock Displays the current UTC time. You may set an alarm as a reminder by left clicking the time. To cancel or ackowledge an active alarm, use middle click.\nPosition \u0026amp; Prime Frequency Displays the currently selected position and selected Prime Frequency.\nWhen connected to VATSIM, the Position field will be inverted colour. Prime frequency of 199.998 indicates you have not yet set a frequency.\nRange Displays the current screen range from left to right extent in Nautical Miles. You may enter a new range and set using the Enter key.\nSettings The Settings menu provides access to every configurable aspect of the client, including Connecting to VATSIM.\nMore information on the various options within this menu is available here.\nWindows The Windows menu provides access to every type of window that can be displayed, including the ATIS Editor for creating a Voice ATIS.\nMore information on the various options within this menu is available here.\nMaps The Maps menu provides access to display or hide the display maps for the current window, as well as to create or edit user created maps.\nMore information on the various options within this menu is available here.\nTools The Tools menu provides access to every tool available for interacting both with the current window and the selected aircraft track or strip.\nMore information on the various options within this menu is available here.\nMessages The Messages menu provides access to System Messages, Controller Messages, and Private Messages.\nInfo The Info menu provides access to aeronautical information such as Weather and NOTAMs.\nMore information on the various options within this menu is available here.\n","id":2,"tag":"","title":"Main Menu Bar","url":"/docs/menubar/"},{"content":"Overview The Settings menu provides access to every configurable aspect of the client such as connection settings, position switching, sector assignment, restricted area configuration, input devices and various global settings that affect both processing and display of data.\nConnection The connection menu item opens the Connection Window. From here you can connect to VATSIM.\nCallsign, Position, Range and Controller Info are loaded from your selected Position\nChoosing a VATSIM position (CTR, FSS, etc.) will update the Range options available and automatically select the second highest value. You can return to the Connection Window at any time to update Range and Controller Info.\nPosition The position menu item allows you to select from a pre-defined list of control positions contained with the profile loaded by vatSys.\nSelecting a position from this list will adjust the display centre of the main Air Situation Display, load Maps, and open Windows appropriate to that position.\nIf you are currently offline, selection of a position will also update Connection Window fields and select the correct Sectors.\nSectors The sectors menu item opens the Sector Configuration Window, which allows you to choose which volumes of airspace you are responsible for.\nSectors must be selected to ensure that vatSys presents information relevant to your control position. Such information includes the track states (colours), strip postings (which strips appear) and the application of appropriate safety net alerts (Conflicting alerting, etc.).\nSectors should always be chosen, even if they don\u0026rsquo;t correspond directly to your control position. For example, a Tower without it\u0026rsquo;s own airspace should choose the Approach airspace to ensure strips and colours are available.\nAirspace Volumes\nAirspace is divided into three dimensional volumes and then those volumes are assigned to Sectors.\nSectors may be defined as parents of other sectors. Parent sectors allows easier selection of grouped airspace.\nSelecting Sectors\nSectors may be moved between Available Sectors and Controlled Sectors by first selecting the sector and then using the arrow button to swap sides.\nParent sectors are indicated by the * character following the sector name. Selecting one of these sectors will expand to show the children sectors also being selected.\nControlled Sectors will update automatically in two situations:\n When a new Position is selected while offline When another controller who is the defined owner of that airspace connects  Restricted Areas The restricted areas menu opens the Restricted Area Setup Window, which allows you to configure the activation and display of defined restricted and danger airspace.\nAreas may be filtered by type using the top drop down menu. Areas that are currently active are shown in inverse colour. Select an area from the list box to modify its parameters.\n   Parameter Function     Lower Level The vertical boundary (lower) in hundreds of feet. Used for alert processing.   Upper Level The vertical boundary (upper) in hundreds of feet. Used for alert processing.   DAIW Checkbox to enable / disable alert processing.   Map Line The appearance of the restricted area map line when area is active.   Activation Times Multiple lines for entry of Start and End times. Area is considered active if the current time is between any pair of Start and End times. End time may be set to 2400 to indicate H24 activity. If a visible map line is selected, the map will appear 15 minutes prior to Start time.    Visibility Centers The visibility centers menu allows you to switch between automatic visibility center point selection and manual visibility point selection.\nAutomatic visibility center points are choosen to cover as much of your display range as possible for the choosen range value in Connection settings. Visibility points are updated every time you Store a new display center. You can view the current points by selecting the Show Vis Centers menu item (also available in Tools).\nSelecting Manual visibility center point selection opens the Visibility Centers dialog window.\nFrom this window you can manipulate the 4 available visibility center points.\nLEFT or RIGHT CLICK - Allows you to graphically set the choosen points location on the main display\nMIDDLE CLICK - Clears the choosen point\nSelection of a manual visibility point disables Automatic visibility center logic.\nDisplay The display menu item opens the Display Settings Window, which allows you to configure Air and Ground situation display properties.\n   Graphics      Scale Marker Toggles display of the range scale marker (shows 6NM by 10NM)   Compass Rose Toggles display of compass headings   ATC List Toggles display of online ATC List   2nd ASD ATC List Toggles display of online ATC List on popup Air and Ground Situation display windows   Filter Non-ATC Toggles filtering non-ATC positions from all online ATC Lists    Label Font Size\nAdjusts the size of font used for aircraft and map labels.\nLeader Length\nAdjusts the default length of the leader line linking aircraft labels and tracks.\nBrightness\nAdjusts the brightness of various map and track colours on a sliding scale.\nAudio The audio menu item opens the Audio Settings Window, which allows you to configure audio device selection and volumes.\nSelect devices from the drop down menus. Whenever choosing a different microphone device, you should adjust the Input Volume Adjustment such that normal speech registers in the green section.\nAir-Ground and Ground-Ground Volume Adjustments alter the output volumes.\nAlert Tone Volume adjusts the volume of aircraft and system alerts. VSCS Tone Volume adjusts the volume of VSCS alerts, such as hotline and coldline chimes. Selection of 0 on either slider disables the respective tones.\nEmulation options show the currently set VHF Emulation preset as defined for the loaded profile, and a togglable option to enable or disable realistic HF emulation (HF Squelch) that is enabled when not connected to the network.\nAdvanced toggles the display of an expanded panel to configure multiple input and output devices. Configure up to 4 additional inputs and outputs, which are mixed with the selected Main Input and Output devices. Toggle Speaker? for vatSys to treat the output as a Speaker device (responds to speaker buttons on VSCS).\nNote: The Adding or Removing Additional Audio Devices and toggling Realistic HF emulation can only be done when not connected to VATSIM\nKeyboard The keyboard menu item opens the Keyboard Settings Window, which allows you to configure shortcut keys for various actions.\nKey Settings\n  Display   Comms   Tracks   Tools       Display Action     Default Resets the display to the center and range defaults defined for the selected position   Store Stores the current display center and range for easy restoration   Restore Restores previously stored display center and range   Offcenter Shifts the display center to the current cursor location   Recenter Resets the display center to the previously stored center location   Pan Up Shifts the display north   Pan Down Shifts the display south   Pan Left Shifts the display west   Pan Right Shifts the display east   Range Inc Increase display range by 10%   Range Dec Decreases display range by 10%        Comms Action     Push To Talk 1 VSCS Push To Talk (Joystick or Mouse Button, or Key)   Push To Talk 2 Alternative VSCS Push To Talk (Joystick or Mouse Button, or Key)   Push To Talk 3 Alternative VSCS Push To Talk (Joystick or Mouse Button, or Key)   Push To Talk 4 Alternative VSCS Push To Talk (Joystick or Mouse Button, or Key)   Mic Mute VSCS Toggle Coordination Input Mute (Joystick or Mouse Button, or Key)   Push To Mute VSCS Push To Mute Coordination Input (Joystick or Mouse Button, or Key)   Quick Text Switches VSCS page to Text        Tracks Action     Accept Accepts the selected track   Handoff Opens the Handoff Window for the selected track   Inhibit Inhibits the selected track   Quick Look Quick Looks the selected track   Route Toggles display of the graphical route for the selected track   Reroute Initiates graphical reroute of selected track   SRP Toggles display of the Short Route Probe for the selected track, or globally if no track selected   UPR Repositions selected Flight Plan Track to the cursor position along the flight plan route        Tools Action     Bearing Range Creates a new Bearing and Range Line   Conflict Area Initiates the Conflict Area Tool for the selected track   Closest Apch Initiates the Closest Approach Tool for the selected track   Hide Routes Hides all displayed graphical routes   Find Opens the Find menu   Contact Me Opens the Contact Me menu for the selected track   Text Area Creates a new text area at the current cursor location   Add LatLon Displays the latitude and longitude at the current cursor location   Clear LatLons Hides all displayed LatLon points   GRIB Opens the GRIB Window at the current cursor location     Lists The lists menu item allows you to configure List Window options, such as the arrival lists.\nHide Unknown Flights - when toggled, aircraft outside of your visibility range are not shown above the bar in List Windows.\nStrips The strips menu item allows you to open the Strip Setup Window and restore hidden strips.\nStrip Setup Window\nThe Strip Setup Window allows for the configuration of all Strip Windows.\n   Strip Sort Mode      Alpha Alphanumeric sort of callsigns   Time Time sort based on sector entry time or departure time if departing within sector   Level Level sort based on Cleared Flight Level       Strip Window Mode      State Strip Windows are organised by current Track State (Preactive, Announced, etc.)   Beacon Strip Windows are organised by defined beacons, waypoints or airports. Flights of at least Preactive state with the defined beacon point in their route will appear in the window, or if none of the points are contained, appear in a generic OTHER Strip Window.    Strip Windows may be opened or closed from this Window.\nBeacon points may be defined by toggling one of the Define ... buttons and selecting one of the 5 available POINT slots. Type the name of the point and press Enter to complete.\nThe Reset button resets all parameters to those defined for the currently selected Position.\nRestore Hidden Strips\nSelecting this menu item will restore any strips that were manually hidden to the strip windows.\nGRIB Winds The GRIB winds menu item allows toggling the application of the GRIB forecast in trajectory calculations.\nDisable Globally - when toggled, disables the use of GRIB forecast winds and temperatures when calculating the flight plan trajectories of all aircraft.\nNavigraph The Navigraph menu item allows linking of a Navigraph account within vatSys for up to date global navigation data.\nLink Navigraph Account / Unlink Navigraph Account - this menu item will open your web browser to either sign in or out of your Navigraph account. Check for Updates - Must have a linked account. Checks Navigraph servers for updates to the currently installed global navigation data. vatSys will automatically check for updates on launch.\nCheck For Updates The check for updates menu item checks the vatSys server for Application updates. vatSys automatically checks for updates on launch.\nChange Profile The change profile menu item allows the switching to another vatSys profile by closing vatSys and opening the Select a Profile Window.\nNote: Holding the SHIFT key when opening vatSys will also bring up the Select a Profile Window.\nSelect a Profile\nvatSys Profiles contained within Documents\\vatSys Files\\Profiles will be listed for selection. You may browse to other profile locations using the Browse button.\n","id":3,"tag":"","title":"Settings","url":"/docs/settings/"},{"content":"Overview The window menu provides you with the ability to manage the windows that you want to see, and what type of window it is.\nWhen you move a window around on your screen, it\u0026rsquo;s position is persisted by vatSys and it should open up in the same location next time you start the application.\nArrival List The Arrival List window allows you to see the FDR\u0026rsquo;s that are inbound to the selected airport. You can open an arrival list for any airport by selecting Arrival List -\u0026gt; Open New and then enter the ICAO code in the field and press ENTER on your keyboard. It is possible to open multiple arrival lists.\nThe arrival list will open with all arriving aircraft appearing above the blue separator (see below).\nThis list is typically used by a flow controller to show the arrival sequence into an airport, however you can click and drag the FDRs in the list into any order you wish. The arrival list takes into account the flight plan track, so the ETA for landing will be inaccurate until an appropriate STAR has been assigned in the FDR. By clicking on the RHS of the strip, notes can be added by the flow controller (more information about this is covered in Tips). These notes can also be adjusted in the flight plan strip (Jurisdiction Window).\nAll notes, and the order of FDRs in the arrival list are synced between vatSys clients.\nGround Window The Ground Window will enable you to see all traffic on the ground that is being picked up by the Surface Movement Radar (SMR) at an aerodrome. This radar requires that an aircraft transponder be Mode C at all times when the aircraft is moving and just prior to pushback. The Ground Window can be rotated as if being viewed from the position of the real-world tower (this is at the discretion of the data provider).\nYou can pick which aerodrome you want to view, by selecting the ICAO code from the dropdown list. It is possible to open multiple ground windows.\nIf taxiway designators have been defined, they can be viewed by selecting the menu item in the list.\nIf an aircraft is not squawking Mode C or the assigned code, it will show as an orange diamond.\nIf the aircraft is squawking mode C and the assigned code, it will show the callsign.\nOverflying aircraft will show on the SMR as purple tracks.\nAir Window The Air Window allows you to open additional Air Situation Displays (ASD). Select what position you want to view from the dropdown, and make any normal adjustments to maps (see map documentation). It is possible to open multiple ASDs.\nATIS Window The ATIS Window is where all ATIS management is conducted.\nTo edit or create an ATIS, click Editor. This will open the ATIS Editor Window.\nStart by typing the ICAO code of the aerodrome for which you wish to open an ATIS. The frequency (if defined in the data profile) will automatically populate. Click Create.\nSelect the voice you wish to broadcast with, the rate (medium is standard) and if the METAR hasn\u0026rsquo;t loaded, click Load METAR. Enter the ATIS data with appropriate abbreviations - these can be defined in the profile by your division and would be found in your local Manual of Air Traffic Services.\nClicking the next button, increases the ATIS letter identifier to the next letter.\nClick save, to persist your ATIS. Click listen, to preview your ATIS.\nOnce ready, click broadcast to play your ATIS on VATSIM.\nThe wind calc window allows you to determine a crosswind component (if applicable).\nvatSys will always be listening for new METAR updates. If a new METAR is detected with changes, you will hear a DONG DING and the ATIS window will flash yellow.\nApplicable changes will be highlighted yellow and the ATIS will automatically increase the letter identifier. If you want to accept the changes, click save and broadcast. If you don\u0026rsquo;t want to accept the changes, click cancel, and the ATIS will remain the same.\nTo view your ATIS (or other ATIS), under the Window Menu, click ATIS -\u0026gt; Request and then type the ICAO code of the airport. The ATIS window will open and display the current ATIS in text format. This will automatically update and show any ATIS changes with a + prior to the information.\nFlight Plan Window The flight plan window allows you to create and edit flight plans. You can search for flight plans by typing the callsign and pressing RETURN on your keyboard. You can also create a flight plan for a user, if they have not done so.\nThe flight plan window will become populated if you search for a valid callsign, or click to view the flight plan from the on-screen tag.\nIf you need to modify the flight plan through this window (which is not preferable but sometimes required), then click modify and you will be able to edit all of the fields. Once modifications are completed, press RETURN to persist the changes.\nYou will also be able to edit items like CFL, runway, SID/STAR, view the ownership/state of the flight plan and activate/deactivate/depart the FDR.\nStrip Windows Individual strip windows may be opened using these menu items.\nStrips are explained here.\n","id":4,"tag":"","title":"Windows","url":"/docs/windows/"},{"content":"Overview This page will walk you through the settings available to you in the Maps Menu.\nAny maps that have been defined by your local division in your profile will be displayed under the map menu.\nDynamic Infill This will enable or disable the differential colours that allow you to view your current active sectors.\nTerrain Heights This will display terrain heights.\nMaps Maps are automatically selected based on the selected Position, but may be toggled individually by selecting the corresponding menu item.\nProfiles may group maps into folders, and this structure is preserved in the menu. If a visible map is within a folder, this folder will be expanded automatically on menu opening.\nThe menu will remain visible on item selection to enable fast change of multiple maps.\n","id":5,"tag":"","title":"Maps","url":"/docs/maps/"},{"content":"Overview This page will walk you through the tools available for interacting with the vatSys display and aircraft Tracks. Tools may be accessed through the Tools menu, Callsign menu or Keyboard commands. Tool behaviour may change based on the type (or lack) of aircraft track selected.\n   Abbreviation Accessed Via     TM Tools Menu   KC Keyboard Command   CM Callsign Menu    Key commands may be viewed here.\nVelocity Vectors TM\nVelocity Vectors display where a Radar/ADSB track is projected to be after a certain time based on derived ground speed and ground track. This will show as a straight line as per the selected range in time for all surveillance tracks, with minute intervals marked along the line.\n   Velocity Vector       Range - A list of options in minutes with the default being 2    Short Route Probe TM\nShort Route Probe function projects a line from an aircraft track along the flight plan route. To be eligible for SRP, the track must be a flight plan track or a coupled radar/ADSB. SRP can be displayed either as a time value, or a distance value. You can turn this function on by selecting an individual aircraft and pressing the SRP assigned key (default key = multiply). To display globally (all aircraft), click \u0026ldquo;Default On\u0026rdquo; in the SRP drop down options.\n   Short Route Probe       Time - A list of options in minutes with the default being 5    Distance - A list of options in nautical miles    Default On- Enable SRP globally (all aircraft)    History Trails TM\nHistory Trails display past radar/ADSB updates for each track. Up to 9 past updates may be selected.\n   History Trails       Range - A list of options up to 9 past position updates. Default setting is 5    FPASD TM\nFlight Plan Air Situation Display toggles the display of Flight Plan tracks on ASDs. Default on.\nIf deselected, only radar / ADS-B tracks are presented. Strips are unchanged.\nExtended Labels TM\nExtended labels toggles the global display of the extended label line, if defined, in labels when the track state is at least Announced.\nExtended labels may also be toggled invidivually using the label clickspot.\nShared Labels TM\nShared labels toggles the display of timeshare label data lines. Default off.\nWhen selected, Air and Ground track labels that contain timeshared lines will display alternating information every 4 display updates (2.4 seconds).\nSSR Callsigns TM\nSSR Callsigns displays the SSR code being transmitted by the aircraft instead of their callsign. When enabled this displays globally (all aircraft labels).\nDisable Filters TM, KC\nDisables all current filters (level, airports).\nFilters TM\nFilters hide aircraft labels of non-concerned tracks based on a specified altitude range in order to reduce label clutter.\n   Filters       Lower Level - 3 digit selection for lowest visible level    Upper level - 3 digit selection for highest visible level    Inhibited List TM\nInhibited list displays flight plans that have been inhibited. Selection of a flight plan from this list will uninhibit that flight plan.\nGraphic Reroute KC, CM\nGraphic Reroute is an interactive function that allows the cleared route to be drawn on the ASD.\nThe reroute may commence from the aircraft Track or any existing downstream flight planned waypoint. Subsequent LEFT CLICK will add waypoints to the reroute, or Lat/Long positions if the cursor location is not near to a waypoint. Reroute will complete without confirmation on joining either a downstream waypoint or the Destination airport.\nMIDDLE CLICK will cancel an in progress reroute with no change to route.\nUser Position Report (UPR) KC\nUser Position Report updates route estimates for uncoupled FDR\u0026rsquo;s to position the Flight Plan Track at the mouse cursors location. Cursor must be positioned over the desired point of the route (forwards or backwards) before executing the key command. There is a 5 second timeout after the use of this function to reduce the number of synchronising messages being sent over the network.\nQuick Tag TM, CM\nQuick Tag provides the ability to label un-coupled radar/ADSB tracks locally to your client only. Limited label functions are then possible without any flight plan interaction. Adding a Quick Tag will allocate a discrete SSR code enabling re-coupling should the aircraft leave surveillance coverage. After 5 minutes of not being coupled, the Quick Tag is automatically removed.\n   Quick Tag       Add or Remove - adjusts the label as selected    Bearing and Range Line TM, KC\nBearing and Range tool displays a bearing in degrees (Magnetic only if defined for current Position), range in Metres for Ground Situation Displays otherwise Nautical Miles, and a time to go in minutes when anchored on a track. Time to go is given as a 4 digit UTC time when both ends are anchored.\n   Bearing and Range           Conflict Area TM, KC\nConflict Area Tool determines the area that two flight plan routes are in lateral conflict. Select one track and click on the other. The drop down values are defined in the current profile and correspond to the required minimum lateral distance between the two routes. On successful calculation of a conflict area, the area with entry and exit times for both aircraft is displayed.\nTo clear a displayed conflict area, MIDDLE CLICK either callsign time label at the entry/exit point.\nClosest Approach TM, KC\nClosest Approach tool displays the point at which two flight plan trajectories are closest. Select one track and click the other to display closest approach trajectory.\nNote: Whilst surveillance data is used to update flight plan trajectories, this tool is not using current radar/ADSB data.\nTo clear a displayed closest approach point, MIDDLE CLICK the text label.\nDisable GRIB Winds TM, KC\nDisable GRIB Winds disables the use of GRIB winds and temperatures for individual flight plans. A track must be selected for this to feature to be available.\nGRIB Winds may be disabled globally in the Settings menu.\nSELCAL TM\nSELCAL (selective calling) opens the SELCAL Window, for the sending of HF/VHF SELCAL tones. If a track is selected with SELCAL code present in their flight plan, the Window will be initialised with this value.\nManual code entry will attempt to resolve callsign from the current list of flight plans.\nSend Contact Me TM, KC\nContact Me sends an automated private message directly to a pilot requesting contact on one of your selected frequencies.\nA key command also exists for this function.\nRequest Break TM\nRequest Break toggles the selection of the break indicator to surrounding controllers.\nShow Vis Centers TM\nShow Vis Centers displays the currently set network Visibility points. Display will self time out and cannot be manually removed.\nAdd Text Area TM, KC\nAdd Text Area creates a new text area on the situation display, local to your client. Complete the text field and key Enter to finish.\nRIGHT CLICK and drag to move the text to another location. MIDDLE CLICK to delete.\n","id":6,"tag":"","title":"Tools","url":"/docs/tools/"},{"content":"Overview This page will walk you through the Info Menu.\nAbout A pop up window that displays Version, Profile and Navigraph Cycle currently being used on your vatSys client.\nFind A function highlighting and centralizing your scope for a period of 5 seconds over a name of any point, navaid and airport ICAO code (YSSY) in your operating profile, or any in range flight plan coupled aircraft.\nType a name and press enter.\nThe default key command for \u0026ldquo;Find\u0026rdquo; is F4.\nAIS Request The ability to request live Vatsim METAR, METAR, TAF and NOTAMs for any prompted airport ICAO code in your operating profile.\nSelect a Type of request\nThen type desired airport ICAO and press enter. The request will display in the box below. Left click and select the \u0026ldquo;Display\u0026rdquo; button to transfer request to \u0026ldquo;AIS Display\u0026rdquo; pop up window.\nTo clear a request simply left click and press \u0026ldquo;Clear\u0026rdquo;.\nAIS Display Any AIS request transferred by selecting \u0026ldquo;Display\u0026rdquo; will appear in this pop up window.\nInitial and Updated requests will be displayed as yellow in colour. Middle click to acknowledge. Once acknowledged the request will appear as light grey and remain as \u0026ldquo;history\u0026rdquo; in the display window. To remove requests displayed as history simply middle click again.\nExternal Information URLs are defined for the loaded profile, which can be accessed as items in the Info menu. These items will open in a vatSys browser. A VATPAC \u0026ldquo;Area QNH\u0026rdquo; example is displayed below:\n","id":7,"tag":"","title":"Info","url":"/docs/info/"},{"content":"Overview A track is a graphical representation of an aircraft position, provides essential information about the aircraft and facilitates recording of new information via mouse interaction.\nTracks may consist of a combination of the following features:\n track symbol leader line track label short route probe velocity vector history trails  Track States Tracks can be presented in a number of states. Current state affects the type of track and label shown, and it\u0026rsquo;s colour. Strips are also coloured based on the associated track state.\nTrack state is decided based on combination of flight plan state and the flights relevance to your selected Sectors.\n   State Meaning Track Colour (Default Profile)     Jurisdiction Controlled by you    Announced Soon to affect your sectors (FDR not departed yet or inbound from adjacent airspace)    Handover In Handoff proposed to you (flashing)   Handover Out Handoff proposed by you    Post Jurisdiction Handover Out accepted (flashing)   Preactive FDR has not been activated (strip state only)    Ghost Jurisdiction Controlled by another controller that is also one of your selected sectors (Shadow Mode)    Non Jurisdiction All other tracks     When the invididual quick-look (IQL) tool is used on a track, the colour of the track changes:\n   State Eurocat Australia Colour (Default Profile)     Jurisdiction    Others     IQL disables filters for an individual track.\nThe brightness of the track colours can be adjusted in the Display Settings window.\nTrack Symbols The track symbol indicates the position of the aircraft and the source of that information.\nThe track symbol position is based on the best source of information available to vatSys. The order of precedence is as follows:\n radar (SSR) ADS-B flight plan predicted position  The shape of the track symbol indicates the source of position information and special SSR codes.\n   Tracks Symbols (Default Profile)       Primary Radar  Secondary Radar    Radar extrapolated position (coast)  SSR code 0001    SSR code 0100  SSR code 1200    SSR code 2000  ADS-B    ADS-B extrapolated position (coast)  Cancelled    Flight plan       Where a primary return is detected with a secondary return, a combined track is presented.\nWhen an aircraft activates the IDENT feature of the transponder, the track symbol flashes cyan.\nThe \u0026ldquo;radar track cancelled\u0026rdquo; symbol is displayed when a track is no longer detected by radar. The history trails are removed one-by-one on each screen update and the cancelled symbol is removed after the history trails.\nLabels Track labels are displayed for all tracks, except filtered tracks and primary tracks. Track labels are connected to their respective track symbols by a leader line.\nThe position of track labels relative to their track symbols can be adjusted by RIGHT CLICK on the track symbol or level field in the track label. The draw order of track labels track labels must be manually adjusted so that they do not overlap and become obscured.\nThe type of label presented is determined by the available information for the track, and individual and global track display settings.\nNote: All tables and diagrams below refer only to the default profile, Eurocat Australia, though label items may be used in other profiles.\n   Label Type Tracks Items (Default Profile)     Limited Uncoupled Radar or ADS-B tracks  EMG WARN     CALLSIGN      LVL          Quick-Tag Uncoupled Radar or ADS-B tracks with quick tag  C EMG WARN    CALLSIGN      LVL \u0026gt; CFL GS   OPDATA          Normal Coupled or Flight Plan tracks  CPDLCMSG      C RWY EMG WARN   CALLSIGN  \u0026#43; W *  LVL \u0026gt; CFL F GS b WXL  CLL  WXR  OPDATA          Extended Coupled or Flight Plan tracks with Extended labels toggled  CPDLCMSG      C RWY EMG WARN   CALLSIGN  \u0026#43; W *  LVL \u0026gt; CFL F GS b WXL  CLL  WXR  ADES  ATYPE  N  OPDATA          Extended - Shared Coupled or Flight Plan tracks with Extended and Shared labels toggled  CPDLCMSG      C RWY EMG WARN   CALLSIGN  \u0026#43; W *  LVL \u0026gt; CFL F GS b WXL  CLL  WXR  NEXT   NEXT\u0026#43;1   OPDATA              Label Fields Content Action     CPDLCMSG Current unacknowledged CPDLC message LEFT CLICK to open CPDLC Menu. MIDDLE CLICK to toggle display. RIGHT CLICK to open CPDLC Editor Window.   C Togglable Coordination Prompt MIDDLE CLICK to toggle display of C prompt.   RWY Arrival or Departure Runway LEFT CLICK to open Runway Menu   EMG EMG (code 7700) or RAD (code 7600) MIDDLE CLICK to acknowledge.   WARN Highest priority current alert abbreviation See alerts MIDDLE CLICK to acknowledge.   CALLSIGN Callsign or SSR code LEFT CLICK to open Callsign menu. MIDDLE CLICK to toggle extended label display. RIGHT CLICK to open SAR Window.   + CPDLC status indicator (+, - or blank) LEFT CLICK to open CPDLC Editor Window. MIDDLE CLICK to toggle CPDLCMSG display.   W Wake turbulance category    * Important information (STS/) contained in FDR LEFT CLICK to open Flight Plan Window.   LVL Mode C level or Pilot Reported LEVEL LEFT CLICK to enter Pilot Reported Level (FP tracks only). RIGHT CLICK to position label.   \u0026gt; Vertical direction indicator (positive ^, negative v, cruise \u0026gt;)    CFL Cleared flight level, colour toggleable LEFT CLICK to open CFL Window. MIDDLE CLICK to toggle CFL colour.   F Flight rule abbreviation    GS 2 digit rounded Groundspeed    b ADS-B not flight planned indicator    WXL/WXR Weather deviation clearance (local only) LEFT CLICK to open Weather Diversion Menu.   CLL Lower bound of a block Cleared Flight Level LEFT CLICK to open CFL Window. MIDDLE CLICK to toggle CFL colour.   ADES Destination    ATYPE Aircraft Type    N Performance Based Navigation capability  (A RNP2 and RNP10/4, 2 RNP2, 4 RNP4, 5 RNAV5, T RNP10, Z none)    NEXT Next route waypoint    NEXT+1 Next route waypoint + 1    OPDATA Label Operational Data (scratchpad) LEFT CLICK to edit Label Op Data. RIGHT CLICK to toggle display of WX/BLOCK label line.    Alerts Alerts trigger an audible and visual warning on a track label. High priority alerts are shown with a solid red background in addition to yellow text.\n   Alert Label Abbreviation Priority Default Criteria     Cleared Level Adherence Monitoring CLAM 3 CFL is not None, VSA or 000 and; Maintaining: Mode C greater than 200FT from CFL Change of Level:  not commenced within 15 minutes, orVertical speed in the opposite direction to CFL   Danger Area Infringement Warning DAIW 1 Radar trajectory will enter dangerous volume in 60 seconds   Estimated Time Over ETO 4 (Not yet implemented) Pilot estimated time over waypoint disagrees with system calculated time by more than 180 seconds   Missed Position Report MPR 4 180 seconds after waypoint ETO when MPR is armed   Minimum Safe Altitude Warning MSAW 1 CFL is not None, VSA or 000 and radar trajectory will be within 600FT of projected obstacle height in 60 seconds   Medium Term Conflict Alert MTCA 3 (Not yet implemented)   Route Adherence Monitoring RAM 3 Radar track is outside of: 20NM from departure and destination aerodrome, and7NM either side of route, and14NM radius of route waypoints   Search and Rescue SAR 3 SAR Timer has expired. SAR Timer is automatically set to ETA+10 minutes when no arrival runway is selected   Short Term Conflict Alert STCA 1 Radar trajectories of two or more radar tracks will be less than: Level (bound by CFL)\n600FT, or1600FT when non-RVSM applies Distance\n2.1NM for TMA volumes, or4.8NM for Enroute volumes In the next 60 seconds for TMA volumes and 90 seconds for Enroute volumes, and the trajectory is not within defined airport STCA inhibition areas.    ","id":8,"tag":"","title":"Tracks","url":"/docs/tracks/"},{"content":"Overview Strips are your quick window to important information and functions for the management of the Flight Data Record (FDR). All routine functions of an aircraft\u0026rsquo;s flight plan are accessible via clickspots on the strip. This page will introduce you to the structure of the strip, the information contained, and the functions accessible for the normal operation of the FDR.\nSetup On Position selection, strip setup will be configured as defined in the profile dataset.\nStrip Setup can be altered by accessing the Strip Setup Window.\nStrip mode and strip sort modes are explained here.\nWindows Strip Windows contain strips for tracks that are of state Preactive or greater. That is to say, all aircraft that enter one of the controlled sectors selected, or are otherwise under jurisdiction will trigger the display of a strip. Strip colour corresponds to the corresponding Track state.\nStrip Mode selection decides which type of strip windows are available for display.\nBeacon Beacon Strip Windows are organised by defined beacons, waypoints or airports. Flights of at least Preactive state with the defined beacon point in their route will appear in the window, or if none of the points are contained, appear in a generic OTHER Strip Window.\nThe OTHER Strip Window will automatically display when strips are present, and hide when empty.\nState State Strip Windows are organised by current Track State (Preactive, Announced, etc.).\nStrips will move between windows when changing state. The OTHER strip window is not used in this mode.\nSelection Strip and Track selection are synchronised. Selecting a strip will select the corresponding track and vice versa. The selected strip will be scrolled into view (disables scrolling).\nLEFT CLICK the aircraft direction indicator (Triangle, Diamond) field to toggle.\nExtension Individual strips may be extended to display more information.\nMIDDLE CLICK the Callsign field to toggle extension of a strip.\nCocking Individual strips may be cocked to the right within their Strip Window.\nRIGHT CLICK the aircraft direction indicator field to toggle.\nHiding Individual strips may be hidden from display.\nMIDDLE CLICK the aircraft direction indicator field to hide.\nHidden strips may be restored in the settings menu.\nFields    Field Content Action     1 Aircraft Direction Indicator. Either a Diamond or Triangle symbol. Triangle points in the direction of flight. Filled when strip is selected LEFT CLICK to select / deselect track. MIDDLE CLICK to hide strip. RIGHT CLICK to cock strip.   2 Controlling Sector Abbreviation LEFT CLICK to open handoff menu   3 FDR State Abbreviation If PREA, LEFT CLICK to activate FDR.   4 Callsign LEFT CLICK to open Callsign menu. MIDDLE CLICK to extend strip.   5 Assigned SSR Code LEFT CLICK to open SSR menu.   a CPDLC Status Indicator. See aircraft labels for values LEFT CLICK to open CPDLC Editor Window.   b VFR Indicator    6 Aircraft Type    7 Actual Departure Time LEFT CLICK to open ATD menu.   8 Destination    9 Planned Cruise TAS    10 Assigned Departure or Arrival Runway LEFT CLICK to open RWY menu.   11 Assigned SID or STAR LEFT CLICK to open SID/STAR menu. RIGHT CLICK to display full name.   c PDC Status Indicator. ^ if PDC eligible, → when sent, ✓ when acknowledged LEFT CLICK to open CPDLC Editor Window (PDC). MIDDLE CLICK to toggle acknowledged.   12 Requested Flight Level    13 Cleared Flight level LEFT CLICK to open CFL Window. RIGHT CLICK to display block level.   14 Pilot Reported Level LEFT CLICK to open PRL Window.   15 Route waypoint name LEFT CLICK to open Waypoint menu. MIDDLE CLICK to toggle MPR alert activation. RIGHT CLICK to display full name.   16 Route waypoint estimate LEFT CLICK to open PETO Window.   17 Route waypoint trajectory level    18 Route waypoint estimate (PETO or ATO entered) LEFT CLICK to open PETO Window.   19 Route waypoint name (MPR armed) LEFT CLICK to open Waypoint menu. MIDDLE CLICK to toggle MPR alert activation. RIGHT CLICK to display full name.   20 Filtered FDR remarks LEFT CLICK to open Flight Plan Window.   21 Global Ops Data field. Shared to all controllers LEFT CLICK to enter data.   22 Local Ops Data field. Local to client LEFT CLICK to enter data.    ","id":9,"tag":"","title":"Strips","url":"/docs/strips/"},{"content":"Introduction The Voice Switching and Control System (VSCS) is the module for controlling all Air-Ground and Ground-Ground communication. It features a series of easily selectable buttons to allow the selection of frequencies, intercom lines and general setup of audio devices. The design is such that the interface can be used via a touchscreen.\nSetup The Setup button displays functions for setting up your communications. You can setup input and output devices, divert all frequencies or system sounds to Speakers, Add and Remove Frequencies or Monitor you ATIS (voice atis).\nCoord The Coord button provides access to Ground-Ground Communications with available sectors currently online.\nYellow - A yellow button opens a Hotline. After pressing the button, an audible warning plays and communication is immediately opened between yourself and the selected controller. Both user\u0026rsquo;s microphones instantly become live and you can speak straight away without any further button pushing. This method may be referred to as \u0026ldquo;override\u0026rdquo; in the VATSIM environment, however other controller clients did not simulate the hot-mic function correctly.\nPlease Note: The hotline function described above, means that one user can immediately open a voice connection to another user, without the other user accepting the incoming \u0026ldquo;call\u0026rdquo;. An audible warning will play when both a hotline or coldline is opened.\nBlue - A blue button opens a Coldline. After pressing the button, the other controller will receive an audible alert of the incoming call. The other controller must accept the call before communications can begin. This method can be compared to the Intercom method explained in other controller clients, or more simply, a normal phone call where the person on the other end has to answer.\nPurple Flashing - An incoming Coldline call. Click the button to accept the call.\nPurple Steady - The Hotline or Coldline is currently active. Click the button to close the line (hang up).\nText The name says it all. This button takes you to the text window allowing you to communicate air-ground over the active frequency. This interface is fairly limited (eg. it will not automatically select the aircraft you are talking to) and it is recommended to use the CPDLC functionality where possible.\nAir-Ground Frequencies Depending on the selected position one or more default frequencies will be available. The first will always be the sector for your own sector frequency. To activate this frequency and set it as primary, select the \u0026ldquo;Transmit\u0026rdquo; and \u0026ldquo;Primary\u0026rdquo; buttons. Additional frequencies (for extended sectors) may be added by setting the status of these to Transmit. Leave the \u0026ldquo;Group\u0026rdquo; button depressed to cross-couple these frequencies.\nIdle - Sets the frequency to \u0026ldquo;Not Active\u0026rdquo;. You are not transmitting or receiving on this frequency.\nReceive - Set the frequency to receive only.\nTransmit - Set the frequency to transmit and receive.\nPrimary - Set the frequency as your primary frequency (the frequency that will be displayed to pilots).\nGroup - Group active frequencies together to you can transmit and receive on all active frequencies at once.\nRemove - Removes the freqency from the VSCS.\nWhite - The frequency is Active and Primary.\nGreen - The frequency is Active for Transmit and Receive.\nPink - The frequency is Active for Receive only.\nWhite - The frequency is currently receiving radio traffic.\nWhen transmitting, any frequency being transmitted on will indicate \u0026ldquo;PTT\u0026rdquo;\n","id":10,"tag":"","title":"VSCS","url":"/docs/vscs/"},{"content":"Overview Flight plans received are parsed and processed into Flight Data Records (FDR).\nFlight Data Records form the basis of all interaction with aircraft other than directly with uncoupled radar tracks.\nWhen an FDR is first added it is initialised at the first FDR state (Preactive), and will evolve through a series of states until it is no longer needed.\nStates and Evolution    Abbreviation State Description     PREA Preactive The initial state. Controlling sector is assigned to the first sector entered or as defined in profile dataset, however FDR may be activated or modified by anyone.   COOR Coordinated Initial activation has occurred. Controlling sector is set to the activating sector unless activated by a TWR position. The activation event seeds an initial coordinated estimate for the first point of the route. FDR is now eligible for coupling to radar tracks and may be departed. The FDR may now only be modified by the controlling sector.   HND Handover First Departure time has been recorded and route estimates updated. An initial handover is proposed to the controlling sector. If departure has occurred within the activating sector, this handover is automatically accepted.   CONT Controlled Departed FDR has been accepted and may only be interacted with by the controlling sector.   HND Handover A handover has been proposed between controlling sectors.   UCTL Uncontrolled Departed FDR has been handed to none. In this state, anyone may accept jurisdiction and become the controlling sector.   INHI Inhibited The FDR has been suppressed locally. Processing still occurs, but Strips and Tracks are suppressed from display. In this state, anyone may accept jurisdiction and become the controlling sector.   FIN Finished The final state when a Departed FDR has been cancelled. Radar update over the assigned arrival runway will automatically cancel an FDR. The FDR is no longer usable and must be recreated if recovery is needed.   NACT Inactive Preactive FDR has been cancelled. The FDR will not generate strips or tracks, but may be recovered by reentering ETD.    Activation FDR\u0026rsquo;s may be activated through the aircraft strip or by accessing the Flight Plan Window.\nAn initial estimate at the departure point is set of now + 10 minutes, or a manual estimate for any waypoint may be entered in the flight plan window.\nPositions that are TWR, GND or DEL, do not alter the assigned controlling sector upon activation.\nNon-vatSys controllers may activate FDR\u0026rsquo;s by momentarily setting the Label Op Data (scratchpad) to TAXI, PUSH or DEPA. In Euroscope, this is done by using the Flight status item of the aircraft list.\nRadar / ADS-B Coupling FDR\u0026rsquo;s are eligible for automatic coupling to a radar or ADS-B track when state is COOR, HND, CONT, UCTL and INHI.\nAutomatic coupling is possible when the following conditions are met when the radar / ADS-B track:\n is squawking assigned code (MODE A/C radar) or has Flight ID (callsign) that matches FDR Callsign (MODE S/ADS-B) and; is within 7NM of FDR route and; has groundspeed of at least defined takeoff speed for aircraft type  FDR\u0026rsquo;s may be manually coupled or decoupled by using the Flight Plan Window. Manual couplings are local to your client. Manual coupling will disable the auto couple function until re-enabled in the Flight Plan Window.\nOn initial coupling if no departure time (ATD) is present, a departure time is calculated and entered.\nAutomatic Position Reporting Radar / ADS-B coupled FDR\u0026rsquo;s will periodically update route estimates and overflown waypoint index based on the current surveillance track location. This function is disabled if the track is in RAM (Route adherence monitor) state.\nTrajectory Calculation On FDR creation and modification, a 4D trajectory is calculated along the FDR route.\nAircraft performance data is used to calculate vertical changes (climbs/descent) in combination with flight planned TAS for level segments and GRIB forecast winds and temperatures.\nTrack state is determined and Strips are \u0026ldquo;posted\u0026rdquo; to sectors when the calculated trajectory enters one of the sector\u0026rsquo;s airspace volumes.\nShared Data Without a central server acting as Flight Data Processor, each client must attempt to synchronise data contained within each FDR. The majority of FDR fields are shared, including but not limited to:\n FDR activation Route estimates CFL (including block levels) Assigned SSR code Label Op Data (Scratchpad) Global Op Data  Fields that are not shared:\n Weather diversion SAR Timer Manual coupling Pilot reported level  ","id":11,"tag":"","title":"Flight Data Records","url":"/docs/fdr/"},{"content":"Overview For proper use, vatSys requires a profile dataset be created and distributed to it\u0026rsquo;s users.\nEach profile dataset should contain the data needed for one or more FIR\u0026rsquo;s or Air Traffic Systems.\nThe default vatSys profile (Eurocat Australia), may be viewed here.\nData Definition Hierarchy The definition of all WAYPOINT, NAVAID, AIRPORT, SID \u0026amp; STAR names referenced by vatSys XML files are searched for in the following order:\n Airspace.xml Navigraph Data  Lat Long Format vatSys accepts coordinates in any valid ISO 6709 format.\nLatitude and Longitude in Degrees: ±DD.DDDD±DDD.DDDD (eg +12.345-098.765) Latitude and Longitude in Degrees and Minutes: ±DDMM.MMMM±DDDMM.MMMM (eg +1234.56-09854.321) Latitude and Longitude in Degrees, Minutes and Seconds: ±DDMMSS.SSSS±DDDMMSS.SSSS (eg +123456.7-0985432.1) Latitude, Longitude (in Degrees) and Altitude: ±DD.DDDD±DDD.DDDD±AAA.AAA (eg +12.345-098.765+15.9) Latitude, Longitude (in Degrees and Minutes) and Altitude: ±DDMM.MMMM±DDDMM.MMMM±AAA.AAA (eg +1234.56-09854.321+15.9) Latitude, Longitude (in Degrees, Minutes and Seconds) and Altitude: ±DDMMSS.SSSS±DDDMMSS.SSSS±AAA.AAA (eg +123456.7-0985432.1+15.9) Chaining Points Together Multiple points may be chained by adding each point on a new line followed by the / character.\nELBIS/ IKUMA/ IDOTO/ GUNAM/ NIKOM/ CIN/ POKOS/ VALRA/ +12.345-098.765/ +15.345-123.765 Colours.XML Colours.xml defines the colours used throughout the entire application. The default IDs are listed below. Additional Custom Colours may be defined for reference by individual maps.\nColour IDs    Colour ID Use     Default Special use by plugins only   State Special use by plugins only   Custom May be defined multiple times to allow custom coloured maps   Window and Control backgrounds    ASDBackground Air Situation Display background   GroundBackground Ground Situation Display background   HighlightedText Selected text   WindowBackground Generic Window background   WindowWarning Warning colour used in menu, button and window backgrounds   WindowEmergency Emergency colour used in menu, button and window backgrounds   WindowButtonSelected Selected (Toggled) menu, button and scrollbar backgrounds   WindowButtonDepressed Depressed (button) or hover (menu item) backgrounds   InteractiveText Font of interactive items   NonInteractiveText Font of non-interactive items   GenericText Generic font   StripBackground Background of strips   StripText Strip Font   ListSeparator List Separator Bars   ListSeparatorSelected List Separator Bars when Selected   CPDLCMessageBackground Generic CPDLC message background   CPDLCDownlink Downlink Messages and label item   CPDLCUplink Uplink Messages and label item   CPDLCFreetext Freetext Messages   CPDLCSendButton CPDLC Editor Window send button   PopupASDWindowBorderFocused Border colour of focused popup Air/Ground Windows   Maps    PrimaryMap System maps and default   SecondaryMap System2 maps   PRDArea REST_NTZ_DAIW, TDA and Supervisor maps   UserMap Local_Private and Global_Private maps (not currently used)   Infill Filled maps   GroundRunway Ground Situation Displays only   GroundTaxiway Ground Situation Displays only   GroundApron Ground Situation Displays only   GroundBuilding Ground Situation Displays only   GroundOther Ground Situation Displays only   Tracks, labels, strips    Preactive    Jurisdiction    GhostJurisdiction    PostJurisdiction    JurisdictionIQL Quick-looked state   Handover    Announced    NonJurisdictionIQL Quick-looked state   NonJurisdiction    NonJurisdictionLabel    CFLHighlight    IdentFlash SPI   Route    PostJurisdictionFlash    GroundUnknown    GroundArrival    GroundDeparture    GroundLocal    Warning    Emergency    Tools    StaticTools    DynamicTools    Arrival Manager    Frozen reserved for future use   SuperStable reserved for future use   Stable reserved for future use   Unstable reserved for future use   DelayMinor reserved for future use   DelayMajor reserved for future use   VSCS    VSCSHotline    VSCSOpenHotline    VSCSColdline    VSCSOpenColdline    VSCSActiveFrequency    VSCSReceivingFrequency    VSCSButtonSelected    VSCSButtonDepressed    VSCSBackground VSCS Window background   VSCSFrequencyWarning Frequency in error state    Colour Defintion \u0026lt;Colour id=\u0026#34;DynamicTools\u0026#34;\u0026gt; \u0026lt;Use\u0026gt;Dynamic Tool In Use\u0026lt;/Use\u0026gt; \u0026lt;Name\u0026gt;OffWhite\u0026lt;/Name\u0026gt; \u0026lt;R\u0026gt;255\u0026lt;/R\u0026gt; \u0026lt;G\u0026gt;230\u0026lt;/G\u0026gt; \u0026lt;B\u0026gt;230\u0026lt;/B\u0026gt; \u0026lt;/Colour\u0026gt; Define the RGB value for a defined colour. Use element is optional and for reference only.\nCustom Colours Custom colours may be defined by using the id=\u0026quot;Custom\u0026quot; and ensuring a unique \u0026lt;Name\u0026gt; is assigned.\n\u0026lt;Colour id=\u0026#34;Custom\u0026#34;\u0026gt; \u0026lt;Use\u0026gt;Special colour for my very special map\u0026lt;/Use\u0026gt; \u0026lt;Name\u0026gt;SpecialPlum\u0026lt;/Name\u0026gt; \u0026lt;R\u0026gt;194\u0026lt;/R\u0026gt; \u0026lt;G\u0026gt;147\u0026lt;/G\u0026gt; \u0026lt;B\u0026gt;141\u0026lt;/B\u0026gt; \u0026lt;/Colour\u0026gt; Custom colours may then be referenced by Maps to affect their displayed colour.\nAirspace.XML SystemRunways This section \u0026lsquo;maps\u0026rsquo; the runway selectable by the controller in the strip or label of an aircraft to a SID or STAR defined in data for a particular runway (the DataRunway).\nFor every controlled airport in australia\u0026hellip; we need to add the airport-\u0026gt;runways-\u0026gt;sidstars\n\u0026lt;SystemRunways\u0026gt; \u0026lt;Airport Name=\u0026#34;YBCG\u0026#34;\u0026gt; \u0026lt;Runway Name=\u0026#34;14\u0026#34; DataRunway=\u0026#34;14\u0026#34;\u0026gt; \u0026lt;SID Name=\u0026#34;APAGI\\d\u0026#34; Type=\u0026#34;Jet\u0026#34;/\u0026gt; \u0026lt;SID Name=\u0026#34;CUDGN\\d\u0026#34; /\u0026gt; \u0026lt;SID Name=\u0026#34;CG\\d\u0026#34; Default=\u0026#34;True\u0026#34; /\u0026gt; \u0026lt;STAR Name=\u0026#34;[A-Z]{4}\\dA\u0026#34; ApproachName=\u0026#34;ILSZ\u0026#34;/\u0026gt; \u0026lt;STAR Name=\u0026#34;[A-Z]{4}\\dY\u0026#34; ApproachName=\u0026#34;RNVY\u0026#34;/\u0026gt; \u0026lt;/Runway\u0026gt; \u0026lt;Runway Name=\u0026#34;32\u0026#34; DataRunway=\u0026#34;32\u0026#34;\u0026gt; \u0026lt;SID Name=\u0026#34;APAGI\\d\u0026#34; Type=\u0026#34;Jet\u0026#34;/\u0026gt; \u0026lt;SID Name=\u0026#34;BURLI\\d\u0026#34; /\u0026gt; \u0026lt;SID Name=\u0026#34;CG\\d\u0026#34; Default=\u0026#34;True\u0026#34; /\u0026gt; \u0026lt;STAR Name=\u0026#34;[A-Z]{4}\\dA\u0026#34; ApproachName=\u0026#34;RNVZ\u0026#34;/\u0026gt; \u0026lt;STAR Name=\u0026#34;[A-Z]{4}\\dY\u0026#34; ApproachName=\u0026#34;RNVY\u0026#34;/\u0026gt; \u0026lt;/Runway\u0026gt; \u0026lt;Runway Name=\u0026#34;14V\u0026#34; DataRunway=\u0026#34;14\u0026#34;\u0026gt; \u0026lt;STAR Name=\u0026#34;[A-Z]{4}\\dV\u0026#34; /\u0026gt; \u0026lt;/Runway\u0026gt; \u0026lt;Runway Name=\u0026#34;32V\u0026#34; DataRunway=\u0026#34;32\u0026#34;\u0026gt; \u0026lt;STAR Name=\u0026#34;[A-Z]{4}\\dV\u0026#34; /\u0026gt; \u0026lt;/Runway\u0026gt; \u0026lt;/Airport\u0026gt; \u0026lt;/SystemRunways\u0026gt; What does this all mean?\n The Name attribute of SID and STAR elements accepts Regex search patterns; eg. If you see the code \\d it means any number, so if the APAGI4 becomes APAGI5 the code doesn\u0026rsquo;t need to change. eg. [A-Z]{4}\\dA means the first 4 characters are anything between A-Z, then look for any number then (in this case) Alpha charts. This means the BLAK3A arrival can change to BLAK4A arrival and the code doesn\u0026rsquo;t need to change. By doing this [A-Z]{4}\\dA and ApproachName=\u0026quot;ILSZ\u0026quot; we have assigned all Alpha STARs the ILSZ approach and [A-Z]{4}\\dY all Yankee STARs to the ApproachName=\u0026quot;RNVY\u0026quot; RNAV Yankee approach. We set the default SID to the airport\u0026rsquo;s radar departure and we set any visual STAR\u0026rsquo;s under a separate runway called [runwayid]V like 14V. We do this by calling all STARs that end in any number and V for Victor/visual using [A-Z]{4}\\dV. The SIDs are written out individually since some are jet and some are non jet. Runway ID cannot be more than 3 characters, so this means for any parallel runways the visual approach is not a seperate runway entry. Applicable to Sydney and Brisbane (#soon).  SIDSTARs This section defines the routes of SIDs, STARs, Approaches and their Transitions.\nSIDs and STARs should be defined for controlled airports whenever you wish to remove reliance on Navigraph defined data.\n\u0026lt;SIDSTARs\u0026gt; \u0026lt;SID Name=\u0026#34;TESTA1\u0026#34; Airport=\u0026#34;AAAA\u0026#34; Runways=\u0026#34;18,36\u0026#34;\u0026gt; \u0026lt;Route Runway=\u0026#34;36\u0026#34;\u0026gt;ROUTE POINT\u0026lt;/Route\u0026gt; \u0026lt;Route Runway=\u0026#34;18\u0026#34;\u0026gt;ANTHR RALTO\u0026lt;/Route\u0026gt; \u0026lt;Route\u0026gt;TESTA\u0026lt;/Route\u0026gt; \u0026lt;Transition Name=\u0026#34;ABCDE\u0026#34;\u0026gt;FINSH ABCDE\u0026lt;/Transition\u0026gt; \u0026lt;/SID\u0026gt; \u0026lt;STAR Name=\u0026#34;TESTA1\u0026#34; Airport=\u0026#34;AAAA\u0026#34; Runways=\u0026#34;18,36\u0026#34;\u0026gt; \u0026lt;Transition Name=\u0026#34;ABCDE\u0026#34;\u0026gt;ABCDE FINSH\u0026lt;/Transition\u0026gt; \u0026lt;Route\u0026gt;TESTA\u0026lt;/Route\u0026gt; \u0026lt;Route Runway=\u0026#34;36\u0026#34;\u0026gt;POINT ROUTE\u0026lt;/Route\u0026gt; \u0026lt;Route Runway=\u0026#34;18\u0026#34;\u0026gt;RALTO ANTHR\u0026lt;/Route\u0026gt; \u0026lt;/STAR\u0026gt; \u0026lt;Approach Name=\u0026#34;RNVZ\u0026#34; Airport=\u0026#34;AAAA\u0026#34; Runway=\u0026#34;18\u0026#34;\u0026gt; \u0026lt;Transition Name=\u0026#34;ABCDE\u0026#34;\u0026gt;ANTHR\u0026lt;/Transition\u0026gt; \u0026lt;Route\u0026gt;FAFFF AA18T\u0026lt;/Route\u0026gt; \u0026lt;/Approach\u0026gt; \u0026lt;/SIDSTARs\u0026gt; What does this all mean? SIDs and STARs consist of Route elements that are runway or non runway specific. For a SID, the non-runway specific route will always follow the runway specific route. For a STAR, the reverse is true. Transitions will be applied whenever the transition end point coincides with a point on the flight planned route.\nApproaches link a STAR to a runway. Transitions will be applied if they conincide with the STAR end point. Approaches are used only if defined in SystemRunways and are not manually selectable.\nAirways Airways may be defined whenever you wish to remove reliance on Navigraph defined data. Airways are always treated as valid in both directions.\n\u0026lt;Airways\u0026gt; \u0026lt;Airway Name=\u0026#34;A216\u0026#34;\u0026gt; APUKA/ MEMIG/ LOCKA/ CS \u0026lt;/Airway\u0026gt; \u0026lt;/Airways\u0026gt; Intersections Intersections (Fixes \u0026amp; Navaids) may be defined whenever you wish to remove reliance on Navigraph defined data.\n\u0026lt;Intersections\u0026gt; \u0026lt;Point Name=\u0026#34;ABARB\u0026#34; Type=\u0026#34;Fix\u0026#34;\u0026gt;-325106.400+1545604.900\u0026lt;/Point\u0026gt; \u0026lt;Point Name=\u0026#34;WP\u0026#34; Type=\u0026#34;Navaid\u0026#34; NavaidType=\u0026#34;VOR\u0026#34; Frequency=\u0026#34;112.800\u0026#34;\u0026gt;-124024.800+1415520.900\u0026lt;/Point\u0026gt; \u0026lt;/Intersections\u0026gt;\tDuplicates are generally accepted. vatSys will attempt to choose the nearest relevant intersection when parsing to resolve.\nIntersection Types\nTypes { Fix, Navaid, Airport, Unknown } Navaid Intersection Types\nNavaidTypes { None, VOR, NDB, TAC } Airports Airports may be defined whenever you wish to remove reliance on Navigraph defined data.\n\u0026lt;Airport ICAO=\u0026#34;YABA\u0026#34; Position=\u0026#34;-345636.000+1174832.000\u0026#34; Elevation=\u0026#34;233\u0026#34;\u0026gt; \u0026lt;Runway Name=\u0026#34;14\u0026#34; Position=\u0026#34;-345639.000+1174835.000\u0026#34;\u0026gt; \u0026lt;Runway Name=\u0026#34;32\u0026#34; Position=\u0026#34;-345642.000+1174838.000\u0026#34;\u0026gt; \u0026lt;/Airport\u0026gt; Maps Maps are what the Air Situation Display uses to display background information to the user of the client.\nEach XML file must contain one \u0026lt;Maps\u0026gt; element, which may define multiple \u0026lt;Map\u0026gt; elements. Each \u0026lt;Map\u0026gt; are individually selectable within vatSys.\nFolder structure within the vatSys Files\\Maps\\ directory is preserved by the Maps menu within vatSys.\nMap Element The Map element has the following attributes and children elements.\nType Each Map element may have one Type attribute from the following:\n { System, System2, Flex, Filled, Local_Private, Global_Private, Supervisor, TDA, REST_NTZ_DAIW, Ground_RWY, Ground_TWY, Ground_APR, Ground_BLD, Ground_BAK } The type primarily will affect the colour vatSys uses to paint the map. Colours are defined in Colours.xml.\nName The title of the Map (as displayed to the user).\nPriority An integer specifying the z-axis layering of the map, 0 being drawn on top of everything else.\nPRIORITY_HIGHEST = 0\nCenter An approximate center point of the map, used to deconflict in the event of multiple Waypoints with the same name.\nCustom Colour Name The optional attribute CustomColourName=\u0026quot;SpecialPlum\u0026quot; will allow display in a colour defined in Colours.xml.\nLine Element Each \u0026lt;Line\u0026gt; element draws a line between all children \u0026lt;Point\u0026gt;'s. Lines may set attribute Pattern to one of the following:\n{ Solid, Broken, Hash, Dashed, Dotted, None } Lines may set attribute Width to any floating value to change the stroke width (in pixels) of the rendered line:\n\u0026lt;Line .. Width=\u0026quot;1.67\u0026quot;\u0026gt; ... \u0026lt;/Line\u0026gt; Default stroke width is 1.0.\nAirway lines may be coded using a special syntax within \u0026lt;Point\u0026gt;\n\u0026lt;Point\u0026gt;STARTFIX.AIRWAYNAME.ENDFIX\u0026lt;/Point\u0026gt;\neg. \u0026lt;Point\u0026gt;VALRA.A339.ELBIS\u0026lt;/Point\u0026gt;\nInfill Element Each \u0026lt;Infill\u0026gt; element fills a polygon bound by the children \u0026lt;Point\u0026gt;'s.\nInfills may specify a Type attribute (default Normal):\n{ Normal, Background, } Background Infill Type is filled in the ASD background colour (useful for simplifying polygon definitions).\nInfills may specify a Pattern attribute (default Solid):\n{ Solid, Broken, Hash, Dashed, Dotted } Symbol Element Each \u0026lt;Symbol\u0026gt; element must have attribute Type to select one of the following types:\n{ SolidTriangle, HollowTriangle, HollowTriangleWithBorder, SolidTriangleWithBorder, SolidSquare, SolidStar, HollowStar, MalteseCross, HollowSquare, Circle, DashedCircle, DotFillCircle, Hexagon, Reticle } Each \u0026lt;Symbol\u0026gt; can have multiple \u0026lt;Point\u0026gt; children. Each Point InnerText is either an otherwise defined waypoint/navaid/airport or latlong in standard format of where to place the Symbol.\nLabel Element Each \u0026lt;Label\u0026gt; element of a map can have attributes HasLeader=\u0026quot;bool\u0026quot;, LabelOrientation=\u0026quot;enum\u0026quot;, Alignment=\u0026quot;enum\u0026quot; and VerticalAlignment=\u0026quot;enum\u0026quot; - these attributes specify if there is a line drawn from the point location to the text label and which compass direction or not, and the alignment of the text.\nLabelOrientation { N, NE, E, SE, S, SW, W, NW } Westerly LabelOrientation directions are Right aligned by default, otherwise default text alignment is Left.\nAlignment { Left, Center, Right } Southerly LabelOrientation directions are Top aligned by default, otherwise default text vertical alignment is Bottom.\nVerticalAlignment { Top, Middle, Bottom } Each \u0026lt;Label\u0026gt; can have multiple \u0026lt;Point\u0026gt; children. Each Point can have the attribute Name=\u0026quot;string\u0026quot; (which is displayed as the label text) and the InnerText is either an otherwise defined waypoint/navaid/airport or latlong in standard format of where to place the label. If you omit Name the name is generated from the InnerText.\nMisc.XML Contains miscellaneous Flight Data Processor and HMI settings.\nRVSMBand \u0026lt;RVSMBand Lower=\u0026quot;28000\u0026quot; Upper=\u0026quot;41000\u0026quot; /\u0026gt;\n-Lower is lower flight level of RVSM airspace in feet -Upper is upper flight level of RVSM airspace in feet\nUsed for triggering display of LABEL_ITEM_FRULES track label item.\nTransition \u0026lt;Transition Altitude=\u0026quot;10000\u0026quot; /\u0026gt;\nAltitude is level below which pressure corrected level is displayed instead of flight level\nRVSMStatus \u0026lt;RVSMStatus FAAEquipment=\u0026quot;L, W, Z\u0026quot; ICAOEquipment=\u0026quot;W\u0026quot; /\u0026gt;\nFAAEquipment comma separated equipment codes that indicate RVSM approval when flight plan is of VATSIM-FAA type ICAOEquipment comma separated equipment codes that indicate RVSM approval when flight plan is of VATSIM-ICAO type\nWhen any of the above are met, RVSM status flag is set to true.\nADSBStatus \u0026lt;ADSBStatus FAAEquipment=\u0026quot;I, L, G, Z\u0026quot; ICAOEquipment=\u0026quot;L, E, B1, B2\u0026quot; Remark=\u0026quot;ADSB\u0026quot; /\u0026gt;\nFAAEquipment comma separated equipment codes that indicate ADSB equipage when flight plan is of VATSIM-FAA type ICAOEquipmentcomma separated equipment codes that indicate ADSB equipage when flight plan is of VATSIM-ICAO type Remark string present in flight plan remarks formatted as RMK/string\nWhen any of the above are met, ADSB status flag is set to true.\nLATCValues \u0026lt;LATCValues\u0026gt;15, 22, 29, 38, 45, 61, 72, 89, 115, 165\u0026lt;/LATCValues\u0026gt;\nDistance values (NM) selectable when using the Conflict Area tool. These should represent meaningful separation values for procedural airspace eg. 7NM CEP + 14NM CEP + 1NM for Separation = 22NM\nFilterGroundTracks \u0026lt;FilterGroundTracks\u0026gt;YMML,YSSY,YPAD,YPPH,YBBN,YSCB,YPDN,YBCG,YBCS\u0026lt;/FilterGroundTracks\u0026gt;\nComma separated airport ICAO designators. ASD radar track labels are filtered in proximity when on the ground.\nPDCAirports \u0026lt;PDCAirports\u0026gt;YMML,YSSY,YPAD,YPPH,YBBN,YSCB,YPDN,YBCG,YBCS\u0026lt;/PDCAirports\u0026gt;\nComma separated airport ICAO designators. PDC strip options are available when the departure point is one of these airports.\nBRL \u0026lt;BRL LabelType=\u0026quot;Extended\u0026quot; /\u0026gt;\nLabelType -Normal (default) or\n-Extended (Shows reciprocal bearing and distance units)\nSets the bearing and range line tool label type.\nASSR \u0026lt;ASSR AutoAssign=\u0026quot;False\u0026quot; ShowNonDiscreteErrors=\u0026quot;False\u0026quot; /\u0026gt;\nAutoAssign boolean defaulting to True. When False, SSR Codes are not assigned automatically. ShowNonDiscreteErrors boolean defaulting to True. When False, SSR Code mismatch and invalid assignment Error messages are suppressed. ShowMismatchErrors boolean defaulting to True. When False, all SSR Code mismatch errors are suppressed.\nStrips.XML This file contains strip layout definitions for the rendering of flight progress strips. Each Position may be assigned a specific strip layout that is defined in this file, otherwise the default layout will be assigned.\nThis file is optional - default layouts are loaded if this file is missing. See example file.\nStripLayouts Contains StripLayout definitions, each a specific layout of strip items that vatSys will render.\nStripLayout StripLayout contains layout sections, which contain layout lines, which contain strip items. Sections \u0026lsquo;flow\u0026rsquo; horizontally or vertically. Widths of each section is calculated by the character width of the vatSys monospaced font and the minimum length of a line of strip items.\nStripLayout has the attributes Name=\u0026quot;string\u0026quot; and ArrowType=\u0026quot;enum\u0026quot;.\n Name is the name of the layout for referencing in Position definitions, or the special name \u0026quot;Default\u0026quot;. A single default layout should always be defined for general use when no specific layout is applicable. ArrowType is the direction of the designator area item (if present). None will render a diamond shape. Direction will automatically choose arrow based on FDR direction of flight.  ArrowType { None, Up, Down, Left, Right, Direction } StripLayoutSection StripLayoutSection defines a portion of the strip. It may contain children StripLayoutSection's in the child element StripLayoutSubsections. It may contain lines of actual strip items in the child element StripLayoutLines. The nesting of multiple child StripLayoutSections allows the creation of complex strip layouts.\nStripLayoutSection has the following attributes, FlowDirection=\u0026quot;enum\u0026quot;, Border=\u0026quot;flags\u0026quot; and DisplayState=\u0026quot;enum\u0026quot;.\n FlowDirection is the direction in which child sub sections will be laid out and may be one of the following  FlowDirection { Horizontal, Vertical } Horizontal Flow Vertical Flow  Border is the desired border to be rendered around this section. One or more flags may be combined with the | character eg. Border=\u0026quot;Left | Bottom\u0026quot;  Border { None = 0, Left = 1, Right = 2, Top = 4, Bottom = 8, Vertical = Left | Right, Horizontal = Top | Bottom, All = Vertical | Horizontal }  DisplayState (optional) is whether this section should be rendered only when the strip is extended or not. Normal sections are always rendered.  DisplayState { Normal, Extended } StripLayoutLine StripLayoutLine contains the StripItems composing a line of a strip. It has one attribute, LineSpan=\u0026quot;int\u0026quot;, which is an optional attribute to specify the number of lines of text that these items will span. For example, the designation arrow in the default strip spans two lines of the strip.\nStripLayoutLine has the child element StripItems, which may contain one or more StripItem elements.\nStripItem StripItems are the actual text item that the user sees and interacts with. It contains the following attributes:\n Type=\u0026quot;enum/string\u0026quot;. Either a default item type from the StripItemType enum, or a unique string name for use in CustomStripItem plugins. DesignationArea is the strip direction arrow and must span two lines. The rest are single lines of text. PointIndex=\u0026quot;int\u0026quot;. When the Type is one of Point, ETOP, PCL, this specifies the route segment index. 0 is the last overflown route point. MinLength=\u0026quot;int\u0026quot;. The minimum length of the item. Set this to ensure layout of sections is calculated correctly. MaxLength=\u0026quot;int\u0026quot;. The maximum length of the item text. If the text exceeds this length, the text is truncated and the last character is replaced by *. LeftClick=\u0026quot;enum\u0026quot;. The ClickspotTypes action to occur on left click. MiddleClick=\u0026quot;enum\u0026quot;. The ClickspotTypes action to occur on middle click. RightClick=\u0026quot;enum\u0026quot;. The ClickspotTypes action to occur on right click. FontSize=\u0026quot;enum\u0026quot;. The ASDFontSize size of the text. Default is Small. Border=\u0026quot;flags\u0026quot;. The desired border to be rendered around this item. One or more flags may be combined with the | character eg. Border=\u0026quot;Left | Bottom\u0026quot;  StripItemType { DesignationArea, Callsign, CPDLCStatus, FlightRules, TAS, RFL, Point, AssignedSSR, AircraftType, PRL, CFL, ETOP, ControllingSector, ATD, Destination, Runway, CoordinationStatus, XFL, PCL, FDRState, OtherInfo, GlobalOpsInfo, LocalOpsInfo, Gate, SIDSTAR, WakeTurbCategory, Departure, ETD, ExitBeacon, ExitETO, EntryBeacon, EntryETO, HoldPoint, PDCStatus, LabelData, ETA, FlightType, PerformanceCategory } ClickspotTypes { Label_Field18_Popup, Label_SAR_Popup, Label_PRL_Popup, Label_CFL_Popup, Strip_CFL_Expand, Strip_Select, Strip_Cock, Strip_State, Strip_Controller, Strip_Extend, Strip_ATD, Strip_SIDSTAR, Strip_SIDSTAR_Expand, Strip_Point, Strip_Point_Expand, Strip_Point_DCT, Strip_MPR_Arm, Strip_PCL, Strip_ETO, Strip_GlobalOps, Strip_LocalOps, Strip_Delete, Strip_ASSR, Strip_PDC_Editor, Strip_PDC_Acknowledge, } ASDFontSize { XtraSmall, Small, Large, XtraLarge } Colours A Colours element may be added to a StripItem to override the default colours of items. It has the following attributes, each are a colour identity as defined in Colours.XML:\n Colour=\u0026quot;enum\u0026quot;. Item text colour BackColour=\u0026quot;enum\u0026quot;. Item background colour BorderColour=\u0026quot;enum\u0026quot;. Item border colour P1Colour=\u0026quot;enum\u0026quot;. Item background colour when P1 alert is valid P2Colour=\u0026quot;enum\u0026quot;. Item text colour when P2 alert is valid P3Colour=\u0026quot;enum\u0026quot;. Item text colour when P3 alert is valid P4Colour=\u0026quot;enum\u0026quot;. Item text colour when P4 alert is valid P1BackColour=\u0026quot;enum\u0026quot;. Item background colour when P1 alert is valid P2BackColour=\u0026quot;enum\u0026quot;. Item background colour when P2 alert is valid P3BackColour=\u0026quot;enum\u0026quot;. Item background colour when P3 alert is valid P4BackColour=\u0026quot;enum\u0026quot;. Item background colour when P4 alert is valid P1BorderColour=\u0026quot;enum\u0026quot;. Item border colour when P1 alert is valid P2BorderColour=\u0026quot;enum\u0026quot;. Item border colour when P2 alert is valid P3BorderColour=\u0026quot;enum\u0026quot;. Item border colour when P3 alert is valid P4BorderColour=\u0026quot;enum\u0026quot;. Item border colour when P4 alert is valid  StripItemSeparator StripItemSeparator is a special blank StripItem for inserting empty space within a line. It\u0026rsquo;s only valid attribute is MinLength=\u0026quot;int\u0026quot;.\n","id":12,"tag":"","title":"Data Preparation Kit","url":"/docs/dpk/"},{"content":"Overview Functionality may be extended beyond the scope of the DPK through the creation of plugins. Extended functionality currently possible includes the adding of custom track label items or creating and displaying custom windows.\nPlugins can be written in C# by implementing the vatsys.Plugin.IPlugin interface exposed by adding a reference to vatSys.exe. vatSys will attempt to load any plugins that are present within /Plugins/ in the currently loaded Profile directory.\nAn example plugin is available here.\n","id":13,"tag":"","title":"Software Development Kit","url":"/docs/sdk/"},{"content":"Nothing, yet. ","id":14,"tag":"","title":"Docs","url":"/docs/"}]