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

« Previous Version 6 Next »

Introduction

This page covers the SafeGuard™ Configuration Application Dashboard, which alerts a user to alarms caused by data exceeding threshold values quickly and easily.

It provides a live view of a connected SafeGuard™ system, which includes some raw FFT data, NavMode data and SafeGuard™ configuration.

  • To monitor the system using FFT and NavMode level data, and make adjustments using the config.

  • Quickly and easily be alerted to data exceeding threshold values in either mode.

  • An option to visually link an output alarm state change with a radar return within or without one of the defined areas. 

  • Ability to quickly identify areas that require immediate attention.

  • Provide an option to "look" at the raw radar data and see its proximity to the threshold value at each location. 

  • Allows the user access so they can identify any potential issues. 

  • The live display can be paused and can be reset to the most current view 

  • Ability to review data when required.

  • Update rate of “live” data on visualiser matches that of the sensor update rate 

  • Provides the ability to view real-time or close to real-time data.

  • The application can display raw radar data, with a minimum refresh rate of 1 Hz 

  • Allow the viewing of up-to-date raw data

  • Application is able to display radar health, this can be abstracted to a single metric

  • Provides the ability to quickly assess the health of the system and identify any issues. 

For more information about SafeGuard™ please refer to this documentation: SafeGuard™ User Guide.

Plan - this will be removed once this page has been completed.

Contents

Navigating the Configuration Application Dashboard

Space holder for a navigation guide to the Dashboard. Similar to: https://navtechradar.atlassian.net/wiki/spaces/TUN/pages/773685283/Navigating+AdvanceGuard#Main-Display-Features

The left hand side features a PPI, and the right hand side features three tabs: Settings, Navigation Data and Alarms.

PPI

The PPI on the Configuration Application Dashboard is a live two-dimensional view of the radar display based around a geographical interface. The radar data is displayed in green with Nav Points (any peaks above threshold values) shown as red dots, along with the current alarm status. It is updated once a second.

There are 2 modes of operation - Global and Alarm. If an indicator turns from green (OK) to red (not OK) then an alarm has been given:

(image of an alarm on the PPI)

Radar Info Panel

There is a radar information panel on the PPI with the following fields:

Serial Number: The serial number of the radar.

Number of Azimuths per Rotation: This is the total number of azimuth samples taken by the radar in a single rotation.

Range in Bins: The total number of measurements taken for each azimuth sample. The calculated range of radar is Range Resolution x Range in Bins. Bins are individual cells measured by radars and the bin size must be rounded to the nearest 8 bins.

Rotation Speed: This is configured rotation speed of the radar, displayed in milli-Hertz. (Hz x 1000).

Resolution: The resolution is our sampling distance (for example, every 15cm) and is used for range and azimuth (also known as angular).

Range: This is the area of radar coverage.

Settings

Hostname: The radar IP address.

Port: The radar port number.

Connect: Click this button to connect to the radar.

Disconnect: Click this button to disconnect from the radar.

Bins to Operate on: This is the window size, in range bins, that is used to identify peaks. This window "slides" along each azimuth sample and is processed to identify peaks. If a signal peak is found then the curve fitting algorithm is applied to the sub-resolve the most accurate range to this peak. If no peaks are found then the window moves onto the next 5 bins. This approach helps eliminate minor secondary peaks which often appear either side of the primary peak.

Minimum Bins: This is the minimum bin from which to start the target extraction process. Any targets / peaks which are closer than this bin will not be processed.

Nav Threshold (dB): The threshold used to exclude noise and unwanted clutter. Only returns from targets that exceed this threshold will be considered for extraction. Anything below this threshold will be ignored.

Max Peaks per Azimuth: The maximum number of detection peaks that will be reported. Once the maximum number of peaks have been detected, further peaks will be ignored.

SET: Click this button to write configuration to the radar. This is disabled until the GET button is clicked and ?

GET: This gets the configuration from the radar. When GET is ? the areas will be drawn in R/L hand side as polygons.

The Area Rules section is greyed out until the GET button is clicked.

Area Rules

Get Area Rules: This gets the area rules configuration from the radar. When this button is clicked the areas will be drawn on the PPI in red.

Set Area Rules: Click this button to update the area rules configuration to the radar. This is disabled until the GET button is clicked and ?

