ROSE. Radar Operation Simulator & Editor. Administration Manual

Size: px

Start display at page:

Download "ROSE. Radar Operation Simulator & Editor. Administration Manual"

Anthony Caldwell
5 years ago
Views:

1 ROSE Radar Operation Simulator & Editor Administration Manual

2 ROSE Version (Serial ) Copyright 2016 Klaus Fischer All rights reserved. Any copying or electronic transfer of this document in part or whole is prohibited without the prior consent of ATC-Sim Fischer. All names of procedures, products or organisations mentioned in this document, including names of hardware or software products are registered trademarks of the respective producers and thus are protected by the respective copyright. Realisation, layout and production: Klaus Fischer Christina Lemke Admin Manual Version from

3 Content 1 How to activate ROSE Get the fingerprint code Enter the activation key ROSE Folders and Files Aircraft Folder BIN Folder ROSE.exe file IRIS.exe file Record folder ROSE Filetypes ROSE generated types Import file types Other files Network Connection Networked training Assign pilot Multi-role piloting Config.ini Parameters Passing path parameters via the command line (system) Files to be loaded Files to be written

1 How to activate ROSE 1.1 Get the fingerprint code Please write to us as the developer team on radarsimulator@aol.

In order to provide your individual key, we need a fingerprint code of the computer you re working on.

installation process is required, just copy the files from your USB, CD or from a web link provided by the ROSE company to your computer. Now if you open the *.

4 1 How to activate ROSE 1.1 Get the fingerprint code Please write to us as the developer team on we will shortly send the activation key for your specific position back. In order to provide your individual key, we need a fingerprint code of the computer you re working on. To get this fingerprint code, please type the letters RX into the Command Line Window (within When ROSE is installed, the ROSE main directory looks like this: No complicated installation process is required, just copy the files from your USB, CD or from a web link provided by the ROSE company to your computer. Now if you open the *.exe file, ROSE starts and an Info Window appears in the middle of the screen, ROSE) and press [ENTER]. informing you about the need of an activation key for the software. Another Info Window appears, displaying the fingerprint code of your station. Example fingerprint code: OMN52B85NJ Please transcribe this code and send it to our address. Be careful not to confuse O (letter) with 0 (number) or I (letter) with 1 (number). 4

5 1.2 Enter the activation key Within short time we will send back an activation key to your address. Now please start ROSE again and enter the command VERIFY followed by the activation key into the Command Line Window. Example activation key: NVOXHEUOPM The input should then be: VERIFYNVOXHEUOPM As soon as you press [ENTER] the following Info Window should appear: The activation information is now stored within the ROSE directory (BIN folder). If you have any problems with the activation, please check the right spelling of the activation key - again be careful not to confuse O (letter) with 0 (number) or I (letter) with 1 (number). Another reason for problems might be the absence of a writing permission on the drive that ROSE is installed on. In any case please don t hesitate to contact us on radarsimulator@aol.com. 5

2 ROSE Folders and Files The folders and files are as follows: 2.1 Aircraft Folder.bmp files All these files are aircraft pictures, showing every type of aircraft that is available in ROSE.

It needs to have the same name of course and has to be a *.bmp file. 2.2 BIN Folder nf1.dat - nf6.dat / mf.dat / sf.dat These files contain the fonts used in ROSE for labels, buttons etc. callsigns.

6 2 ROSE Folders and Files The folders and files are as follows: 2.1 Aircraft Folder.bmp files All these files are aircraft pictures, showing every type of aircraft that is available in ROSE. When opening the Aircraftinfo Window in ROSE (with the [F5] key), the pictures are shown. The pictures can be replaced, if you like a more suiting picture of the respective aircraft. It needs to have the same name of course and has to be a *.bmp file. 2.2 BIN Folder nf1.dat - nf6.dat / mf.dat / sf.dat These files contain the fonts used in ROSE for labels, buttons etc. callsigns.txt All ICAO codes shown in the callsigns are here assigned to the full company name. If in ROSE the CANI label is selected, the Electronic Strips Window can be opened. The full company name is displayed is the RTF column. The file can be opened with a standard text editor. 6

