AXIS Q1656-DLE Radar-Video Fusion Camera

A radar-video fusion camera is a visual camera with a fully integrated radar module. As such it can use radar and video – separately or combined – to detect and classify objects.

The benefits of radar-video fusion are more accurate detections and classifications, and less false and missed alarms. The fusion of the two technologies comes together in AXIS Object Analytics, which is the main interface used to access and configure the radar-video fusion.

AXIS Q1656-DLE detects and classifies objects in wide areas with depth, and you can use it for area monitoring or road monitoring. Additionally, AXIS Q1656-DLE works well in a site design combined with other devices. Since the detection range of the radar is larger than the field of view of the camera in AXIS Q1656-DLE, combine it with PTZ cameras with IR illumination to achieve visual confirmation in the entire detection range of the radar. Or combine it with thermal cameras, which can detect and classify objects in long and narrow areas.

Used on their own, video and radar both have their own strengths and limitations:

• The video typically provides more accurate classifications when there is sufficient contrast and when the object is moving close to the camera. It will also provide more granular classifications than the radar. However, a camera needs good lighting conditions to see.

• The radar on the other hand can detect objects even in challenging lighting conditions, and its detection and classification range is longer. Regardless of the weather conditions, the radar can measure the speed of a moving object, as well as its direction and the distance to it. However, the lack of visual confirmation can make the radar classifications more fragile. Swaying objects and reflective surfaces can trigger false alarms and must be taken into consideration when designing the site and configuring the radar.

The two technologies in the radar-video fusion camera can of course be used on their own but are more powerful when the analytics from both technologies interact to provide more reliable detections and classifications.

• This product fuses the radar data with the video data in two ways:

• Visual fusion: The radar detections and classifications are fused into the video image. This is a way to visualize the radar data in the video stream when the video analytics isn’t available.

  For example, if an object appears at a distance of 50 m (164 ft), it may be too small for the video analytics to detect, but the radar can identify it. In that case, the radar detection is fused into the image plane and can be used to trigger alarms inside AXIS Object Analytics.

• Analytics fusion: The radar detections and classifications are fused with the detections and classifications from the video analytics. This gives the device a combined analytics output where the respective strengths of both technologies are merged. It uses the distance and speed from the radar, and the position and class from the video.

  When the object in the example above comes closer, the video analytics also detects it. The radar detection is then fused with the video analytics output to produce an output of higher quality, and with more information, than what the technologies can provide separately.

Preview mode is ideal for installers when fine tuning the camera view during the installation. No login is required to access the camera view in preview mode. It is available only in factory defaulted state for a limited time from powering up the device.

The installation guide and other documents for this product can be found on axis.com/products/axis-q1656-dle/support#support-resources

To get the best video and radar coverage, the product must be appropriately mounted. Consider the following when you mount a radar-video fusion camera:

Area or road monitoring

This product is intended for monitoring open areas and you can use it either for area monitoring or road monitoring. For installation examples and use cases, see Area installation and Road installation.

Avoid solid and reflective objects

Solid and metal objects can affect the performance of the radar in AXIS Q1656-DLE. Most solid objects (such as walls, fences, trees, or large bushes) in the coverage area will create a blind spot (radar shadow) behind them. 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 in the coverage area of the radar, see Add exclude zones.

Mounting position

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 in AXIS Q1656-DLE.

If you install the product on a wall, it needs to point away from the wall at least 15°.

Additionally, the mounting height affects the detection distance and range of both the video and the radar.

Tilt angle

The product must be sufficiently oriented towards the ground so that the center of the image is below the horizon. The recommended mounting tilt is 15–45°.

You can add an overlay in the radar’s live view that shows the tilt angle of the product. For instructions, see Show a text overlay with the tilt angle of the radar.

Roll angle

The product's roll angle must be nearly equal to zero, which means that the image should be level with the horizon.

Coexistence

If you mount more than eight radars or radar-video fusion cameras operating on the 60 GHz frequency band close together, they may interfere with each other. To avoid interference, see Install multiple Axis radar devices.

Coexistence

The radio waves of the radar in AXIS Q1656-DLE continue beyond the detection area, and can interfere with other radars up to 350 m (380 yd) away. This is called a coexistence zone.

AXIS Q1656-DLE operates on the 60 GHz frequency band. You can install up to eight Axis radars or radar-video fusion cameras 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 radar devices 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.

You can combine the radar-video fusion camera with Axis radars operating on another frequency band without having to think about coexistence. Axis radar devices that are operating on different frequency bands will not interfere with each other.

The radar in AXIS Q1656-DLE has a horizontal field of detection of 95°. The detection range of the radar depends on factors like the scene, the mounting height and tilt angle of the product, and the size and speed of the moving objects.

The detection range also depends on the monitoring profile you select. You can use AXIS Q1656-DLE for area or road monitoring and there are two profiles in the radar that are optimized for each one of the scenarios:

• Area monitoring profile: the radar tracks and classifies humans, vehicles and unknown objects moving at speeds lower than 55 km/h (34 mph). For information about detection range, see Area detection range.

• Road monitoring profile: the radar mainly tracks and classifies vehicles moving at speeds up to 200 km/h (125 mph). For information about detection range, see Road detection range.

• Note

  When the radar and video is combined in AXIS Object Analytics, AXIS Q1656-DLE can classify vehicle subclasses (buses, cars, bikes, trucks, and other).

Select the area or monitoring profile in the product’s web interface. For instructions, see Select a radar profile.

The radar in this device has a horizontal field of detection of 95°. The area of coverage corresponds to 2700 m² (29000 ft²) for humans and 6100 m² (65600 ft²) for vehicles.

The detection range is the distance within which an object can be tracked and can trigger an alarm. It’s 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.25 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

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.

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-video fusion camera and the vehicle speed will impact the detection range of the radar. 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).

The analytics fusion zone, which is the zone in where an object can be detected and classified by both technologies, depends on factors like:

• The installation height of the camera.

• The tilt angle of the camera.

• The zoom level of the camera lens.

• The lighting conditions of the surrounding environment, and of the light provided by the camera itself and other devices in the site.

• The distance to the moving object.

Once the radar-video fusion camera has been installed, the radar coverage is fixed. The field of view of the camera, however, depends on the zoom level of the lens.

To visualize the camera’s field of view in relation to the radar coverage, there are two green lines in the radar stream that represent the approximate field of view of the camera. The lines will adjust when the camera zooms in or out. Additionally, there are two dotted lines that represent the approximate area in which the camera can see. The dotted line closer to the device represent the near detection limit, while the one farther away represents the far detection limit.

The size of the analytics fusion zone is affected by the zoom level of the lens in AXIS Q1656-DLE. The two extremes of the zoom level are described below.

Lens zoomed out (max wide)

When the lens in AXIS Q1656-DLE is zoomed out maximally, objects can get too small to detect for the video analytics. In this scenario, it's likely that objects will be detected by the radar with its wide coverage, but not by the video analytics. If you want to establish visual confirmation in the entire detection range of the radar, you can pair AXIS Q1656-DLE with one or more PTZ cameras.

Lens zoomed in (max tele)

When the lens is zoomed in maximally, it will limit the camera’s field of view significantly. However, since objects far away are magnified compared to when the lens is zoomed out maximally, it means the objects can be detected by the video analytics at a much larger distance from the device. In this scenario, it’s possible that objects will be detected by the video analytics but not by the radar analytics.

To maximize the chance of accurately classifying an object by both the radar and the video analytics, adjust the zoom – if possible – so that objects in the area of interest are large enough for the video analytics to detect them.

Since AXIS Q1656-DLE can detect and classify objects using radar and video — or just one of the technologies — there are several things to be aware of.

• If two people are walking close together and are detected by the radar, but not the video analytics, they will be classified as one person and only one bounding box will surround them. When they enter the analytics fusion zone and visual confirmation is achieved, they will be accurately classified. The spatial differentiation of the radar in AXIS Q1656-DLE is 3 m(9 ft).

• If an object is outside the camera's field of view, AXIS Q1656-DLE can't fuse any detections or classifications into the image plane. This means that AXIS Object Analytics can't trigger an alarm. To trigger an alarm when an object is detected by the radar only, configure a scenario in the radar’s web interface and use conditions to trigger on motion within the radar scenario.

• The exclude zones you add in the radar’s web interface are global, which means that any motion detected in these zones will always be ignored – even if the exclude zone overlaps with the analytics fusion zone in AXIS Object Analytics. The exclude zones you add in AXIS Object Analytics, however, will only ignore motion in AXIS Object Analytics scenarios.

To get the best radar performance in area installations, select the area monitoring profile in AXIS Q1656-DLE. For more information, see Select a radar profile.

You can place multiple radar-video fusion cameras side-by-side to create a virtual fence, for example along or around a building.

For 180° radar coverage, place two AXIS Q1656-DLE next to each other. When you install more than one pair of radar-video fusion cameras side-by-side, we recommend placing them with 100 m (330 ft) spacing between each pair, as shown in the example.

You can install up to eight radar-video fusion cameras close together without interference between the radars. For more information about placing Axis radar devices close together, see Install multiple Axis radar devices.

Cover an open field around a building

A company in an office building needs to secure the premises from intrusion and vandalism, particularly after working hours, on weekends and on public holidays. To cover the area around the building, they install a combination of radar-video fusion cameras and PTZ cameras. They configure the radar-video fusion cameras to trigger an alarm when humans and vehicles approach the building. To get as reliable detections and classifications as possible, they select a detection sensitivity in AXIS Object Analytics suitable for the area. For more information about detection sensitivity, see Select detection sensitivity.

To make sure they get visual confirmation of potential intruders in the entire detection range of the radar, they add two PTZ cameras with built-in IR on the opposite corners of the building. The radars steer the PTZ cameras through AXIS Radar Autotracking for PTZ, and the built-in IR also provides more light for the radar-video fusion cameras, which makes it possible to detect and identify intruders on a greater distance.

Cover a fenced building

A warehouse that normally keeps goods on the premises is surrounded by a fence to keep intruders away. To detect potential trespassers, they install a combination of radar-video fusion cameras and PTZ cameras with built-in IR to secure the premises. The radar-video fusion cameras provide reliable detections and trigger alarms, while the PTZ cameras extend the visual coverage. The PTZ cameras’ built-in IR also provides more light for the radar-video fusion cameras, which makes it possible to detect and identify intruders on a greater distance.

In this scene, the area outside the fence is not covered since it’s a busy area that can trigger false alarms. In scenes with less activity, the area outside the fence could be covered as well. In such a scene, it would be possible to configure the cameras to trigger external lights when movement is detected outside the fence to deter potential intruders. They could also trigger an alarm when intruders are actually detected inside the fence. To be able to detect movement outside the fence, the cameras need to be mounted high enough.

Cover a critical asset

A telecom shelter that contains critical equipment and cabling is surrounded by a fence to keep intruders away. To avoid tampering and sabotage, they need additional protection. Since it’s important to keep false alarms to a minimum, they install two radar-video fusion cameras in the opposite corners of the site. The cameras can together cover the shelter, the antennas and the grounds. With the use of both the radar and video technology in the radar-video fusion cameras, the cameras can provide reliable detections and classifications of potential trespassers.

It’s possible to place radar-video fusion cameras facing each other in this way without interference between the radars. However, to make sure the video technology can provide accurate detections and classifications, good lighting conditions are required.

Cover the area around a loading bay

The loading bay of a commercial building is surrounded by a fence to protect the premises. For additional security, the company installs a thermal camera and three radar-video fusion cameras on the site. To detect potential trespassers, they install a thermal camera along the fence. To detect intruders that have managed to pass the fence, they install two of the radar-video fusion cameras on a pole facing the loading docks. These cameras will be able to detect and classify humans and vehicles moving around the docks and can trigger an alarm after working hours. To detect any intruders coming through the area with the turning point on the right side, they install an additional radar-video fusion camera facing the area. Finally, the thermal camera can also help to detect tampering attempts of the two cameras installed close to the fence.

To get the best radar performance in road installations, select the road monitoring profile in AXIS Q1656-DLE. For more information, see Select a radar profile.

When monitoring roads and highways, make sure to mount the radar-video fusion camera at a sufficient height to avoid blind spots (radar shadow) behind the vehicles.

Side mounted

