| 21 | |
| 22 | Existing fields can be changed by clicking the corresponding field and enter the new value, save the value with [Enter]. It is not possible to the UID of an account. |
| 23 | |
| 24 | ==== Managing Flarmradar Client Stations ==== |
| 25 | |
| 26 | Navigate to Admin -> Masterdata and select the tab 'Stations' to display a list of client stations. Initally, there is only the built-in station with key 'demo' available but you are free to create any number of client stations on your private server. The only restriction is that the key must be unique for each station. |
| 27 | |
| 28 | Just enter a chosen client key and press enter to define a new client station. The fields 'Name' and 'ICAO' are later displayed in the menu list for this new station. Select the checkbox 'Active' to activate the station on the server side and then refresh the webpage in your browser. The station should now appear under the menu item 'Station'. |
| 29 | |
| 30 | The meanings of the other fields are as follows: |
| 31 | - Runways (e.g. '06,24'): A comma separated list of runway directions. The server will try to determine the correct runways for departures and landings |
| 32 | - Elevation (e.g. '416'): Elevation of the runway (in AMSL) |
| 33 | - Antenna Level (e.g. '3'): Antenna level (in meters) |
| 34 | - Sensor Radius (e.g. '1500'): Departure/Landing events outside that radius are ignored |
| 35 | - Map Zoom (e.g. '13'): As its name already says |
| 36 | - Map Center(e.g. '300'): Used to position the map center |
| 37 | - Trace: Write the received data to the server log file if selected |
| 38 | |