User - System Configuration

Introduction

The System Configuration page allows you to change the configuration of the system.

Contents

System Configuration

Once you have logged into the Vertex system the System Configuration screen will be displayed.

Open

The following fields will be displayed and most are editable:

IP Address: IP address of the radar sensor.

Subnet Mask: IP V4 subnet mask.

Gateway: IP V4 gateway.

Syslog Address: IP V4 address of the target syslog server. Once configured the radar will send logging data to the syslog server over the network.

Link Speed: The maximum link speed that the network could reach.

User Password: The user’s password.

FFT Data

Protocol: Select the protocol mode:

Navtech: This is the default setting. Nav mode outputs data over TCP/IP to the client.

CAT 240: Please refer to:https://navtechradar.atlassian.net/wiki/spaces/PROD/pages/2265514016/User+-+System+Configuration#FFT-Data-Settings-for-CAT-240-Option.

Sensor Port: The port used for raw TCP / IP data. In general we do not recommend customers change this port.

IP Address: If CAT-240 has been selected as the Protocol, then you will be able to amend the IP address.

Max Packet Size: If CAT-240 has been selected as the Protocol, then you will be able to amend the maximum packet size.

Navigation Data

We use Nav Mode or Point Cloud methods to extract significant features in the radar data. A threshold is applied to the data and any feature or target which exceeds this threshold is reported as a data point. This data point includes the range, bearing and it's amplitude. Both modes provide all the detected points per azimuth in a single network message. The number of points reported is constrained for performance reasons.

Nav Mode differs from Point Cloud because it uses a sub-resolving technique to significantly improve the range calculation for each point. When the radar is operating in its highest resolution this can lead to sub 2cm accuracy.
The Nav Mode uses a configurable fixed threshold to identify targets however the Point Cloud Mode has the advantage of using a dynamic threshold based on cell averaging.

Output Format: Select the Navigation Output Format. The Point Mode output is an alternative to the standard Nav Mode output.

Nav Mode: This is the default setting. Nav mode outputs data over TCP/IP to the client. Fore more information about Nav Points please see: https://navtechradar.atlassian.net/wiki/spaces/PROD/pages/2261516289/TCP+Networking#Navigation-Data-Message.

Point Cloud: Point Cloud mode outputs data over UDP. Please refer to: for more information about Point Cloud data.

IP Address: If Point Cloud has been selected as the Output Format, then you will be able to amend the IP address. This is used in conjunction with the Sensor Port parameter and defines the endpoint that the UDP messages are sent to.

Sensor Port: This field cannot be edited here. In general we do not recommend customers change this port, however, If the port must be revised, it can be edited via the Sensor Port in FFT Data.

Time Sync

Protocol: Select the time source protocol:

NTP: This is the default setting. This setting synchronises the clock to less than one millisecond of Universal Coordinated Time (UTC).

PTP: PTP uses a local area network to synchronise the clock, and achieves accuracy in the sub-microsecond range.

NTP Address: The IP V4 address of the NTP time source (if NTP has been selected above).

Changing the FFT Data

1. Select the drop-down arrow in the Protocol field in the FFT Data section:
   
   

   Open

   

    

2. Select the desired Protocol from the Protocol Mode drop-down:
   
   

    

3. You can then amend any available parameters as desired and click Apply. (If you have selected CAT-240 there will be additional options. Please see: for further information).
   
   

    

4. A Data Applied confirmation message will be displayed:
   
   

    

5. Select Commit Changes:
   
   

    

6. A Config Saved Confirmation message will be displayed:
   
   

    

7. You will then need to reboot the system for the FFT Data changes to take affect:
   
   

    

8. Click Reboot:
   
   

    

FFT Data Settings for CAT-240 Option

Sensor Port: The port used for raw TCP / IP data. In general we do not recommend customers change this port.

IP Address: This is used in conjunction with the Sensor Port parameter and defines the endpoint that the UDP messages are sent to.

Max Packet Size: This parameter specifies the maximum CAT-240 UDP packet size and is used to minimise potential problems of data loss when sending high-volume data over UDP.

More information about UDP packet loss and message splitting can be found here: .

Changing the Navigation Data

To change the Output Format:

1. Select the drop-down arrow in the Output Format field in the Navigation Data section.
   
   

    

2. Select the desired Output Format from the drop-down:
   
   

    

3. You can then amend any available parameters as desired and click Apply. (If you have selected Point Cloud there will be an additional IP Address option).
   
   

    

4. A confirmation message will be displayed. Select Commit Changes:
   
   

    

5. A Data Applied confirmation message will be displayed:
   
   

    

6. You will then need to reboot the system for the Navigation Data changes to take affect:
   
   

    

7. Click Reboot:
   
   

    

Changing the Time Sync

The Time Sync panel allows the radar's time server source to be changed.

1. To change the source click the drop down arrow in the Protocol field to show the choices:
   
   

    

2. Choose either NTP or PTP. If NTP is selected, the user must enter a valid NTP server address. If PTP is selected, the NTP server address field is hidden, as it is not relevant.
   
   

    

3. Once you have made your changes, click the Apply button to save the settings:
   
   

    

4. A Data Applied confirmation message will be displayed:
   
   

    

5. Then click the Commit Changes button:
   
   

    

6. A Config Saved confirmation message will be displayed:
   
   

    

7. You will then need to reboot the system for the Time Sync changes to take affect:
   
   

    

8. Click Reboot:
   
   

    

Related Information