To monitor vehicles travelling along a road you can mount the radar-video fusion camera 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 make it possible for the radar in AXIS Q1656-DLE to measure high speeds accurately, position the radar-video fusion camera within a lateral distance of 10 m (32 ft) from the vehicles. For more information about detection range and velocity accuracy, see Road detection range.

Center mounted

To monitor vehicles on a multi-lane road, you can mount one or more radar-video fusion cameras 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-video fusion camera, instead of driving towards it.

You can also place the radar-video fusion camera on a gantry overlooking a pedestrian crossing with traffic lights, for example to log the speeds of departing vehicles, or detect speed violations.

To make it possible for the radar in AXIS Q1656-DLE to measure high speeds accurately, position the radar-video fusion camera within a lateral distance of 10 m (32 ft) from the vehicles. For more information about detection range and velocity accuracy, see Road detection range.

Wrong-way detection on a highway ramp

To detect and identify vehicles driving in the wrong direction on a highway ramp, traffic control mounts AXIS Q1656-DLE on a pole facing the ramp. For reliable detections, they set up a line crossing scenario in the radar pages of the device’s web interface and configure it so that vehicles must cross two lines to trigger an alarm. In the radar scenario, they position the two lines on the ramp as seen in the illustration and specify the driving direction and speeds to trigger on. With this configuration, the radar will trigger the alarm, and the camera can provide visual identification of the vehicle on the ramp. For information about how to set up a radar scenario, see Add scenarios.

Monitor traffic flow at an intersection – queue build-up

To monitor how and when queues build up in a busy intersection, traffic control installs AXIS Q1656-DLE on a gantry above the intersection. They set up an object in area scenario in AXIS Object Analytics that will trigger on vehicles moving in an area. They shape the scenario to only cover the part of the road leading up to the intersection and select a detection sensitivity that suits the scene. 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). For information about how to configure an AXIS Object Analytics scenario and select a suitable detection sensitivity, see Configure AXIS Object Analytics.

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 AXIS Q1656-DLE on a gantry above the road leading up to the intersection. They set up a line crossing scenario in the radar pages of the device’s web interface where vehicles must cross two lines to trigger an alarm. When they configure the radar scenario, they place the first of the two lines over the lanes leading up to the intersection, just 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 radar scenario from 2 to 0 seconds.

To monitor the traffic flow in all directions, they create one radar scenario for each direction. For information about how to set up a radar scenario, see Add scenarios.

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.

You can use the device with the following browsers:

✓: Recommended
*: Supported with limitations

1. Open a browser and type the IP address or host name of the Axis device.

   If you don’t know the IP address, use AXIS IP Utility or AXIS Device Manager to find the device on the network.

2. 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 features and settings in the web interface of devices with AXIS OS, see AXIS OS web interface help.

The first time you log in to your device, you must create an administrator account.

1. Enter a username.

2. Enter a password. See Secure passwords.

3. Re-enter the password.

4. Accept the license agreement.

5. Click Add account.

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.

1. To make sure that the device has its original AXIS OS, or to take full control of the device after a security attack:

2. Reset to factory default settings. See Reset to factory default settings.

   After the reset, secure boot guarantees the state of the device.

3. Configure and install the device.

This video gives you an overview of the device’s web interface.

Set the power line frequency

1. Go to Video > Installation > Power line frequency.

2. Select a power line frequency and click Save and restart.

Set the capture mode

1. Go to Video > Installation > Capture mode.

2. Click Change.

3. Select a capture mode and click Save and restart.

   See also Capture modes.

This section includes instructions about configuring your device. If you want to learn more about how certain features work, go to Learn more.

To improve image quality for specific surveillance scenes, use exposure modes. Exposure modes lets you control aperture, shutter speed, and gain. Go to Video > Image > Exposure and select between the following exposure modes:

• For most use cases, select Automatic exposure.

• For environments with certain artificial lighting, for example fluorescent lighting, select Flicker-free.

  Select the same frequency as the power line frequency.

• For environments with certain artificial light and bright light, for example outdoors with fluorescent lighting at night and sun during daytime, select Flicker-reduced.

  Select the same frequency as the power line frequency.

• To lock the current exposure settings, select Hold current.

Depending on the installation environment and the conditions around the camera, for example external light sources in the scene, you can sometimes improve the image quality if you manually adjust the intensity of the LEDs. If you have problems with reflections from the LEDs, you can try to reduce the intensity.

1. Go to Video > Image > Day-night mode.

2. Turn on Allow illumination.

3. Click in the live view and select Manual.

4. Adjust the intensity.

Your camera uses visible light to deliver color images during the day. But as the visible light diminishes, color images become less bright and clear. If you switch to night mode when this happens, the camera uses both visible and near-infrared light to deliver bright and detailed black-and-white images instead. You can set the camera to switch to night mode automatically.

1. Go to Video > Image > Day-night mode, and make sure that the IR-cut filter is set to Auto.

2. To use the built-in IR light when the camera is in night mode, turn on Allow illumination and Synchronize illumination.

To reduce noise in low-light conditions, you can adjust one or more of the following settings:

• Adjust the trade-off between noise and motion blur. Go to Video > Image > Exposure and move the Blur-noise trade-off slider toward Low noise.

• Set the exposure mode to automatic.

• Note

  A high max shutter value can result in motion blur.

• To slow down the shutter speed, set max shutter to the highest possible value.

• Note

  When you reduce the max gain, the image can become darker.

• Set the max gain to a lower value.

• If there is an Aperture slider, move it towards Open.

• Reduce sharpness in the image, under Video > Image > Appearance.

• To reduce motion blur in low-light conditions, adjust one or more of the following settings in Video > Image > Exposure:
• Note

  When you increase the gain, image noise also increases.

• Set Max shutter to a shorter time, and Max gain to a higher value.

• If you still have problems with motion blur:

• Increase the light level in the scene.

• Mount the camera so that objects move toward it or away from it rather than sideways.

• Make sure to select the capture mode that has the highest resolution.

• Go to Video > Stream > General and set the compression as low as possible.

• Below the live view image, click and in Video format, select MJPEG.

• Go to Video > Stream > Zipstream and select Off.