7 LFZ.prm All aircraft data is stored in this file, like minimal speed, maximal speed, climbrate etc. If a new aircraft type shall be added to the system, this file will be expanded and needs to be updated. It can be opened with a standard text editor. emerg.wav / stca.wav / traffic.wav These files will be played in ROSE in case the respective kind of emergency occurs. If different soundfiles shall be played, you can just replace these files - but have in mind, that the naming has to be equal. HeadSymbol0.bmp - HeadSymbol12.bmp HistorySymbol0.bmp - HistorySymbol5.bmp NavSymbol0.bmp - NavSymbol20.bmp The appearance of head, history and navigational symbols can be customized. The ROSE standard symbols will be overwritten, when respective files are available in the BIN folder. The size of each *.bmp has to be 21*21 pixels and the only colours applicable are black (0x000000) and white (0xffffff). All black parts of the *.bmps will not be painted, all white parts will be used as symbol and can be coloured within ROSE. NTSYSDR.dll This file holds the validation code for the specific station. If it doesn t exist, ROSE will not be fully useable and will always start with an info saying ROSE is not licensed for this computer. The file will be created, when entering the VERIFY code. Therefore it is necessary, that the user has a write permission on the drive, where ROSE is installed. config.ini This file holds all the configuration parameters like which rights the user has on the specific station or which label configuration is set. All parameters are explained in detail later in this document. tcpic.ini In a setup where several stations are steadily linked to each other, ROSE establishes a connection to the host station as soon as it is started. This file stores the IP number or host name of the station ROSE will always connect itself to. Important: ROSE must be started on the host station before any slave tries to connect itself to the host. The tcpip.ini is created automatically if the button [Connect steady] in the Master Control Window [F1] is pressed. If the file is deleted, ROSE will not establish a steady connection on launching. The tcpip.ini may be extended by any commands, which will be executed after the system has started and a connection to the host has been established. So you might choose a certain role, open the TIP Window, use your desired label-format or other. Any given command will be executed similar to typing it into the command line after connecting to the host. The tcpip.ini can be generated, opened and edited with a standard text editor. ROSE fully supports the use of host names in addition to the TCP-IP number. 2.3 ROSE.exe file This is the ROSE executable file. On version updates only this file needs to be replaced. 2.4 IRIS.exe file This is the IRIS executable file. It is started and controlled from the ROSE.exe. 7

8 This folder is created automatically as soon as an exercise is loaded and running in ROSE and is not part of the installation files. 2.5 Record folder ROSE saves the progress of a run in *.zzr files. Every five seconds the actual situation (positions of aircraft eg.) is stored. This enables the user to resume an exercise after reviewing it via the Debriefilator. The progress of the last exercise that was done is saved in this folder. The last.ini in the Record folder always points towards the latest situation in the last run. If another exercise is started, the new data generated will overwrite the old *.zzr files. *************************************** Please note Since ROSE version the complete soundbackends folder as well as the *.dll files: ts3client_win32.dll ts3client_win64.dll ts3client_server32.dll ts3client_server64.dll are not needed anymore. Those files were used for the former support of IRIS, which was based on the teamspeak library. Since the software redesign IRIS is a fully independent programme and does not need any *.dlls. 8

9 3 ROSE Filetypes 3.1 ROSE generated types *.run This is a ROSE exercise file. It contains flight data of the flights programmed. It also holds the file reference to the airspace file, that the exercise is based on. *.def This is a ROSE airspace file. It contains all airspace elements and every configuration parameter for the specific elements (e.g. holding data for fixes or RWY data for airports). *.fpl A single flight plan is stored as *.fpl file and can be reused for different flights and exercises. It can be loaded when creating an exercise or during a running simulation with specific ROSE command. *.conf The screen setup can be saved at a single station. It saves data about window positions and configurations as well as the basic color setup. If a station is used by different trainees/coaches etc, everyone can save his preferred setup in a *.conf file. *.iris The IRIS (communication module of ROSE) setup can be saved in a single file and be used in different exercises. It holds information about the defined frequencies, telephone positions and headline namings in the IRIS window [F10]. 3.2 Import file types *.txt Flight plans and exercises can be imported from tab delimited *.txt files. It is explained in detail in the ROSE Handbook in chapters Import flight plans and 3.10 Import Exercises how the import works and how the import file has to be formatted. *.ext Airspaces can be imported from tab delimited *.ext files. It is explained in detail in the ROSE Handbook in chapter 5.13 Airspace Import how the import works and how the import file has to be formatted. 3.3 Other files FIR.txt This file contains entry and exit points for an FIR. It is used in combination with the SKYVISU connection and will only work under certain setup conditions, that are not freely available for the whole ROSE community, but for a special SKYSOFT/ROSE combination. 9

4 Network Connection 4.1 Networked training ROSE can be used as a trainer for individual exercises as well as for complex exercises consisting of several control sectors and simulation pilots.

