Andrew Heath

The Toolbar Button is used to invoke all the available toolbars in ERAM. It is a floating button that can be positioned anywhere on the screen. It cannot be covered up and it cannot be deleted.

Buttons are used to open sub-menus, views, or toggle certain features within the Radar Client. A button can be activated or de-activated by TBP/TBE while the cursor is positioned within the button content area. Menu Buttons Blue indicates the sub-menu is closed. Brown indicates the sub-menu is open. Toggle Buttons Black indicates the view or feature is not currently displayed. Gray indicates the view or feature is currently displayed. Override Function Button Black indicates the override is currently deactivated. Gray indicates the override is currently activated. The user must press and hold TBP/TBE on the button for the function to continually activate. Increment/Decrement Buttons Increments (TBE) or decrements (TBP) the indicated feature. Command Buttons Teal indicates a command that is not activated. Burnt Coral indicates an activated command. The yellow border to the left of the button is used to reposition a button if desired. To do this: Position the cursor over the yellow bar. TBP and an outline of the button appears. Drag the outline to any location on the Situation Display, including any snap-to-grid position on a toolbar. TBP again to drop the button. Buttons can be "torn-off" the Master Toolbar for quick access to certain application functions - we call these eligible buttons "Tearoff Buttons". Tearoff Buttons allow the user to close the Master Toolbar and still have access to a particular button's functionality. To delete a Tearoff Button: TBP/TBE on the "DELETE TEAROFF" button. TBE on the button you wish to delete. To delete multiple Tearoff Buttons simultaneously: TBP/TBE on the "DELETE TEAROFF" button. TBP on every Tearoff Button you wish to delete except the last. TBE on the last button you wish to delete in the sequence.

The Radar Position (R-Position) interface consists of the following components: Buttons - Typically used to open different windows and views Toolbar Button - Used to invoke different toolbars Situation Display - Used to view traffic and sector data Message Composition Area (MCA) View - Used to compose and execute commands, receive syntax feedback and short character server responses Response Area (RA) View - Used to receive long character server responses such as flight plan readouts Time View - Used to view the current UTC or Coordinated Universal Time (aka Zulu)

By default, controllers are already logged-in (connected) to the POSCON network when they open the Radar Client. This is accomplished by a token authentication system that the Launcher Client manages behind the scenes. As a result, it is rare that a controller would ever have to enter their authentication details more than once since the token is refreshed automatically while the Launcher Client when running. There are times when a controller may inadvertently be disconnected or may wish to manually disconnect from the network, but these situations are rare. As described in the Launching the Radar Client section, if you wish to manually disconnect, you may use the Log-Out (LO) command and if you wish to manually reconnect, you may use the Log-In (LI) command.

Alternatively to using the Sign-In menu mentioned above, if the proper syntax combination is typed into the Message Composition Area (MCA) after "SI" or “SO” then the server will invoke the request directly. Example syntax: The following will Sign-In to the specified position: SI R USA.KZNY.N90.JFK.N2G <KBE> The following will Sign-Out from the specified position: SO R USA.KZNY.N90.JFK.N2G <KBE> NOTE: You must include the Authority in this command.

See the definition of Position in the Glossary.

See the definition of Role in the Glossary.

See the definition of Sector in the Glossary. A sector path is a quick way of referring to a sector. Sector paths are unique on POSCON and they must follow this format: <fir>.<facility>.<area>.<sector> NOTE: Authority is always omitted from the sector path. Example sector path: KZNY.N90.JFK.N2G

In order to control traffic on the POSCON network, a controller must first Sign-In to a Sector + Role combination that they are authorized for. For more information on sector authorizations/approvals, please see the ATC Policies document. The menu depicted below is invoked by using the SI <KBE> command in the Radar Client command line. The above menu, and the data that exists within it, constitutes all the available sectors that are able to be opened on POSCON. This data is populated by Facility Data Specialists for whatever FIRs they are responsible for. Controllers are limited by the role permissions granted to them. By default, a controller can sign into any sector using the "Observer" role. More information on roles is outlined in the sub-section below.

