Skip to main content
Designing for Axis Object Analytics

Troubleshooting and design considerations for Axis Object Analytics

Updated over 2 months ago

Overview

Arcules can bring in and support Axis Object Analytics from supported cameras.

This can include People and Vehicle Detection, as well as acting on triggers from Scenarios, leveraging the power of your Axis cameras at the edge.

Supported cameras and considerations

All Axis cameras compatible with Axis Object Analytics will work, but there are a few important notes to consider:

  • Dual sensor / multi-sensor cameras are not recommended

    • Only the first sensor will deliver object detections to Arcules

  • Both machine-learning and deep learning (MLPU and DLPU) Axis cameras are supported

    • DLPU cameras will provide higher detection accuracy

  • Some older Axis cameras require you update firmware to install the AOA application

  • Axis PTZ cameras are supported

How Arcules incorporates Axis Analytics functionality

Axis Object Detection

Arcules can ingest the People and Vehicle detection data from Axis Object Analytics.

Edge gateway-connected cameras most commonly use this functionality, as Arcules' detections can only be applied to Cloud gateway cameras. With the Axis analytics, you however do not currently get the ability to filter by color.

Cloud gateway-connected cameras can use Arcules Cloud Analytics with higher accuracy and color search

Camera-to-cloud cameras have this functionality automatically enabled.

Axis Object Analytics Scenarios

You can use Axis Object Analytics Scenarios for additional event functionality. This allows you to trigger rules based on the alarm condition of any AOA Scenario, or if using a counting scenario, if a certain count is met or exceeded.

This can also be configured to utilize our Occupancy Analytic widget.

Caveats

Additional Axis Object Analytics options in the AXIS OS interface (like the Settings tab) will not have an effect for Arcules Device Analytics.

You might see people and vehicle detections on your playback timeline, or Forensic Search results, even though no video was recorded during the time of detection.


This is expected behavior if your recording schedule indicates no recording or if you are recording on motion and no motion is detected.

You may want to adjust your motion detection settings if you are missing recordings when the camera is detecting people or vehicles in the scene.

Network connectivity

Object detections are delivered from your Axis camera to the gateway then uploaded to the Arcules cloud. It is best to maintain consistent network connectivity from gateway to cloud.

An additional 20 Kbps to 100 Kbps bandwidth per camera may be needed. Bandwidth can vary significantly per camera based on the camera model and frequency of detections.

If network connectivity from your gateway to the Arcules cloud is interrupted, new detections will not be available until it is restored. This means rules, alarms, notifications, and other functionality will be delayed.

Once connectivity is restored, the gateway will "catch up" delivering detections delayed during the outage, resulting in increased bandwidth.

Troubleshooting

  • You won't see an Object Detection option with an edge gateway-connected camera if it is not an Axis device.

    • On a cloud-gateway connected camera, you won't be able to choose "Device" as your analytics source, only "Cloud" if it is not an Axis device.

  • Axis cameras without Axis Object Analytics will not deliver object detections, even though you can still select "Device" as your analytics source. Make sure you're using an AXIS Object Analytics compatible camera with the proper firmware.

  • Adjust the resemblance slider(s) if you are getting false detections for either people or vehicles.

  • If rules don't seem to be triggering or are triggering minutes or hours after the actual detection, network connectivity or bandwidth may be delaying the uploading of object detections to the cloud.

Did this answer your question?