Dynamic range is the difference in light levels in an image. In some cases the difference between the darkest and the brightest areas can be significant. The result is often an image where either the dark or the bright areas are visible. Wide dynamic range (WDR) makes both dark and bright areas of the image visible.

1. Go to Video > Image > Wide dynamic range.

2. Turn on WDR.

3. Use the Local contrast slider to adjust the amount of WDR.

4. If you still have problems, go to Exposure and adjust the Exposure zone to cover the area of interest.

Find out more about WDR and how to use it at axis.com/web-articles/wdr.

Image stabilization is suitable in environments where the product is mounted in an exposed location where vibrations can occur, for example, due to wind or passing traffic.

The feature makes the image smoother, steadier, and less blurry. It also reduces the file size of the compressed image and lowers the bitrate of the video stream.

1. Go to Video > Installation > Image correction.

2. Turn on Image stabilization.

You can create one or several privacy masks to hide parts of the image.

1. Go to Video > Privacy masks.

2. Click .

3. Click the new mask and type a name.

4. Adjust the size and placement of the privacy mask according to your needs.

5. To change the color for all privacy masks, click Privacy masks and select a color.

See also Privacy masks

You can add an image as an overlay in the video stream.

1. Go to Video > Overlays.

2. Click Manage images.

3. Upload or drag and drop an image.

4. Click Upload.

5. Select Image from the drop-down list and click .

6. Select the image and a position. You can also drag the overlay image in the live view to change the position.

Use onscreen controls to see both the live view of the video and the radar in the same stream.

1. Go to Video > Image.

2. Click in the live view to access the product’s onscreen controls.

3. Select Predefined controls.

4. Turn on Radar picture-in-picture.

5. Click Enable picture-in-picture.

6. To change the size of the radar projection, click Resize picture-in-picture.

7. To change the position of the radar projection, click Move picture-in-picture.

1. Go to Apps.

2. Select axis-orientationaid.

3. Click Open.

4. To add a street name, click Add text and modify the text to fit the street.

5. To add a compass, click Add compass and modify the compass to fit the image.

1. Record video directly from the camera

2. Go to Video > Stream.

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

4. To stop recording, click again.

1. Watch video

2. Go to Recordings.

3. Click for your recording in the list.

This section includes instructions about configuring your device. To learn more about how streaming and storage works, go to Streaming and storage.

1. Go to Video > Stream.

2. Click in the live view.

3. Select Video format AV1 if your device supports it. Otherwise select H.264.

4. Go to Video > Stream > General and increase Compression.

5. Go to Video > Stream > Zipstream and do one or more of the following:

6. • Note

     The Zipstream settings are used for all video encodings except MJPEG.

   • Select the Zipstream Strength that you want to use.

   • Turn on Optimize for storage. This can only be used if the video management software supports B-frames.

   • Turn on Dynamic FPS.

   • Turn on Dynamic GOP and set a high Upper limit GOP length value.

1. To store recordings on the network, you need to set up your network storage.

2. Go to System > Storage.

3. Click Add network storage under Network storage.

4. Type the IP address of the host server.

5. Type the name of the shared location on the host server under Network share.

6. Type the username and password.

7. Select the SMB version or leave it on Auto.

8. Select Add share without testing if you experience temporary connection issues, or if the share is not yet configured.

9. Click Add.

The radar in this radar-video fusion camera has two profiles; one that is optimized for area monitoring, and one that is optimized for road monitoring. Select the profile that suits your type of installation.

1. In the web interface:

2. Go to Radar > Settings > Detection.

3. Select a profile under Radar profiles.

Set the mounting height of the device in the radar's 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 device as accurately as possible. For scenes with uneven surfaces, set the value that represents the average height in the scene.

1. Go to Radar > Settings > General.

2. Set the height under Mounting height.

You can also set the mounting height in AXIS Object Analytics. Setting the height in one place will automatically populate the mounting height in the other.

1. Go to Apps > AXIS Object Analytics.

2. Turn on the application and click Open.

3. Click Settings.

4. Set the height under Mounting height.

To validate that you have measured and set the correct mounting height of the device, add an augmented overlay in the camera’s live view. The overlay consists of white bounding boxes projected around moving objects.

1. Go to Video > Image.

2. Click in the live view to access the device’s onscreen controls.

3. Expand Predefined controls.

4. Turn on Augmented overlay (radar).

5. Click Toggle augmented bounding boxes.

6. Ask someone to move in the scene you’re monitoring and check in the camera’s live view that the bounding boxes are projected around the moving objects, and not above, below, or next to them.

7. If necessary, re-measure the mounting height, adjust the settings, and check again.

8. Turn off the augmented overlay when you’re done with the validation.

To make it easier to see where detected objects are moving, you can upload a map for reference. You can use a ground plan or an aerial photo that shows the area covered by the radar. Calibrate the map so the radar view 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 scene.

You can either use a setup assistant that takes you through the map calibration step by step, or edit each setting individually.

1. Use the setup assistant:

2. Go to Radar > Map calibration.

3. Click Setup assistant and follow the instructions.

4. To remove the uploaded map and the settings you have added, click Reset calibration.

1. Edit each setting individually:
2. The map will calibrate gradually after you adjust each setting.

3. Go to Radar > Map calibration > Map.

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

5. Under Rotate map, use the slider to rotate the map into position.

6. Go to Scale and distance on a map and click on two pre-determined points on the map.

7. Under Distance, add the actual distance between the two points you have added to the map.

8. Go to Pan and zoom map and use the buttons to pan the map image, or zoom in and out on the map image.

9. Note

   The zoom function doesn’t 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.

10. Go to Radar position and use the buttons to move or rotate the position of the radar on the map.

11. To remove the uploaded map and the settings you have added, click Reset calibration.

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.

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.

1. Add a scenario:

2. Go to Radar > Scenarios.

3. Click Add scenario.

4. Type the name of the scenario.

5. Select if you want to trigger on objects moving in an area or on objects crossing one, or two, lines.

1. Trigger on objects moving in an area:

2. Select Movement in area.

3. Click Next.

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

5. Click Next.

6. Add detection settings.

7. 1. Add seconds until trigger after under Ignore short-lived objects.

   2. Select which object type to trigger on under Trigger on object type.

   3. Add a range for the speed limit under Speed limit.

8. Click Next.

