{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/choose-axis-radar-guard-tour-dwell-time-for-detected-objects/", "item": { "id": "https://update.dsesecurity.com/updates/choose-axis-radar-guard-tour-dwell-time-for-detected-objects/", "slug": "choose-axis-radar-guard-tour-dwell-time-for-detected-objects", "url": "https://update.dsesecurity.com/updates/choose-axis-radar-guard-tour-dwell-time-for-detected-objects/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/choose-axis-radar-guard-tour-dwell-time-for-detected-objects.md", "json": "https://update.dsesecurity.com/api/v1/posts/choose-axis-radar-guard-tour-dwell-time-for-detected-objects/" }, "title": "Choose Axis radar guard tour dwell time for detected objects", "summary": "Set the radar object tour’s per-object dwell time using the device’s reported bounds. Keep that time distinct from an ordinary preset-tour wait or a return-to-home timeout.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "advisory", "name": "Advisory" }, "featured": false, "image": { "theme": "physical-security", "label": "Physical security", "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.", "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "video-surveillance", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-30T06:05:06+00:00", "modified_at": "2026-10-30T06:05:13+00:00", "reviewed_on": "2026-10-30", "reading_minutes": 3, "word_count": 516, "potentially_affected": "Axis radar autotracking deployments exposing the documented guard-tour methods; confirm actual radar, PTZ and software support.", "dse_recommendation": "DSE recommends choosing the object-tour dwell value from actual device-reported limits and an operator-reviewed observation plan.", "primary_source": { "name": "Axis Communications — Radar autotracking", "url": "https://developer.axis.com/vapix/radar/radar-autotracking/", "published_on": null, "authority": "Axis Communications" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

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.

\n

Source fact: documented behavior

\n

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

\n

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

\n

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

\n

What the source does not establish

\n

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.

\n

Applicability questions

\n\n

DSE recommendation: controlled next steps

\n

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

\n

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

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

Verification and evidence

\n

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.

\n

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.

\n

Official references

\n\n

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

\n", "content_text": "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.\nSource fact: documented behavior\nThe Radar autotracking says its enabled guard tour directs the PTZ toward radar-detected objects in chronological order.\nThe documented guard-tour time controls how long the PTZ lingers on each object during that tour.\nThe getGuardTourTime response supplies the current value and minimum and maximum values in seconds; setGuardTourTime changes the time within that documented workflow.\nWhat the source does not establish\nThis 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.\nApplicability questions\n\nIs the requested behavior a radar object tour rather than a preset route?\nWhat current time and bounds does the device report?\nWhich permitted scene and object sequence can demonstrate the intended dwell?\nWho can stop camera movement during the observation?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends choosing the object-tour dwell value from actual device-reported limits and an operator-reviewed observation plan.\n\nIdentify 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.\nPropose 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.\nSchedule 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.\n\nVerification and evidence\nProposed 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.\nHave 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.\nOfficial references\n\nRadar autotracking — Axis Communications; official VAPIX documentation.\n\nSource review completed October 30, 2026. Recheck the official source and deployment-specific applicability before changing production settings.", "content_markdown": "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.\n\n## Source fact: documented behavior\n\nThe [Radar autotracking](https://developer.axis.com/vapix/radar/radar-autotracking/) says its enabled guard tour directs the PTZ toward radar-detected objects in chronological order.\n\nThe documented guard-tour time controls how long the PTZ lingers on each object during that tour.\n\nThe getGuardTourTime response supplies the current value and minimum and maximum values in seconds; setGuardTourTime changes the time within that documented workflow.\n\n## What the source does not establish\n\nThis 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.\n\n## Applicability questions\n\n- Is the requested behavior a radar object tour rather than a preset route?\n\n- What current time and bounds does the device report?\n\n- Which permitted scene and object sequence can demonstrate the intended dwell?\n\n- Who can stop camera movement during the observation?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends choosing the object-tour dwell value from actual device-reported limits and an operator-reviewed observation plan.\n\n- 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.\n\n- 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.\n\n- 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.\n\n## Verification and evidence\n\nProposed 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.\n\nHave 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.\n\n## Official references\n\n- [Radar autotracking](https://developer.axis.com/vapix/radar/radar-autotracking/) — Axis Communications; official VAPIX documentation.\n\nSource review completed October 30, 2026. Recheck the official source and deployment-specific applicability before changing production settings." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/choose-axis-radar-guard-tour-dwell-time-for-detected-objects/", "url": "https://update.dsesecurity.com/updates/choose-axis-radar-guard-tour-dwell-time-for-detected-objects/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-30" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/choose-axis-radar-guard-tour-dwell-time-for-detected-objects/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "IT", "item": "https://update.dsesecurity.com/topic/it/" }, { "@type": "ListItem", "position": 3, "name": "Choose Axis radar guard tour dwell time for detected objects", "item": "https://update.dsesecurity.com/updates/choose-axis-radar-guard-tour-dwell-time-for-detected-objects/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/choose-axis-radar-guard-tour-dwell-time-for-detected-objects/#article", "identifier": "https://update.dsesecurity.com/updates/choose-axis-radar-guard-tour-dwell-time-for-detected-objects/", "url": "https://update.dsesecurity.com/updates/choose-axis-radar-guard-tour-dwell-time-for-detected-objects/", "headline": "Choose Axis radar guard tour dwell time for detected objects", "description": "Set the radar object tour’s per-object dwell time using the device’s reported bounds.", "abstract": "Set the radar object tour’s per-object dwell time using the device’s reported bounds. Keep that time distinct from an ordinary preset-tour wait or a return-to-home timeout.", "articleBody": "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.\nSource fact: documented behavior\nThe Radar autotracking says its enabled guard tour directs the PTZ toward radar-detected objects in chronological order.\nThe documented guard-tour time controls how long the PTZ lingers on each object during that tour.\nThe getGuardTourTime response supplies the current value and minimum and maximum values in seconds; setGuardTourTime changes the time within that documented workflow.\nWhat the source does not establish\nThis 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.\nApplicability questions\n\nIs the requested behavior a radar object tour rather than a preset route?\nWhat current time and bounds does the device report?\nWhich permitted scene and object sequence can demonstrate the intended dwell?\nWho can stop camera movement during the observation?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends choosing the object-tour dwell value from actual device-reported limits and an operator-reviewed observation plan.\n\nIdentify 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.\nPropose 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.\nSchedule 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.\n\nVerification and evidence\nProposed 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.\nHave 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.\nOfficial references\n\nRadar autotracking — Axis Communications; official VAPIX documentation.\n\nSource review completed October 30, 2026. Recheck the official source and deployment-specific applicability before changing production settings.", "datePublished": "2026-10-30T06:05:06+00:00", "dateModified": "2026-10-30T06:05:13+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/choose-axis-radar-guard-tour-dwell-time-for-detected-objects/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/choose-axis-radar-guard-tour-dwell-time-for-detected-objects/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Choose Axis radar guard tour dwell time for detected objects" }, "articleSection": [ "IT", "Video Surveillance" ], "keywords": [ "IT", "Video Surveillance", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "wordCount": 516, "timeRequired": "PT3M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Axis Communications — Radar autotracking", "url": "https://developer.axis.com/vapix/radar/radar-autotracking/" } } ] } }