10 4 Network Connection 4.1 Networked training ROSE can be used as a trainer for individual exercises as well as for complex exercises consisting of several control sectors and simulation pilots. Therefore ROSE must be configurated. The first step is to establish network between all computers which shall be connected. Hardwork network is probably the safest and fastest type of connection, but depending on the speed of the line WLAN might also be sufficient. ROSE uses TCPIP protocol to connect the single computers. So the next step is to define the HOST in the network. From this HOST the exercises will be distributed and monitored. The run history will be saved on this computer. Now all other computers have to be connected to the HOST. Read out the TCPIP number in the Master Control Window [F1]. This number is relevant to connect the slaves to their new master. Now start ROSE on a slave computer and enter the IP number of the HOST into the HOST text input field. Then press the [Connect Single] button. In this case the connection will be established just for 4.2 Assign pilot Every slave that is connected to the HOST serves automatically as a radar working position. To define it as a specific pilot, assign a number to the slave. The HOST is always PILOT1. Enter the command PILOT followed by the number of pilot he shall be at the slave computer. ROSE confirms your input as you see here: To transfer a flight from one pilot to the next define the number of the pilot when sending away a flight using the command >n (n = number of pilot). If a flight shall appear at a special pilot position use the command Z followed by the ID number of the pilot. The role of the actual position is displayed in the headline of the Command Line Window. this training. That means after shutting down all computers, the connection is lost. If you press the [Connect Steady] button instead your computer will try to establish connection every time you start ROSE on this computer. This of course can only be successful when the HOST computer is running and ROSE is started. To break a steady connection leave the HOST text input field empty an press the [Connect Steady] button. For the steady connection ROSE generates a file in the BIN folder named tcpip.ini (also see chapter 2 ROSE Folders and Files ). 10

11 4.3 Multi-role piloting ROSE offers multi-role piloting. You may assign more than one pilot role to a single slave computer. Do that by entering any number of pilots to a slave, dividing each number with a comma: Example: PILOT2,5,7,10 Another option is to add pilot roles to the ones already assigned to a slave computer. Therefore you have to type in a + (plus) behind the PILOT command. Example: PILOT+7 To cancel a specific role at a slave position, type in a - (minus) behind the PILOT command. Example: PILOT-5 If this slave was PILOT3,5,7,10 before cancelling one role, after that he will still be PILOT3,7,10. 11

12 5 Config.ini Parameters This is a short list of all parameters that can be set in the config.ini file, which is located in the BIN directory. Please be aware of copying them exactly regarding the spelling. ROSE does not differentiate between upper an lower case. Commands for development and administration PING LOG Opens a window in ROSE where event messages are displayed, is more for development and bugfixing - it is not of use for simulation or training Plots ROSE events and writes them into a log file Broad ROSE commands ROSE: ROSEcommand Any command known in ROSE can be passed to the config.file and will be executed on startup Example: ROSE:AS:4 HS:3 (set head and history symbols) User rights LOAD YES / LOAD NO SAVE YES / SAVE NO FREEZE YES / FREEZE NO FASTMODE YES / FASTMODE NO Defines whether a user has the right to load new exercises Defines whether a user has the right to save exercises Defines whether a user has the right to freeze during a simulation Defines whether a user has the right use fastmode EXERCISEEDIT YES / EXERCISEEDIT NO Defines whether a user has the right to edit exercises AIRSPACEEDIT YES / AIRSPACEEDIT NO Defines whether a user has the right to edit airspaces Voice Com IRISACTIVE Activates ROSE internal Voicecom Live Chat TIPCHAT Activates Live Chat option within the TIP Window Control mode AUTOPILOT ROSE will auto-execute all RADAR commands when in AUTOPILOT mode ( indication AP in the Command Line Window ) 12

13 Graphical Settings MULTIQLINE SKYQLINE SPEEDVECTOR = MINUTES SPEEDVECTOR = SECONDS HEADSYMBOLKLICK 10 GALCOMPASS FULLSCREEN FALSE This parameter switches the Q-Lines on or off - if it is not set in the config.ini, you will not be able to draw any measuring line. This parameter sets the Sky Q-line Mode as default setting for Q-line usage Specifies that the number following the command V means minutes Specifies that the number following the command V means seconds Specifies the distance from the head symbols center, which will be interpreted as a click onto the headsymbol (eg. Q-Lines or other selections), here meaning 10 pixels This parameter sets the old compass as default With this parameter set, ROSE will start as a window application, not in Fullscreen Mode Directories These are default directories which ROSE will address if you open the file-select dialog for different file operations RECORD = C:\ROSE\RecData AIRCRAFT = C:\ROSE\Aircraft AIRSPACE = C:\ROSE\Airspace EXERCISE = C:\ROSE\Exercise LOADRUN 12Sectors\Demo.run Defines a default directory of the Record folder Defines a default directory of the Aircraft folder Defines a default directory of the folder for airspace data Defines a default directory of the folder for exercise data Defines the run that will be loaded when starting ROSE Groupcodes Defines certain transponder codes, which will be shown as the given text instead of the callsign or only the squawk code. Put them directly below the headline Groupcodes. GROUPCODES Keyword to initiate the Groupcode definition 0045 VL (Examples of Groupcodes) 0022 VH 0033 MV 0025 PARA 7000 VFR 13

