Von Duprin QEL, RX and Electrified Exit Devices
Von Duprin exit-device families support options such as Quiet Electric Latch Retraction (QEL), request-to-exit (RX), latch monitoring (LX), alarms and specialized trim. Availability and compatibility vary by series, device type, fire rating and combination, so the complete opening must be scheduled before ordering or retrofitting.
Select the complete system, not one headline feature
Match devices, software, licensing, infrastructure, retention, integrations and support to the operating requirement before finalizing the design.
Exit-device and electrified-option survey
Identify the existing or specified series, device type, length, door and frame, trim, dogging, fire label, latch condition and vertical-rod geometry. Confirm whether the opening is panic hardware or fire exit hardware and preserve required mechanical egress.
Use the current Von Duprin option matrix for QEL, RX, LX, delayed egress, alarms and trim. Some option combinations or retrofit kits are series- and date-dependent. Record device markings and manufacturing information before assuming an existing bar can accept a conversion.
Discovery should identify protected areas, users, schedules, response procedures, privacy expectations, existing equipment and the party who will administer the finished system. Product claims only become useful after they are translated into measurable coverage, capacity, availability and response requirements.
- Series and device type
- Fire/panic label
- Existing option compatibility
- Mechanical condition
QEL, monitoring, trim and power design
Define whether the system needs latch retraction for push-pull operation, request-to-exit signaling, latch monitoring, outside-trim control or local alarm. RX and LX are not interchangeable observations. Coordinate the access-control input and alarm programming with the actual switch function.
Select the approved power supply and control modules for inrush, holding current, cable distance and number of devices operating together. Include fire-alarm behavior, schedule, remote dogging or lockdown only when allowed by the listed opening and approved sequence.
Coordinate network addressing, PoE or low-voltage power, pathways, environmental ratings, mounting, door or camera interfaces and backup power. Verify exact model compatibility and supported software before ordering; similar product names can conceal different capacity, license or integration limits.
- QEL operating purpose
- RX versus LX signal
- Trim and transfer method
- Supply and simultaneous load
| Option | Purpose | Confirm |
|---|---|---|
| QEL | Quiet latch retraction | Series, rating and power |
| RX | Touchpad request to exit | Alarm/input logic |
| LX | Latch state monitoring | Device compatibility |
| Electrified trim | Controlled outside entry | Function and power transfer |
Installation, adjustment and access integration
Install or retrofit with the manufacturer template and correct kit. Adjust rods, latches, strikes, center case, touchpad and closer before powering the option. Keep wiring clear of moving parts and use the approved power transfer.
Test mechanical egress with power present and absent, authorized entry, QEL retract and relatch, RX or LX reporting, schedule, alarms, fire input and outside trim. Repeated cycles should not drag rods, leave latches partially retracted or require excessive touchpad force.
Use named administrators, least privilege and multifactor authentication where supported. Establish backup, update, health-monitoring and escalation ownership. Firmware and software should come from the manufacturer portal after compatibility and release-note review, with rollback or recovery prepared before change.
- Template and listed kit
- Rod/latch adjustment
- Mechanical egress tests
- Controller and alarm mapping
Acceptance, rating records and maintenance
Deliver device and kit part numbers, series, function, trim, power supply, control point, transfer method, switch mapping, rating and test results. Keep official installation and option documents with the protected opening schedule.
Inspect fasteners, touchpad, rods, latches, strikes, power transfer, wiring and retraction timing. Re-test alarm and life-safety behavior after door, controller, supply or fire-interface changes.
Acceptance should test normal use, denied or alarm conditions, loss of network or power, notification, audit history and administrator recovery. Deliver protected configuration records, licenses, serials, diagrams, test evidence, support links and clearly owned exceptions.
- Opening and option schedule
- Power/control record
- Official documents retained
- Periodic functional testing
How we plan and deliver the work
The final design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Discover
Document people, assets, workflows, risks and existing systems.
Design
Select the supported architecture, devices, licenses and integrations.
Install
Stage, label and commission through controlled changes.
Validate
Exercise operating scenarios and deliver lifecycle records.
Information to gather before design
Good decisions are easier when the project team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.
- Operational use cases and response
- Device and software compatibility
- Power, network and physical interfaces
- Licensing, identity and cybersecurity
- Acceptance, support and lifecycle
Frequently asked questions
These are common planning questions. A site-specific answer should be confirmed during discovery and design.
Does RX prove the latch is secure?
No. RX generally reports touchpad operation; use the appropriate latch or door monitoring for the required state.
Can QEL be added to every exit device?
No. Verify series, device type, age, rating and approved kit compatibility.
Should QEL replace mechanical egress?
No. Required mechanical egress must remain functional under the approved conditions.
What causes unreliable retraction?
Incorrect power, voltage drop, wiring, rod or latch adjustment, incompatible kits and mechanical door problems are common causes.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Discuss a commercial security project
Tell us about the doors, buildings, users, existing equipment, operational requirements and desired completion date. We will help organize the right discovery and design conversation.