Check Axis I/O circuit state against its active setting

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.

Source fact: documented behavior

Axis’s Input and outputs says the I/O check result uses 1 for a closed circuit and 0 for an open circuit.

The checkactive result instead depends on Output.Active for an output or Input.Trig for an input.

Its ActiveStateEnum defines open as active when floating and closed as active when grounded.

What the source does not establish

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.

Applicability questions

• Which physical connector and logical port identifier are being reviewed?
• Is that port configured as an input or an output?
• What circuit condition should represent the approved active event?
• What independent observation can distinguish the detector state from the API interpretation?

DSE recommendation: controlled next steps

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

DSE recommends a port worksheet linking direction, raw circuit state, active-state configuration and intended event meaning.

1. 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.
2. 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.
3. 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.

Verification and evidence

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.

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.

Official references

• Input and outputs — Axis Communications; official VAPIX documentation.

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