9. Set the minimum duration of the alarm under Minimum trigger duration.

10. Click Save.

1. Trigger on objects crossing a line:

2. Select Line crossing.

3. Click Next.

4. Position the line in the scene.

   Use the mouse to move and shape the line.

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

6. Click Next.

7. Add detection settings.

8. 1. Add seconds until trigger after under Ignore short-lived objects.

   2. Select which object type to trigger on under Trigger on object type.

   3. Add a range for the speed limit under Speed limit.

9. Click Next.

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

11. Click Save.

1. Trigger on objects crossing two lines:

2. Select Line crossing.

3. Click Next.

4. To make the object cross two lines for the alarm to trigger, turn on Require crossing of two lines.

5. Position the lines in the scene.

   Use the mouse to move and shape the line.

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

7. Click Next.

8. Add detection settings.

9. 1. Set the time limit between crossing the first and the second line under Max time between crossings.

   2. Select which object type to trigger on under Trigger on object type.

   3. Add a range for the speed limit under Speed limit.

10. Click Next.

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

12. Click Save.

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.

1. Add an exclude zone:

2. Go to Radar > Exclude zones.

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

Autocalibration of the radar-video fusion camera improves the accuracy of the bounding boxes that appear around detected objects in AXIS Object Analytics. With autocalibration, the device uses information from the video, like height and angular accuracy, to improve the positioning of the bounding boxes based on the radar detections.

1. For elevation calibration:

2. Go to Radar > Autocalibration > Elevation.

3. Turn on Autocalibration.

   The autocalibration occurs as soon as calibration data is available.

4. Select a Smoothing option.

5. • If your scene contains little variation in elevation, leave Smoothing set to High.

   • If your scene is hilly or sloped, or if it contains stairs or high buildings, set Smoothing to Low to keep the differences in elevation.

6. Visualize the result of the calibration in the web interface with the following options:

7. • Show elevation pattern shows the vertical distance from the ground up to the camera in a pattern of colored dots.

   • Show color legend shows a legend containing the colors of the elevation pattern and the vertical distance that each color represent.

   • Show reference area shows the area which the calibration is based on.

1. For azimuth calibration:

2. Go to Radar > Autocalibration > Azimuth.

3. Turn on Autocalibration.

   The autocalibration occurs as soon as calibration data is available.

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.

1. Go to Radar > Overlays.

2. Select Text and click .

3. Type #op.

   You can also click Modifier and select #op from the list.

4. Select a position. You can also drag the overlay field in the live view to change the position.

AXIS Object Analytics is an AI-based application that detects and classifies moving objects. It’s also the main interface for configuring the radar-video fusion in AXIS Q1656-DLE. The real-time output of the fusion can only be seen in the video stream inside a scenario configured in the application.

Use scenarios in AXIS Object Analytics to define the detection settings and triggering conditions for your radar-video fusion camera.

1. In the device’s web interface, go to Apps > AXIS Object Analytics.

2. Start the application and click Open.

3. In the welcome screen, click Step-by-step and follow the recommended setup procedure.

4. In Considerations, read through the information and click Finish.

5. Click + New scenario.

6. Note

   By default, the scenarios Object in area and Line crossing use both video and radar input. The other scenarios in AXIS Object Analytics use video input only.

7. Select a scenario based on your requirements.

8. Select the type of object you want the application to detect.

9. Configure your scenario.

10. Verify your settings and click Finish.

11. Note

    To get bounding boxes around the moving objects, go to Settings and turn on Metadata overlay. When you create two scenarios, where one scenario uses both video and radar input and the other only uses video input, there will be double bounding boxes around the moving object. This behavior is expected.

You have now created a scenario in AXIS Object Analytics. To modify the scenario and apply additional settings, click Open. For scenarios that use both radar and video input, you can use speed to trigger and select a detection sensitivity. For instructions, see:

• Use speed to trigger

• Select detection sensitivity.

To learn more about AXIS Object Analytics and its general settings, see AXIS Object Analytics user manual.

If you have created an Object in area or Line crossing scenario in AXIS Object Analytics, you can trigger on objects moving within a set speed range, or above and below it.

1. Go to Apps > AXIS Object Analytics.

2. Start the application and click Open.

3. Select the scenario you want to modify and click Open.

4. Go to Object speed and turn on Use speed to trigger.

5. Set the speed range to trigger on.

6. If you want to trigger on speeds above and below your set range, click Invert.

With the option to select detection sensitivity, you can decide if you want to trigger on detections made by either the video or the radar, or detections made by both. You can also let the device itself, based on the fusion algorithms, decide if it should rely on one of the technologies, or both.

This option is available in Object in area and Line crossing scenarios.

1. Go to Apps > AXIS Object Analytics.

2. Start the application and click Open.

3. Select the scenario you want to modify and click Open.

4. Go to Detection sensitivity and select one of the following options:

5. • Low sensitivity: Requires both the radar and the camera to detect the object. This reduces the risk of false alarms, but increases the risk of missed detections.

     To make sure that objects can be detected by both technologies, the scene can't be too complex. The light conditions need to be good, the detection area needs to be within the detection range of both technologies, and there should preferably not be any disturbing elements, such as trees or bushes.

   • Automatic: Lets the application decide if both the radar and the camera, or only one of them, is required to detect the object. This is the default option.

   • High sensitivity: Requires either the radar or the camera to detect the object. This increases the risk of false alarms, but reduces the risk of missed detections.

     The lighting conditions and the size of the detection area are less important when you select high sensitivity since you only need one of the technologies to detect the object.

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 AXIS Object Analytics:

  Go to Apps > AXIS Object Analytics, open a scenario, and select a lower Detection sensitivity.

• • Low sensitivity: Requires both the radar and the camera to detect the object. Reduced risk of false alarms, but increased risk of missed detections.

  • Automatic: Lets the application decide if both radar and camera or only one of them is required to detect the object.

  • High sensitivity: Requires either the radar or the camera to detect the object. Increased risk of false alarms but reduced risk of missed detections.

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

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

• Note

  The object type setting only affects the radar. It will be ignored by AXIS Object Analytics.

To learn more, see Get started with rules for events.

This example explains how to turn on power saving mode when no motion is detected in the scene.