Use sixth area for health data: By default, this option is disabled. Enabling this option disables area checking for Area 6. In addition, it uses the Modbus relay output for Area 6 to indicate overall system health as a binary healthy / not-healthy.

Areas 1-6

Enabled: Select this option to enable this area.

Invert Break Logic: The default logic for each detection area is that on each scan, if an object is detected in the area, then this will trigger an alarm. Once the object moves out of the area the alarm will stop. The Invert Break Logic inverts this logic and instead an object is expected to be in the area at all times. If no objects are detected then an alarm is raised and is only cleared when one or more objects are detected.

Threshold Delta: This delta is the additional threshold to add to the global threshold check in this area. This allows for greater thresholds in each area but it can't be lower than the global threshold. For example if the area Threshold Delta is 15 and the global Threshold is 65 then the actual threshold used in the area will be 80. All targets that fall below this new area threshold will be ignored, only targets which match or exceed the threshold will count as detections.

Break Allowance: This is the detection count that must be matched or exceeded for an alarm to be triggered for the area. For example, if the break count is 2 then the alarm will only be raised if an object is detected in the area on two consecutive scans. The break count is incremented on each radar scan if the detection conditions are met. This provides an effective way of ensuring the target is present and helps eliminate false alarms. This works in reverse if the Invert Break Logic is enabled, in that the break count will increase for every scan where an object is not seen in the area.

Allowance Curve Decrement: This value provides the speed at which the break count starts to decrease when there are no detections. Adjusting this value will effect the speed at which an area will go into an alarm or re-alarm. For example, if the break allowance is 16 and the decrement is also 16, then it will take 16 consecutive hits on a target to generate an alarm, but as soon as a scan is missed this will value be decremented by 16 and effectively reset.

Area Points X/Y: These are the X and Y coordinates of the Area Points.

The Area Rules will be disabled whilst they are in the process of being set after the Set Area Rules button has been selected.

The lower section is greyed out until the GET button is clicked.

To get live data:

  1. Type in the IP address of the radar.

  2. Click the Connect button.

  3. The PPI will be updated to show the live radar data.

You can view the Area Rules. To do this:

(image of empty area rules)

  1. Click the Get Area Rules button:

  2. (image of populated area rules)

You can add or edit areas in the Settings section. To do this:

  1. Amend the settings within each of the Area Rules and when you are happy with your choices, select the Set Area Rules button:

  2. (image of updated area rules)

Navigation Data

The Navigation Data tab will only display data when requested by the user clicking the Snapshot and Pause Data button.

Bearing (°): The determination of the direction of the plot.

Range (m): This is the area of coverage of the plot.

Power (dB): The power amplitude of the plot.

Snapshot and Pause Data: Clicking this button will take a snapshot of the last rotation of NavMode data and show it on the PPI, thus pausing the live display.

Resume Data: This option resumes the live display of data on the PPI. This option is only enabled if there is no data coming from the radar.

Save Data to File: This option allows you to export the to a CSV file.

Load Background Image: Clicking this button will load in a Bitmap representing? radar range & plot on Background.

Clear Background: Click this button to remove and FFT or Bitmap from background of LHS - will this still be here?

Alarm Areas Only: When this checkbox is selected, only NewMode Output within the alarm areas is shown in the list and on the PPI. Always updating list of NavMode output. This list can be sorted by clicking the header.

Alarms

The alarms panel shows the alarm status via an alarm indicator for each area (located at the top of the panel) and one for the radar health status (at the bottom of the panel), which should reflect corresponding alarm status on the PPI. If an indicator turns from green (OK) to red (not OK) then an alarm has been given.

  1. Have a visual viewer to show what radar data (spatially) is exceeding the SafeGuard threshold value in two modes: 

    1. Mode 1: Global mode (ignoring area offset) 

    2. Mode 2: Area based mode only showing in areas based on their offset  

Risks

  • It might not be possible to update a raw data display in real time using standard UI technology

  • The current plan is to display raw data at a 1Hz update rate, not the native update rate. Feasibility is required to ensure this is achievable.

  • It might not be possible to display very large number of nav plots in real time using standard UI technology

  • A certain level of real time plots should be achievable but quantities above a certain threshold may introduce unacceptable latency. Feasibility is required to establish the maximum threshold.

Related Information

  • No labels