{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/check-axis-i-o-circuit-state-against-its-active-setting/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/check-axis-i-o-circuit-state-against-its-active-setting/",
        "slug": "check-axis-i-o-circuit-state-against-its-active-setting",
        "url": "https://update.dsesecurity.com/updates/check-axis-i-o-circuit-state-against-its-active-setting/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/check-axis-i-o-circuit-state-against-its-active-setting.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/check-axis-i-o-circuit-state-against-its-active-setting/"
        },
        "title": "Check Axis I/O circuit state against its active setting",
        "summary": "Read Axis I/O circuit state and active-state configuration together. Do not infer an alarm meaning from an open or closed level without checking the port’s direction and configured interpretation.",
        "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": "access-control",
                "name": "Access Control",
                "url": "https://update.dsesecurity.com/topic/access-control/"
            },
            {
                "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-29T20:33:29+00:00",
        "modified_at": "2026-10-29T20:33:34+00:00",
        "reviewed_on": "2026-10-29",
        "reading_minutes": 3,
        "word_count": 498,
        "potentially_affected": "Axis products exposing the documented Input and outputs interface; confirm actual device, hardware and software applicability before applying the proposed checks.",
        "dse_recommendation": "DSE recommends a port worksheet linking direction, raw circuit state, active-state configuration and intended event meaning.",
        "primary_source": {
            "name": "Axis Communications — Input and outputs",
            "url": "https://developer.axis.com/vapix/network-video/input-and-outputs/",
            "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": "<p><strong>Bottom line:</strong> Keep the measured circuit level separate from the configured active state. Have the sensor and integration owners agree which combination represents the intended operational event before changing an input rule.</p>\n<h2>Source fact: documented behavior</h2>\n<p>Axis’s <a href=\"https://developer.axis.com/vapix/network-video/input-and-outputs/\" target=\"_blank\" rel=\"noopener noreferrer\">Input and outputs</a> says the I/O <code>check</code> result uses <code>1</code> for a closed circuit and <code>0</code> for an open circuit.</p>\n<p>The <code>checkactive</code> result instead depends on <code>Output.Active</code> for an output or <code>Input.Trig</code> for an input.</p>\n<p>Its <code>ActiveStateEnum</code> defines <code>open</code> as active when floating and <code>closed</code> as active when grounded.</p>\n<h2>What the source does not establish</h2>\n<p>Do not turn an active flag into a diagnosis of wiring, supervision or a specific detector. Confirm the connector, device capability and manufacturer wiring instructions before a physical change. Keep simple circuit interpretation separate from supervised-input voltage ranges and from approval of a life-safety function.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>Which physical connector and logical port identifier are being reviewed?</li>\n<li>Is that port configured as an input or an output?</li>\n<li>What circuit condition should represent the approved active event?</li>\n<li>What independent observation can distinguish the detector state from the API interpretation?</li>\n</ul>\n<h2>DSE recommendation: controlled next steps</h2>\n<p><em>The following steps are DSE recommendations based on the cited source.</em></p>\n<p>DSE recommends a port worksheet linking direction, raw circuit state, active-state configuration and intended event meaning.</p>\n<ol>\n<li>Identify an authorized noncritical test input with its hardware owner. Record the connector and the API’s actual port identifier without assuming every interface uses the same numbering convention. Read direction and the relevant active-state configuration through supported operations, then write the intended normal and active observations in separate rows.</li>\n<li>Have the qualified hardware owner select a permitted way to exercise the input according to the exact product and detector instructions. Do not short an unfamiliar connector or apply an improvised voltage to demonstrate a software flag. Keep the initial configuration available and leave an unexplained wiring state unresolved.</li>\n<li>During the attended pilot, collect the raw circuit result and active result at each approved test state. Compare both with the worksheet and the detector observation. If the values disagree with the intended event, investigate the identified direction and configuration before reversing several downstream rules. Restore the approved normal state and verify the consuming application separately.</li>\n</ol>\n<h2>Verification and evidence</h2>\n<p>Retain the device and connector reference, port identity, direction, configuration values and paired observations. Have another reviewer explain why a circuit level and an active flag answer different questions. Require a specific disposition for an undefined or unexpected state rather than translating it silently into normal.</p>\n<p>Use a proposed paper case with an input configured active when open and another configured active when closed. Ask the reviewer to derive the intended interpretation from the documented settings, without claiming either arrangement describes an installed detector. No wiring inspection, input transition or alarm test has been performed for this article.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://developer.axis.com/vapix/network-video/input-and-outputs/\" target=\"_blank\" rel=\"noopener noreferrer\">Input and outputs</a> — Axis Communications; official VAPIX documentation.</li>\n</ul>\n<p>Source review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.</p>\n",
        "content_text": "Bottom line: Keep the measured circuit level separate from the configured active state. Have the sensor and integration owners agree which combination represents the intended operational event before changing an input rule.\nSource fact: documented behavior\nAxis’s Input and outputs says the I/O check result uses 1 for a closed circuit and 0 for an open circuit.\nThe checkactive result instead depends on Output.Active for an output or Input.Trig for an input.\nIts ActiveStateEnum defines open as active when floating and closed as active when grounded.\nWhat the source does not establish\nDo not turn an active flag into a diagnosis of wiring, supervision or a specific detector. Confirm the connector, device capability and manufacturer wiring instructions before a physical change. Keep simple circuit interpretation separate from supervised-input voltage ranges and from approval of a life-safety function.\nApplicability questions\n\nWhich physical connector and logical port identifier are being reviewed?\nIs that port configured as an input or an output?\nWhat circuit condition should represent the approved active event?\nWhat independent observation can distinguish the detector state from the API interpretation?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends a port worksheet linking direction, raw circuit state, active-state configuration and intended event meaning.\n\nIdentify an authorized noncritical test input with its hardware owner. Record the connector and the API’s actual port identifier without assuming every interface uses the same numbering convention. Read direction and the relevant active-state configuration through supported operations, then write the intended normal and active observations in separate rows.\nHave the qualified hardware owner select a permitted way to exercise the input according to the exact product and detector instructions. Do not short an unfamiliar connector or apply an improvised voltage to demonstrate a software flag. Keep the initial configuration available and leave an unexplained wiring state unresolved.\nDuring the attended pilot, collect the raw circuit result and active result at each approved test state. Compare both with the worksheet and the detector observation. If the values disagree with the intended event, investigate the identified direction and configuration before reversing several downstream rules. Restore the approved normal state and verify the consuming application separately.\n\nVerification and evidence\nRetain the device and connector reference, port identity, direction, configuration values and paired observations. Have another reviewer explain why a circuit level and an active flag answer different questions. Require a specific disposition for an undefined or unexpected state rather than translating it silently into normal.\nUse a proposed paper case with an input configured active when open and another configured active when closed. Ask the reviewer to derive the intended interpretation from the documented settings, without claiming either arrangement describes an installed detector. No wiring inspection, input transition or alarm test has been performed for this article.\nOfficial references\n\nInput and outputs — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.",
        "content_markdown": "Bottom line: Keep the measured circuit level separate from the configured active state. Have the sensor and integration owners agree which combination represents the intended operational event before changing an input rule.\n\n## Source fact: documented behavior\n\nAxis’s [Input and outputs](https://developer.axis.com/vapix/network-video/input-and-outputs/) says the I/O check result uses 1 for a closed circuit and 0 for an open circuit.\n\nThe checkactive result instead depends on Output.Active for an output or Input.Trig for an input.\n\nIts ActiveStateEnum defines open as active when floating and closed as active when grounded.\n\n## What the source does not establish\n\nDo not turn an active flag into a diagnosis of wiring, supervision or a specific detector. Confirm the connector, device capability and manufacturer wiring instructions before a physical change. Keep simple circuit interpretation separate from supervised-input voltage ranges and from approval of a life-safety function.\n\n## Applicability questions\n\n- Which physical connector and logical port identifier are being reviewed?\n\n- Is that port configured as an input or an output?\n\n- What circuit condition should represent the approved active event?\n\n- What independent observation can distinguish the detector state from the API interpretation?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends a port worksheet linking direction, raw circuit state, active-state configuration and intended event meaning.\n\n- Identify an authorized noncritical test input with its hardware owner. Record the connector and the API’s actual port identifier without assuming every interface uses the same numbering convention. Read direction and the relevant active-state configuration through supported operations, then write the intended normal and active observations in separate rows.\n\n- Have the qualified hardware owner select a permitted way to exercise the input according to the exact product and detector instructions. Do not short an unfamiliar connector or apply an improvised voltage to demonstrate a software flag. Keep the initial configuration available and leave an unexplained wiring state unresolved.\n\n- During the attended pilot, collect the raw circuit result and active result at each approved test state. Compare both with the worksheet and the detector observation. If the values disagree with the intended event, investigate the identified direction and configuration before reversing several downstream rules. Restore the approved normal state and verify the consuming application separately.\n\n## Verification and evidence\n\nRetain the device and connector reference, port identity, direction, configuration values and paired observations. Have another reviewer explain why a circuit level and an active flag answer different questions. Require a specific disposition for an undefined or unexpected state rather than translating it silently into normal.\n\nUse a proposed paper case with an input configured active when open and another configured active when closed. Ask the reviewer to derive the intended interpretation from the documented settings, without claiming either arrangement describes an installed detector. No wiring inspection, input transition or alarm test has been performed for this article.\n\n## Official references\n\n- [Input and outputs](https://developer.axis.com/vapix/network-video/input-and-outputs/) — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities 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/check-axis-i-o-circuit-state-against-its-active-setting/",
                "url": "https://update.dsesecurity.com/updates/check-axis-i-o-circuit-state-against-its-active-setting/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-10-29"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/check-axis-i-o-circuit-state-against-its-active-setting/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Access Control",
                        "item": "https://update.dsesecurity.com/topic/access-control/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 3,
                        "name": "Check Axis I/O circuit state against its active setting",
                        "item": "https://update.dsesecurity.com/updates/check-axis-i-o-circuit-state-against-its-active-setting/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/check-axis-i-o-circuit-state-against-its-active-setting/#article",
                "identifier": "https://update.dsesecurity.com/updates/check-axis-i-o-circuit-state-against-its-active-setting/",
                "url": "https://update.dsesecurity.com/updates/check-axis-i-o-circuit-state-against-its-active-setting/",
                "headline": "Check Axis I/O circuit state against its active setting",
                "description": "Read Axis I/O circuit state and active-state configuration together. Do not infer an alarm meaning from an open or closed level without checking the port’s…",
                "abstract": "Read Axis I/O circuit state and active-state configuration together. Do not infer an alarm meaning from an open or closed level without checking the port’s direction and configured interpretation.",
                "articleBody": "Bottom line: Keep the measured circuit level separate from the configured active state. Have the sensor and integration owners agree which combination represents the intended operational event before changing an input rule.\nSource fact: documented behavior\nAxis’s Input and outputs says the I/O check result uses 1 for a closed circuit and 0 for an open circuit.\nThe checkactive result instead depends on Output.Active for an output or Input.Trig for an input.\nIts ActiveStateEnum defines open as active when floating and closed as active when grounded.\nWhat the source does not establish\nDo not turn an active flag into a diagnosis of wiring, supervision or a specific detector. Confirm the connector, device capability and manufacturer wiring instructions before a physical change. Keep simple circuit interpretation separate from supervised-input voltage ranges and from approval of a life-safety function.\nApplicability questions\n\nWhich physical connector and logical port identifier are being reviewed?\nIs that port configured as an input or an output?\nWhat circuit condition should represent the approved active event?\nWhat independent observation can distinguish the detector state from the API interpretation?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends a port worksheet linking direction, raw circuit state, active-state configuration and intended event meaning.\n\nIdentify an authorized noncritical test input with its hardware owner. Record the connector and the API’s actual port identifier without assuming every interface uses the same numbering convention. Read direction and the relevant active-state configuration through supported operations, then write the intended normal and active observations in separate rows.\nHave the qualified hardware owner select a permitted way to exercise the input according to the exact product and detector instructions. Do not short an unfamiliar connector or apply an improvised voltage to demonstrate a software flag. Keep the initial configuration available and leave an unexplained wiring state unresolved.\nDuring the attended pilot, collect the raw circuit result and active result at each approved test state. Compare both with the worksheet and the detector observation. If the values disagree with the intended event, investigate the identified direction and configuration before reversing several downstream rules. Restore the approved normal state and verify the consuming application separately.\n\nVerification and evidence\nRetain the device and connector reference, port identity, direction, configuration values and paired observations. Have another reviewer explain why a circuit level and an active flag answer different questions. Require a specific disposition for an undefined or unexpected state rather than translating it silently into normal.\nUse a proposed paper case with an input configured active when open and another configured active when closed. Ask the reviewer to derive the intended interpretation from the documented settings, without claiming either arrangement describes an installed detector. No wiring inspection, input transition or alarm test has been performed for this article.\nOfficial references\n\nInput and outputs — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.",
                "datePublished": "2026-10-29T20:33:29+00:00",
                "dateModified": "2026-10-29T20:33:34+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/check-axis-i-o-circuit-state-against-its-active-setting/"
                },
                "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/check-axis-i-o-circuit-state-against-its-active-setting/#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": "Check Axis I/O circuit state against its active setting"
                },
                "articleSection": [
                    "Access Control",
                    "IT",
                    "Video Surveillance"
                ],
                "keywords": [
                    "Access Control",
                    "IT",
                    "Video Surveillance",
                    "Guide",
                    "Advisory priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Access Control",
                        "url": "https://update.dsesecurity.com/topic/access-control/"
                    },
                    {
                        "@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": 498,
                "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 — Input and outputs",
                    "url": "https://developer.axis.com/vapix/network-video/input-and-outputs/"
                }
            }
        ]
    }
}