Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Introduction

This page covers the installation and configuration of the ADS-B plugin which enables AdvanceGuard® to receive data via your ADS-B receivers.

Contents

Overview

The ADS-B plugin passes information from your existing ADS-B receivers into AdvanceGuard®, such as location information and flight numbers transmitted by aircraft.  AdvanceGuard® then correlates this information with radar tracks to provide accurate classification of detected objects and additional information such as flight numbers of aircraft.

The ADS-B Plugin

Witness supports integration with many different types of external systems through the use of plugins.

The plugin can be selected during setup and will automatically be installed in the correct location.

Prerequisites

The ADS-B Plugin relies on using the UDP Protocol to receive messages from a compatible ADS-B receiver.

Provide a link for the online reference for that protocol.

Configuring the ADS-B Plugin in AdvanceGuard®

Plugin Enabled: Select to enable the ADS-B Plugin.

Name: The ADS-B Plugin name.

System Id:

Timer Interval (s):

Track Expiry (s):

Show All Targets: If enabled, this option will show all targets, otherwise, only ground based targets will be processed.

Send Non Friendly: If enabled both friendly and non friendly tracks will be processed, otherwise, only friendly tracks will be processed.

Use Detection Areas: If enabled, tracks will only be shown in Detection Areas - see Detection Areas.

UDP Server

UDP Port: The port number used for the UDP Server.

Remote IP Address: The Remote IP Address of the UDP Server.

Tag Overrides

Classification overrides have been added to the ADS-B plugin so specific known vehicles / planes / targets can be classified within it.

Address Type: 

Non Unique

ICAO (airport code or location indicator)

Surface Vehicle

Vehicle

Other

Target Address (Hex):

Tag Override: Friendly name given to the known target.

Classification: The Classification Model of the target - see https://navtechradar.atlassian.net/wiki/spaces/TUN/pages/790069631/Classification+Configs#Classification-Models

None

Unclassified

Vehicle

Person

Debris

Aeroplane

Boat

Large Vehicle

Animal

Drone

Helicopter

Any

IFF (Identification Friend or Foe) Overrides

Classification: The Classification Model:

Unclassified

Aeroplane

Drone

Large Vehicle

Vehicle

Debris

Helicopter

Is Friend: Select the checkbox if the Classification Model is to be regarded as friendly.

Exceptions

Address Type: 

Non Unique

ICAO (airport code or location indicator)

Surface Vehicle

Vehicle

Other

Target Address:

Stuff from release notes:

  • Created a new security rule check that will mark a track as a friend if it’s within a configurable distance of an IFF track and also within a configurable distance to a breach line. This is designed to avoid nuisance alarms from tugs which are towing aircraft with active ADS-B transponders across CP line

  • Ensured that ADS-B numeric tags appear as hex within the UI

  • Changed the default ADS-B classification probability to be 0 for unclassified to match radar track sightings. When classified all ADS-B targets will have a probability of 1

  • Added a non-friendly sighting filter to ADS-B plugin to avoid passing non-friendly targets into AdvanceGuard. This now the default option

  • Added classification override to ADS-B plugin so specific know vehicles / planes can be classified within the ADS-B plugin

  • Added new ADS-B plugin which support Asterix Category 21. This supports using ADS-B target data to correlate with radar tracks to provide IFF functionality.

Related Information

  • No labels

Safety is everything.