1. Make sure that AXIS Object Analytics is running:

2. Go to Apps > AXIS Object Analytics.

3. Start the application if it is not already running.

4. Make sure you have set up the application according to your needs.

1. Create a rule:

2. Go to System > Events and add a rule.

3. Type a name for the rule.

4. In the list of conditions, under Application, select Object Analytics.

5. Select Invert this condition.

6. In the list of actions, under Power saving mode, select Use power saving mode while the rule is active.

7. Click Save.

This example explains how to set up an email notification when the housing or casing of the device is opened.

1. Add an email recipient:

2. Go to System > Events > Recipients and click Add recipient.

3. Type a name for the recipient.

4. Select Email as the notification type.

5. Type the recipient’s email address.

6. Type the email address that you want the camera to send notifications from.

7. Provide the login details for the sending email account, along with the SMTP hostname and port number.

8. To test your email setup, click Test.

9. Click Save.

10. Create a rule:

11. Go to System > Events > Rules and click Add a rule.

12. Type a name for the rule.

13. In the list of conditions, select Casing open.

14. In the list of actions, select Send notification to email.

15. Select a recipient from the list.

16. Type a subject line and message for the email.

17. Click Save.

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.

1. Add an email recipient:

2. Go to System > Events > Recipients and add a recipient.

3. Type a name for the recipient.

4. Under Type, select Email.

5. Type an email address to send the email to.

6. Fill in the rest of the information according to your email provider.

   The radar device doesn’t have its own email server, so it needs to log into an email server to send emails.

7. To send a test email, click Test.

8. Click Save.

9. Create a rule:

10. Go to System > Events and add a rule.

11. Type a name for the rule, for example Tampering mail.

12. From the list of conditions, under Device status, select Radar data failure.

13. Under Reason, select Tampering.

14. In the list of actions, under Notifications, select Send notification to email.

15. Select the recipient you created.

16. Type a subject and a message for the email.

17. Click Save.

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.

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.

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.

1. Pair the radar with the PTZ camera:

2. Go to System > Edge-to-edge > PTZ pairing.

3. Enter the IP address, username and password for the PTZ camera.

4. Click Connect.

5. Click Configure Radar autotracking or go to Radar > Radar PTZ autotracking to set up radar autotracking.

6. Calibrate the radar and the PTZ camera:

7. Go to Radar > Radar PTZ autotracking.

8. To set the mounting height of the camera, go to Camera mounting height.

9. To pan the PTZ camera so that it points in the same direction as the radar, go to Pan alignment.

10. If you need to adjust the tilt to compensate for a sloping ground, go to Ground incline offset and add an offset in degrees.

11. Set up the PTZ tracking:

12. Go to Track to select if you want to track humans, vehicles and/or unknown objects.

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

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

15. To determine how many seconds to track each object, set Object hold time.

16. To make the PTZ camera return to its home position when the radar no longer tracks any objects, turn on Return to home.

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

18. To fine tune the zoom of the PTZ camera, adjust the zoom on the slider.

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 the radar-video fusion camera 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-video fusion camera, or install it in a camera that you connect to the radar in the radar-video fusion camera.

  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.

1. Set up the MQTT client in the web interface of the device where you have installed AXIS Speed Monitor:

2. Go to System > MQTT > MQTT client > Broker and enter the following information:

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

4. Click Save and Connect.

5. Create a condition that publishes the radar data as a payload to the MQTT broker:

6. Go to System > MQTT > MQTT publication and click + Add condition.

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

This example explains how to set up the camera to start recording to the SD card when the camera detects an object. The recording will include five seconds before detection and one minute after detection ends.

Before you start:

• Make sure you have an SD card installed.

1. Make sure that AXIS Object Analytics is running:

2. Go to Apps > AXIS Object Analytics.

3. Start the application if it is not already running.

4. Make sure you have set up the application according to your needs.

1. Create a rule:

2. Go to System > Events and add a rule.

3. Type a name for the rule.

4. In the list of conditions, under Application, select Object Analytics.

5. In the list of actions, under Recordings, select Record video while the rule is active.

6. In the list of storage options, select SD_DISK.

7. Select a camera and a stream profile.

8. Set the prebuffer time to 5 seconds.

9. Set the postbuffer time to 1 minute.

10. Click Save.

You have the option to connect the AXIS I/O Indication LED to your network camera. This LED can be configured to turn on whenever certain events occur in the camera. For example, to let people know that video recording is in progress.

Required hardware

• AXIS I/O Indication LED

• An Axis network video camera

• Note

  For instructions on how to connect the AXIS I/O Indication LED, see the installation guide provided with the product.

The following example shows how to configure a rule that turns on the AXIS I/O Indication LED to indicate that camera is recording.

1. Go to System > Accessories > I/O ports.

2. For the port that you connected the AXIS I/O Indication LED to, click to set the direction to Output, and click to set the normal state to Circuit open.

3. Go to System > Events.

4. Create a new rule.

5. Select the Condition that must be met to trigger the camera to start recording. It can, for example, be a time schedule or motion detection.

6. In the list of actions, select Record video. Select a storage space. Select a stream profile or create a new. Also set the Prebuffer and Postbuffer as required.

7. Save the rule.

8. Create a second rule and select the same Condition as in the first rule.

9. In the list of actions, select Toggle I/O while the rule is active, and then select the port the AXIS I/O Indication LED is connected to. Set the state to Active.

10. Save the rule.

• Other scenarios where AXIS I/O Indication LED can be used are for example:

• Configure the LED to turn on when the camera starts, to indicate the presence of the camera. Select System ready as a condition.

• Configure the LED to turn on when live stream is active to indicate that a person or a program is accessing a stream from the camera. Select Live stream accessed as a condition.

This example explains how to display the text “Motion detected” when the device detects an object.

1. Make sure that AXIS Object Analytics is running:

2. Go to Apps > AXIS Object Analytics.

3. Start the application if it is not already running.

4. Make sure you have set up the application according to your needs.

1. Add the overlay text:

2. Go to Video > Overlays.

3. Under Overlays, select Text and click .

4. Enter #D in the text field.

5. Choose text size and appearance.

6. To position the text overlay, click and select an option.

1. Create a rule:

2. Go to System > Events and add a rule.

