{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/check-shared-physical-pins-before-assigning-axis-controller-i-o/", "item": { "id": "https://update.dsesecurity.com/updates/check-shared-physical-pins-before-assigning-axis-controller-i-o/", "slug": "check-shared-physical-pins-before-assigning-axis-controller-i-o", "url": "https://update.dsesecurity.com/updates/check-shared-physical-pins-before-assigning-axis-controller-i-o/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/check-shared-physical-pins-before-assigning-axis-controller-i-o.md", "json": "https://update.dsesecurity.com/api/v1/posts/check-shared-physical-pins-before-assigning-axis-controller-i-o/" }, "title": "Check shared physical pins before assigning Axis controller I/O", "summary": "Map logical Axis controller I/O to required modes and shared physical pins before assigning services. Do not treat different logical names as independent hardware resources.", "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/" } ], "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-29T17:41:32+00:00", "modified_at": "2026-10-29T17:41:37+00:00", "reviewed_on": "2026-10-29", "reading_minutes": 3, "word_count": 564, "potentially_affected": "Axis products exposing the documented I/O assignment service interface; confirm actual device, hardware and software applicability before applying the proposed checks.", "dse_recommendation": "DSE recommends approving a pin-conflict worksheet before applying a new logical I/O assignment.", "primary_source": { "name": "Axis Communications — I/O assignment service", "url": "https://developer.axis.com/vapix/physical-access-control/io-assignment-service/", "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: Check the physical pin overlap behind each logical I/O choice before assigning controller services. Build the allocation from actual service requirements and returned hardware information, rather than from convenient names.

\n

Source fact: documented behavior

\n

Axis’s I/O assignment service explains that an I/O represents how a combination of controller physical pins can be used, rather than being identical to one physical pin.

\n

Different pins have different electrical properties, and when multiple I/O choices use the same physical pins, only one of those I/O choices can be used at a time.

\n

The documented workflow configures the consuming services first, retrieves their requirements with axisio:GetIoUserInfoList, and retrieves available I/O and pin information with axisio:GetIoInfoList.

\n

What the source does not establish

\n

Do not use a logical allocation worksheet as permission to wire an arbitrary device to a terminal. Require the exact controller and connected-device documentation for electrical design. Keep this API allocation check separate from egress approval, lock-power design and proof that a physical reader or door operates correctly.

\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 approving a pin-conflict worksheet before applying a new logical I/O assignment.

\n
    \n
  1. Work from an authorized controller configuration and the approved point schedule. List each consuming entity, its service identity, intended use and required mode. Read the service requirements after the relevant entities have been configured. Preserve identifiers rather than matching entities only by a repeated label such as reader or door. Mark any requirement that has not yet been resolved.
    2. \n
  2. Retrieve the available logical I/O descriptions and expand each candidate into its physical pin list. For a proposed test case, compare two differently named choices that share a pin, if the device reports such a pair. Mark the pair as competing resources in the worksheet. Compare supported modes with each service requirement and refer electrical questions to the installer before making assignments.
    3. \n
  3. Choose an allocation with no unresolved pin conflict and apply it only through the supported workflow in an approved test window. Read back the resulting allocation. Have the qualified installer and application owner verify the intended point operation separately. If the readback or physical behavior disagrees with the plan, restore the approved configuration rather than trying additional undocumented combinations.
    4. \n
\n

Verification and evidence

\n

Retain the service-requirement response, available-I/O response, allocation worksheet and approved wiring reference together. Highlight the pin names that justified accepting one choice and rejecting another. Record device identity and software so a replacement-controller review does not inherit an unexamined allocation.

\n

Include a desk-review rejection case: present two proposed allocations sharing a returned pin and ask the reviewer to identify the conflict before implementation. Record that exercise as a proposed planning test, not as evidence that a field wiring fault was created or that a door’s complete safety and security workflow passed.

\n

Official references

\n\n

Source review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.

\n", "content_text": "Bottom line: Check the physical pin overlap behind each logical I/O choice before assigning controller services. Build the allocation from actual service requirements and returned hardware information, rather than from convenient names.\nSource fact: documented behavior\nAxis’s I/O assignment service explains that an I/O represents how a combination of controller physical pins can be used, rather than being identical to one physical pin.\nDifferent pins have different electrical properties, and when multiple I/O choices use the same physical pins, only one of those I/O choices can be used at a time.\nThe documented workflow configures the consuming services first, retrieves their requirements with axisio:GetIoUserInfoList, and retrieves available I/O and pin information with axisio:GetIoInfoList.\nWhat the source does not establish\nDo not use a logical allocation worksheet as permission to wire an arbitrary device to a terminal. Require the exact controller and connected-device documentation for electrical design. Keep this API allocation check separate from egress approval, lock-power design and proof that a physical reader or door operates correctly.\nApplicability questions\n\nWhich exact controller and installed software support the documented assignment service?\nWhich configured door or reader service requires each I/O, and in which mode?\nDo proposed logical I/O choices share any returned physical pin names?\nHas a qualified installer checked the electrical requirements against the approved wiring design?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends approving a pin-conflict worksheet before applying a new logical I/O assignment.\n\nWork from an authorized controller configuration and the approved point schedule. List each consuming entity, its service identity, intended use and required mode. Read the service requirements after the relevant entities have been configured. Preserve identifiers rather than matching entities only by a repeated label such as reader or door. Mark any requirement that has not yet been resolved.\nRetrieve the available logical I/O descriptions and expand each candidate into its physical pin list. For a proposed test case, compare two differently named choices that share a pin, if the device reports such a pair. Mark the pair as competing resources in the worksheet. Compare supported modes with each service requirement and refer electrical questions to the installer before making assignments.\nChoose an allocation with no unresolved pin conflict and apply it only through the supported workflow in an approved test window. Read back the resulting allocation. Have the qualified installer and application owner verify the intended point operation separately. If the readback or physical behavior disagrees with the plan, restore the approved configuration rather than trying additional undocumented combinations.\n\nVerification and evidence\nRetain the service-requirement response, available-I/O response, allocation worksheet and approved wiring reference together. Highlight the pin names that justified accepting one choice and rejecting another. Record device identity and software so a replacement-controller review does not inherit an unexamined allocation.\nInclude a desk-review rejection case: present two proposed allocations sharing a returned pin and ask the reviewer to identify the conflict before implementation. Record that exercise as a proposed planning test, not as evidence that a field wiring fault was created or that a door’s complete safety and security workflow passed.\nOfficial references\n\nI/O assignment service — 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: Check the physical pin overlap behind each logical I/O choice before assigning controller services. Build the allocation from actual service requirements and returned hardware information, rather than from convenient names.\n\n## Source fact: documented behavior\n\nAxis’s [I/O assignment service](https://developer.axis.com/vapix/physical-access-control/io-assignment-service/) explains that an I/O represents how a combination of controller physical pins can be used, rather than being identical to one physical pin.\n\nDifferent pins have different electrical properties, and when multiple I/O choices use the same physical pins, only one of those I/O choices can be used at a time.\n\nThe documented workflow configures the consuming services first, retrieves their requirements with axisio:GetIoUserInfoList, and retrieves available I/O and pin information with axisio:GetIoInfoList.\n\n## What the source does not establish\n\nDo not use a logical allocation worksheet as permission to wire an arbitrary device to a terminal. Require the exact controller and connected-device documentation for electrical design. Keep this API allocation check separate from egress approval, lock-power design and proof that a physical reader or door operates correctly.\n\n## Applicability questions\n\n- Which exact controller and installed software support the documented assignment service?\n\n- Which configured door or reader service requires each I/O, and in which mode?\n\n- Do proposed logical I/O choices share any returned physical pin names?\n\n- Has a qualified installer checked the electrical requirements against the approved wiring design?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends approving a pin-conflict worksheet before applying a new logical I/O assignment.\n\n- Work from an authorized controller configuration and the approved point schedule. List each consuming entity, its service identity, intended use and required mode. Read the service requirements after the relevant entities have been configured. Preserve identifiers rather than matching entities only by a repeated label such as reader or door. Mark any requirement that has not yet been resolved.\n\n- Retrieve the available logical I/O descriptions and expand each candidate into its physical pin list. For a proposed test case, compare two differently named choices that share a pin, if the device reports such a pair. Mark the pair as competing resources in the worksheet. Compare supported modes with each service requirement and refer electrical questions to the installer before making assignments.\n\n- Choose an allocation with no unresolved pin conflict and apply it only through the supported workflow in an approved test window. Read back the resulting allocation. Have the qualified installer and application owner verify the intended point operation separately. If the readback or physical behavior disagrees with the plan, restore the approved configuration rather than trying additional undocumented combinations.\n\n## Verification and evidence\n\nRetain the service-requirement response, available-I/O response, allocation worksheet and approved wiring reference together. Highlight the pin names that justified accepting one choice and rejecting another. Record device identity and software so a replacement-controller review does not inherit an unexamined allocation.\n\nInclude a desk-review rejection case: present two proposed allocations sharing a returned pin and ask the reviewer to identify the conflict before implementation. Record that exercise as a proposed planning test, not as evidence that a field wiring fault was created or that a door’s complete safety and security workflow passed.\n\n## Official references\n\n- [I/O assignment service](https://developer.axis.com/vapix/physical-access-control/io-assignment-service/) — 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-shared-physical-pins-before-assigning-axis-controller-i-o/", "url": "https://update.dsesecurity.com/updates/check-shared-physical-pins-before-assigning-axis-controller-i-o/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-29" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/check-shared-physical-pins-before-assigning-axis-controller-i-o/#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 shared physical pins before assigning Axis controller I/O", "item": "https://update.dsesecurity.com/updates/check-shared-physical-pins-before-assigning-axis-controller-i-o/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/check-shared-physical-pins-before-assigning-axis-controller-i-o/#article", "identifier": "https://update.dsesecurity.com/updates/check-shared-physical-pins-before-assigning-axis-controller-i-o/", "url": "https://update.dsesecurity.com/updates/check-shared-physical-pins-before-assigning-axis-controller-i-o/", "headline": "Check shared physical pins before assigning Axis controller I/O", "description": "Map logical Axis controller I/O to required modes and shared physical pins before assigning services.", "abstract": "Map logical Axis controller I/O to required modes and shared physical pins before assigning services. Do not treat different logical names as independent hardware resources.", "articleBody": "Bottom line: Check the physical pin overlap behind each logical I/O choice before assigning controller services. Build the allocation from actual service requirements and returned hardware information, rather than from convenient names.\nSource fact: documented behavior\nAxis’s I/O assignment service explains that an I/O represents how a combination of controller physical pins can be used, rather than being identical to one physical pin.\nDifferent pins have different electrical properties, and when multiple I/O choices use the same physical pins, only one of those I/O choices can be used at a time.\nThe documented workflow configures the consuming services first, retrieves their requirements with axisio:GetIoUserInfoList, and retrieves available I/O and pin information with axisio:GetIoInfoList.\nWhat the source does not establish\nDo not use a logical allocation worksheet as permission to wire an arbitrary device to a terminal. Require the exact controller and connected-device documentation for electrical design. Keep this API allocation check separate from egress approval, lock-power design and proof that a physical reader or door operates correctly.\nApplicability questions\n\nWhich exact controller and installed software support the documented assignment service?\nWhich configured door or reader service requires each I/O, and in which mode?\nDo proposed logical I/O choices share any returned physical pin names?\nHas a qualified installer checked the electrical requirements against the approved wiring design?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends approving a pin-conflict worksheet before applying a new logical I/O assignment.\n\nWork from an authorized controller configuration and the approved point schedule. List each consuming entity, its service identity, intended use and required mode. Read the service requirements after the relevant entities have been configured. Preserve identifiers rather than matching entities only by a repeated label such as reader or door. Mark any requirement that has not yet been resolved.\nRetrieve the available logical I/O descriptions and expand each candidate into its physical pin list. For a proposed test case, compare two differently named choices that share a pin, if the device reports such a pair. Mark the pair as competing resources in the worksheet. Compare supported modes with each service requirement and refer electrical questions to the installer before making assignments.\nChoose an allocation with no unresolved pin conflict and apply it only through the supported workflow in an approved test window. Read back the resulting allocation. Have the qualified installer and application owner verify the intended point operation separately. If the readback or physical behavior disagrees with the plan, restore the approved configuration rather than trying additional undocumented combinations.\n\nVerification and evidence\nRetain the service-requirement response, available-I/O response, allocation worksheet and approved wiring reference together. Highlight the pin names that justified accepting one choice and rejecting another. Record device identity and software so a replacement-controller review does not inherit an unexamined allocation.\nInclude a desk-review rejection case: present two proposed allocations sharing a returned pin and ask the reviewer to identify the conflict before implementation. Record that exercise as a proposed planning test, not as evidence that a field wiring fault was created or that a door’s complete safety and security workflow passed.\nOfficial references\n\nI/O assignment service — 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-29T17:41:32+00:00", "dateModified": "2026-10-29T17:41:37+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/check-shared-physical-pins-before-assigning-axis-controller-i-o/" }, "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-shared-physical-pins-before-assigning-axis-controller-i-o/#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 shared physical pins before assigning Axis controller I/O" }, "articleSection": [ "Access Control", "IT" ], "keywords": [ "Access Control", "IT", "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/" } ], "wordCount": 564, "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 — I/O assignment service", "url": "https://developer.axis.com/vapix/physical-access-control/io-assignment-service/" } } ] } }