Installation
This video shows an example of how to install the radar.
For complete instructions on all installation scenarios as well as important safety information, see the installation guide on axis.com/products/axis-d2210-ve-radar/support
Considerations
Where to install the product
Area or road monitoring
The radar is intended for monitoring open areas and you can use it either for area monitoring or road monitoring. The radar has two profiles to optimize the performance for each one of the scenarios. For more information about detection range, installation examples and use cases, see Radar profiles.
Avoid solid and reflective objects
Most solid objects (such as walls, fences, trees, or large bushes) in the coverage area will create a blind spot (radar shadow) behind it. Metal objects in the field of view cause reflections that affect the ability of the radar to perform classifications. This can lead to ghost tracks and false alarms in the radar stream.
For information about how to handle solid and reflective objects, see Add exclude zones.
Positioning
Install the product on a stable pole or a spot on a wall where there are no other objects or installations. Objects within 1 m (3 ft) to the left and right of the product, that reflect radio waves, affect the performance of the radar.
If you install the product on a wall, it needs to point away from the wall at least 15°.
Roll angle
The product's roll angle must be nearly equal to zero, which means that radar should be level with the horizon.
Tilt angle
The radar can be tilted 0-30°, but the recommended mounting tilt of the device is 15°. To help you achieve 15° tilt, make sure the back part of the chassis is level, as shown in the illustration.
You can add an overlay in the radar’s live view that shows the tilt angle of the radar. For instructions, see Show a text overlay with the tilt angle of the radar
Coexistence
If you mount more than eight Axis radars operating on the 60 GHz frequency band close together, they may interfere with each other. To avoid interference, see Install multiple radars.
Install multiple radars
You can install multiple radars to cover areas such as the surroundings of a building or the buffer zone outside a fence.
Coexistence
The radar’s radio waves continue beyond the detection area, and can interfere with other radars up to 350 m (380 yd) away. This is called a coexistence zone.
This radar operates on the 60 GHz frequency band. You can install up to eight radars operating on the 60 GHz frequency band close to each other, or facing each other, without causing problems. The built-in coexistence algorithm can find a suitable time slot and frequency channel that will minimize interference.
If an installation contains more than eight radars operating on the same frequency band, and many of the devices are pointing away from each other, there is less risk of interference. In general, radar interference will not cause the radar to stop functioning. There is a built-in interference mitigation algorithm that tries to repair the radar signal even when interference is present. A warning about interference is expected to happen in an environment with many radars operating on the same frequency band in the same coexistence zone. The main impact of interference is deterioration of the detection performance, and occasional ghost tracks.
Axis radars operating on different frequency bands will not interfere with each other. For example, you can combine AXIS D2210-VE with multiple AXIS D2110-VE Security Radar, which operates on the 24 GHz frequency band, without interference.
AXIS D2110-VE Security Radar requires additional configuration when more than two AXIS D2110-VE are mounted in the same coexistence zone. To learn more, see AXIS D2110-VE Security Radar user manual.
Environment
There are also other design factors to check when placing multiple radars in a site, like the surrounding environment, swaying objects, flag poles, and swaying vegetation. In some cases you need to filter out swaying objects from the radar stream to avoid false alarms.
Radar profiles
You can use the radar for area monitoring or road monitoring. There are two profiles that are optimized for each one of the scenarios:
Area monitoring profile: track humans, vehicles and unknown objects moving at speeds lower than 55 km/h (34 mph)
Road monitoring profile: track mainly vehicles moving at speeds up to 200 km/h (125 mph)
Select the area or monitoring profile in the web interface of the radar. For instructions, see Select a radar profile.
Area monitoring profile
The area monitoring profile is optimized 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 action when any of these objects is detected. To track vehicles moving in higher speeds, use the Road monitoring profile.
Area of coverage
AXIS D2210-VE has a horizontal field of detection of 95°. The area of coverage corresponds to 2700 m2 (29000 ft2) for humans and 6100 m2 (65600 ft2) for vehicles.
Optimal area coverage applies when the radar is mounted at 3.5–7 m (11–23 ft). The mounting height will affect the size of the blind spot below the radar.
Area detection range
The detection range is the distance within which an object can be tracked and can trigger an alarm. It is measured from a 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 speed accuracy of +/- 2 km/h (1.24 mph).
When mounted at the optimal installation height, the detection ranges are:
5 – 60 m (16–200 ft) when detecting a human
5 – 90 m (16–300 ft) when detecting a vehicle
- Enter the mounting height in the web interface when you calibrate the radar.
- The detection range is affected by the scene and the product’s tilt angle.
- The detection range is affected by the moving object type and size.
The radar detection range was measured under these conditions:
The range was measured along the ground.
The object was a person with a height of 170 cm (5 ft 7 in).
The person was walking straight in front of the radar.
The values were measured when the person entered the detection zone.
The radar sensitivity was set to Medium.
Mounting height | 0° tilt | 5° tilt | 10° tilt | 15° tilt | 20° tilt | 25° tilt | 30° tilt |
---|---|---|---|---|---|---|---|
3.5 m (11 ft) | 6.0–60+ m (19–196+ ft) | 5.0–60+ m (16–196+ ft) | 4.0–60+ m (13–196+ ft) | 4.0–60 m (13–196 ft) | 4.0–55 m (13– 180 ft) | 4.0–40 m (13–131 ft) | 4.0–30 m (13–98 ft) |
4.5 m (14 ft) | 6.0–60+ m (19–196+ ft) | 6.0–60+ m (19–196+ ft) | 5.0–60+ m (16–196+ ft) | 4.0–60+ m (13–96+ ft) | 4.0–60 m (13–196 ft) | 4.0–45 m (13–147 ft) | 4.0–40 m (13–131 ft) |
6 m (19 ft) | 10–60+ m (32–196+ ft) | 9.0–60+ m (29–196+ ft) | 7.0–60+ m (22–196+ ft) | 6.0–60+ m (19–196+ ft) | 6.0–60 m (19–196 ft) | 5.0–55 m (16–180 ft) | 5.0–55 m (16–180 ft) |
8 m (26 ft) | 16–60 m (52–196 ft) | 14–60 m (45–196 ft) | 10–60 m (32–196 ft) | 8.0–60+ m (26–196+ ft) | 8.0–60+ m (26–196+ ft) | 7.0–60 m (22–196 ft) | 7.0–60 m (22–196 ft) |
10 m (32 ft) | 21–60 m (68–196 ft) | 19–60 m (62–196 ft) | 14–60 m (45–196 ft) | 12–60+ m (39–196+ ft) | 10–60+ m (32–196+ ft) | 9.0–60 m (29–196 ft) | 9.0–60 m (29–196 ft) |
12 m (39 ft) | 25–60 m (82–196 ft) | 23–60 m (75–196 ft) | 19–60 m (62–196 ft) | 16–60+ m (52–196+ ft) | 13–60+ m (42–196+ ft) | 11–60+ m (36–196+ ft) | 11–55 m (36–180 ft) |
- Setting the radar sensitivity to Low will decrease the detection range by 20% while setting it to High will increase the detection range by 20%.
Area installation examples
To create a virtual fence, for example along or around a building, you can place up to eight AXIS D2210-VE Radars side-by-side. When you place two AXIS D2210-VE next to each other, you will get 180° coverage.
When you install more than one pair of AXIS D2210-VE side-by-side, we recommend that you place them with 100 m (330 ft) spacing between each pair.
Axis radars operating on different frequency bands will not interfere with each other. This means that you can combine AXIS D2210-VE, which operates on the 60 GHz frequency band, with AXIS D2110-VE Security Radar, which operates on the 24 GHz frequency band in the same coexistence zone.
For more information about coexistence and interference, see Install multiple radars.
Area monitoring use cases
Cover the area around a building
A company in an office building needs to secure the premises from intrusion and vandalism, particularly after working hours. To cover the area around the building, they install a combination of radars and PTZ cameras. They use AXIS D2110-VE Security Radars with 180° coverage to cover the long sides of the building, and AXIS D2210-VE Radar with 95° coverage for the shorter sides and corners. They configure the radars to trigger an alarm when humans approach the building after working hours. To make sure they get visual confirmation of potential intruders, they add two PTZ cameras. The radars can steer the PTZ cameras through AXIS Radar Autotracking for PTZ.
Additionally, the company wants to keep the premises safe during working hours. To make sure that vehicles passing the road on the side of the building are within the speed limits, they pair one of the AXIS D2110-VE Security Radars with a speed sign from Microbus, using AXIS Radar Integration for Microbus.
Cover a complex scene
A company that keeps critical equipment in a building on the premises is surrounded by a fence to keep intruders away. To avoid tampering and sabotage, they need additional protection. Their wish is to trigger an alarm when humans approach the building. However, the scene contains trees with swaying branches, a metal fence that could cause reflections, and even small animals moving around the site, which all could cause false alarms.
To reduce false alarms, they configure a scenario in the radar’s web interface so that an approaching object must cross two virtual lines before an alarm is triggered. This will help to trigger on objects that intentionally move towards the building, while objects that just happen to cross one of the virtual lines are filtered out.
In sites where there are no fences, the two lines could act as a virtual fence. To learn more about adding two lines to a scenario in the radar’s web interface, see Add scenarios.
Road monitoring profile
The road monitoring profile is optimized for tracking vehicles moving at up to 200 km/h (125 mph) on suburban roads and highways. To track humans and other objects moving at lower speeds, use the area monitoring profile. For more information, see Area monitoring profile.
Road detection range
The road monitoring profile is optimized for detection of vehicles and provides a speed accuracy of +/- 2 km/h (1.24 mph) when monitoring vehicles moving at up to 200 km/h (125 mph).
The mounting height of the radar and the vehicle speed will impact the detection range. When mounted at an optimal installation height, the radar detects approaching and departing vehicles with a speed accuracy of +/- 2 km/h (1.24 mph) within the following ranges:
25–100 m (82–328 ft) for vehicles moving at 50 km/h (31 mph).
40–80 m (131–262 ft) for vehicles moving at 100 km/h (62 mph).
50–70 m (164–230 ft) for vehicles moving at 200 km/h (125 mph).
To minimize the risk of missed detections of vehicles travelling in high speeds, set up a scenario in the radar that triggers on the object types Vehicle and Unknown. For more information about how to set up a scenario, see Add scenarios.
Road installation examples
When monitoring roads and highways, make sure to mount the radar at a sufficient height to avoid blind spots (radar shadow) behind the vehicles.
The size of the radar shadow depends on the radar’s mounting height and the vehicles’ height and distance from the radar. For example, when a vehicle with a height of 4.5 m (15 ft) is 50 m (164 ft) away from a radar that is mounted at a height of 8 m (26 ft), the radar shadow behind the vehicle will be 50 m (164 ft). However, if the radar is mounted at a height of 12 m (39 ft), the shadow behind the same vehicle will only be 23 m (74 ft).
Side mounted
To monitor vehicles travelling along a road you can mount the radar on the side of the road, for example on a pole. In this type of installation, we recommend a pan angle of max 25°.
To measure high speeds accurately, position the radar within a lateral distance of 10 m (32 ft) from the vehicles. For more information about detection range and speed accuracy, see Road detection range.
Center mounted
To monitor vehicles on a multi-lane road, you can mount one or more radars on a gantry above the road.
The same type of installation is possible if you want to monitor vehicles that drive away from the radar, instead of driving towards it.
To measure high speeds accurately, position the radar within a lateral distance of 10 m (32 ft) from the vehicles. For more information about detection range and speed accuracy, see Road detection range.
Road monitoring use cases
A common use case for AXIS D2210-VE Radar and the road monitoring profile is to track and measure the speed of vehicles. Additionally, you can use the radar with a visual camera and the application AXIS Speed Monitor to visualize the speed of the vehicles in the camera’s live view, or to log the radar tracks for statistical processing. For more information, see the user manual for AXIS Speed Monitor.
For more examples of how you can set up the radar when using the road monitoring profile, see the following use cases:
Wrong-way detection on a highway ramp
To detect and identify vehicles driving in the wrong direction on a highway ramp, traffic control uses an AXIS D2210-VE and an Axis bullet camera. They mount the radar on a pole facing the ramp to detect vehicles driving in the wrong direction. For reliable detections, they set up a line crossing scenario and configure the radar so that vehicles must cross two lines to trigger an alarm. In the scenario, they position the two lines on the ramp as seen in the illustration. They also specify the driving direction and speeds to trigger on. When the radar triggers an alarm, the Axis bullet camera can provide visual identification of the vehicle on the ramp.
Monitor traffic flow at an intersection – queue build-up
To monitor how and when queues build up in a busy intersection, traffic control installs a radar on a gantry above the intersection. They set up a scenario in the radar’s web interface and configure it to trigger on vehicles moving in an area. They shape the scenario to only cover the part of the road leading up to the intersection. To trigger an alarm when queues start to build up, they configure the scenario to trigger on vehicles moving at speeds below 5 km/h (3 mph).
Monitor traffic flow at an intersection – direction
To get an overview of the traffic flow and the direction vehicles travel in a busy intersection, traffic control installs a radar on a gantry above the road leading up to the intersection. They set up a line crossing scenario in the radar’s web interface where vehicles must cross two lines to trigger an alarm. When they configure the scenario, they place the first of the two lines over the lanes leading up to the intersection, after the pedestrian crossing to avoid vehicles stopping at the line. They place the second line over the lanes leading to the right. The vehicles must cross both lines in the specified direction to trigger an alarm. To avoid triggering on more than one vehicle per crossing, they lower the minimum trigger duration in the scenario from 2 to 0 seconds.
To monitor the traffic flow in all directions, they create one scenario for each direction.
The scenario doesn’t count the vehicles crossing the lines, instead you can use the event system in the radar's web interface to keep count. One way to count vehicles is to send an MQTT message each time the scenario triggers, and count the triggers on the MQTT receiver side.
Get started
Find the device on the network
To find Axis devices on the network and assign them IP addresses in Windows®, use AXIS IP Utility or AXIS Device Manager. Both applications are free and can be downloaded from axis.com/support.
For more information about how to find and assign IP addresses, go to How to assign an IP address and access your device.
Browser support
You can use the device with the following browsers:
ChromeTM | Firefox® | EdgeTM | Safari® | |
Windows® | recommended | recommended | ✓ | |
macOS® | recommended | recommended | ✓ | ✓ |
Linux® | recommended | recommended | ✓ | |
Other operating systems | ✓ | ✓ | ✓ | ✓* |
*To use AXIS OS web interface with iOS 15 or iPadOS 15, go to Settings > Safari > Advanced > Experimental Features and disable NSURLSession Websocket.
Open the device's web interface
Open a browser and type the IP address or host name of the Axis device.
If you do not know the IP address, use AXIS IP Utility or AXIS Device Manager to find the device on the network.
Type the username and password. If you access the device for the first time, you must create an administrator account. See Create an administrator account.
For descriptions of all the controls and options in the device’s web interface, see The web interface.
Create an administrator account
The first time you log in to your device, you must create an administrator account.
Enter a username.
Enter a password. See Secure passwords.
Re-enter the password.
Accept the license agreement.
Click Add account.
The device has no default account. If you lose the password for your administrator account, you must reset the device. See Reset to factory default settings.
Secure passwords
Axis devices send the initially set password in clear text over the network. To protect your device after the first login, set up a secure and encrypted HTTPS connection and then change the password.
The device password is the primary protection for your data and services. Axis devices do not impose a password policy as they may be used in various types of installations.
To protect your data we strongly recommend that you:
Use a password with at least 8 characters, preferably created by a password generator.
Don’t expose the password.
Change the password at a recurring interval, at least once a year.
Verify that no one has tampered with the device software
- To make sure that the device has its original AXIS OS, or to take full control of the device after a security attack:
Reset to factory default settings. See Reset to factory default settings.
After the reset, secure boot guarantees the state of the device.
Configure and install the device.
Web interface overview
This video gives you an overview of the device’s web interface.
Configure your device
Select a radar profile
- In the web interface:
Go to Radar > Settings > Detection.
Select a profile under Radar profiles.
Set the mounting height
Set the mounting height of the radar in the web interface. This helps the radar to detect and measure the speed of passing objects correctly.
Measure the height from the ground up to the radar as accurately as possible. For scenes with uneven surfaces, set the value that represents the average height in the scene.
Example
Depending on the area of interest, the mounting height (h1, h2) differs.
If the surface in the area of interest is uneven, add the average height (in this case (h1 + h2) / 2) when you configure the radar.
- Set the mounting height:
Go to Radar > Settings > General.
Set the height under Mounting height.
Calibrate a reference map
Upload a reference map to make it easier to see where detected objects are moving. You can use a ground plan or an aerial photo that shows the area covered by the radar. Calibrate the map so the radar coverage fits the position, direction, and scale of the map, and zoom in on the map if you're interested in a specific part of the radar coverage.
You can either use a setup assistant that takes you through the map calibration step by step, or edit each setting individually.
- Use the setup assistant:
Go to Radar > Map calibration.
Click Setup assistant and follow the instructions.
- To remove the uploaded map and the settings you have added, click Reset calibration.
- Edit each setting individually:
- The map will calibrate gradually after you adjust each setting.
Go to Radar > Map calibration > Map.
Select the image you want to upload, or drag and drop it in the designated area.
To reuse a map image with its current pan and zoom settings, click Download map.
Under Rotate map, use the slider to rotate the map into position.
Go to Scale and distance on a map and click on two pre-determined points on the map.
Under Distance, add the actual distance between the two points you have added to the map.
Go to Pan and zoom map and use the buttons to pan the map image, or zoom in and out on the map image.
- Note
The zoom function does not alter the radar’s area of coverage. Even if parts of the coverage is out of view after zooming, the radar will still detect moving objects in the entire area of coverage. The only way to exclude detected movement is to add exclude zones. For more information, see Add exclude zones.
Go to Radar position and use the buttons to move or rotate the position of the radar on the map.
- To remove the uploaded map and the settings you have added, click Reset calibration.
Set detection zones
To determine where to detect motion, you can add one or more detection zones. Use different zones 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.
Add scenarios
A scenario is a combination of triggering conditions and detection settings, which you can use to create rules in the event system. Add scenarios if you want to create different rules for different parts of the scene.
- Add a scenario:
Go to Radar > Scenarios.
Click Add scenario.
Type the name of the scenario.
Select if you want to trigger on objects moving in an area or on objects crossing one, or two, lines.
- Trigger on objects moving in an area:
Select Movement in area.
Click Next.
Select the type of 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.
Click Next.
Add detection settings.
Add seconds until trigger after under Ignore short-lived objects.
Select which object type to trigger on under Trigger on object type.
Add a range for the speed limit under Speed limit.
Click Next.
Set the minimum duration of the alarm under Minimum trigger duration.
Click Save.
- Trigger on objects crossing a line:
Select Line crossing.
Click Next.
Position the line in the scene.
Use the mouse to move and shape the line.
To change the detection direction, turn on Change direction.
Click Next.
Add detection settings.
Add seconds until trigger after under Ignore short-lived objects.
Select which object type to trigger on under Trigger on object type.
Add a range for the speed limit under Speed limit.
Click Next.
Set the minimum duration of the alarm under Minimum trigger duration.
The default value is set to 2 seconds. If you want the scenario to trigger every time an object crosses the line, lower the duration to 0 seconds.
Click Save.
- Trigger on objects crossing two lines:
Select Line crossing.
Click Next.
To make the object cross two lines for the alarm to trigger, turn on Require crossing of two lines.
Position the lines in the scene.
Use the mouse to move and shape the line.
To change the detection direction, turn on Change direction.
Click Next.
Add detection settings.
Set the time limit between crossing the first and the second line under Max time between crossings.
Select which object type to trigger on under Trigger on object type.
Add a range for the speed limit under Speed limit.
Click Next.
Set the minimum duration of the alarm under Minimum trigger duration.
The default value is set to 2 seconds. If you want the scenario to trigger every time an object has crossed the two lines, lower the duration to 0 seconds.
Click Save.
Add exclude zones
Exclude zones are areas in which moving objects will be ignored. Add exclude zones to ignore, for example, swaying foliage on the side of a road. You could also add exclude zones to ignore ghost tracks caused by radar-reflective materials, for example a metal fence.
- Add an exclude zone:
Go to Radar > Exclude zones.
Click Add exclude zone.
Use the mouse to move and shape the zone so that it covers the desired part of the radar view or reference map.
Minimize false alarms
If you notice that you get too many false alarms, you can filter out certain types of movement or objects, change the coverage, or adjust the detection sensitivity. See which settings work best for your environment.
Adjust the detection sensitivity of the radar:
Go to Radar > Settings > Detection and select a lower Detection sensitivity. This decreases the risk of false alarms, but it could also cause the radar to miss some movement.
The sensitivity setting affects all zones.
Low: Use this sensitivity when there are a lot of metal objects or large vehicles in the area. It will take longer time for the radar to track and classify objects. This can reduce the detection range, especially for fast moving objects.
Medium: This is the default setting.
High: Use this sensitivity when you have an open field without metal objects in front of the radar. This will increase the detection range for humans.
Modify scenarios and exclude zones:
If a scenario includes hard surfaces, such as a metal wall, there may be reflections that causes multiple detections for a single physical object. You can either modify the shape of the scenario, or add an exclude zone that ignores certain parts of the scenario. For more information, see Add scenarios and Add exclude zones.
Trigger on objects crossing two lines instead of one:
If a line crossing scenario includes swaying objects or animals moving around, there is a risk that an object will happen to cross the line and trigger a false alarm. In this case, you can configure the scenario to trigger only when an object has crossed two lines. For more information, see Add scenarios.
Filter on movement:
Go to Radar > Settings > Detection and select Ignore swaying objects. This setting minimizes false alarms from trees, bushes, and flagpoles in the coverage zone.
Go to Radar > Settings > Detection and select Ignore small objects. This setting is available in the area monitoring profile and minimizes false alarms from small objects in the coverage zone, such as cats and rabbits.
Filter on time:
Go to Radar > Scenarios.
Select a scenario, and click to modify its settings.
Select a higher value under Seconds until trigger. This is the delay time from when the radar starts tracking an object until it can trigger and alarm. The timer starts when the radar first detects the object, not when the object enters the specified zone in the scenario.
Filter on object type:
Go to Radar > Scenarios.
Select a scenario, and click to modify its settings.
To avoid triggering on specific object types, deselect the object types that should not trigger events in the scenario.
Adjust the radar image
This section includes instructions about configuring your device. If you want to learn more about how certain features work, go to Learn more.
Show an image overlay
You can add an image as an overlay in the radar stream.
Go to Radar > Overlays.
Select Image and click .
Click Images.
Drag and drop an image.
Click Upload.
Click Manage overlay.
Select the image and a position. You can also drag the overlay image in the live view to change the position.
Show a text overlay
You can add a text field as an overlay in the radar stream. This is useful for example when you want to display the date, time or a company name in the video stream.
Go to Radar > Overlays.
Select Text and click .
Type the text you want to display in the video stream.
Select a position. You can also drag the overlay text field in the live view to change the position.
Show a text overlay with the tilt angle of the radar
You can add an overlay in the radar’s live view that shows the tilt angle of the radar. This is helpful during installation, or whenever you need to know the tilt angle of the device.
The tilt angle overlay shows “90” when the device is horizontal. If the overlay shows “75”, the tilt angle of the radar is 15° below the horizon.
Go to Radar > Overlays.
Select Text and click .
Type #op.
You can also click Modifier and select #op from the list.
Select a position. You can also drag the overlay field in the live view to change the position.
View and record video
This section includes instructions about configuring your device. To learn more about how streaming and storage works, go to Streaming and storage.
Reduce bandwidth and storage
Reducing the bandwidth can result in loss of details in the image.
Go to Radar > Stream.
Click in the live view.
Select Video format H.264.
Go to Radar > Stream > General and increase Compression.
Most web browsers don’t support H.265 decoding and because of this the device doesn’t support it in its web interface. Instead you can use a video management system or application that supports H.265 decoding.
Set up network storage
- To store recordings on the network, you need to set up your network storage.
Go to System > Storage.
Click Add network storage under Network storage.
Type the IP address of the host server.
Type the name of the shared location on the host server under Network share.
Type the username and password.
Select the SMB version or leave it on Auto.
Select Add share without testing if you experience temporary connection issues, or if the share is not yet configured.
Click Add.
Record and watch video
- Record video directly from the radar
Go to Radar > Stream.
To start a recording, click .
If you haven’t set up any storage, click and . For instructions on how to set up network storage, see Set up network storage
To stop recording, click again.
- Watch video
Go to Recordings.
Click for your recording in the list.
Set up rules for events
To learn more, check out our guide Get started with rules for events.
Trigger an action
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.
Enter a Name.
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.
Select which Action the device should perform when the conditions are met.
If you make changes to an active rule, the rule must be turned on again for the changes to take effect.
If you change the definition of a stream profile that is used in a rule, then you need to restart all the rules that use that stream profile.
Record video from a camera when motion is detected
This example explains how to set up the radar and a camera so that the camera starts recording to the SD card five seconds before the radar detects motion and to stop one minute after.
- Connect the devices:
Connect a cable from an I/O output on the radar to an I/O input on the camera.
- Configure the I/O port of the radar:
Go to System > Accessories > I/O ports and configure the I/O port as an output and select the normal state.
- Create a rule in the radar:
Go to System > Events and add a rule.
Type a name for the rule.
From the list of conditions, select a scenario under Radar motion.
To set up a scenario, see Add scenarios.
From the list of actions, select Toggle I/O while the rule is active and then select the port that is connected to the camera.
Click Save.
- Configure the I/O port of the camera:
Go to System > Accessories > I/O ports and configure the I/O port as an input and select the normal state.
- Create a rule in the camera:
Go to System > Events and add a rule.
Type a name for the rule.
From the list of conditions, select Digital input is active and then select the port that should trigger the rule.
From the list of actions, select Record video.
From the list of storage options, select SD card.
Select an existing stream profile or create a new one.
Set the prebuffer to 5 seconds.
Set the postbuffer to 1 minute.
Click Save.
Record video from a camera when a vehicle drives in the wrong direction
This example explains how to set up the radar and a camera so that the camera starts recording to an SD card when the radar detects a vehicle that drives in the wrong direction.
Before you start
Create a scenario in the radar’s web interface that triggers on line crossing and vehicles crossing two lines.
See Add scenarios for more information.
Make sure to position the two lines over the traffic lane where you want to detect vehicles driving in the wrong direction. Use a reference map, such as an aerial photo, to make it easier to see where objects are moving.
See Calibrate a reference map for more information.
Create two recipients in the radar.
In the radar’s device interface, go to System > Events > Recipients and add the first recipient.
Add the following information:
Name: Activate virtual port
Type: HTTP
URL: http://<IPaddress>/axis-cgi/virtualinput/activate.cgi
Replace <IPaddress> with the address of the camera you want to start recording.
The username and password of the camera.
Click Test to make sure all data is valid.
Click Save.
Add a second recipient with the following information:
Name: Deactivate virtual port
Type: HTTP
URL: http://<IPaddress>/axis-cgi/virtualinput/deactivate.cgi
Replace <IPaddress> with the address of the camera.
The username and password of the camera.
Click Test to make sure all data is valid.
Click Save.
Create two rules in the radar.
In the radar’s device interface, go to System > Events > Rules and add the first rule.
Add the following information:
Name: Activate virtual IO1
Condition: Select the scenario you created under Radar motion.
Action: Notifications > Send notification through HTTP
Recipient: Activate virtual port
Query string suffix: schemaversion=1&port=1
Click Save.
Add another rule with the following information:
Name: Deactivate virtual IO1
Condition: Select the scenario you created under Radar motion.
Select Invert this condition.
Action: Notifications > Send notification through HTTP
Recipient: Deactivate virtual port
Query string suffix: schemaversion=1&port=1
Click Save.
Create a rule in the camera.
In the camera’s device interface, go to System > Events > Rules and add a rule.
Add the following information:
Name: Trigger on virtual input 1
Condition: I/O > Virtual input is active.
Port: 1
Action: Recordings > Record video while the rule is active
Storage options: SD_DISK
Select Camera and a Stream profile.
Click Save.
Activate a sweeping red light on the radar
You can use the dynamic LED strip on the front of the radar to show that the area is monitored.
This example explains how you activate a red sweeping light, and how you set up a schedule so that it only sweeps after working hours on weekdays.
- Create a schedule:
Go to System > Events > Schedules and add a schedule.
Type a name for the schedule.
Under Type, select Schedule.
Under Recurrent, select Daily.
Set the start time to 06:00 PM.
Set the end time to 06:00 AM.
Under Days, select Monday to Friday.
Click Save.
- Create a rule:
Go to System > Events and add a rule.
Type a name for the rule.
In the list of conditions, under Scheduled and recurring, select Schedule.
Select the schedule you created in the Schedule drop-down.
In the list of actions, under Radar, select Dynamic LED strip.
Select the pattern Sweeping red in the Pattern drop-down.
Set the duration to 12 hours.
Click Save.
Send an email if someone covers the radar with a metallic object
This example explains how to create a rule that sends an email notification when someone tampers with the radar by covering it with a metallic object, such as metallic foil or a metallic sheet.
The option to create rules for radar tampering events is available from AXIS OS 11.11.
- Add an email recipient:
Go to System > Events > Recipients and click Add recipient.
Type a name for the recipient.
Select Email.
Type an email address to send the email to.
The camera doesn’t have it’s own email server, so it will need to log into another email server to be able to send mails. Fill in the rest of the information according to your email provider.
To send a test email, click Test.
Click Save.
- Create a rule:
Go to System > Events and add a rule.
Type a name for the rule.
From the list of conditions, under Device status, select Radar data failure.
Under Reason, select Tampering.
From the list of actions, under Notifications, select Send notification to email.
Select the recipient you created.
Type a subject and a message for the email.
Click Save.
Turn on a light when motion is detected
Turning on a light when an intruder enters the detection zone can have a deterring effect, and will also improve the image quality of a visual camera recording the intrusion.
This example explains how to set up the radar and an illuminator so that the illuminator turns on when the radar detects motion and turns off after one minute.
- Connect the devices:
Connect one of the illuminator cables to the power supply via the relay port on the radar. Connect the other cable directly between the power supply and the illuminator.
- Configure the relay port of the radar:
Go to System > Accessories > I/O ports and select Open circuit as the normal state of the relay port.
- Create a rule in the radar:
Go to System > Events and add a rule.
Type a name for the rule.
From the list of conditions, select a scenario under Radar motion.
To set up a scenario, see Add scenarios.
From the list of actions, select Toggle I/O once and then select the relay port.
Select Active.
Set the Duration.
Click Save.
Control a PTZ camera with the radar
It’s possible to use the information about objects’ positions from the radar to make a PTZ camera track objects. There are two ways to do this:
Control a PTZ camera with the built-in radar autotracking service. The built-in option is suitable when you have a PTZ camera and radar mounted very close together.
Control a PTZ camera with AXIS Radar Autotracking for PTZ. The Windows application is suitable when you want to use multiple PTZ cameras and radars for tracking objects.
Use an NTP server to synchronize the time on the cameras, radars and the Windows computer. If the clocks are out of sync, you may experience delays in the tracking, or ghost tracking.
Control a PTZ camera with the built-in radar autotracking service
The built-in radar autotracking creates an edge-to-edge solution where the radar directly controls the PTZ camera. It supports all Axis PTZ cameras.
You can use the built-in radar autotracking service to connect one radar with one PTZ camera. For a setup where you want to use more than one radar or PTZ camera, use AXIS Radar Autotracking for PTZ. For more information, see Control a PTZ camera with AXIS Radar Autotracking for PTZ.
This instruction explains how to pair the radar with a PTZ camera, how to calibrate the devices, and how to set up the tracking of objects.
Before you start:
Define the area of interest and avoid unwanted alarms by setting up exclude zones in the radar. Make sure to exclude zones with radar-reflective materials or swaying objects, like foliage, to prevent the PTZ camera from tracking irrelevant objects. For instructions, see Add exclude zones.
- Pair the radar with the PTZ camera:
Go to System > Edge-to-edge > PTZ pairing.
Enter the IP address, username and password for the PTZ camera.
Click Connect.
Click Configure Radar autotracking or go to Radar > Radar PTZ autotracking to set up radar autotracking.
- Calibrate the radar and the PTZ camera:
Go to Radar > Radar PTZ autotracking.
To set the mounting height of the camera, go to Camera mounting height.
To pan the PTZ camera so that it points in the same direction as the radar, go to Pan alignment.
If you need to adjust the tilt to compensate for a sloping ground, go to Ground incline offset and add an offset in degrees.
- Set up the PTZ tracking:
Go to Track to select if you want to track humans, vehicles and/or unknown objects.
To start tracking objects with the PTZ camera, turn on Tracking.
The tracking automatically zooms in on an object, or a group of objects, to keep them in the view of the camera.
Turn on Object switching if you expect multiple objects that won’t fit in the camera view.
With this setting, the radar gives priority of the objects to track.
To determine how many seconds to track each object, set Object hold time.
To make the PTZ camera return to its home position when the radar no longer tracks any objects, turn on Return to home.
To determine how long the PTZ camera should stay at the tracked objects last known position before returning to home, set Return to home timeout.
To fine tune the zoom of the PTZ camera, adjust the zoom on the slider.
Control a PTZ camera with AXIS Radar Autotracking for PTZ
AXIS Radar Autotracking for PTZ is a server-based solution that can handle different setups when tracking objects:
Control several PTZ cameras with one radar.
Control one PTZ camera with several radars.
Control several PTZ cameras with several radars.
Control one PTZ camera with one radar when they are mounted in different positions covering the same area.
The application is compatible with a specific set of PTZ cameras. For more information, see axis.com/products/axis-radar-autotracking-for-ptz#compatible-products.
Download the application and see the user manual for information about how to set up the application. For more information, see axis.com/products/axis-radar-autotracking-for-ptz/support.
Use MQTT to send radar data
Use the radar with the application AXIS Speed Monitor to collect radar data for detected objects and send it over MQTT.
This example explains how to set up an MQTT client in the device where you have installed AXIS Speed Monitor, and how to create a condition that will publish the radar data collected in AXIS Speed Monitor as a payload to an MQTT broker.
- Before you start:
Install AXIS Speed Monitor in your radar, or install it in a camera that you connect to your radar.
For more information, see AXIS Speed Monitor user manual.
Set up an MQTT broker and get the broker’s IP address, username and password.
Learn more about MQTT and MQTT brokers in AXIS OS Knowledge Base.
- Set up the MQTT client in the web interface of the device where you have installed AXIS Speed Monitor:
Go to System > MQTT > MQTT client > Broker and enter the following information:
Host: The broker IP address
Client ID: The ID of the device
Protocol: The protocol the broker is set to
Port: The port number used by the broker
The broker Username and Password
Click Save and Connect.
- Create a condition that publishes the radar data as a payload to the MQTT broker:
Go to System > MQTT > MQTT publication and click + Add condition.
In the list of conditions, under Application, select Speed Monitor: Track exited zone.
The device will now be able to send information about the radar tracks for every moving object that exits a scenario. Every object will have its own radar track parameters, for example rmd_zone_name, tracking_id, and trigger_count. You can find the full list of parameters in AXIS Speed Monitor user manual.
The web interface
To reach the device’s web interface, type the device’s IP address in a web browser.
Support for the features and settings described in this section varies between devices. This icon indicates that the feature or setting is only available in some devices.
Show or hide the main menu. Access the release notes. Access the product help. Change the language. Set light theme or dark theme. The user menu contains:
The context menu contains:
|
Status
Device info
Shows the device information, including AXIS OS version and serial number.
Upgrade AXIS OS: Upgrade the software on your device. Takes you to the Maintenance page where you can do the upgrade. |
Time sync status
Shows NTP synchronization information, including if the device is in sync with an NTP server and the time remaining until the next sync.
NTP settings: View and update the NTP settings. Takes you to the Date and time page where you can change the NTP settings. |
Security
Shows what kind of access to the device that is active, what encryption protocols are in use, and if unsigned apps are allowed. Recommendations to the settings are based on the AXIS OS Hardening Guide.
Hardening guide: Link to AXIS OS Hardening guide where you can learn more about cybersecurity on Axis devices and best practices. |
Connected clients
Shows the number of connections and connected clients.
View details: View and update the list of connected clients. The list shows IP address, protocol, port, state, and PID/process of each connection. |
Ongoing recordings
Shows ongoing recordings and their designated storage space.
Recordings: View ongoing and filtered recordings and their source. For more information, see Recordings Shows the storage space where the recording is saved. |
Radar
Settings
General
Radar transmission: Use this to turn off the radar module completely. Channel: If you have problems with multiple devices interfering with each other, select the same channel for up to four devices that are close to each other. For most installations, select Auto to let the devices automatically negotiate which channel to use. Mounting height: Enter the mounting height for the product. Note Be as specific as you can when you enter the mounting height. This helps the device visualize the radar detection in the correct position in the image. |
Detection
Detection sensitivity: Select how sensitive the radar should be. A higher value means that you get a longer detection range, but there is also a higher risk of false alarms. A lower sensitivity decreases the number of false alarms, but it may shorten the detection range. Radar profile: Select a profile that suits your area of interest.
|
View
Information legend: Turn on to show a legend containing the object types the radar can detect and track. Drag and drop to move the information legend. Zone opacity: Select how opaque or transparent the coverage zone should be. Grid opacity: Select how opaque or transparent the grid should be. Color scheme: Select a theme for the radar visualization. Rotation: Select the preferred orientation of the radar image. |
Object visualization
Trail lifetime: Select how long the trail of a tracked object is visible in the radar view. Icon style: Select the icon style of the tracked objects in the radar view. For plain triangles, select Triangle. For representative symbols, select Symbol. The icons will point in the direction the tracked objects are moving, regardless of style.
|
Stream
General
Resolution: Select the image resolution suitable for the surveillance scene. A higher resolution increases bandwidth and storage. Frame rate: To avoid bandwidth problems on the network or reduce storage size, you can limit the frame rate to a fixed amount. If you leave the frame rate at zero, the frame rate is kept at the highest possible rate under the current conditions. A higher frame rate requires more bandwidth and storage capacity. P-frames: A P-frame is a predicted image that shows only the changes in the image from the previous frame. Enter the desired number of P-frames. The higher the number, the less bandwidth is required. However, if there is network congestion, there could be a noticeable deterioration in the video quality. Compression: Use the slider to adjust the image compression. High compression results in a lower bitrate and lower image quality. Low compression improves the image quality, but uses more bandwidth and storage when you record. Signed video: Turn on to add the signed video feature to the video. Signed video protects the video from tampering by adding cryptographic signatures to the video. |
Bitrate control
|
Map calibration
Use map calibration to upload and calibrate a reference map. The result of the calibration is a reference map that displays the radar coverage in the appropriate scale, which makes it easier to see where objects are moving.
Setup assistant: Click to open the setup assistant that guides you through the calibration step by step. Reset calibration: Click to remove the current map image and radar position on the map. |
Map
Upload map: Select or drag and drop the map image you want to upload. Download map: Click to download the map. Rotate map: Use the slider to rotate the map image. |
Scale and distance on map
Distance: Add the distance between the two points you have added to the map. |
Pan and zoom map
Pan: Click on the buttons to pan the map image. Zoom: Click on the buttons to zoom in or out on the map image. Reset pan and zoom: Click to remove the pan and zoom settings. |
Radar position
Position: Click on the buttons to move the radar on the map. Rotation: Click on the buttons to rotate the radar on the map. |
Exclude zones
An exclude zone is an area in which moving objects are ignored. Use exclude zones if there are areas inside a scenario that trigger a lot of unwanted alarms. : Click to create a new exclude zone. To modify an exclude zone, select it in the list. Track passing objects: Turn on to track objects that pass through the exclude zone. The passing objects keep their track IDs and are visible throughout the zone. Objects that appear from within the exclude zone will not be tracked. Zone shape presets: Select the initial shape of the exclude zone.
|
Scenarios
A scenario is a combination of triggering conditions, as well as scene and detection settings. : Click to create a new scenario. You can create up to 20 scenarios.
For Line crossing:
|
Overlays
: Click to add an overlay. Select the type of overlay from the dropdown list:
Widget: Meter: Show a bar chart that displays the most recently measured data value.
|
Dynamic LED strip
Dynamic LED strip patterns
Use this page to test the patterns of the dynamic LED strip. Pattern: Select the pattern you want to test. Duration: Specify the duration of the test. Test: Click to start the pattern you want to test. Stop: Click to stop the test. If you leave the page when a pattern plays, it will stop automatically. To activate a pattern for indication or deterrence purposes, go to System > Events and create a rule. For an example, see Activate a sweeping red light on the radar. |
Radar PTZ autotracking
Pair the radar with a PTZ camera to use radar autotracking. To establish the connection, go to System > Edge-to-edge.
Configure initial settings: Camera mounting height: The distance from the ground to the height of the mounted PTZ camera. Pan alignment: Pan the PTZ camera so that it points in the same direction as the radar. Click on the IP address of the PTZ camera to access it. Save pan offset: Click to save the pan alignment. Ground incline offset: Use the ground incline offset to fine tune the camera’s tilt. If the ground is sloped, or if the camera is not mounted horizontally, the camera may aim too high or too low when tracking an object. Done: Click to save your settings and continue with the configuration. |
Configure PTZ autotracking: Track: Select if you want to track humans, vehicles and/or unknown objects. Tracking: Turn on to start tracking objects with the PTZ camera. The tracking automatically zooms in on an object, or a group of objects, to keep them in the view of the camera. Object switching: If the radar detects multiple objects that won't fit in the PTZ camera's view, the PTZ camera tracks the object that the radar gives the highest priority, and ignores the others. Object hold time: Determines for how many seconds the PTZ camera should track each object. Return to home: Turn on to make the PTZ camera return to its home position when the radar no longer tracks any objects. Return to home timeout: Determines how long the PTZ camera should stay at the tracked objects last known position before returning to home. Zoom: Use the slider to fine tune the zoom of the PTZ camera. Reconfigure installation: Click to clear all settings and go back to the initial configuration. |
Recordings
Ongoing recordings: Show all ongoing recordings on the device. Start a recording on the device. Choose which storage device to save to. Stop a recording on the device. Triggered recordings will end when manually stopped or when the device is shut down. Continuous recordings will continue until manually stopped. Even if the device is shut down, the recording will continue when the device starts up again. |
Play the recording. Stop playing the recording. Show or hide information and options about the recording. Set export range: If you only want to export part of the recording, enter a time span. Note that if you work in a different time zone than the location of the device, the time span is based on the device’s time zone. Encrypt: Select to set a password for exported recordings. It will not be possible to open the exported file without the password. Click to delete a recording. Export: Export the whole or a part of the recording. |
Click to filter the recordings. From: Show recordings done after a certain point in time. To: Show recordings up until a certain point in time. Source: Show recordings based on source. The source refers to the sensor. Event: Show recordings based on events. Storage: Show recordings based on storage type. |
Apps
Add app: Install a new app. Find more apps: Find more apps to install. You will be taken to an overview page of Axis apps. Allow unsigned apps: Turn on to allow installation of unsigned apps. Allow root-privileged apps: Turn on to allow apps with root privileges full access to the device. View the security updates in AXIS OS and ACAP apps. Note The device’s performance might be affected if you run several apps at the same time. Use the switch next to the app name to start or stop the app. Open: Access the app’s settings. The available settings depend on the application. Some applications don’t have any settings. The context menu can contain one or more of the following options:
|
System
Time and location
Date and time
The time format depends on the web browser’s language settings.
We recommend you synchronize the device’s date and time with an NTP server.
Synchronization: Select an option for the device’s date and time synchronization.
Time zone: Select which time zone to use. Time will automatically adjust to daylight saving time and standard time.
Note The system uses the date and time settings in all recordings, logs, and system settings. |
Device location
Enter where the device is located. Your video management system can use this information to place the device on a map.
|
Regional settings
Sets the system of measurement to use in all system settings.
Metric (m, km/h): Select for distance measurement to be in meters and speed measurement to be in kilometers per hour. U.S. customary (ft, mph): Select for distance measurement to be in feet and speed measurement to be in miles per hour. |
Network
IPv4
Assign IPv4 automatically: Select to let the network router assign an IP address to the device automatically. We recommend automatic IP (DHCP) for most networks. IP address: Enter a unique IP address for the device. Static IP addresses can be assigned at random within isolated networks, provided that each address is unique. To avoid conflicts, we recommend you contact your network administrator before you assign a static IP address. Subnet mask: Enter the subnet mask to define what addresses are inside the local area network. Any address outside the local area network goes through the router. Router: Enter the IP address of the default router (gateway) used to connect devices that are attached to different networks and network segments. Fallback to static IP address if DHCP isn’t available: Select if you want to add a static IP address to use as fallback if DHCP is unavailable and can’t assign an IP address automatically. Note If DHCP isn’t available and the device uses a static address fallback, the static address is configured with a limited scope. |
IPv6
Assign IPv6 automatically: Select to turn on IPv6 and to let the network router assign an IP address to the device automatically. |
Hostname
Assign hostname automatically: Select to let the network router assign a hostname to the device automatically. Hostname: Enter the hostname manually to use as an alternative way of accessing the device. The server report and system log use the hostname. Allowed characters are A–Z, a–z, 0–9 and -. |
DNS servers
Assign DNS automatically: Select to let the DHCP server assign search domains and DNS server addresses to the device automatically. We recommend automatic DNS (DHCP) for most networks. Search domains: When you use a hostname that is not fully qualified, click Add search domain and enter a domain in which to search for the hostname the device uses. DNS servers: Click Add DNS server and enter the IP address of the DNS server. This provides the translation of hostnames to IP addresses on your network. |
HTTP and HTTPS
HTTPS is a protocol that provides encryption for page requests from users and for the pages returned by the web server. The encrypted exchange of information is governed by the use of an HTTPS certificate, which guarantees the authenticity of the server.
To use HTTPS on the device, you must install an HTTPS certificate. Go to System > Security to create and install certificates.
Allow access through: Select if a user is allowed to connect to the device through the HTTP, HTTPS, or both HTTP and HTTPS protocols. Note If you view encrypted web pages through HTTPS, you might experience a drop in performance, especially when you request a page for the first time. HTTP port: Enter the HTTP port to use. The device allows port 80 or any port in the range 1024-65535. If you are logged in as an administrator, you can also enter any port in the range 1-1023. If you use a port in this range, you get a warning. HTTPS port: Enter the HTTPS port to use. The device allows port 443 or any port in the range 1024-65535. If you are logged in as an administrator, you can also enter any port in the range 1-1023. If you use a port in this range, you get a warning. Certificate: Select a certificate to enable HTTPS for the device. |
Network discovery protocols
Bonjour®: Turn on to allow automatic discovery on the network. Bonjour name: Enter a friendly name to be visible on the network. The default name is the device name and MAC address. UPnP®: Turn on to allow automatic discovery on the network. UPnP name: Enter a friendly name to be visible on the network. The default name is the device name and MAC address. WS-Discovery: Turn on to allow automatic discovery on the network. LLDP and CDP: Turn on to allow automatic discovery on the network. Turning LLDP and CDP off can impact the PoE power negotiation. To resolve any issues with the PoE power negotiation, configure the PoE switch for hardware PoE power negotiation only. |
Global proxies
Http proxy: Specify a global proxy host or IP address according to the allowed format. Https proxy: Specify a global proxy host or IP address according to the allowed format.
Note Restart the device to apply the global proxy settings.
|
One-click cloud connection
One-click cloud connection (O3C) together with an O3C service provides easy and secure internet access to live and recorded video from any location. For more information, see axis.com/end-to-end-solutions/hosted-services.
Allow O3C:
Proxy settings: If needed, enter the proxy settings to connect to the proxy server. Host: Enter the proxy server’s address. Port: Enter the port number used for access. Login and Password: If needed, enter username and password for the proxy server. Authentication method:
Owner authentication key (OAK): Click Get key to fetch the owner authentication key. This is only possible if the device is connected to the internet without a firewall or proxy. |
SNMP
The Simple Network Management Protocol (SNMP) allows remote management of network devices.
SNMP: Select the version of SNMP to use.
Note All Axis Video MIB traps are enabled when you turn on SNMP v1 and v2c traps. For more information, see AXIS OS Portal > SNMP.
|
Security
Certificates
Certificates are used to authenticate devices on a network. The device supports two types of certificates:
These formats are supported:
Important If you reset the device to factory default, all certificates are deleted. Any pre-installed CA certificates are reinstalled. Add certificate : Click to add a certificate.
The context menu contains:
Secure keystore:
|
Network access control and encryption
IEEE 802.1x IEEE 802.1x is an IEEE standard for port-based network admission control providing secure authentication of wired and wireless network devices. IEEE 802.1x is based on EAP (Extensible Authentication Protocol). To access a network protected by IEEE 802.1x, network devices must authenticate themselves. The authentication is performed by an authentication server, typically a RADIUS server (for example, FreeRADIUS and Microsoft Internet Authentication Server). IEEE 802.1AE MACsec IEEE 802.1AE MACsec is an IEEE standard for media access control (MAC) security that defines connectionless data confidentiality and integrity for media access independent protocols. Certificates When configured without a CA certificate, server certificate validation is disabled and the device tries to authenticate itself regardless of what network it is connected to. When using a certificate, in Axis' implementation, the device and the authentication server authenticate themselves with digital certificates using EAP-TLS (Extensible Authentication Protocol - Transport Layer Security). To allow the device to access a network protected through certificates, you must install a signed client certificate on the device. Authentication method: Select an EAP type used for authentication. Client certificate: Select a client certificate to use IEEE 802.1x. The authentication server uses the certificate to validate the client’s identity. CA certificates: Select CA certificates to validate the authentication server’s identity. When no certificate is selected, the device tries to authenticate itself regardless of what network it is connected to. EAP identity: Enter the user identity associated with the client certificate. EAPOL version: Select the EAPOL version that is used in the network switch. Use IEEE 802.1x: Select to use the IEEE 802.1x protocol. These settings are only available if you use IEEE 802.1x PEAP-MSCHAPv2 as the authentication method:
These settings are only available if you use IEEE 802.1ae MACsec (Static CAK/Pre-Shared Key) as the authentication method:
|
Prevent brute-force attacks
Blocking: Turn on to block brute-force attacks. A brute-force attack uses trial-and-error to guess login info or encryption keys. Blocking period: Enter the number of seconds to block a brute-force attack. Blocking conditions: Enter the number of authentication failures allowed per second before the block starts. You can set the number of failures allowed both on page level and device level. |
Firewall
Activate: Turn on the firewall.
To make exceptions to the default policy, you can create rules that allows or denies connections to the device from specific addresses, protocols, and ports.
: Click to create another rule.
Pending rules: An overview of the latest tested rules that you are yet to confirm. Note The rules that have a time limit appear under Active rules until the displayed timer runs out, or until you confirm them. If you don't confirm them, they will appear under Pending rules once the timer runs out, and the firewall will revert to the previously defined settings. If you confirm them, they will replace the current active rules. Confirm rules: Click to activate the pending rules. Active rules: An overview of the rules you are currently running on the device. : Click to delete an active rule. : Click to delete all rules, both pending and active. |
Custom signed AXIS OS certificate
To install test software or other custom software from Axis on the device, you need a custom signed AXIS OS certificate. The certificate verifies that the software is approved by both the device owner and Axis. The software can only run on a specific device which is identified by its unique serial number and chip ID. Only Axis can create custom signed AXIS OS certificates, since Axis holds the key to sign them. Install: Click to install the certificate. You need to install the certificate before you install the software. The context menu contains:
|
Accounts
Accounts
Add account: Click to add a new account. You can add up to 100 accounts. Account: Enter a unique account name. New password: Enter a password for the account. Passwords must be 1 to 64 characters long. Only ASCII printable characters (code 32 to 126) are allowed in the password, for example, letters, numbers, punctuation, and some symbols. Repeat password: Enter the same password again. Privileges:
The context menu contains: Update account: Edit the account properties. Delete account: Delete the account. You can’t delete the root account. |
Anonymous access
Allow anonymous viewing: Turn on to allow anyone access the device as a viewer without logging in with an account. Allow anonymous PTZ operating: Turn on to allow anonymous users to pan, tilt, and zoom the image. |
SSH accounts
Add SSH account: Click to add a new SSH account.
Account: Enter a unique account name. New password: Enter a password for the account. Passwords must be 1 to 64 characters long. Only ASCII printable characters (code 32 to 126) are allowed in the password, for example, letters, numbers, punctuation, and some symbols. Repeat password: Enter the same password again. Comment: Enter a comment (optional). The context menu contains: Update SSH account: Edit the account properties. Delete SSH account: Delete the account. You can’t delete the root account. |
Virtual host
Add virtual host: Click to add a new virtual host. Enabled: Select to use this virtual host. Server name: Enter the name of the server. Only use numbers 0-9, letters A-Z, and hyphen (-). Port: Enter the port the server is connected to. Type: Select the type of authentication to use. Select between Basic, Digest, and Open ID. The context menu contains:
Disabled: The server is disabled. |
OpenID Configuration
If you can't use OpenID to sign in, use the Digest or Basic credentials you used when you configured OpenID to sign in.
Client ID: Enter the OpenID username. Outgoing Proxy: Enter the proxy address for the OpenID connection to use a proxy server. Admin claim: Enter a value for the admin role. Provider URL: Enter the web link for the API endpoint authentication. Format should be https://[insert URL]/.well-known/openid-configuration Operator claim: Enter a value for the operator role. Require claim: Enter the data that should be in the token. Viewer claim: Enter the value for the viewer role. Remote user: Enter a value to identify remote users. This assists to display the current user in the device’s web interface. Scopes: Optional scopes that could be part of the token. Client secret: Enter the OpenID password Save: Click to save the OpenID values. Enable OpenID: Turn on to close current connection and allow device authentication from the provider URL. |
Events
Rules
A rule defines the conditions that triggers the product to perform an action. The list shows all the currently configured rules in the product.
You can create up to 256 action rules.
Add a rule: Create a rule. Name: Enter a name for the rule. Wait between actions: Enter the minimum time (hh:mm:ss) that must pass between rule activations. It is useful if the rule is activated by, for example, day-night mode conditions, to avoid that small light changes during sunrise and sunset activate the rule repeatedly. Condition: Select a condition from the list. A condition must be met for the device to perform an action. If multiple conditions are defined, all of them must be met to trigger the action. For information about specific conditions, see Get started with rules for events. Use this condition as a trigger: Select to make this first condition function only as a starting trigger. It means that once the rule is activated, it remains active for as long as all the other conditions are met, no matter the state of the first condition. If you don’t select this option, the rule will simply be active whenever all the conditions are met. Invert this condition: Select if you want the condition to be the opposite of your selection. Add a condition: Click to add an additional condition. Action: Select an action from the list and enter its required information. For information about specific actions, see Get started with rules for events. |
Recipients
You can set up your device to notify recipients about events or send files.
If you set up your device to use FTP or SFTP, don’t change or remove the unique sequence number that’s added to the file names. If you do that, only one image per event can be sent.
The list shows all the recipients currently configured in the product, along with information about their configuration.
You can create up to 20 recipients.
Add a recipient: Click to add a recipient. Name: Enter a name for the recipient. Type: Select from the list:
Test: Click to test the setup. The context menu contains: View recipient: Click to view all the recipient details. Copy recipient: Click to copy a recipient. When you copy, you can make changes to the new recipient. Delete recipient: Click to delete the recipient permanently. |
Schedules
Schedules and pulses can be used as conditions in rules. The list shows all the schedules and pulses currently configured in the product, along with information about their configuration. Add schedule: Click to create a schedule or pulse. |
Manual triggers
You can use the manual trigger to manually trigger a rule. The manual trigger can, for example, be used to validate actions during product installation and configuration. |
MQTT
MQTT (Message Queuing Telemetry Transport) is a standard messaging protocol for the Internet of Things (IoT). It was designed for simplified IoT integration and is used in a wide variety of industries to connect remote devices with a small code footprint and minimal network bandwidth. The MQTT client in Axis device software can simplify integration of data and events produced in the device to systems which are not video management software (VMS). Set up the device as an MQTT client. MQTT communication is based on two entities, the clients and the broker. The clients can send and receive messages. The broker is responsible for routing messages between clients. You can learn more about MQTT in AXIS OS Portal. |
ALPN
ALPN is a TLS/SSL extension that allows for the selection of an application protocol during the handshake phase of the connection between the client and server. This is used to enable MQTT traffic over the same port that is used for other protocols, such as HTTP. In some cases, there might not be a dedicated port open for MQTT communication. A solution in such cases is to use ALPN to negotiate the use of MQTT as the application protocol on a standard port, allowed by the firewalls. |
MQTT client
Connect: Turn on or off the MQTT client. Status: Shows the current status of the MQTT client. Broker Host: Enter the hostname or IP address of the MQTT server. Protocol: Select which protocol to use. Port: Enter the port number.
ALPN protocol: Enter the ALPN protocol name provided by your MQTT broker provider. This is only applicable with MQTT over SSL and MQTT over WebSocket Secure. Username: Enter the username that the client will use to access the server. Password: Enter a password for the username. Client ID: Enter a client ID. The client identifier is sent to the server when the client connects to it. Clean session: Controls the behavior at connection and disconnection time. When selected, the state information is discarded at connect and disconnect. HTTP proxy: A URL with a maximum length of 255 bytes. You can leave the field empty if you don't want to use an HTTP proxy. HTTPS proxy: A URL with a maximum length of 255 bytes. You can leave the field empty if you don't want to use an HTTPS proxy. Keep alive interval: Enables the client to detect when the server is no longer available without having to wait for the long TCP/IP timeout. Timeout: The time interval in seconds to allow a connect to complete. Default value: 60 Device topic prefix: Used in the default values for the topic in the connect message and LWT message on the MQTT client tab, and in the publication conditions on the MQTT publication tab. Reconnect automatically: Specifies whether the client should reconnect automatically after a disconnect. Connect message Specifies if a message should be sent out when a connection is established. Send message: Turn on to send messages. Use default: Turn off to enter your own default message. Topic: Enter the topic for the default message. Payload: Enter the content for the default message. Retain: Select to keep the state of client on this Topic QoS: Change the QoS layer for the packet flow. Last Will and Testament message The Last Will Testament (LWT) lets a client provide a testament along with its credentials when connecting to the broker. If the client disconnects ungracefully at some point later (maybe because his power source died), it can let the broker deliver a message to other clients. This LWT message has the same form as an ordinary message and gets routed via the same mechanics. Send message: Turn on to send messages. Use default: Turn off to enter your own default message. Topic: Enter the topic for the default message. Payload: Enter the content for the default message. Retain: Select to keep the state of client on this Topic QoS: Change the QoS layer for the packet flow. |
MQTT publication
Use default topic prefix: Select to use the default topic prefix, that is defined in the device topic prefix in the MQTT client tab. Include topic name: Select to include the topic that describes the condition in the MQTT topic. Include topic namespaces: Select to include ONVIF topic namespaces in the MQTT topic. Include serial number: Select to include the device’s serial number in the MQTT payload. Add condition: Click to add a condition. Retain: Defines which MQTT messages are sent as retained.
QoS: Select the desired level for the MQTT publication. |
MQTT subscriptions
Add subscription: Click to add a new MQTT subscription. Subscription filter: Enter the MQTT topic that you want to subscribe to. Use device topic prefix: Add the subscription filter as prefix to the MQTT topic. Subscription type:
QoS: Select the desired level for the MQTT subscription. |
MQTT overlays
Note Connect to an MQTT broker before you add MQTT overlay modifiers. Add overlay modifier: Click to add a new overlay modifier. Topic filter: Add the MQTT topic that contains the data you want to show in the overlay. Data field: Specify the key for the message payload that you want to show in the overlay, assuming the message is in JSON format.
|
Storage
Network storage
Ignore: Turn on to ignore network storage. Add network storage: Click to add a network share where you can save recordings.
Remove network storage: Click to unmount, unbind, and remove the connection to the network share. This removes all settings for the network share. Unbind: Click to unbind and disconnect the network share. Unmount: Click to unmount the network share. Write protect: Turn on to stop writing to the network share and protect recordings from being removed. You can’t format a write-protected network share. Retention time: Select how long to keep recordings, to limit the amount of old recordings, or to comply with regulations regarding data storage. If the network storage becomes full, old recordings are removed before the selected time period passes. Tools
|
Onboard storage
Important Risk of data loss and corrupted recordings. Do not remove the SD card while the device is running. Unmount the SD card before you remove it. Unmount: Click to safely remove the SD card. Write protect: Turn on to stop writing to the SD card and protect recordings from being removed. You can’t format a write-protected SD card. Autoformat: Turn on to automatically format a newly inserted SD card. It formats the file system into ext4. Ignore: Turn on to stop storing recordings on the SD card. When you ignore the SD card, the device no longer recognizes that the card exists. The setting is only available to administrators. Retention time: Select how long to keep recordings to limit the amount of old recordings or comply with data storage regulations. When the SD card is full, it deletes old recordings before their retention time has passed. Tools
Wear trigger: Set a value for the SD card wear level at which you want to trigger an action. The wear level ranges from 0–200%. A new SD card that has never been used has a wear level of 0%. A wear level of 100% indicates that the SD card is close to its expected lifetime. When the wear-level reaches 200%, there is a high risk of the SD card malfunctioning. We recommend setting the wear trigger between 80–90%. This gives you time to download any recordings as well as replace the SD card in time before it potentially wears out. The wear trigger allows you to set up an event and get a notification when the wear level reaches your set value. |
Stream profiles
A stream profile is a group of settings that affect the video stream. You can use stream profiles in different situations, for example, when you create events and use rules to record.
Add stream profile: Click to create a new stream profile. Preview: A preview of the video stream with the stream profile settings you select. The preview updates when you change the settings on the page. If your device has different view areas, you can change the view area in the drop-down in the bottom left corner of the image. Name: Add a name for your profile. Description: Add a description of your profile. Video codec: Select the video codec that should apply for the profile. Resolution: See for a description of this setting. Frame rate: See for a description of this setting. Compression: See for a description of this setting. Zipstream: See for a description of this setting. Optimize for storage: See for a description of this setting. Dynamic FPS: See for a description of this setting. Dynamic GOP: See for a description of this setting. Mirror: See for a description of this setting. GOP length: See for a description of this setting. Bitrate control: See for a description of this setting. Include overlays: Select what type of overlays to include. See Overlays for information about how to add overlays. Include audio: See for a description of this setting. |
ONVIF
ONVIF accounts
ONVIF (Open Network Video Interface Forum) is a global interface standard that makes it easier for end-users, integrators, consultants, and manufacturers to take advantage of the possibilities offered by network video technology. ONVIF enables interoperability between different vendor products, increased flexibility, reduced cost and future-proof systems.
When you create an ONVIF account, you automatically enable ONVIF communication. Use the account name and password for all ONVIF communication with the device. For more information see the Axis Developer Community at axis.com.
Add accounts: Click to add a new ONVIF account. Account: Enter a unique account name. New password: Enter a password for the account. Passwords must be 1 to 64 characters long. Only ASCII printable characters (code 32 to 126) are allowed in the password, for example, letters, numbers, punctuation, and some symbols. Repeat password: Enter the same password again. Role:
The context menu contains: Update account: Edit the account properties. Delete account: Delete the account. You can’t delete the root account. |
ONVIF media profiles
An ONVIF media profile consists of a set of configurations that you can use to change media stream settings. You can create new profiles with your own set of configurations or use preconfigured profiles for a quick setup.
Add media profile: Click to add a new ONVIF media profile. Profile name: Add a name for the media profile. Video source: Select the video source for your configuration.
Video encoder: Select the video encoding format for your configuration.
Note Enable audio in the device to get the option to select an audio source and audio encoder configuration. Audio source: Select the audio input source for your configuration.
Audio encoder: Select the audio encoding format for your configuration.
Audio decoder: Select the audio decoding format for your configuration.
Audio output: Select the audio output format for your configuration.
Metadata: Select the metadata to include in your configuration.
PTZ: Select the PTZ settings for your configuration.
Create: Click to save your settings and create the profile. Cancel: Click to cancel the configuration and clear all settings. profile_x: Click on the profile name to open and edit the preconfigured profile. |
Detectors
Shock detection
Shock detector: Turn on to generate an alarm if the device is hit by an object or if it is tampered with. Sensitivity level: Move the slider to adjust the sensitivity level at which the device should generate an alarm. A low value means that the device only generates an alarm if the hit is powerful. A high value means that the device generates an alarm even with mild tampering. |
Accessories
I/O ports
Use digital input to connect external devices that can toggle between an open and closed circuit, for example, PIR sensors, door or window contacts, and glass break detectors.
Use digital output to connect external devices such as relays and LEDs. You can activate connected devices through the VAPIX® Application Programming Interface or the web interface.
Port Name: Edit the text to rename the port. Direction: indicates that the port is an input port. indicates that it’s an output port. If the port is configurable, you can click the icons to change between input and output. Normal state: Click for open circuit, and for closed circuit. Current state: Shows the current state of the port. The input or output is activated when the current state is different from the normal state. An input on the device has an open circuit when it’s disconnected or when there is a voltage above 1 V DC. Note During restart, the output circuit is open. When the restart is complete, the circuit goes back to the normal position. If you change any settings on this page, the output circuits go back to their normal positions regardless of any active triggers. Supervised: Turn on to make it possible to detect and trigger actions if someone tampers with the connection to digital I/O devices. In addition to detecting if an input is open or closed, you can also detect if someone has tampered with it (that is, cut or shorted). To supervise the connection requires additional hardware (end-of-line resistors) in the external I/O loop. |
Edge-to-edge
Audio pairing allows you to use a compatible Axis network speaker as if it’s part of the main device. Once paired, the network speaker acts as an audio out device where you can play audio clips and transmit sound.
For this feature to work with a video management software (VMS), you must first pair the device with the speaker, then add the device to your VMS.
Set a 'Wait between actions (hh:mm:ss)' limit in the event rule when you use a network paired audio device in an event rule with 'Audio detection' as condition and 'Play audio clip' as action. This will help you avoid a looping detection if the capturing microphone picks up audio from the speaker.
Audio pairing Address: Enter the host name or IP address of the network speaker. Username: Enter username. Password: Enter password for the user. Speaker pairing: Select to pair a network speaker. Clear fields: Click to clear all fields. Connect: Click to establish connection to the speaker. |
PTZ pairing allows you to pair a radar with a PTZ camera to use autotracking. Radar PTZ autotracking makes the PTZ camera track objects based on information from the radar about the objects’ positions.
PTZ pairing Address: Enter host name or IP address of the PTZ camera. Username: Enter the username of the PTZ camera. Password: Enter the password for the PTZ camera. Clear fields: Click to clear all fields. Connect: Click to establish connection to the PTZ camera. Configure radar autotracking: Click to open and configure autotracking. You can also go to Radar > Radar PTZ autotracking to configure. |
Logs
Reports and logs
Reports
Logs
|
Network trace
Important A network trace file might contain sensitive information, for example certificates or passwords. A network trace file can help you troubleshoot problems by recording activity on the network. Trace time: Select the duration of the trace in seconds or minutes, and click Download. |
Remote system log
Syslog is a standard for message logging. It allows separation of the software that generates messages, the system that stores them, and the software that reports and analyzes them. Each message is labeled with a facility code, which indicates the software type generating the message, and assigned a severity level.
Server: Click to add a new server. Host: Enter the hostname or IP address of the server. Format: Select which syslog message format to use.
Protocol: Select the protocol to use:
Port: Edit the port number to use a different port. Severity: Select which messages to send when triggered. CA certificate set: See the current settings or add a certificate. |
Plain config
Plain config is for advanced users with experience of Axis device configuration. Most parameters can be set and edited from this page. |
Maintenance
Restart: Restart the device. This does not affect any of the current settings. Running applications restart automatically. Restore: Return most settings to the factory default values. Afterwards you must reconfigure the device and apps, reinstall any apps that didn’t come preinstalled, and recreate any events and presets. Important The only settings saved after restore are:
Factory default: Return all settings to the factory default values. Afterwards you must reset the IP address to make the device accessible. Note All Axis device software is digitally signed to ensure that you only install verified software on your device. This further increases the overall minimum cybersecurity level of Axis devices. For more information, see the white paper “Axis Edge Vault” at axis.com. AXIS OS upgrade: Upgrade to a new AXIS OS version. New releases can contain improved functionality, bug fixes, and completely new features. We recommend you to always use the latest AXIS OS release. To download the latest release, go to axis.com/support.
AXIS OS rollback: Revert to the previously installed AXIS OS version. |
Validate your installation
Validate the installation of the radar
This test helps you to validate your installation under current conditions. The everyday performance of your installation can be affected by changes in the scene.
The radar is ready to use as soon as it is installed, however, we recommend that you perform a validation before you start to use it. This can increase the accuracy of the radar by helping you to identify any problems with the installation or manage objects (such as trees and reflective surfaces) in the scene.
First before attempting the validation. Then follow these steps:
Check that there are no false detections
Check that the detection zone is clear from human activity.
Wait for a few minutes to ensure that the radar is not detecting any static objects in the detection zone.
If there are no unwanted detections you can skip step 4.
If there are unwanted detections, learn how to filter out certain types of movement or objects, change the coverage, or adjust the detection sensitivity in Minimize false alarms.
Check for the correct symbol and direction of travel when the radar is approached from the front
Go into the radar’s web interface and record the session. For help doing this, go to Record and watch video.
Start up to 60 m (196 ft) in front of the radar and walk directly towards the radar.
Check the session in the radar’s web interface. The symbol for a human classification should appear when you are detected.
Check that the radar’s web interface shows the correct direction of travel.
Check for the correct symbol and direction of travel when the radar is approached from the side
Go into the radar’s web interface and record the session. For help doing this, go to Record and watch video.
Start 30 m (98 ft) out from the radar and walk straight across the radar coverage area.
Check that the radar’s web interface shows the symbol for a human classification.
Check that the radar’s web interface shows the correct direction of travel.
Create a table similar to the one below to help you record the data from your validation.
Test | Pass/Fail | Comment |
1. Check that there are no unwanted detections when the area is clear | ||
2a. Check that the object is detected with the correct symbol for ‘Human’ when the radar is approached from the front | ||
2b. Check that the direction of travel is correct when the radar is approached from the front | ||
3a. Check that the object is detected with the correct symbol for ‘Human’ when the radar is approached from the side | ||
3b. Check that the direction of travel is correct when the radar is approached from the side |
Complete the validation
Once you have successfully completed the first part of the validation, perform the following tests to complete the validation process.
Make sure you have configured your radar and followed the instructions.
For further validation, add and calibrate a reference map.
Set the radar scenario to trigger when an appropriate object is detected. By default, seconds until trigger is set to two seconds but you can change this in the web interface if needed.
Set the radar to record data when an appropriate object is detected.
See Record and watch video for instructions.
Set the trail lifetime to one hour so that it will safely exceed the time it takes for you to leave your seat, walk around the area of surveillance, and return to your seat. The trail lifetime will keep the track in the radar's live view for the set time and, once you have finished the validation, it can be disabled.
Walk along the border of the radar coverage area and make sure that the trailing on the system matches the route that you walked.
If you are unsatisfied with the results of your validation, re-calibrate the reference map and repeat the validation.
Learn more
Streaming and storage
Video compression formats
Decide which compression method to use based on your viewing requirements, and on the properties of your network. The available options are:
Motion JPEG
Motion JPEG, or MJPEG, is a digital video sequence that is made up of a series of individual JPEG images. These images are then displayed and updated at a rate sufficient to create a stream that shows constantly updated motion. For the viewer to perceive motion video the rate must be at least 16 image frames per second. Full motion video is perceived at 30 (NTSC) or 25 (PAL) frames per second.
The Motion JPEG stream uses considerable amounts of bandwidth, but provides excellent image quality and access to every image contained in the stream.
H.264 or MPEG-4 Part 10/AVC
H.264 is a licensed technology. The Axis product includes one H.264 viewing client license. To install additional unlicensed copies of the client is prohibited. To purchase additional licenses, contact your Axis reseller.
H.264 can, without compromising image quality, reduce the size of a digital video file by more than 80% compared to the Motion JPEG format and by as much as 50% compared to older MPEG formats. This means that less network bandwidth and storage space are required for a video file. Or seen another way, higher video quality can be achieved for a given bitrate.
H.265 or MPEG-H Part 2/HEVC
H.265 can, without compromising image quality, reduce the size of a digital video file by more than 25% compared to H.264.
- H.265 is licensed technology. The Axis product includes one H.265 viewing client license. Installing additional unlicensed copies of the client is prohibited. To purchase additional licenses, contact your Axis reseller.
- Most web browsers don’t support H.265 decoding and because of this the camera doesn’t support it in its web interface. Instead you can use a video management system or application supporting H.265 decoding.
Bitrate control
Bitrate control helps you to manage the bandwidth consumption of your video stream.
Variable bitrate (VBR)
Variable bitrate allows the bandwidth consumption to vary depending on the level of activity in the scene. The more activity, the more bandwidth you need. With variable bitrate you are guaranteed constant image quality, but you need to make sure you have storage margins.
Maximum bitrate (MBR)
Maximum bitrate lets you set a target bitrate to handle bitrate limitations in your system. You might see a decline in image quality or frame rate as the instantaneous bitrate is kept below the specified target bitrate. You can choose to prioritize either image quality or frame rate. We recommend that you configure the target bitrate to a higher value than the expected bitrate. This gives you a margin in case there is a high level of activity in the scene.
Average bitrate (ABR)
With average bitrate, the bitrate is automatically adjusted over a longer period of time. This is so you can meet the specified target and provide the best video quality based on your available storage. Bitrate is higher in scenes with a lot of activity, compared to static scenes. You are more likely to get better image quality when in scenes with a lot of activity if you use the average bitrate option. You can define the total storage required to store the video stream for a specified amount of time (retention time) when image quality is adjusted to meet the specified target bitrate. Specify the average bitrate settings in one of the following ways:
To calculate the estimated storage need, set the target bitrate and the retention time.
To calculate the average bitrate, based on available storage and required retention time, use the target bitrate calculator.
- Target bitrate
- Actual average bitrate
- You can also turn on maximum bitrate and specify a target bitrate within the average bitrate option.
- Target bitrate
- Actual average bitrate
Overlays
Overlays are superimposed over the video stream. They are used to provide extra information during recordings, such as a timestamp, or during product installation and configuration. You can add either text or an image.
Specifications
Product overview
LED indicators
- The Status LED can be configured to flash while an event is active.
Status LED | Indication |
Green | Steady green for normal operation. |
Amber | Steady during startup. Flashes during device software upgrade or reset to factory default. |
Red | Device software upgrade failure. |
Dynamic LED strip patterns |
Red |
Blue |
Green |
Yellow |
White |
Sweeping red |
Sweeping blue |
Sweeping green |
Flashing red, blue, white |
SD card slot
This device supports microSD/microSDHC/microSDXC cards.
For SD card recommendations, see axis.com.
microSD, microSDHC, and microSDXC Logos are trademarks of SD-3C LLC. microSD, microSDHC, microSDXC are trademarks or registered trademarks of SD-3C, LLC in the United States, other countries or both.
Buttons
Control button
- The control button is used for:
Resetting the product to factory default settings. See Reset to factory default settings.
Connecting to a one-click cloud connection (O3C) service over the internet. To connect, press and hold the button for about 3 seconds until the status LED flashes green.
Connectors
Network connector (PoE in)
RJ45 Ethernet connector with Power over Ethernet IEEE 802.3bt, Type 3 Class 6.
Power over Ethernet IEEE 802.3bt, Type 3 Class 6, is required for PoE out. When not powering a second device, Power over Ethernet IEEE 802.3at, Type 2 Class 4, is sufficient.
Network connector (PoE out)
RJ45 Ethernet connector supplying Power over Ethernet IEEE 802.3at, Type 2 Class 4, max 30 W.
Use this connector to supply power to another PoE device, for example a camera, a horn speaker, or a second Axis radar.
The PoE output is enabled when the radar is powered by a 60 W midspan (Power over Ethernet IEEE 802.3bt, type 3).
If the radar is powered by a 30 W midspan or DC power, the PoE out is disabled.
Maximum Ethernet cable length is 100 m in total for PoE out and PoE in combined. You can increase it with a PoE extender.
If the connected PoE device requires more than 30 W, you can add a 60 W midspan between the PoE out port on the radar and the device. The midspan will power the device while the radar will provide the Ethernet connection.
I/O connector
Use the I/O connector with external devices in combination with, for example, event triggering and alarm notifications. In addition to the 0 V DC reference point and power (DC output), the I/O connector provides the interface to:
- Digital input
- For connecting devices that can toggle between an open and closed circuit, for example PIR sensors, door/window contacts, and glass break detectors.
- Supervised input
- Enables possibility to detect tampering on a digital input.
- Digital output
- For connecting external devices such as relays and LEDs. Connected devices can be activated by the VAPIX® Application Programming Interface, through an event or from the device’s web interface.
4-pin terminal block
Function | Pin | Notes | Specifications |
DC ground | 1 | 0 V DC | |
DC output | 2 | Can be used to power auxiliary equipment. Note: This pin can only be used as power out. | 12 V DC Max load = 25 mA |
Digital Input | 3 | Connect to pin 1 to activate, or leave floating (unconnected) to deactivate. | 0 to max 30 V DC |
Digital Output | 4 | Internally connected to pin 1 (DC ground) when active, and floating (unconnected) when inactive. If used with an inductive load, e.g., a relay, connect a diode in parallel with the load, to protect against voltage transients. | 0 to max 30 V DC, open drain, 100 mA |
Example
Power connector
2-pin terminal block for DC power input. Use a Safety Extra Low Voltage (SELV) compliant limited power source (LPS) with either a rated output power limited to ≤100 W or a rated output current limited to ≤5 A.
Clean your device
You can clean your device with lukewarm water.
- Harsh chemicals can damage the device. Don’t use chemicals such as window cleaner or acetone to clean your device.
- Avoid cleaning in direct sunlight or elevated temperatures, since this can cause stains.
Use a can of compressed air to remove dust and loose dirt from the device.
If necessary, clean the device with a soft microfiber cloth dampened with lukewarm water.
To avoid stains, dry the device with a clean, nonabrasive cloth.
Troubleshooting
Reset to factory default settings
Reset to factory default should be used with caution. A reset to factory default resets all settings, including the IP address, to the factory default values.
To reset the product to the factory default settings:
Disconnect power from the product.
Press and hold the control button while reconnecting power. See Product overview.
Keep the control button pressed for 15–30 seconds until the status LED indicator flashes amber.
Release the control button. The process is complete when the status LED indicator turns green. If no DHCP server is available on the network, the device IP address will default to one of the following:
Devices with AXIS OS 12.0 and later: Obtained from the link-local address subnet (169.254.0.0/16)
Devices with AXIS OS 11.11 and earlier: 192.168.0.90/24
Use the installation and management software tools to assign an IP address, set the password, and access the device.
The installation and management software tools are available from the support pages on axis.com/support.
You can also reset parameters to factory default through the device’s web interface. Go to Maintenance > Factory default and click Default.
Check the current AXIS OS version
AXIS OS determines the functionality of our devices. When you troubleshoot a problem, we recommend that you to start by checking the current AXIS OS version. The latest version might contain a correction that fixes your particular problem.
To check the current AXIS OS version:
Go to the device’s web interface > Status.
Under Device info, see the AXIS OS version.
Upgrade AXIS OS
- Preconfigured and customized settings are saved when you upgrade the device software (provided that the features are available in the new AXIS OS) although this is not guaranteed by Axis Communications AB.
- Make sure the device remains connected to the power source throughout the upgrade process.
When you upgrade the device with the latest AXIS OS version in the active track, the product receives the latest functionality available. Always read the upgrade instructions and release notes available with each new release before you upgrade. To find the latest AXIS OS version and the release notes, go to axis.com/support/device-software.
Download the AXIS OS file to your computer, available free of charge at axis.com/support/device-software.
Log in to the device as an administrator.
Go to Maintenance > AXIS OS upgrade and click Upgrade.
- When the upgrade has finished, the product restarts automatically.
Technical issues, clues, and solutions
If you can’t find what you’re looking for here, try the troubleshooting section at axis.com/support.
Problems upgrading AXIS OS | |
AXIS OS upgrade failure | If the upgrade fails, the device reloads the previous version. The most common reason is that the wrong AXIS OS file has been uploaded. Check that the name of the AXIS OS file corresponds to your device and try again. |
Problems after AXIS OS upgrade | If you experience problems after the upgrade, roll back to the previously installed version from the Maintenance page. |
Problems setting the IP address | |||||
The device is located on a different subnet | If the IP address intended for the device and the IP address of the computer used to access the device are located on different subnets, you cannot set the IP address. Contact your network administrator to obtain an IP address. | ||||
The IP address is being used by another device | Disconnect the Axis device from the network. Run the ping command (in a Command/DOS window, type
| ||||
Possible IP address conflict with another device on the same subnet | The static IP address in the Axis device is used before the DHCP server sets a dynamic address. This means that if the same default static IP address is also used by another device, there may be problems accessing the device. |
The device can’t be accessed from a browser | ||||||||||||
Can’t log in | When HTTPS is enabled, ensure that the correct protocol (HTTP or HTTPS) is used when attempting to log in. You may need to manually type If the password for the root account is lost, the device must be reset to the factory default settings. See Reset to factory default settings. | |||||||||||
The IP address has been changed by DHCP | IP addresses obtained from a DHCP server are dynamic and may change. If the IP address has been changed, use AXIS IP Utility or AXIS Device Manager to locate the device on the network. Identify the device using its model or serial number, or by the DNS name (if the name has been configured). If required, a static IP address can be assigned manually. For instructions, go to axis.com/support. | |||||||||||
Certificate error when using IEEE 802.1X | For authentication to work properly, the date and time settings in the Axis device must be synchronized with an NTP server. Go to System > Date and time. |
The device is accessible locally but not externally | |||||||||||||||||||
To access the device externally, we recommend you to use one of the following applications for Windows®:
For instructions and download, go to axis.com/vms. |
Can’t connect over port 8883 with MQTT over SSL | |||||||||||||||||||||
The firewall blocks traffic using port 8883 as it’s deemed insecure. | In some cases the server/broker might not provide a specific port for MQTT communication. It may still be possible to use MQTT over a port normally used for HTTP/HTTPS traffic.
|
Performance considerations
When setting up your system, it is important to consider how various settings and situations affect the amount of needed bandwidth (the bitrate) required.
The following factors are the most important to consider:
Heavy network utilization due to poor infrastructure affects the bandwidth.
Contact support
If you need more help, go to axis.com/support.