ICD-001 Alarm Load Simulator

Introduction

The ICD-001 Alarm Load Simulator provides ClearWay™ carriageway alarms over the ICD-001 interface that are raised as normal alarms. There are two types of alarms - short and long alarms. These stopped vehicle alarms will be raised with the same information as a genuine alarm and cleared at random periods depending on the configuration of the system. The simulation can be run using a batch file on an external machine.

The system will not simulate system alarms and will not raise tracks.

Prerequisites

This feature requires carriageway statistics to have been updated so that it can access radar coverage data of the carriageway or carriageways: it only generates alarms on sections that have coverage and the coverage is being provided by a radar assigned to the current track engine. Please refer to: https://navtechradar.atlassian.net/wiki/x/ZYDKj and: Carriageways | Statistics.

Accessing the Alarm Load Simulator

There is a new Track Engine Provider Type called Alarm Load Simulator:

When switching to this provider type it will load a config file called AlarmLoadSimulatorTestConfig.xml located here: "C:\ProgramData\Navtech\AlarmLoadSimulatorTrackProvider\AlarmLoadSimulatorTestConfig.xml"

This simulation works on a per Track Engine basis. Having multiple Track Engine’s in the system will require each Track Engine to be configured individually.

Configuring the Alarm Load Simulator

An example AlarmLoadSimulatorTestConfig.xml file:

<?xml version="1.0" encoding="utf-8"?>
<AlarmLoadSimulatorConfig xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <TestCycles>
    <TestCycle>
      <CycleLength>1</CycleLength>
      <Carriageways>
        <CarriagewayConfig>
          <Name>Carriageway 1</Name>
          <EmergencyAreaAlarms>
            <Rate>200</Rate>
            <ShortAlarmPercentage>100</ShortAlarmPercentage>
          </EmergencyAreaAlarms>
          <LiveLaneAlarms>
            <Rate>200</Rate>
            <ShortAlarmPercentage>0</ShortAlarmPercentage>
          </LiveLaneAlarms>
        </CarriagewayConfig>
      </Carriageways>
    </TestCycle>
    <TestCycle>
      <CycleLength>90</CycleLength>
      <Carriageways>
        <CarriagewayConfig>
          <Name>Carriageway 1</Name>
          <EmergencyAreaAlarms>
            <Rate>200</Rate>
            <ShortAlarmPercentage>0</ShortAlarmPercentage>
          </EmergencyAreaAlarms>
          <LiveLaneAlarms>
            <Rate>200</Rate>
            <ShortAlarmPercentage>0</ShortAlarmPercentage>
          </LiveLaneAlarms>
        </CarriagewayConfig>
      </Carriageways>
    </TestCycle>
  </TestCycles>
</AlarmLoadSimulatorConfig>

Test Cycles

This allows you to configure individual cycles which have a cycle length that can be set in minutes.

Carriageways: Enter the name of the carriageway you wish to use for the simulation.

CycleLength: This sets the length of the cycle in minutes.

EmergencyAreaAlarms: This sets the alarm values for the emergency areas (Lane 0). If this is not set, Lane 0 is assumed to be a live lane.

LiveLaneAlarms: Set the alarm values for live lanes.

Rate: The amount of alarms to be generated as a per hour value.

ShortAlarmPercentage: The amount of alarms that should be 5 to 30 seconds as a percentage of the rate. this value should be set between 0 and 100. The long alarms (5 to 30 minutes) will fill the remaining percentage of the alarm rate.

Using the Alarm Load Simulator

Once you have configured the AlarmLoadSimulatorTestConfig.xml file, start the Track Engine.
The system will perform each cycle in order before looping back to the first one.
Each cycle can have one or more carriageways specified and each carriageway can have ERA alarms and live lane alarms configured with an alarm rate (alarms/hour) and the percentage of alarms raised that will be short alarms.
It should start automatically, generating alarms for the carriageways based on the current test cycle.
It picks a random section and lane for live lane alarms when there are more lanes configured.
If you use ICD-001 to receive alarm reports, you should get alarm reports through once it starts raising the alarms. Please refer to ICD-001 Alarm Report for more information.
Stopping the Track Engine will stop the simulation.
The configuration will not be able to be changed whilst running a simulation. To update the configuration you will need to stop the Track Engine, amend the config file and then restart the Track Engine.

Related Information

Page:

ICD-001 Track Filter Command (Witness 4.0)
Page:

ICD-001 Acknowledge Alarm Command (Witness 4.0)
Page:

ICD-001 Request Status Command (Witness 4.0)
Page:

ICD-001 Detection Command (Witness 4.0)
Page:

ICD-001 Update Entity Command (Witness 4.0)
Page:

ICD-001 System Profile Command (Witness 4.0)
Page:

ICD-001 External Trigger Command (Witness 4.0)
Page:

ICD-001 Plugin (Witness 4.0)
Page:

ICD-001 Command Reply (Witness 4.0)
Page:

ICD-001 Camera Command (Witness 4.0)

Witness 4.0