AXIS Speed Monitor

AXIS Speed Monitor visualizes the speed of vehicles in a radar detection zone in the camera's live view, and logs the radar tracks on the SD card for statistical processing. The application works on Axis cameras, check the compatibility list on the product page.

For standalone radar installations without a camera, due to privacy concerns or for statistical purpose only, then the application can be installed in the radar directly. The speed overlay will then be visualized in the radar's live view. In this case, the SD card should be installed in the radar to log the statistics.

The application requires an AXIS Radar D2110-VE for the installation, mounted and configured in accordance with the D2110-VE installation guide and the radar white paper.

Before you set up the connection with the radar and configure the app overlays, you should calibrate the radar for the scene. The radar can be set to run on either Area monitoring or Road Monitoring depending on the use case.

The radar is ready to use as soon as it is installed. The default live view will show the radar coverage and any detected movement, and you can add detection zones and rules right away.

If the radar is mounted 3.5 m (11 ft) above ground, there is no need to do anything else. If the radar is mounted on a different height you need to calibrate the radar to compensate for the mounting height.

For full radar calibration instructions, see the user manual for AXIS D2110-VE Security Radar.

To make it easier to see where objects are moving, you can upload a reference map, for example a ground plan or an aerial photo, that shows the area covered by the radar.

• Image requirements:

• Supported file formats are jpeg and png.

• The image can be cropped in the radar.

• The image can be rotated ±35° in the radar.

• The orientation is not important, since the radar coverage shape will move to adapt to the image during calibration.

1. Upload a reference map
2. Upload a reference map and crop and calibrate it so that the actual radar coverage fits the position, direction and scale of the map.

3. Go to Radar > Map calibration.

4. Upload your reference map and follow the setup assistant.

To determine where to detect motion, you can add multiple zones. Different zones can be used to trigger different actions.

• There are two types of zones:

• A scenario (previously called include zone) is an area in which moving objects will trigger rules. The default scenario matches the entire area covered by the radar.

• An exclude zone is an area in which moving objects will be ignored. Use exclude zones if there are areas inside a scenario that trigger a lot of unwanted alarms.

A scenario (previously called an include zone) is an area in which moving objects will trigger rules. Add scenarios if you want to create different events for different parts of the scene.

1. Add a scenario:

2. Go to Radar > Scenarios.

3. Click Add scenario.

4. Type the name of the scenario.

5. Select if you want to trigger on objects moving in an area or on objects crossing a line.

1. Trigger on objects moving in an area:

2. Select Object moving in area.

3. Click Next.

4. Select the zone that should be included in the scenario.

   Use the mouse to move and shape the zone so that it covers the desired part of the radar image or reference map.

5. Click Next.

6. Add detection settings.

7. 1. Add seconds until trigger.

   2. Select which object type to trigger on.

   3. Add a range for the speed limit.

8. Click Save.

1. Trigger on objects crossing a line:

2. Select Object crossing line.

3. Click Next.

4. Position the line in the scene.

   Use the mouse to move and shape the line.

5. To change the detection direction, turn on Change direction.

6. Click Next.

7. Add detection settings.

8. 1. Add seconds until trigger.

   2. Select which object type to trigger on.

   3. Add a range for the speed limit.

9. Click Save.

Area monitoring profile is best used for objects moving at up to 55 km/h (34 mph). This profile allows you to detect whether an object is human, vehicle, or unknown. A rule can be set to trigger an event when any of these objects is detected. If you want to track only vehicles, you should use the Road monitoring profile.

Detection range is the distance within which an object can be tracked and can trigger an alarm. It is measured from near detection limit (how close to the device a detection can be made) to a far detection limit (how far from the device a detection can be made).

The Area monitoring profile is optimized for human detection, however, it will also allow you to track vehicles and other objects moving at up to 55 km/h (34 mph) with a velocity accuracy of +/- 2 km/h (1.24 mph).

When mounted at the optimal installation height, the detection ranges are:

• 3–60 m (10–200 ft) when detecting a human

• 3–85 m (10–280 ft) when detecting a vehicle

The Road monitoring profile is best used to track vehicles moving at up to 105 km/h (65 mph) in urban zones, closed zones, and on sub-urban roads. This mode should not be used for detection of humans or other types of objects. To track objects other than vehicles, use your radar in the Area monitoring profile.

Side mounted

To monitor vehicles travelling along a road you can mount the radar on to the side of the road. The radar will provide a lateral coverage distance of 10 m (32 ft).

Center mounted

This mounting option requires a stable position. The radar can be mounted on a pole in the middle of the road or on a bridge above the road. The radar will then provide a lateral coverage distance of 10 m (32 ft) to both sides of the radar. The radar covers a broader lateral distance when center mounted.

Detection range is the distance within which an object can be tracked and can trigger an alarm. It is measured from near detection limit (how close to the device a detection can be made) to a far detection limit (how far from the device a detection can be made).

This profile is optimized for detection of vehicles and will produce a velocity accuracy of +/- 2 km/h (1.24 mph) when monitoring vehicles moving at up to 105 km/h (65 mph).

Detection range when the radar is mounted at an optimal installation height:

• 25–70 m (82–229 ft) for vehicles moving at 60 km/h (37 mph).

• 30–60 m (98–196 ft) for vehicles moving at 105 km/h (65 mph).

Regulating vehicles in low speed zones

An industrial complex with a long road between two warehouses has installed a radar to help enforce a speed limit of 60 km/h (37 mph). In the Road monitoring profile, the radar can detect when a vehicle in its detection zone exceeds that speed. It then triggers an event which sends an email notifications to drivers and managers. The reminder helps increase compliance with the speed restrictions.

Unwanted vehicles on a closed road

A small road out to an old quarry has been closed, however, reports of vehicles driving on the road have resulted in authorities installing a security radar in the Road monitoring profile. The radar is mounted alongside the road and covers the entire width of the road. Whenever a vehicle enters the scenario, it triggers a flashing beacon that warns drivers to leave the road. It also sends a message to the security team so that they can dispatch a unit if needed.

Speed awareness on the road

A road that passes through a small town has had some incidents of speeding. To enforce the speed limit of 70 km/h (43 mph), the traffic control has installed a security radar, in the Road monitoring profile, on a bridge that crosses over the road. This has allowed them to detect the speed that vehicles are travelling at and monitor when they should have units stationed long the road to control the traffic.

Safety with humans and vehicles

Staff at a school have identified two safety issues that they would like to address. They have experienced unwanted visitors entering the premises during the school day, as well as vehicles violating the low speed zone of 20 km/h (12 mph) outside the school. The radar is mounted on a pole, next to the pedestrian walk path. The Area monitoring profile was chosen, as it makes the radar capable of tracking both humans and vehicles moving at speeds lower than 55 km/h (34 mph). This helps the staff keep track of people coming and going during school hours while also being able to trigger a speaker to warn pedestrians when a passing vehicle is driving too fast.

To install the application, go to the product page and download the latest version. Access the camera you want to connect to the radar, or install the application directly on the radar. Then do the following:

1. Go to Apps.

2. Click Add app.

3. Select the file in your downloads folder.

4. Click Install.

5. Turn on the app to activate the application.

In the camera’s webpage under Apps:

1. Go to the AXIS Speed Monitor app.

2. Click Open.

3. Go to Connect to radar.

4. Type the address of the radar, username and password.

5. Click Connect.

6. Scenarios (previously called include zones) are imported from the radar and will be listed as labels.

7. Click on the labels to edit the parameters. Remove the parameters to remove the overlay from the view.

• Parameters:
• These modifiers can be applied to each of the scenarios:

• #n: Name of the scenario.

• #M: Live speed measurement of the fastest moving object in the scenario.

• #c: How many cars have passed in the last 15 minutes.

• #a: Average speed in the last 15 minutes.

You can download the statistics of the day or a set date range. The information in the file includes all detected moving objects within range, and when those objects entered or exited a particular radar scenario. The statistics will be saved as a comma separated file (csv).

• Parameters in the file:

• rmd_zone name: Name of the scenario.

• tracking_id: The object ID in the radar metadata stream. Restarting the radar will reset the counter to 1.

• trigger_count: The number of times that the scenario has been triggered while there is an active tracked object in the scenario.

• object_class: Currently, the object classes consists of "Human", "Vehicle" and "Unknown". Select the class you would like to count in the scenario.

• weekday: The weekday when the track_id entered the scenario.

• date: The date the track_id entered the scenario.

• time: The time when the track_id entered the scenario. In HH:MM:SS.

• duration: How long the track_id spent inside the scenario. Given in seconds.

• enter_azimuth and exit_azimuth: The direction the object was pointing when it first entered and exited the scenario. The azimuth is given in degrees, and follows the same convention as radar metadata.

• enter_direction and exit_direction: A textual description of the movement, such as "departing", "rightwards", "approaching" and "leftwards".

• min_speed, avg_speed, max_speed: The minimum, average and maximum speed, respectively, that the object travelled while inside the scenario. Given in kilometers per hour or miles per hour. To change settings in the radar, go to System > Date and Time > Regional settings

• speed_delta The difference between the speed the object exited the scenario versus when it entered the scenario. Given in kilometers per hour or miles per hour. A positive number means acceleration, and a negative means deceleration.

• alarm: Denotes whether the object has travelled at an unacceptable speed while inside the scenario. 0 means acceptable speed and 1 unacceptable speed at one point.

To learn more, check out our guide Get started with rules for events.

1. Go to System > Events and add a rule. The rule defines when the device will perform certain actions. You can set up rules as scheduled, recurring, or manually triggered.

2. Enter a Name.

3. Select the Condition that must be met to trigger the action. If you specify more than one condition for the rule, all of the conditions must be met to trigger the action.

4. Select which Action the device should perform when the conditions are met.

Use an Axis strobe siren to let possible speeders know that your perimeter is protected.

This example explains how to activate a profile in the strobe siren whenever AXIS Speed Monitor detects a speed violation using the connected radar.

• Prerequisites

• Create a new user with the role Operator or Administrator in the strobe siren.

• Create two profiles in the strobe siren: one for when the driver is moving within the allowed speed, and the other when the speed limits are violated.

• Set up AXIS Speed Monitor in the camera, and an include area called “Area 1”.

1. Create two recipients in the camera

2. In the camera’s device interface, go to System > Events > Recipients and add a recipient.

3. Enter the following information:

4. • Name: Activate virtual port

   • Type: HTTP

   • URL: http://<IPaddress>/axis-cgi/virtualinput/activate.cgi

     Replace <IPaddress> with the address of the strobe siren.

   • The username and password of the newly created strobe siren user.

5. Click Test to make sure all data is valid.

6. Click Save.

7. Add a second recipient with the following information:

8. • Name: Deactivate virtual port

   • Type: HTTP

   • URL: http://<IPaddress>/axis-cgi/virtualinput/deactivate.cgi

     Replace <IPaddress> with the address of the strobe siren.

   • The username and password of the newly created strobe siren user.

9. Click Test to make sure all data is valid.

10. Click Save.

1. Create two rules in the camera

2. Go to Rules and add a rule.

3. Enter the following information:

4. • Name: Activate virtual IO1

   • Condition: Applications > Speed Monitor: Area 1

   • Action: Notifications > Send notification through HTTP

   • Recipient: Activate virtual port

   • Query string suffix: schemaversion=1&port=1

5. Click Save.

6. Add another rule with the following information:

7. • Name: Deactivate virtual IO1

   • Condition: Applications >Speed Monitor: Area 1

   • Action: Notifications > Send notification through HTTP

   • Recipient: Deactivate virtual port

   • Query string suffix: schemaversion=1&port=1

8. Click Save.

1. Create a rule in the strobe siren

2. In the strobe siren’s device interface, go to System > Events and add a rule.

3. Enter the following information:

4. • Name: Trigger on virtual input 1

   • Condition: I/O > Virtual input

   • Port: 1

   • Action: Light and siren > Run light and siren profile while the rule is active

   • Profile: select the newly created profile

5. Click Save.

The AXIS Speed Monitor app can be installed on a device that is connected to a radar, or directly installed on a radar.

If a device or radar is configured with AXIS Speed Monitor, it is considered as an external data source in AXIS Camera Station. You can connect a view to the data source, search for the object speeds that are captured by the device, and view the related image.

1. Download and install the application on your device.

2. Configure the application and the radar. See AXIS Speed Monitor user manual.

3. For an existing AXIS Camera Station installation, renew your server certificate that is used to communicate with the client. See Certificate renewal.

4. Turn on time synchronization to use the AXIS Camera Station server as the NTP server. See Server settings.

5. Add the related devices to AXIS Camera Station. See Add devices.

6. • If the app is installed on a device connected to radar, add the device and radar.

   • If the app is installed on a radar, add the radar.

7. When the first event is received, a data source is automatically added under Configuration > Devices > External data sources.

8. Connect the data source to a view. See External data sources.

9. Search for object speeds that are captured by the device. See Data search.

10. Click to export the search results to a .txt file.

AXIS Optimizer for Milestone Xprotect^® includes a feature called Zone speed search. The feature works together with AXIS Speed Monitor to visualize the speed of vehicles in a radar detection zone in the live view of the camera.

Use Zone speed search to search for speeding vehicles that have been detected when entering a predetermined zone in the camera’s view. See Zone speed search in the AXIS Optimizer user manual for more information.