What this solves

A PTZ that pans to a moving object looks impressive in a demo, but in a live installation the value depends on whether it tracks the right object for the right amount of time and then returns to a useful idle state. Dahua's Web 5.0 interface exposes auto tracking as a parameter of the linkage behaviour, not as a standalone detector. That distinction matters: tracking inherits whatever the rule already decided.

This guide walks through the order that avoids rework — confirm the rule and target filter, set the tracking duration and target size ratio, then enable tracking, then tune patrol and presets. Where the manual does not confirm a behaviour for a given model, we say so rather than guessing.

The scope here is the parameters documented in the Dahua Network PTZ Camera Web 5.0 User Manual V3.0.1: auto tracking and tracking duration (p. 224), target filter and effective target action (p. 224), auto patrol with preset and scan linkage (p. 224), linkage track parameters for panorama-detail configurations (p. 184), and the Linkage Track / Relay Tracking modes (p. 243).

How the workflow works

The chain is: a smart plan and IVS rule detect a target, the target filter decides whether that target is "effective", the effective target action decides whether appearance or crossing counts, and only then does auto tracking move the PTZ. If any earlier stage is misconfigured, the tracking stage cannot compensate.

On dual-lens or panorama-detail models the chain gains a second layer. The panorama camera detects and the detail camera tracks, and the tracking duration options differ — you can continue until the object disappears, use a custom time, or tie tracking to when the object leaves the panorama or detail camera's view (p. 184). The Tracking Target Size Ratio then sets how large the tracked object should appear in the detail camera's frame (p. 184).

Idle behaviour is the third layer. Auto Patrol lets the camera return to a patrol of presets or a scan when nothing is being tracked, and it is not enabled by default (p. 224). That is the piece most often left unconfigured, which is why cameras end up parked at an odd angle after an event.

Prerequisites and site checks

Before touching the web interface, confirm the camera supports the functions you intend to sell. The manual is explicit that only some devices support auto tracking (p. 224), and that linkage track only supports tracking humans on select models (p. 243). Check the datasheet for the exact model and firmware you are quoting, not the product family.

Site checks that save callbacks: verify the PTZ has enough travel and speed for the scene, confirm the presets you intend to use for patrol are already stored, and confirm scan rules exist if you plan to use scan linkage. The manual states that all IVS rules support the scan linkage but that you must configure preset and scan rules in PTZ in advance (p. 224).

On the network side, confirm the recorder or VMS can consume the stream and any alarm outputs. If third-party integration is in scope, validate against the ONVIF profile your platform requires — onvif.org publishes the profiles, but conformance is a model and firmware question. For a broader hardware shortlist, see our PTZ cameras and WizMind ranges.

Step-by-step configuration

Step 1 — Build the rule first. Configure the smart plan and the IVS rule (tripwire, intrusion, or fast moving) as you normally would. Do not enable auto tracking yet. The target filter only applies to tripwire, intrusion and fast moving (p. 224), so if you are using a different rule type, expect the filter options to be unavailable.

Step 2 — Set the target filter. Enable Target Filter so that only effective targets are detected. Effective targets are Human and Motor Vehicle, and non-motor vehicles fall under the People category (p. 224). Note the manual's wording: when the target filter is enabled, non-effective targets are not detected and will not trigger alarms (p. 224). That is a deliberate trade — fewer false alarms, but you lose events from anything outside those classes.

Step 3 — Set the effective target action. For intrusion rules, choose whether the target must Appear or Cross (p. 224). Appear is more sensitive and suits perimeter warning; Cross is stricter and suits a defined boundary. Pick one and document it, because it changes what "detected" means for every downstream action.

Step 4 — Set tracking duration. On single-lens PTZ configurations, configure Tracking Duration alongside auto tracking; the camera tracks and captures the target until the tracking duration is reached (p. 224). On panorama-detail configurations the options are richer: continue till object disappears, custom time, track until objects captured by the panorama camera disappear, or track until objects captured by the detail camera disappear (p. 184).