3. Type a name for the rule.

4. In the list of conditions, under Application, select Object Analytics.

5. In the list of actions, under Overlay text, select Use overlay text.

6. Select a video channel.

7. In Text, type “Motion detected”.

8. Set the duration.

9. Click Save.

This example explains how to connect a PIR detector (normally closed) to the device, and to start recording video when the detector senses motion.

• Required hardware

• 3-wire cable (ground, power, I/O)

• PIR detector, normally closed

1. Connect the wires to the device’s I/O connector
2. Note

   For information on the I/O connector, see Connectors.

3. Connect the ground wire to pin 1 (GND/-).

4. Connect the power wire to pin 2 (12V DC output).

5. Connect the I/O wire to pin 3 (I/O input).

1. Connect the wires to the PIR detector’s I/O connector

3. Connect the other end of the ground wire to pin 1 (GND/-).

4. Connect the other end of the power wire to pin 2 (DC input/+).

5. Connect the other end of the I/O wire to pin 3 (I/O output).

Configure the I/O port in the device web interface

1. Go to System > Accessories > I/O ports.

2. Click to set the direction to input for port 1.

3. Give the input module a descriptive name, for example “PIR detector”.

4. If you want to trigger an event whenever the PIR detector senses motion, click to set the normal state to circuit closed.

1. Create a rule

2. Go to System > Events and add a rule.

3. Type a name for the rule.

4. In the list of conditions, select PIR detector.

5. In the list of actions, under Recordings, select Record video while the rule is active.

6. In the list of storage options, select SD_DISK.

7. Select a camera and a stream profile.

8. Set the prebuffer time to 5 seconds.

9. Set the postbuffer time to 1 minute.

10. Click Save.

This example explains how to set up the camera to start recording to the SD card five seconds before it detects loud noise and to stop two minutes after.

1. Turn on audio:

2. Set up the stream profile to include audio, see Add audio to your recording.

1. Turn on audio detection:

2. Go to System > Detectors > Audio detection.

3. Adjust the sound level according to your needs.

1. Create a rule:

2. Go to System > Events and add a rule.

3. Type a name for the rule.

4. In the list of conditions, under Audio, select Audio Detection.

5. In the list of actions, under Recordings, select Record video.

6. In the list of storage options, select SD_DISK.

7. Select the stream profile where audio has been turned on.

8. Set the prebuffer time to 5 seconds.

9. Set the postbuffer time to 2 minutes.

10. Click Save.

This example explains how to send an email when the input signal is cut or short-circuited. For more information about the I/O connector, see I/O connector.

1. Go to System > Accessories > I/O ports and turn on Supervised for the relevant port.

1. Add an email recipient:

2. Go to System > Events > Recipients and add a recipient.

3. Type a name for the recipient.

4. Select Email as the notification type.

5. Type the recipient’s email address.

6. Type the email address that you want the camera to send notifications from.

7. Provide the login details for the sending email account, along with the SMTP hostname and port number.

8. To test your email setup, click Test.

9. Click Save.

1. Create a rule:

2. Go to System > Events > Rules and add a rule.

3. Type a name for the rule.

4. In the list of conditions, under I/O, select Supervised input tampering is active.

5. Select the relevant port.

6. In the list of actions, under Notifications, select Send notification to email and then select the recipient from the list.

7. Type a subject line and message for the email.

8. Click Save.

1. Turn on audio:

2. Go to Video > Stream > Audio and include audio.

3. If the device has more than one input source, select the correct one in Source.

4. Go to Audio > Device settings and turn on the correct input source.

5. If you make any changes to the input source, click Apply changes.

6. Edit the stream profile that is used for the recording:

7. Go to System > Stream profiles and select the stream profile.

8. Select Include audio and turn it on.

9. Click Save.

To read about all the features and settings available in the web interface of devices with AXIS OS, go to AXIS OS web interface help.

• This product supports fiber-optic cable installations through a media converter. Fiber-optic cable installations offer a number of benefits such as:

• Long-distance connection

• High speed

• Long lifetime

• Large capacity of data transmission

• Electromagnetic interference immunity

Find out more about fiber-optic cable installations in the white paper “Long distance surveillance - Fiber-optic communication in network video” at axis.com/learning/white-papers.

For information about how to install the media converter see the Installation Guide for this product.

A capture mode is a preset configuration that defines how the camera captures images.

• The capture mode setting can affect the maximum resolution and maximum frame rate available in the device.

• The capture mode with a lower resolution than the maximum can reduce the field of view.

• The capture mode also affects the shutter speed, which in turn affects the light sensitivity. This is because a capture mode with a high maximum frame rate has a reduced light sensitivity, and the other way around.

• With some capture modes you can’t use WDR.

The lower resolution capture mode might be sampled from the original resolution, or it might be cropped out from the original, in which case the field of view could also be affected.

What capture mode to choose depends on the requirements for the frame rate and resolution of the specific surveillance setup. For specifications about available capture modes, see the product’s datasheet at axis.com.

The remote focus and zoom functionality allows you to make focus and zoom adjustments to your camera from a computer. It is a convenient way to ensure that the scene’s focus, viewing angle and resolution are optimized without having to visit the camera’s installation location.

A privacy mask is a user-defined area that covers a part of the monitored area. In the video stream, privacy masks appear either as blocks of solid color or with a mosaic pattern.

You’ll see the privacy mask on all snapshots, recorded video, and live streams.

You can use the VAPIX® application programming interface (API) to hide the privacy masks.

You can create several privacy masks. Each mask can have 3 to 10 anchor points.

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.

The video streaming indicator is another type of overlay. It shows you that the live view video stream is live.

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

The Image tab contains camera settings that affect all video streams from the product. If you change something in this tab, it immediately affects all video streams and recordings.

The Stream tab contains settings for video streams. You get these settings if you request a video stream from the product and don’t specify for example resolution, or frame rate. When you change the settings in the Stream tab, it doesn’t affect ongoing streams, but it will take effect when you start a new stream.

The Stream profiles settings override the settings from the Stream tab. If you request a stream with a specific stream profile, the stream contains the settings of that profile. If you request a stream without specifying a stream profile, or request a stream profile that doesn't exist in the product, the stream contains the settings from the Stream tab.

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.