After launching the Radar Client for the first time, you must set your desired hardware. To do this, go to the Master Toolbar, then left-click on "VIEWS", and then left-click on "HW CONFIG". The following window will open: Make sure you are familiar with what the mouse buttons control: Trackball PICK, which is referred to as TBP in this document. TBP defaults to mouse left-click, but it can be changed via the drop-down menu. Trackball ENTER, which is referred to as TBE in this document. TBE defaults to mouse middle-click, but it can be changed via the drop-down menu. Trackball HOME, which is referred to as TBH in this document. TBH defaults to mouse right-click, but it can be changed via the drop-down menu. In order for the voice communications system work properly, you must also configure your audio hardware in the Launcher Client. For recommended audio settings, see this FAQ question.

In order to launch the Radar Client, open the POSCON Launcher, navigate to "Library", and click the "Launch" button on the Radar Client panel. There are a few things worth noting about the first time you launch the Radar Client: The Launcher Client keeps a token refreshed which prevents the user from having to type in a username and password, thus the Launcher Client must be running in the background at all times in order to authenticate and authorize your session. When you open the Radar Client, you are automatically logged into the network as an observer. You should immediately see traffic, but you will not be able to manipulate datablocks. If your Radar Client is not receiving aircraft position data from the server, you will see the following on your screen: You can manually log into or out of the network by invoking the following commands in the MCA or Message Composition Area: Log-In = LI <KBE> Log-Out = LO <KBE> The functionality to invoke Preference Settings (Pref Sets) does not currently exist yet, but all preferences are saved automatically in a text file called EramGuiState.txt which is located in the AppData\Local\POSCON\Radar Client\Session folder. Each time you move a window, increase the size of a font, drag a tearoff button to a different position on the screen, etc. the Radar Client automatically saves that change in the EramGuiState.txt file. We highly recommend you back up this file once you have configured the Situation Display the way you like. NOTE: You must have a "clean" shutdown of the radar client in order for changes to be saved in the EramGuiState.txt file. To load a sector file, type LOADSCT <KBE> in the Message Composition Area (MCA). This will open a file browser where you will need to locate the sector file you wish to use. By default, the browser is set to look for .SCT files, but this can be changed to search for .SCT2 files instead. When you locate the desired file, click "Open" and the sector data will load.

The Radar Client utilizes a dynamic zoom feature that allows users to display different maps based on zoom level. Currently, a user needs to manually configure the sector file in order to get this feature to work correctly. The following steps will go over the manual manipulation required. Please note that this is a temporary solution until a more automated system is developed: Open any sector file in the .SCT or .SCT2 format using Notepad++ or equivalent text editor. By default, when a sector file is loaded, all sector data is automatically rendered on the screen. This can be very cluttered, thus we have included the ability to specify RANGE values for specific elements. RANGE corresponds to your Radar Client zoom level. In this example, your current RANGE is 845. It is good practice to turn all elements of a sector file to OFF by creating a RANGE value from 0 to 0 (e.g. RANGE <SPACE> 0 <SPACE> 0) for each element. This will give you a clean slate from which to work and allow you to turn elements on and off at your discretion. When you are ready to start enabling specific elements, find where the element begins in the sector file and add the bottom and top of the range. In the example below, the user wants the [VOR] data to appear from range 10 to 50, thus they have entered RANGE 10 50. Once a RANGE value is set, the Radar Client will continue to apply that value to every subsequent element found in the sector file without a RANGE value set. That is why it is good practice to include a RANGE value for each element in a sector file, even if it is RANGE 0 0. NOTE: It may be required to add a RANGE value at the end of the sector file for the file to work at all. The main limitation to this RANGE method is if you quickly want to change between airport configuration maps, then you will likely need to either edit the sector file to display the correct map or you can have multiple sector files with the RANGE values preset.

