Separate Axis current-loop threshold alarms from wiring faults

Bottom line: Use separate response paths for an out-of-range process measurement and a current-loop diagnostic fault. Preserve what the interface actually reports before translating both into a generic sensor alarm.

Source fact: documented behavior

Axis’s Current loop input API describes an optional interface for 4 to 20 mA sensors and cautions that it might not be available on every product.

The threshold alarm becomes true when a sensor reading crosses a configured warning or critical threshold, while the fault event becomes true when a hardware or wiring issue is detected on the loop.

The status object reports sensor data and diagnostic results; values update every 100 milliseconds, but loopState and thresholdState can include a validation delay.

What the source does not establish

Do not infer a safety-rated instrument function, immediate fault indication or universal sensor compatibility from this API description. Require the exact sensor and Axis product documentation before planning electrical work. Keep this article’s event-class distinction separate from an approved process-control or life-safety design, and do not short live wiring to improvise a test.

Applicability questions

• Does the exact Axis product expose the optional current-loop interface?
• Which sensor, engineering unit and threshold configuration belong to the monitored process?
• Which operator response should follow a measurement threshold versus a loop diagnostic condition?
• What qualified personnel and manufacturer-approved method can perform any permitted stimulus test?

DSE recommendation: controlled next steps

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

DSE recommends preserving threshold and loop-diagnostic classifications through monitoring, notification and restoration checks.

1. Read the target device’s configuration and status through the supported interface. Map each sensor identity to the approved engineering unit and threshold plan. Write separate proposed operator cases: a process value outside its approved warning range, and a diagnosed loop problem. Label them as test scenarios, not observed incidents. Assign the intended owner and escalation for each before configuring a common notification destination.
2. Build the event mapping so the reported classification and state details remain available to the operator. Keep the original sensor identity and observation time with the notification. For a desk exercise, give the reviewer one threshold case and one wiring-diagnostic case and require different dispositions. Avoid translating every input into the same process-value conclusion merely because both require attention.
3. Where physical verification is authorized, have qualified personnel select a supported test method appropriate to the exact sensor and installation. Protect normal operations and record the stimulus, immediate readings, eventual state changes and recovery. Allow for the documented validation-delay boundary when evaluating timing, without inventing an acceptable delay. Restore the approved configuration and verify that both the device and consuming system reflect the final condition.

Verification and evidence

Retain the sensor mapping, approved threshold plan, sanitized configuration and status, event records and operator disposition for each proposed case. Keep the stimulus time distinct from measurement, state-change and notification times. Mark missing observations or uncertain classifications explicitly so a numeric reading does not stand in for a confirmed diagnostic result.

Ask a second reviewer to explain why each observed condition was routed as a process threshold or a loop issue. Record the actual timing and any remaining gap against the separately approved requirement. This proposed check does not certify an instrument function, establish a fault-detection deadline or report completed electrical testing.

Official references

• Current loop input API — 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.