• 1. Target bitrate
  2. Actual average bitrate
• You can also turn on maximum bitrate and specify a target bitrate within the average bitrate option.
• 1. Target bitrate
  2. Actual average bitrate

With analytics and apps you can get more out of your Axis device. AXIS Camera Application Platform (ACAP) is an open platform that makes it possible for third parties to develop analytics and other apps for Axis devices. Apps can be preinstalled on the device, available for download for free, or for a license fee.

To find the user manuals for Axis analytics and apps, go to help.axis.com.

AXIS Object Analytics is an analytic application that comes preinstalled on the camera. It detects objects that move in the scene and classifies them as, for example, humans or vehicles. You can set up the application to send alarms for different types of objects. To find out more about how the application works, see AXIS Object Analytics user manual.

AXIS Image Health Analytics is an AI-based application that can be used to detect image degradations or tampering attempts. The application analyzes and learns the behavior of the scene to detect blurriness or underexposure in the image, or to detect an obstructed or redirected view. You can set up the application to send events for any of these detections, and trigger actions through the camera’s event system or third-party software.

To find out more about how the application works, see AXIS Image Health Analytics user manual.

Analytics metadata is available for moving objects in the scene. Supported object classes are visualized in the video stream through a bounding box surrounding the object, along with information about the object type and confidence level of the classification. To learn more about how to configure and consume analytics metadata, see AXIS Scene Metadata integration guide.

For product-specific information about cybersecurity, see the product's datasheet at axis.com.

For in-depth information about cybersecurity in AXIS OS, read the AXIS OS Hardening guide.

Signed OS is implemented by the software vendor signing the AXIS OS image with a private key. When the signature is attached to the operating system, the device will validate the software before installing it. If the device detects that the integrity of the software is compromised, the AXIS OS upgrade will be rejected.

Secure boot is a boot process that consists of an unbroken chain of cryptographically validated software, starting in immutable memory (boot ROM). Being based on the use of signed OS, secure boot ensures that a device can boot only with authorized software.

Axis Edge Vault provides a hardware-based cybersecurity platform that safeguards the Axis device. It offers features to guarantee the device’s identity and integrity and to protect your sensitive information from unauthorized access. It builds on a strong foundation of cryptographic computing modules (secure element and TPM) and SoC security (TEE and secure boot), combined with expertise in edge device security.

The TPM (Trusted Platform Module) is a component that provides cryptographic features to protect information from unauthorized access. It is always activated and there are no settings you can change.

Being able to verify the origin of the device is key to establishing trust in the device identity. During production, devices with Axis Edge Vault are assigned a unique, factory-provisioned, and IEEE 802.1AR-compliant Axis device ID certificate. This works like a passport to prove the origin of the device. The device ID is securely and permanently stored in the secure keystore as a certificate signed by Axis root certificate. The device ID can be leveraged by the customer’s IT infrastructure for automated secure device onboarding and secure device identification

Signed video ensures that video evidence can be verified as untampered without proving the chain of custody of the video file. Each camera uses its unique video signing key, which is securely stored in the secure keystore, to add a signature into the video stream. When the video is played, the file player shows whether the video is intact. Signed video makes it possible to trace the video back to the camera origin and verifies that the video has not been tampered with after it left the camera.

To learn more about the cybersecurity features in Axis devices, go to axis.com/learning/white-papers and search for cybersecurity.

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.

• 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 release the button, then wait for the status LED to flash green three times.

Use the intrusion alarm switch to get a notification when someone opens the device’s housing. Create a rule to make the device perform an action when the switch is activated. See Trigger a notification when the enclosure is opened.

RJ45 Ethernet connector with Power over Ethernet Plus (PoE+).

• Audio in – 3.5 mm input for a mono microphone, or a line-in mono signal (left channel is used from a stereo signal).

• Audio in – 3.5 mm input for a digital microphone, an analog mono microphone, or a line-in mono signal (left channel is used from a stereo signal).

• Audio out – 3.5 mm output for audio (line level) that can be connected to a public address (PA) system or an active speaker with a built-in amplifier. A stereo connector must be used for audio out.

Audio input

Audio output

Use the I/O connector with external devices in combination with, for example, motion detection, event triggering, and alarm notifications. In addition to the 0 VDC reference point and power (12 V 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.

6-pin terminal block

Example

1. DC ground
2. DC output 12 V, max 50 mA
3. I/O configured as supervised input
4. I/O configured as output
5. Configurable I/O
6. Configurable I/O

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.

Two 2-pin terminal blocks for RS485/RS422 serial interface.

The serial port can be configured to support:

• Two-wire RS485 half duplex

• Four-wire RS485 full duplex

• Two-wire RS422 simplex

• Four-wire RS422 full duplex point to point communication

To reset the product to the factory default settings:

1. Disconnect power from the product.

2. Press and hold the control button while reconnecting power. See Product overview.

3. Keep the control button pressed for 15–30 seconds until the status LED indicator flashes amber.

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

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

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

Axis offers device software management according to either the active track or the long-term support (LTS) tracks. Being on the active track means continuously getting access to all the latest product features, while the LTS tracks provide a fixed platform with periodic releases focused mainly on bug fixes and security updates.

Using AXIS OS from the active track is recommended if you want to access the newest features, or if you use Axis end-to-end system offerings. The LTS tracks are recommended if you use third-party integrations, which are not continuously validated against the latest active track. With LTS, the products can maintain cybersecurity without introducing any significant functional changes or affecting any existing integrations. For more detailed information about Axis device software strategy, go to axis.com/support/device-software.

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:

1. Go to the device’s web interface > Status.

2. Under Device info, see the AXIS OS version.

1. Download the AXIS OS file to your computer, available free of charge at axis.com/support/device-software.

2. Log in to the device as an administrator.

3. Go to Maintenance > AXIS OS upgrade and click Upgrade.

4. When the upgrade has finished, the product restarts automatically.

Problems upgrading AXIS OS

Problems setting the IP address

Problems accessing the device

Problems with MQTT

Problems with operating the device

If you can’t find what you’re looking for here, try the troubleshooting section at axis.com/support.

The most important factors to consider:

• Heavy network utilization due to poor infrastructure affects the bandwidth.

If you need more help, go to axis.com/support.