Application Settings

Introduction

This page covers the SafeGuard™ Configuration Application Settings. Here you will be able to connect to the radar and get live data, view and edit the Navigation Mode Configuration and also the Area Rule Configuration.

Contents



Settings

image-20240214-150809.png

Connection Details

Hostname: The radar IP address.

Port: The radar port number.

Data Point Mode: This allows you to tell the app if it should expect to receive Nav Mode Points over the regular TCP connection, or by using Point Cloud Data over a UDP connection. The mode will need to match the Safeguard mode on the radar.

UDP Interface: If you have selected Point Cloud Data as the Data Point Mode then the UDP interface setting tells Safeguard where the radar is sending point cloud data to. This will usually be your IP address.

Connect: Click this button to connect to the radar.

Disconnect: Click this button to disconnect from the radar.

Data Point Configuration

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.

If the Nav Threshold is set too low and Max Peaks per Azimuth is set too high, then the radar will start to struggle and the Configuration Application may become unresponsive. We recommend setting a min threshold of 30dB.

If the Configuration Application becomes unresponsive, you can fix it by logging into Vertex, connecting and disconnecting.

Area Rule Configuration

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.

Enable Fail-Safe Mode: By default, this option is disabled. Enabling this option sets the Modbus relays into Fail-Safe Mode. This mode affects the relays and it inverts the logic on the relays so that they are powered open. So if there is a fault or power cut, for example, the relays close into a safe state.

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 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.

 

image-20240131-090811.png

Save to File: This saves the current navigation config and area rules to a formatted JSON file.

Load from File: This loads settings from a previously saved file, then immediately uploads these settings to the radar, with a prompt to warn the you before proceeding. 

Fetch Config: This gets the area rules configuration from the radar.

Send Config: Click this button to update the area rules configuration to the radar.

Accessing Live Data

To get live data:

  1. Type in the IP address of the radar in the Hostname field and click the Connect button:

     

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

     

View Area Rules

You can view the Area Rules for each area. To do this:

  1. Click the desired area number tab:

     

  2. The rules for that area will be displayed: