Supervised Door Contact Inputs: End-of-Line Resistors, Fault States and Commissioning

TL;DR

• Separate the door’s physical position from the electrical condition of its monitoring circuit.
• Confirm that the selected controller input supports the required supervision mode.
• Use the manufacturer’s resistor values, topology and placement instructions.
• Test normal door states and supported wiring fault states as separate events.
• Record the input configuration, event mapping and restoration result at handover.

Quick Answer

Supervised door contact inputs use a compatible monitoring circuit and controller configuration to distinguish expected contact states from certain wiring faults. End-of-line resistors help create the electrical conditions the input recognises, but values and wiring arrangements are product-specific. Select the controller, input mode and contact interface together, then follow the applicable connection diagram. During commissioning, verify normal door opening and closing, supported circuit-fault indications and recovery. A door-position signal does not prove that the latch or deadbolt is engaged, and adding resistors does not by itself create a complete or compliant access-control design.

Keep door position, lock status and circuit health separate

A door contact typically provides information about the leaf’s position relative to its sensor arrangement. A lock monitor may report another condition, such as a component position defined by that lock’s documentation. A controller combines inputs with its operating logic. Buyers should not collapse all of these into one statement that the door is secure.

For example, a controller can receive an expected closed-door signal without having evidence that every locking component is engaged. Equally, a wiring fault can make a controller’s displayed state unreliable even though the leaf itself has not moved. Define which physical condition each input represents and which circuit conditions the system can distinguish.

Start the hardware discussion with the TOPTEK electronic lock and access control range. Keep the proposed lock function, door contact and controller input on separate lines in the schedule. That makes it easier to identify which supplier must confirm each interface.

What supervision adds to a contact input

A simple contact input and a supervised input are not automatically interchangeable modes. In a supervised arrangement, the controller interprets electrical conditions within supported ranges. A correctly selected resistor network can allow more conditions to be distinguished than a basic open-or-closed contact connection. The supported states and thresholds depend on the hardware and its configuration.

Axis describes hardware-dependent ranges and supported states in its Supervised I/O documentation. Its documentation is a useful example of why the chosen controller matters. It should not be read as a universal wiring specification or as evidence that a TOPTEK lock includes that controller functionality.

Ask the integrator to identify what the system will report for each intended condition. Some configurations distinguish normal contact transitions and specific circuit faults; others may expose fewer states or different event names. The commissioning sheet should use the actual controller terminology and explain the physical or electrical condition behind each label.

Supervision also has a defined boundary. Identify the part of the circuit being monitored, including the location of the resistor network and any intermediate connections. Do not assume that every cable section is supervised because resistors appear somewhere in a drawing.

Select the contact, input and resistor arrangement together

Confirm whether the proposed door sensor provides the electrical interface the controller expects. A passive switch contact, a powered sensor and an electronic output can require different treatment. Obtain the applicable diagrams rather than guessing from wire colours or the presence of two terminals. The contact’s normal state should be described with its reference condition, such as the installed door being closed.

Next identify the specific controller input and its supported supervision setting. Record the controller model, hardware version where relevant and configuration reference. Select resistor values and tolerance requirements from its instructions. A value used successfully on another site is not a reason to reuse it on a different input design.

The AXIS A1610 supervised-input instructions show different supported connection arrangements. Those arrangements apply to that product. For another controller, obtain its own diagrams and do not copy the values, pin assignments or cable limits across platforms.

Place and protect components as instructed for the intended monitoring boundary. Record the actual resistor location on the as-built drawing. If resistors are fitted near the panel merely for convenience, ask whether the field cable has the protection the design intended. Confirm the answer through the correct diagram and the agreed commissioning test.

Use a state matrix before writing the test script

This is a planning matrix, not an instruction to short live terminals. A qualified integrator should define safe simulation methods for the actual input, isolate equipment where required and coordinate the test with the operator. Avoid improvised tests that could damage an output or unintentionally operate another connected system.

For each row, distinguish three observations: the physical condition at the opening, the input condition reported by the controller and the event shown to the operator. A correct input reading does not prove that the software event is mapped to the right door or delivered to the right destination.

Commission the complete path to the operator

Begin by checking the as-built circuit against the selected diagram and saved configuration. Confirm terminal identities, resistor arrangement, sensor reference state and the opening name. Check that the event label describes the intended door, especially where many similar inputs are commissioned together.

Observe normal opening and closing before introducing any approved fault simulation. Record the expected and actual state separately. If the normal signal is unstable, investigate the physical sensor alignment, connection quality and relevant settings before changing fault thresholds. Do not widen limits simply to make an unexplained symptom disappear.

Carry out the agreed circuit-fault tests and verify the full reporting path. Check that the controller identifies the supported condition, that the software shows the expected event and that the operator can distinguish a wiring problem from ordinary door use. Where the design requires notifications, verify those notifications under the approved test plan.

Restore the circuit and confirm both normal door operation and event recovery. Save the final configuration after approved changes, and identify any differences from the original drawing. A test is incomplete if the expected alarm appears but the system is left in a fault, bypass or temporary test condition.

Review the physical cable route and related connections alongside the electronic mortise lock wiring guide. Keep power-circuit requirements and monitored contact requirements distinct, even when they pass through the same opening.

Common mistakes that weaken the monitoring result

One mistake is assuming that every input on a controller has the same capabilities. A board may offer different input types, so identify the exact terminal and supported mode. Another is copying resistor values from a previous installation without recording the source. Both errors can produce a circuit that appears functional during a limited check but does not report the intended fault states.

A third mistake is confusing a door-open indication with a cable interruption. The purpose of the state matrix is to make that distinction visible where the selected hardware supports it. If the design cannot distinguish a condition the project requires, resolve the design gap instead of renaming an event to suggest greater capability.

Also avoid combining several doors under an ambiguous label. Even a correctly supervised circuit is less useful if facilities staff cannot locate the opening. Retain consistent door identifiers across drawings, controller inputs, software events and maintenance records.

TOPTEK scope and the information an RFQ needs

The TOPTEK motorized mortise lock product reference can help start a lock configuration enquiry. Request the current model-specific interface information and identify the controller separately. Do not assume a lock includes a supervised door contact, a particular monitoring output or a universal resistor arrangement.

Why TOPTEK? A useful enquiry connects the lock requirement with drawings and the relevant manufacturing and quality management information. Ask for the evidence needed for the exact supplied product. System-level supervision, software mapping and commissioning remain defined by the chosen equipment and the agreed integration scope.

• Identify each opening and the physical condition each input must report.
• List the lock, sensor, controller and proposed input terminal.
• Attach the controller’s supported supervision diagram and configuration reference.
• Show cable routing, joints and the intended resistor location.
• State the required normal, fault and recovery events.
• Identify who designs, installs, commissions and maintains the circuit.
• Request the model-specific interface documents and an agreed acceptance record.

For repeat projects, keep the accepted configuration as a controlled reference. A replacement controller, sensor or board revision should trigger a review of the relevant circuit and settings. Repeatability comes from a documented combination, not from keeping an unlabeled bag of resistors in the installer’s van.

Frequently asked questions

Does a door contact prove that a lock is secure?

No. It reports the condition defined by its sensor arrangement, commonly door position. Lock engagement requires the appropriate separate evidence or monitoring interface.

Can any controller input be supervised?

No. Confirm that the specific input supports the required mode and follow the controller’s configuration and wiring instructions.

Are end-of-line resistor values universal?

No. Values, tolerances and connection arrangements depend on the selected input hardware and its supported configuration.

Should commissioning include wiring fault tests?

Include the fault conditions required by the design and supported by the equipment, using manufacturer-approved methods and a controlled restoration procedure.

What should be retained at handover?

Keep the as-built circuit, component identities, resistor location and values, controller settings, event mapping, test results and confirmation of normal operation after restoration.

Request an interface review or system quotation

If the monitoring boundary is unclear, start with the circuit diagram and the required state matrix. For a formal lock and hardware enquiry, add opening quantities, the selected interfaces and document requirements through TOPTEK’s commercial locks and access control enquiry. A well-defined supervised input gives operators useful information because its physical meaning, electrical limits and reporting path have all been checked.