Known Issues as of March 4th, 2021 Issue: If the Launcher Client is not running or your token failed to refresh, then you will see "NOT RECEIVING SURVEILLANCE DATA" and in the Messages View window, you will see the following error: Solution: Simply restart the launcher and try again. Issue: When Signing-In to a position, you see the following exception in the Messages View: Solution: This is normal. It means that no one has created any Facility Data for KZID, thus the server was unable to download anything. Issue: You Sign-In to a position and your VSCS is blank. Solution: Consult with your FIR's Facility Data Specialist. There is likely something wrong with the facility data.

Users may download Radar Client through the POSCON Launcher Client. The option to download the Radar Client will become available when SSO ATC access is granted. If you do not see it after this authorization is granted, you may need to log out and back into the Launcher Client. Once the Radar Client is downloaded, check changelog to ensure you have the current version.

Please see our ATC Policies document for more information regarding ATC policies on the Positive Control Network.

Generally, assume that any missing functionality is known to developers. Any functionality that is described in this manual, but is not working as intended should be reported via the Support Center. In the event of a crash-to-desktop or other bug, please create a support ticket. Make sure to be as thorough as possible in your report including detailed steps to reproduce the issue. The Radar Client produces two log files which we will need to debug any reported issue. Please locate the these two files by navigating to AppData\Local\POSCON\Radar Client and attaching the following files to your ticket: PositiveControlRadarClient_crash.dmp PositiveControlRadarClient_crash_.txt For minor support issues, please post in the POSCON Network Discord server > ATC > #coffee-pot channel.

Positive Control set out with the goal of designing the most realistic air traffic control simulation available. In keeping with that goal, we began by rethinking how our client software would interact with our server software. In the real-world, the processing power for these systems typically comes from a central mainframe computer located at each air traffic control facility. Radar workstations used by air traffic controllers consist of human controllable interfaces that allow users to send commands and receive responses from the mainframe computer system. On legacy networks, the server-side software is fairly basic while the radar clients themselves do most of the processing. On POSCON, we have moved most of this processing power from the radar client to the server. This serves two key advantages: It allows us to more closely emulate the real-world air traffic control systems. It allows future developers to tap into robust APIs to quickly create new user-interfaces for different countries. Initially, we have chosen to focus on developing ERAM or En Route Automation Modernization, which is the interface used to control enroute air traffic in the United States of America. Future development efforts will focus around the following: Terminal radar systems in the United States of America; and International radar systems. The above is POSCON's tentative internal development roadmap, but it assumes that no other opportunities present themselves. We are more than happy to interview new developers that are interested in developing their own radar systems as well. Please email [email protected] if you are capable of assisting.

Any vacant position that normally reports to a specific Director or Manager shall be assumed by that respective Manager or Director until filled.

All Network Directors, Managers, and other staff (including Division staff) must remain active within the POSCON community and within their respective departments. This includes, but is not limited to: Responding to internal management communications within three days or less, unless granted a leave of absence from their direct supervisor Participating in at least one Network or Division sanctioned event per month, unless granted a leave of absence from their director supervisor When appropriate, responding to general membership correspondence without undue delay

Network Directors, Managers, and other staff must maintain good standing within the POSCON community at all times. Since "good standing" is sometimes subjective, the final determination of "good standing" shall be determined by the Director or Manager responsible for the appointment.

Any person wishing to obtain a position that contributes Work Product to the POSCON Non-Profit Organization (POSCON Inc.) is required to sign the Volunteer Agreement. This includes, but is not limited to the following positions: President Network Directors Network Managers Division Managers Sub-Division Managers Moderators Support Specialists Other positions can designated by the President.

The following staff positions require candidates to be 21 years of age or older on the day they assume the position: President Network Directors Network Managers Moderators The following staff positions require candidates to be 18 years of age or older on the day they assume the position: Division Managers Sub-Division Managers Support Specialists. All other positions require candidates to be 16 years of age or older on the day they assume the position.

7g.5.1 Policy. A maximum of one staff position may be held by an individual at any given time on the POSCON Network. 7g.5.1 Exceptions. Anyone may interview and be hired as Moderator. Other exceptions may be granted on a case-by-case basis at the discretion of the President.

The following policies apply at the time of connection and/or during all times while connected to the Positive Control Network.

The following policies apply to every time a pilot intends to fly on POSCON.