14 Conflicts STCATIME 2 TCASSECONDS 30 TCASACTION Defines a time in minutes, which will be considered as preview for an upcoming conflict Number of seconds, that aircraft look ahead to recognize the risk of a mid-air-collision If set, ROSE virtual pilots will automatically follow any given RA - the pseudo pilot will not have to react manually Label commands SKYAPP SKYACC SKYCOLORPRIORENTRY = 0,200,0 SKYCOLORAFTEREXIT = 0,200,0 CANILABEL SPEEDDIGITS 2 ACG Displays the label in the Skyguide Approach mode Displays the label in the Skyguide Center mode Colour of SKYGUIDE label of a flight that will be controlled by the actual position in R,G,B Colour of SKYGUIDE label of a flight that was previously controlled by the actual position in R,G,B Displays the label in the CANI mode (Czech ANS) Sets two digit speed indication in the radar label Displays the label in the AustroControl mode ACGREDUCEDLABELCONTENT cs=1 type=0 wake=0 dest=0 fl=0 cfl=0 roc=0 nextfix=0 rfl=0 xfl=0 gs=0 spd=0 hdg=0 xpt=0 Definition of the ACG reduced label content element=1 element will be displayed element=0 element will not be displayed ACGCOLOURPRIORENTRY = 162,193,238 Colour of ACG label of a flight that will be controlled by the actual position in R,G,B ACGCOLOURAFTEREXIT = 190,163,122 PATHCOUNTDOWNVALUE = 10 Colour of ACG label of a flight that was previously controlled by the actual position in R,G,B Defines duration of the path display (assume) in seconds 14

15 Help Buttons inside the Master Control Window [F1] ADDITIONALBUTTON1 Name of the button one Link to file one Via the two parameters inside the quotation marks, a file can be addressed from buttons one inside the Master Control Window [F1] ADDITIONALBUTTON2 Name of the button two Link to file two Via the two parameters inside the quotation marks, a file can be addressed from buttons two inside the Master Control Window [F1] ADDITIONALBUTTON3 Name of the button three Link to file three Via the two parameters inside the quotation marks, a file can be addressed from buttons three inside the Master Control Window [F1] SKYVISUAL Connection These commands will only work in a special ROSE version designed for connection with the SKYVISUAL HMI. In the standard ROSE version they do not cause any specific behaviour. ROSE:SKYSOC:5010 ROSE:SKYSOCFIR:5011 ROSE:SKYTIME: ,5910 ROSE:SKYCOMMANDPORT:50 ACT_TIME_MINUTES = 15 AFTN_MESSAGE_SLEEP = 100 Definition of port, on which ROSE will send AFTN messages (FPL,...) Definition of port, on which ROSE will send ACT messages Definition of IP address and port, on which ROSE will send data for time synchronisation Definition of port, on which ROSE will listen to input commands Definion of time (in minutes) ACT messages will be sent by ROSE before FIR entry Definition on milliseconds ROSE will wait between sending single AFTN messages 15

16 6 Passing path parameters via the command line (system) When starting ROSE via the command line, different parameters can be added. These parameters specify the path of certain subfiles that shall be loaded or written. All paths of course can be local paths or network paths. 6.1 Files to be loaded If you add the following paramentes, these files will be loaded from the given path instead of the standard directory ROSE would load them from per default. Path of config.ini Prefix: Example: -ini: rose.exe -ini:c:\rose\alternativeconfig\config1.ini Path of tcpip.ini Prefix: Example: -tcpip: rose.exe -tcpip:c:\rose\networksetup\tcpip_13.ini Path of IRIS configuration file Prefix: Example: -iris: rose.exe -iris:c:\rose\voicecomsetup\sectortraining.iris 16

17 6.2 Files to be written If you pass the following parameters, the exercise progress will be recorded automatically in intervals of one minute. The record file will be generated within the given directory and will be named as stated. Record files hold all exercise and airspace data and can also be manually generated from the ROSE Debriefilator (see chapter 1.9 ROSE Debriefilator ). Path of record file Prefix: Example: Example file name: -rec: rose.exe -rec:c:\rose\pruefung_basic\extest_3.rec ExTest_3.rec ( the name of the PC will not be considered) Path of record file, extended with the name of the PC within the network Prefix: Example: Example file name: -rec_: rose.exe -rec_:\\netserverrose\\ex_rating\ex_1.rec userpc-135_ex_1.rec ( if the name of the PC was userpc-135 ) 17

Headset plugs earphones (left), microphone (right)

Headset plugs earphones (left), microphone (right) Aerodrome control tower simulator [pd] Deployment - connect the power supply plug - connect the USB mouse and possibly a USB keyboard - connect the headset (pseudopilot) or the loudspeakers (student) -