Step 5 — Set the target size ratio (panorama-detail only). Tracking Target Size Ratio sets the proportion of the tracked object to the detail camera screen (p. 184). Start moderate and adjust after observing real subjects at real distances.

Step 6 — Enable auto tracking. Only now enable the function. On panorama-detail models, select the tracking mode: Linkage Track stops the detail camera when the target leaves the panorama camera's view, while Relay Tracking lets the detail camera continue (p. 243). Also note that on those models, manual position and manual linkage only take effect when linkage track is enabled (p. 243).

Step 7 — Configure idle behaviour. Enable Auto Patrol and choose Preset or Scan from the Linkage Operation drop-down, then select the corresponding preset or scan rule (p. 224). You may select one or more presets, up to five, and multiple presets are executed in order (p. 224). If you enable SMD in advance, Smart Motion Detection opens automatically once presets are configured (p. 224).

Tuning and verification

Verify in layers. First, with tracking disabled, confirm the rule fires on a person and a vehicle and does not fire on a non-effective object. Second, enable tracking and confirm the camera acquires and follows. Third, confirm it releases and returns to patrol. Each layer isolates a different failure.

Use the table below as a starting point, then adjust against observed behaviour. These are engineering starting points, not vendor defaults — the manual does not publish recommended values, and the correct value depends on scene geometry, lens, and subject speed.

The second table maps the symptoms you will actually see on commissioning to the stage that caused them. Work top-down; the earlier stages are cheaper to fix.

Record the final values in the handover pack. Tracking behaviour is sensitive to preset positions, so any later change to a preset should trigger a re-check of patrol order and duration.

Buying notes and deployment fit

For a buyer, the practical question is not "does it auto track" but "does this specific model and firmware support the tracking mode my scene needs". Auto tracking is model-dependent (p. 224), and human tracking under linkage track is limited to select models (p. 243). Ask for the datasheet and, where possible, a firmware version in writing.

Single-lens PTZ suits a scene with one area of interest where a bounded custom tracking duration is acceptable. Panorama-detail configurations suit wide areas where you want continuous situational awareness plus a detail camera that can relay tracking beyond the panorama's view (p. 243). The relay mode is the differentiator when subjects move along a long perimeter.

Budget for the recorder side too. Multi-camera sites with tracking events generate more clips and alarm records; size storage and review workflows accordingly. Our network recorders collection covers the common pairings. If you need help matching a model to a scene, contact our team with the site plan and camera positions.

FAQ

Does enabling auto tracking also enable detection? No. Auto tracking is a linkage behaviour configured alongside the rule; the rule and smart plan must be set up first, and the manual describes tracking as following detection (p. 224).

Why do I get no alarms on some objects? If Target Filter is enabled, non-effective targets are not detected and alarms are not triggered; effective targets are Human and Motor Vehicle, with non-motor vehicles counted as People (p. 224).

What is the difference between Linkage Track and Relay Tracking? With Linkage Track the detail camera stops when the target leaves the panorama camera's view; with Relay Tracking the detail camera continues tracking (p. 243).

How many presets can auto patrol use? Up to five, and if multiple presets are configured the patrol executes them in order (p. 224). Auto Patrol is not enabled by default.

Why is manual positioning not working? On models with linkage track, manual position and manual linkage only take effect when linkage track is enabled (p. 243).

Are the tuning values in this article vendor defaults? No. The manual documents the parameters and their effects but does not publish recommended values; the correct settings depend on model, firmware and scene.

Sources

• Dahua Network PTZ Camera Web 5.0 User Manual V3.0.1 — page 224 (auto tracking, tracking duration, target filter, effective target action, auto patrol, preset and scan linkage); page 184 (linkage track parameters, tracking duration modes, tracking target size ratio); page 243 (linkage track, Linkage Track vs Relay Tracking modes).
• Dahua official site: https://www.dahuasecurity.com/
• ONVIF: https://www.onvif.org/