Low-Voltage Field Reference • Wire & pinout diagram
Door Strike Power and Dry-Contact Relay Wiring Diagram
A dry relay contact does not supply lock power; it opens or closes a separate listed power circuit. The correct NO/NC choice depends on hardware function, fail mode, egress arrangement and the approved sequence—not on a generic diagram alone.
Direct answer
door strike dry contact wiring diagram: the practical answer
A dry relay contact does not supply lock power; it opens or closes a separate listed power circuit. The correct NO/NC choice depends on hardware function, fail mode, egress arrangement and the approved sequence—not on a generic diagram alone.
For a working contractor, the value of this diagram is its ability to turn a wiring convention into an orientation-controlled installation record. Use the sequence scope → orientation → conductors → termination → test. Never treat an editorial drawing as a manufacturer terminal diagram.
What this changes in the design package
Door Strike Power and Dry-Contact Relay Wiring Diagram should change at least one controlled project record. On a floor plan, identify the physical location or route affected by lock voltage and inrush/current and power-supply and relay ratings. On the riser or signal-flow drawing, show how the selected equipment, pathway, power and communications relationships support the intended outcome. In the schedule, preserve the exact data needed to buy, configure, install and test the system.
Plan
Show the device, route, zone or interface in context. Use stable IDs rather than relying on a symbol alone, and flag any assumption that can change quantity or performance.
Riser or schematic
Show origin, destination, intervening equipment, shared infrastructure and interface responsibility. A diagram should expose relationships the floor plan cannot show clearly.
Schedule
Record fail-safe or fail-secure function, egress and fire-interface requirements, voltage drop and conductor size and surge suppression requirement where they can be reviewed and revised without redrawing the entire plan.
Proposal
State the verified design basis, named allowances, exclusions, owner/IT/electrical dependencies, testing method and the event that triggers a change order.
Field method
A repeatable diagram workflow
Start with the exact product and the viewing orientation. Work from documented terminals and conductor identities, then prove the installed result with the appropriate test.
- 1. write the normal, access, fire and power-loss states.
- 2. measure voltage at the lock under load.
- 3. test relay contact behavior with power isolated.
- 4. verify every release path and event.
After the final step, repeat the original operating scenario. A correction is not complete until the system passes the required function, the drawing and schedule match the installed condition, and the handoff record identifies what changed.
Decision and evidence table
| Question | Evidence to collect | Where to record it | Acceptance signal |
|---|---|---|---|
| What controls lock voltage and inrush/current? | write the normal, access, fire and power-loss states; use exact model, reading, setting, photo or log evidence. | door power diagram, keyed to the same device/cable/door/zone ID. | The reviewed record and field condition agree, with no unresolved assumption hidden as fact. |
| What controls power-supply and relay ratings? | measure voltage at the lock under load; use exact model, reading, setting, photo or log evidence. | sequence of operations, keyed to the same device/cable/door/zone ID. | The reviewed record and field condition agree, with no unresolved assumption hidden as fact. |
| What controls fail-safe or fail-secure function? | test relay contact behavior with power isolated; use exact model, reading, setting, photo or log evidence. | load and voltage-drop record, keyed to the same device/cable/door/zone ID. | The reviewed record and field condition agree, with no unresolved assumption hidden as fact. |
| What controls egress and fire-interface requirements? | verify every release path and event; use exact model, reading, setting, photo or log evidence. | acceptance-state matrix, keyed to the same device/cable/door/zone ID. | The reviewed record and field condition agree, with no unresolved assumption hidden as fact. |
Keep evidence close to the decision it supports. A screenshot without an equipment ID, a cable test without the cable identifier, or a code note without edition and jurisdiction is difficult to audit later.
Technical deep dive
Six controls that make door strike wiring defensible
1. lock voltage and inrush/current
reconcile lock voltage and inrush/current before the team commits dry contact relay to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to write the normal, access, fire and power-loss states. Compare the evidence with the intended access control outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for feeding lock power from an unrated controller output, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the door power diagram. Tie it to door strike wiring and dry contact relay with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
2. power-supply and relay ratings
challenge power-supply and relay ratings before the team commits NO NC COM terminals to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to measure voltage at the lock under load. Compare the evidence with the intended access control outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for selecting NO or NC by habit, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the sequence of operations. Tie it to door strike wiring and NO NC COM terminals with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
3. fail-safe or fail-secure function
preserve fail-safe or fail-secure function before the team commits fail safe fail secure to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to test relay contact behavior with power isolated. Compare the evidence with the intended access control outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for placing suppression incorrectly, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the load and voltage-drop record. Tie it to door strike wiring and fail safe fail secure with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
4. egress and fire-interface requirements
establish egress and fire-interface requirements before the team commits lock power supply to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to verify every release path and event. Compare the evidence with the intended access control outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for ignoring shared return or ground paths, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the acceptance-state matrix. Tie it to door strike wiring and lock power supply with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
5. voltage drop and conductor size
measure voltage drop and conductor size before the team commits access control door sequence to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to write the normal, access, fire and power-loss states. Compare the evidence with the intended access control outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for feeding lock power from an unrated controller output, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the door power diagram. Tie it to door strike wiring and access control door sequence with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
6. surge suppression requirement
trace surge suppression requirement before the team commits door strike wiring to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to measure voltage at the lock under load. Compare the evidence with the intended access control outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for selecting NO or NC by habit, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the sequence of operations. Tie it to door strike wiring and door strike wiring with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
Field-capture worksheet
Before leaving the site, collect enough evidence that another qualified person can reconstruct the decision. Start with the site, floor, room and stable asset ID. Record the date, technician and current drawing revision. Photograph the overall context before taking close-ups, and place a readable label or reference in the image when practical.
- Identity
- Exact manufacturer, model, firmware or listing, terminal names, cable ID, panel/port/zone/door address, and the related plan symbol.
- Observed state
- What the user reported, what the technician reproduced, timestamps, LEDs or messages, logs, settings and whether the condition is continuous or intermittent.
- Measured state
- Applicable voltage, current, resistance, optical level, cable result, protocol status, signal format or environmental condition, including the instrument and test boundary.
- Change control
- The one change made, authorization, before/after evidence, temporary workaround, regression checks and any effect on other devices or shared infrastructure.
For this topic, call out lock voltage and inrush/current, fail-safe or fail-secure function and voltage drop and conductor size. Use the vocabulary door strike wiring, dry contact relay, NO NC COM terminals consistently so the field note, drawing, schedule and proposal can be found together.
Worked field example
From an uncertain condition to a controlled record
A design-build contractor receives a report involving door strike wiring. The available plan shows a symbol, but it does not identify lock voltage and inrush/current, power-supply and relay ratings or fail-safe or fail-secure function. Instead of pricing or repairing from the incomplete symbol, the team opens a single issue record and assigns the affected equipment, cable or location a stable ID.
The technician collects the current settings, model information, photos and measured state. The designer compares that evidence with the selected equipment documentation and the current authoritative sources listed below. The estimator separates verified scope from allowances. The project manager records who owns any external dependency, such as an electrical circuit, network policy, door hardware condition, AHJ decision or owner-furnished device.
The corrected package includes the door power diagram, sequence of operations and load and voltage-drop record. The team then repeats the operating test under the same conditions that produced the original question. That closed loop turns dry contact relay and NO NC COM terminals from search terms into traceable project decisions instead of isolated notes.
Common failure modes—and why they happen
Failure 01
feeding lock power from an unrated controller output
This shortcut removes context from the decision. Correct it by returning to the project-specific input, documenting the selected basis, and repeating the affected acceptance test.
Failure 02
selecting NO or NC by habit
This shortcut removes context from the decision. Correct it by returning to the project-specific input, documenting the selected basis, and repeating the affected acceptance test.
Failure 03
placing suppression incorrectly
This shortcut removes context from the decision. Correct it by returning to the project-specific input, documenting the selected basis, and repeating the affected acceptance test.
Failure 04
ignoring shared return or ground paths
This shortcut removes context from the decision. Correct it by returning to the project-specific input, documenting the selected basis, and repeating the affected acceptance test.
When a failure involves regulated life safety, egress, listing, energized work, public-safety radio, or code interpretation, stop at the boundary of your authorization. Escalate to the responsible qualified party and preserve the condition and evidence.
Minimum contractor deliverables
A useful answer survives the handoff from design to estimating, proposal, installation and closeout. At minimum, create the following:
- door power diagram.
- sequence of operations.
- load and voltage-drop record.
- acceptance-state matrix.
Each deliverable should show the project, revision, author, review status and the identity of the system element it controls. If a value is not verified, label it as an assumption, allowance, pending submittal or owner/AHJ decision. Do not let a blank field become an accidental commitment.
How to carry the answer into scope and proposal language
Describe the outcome first: what the customer will receive, where it applies and how it will be tested. Then name the basis used for door strike wiring, including the controlling drawing revision and selected equipment data. Include the labor and documentation needed to produce door power diagram and sequence of operations.
Separate dependencies explicitly. Examples include usable owner drawings, accessible ceilings, working branch power, network addressing and policy, compatible owner equipment, door hardware readiness, permits, shutdown windows, AHJ review and access to occupied areas. If one of those facts is unknown, write an allowance or qualification and define how the price changes when the fact is confirmed.
Finish with acceptance: identify who witnesses the test, what evidence is retained and which result constitutes completion. This makes the page commercially useful without turning it into a product pitch.
Commissioning, handoff and future service
Commissioning should prove the designed function, not simply show that equipment turns on. Run the accepted scenario, an expected failure or trouble state, recovery, and any interface that crosses to network, electrical, fire alarm, door hardware, controls or owner systems. Save results against stable IDs and the approved revision.
At handoff, give the owner the door power diagram, sequence of operations, final configuration, approved substitutions, warranties and the contact path for unresolved external responsibilities. Remove default credentials and temporary access where applicable. Explain which changes can invalidate the result—for example a new firmware release, equipment replacement, changed speaker tap, moved camera, added cable, revised AHJ direction or modified switch policy.
Future service begins by comparing the current condition with this accepted baseline. If the record is missing, recreate it before making broad changes. That discipline reduces repeated troubleshooting, protects proposal scope, and lets the next technician distinguish a design issue from a later operational change.
Frequently asked questions
What should I verify first?
Start with lock voltage and inrush/current and power-supply and relay ratings. Establish the exact product, project location and current system state before applying a diagram or changing configuration.
Can I use this page as a construction detail?
Use it as an editorial planning and verification aid. Convert it into a project detail only after reconciling the manufacturer instructions, adopted requirements, approved submittals and responsible professional or AHJ direction.
What belongs in the closeout package?
Include door power diagram, sequence of operations, load and voltage-drop record, acceptance-state matrix, plus test evidence, deviations, final settings and the identity of the person or authority that accepted the result.
What should I read next?
Continue with OSDP Access Control Explained: Wiring, Supervision and Secure Channel, Wiegand Reader Interface: Signals, Limitations and Upgrade Planning, Request to Exit (REX) in Access Control: Function and Documentation, Access-Control Composite Cable Color Guide: How to Document Conductors Safely and the Access Control design software resource.
Authoritative references and how to use them
These links are starting points for current primary-source information. Confirm the current edition, product revision, publication status, jurisdiction and applicability. Accessed for this release on 2026-08-08.
- 2024 IBC means of egress — use the source to verify terminology, conformance, published requirements or manufacturer-specific behavior; do not substitute this summary for the controlling document.
- Security Industry Association OSDP — use the source to verify terminology, conformance, published requirements or manufacturer-specific behavior; do not substitute this summary for the controlling document.
- UL Standards and Engagement — use the source to verify terminology, conformance, published requirements or manufacturer-specific behavior; do not substitute this summary for the controlling document.