Choose Axis radar guard tour dwell time for detected objects

Bottom line: Choose how long the radar-driven tour should remain on each detected object. Read the supported time range from the actual device before proposing a value or accepting the observed tour.

Source fact: documented behavior

The Radar autotracking says its enabled guard tour directs the PTZ toward radar-detected objects in chronological order.

The documented guard-tour time controls how long the PTZ lingers on each object during that tour.

The getGuardTourTime response supplies the current value and minimum and maximum values in seconds; setGuardTourTime changes the time within that documented workflow.

What the source does not establish

This article concerns a tour between detected objects. Do not transfer ordinary preset-tour settings into it or interpret the dwell setting as a guaranteed identification opportunity. Radar detection, camera alignment, operator priorities and the response plan need their own acceptance checks.

Applicability questions

• Is the requested behavior a radar object tour rather than a preset route?
• What current time and bounds does the device report?
• Which permitted scene and object sequence can demonstrate the intended dwell?
• Who can stop camera movement during the observation?

DSE recommendation: controlled next steps

The following steps are DSE recommendations based on the cited source.

DSE recommends choosing the object-tour dwell value from actual device-reported limits and an operator-reviewed observation plan.

1. Identify the radar and controlled PTZ before changing anything. Retrieve the existing guard-tour enablement and time through the supported methods. Preserve the returned units and bounds beside the current value. Ask the operator to describe the required viewing opportunity without translating that requirement directly into an unverified number of seconds.
2. Propose a value inside the returned range and review it with the operator. Keep return-to-home settings and unrelated preset routes outside this edit. Use a desk scenario with two authorized objects detected at different times and ask the reviewer to describe the intended viewing sequence. Mark uncertain behavior as a question for the actual supported deployment rather than filling it with an assumed priority rule.
3. Schedule an attended observation with a clear movement area and a supported stop procedure. Apply only the approved dwell change, read it back and retain the response. Use only the permitted scene arrangement; do not introduce people or vehicles into a hazardous area merely to generate detections. Restore the prior value if the operator rejects the resulting observation opportunity.

Verification and evidence

Proposed verification: record the approved detected-object sequence and actual camera observations on one timeline. Compare the observed dwell with the selected setting while keeping detection times and operator intervention visible. A discrepancy should remain open until the device-specific behavior is explained; avoid changing several tracking settings in the same attempt.

Have a second reviewer distinguish the configured number, the returned value and the actual viewing result. Preserve only the necessary sanitized scene evidence and record which controls were changed. No radar detections, camera movement or dwell-time measurement was performed for this article, and the proposed exercise supplies no coverage or identification guarantee.

Official references

• Radar autotracking — Axis Communications; official VAPIX documentation.

Source review completed October 30, 2026. Recheck the official source and deployment-specific applicability before changing production settings.