Solution overview
- AXIS D2123–VE Radar paired with AXIS Q6358-LE PTZ camera
- AXIS D4200–VE Strobe speaker
- Surveillance center
- AXIS C1310-E horn speaker
- AXIS D2122–VE Radar paired with AXIS Q6358-LE PTZ camera
Installation
Considerations
The radar is intended for monitoring open areas (1). Any solid object such as a wall, fence, tree, or large bush in the scene creates a blind spot, a so-called radar shadow, behind it (2, 3). The mounting height affects the size of the radar shadow.
For more complex scenes, where for example reflective surfaces are present, we recommend radar-video fusion technology with selected PTZ cameras.
The radar works best if the ground is covered by a paved surface such as asphalt. When the ground is covered by gravel or grass, the detection performance can be affected.
If you install the radar on a wall, make sure there are no other objects or installations within one meter (three feet) to the left or right of the radar. Such objects can reflect radio waves which can affect the radar’s performance.
If you install the radar on a pole, make sure the pole is stable. The radar has a stabilization mechanism that you can enable, but it can affect the radar sensitivity or the time it takes to detect a moving object.
A metal object or a reflective surface in the scene can reflect humans or vehicles that move close to it and cause a reflected radar track, or ghost track (4). This can affect the radar’s ability to perform accurate classifications and result in false alarms. You can use exclusion zones to filter out such reflections. You can also minimize the impact of reflections if you pair a camera with the radar.
The recommended mounting height is listed in the device’s datasheet at axis.com.
Monitor the scene
The radar can detect moving objects and classify them as humans, vehicles or unknown. When you monitor an area, use the Area monitoring profile.
Install multiple radars
To monitor areas such as the surroundings of a building or the buffer zone outside a fence, you can install multiple radars near each other. Each radar can coexist with up to eleven other AXIS D2122-VE or AXIS D2123-VE radars within a 500-meter (1640 feet) radius, which forms the coexistence zone. You can also install this radar model in the coexistence zone of previous Axis radar models, as they don’t interfere with each other. For more information about the coexistence zone, see Coexistence zone.
- Coexistence zone
- Detection zone
- Axis D2122–VE Radar
- Coexistence zone
- Detection zone
- Axis D2123–VE Radar
The performance of the radar in the coexistence zone can be affected by the environment and the radar's direction toward fences, buildings, or neighboring radars.
Installation examples
Create a virtual fence with multiple radars
To create a virtual fence, for example along a building, place multiple radars side-by-side. We recommend that you place them with 200 m (656 ft) spacing.
Cover an area around a building
To monitor an area around a building, place radars on the walls of the building facing outwards.
Cover an open area
To monitor a large open area, use two pole mounts to install two AXIS D2122-VE Radars back-to-back.
Each radar can provide up to 60 W PoE output when the radar is powered by a 90 W midspan. PoE out requires Power over Ethernet IEEE 802.3bt, Type 4 Class 8.
Install multiple radars facing each other
To monitor an area for example between buildings, place radars facing each other. There can be up to 12 radars facing each other in the same coexistence zone.
Recognition and detection distances
When the radar is mounted at the optimal installation height:
In the recognition zone, you can detect and classify humans at a maximum distance of 100–140 meters (330–459 feet) from the radar, depending on the human’s position in relation to the radar.
In the detection zone, you can detect vehicles at a maximum distance of 140–200 meters (459–656 feet) from the radar, depending on:
the vehicle’s speed
the vehicle’s direction in relation to the radar
the flatness of the ground
the ground material
For more information about the zones, see Recognition and detection zones.
- Enter the actual mounting height in the device’s web interface when you calibrate the radar.
- The recognition and detection distances are affected by the scene.
- The recognition and detection distances are different for different object types.
- The recognition and detection distances were measured in the following conditions:
The distance was measured on flat, horizontal ground.
The radar was mounted with no tilt.
The object was a 170 cm (5 ft 7 in) tall person.
There was a clear line of sight from the radar to the person.
The radar sensitivity was set to Medium.
The radar can’t detect objects that are closer than the minimum detection distance. The minimum detection distance depends on the radar’s mounting height:
| Mounting height | Minimum detection distance |
4 m | 4 m |
5 m | 6 m |
6 m | 8 m |
7 m | 11 m |
8 m | 13 m |
9 m | 15 m |
10 m | 18 m |
When you pair the radar with a PTZ camera, the camera can continue tracking an object even within the radar’s minimum detection distance.
Use cases
Rooftop area coverage
A large distribution center wants to use radars to cover the rooftop area. The radars are paired with ARTPEC-9 PTZ cameras and mounted back-to-back on poles, covering the whole rooftop. The radar discovers and classifies moving objects on the roof, and directs the camera to the object and lets the camera validate the classification. The camera uses autotracking to continue tracking the object.
Use a mobile surveillance trailer to cover a large open area
The outdoor yard of a hardware store has had several break-ins after-hours. There is one security guard on duty at a time, but there is a need to bolster the security at night without the added cost of hiring more staff. They have decided to install two radars mounted back-to-back on a mobile surveillance trailer to cover the entire yard. The radars are configured to alert the on-duty security guard of suspicious behavior so that the guard can investigate the scene. They also consider installing a strobe speaker that is triggered by the radars to deter intruders.
Cover a fenced building
In the following scenario, a PTZ camera has been mounted with the radar to validate alarms and provide accurate classification thanks to radar-video-fusion technology.
Intruders are walking outside the fence, not triggering an alarm.
Intruders break in through the fence, the radar discovers them and triggers an alarm.
The radar directs the PTZ camera towards the intruders, and lets the camera validate the alarm with video analytics.
For more information, see Autotracking.
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 | EdgeTM | Firefox® | Safari® | |
Windows® | ✓ | ✓ | * | * |
macOS® | ✓ | ✓ | * | * |
Linux® | ✓ | ✓ | * | * |
Other operating systems | * | * | * | * |
✓: Recommended
*: Supported with limitations
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
Use HTTPS (which is enabled by default) to set your password or other sensitive configurations over the network. HTTPS enables secure and encrypted network connections, thereby protecting sensitive data, such as passwords.
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.
Configure your device
To get the most out of your device, we recommend that you go through the following steps:
If you install several radars close to each other: Set the number of neighboring radars
Set the mounting height
Set the radar’s mounting height in the web interface. The correct mounting height is important for the radar to be able to detect and measure the speed of passing objects correctly. It’s also very important for autotracking to work.
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.
Go to Radar > Settings > General.
Set the height under Mounting height.
Set the number of neighboring radars
If you install other radars of the same model in this radar’s coexistence zone, define the number of neighboring radars in the web interface of each radar. This improves the performance of the radars and minimizes the risk of interference.
Go to Radar > Settings > Coexistence.
Select the number of neighboring radars in this radar’s coexistence zone.
Add a map for reference
To make it easier to set up scenarios and to understand where in the scene objects are moving, you can choose to use a map as a background to the radar stream. You can use a ground plan or an aerial photo that shows the area covered by the radar. Adjust and 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 use either 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 calibrates 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 at 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 doesn’t alter the radar’s view. Even if parts of the view aren’t visible after zooming, the radar still detects moving objects in the entire view. The only way to exclude detected movement is to add exclusion zones.
- You can adjust the pan and zoom at any time from the Map calibration, Exclusion zones, or Scenarios pages by clicking .
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.
Create a scenario for detecting objects
With a scenario, you can detect or recognize objects that move in the scene. To trigger actions when the conditions in your scenario are fulfilled, create a rule in Events. You can create several scenarios to detect different behaviors or cover different parts of the scene.
Go to Radar > Scenarios.
Click Add scenario.
Type the name of the scenario.
Select if you want to trigger on objects that move inside an area or on objects that cross a line.
Click Next.
For Movement in area scenarios:
Select the zone shape.
Use the mouse to move and adjust the zone to cover the desired part of the radar view or reference map.
For Line crossing scenarios:
Position the line in the scene.
Use the mouse to move and adjust the line.
To change the detection direction, turn on Change direction.
To require the object to cross two lines to trigger actions, turn on Require crossing of two lines.
Position the second line in the scene.
Click Next.
Add detection settings.
For Movement in area scenarios and Line crossing scenarios with one line, add a delay time to minimize false alarms in Ignore short-lived objects.
For Line crossing scenarios with two lines, 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 under Speed limit.
Click Next.
Set the minimum duration of the alarm under Minimum trigger duration.
For Line crossing scenarios, lower the duration to 0 seconds if you want objects to trigger actions as soon as they cross the line.
Click Save.
Minimize false alarms
If you get many false alarms, you can try to minimize them by changing different settings. For example, you can filter out certain types of movement or objects, adjust the zones where objects trigger alarms, or adjust the detection sensitivity.
Adjust the detection sensitivity of the radar:
Go to Radar > Settings > Detection and lower the Detection sensitivity.
The sensitivity setting affects all zones.
A lower detection sensitivity is suitable when there are many metal objects or large vehicles in the scene. It reduces the risk of false alarms, but also the radar’s capability to classify small objects.
A higher detection sensitivity is suitable for an open scene, like a field, without metal objects.
Modify inclusion and exclusion zones:
Hard surfaces in the scene can cause reflections that result in multiple detections for a single physical object. You can either adjust the shape of the inclusion zone in the scenario, or add a generic exclusion zone to ignore a certain part of the scene.
Trigger on objects crossing two lines instead of one:
If the scene in a line-crossing scenario contains swaying objects or animals, there is a risk that such an object crosses the line and triggers a false alarm. In this case, you can adjust the scenario to trigger only when an object has crossed two lines.
Filter on certain movement:
To minimize false alarms caused by trees, bushes, and flags in the scene, go to Radar > Settings > Detection and turn on Ignore swaying objects.
To minimize false alarms caused by small objects, such as cats and rabbits, in the scene, go to Radar > Settings > Detection and turn on Ignore small objects. This setting is available in the area monitoring profile.
Filter on time:
Go to Radar > Scenarios.
Select a scenario, and click to modify its settings.
Increase Seconds until trigger. This is the delay time from when the radar starts tracking an object until it can trigger an alarm. The timer starts when the radar detects the object, not when the object enters the inclusion 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, clear the object types that should not trigger alarms in the scenario.
Validate your installation
Validate the installation of the radar
Before you start using the radar, we recommend that you validate the installation. The validation can help you identify problems with the installation or manage static objects such as trees or reflective surfaces in the scene.
The installation is validated in the conditions that apply at the time of validation. Changed conditions in the scene can affect the everyday performance of your installation.
Check that there are no false detections
Check that the recognition zone is clear from human activity.
Wait for a few minutes to make sure the radar doesn’t detect any static objects in the recognition zone.
If there are unwanted detections, you can filter out certain types of movement or objects, adjust the zones where objects trigger alarms, or adjust the detection sensitivity. For instructions, see Minimize false alarms.
Check for the correct symbol, direction of travel, and position on map
In the radar’s web interface, start a recording. For instructions, see Record and watch video.
Start walking just outside the recognition zone, and walk directly toward the radar.
Check that a human classification symbol is shown when the person enters the recognition zone.
Check that the radar’s web interface shows the correct direction of travel.
Check that the person’s actual position matches the position on the map.
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. | ||
| 2. Check that the human classification symbol is shown when the person enters the recognition zone. | ||
| 3. Check that the direction of travel is correct. | ||
| 4. Make sure that the person’s actual position matches the position on the map. |
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 according to the instructions.
Make sure you have added and calibrated a reference map.
Set the radar scenario to trigger when a human is detected. By default, Seconds until trigger is set to two seconds but you can change this if needed.
Set the radar to record video when an appropriate object is detected.
For instructions, see Record and watch video.
Go to Radar > Settings > Object visualization and 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, you can disable it.
Walk along the border of the recognition zone and make sure that the trailing on the system matches the route that you walked.
If you are not satisfied with the results of your validation, re-calibrate the reference map and repeat the validation.
Adjust the radar image
This section includes instructions about configuring the radar image. 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.
Click Manage images.
Upload or drag and drop an image.
Click Upload.
Select Image from the drop-down list and click .
Select the image and a position. You can also drag the overlay image 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.
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
To stop recording, click again.
- Watch video
Go to Recordings.
Click for your recording in the list.
Set up rules for events
You can create rules to make your device perform an action when certain events occur. A rule consists of conditions and actions. The conditions can be used to trigger the actions. For example, the device can start a recording or send an email when it detects motion, or show an overlay text while the device is recording.
To learn more, see 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 to 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, you need to restart all the rules that use that stream profile.
Activate a sweeping red light on the radar
You can use the dynamic LED strip on the front of the radar to indicate that the area is monitored.
This example explains how to activate a red sweeping light after working hours on weekdays.
- Create a schedule:
Go to System > Events > Schedules and add a schedule.
Type a name for the schedule, for example
Weekday nights.Under Type, select Schedule.
Under Recurrence, 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, for example
Red sweeping light.In the list of conditions, under Scheduled and recurring, select Schedule.
In the list of schedules, select Weekday nights.
In the list of actions, under Radar, select Dynamic LED strip.
Select the pattern Sweeping red.
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.
- Add an email recipient:
Go to System > Events > Recipients and add a recipient.
Type a name for the recipient.
Under Type, select Email.
Type an email address to send the email to.
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.
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, for example
Tampering mail.From the list of conditions, under Device status, select Radar data failure.
Under Reason, select Tampering.
In 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.
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 information about the device, 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 Time and location 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. |
Power status
Shows power status information, including current power, average power, and max power.
Power settings: View and update the power settings for the device. Takes you to the Power settings page where you can change the power settings. |
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. |
Coexistence
Number of neighboring radars: Select the number of neighboring radars that are mounted within the same coexistence zone. This will help to avoid interference.
|
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. |
Exclusion zones
An exclusion zone is an area in which moving objects are ignored. Use exclusion zones if there are areas inside a scenario that trigger a lot of unwanted alarms. : Click to create a new exclusion zone. To modify an exclusion zone, select it in the list. Track passing objects: Turn on to track objects that pass through the exclusion zone. The passing objects keep their track IDs and are visible throughout the zone. Objects that appear from within the exclusion zone will not be tracked. Zone shape presets: Select the initial shape of the exclusion 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. |
Analytics
Metadata configuration
RTSP metadata producers
View and manage the data channels that stream metadata and the channels they use.
These settings are for the RTSP metadata stream that uses ONVIF XML. Changes made here don't affect the Metadata visualization page.
Producer: A data channel that uses Real-Time Streaming Protocol (RTSP) to send metadata. Channel: The channel used to send metadata from a producer. Turn on to enable the metadata stream. Turn off for compatibility or resource management reasons. |
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. 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 IPv4 automatic IP (DHCP) to let the network assign your IP address, subnet mask, and router automatically, without manual configuration. We recommend using automatic IP assignment (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 -. Enable dynamic DNS updates: Allow your device to automatically update its domain name server records whenever its IP address changes. Register DNS name: Enter a unique domain name that points to your device's IP address. Allowed characters are A–Z, a–z, 0–9 and -. TTL: Time to Live (TTL) sets how long a DNS record stays valid before it needs to be updated. |
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. |
If DHCP is disabled, features that rely on automatic network configuration, such as hostname, DNS servers, NTP, and others, may stop working.
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. |
Network ports
Power and ethernet: Select this option to turn on network for the switch port. Power only: Select this option to turn off network for the switch port. The port still provides power over ethernet. |
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. A step-by-step guide opens up.
The context menu contains:
Secure keystore:
|
Cryptographic policy
The cryptographic policy defines how encryption is used to protect data.
Active: Select which cryptographic policy to apply to the device:
|
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
Firewall: Turn on to activate the firewall.
To make exceptions to the default policy, you can create rules that allows or blocks connections to the device from specific addresses, protocols, and ports. + New rule: Click to create a rule.
LIMIT: Select to accept connections from devices that match the criteria defined in the rule but apply limits to reduce excessive traffic.
Test rules: Click to test the rules that you have defined.
|
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, Open ID, and Client Credential Grant. HTTPS: Select to use HTTPS. The context menu contains:
|
Client Credentials Grant Configuration
Admin claim: Enter a value for the admin role. Verification URI: Enter the web link for the API endpoint authentication. 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. Save: Click to save the values. |
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. |
Your product may have some of the following pre-configured rules: Front-facing LED Activation: LiveStream: When the microphone is turned on and a live stream is received, then the front-facing LED on the audio device will turn green. Front-facing LED Activation: Recording : When the microphone is turned on and a recording is ongoing, then the front-facing LED on the audio device will turn green. Front-facing LED Activation: SIP : When the microphone is turned on and a SIP call is active, then the front-facing LED on the audio device will turn green. You must enable SIP on the audio device before it can trigger this event. Pre-announcement tone: Play tone on incoming call: When a SIP call is made to the audio device, then the device plays a pre-defined audio clip. You must enable SIP for the audio device. For the SIP caller to hear a ring tone while the audio device plays the audio clip, you must configure the SIP account for the device to not answer the call automatically. Pre-announcement tone: Answer call after incoming call-tone: When the audio clip has ended, the incoming SIP-call is answered. You must enable SIP for the audio device. Loud ringer : When a SIP call is made to the audio device, a pre-defined audio clip is played as long as the rule is active. You must enable SIP for the audio device. |
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 Knowledge base. |
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 condition: Select to include the topic that describes the condition in the MQTT topic. Include 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
Network storage: Turn on to use 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. |
Onboard storage
Unmount: Click before you disconnect the device from the system. This will stop all ongoing recordings. Write protect: Turn on to protect the storage device from being overwritten. Autoformat: The disk will automatically format using the ext4 file system. |
Onboard storage
Hard drive status: Click to view the hard drive status, capacity, and serial number. Write protect: Turn on write protection to protect the storage device from being overwritten. |
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. Privileges:
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. |
Power settings
Power status
Shows power status information. Information varies depending on the product. |
Power settings
Delayed shutdown: Turn on if you want to set a delay time before the power turns off. Delay time: Set a delay time between 1 and 60 minutes. Power saving mode: Turn on to put the device into power saving mode. When you turn on power saving mode, the IR illumination range reduces. Set power configuration: Change the power configuration by selecting a different PoE class option. Click Save and restart to save the change. Note If you set the power configuration to PoE class 3, we recommend you select Low power profile if your device has that option. Dynamic power mode: Turn on to reduce power consumption when the device is inactive. Power warning overlay: Turn on to show a power warning overlay when the device doesn’t have enough power. I/O port power: Turn on to supply 12 V power to external devices connected to the I/O ports. Leave off to prioritize internal functions, such as IR, heating, and cooling. As a result, devices and sensors that require 12 V power will stop working properly. |
Power meter
Energy usage
Shows the current power usage, average power usage, maximum power usage, and power consumption over time. The context menu contains:
|
Edge-to-edge
Pairing
Pairing allows you to use a compatible Axis device as if it were part of the main device.
Add: Add a device to pair with. Discover devices: Click to find devices on the network. When the network has been scanned a list of available devices is shown. Note The list will show all Axis devices that are found, not only devices that can be paired. Only devices with Bonjour enabled can be found. To enable Bonjour for a device, open the device’s web interface and go to System > Network > Network discovery protocols. Note An info icon is shown for devices that have already been paired. Hover over the icon to get information about pairings that are already active. |
Audio pairing allows you to pair with network speaker or microphone. Once paired, the network speaker acts as an audio out device where you can play audio clips and transmit sound through the camera. The network microphone will take up sounds from the surrounding area and make it available as an audio input device, usable in media streams and recordings.
For this feature to work with a video management software (VMS), you must first pair the camera with the speaker or microphone, then add the camera 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.
To pair a device from the list, click . Select pairing type: Select from the drop-down list. Speaker pairing: Select to pair a network speaker. Microphone pairing: Select to pair a microphone. Address: Enter host name or IP address to the network speaker. Username: Enter username. Password: Enter password for the user. Close: Click to clear all fields. Connect: Click to establish connection to the device to pair with. |
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.
To pair a device from the list, click . Select pairing type: Select from the drop-down list. 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. Close: 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. |
Generic pairing allows you to pair with a device with light and siren functionality.
To pair a device from the list, click . Select pairing type: Select from the drop-down list. Address: Enter host name or IP address to the device. Username: Enter username. Password: Enter password. Certificate name: Enter certificate name. Close: Click to clear all fields. Connect: Click to establish connection to the device to pair with. |
Logs
Reports and logs
Reports
Logs
|
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. Type: Select the type of logs you want to send. Test server setup: Send a test message to all servers before you save the settings. 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
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. |
Troubleshoot
Reset PTR: Reset PTR if for some reason the Pan, Tilt, or Roll settings aren’t working as expected. The PTR motors are always calibrated in a new camera. But calibration can be lost, for example, if the camera loses power or if the motors are moved by hand. When you reset PTR, the camera is re-calibrated and returns to its factory default position. Calibration: Click Calibrate to recalibrate the pan, tilt, and roll motors to their default positions. Ping: To check if the device can reach a specific address, enter the hostname or IP address of the host you want to ping and click Start. Port check: To verify connectivity from the device to a specific IP address and TCP/UDP port, enter the hostname or IP address and port number you want to check and click Start. Network trace Important A network trace file might contain sensitive information such as 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. |
Learn more
Radar
Recognition and detection zones
The recognition zone is a zone where the radar with certainty can classify objects as humans or vehicles.
The detection zone is a zone where the radar can detect fast-moving vehicles.
The size of each zone depends on installation height and other factors.
Scenarios, inclusion zones, and exclusion zones
A scenario consists of a set of conditions that moving objects must fulfill to trigger rules in the event system. Some of the conditions are:
Object type (human, vehicle, unknown)
Object behavior (movement in area or line crossing)
Part of the scene (inclusion zone or virtual line)
Object speed
The inclusion zone is the part of the scene where objects in a Movement in area scenario are detected and classified.
If there are areas in the scene where you don’t want moving objects to trigger alarms, you can create exclusion zones. You can also use exclusion zones if there are areas inside an inclusion zone that cause a lot of unwanted alarms. In an exclusion zone, moving objects are ignored. Use them to filter out, for example, swaying foliage on the side of a road or ghost tracks caused by objects made of radar-reflective materials such as a metal fence.
Coexistence zone
You can install multiple radars to cover areas that are larger than a single radar’s specified detection zone. Radars that use the same radio frequency can cause electromagnetic interference, which can affect the performance. Each Axis radar model has a specified coexistence zone. Within this you can install a certain number of radars without causing interference. To find out the radius and the recommended maximum number of radars of the coexistence zone, see the device’s datasheet at axis.com.
Radar-video fusion technology
Radar-video fusion combines the strengths of an Axis radar with those of an Axis camera. This combination provides great situational awareness and reduces false alarms. When you pair an ARTPEC-9 PTZ camera with an ARTPEC-9 radar from the camera’s web interface, the radar can discover and classify a moving object, direct the camera to the object, and let the camera validate the classification. The camera can then continue tracking the object with autotracking, which you can read about in the PTZ camera’s user manual.
Autotracking
You can use radar data about different objects’ positions to make a PTZ camera track objects. There are three different options:
If you want to connect multiple PTZ cameras and radars, use the application AXIS Radar Autotracking for PTZ. For more information, see Control a PTZ camera with AXIS Radar Autotracking for PTZ.
If you want to connect one radar and one ARTPEC-7 PTZ camera that are mounted close to each other, use camera pairing to use the built-in radar autotracking.
If you want to connect one radar and one ARTPEC-9 PTZ camera that are mounted together, use radar pairing to use built-in radar-video fusion autotracking. This option combines AI-powered radar and video analytics to minimize false alarms. For instructions on how to set up radar-video fusion autotracking, see the PTZ camera’s user manual at help.axis.com/axis-q6325-le.
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.
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.
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.
AV1
AV1 (AOMedia Video 1) is a license -free video coding format optimized for streaming media. AV1 enables high-quality video streaming even in bandwidth-constrained environments. By reducing a video's bitrate, AV1 preserves video quality while minimizing data usage.
AV1 supports all major browsers, computer operating systems and mobile platforms.
AV1 requires more processing power for encoding and decoding compared to some other codecs.
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.
- Target bitrate
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
Edge-to-edge technology
Edge-to-edge is a technology that makes IP devices communicate directly with each other. It offers smart pairing functionality between, for example, Axis cameras and Axis audio or radar products.
For more information, see the white paper “Edge-to-edge technology” at whitepapers.axis.com/edge-to-edge-technology.
Speaker pairing
Edge-to-edge speaker pairing allows you to use a compatible Axis network speaker as if it’s part of your camera. Once paired, the speaker's features are integrated in the camera's web interface and the network speaker acts as an audio out device where you can play audio clips and transmit sound through the camera.
The camera will identify itself to the VMS as a camera with integrated audio output and redirect any played audio to the speaker.
Microphone pairing
Edge-to-edge microphone pairing allows you to use a compatible Axis microphone as if it’s part of your camera. Once paired, the microphone will take up sounds from the surrounding area and make it available as an audio input device, usable in media streams and recordings.
Cybersecurity
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.
Axis security notification service
Axis provides a notification service with information about vulnerability and other security related matters for Axis devices. To receive notifications, you can subscribe at axis.com/security-notification-service.
Vulnerability management
To minimize customers' risk of exposure, Axis, as a Common Vulnerability and Exposures (CVE) numbering authority (CNA), follows industry standards to manage and respond to discovered vulnerabilities in our devices, software, and services. For more information about Axis vulnerability management policy, how to report vulnerabilities, already disclosed vulnerabilities, and corresponding security advisories, see axis.com/vulnerability-management.
Secure operation of Axis devices
Axis devices with factory default settings are pre-configured with secure default protection mechanisms. We recommend using more security configuration when installing the device. To learn more about Axis' approach to cybersecurity, including best practices, resources, and guidelines for securing your devices, go to axis.com/about-axis/cybersecurity.
Specifications
Product overview
- Network connector (PoE out)
- Dynamic LED strip
- Hook for safety wire
- Network connector (PoE in)
- Ground screw
- microSD card slot
- Control button
- Action button
- Function button (not used)
LED indicators
| Status LED | Indication |
| Green | Steady green for normal operation. |
| Amber | Steady during startup. Flashes during device software upgrade or reset to factory default. |
| 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.
Connectors
Network connector (PoE in)
RJ45 Ethernet connector with Power over Ethernet IEEE 802.3bt, Type 4 Class 8.
Power over Ethernet IEEE 802.3bt, Type 4 Class 8, 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)
Power over Ethernet IEEE 802.3bt, Type 3 Class 6.
Use this connector to supply power to another PoE device, for example a camera, a horn speaker, or a second Axis radar.
- Powering the radar with Power over Ethernet IEEE 802.3bt, Type 4 Class 8 allows for a second device that is using Power over Ethernet IEEE 802.3bt, Type 3 Class 6.
- Powering the radar with Power over Ethernet IEEE 802.3bt, Type 3 Class 6 allows for a second device that is using Power over Ethernet IEEE 802.3bt, Type 2 Class 4.
- If powering the radar with Power over Ethernet IEEE 802.3bt, Type 2 Class 4 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.
Clean your device
You can clean your device with lukewarm water and mild, nonabrasive soap.
- Harsh chemicals can damage the device. Don’t use chemicals such as window cleaner or acetone to clean your device.
- Don’t spray detergent directly on the device. Instead, spray detergent on a nonabrasive cloth and use that to clean the 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 and mild, nonabrasive soap.
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.
Make sure 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.
AXIS OS options
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.
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
- When you upgrade the device software, your preconfigured and customized settings are saved. Axis Communications AB can't guarantee that the settings are saved, even if the features are available in the new AXIS OS version.
- Starting from AXIS OS 12.6, you must install every LTS version between your device’s current version and the target version. For example, if the currently installed device software version is AXIS OS 11.2, you have to install the LTS version AXIS OS 11.11 before you can upgrade the device to AXIS OS 12.6. For more information, see AXIS OS Portal: Upgrade path.
- Make sure the device remains connected to the power source throughout the upgrade process.
- Make sure the cover is attached during upgrade to avoid installation failure.
- 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 problems and possible solutions
Problems upgrading AXIS OS
AXIS OS upgrade failed 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
Can’t set the IP address
|
Problems accessing the device
Can’t log in when accessing the device from a browser When HTTPS is enabled, make sure that you use the correct protocol (HTTP or HTTPS) when you try to log in. You might need to manually type If you’ve lost the password for the root account, you must reset the device to the factory default settings. For instructions, see Reset to factory default settings. |
The IP address has been changed by DHCP IP addresses obtained from a DHCP server are dynamic and could 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, you can assign a static IP address 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 browser isn’t supported For a list of recommended browsers, see Browser support. |
Can’t access the device 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. |
Problems with MQTT
Can’t connect over port 8883 with MQTT over SSL The firewall blocks traffic that uses port 8883 since it’s regarded insecure. In some cases the server/broker might not provide a specific port for MQTT communication. It might still be possible to use MQTT over a port normally used for HTTP/HTTPS traffic.
|
If you can’t find what you’re looking for here, try the troubleshooting section at axis.com/support.
Problems with the image
Image degradation or image loss
|
Problems with the device turning itself off
The device shuts down
|
Performance considerations
When you set up your system, it’s important to consider how different settings and situations affect the required bandwidth (bitrate).
The most important factors to consider:
Removing or attaching the cover will restart the camera.
Heavy network utilization due to poor infrastructure affects the bandwidth.
Contact support
If you need more help, go to axis.com/support.