Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

These are the primary global settings for the software system. They include policy settings for user security, database retention limits, system profiles and database backup options. Please refer to the documentation before making changes because these settings can significantly alter the behaviour of the software,.

Contents

...

Table of Contents
maxLevel3
indent16px
excludeIntroduction|Contents

...

Track Check Period (ms): How often the system checks for expired tracks.

Maximum Sightings: Maximum number of sightings stored of a single track - after which the system stops recording sightings.

...

Last Sightings: Number of sightings guaranteed to be recorded at the end of a track. This guarantees the last X sightings will be recorded, in the event of the max sighting limit being hit. This is also applied when the recording frequency of sightings is lower, due to the target being stationary.

Debris (and IFF) Movement Limit (m): Distance of movement below which debris (and IFF tracks) will not be recorded.

Use Radar NTP Time: This is the Network Time Protocol data sent with the tracks from the radar. NTP is a networking protocol for clock synchronisation between computer systems over packet-switched, variable-latency data networks.

Tracker SSH Start Delay (ms): This sets the amount of delay after the Track Engine has connected to the Onboard Tracker, before we connect to the tracker and radar via SSH to check the status and retrieve logs.

Central Tracker Licencing

...

Backup Radars On Shutdown: If a track engine has a backup track engine configured, and this setting is selected, then the system will automatically backup the radars when the track engine is shut down.

Capture Radar Logs Mode: There are two options:

Automatic: After the Tracker SSH Start Delay the system will try to download logs from the radar and onboard tracker.

Manual: The automatic setting is not selected and you will have to manually retrieve the logs or run a schedule for capturing the logs. Please refer to https://navtechradar.atlassian.net/wiki/spaces/TUN/pages/211190045/Radar+Actions#Actions and https://navtechradar.atlassian.net/wiki/spaces/TUN/pages/206537165/Schedules#Common respectively.

Enable Track ID Correlation: If enabled, the system will attempt to correlate an active track with another track that has recently been lost by checking the distance and speed. If the tracks match, it combines the active track with the old one so that it has the same Track ID. If no new tracks match the lost track within a given timeframe, it will expire and the feature will stop testing new tracks for a match.

Track ID Correlation is available in AdvanceGuard®, Sea360® and ClearWay™, and should not be confused with Track Correlation, which is only available in AdvanceGuard® and Sea360®.

Central Tracker Licensing

...

Disabled: This disables Central Tracker Licensing, which means that the Per Tracker Licensing will be operational. For more information, please refer to this information: Per Tracker Licensing

Enabled: This is where you can enable central licensing , by selecting the tick box. It is documented here: Centralised Tracker LicencingLicensing.

Alarm Options

...

Audible Alarm: Select to have a sound emitted when a system alarm is active.

...

Info

The Roles are a hierarchy: 

  1. Administrator

  2. Engineer

  3. User

  4. System

A complex password will be required from not only from the role selected, but all roles above it in the hierarchy too.

...

Filter by label (Content by label)
showLabelsfalse
cqllabel in ( "settings" , "alarm" , "profile" , "system" , "menu" , "systemmenu" , "sso" , "tracks" , "configuration" , "alarms" ) and space = "TUN"