Commercial security product guide

Von Duprin QEL, RX and Electrified Exit Devices

Options across the Von Duprin exit-device families include Quiet Electric Latch Retraction (QEL), request-to-exit (RX), latch monitoring (LX), alarms and specialized trim. Which of them can be had, and which will work together, depends on the series, the device type, the fire rating and the combination itself, so schedule the whole opening before any order or retrofit is placed.

KSEDCO supplies, installs, configures, maintains, repairs, and supports these systems across Georgia. Discuss a site or service request

A single feature does not carry the system

Match devices, software, licensing, infrastructure, retention, integrations and support to the operating requirement before finalizing the system engineering.

Device architectureRim, surface vertical rod, concealed vertical rod, mortise or other listed exit-device type.
QEL roleMotorized latch retraction for compatible device families and approved operating sequences.
RX/LX rolesTouchpad request-to-exit versus latch-state monitoring, selected from the actual alarm requirement.
Power and controlApproved power supply, wire, control input, fire behavior and simultaneous-load calculation.

Survey the device and options

Start at the opening itself: the series specified or already installed, device type and length, the door and frame, trim, dogging, fire label, latch condition and vertical-rod geometry. Establish whether this is panic hardware or fire exit hardware, and keep the required mechanical egress intact.

Nothing about QEL, RX, LX, delayed egress, alarms or trim should be assumed from memory; the current Von Duprin option matrix is the reference. Certain combinations and retrofit kits depend on the series and the date, so read the device markings and manufacturing information off the bar before treating it as convertible.

Discovery needs to 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.

  • Which series, which device type
  • Fire/panic label
  • What options it already accepts
  • Mechanical condition

QEL, monitoring, trim and power system engineering

Fix the requirement first: latch retraction for push-pull operation, request-to-exit signaling, latch monitoring, outside-trim control, or a local alarm. RX and LX observe different things and cannot substitute for each other. Program the access-control input and the alarms against the switch function actually present.

Power supply and control module selection comes down to four numbers: inrush, holding current, cable distance, and how many devices operate together. Use approved parts. Fire-alarm behavior, scheduling, remote dogging and lockdown belong in the design only where the listed opening and the approved sequence permit them.

Verify the exact model and the software it supports before ordering, since names that look similar can hide different capacity, licensing or integration limits. Coordinate the rest alongside it: network addressing, PoE or low-voltage power, pathways, environmental ratings, mounting, the door or camera interfaces and backup power.

  • What QEL is for
  • What RX reports, what LX reports
  • Trim, and how power transfers
  • Simultaneous load on the supply
Von Duprin electrified option roles
OptionPurposeConfirm
QELQuiet latch retractionSeries, rating and power
RXTouchpad request to exitAlarm/input logic
LXLatch state monitoringDevice compatibility
Electrified trimControlled outside entryFunction and power transfer

Field Installation, adjustment and access integration

The manufacturer template and the correct kit govern both new field installation and retrofit. Rods, latches, strikes, center case, touchpad and closer all get adjusted while the option is still unpowered. Route wiring away from moving parts and take it through 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 needs to 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 needs to come from the manufacturer portal after compatibility and release-note review, with rollback or recovery prepared before change.

  • Listed kit, correct template
  • Rod/latch adjustment
  • Does mechanical egress still work
  • Mapping into controller and alarm

Acceptance, rating records and preventive maintenance

Deliver device and kit part numbers, series, function, trim, power supply, control point, transfer method, switch mapping, rating and test results. Keep official field installation and option documents with the protected opening schedule.

Fasteners, touchpad, rods, latches, strikes, power transfer, wiring and retraction timing all get inspected. Any change to the door, controller, supply or fire interface means re-testing alarm and life-safety behavior.

Acceptance needs to 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.

  • Schedule of openings and options
  • Power/control record
  • Official documents on file
  • Function tested on a schedule

Our approach from survey to handover

The final system engineering depends on site conditions, existing systems, client policies and the selected manufacturer or platform.

Discover

We write down people, assets, workflows, risks and installed systems.

System Engineering

Only supported architecture, devices, licenses and integrations get chosen.

Install

Staging, labeling and commissioning happen under change control.

Validate

Operating scenarios are run, and lifecycle records handed over.

Information to gather before system engineering

Good decisions are easier when the security engagement team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.

  • Day-to-day use and response steps
  • Software matched to the device
  • Interfaces: power, network, physical
  • Identity, cybersecurity and license terms
  • Support and lifecycle after acceptance

Questions we hear often

These are common engineering assessment questions. A site-specific answer needs to be confirmed during discovery and system engineering.

Can RX tell you the latch is secure?

No. What RX generally reports is touchpad operation, so latch or door state needs the monitoring appropriate to it.

Will QEL retrofit onto any exit device?

No. The series, device type, age, rating and approved kit all have to be verified.

Can QEL stand in for mechanical egress?

No. Mechanical egress that is required has to keep working under the approved conditions.

Why does retraction get unreliable?

Wiring, voltage drop, incorrect power, adjustment at the rod or latch, incompatible kits and mechanical trouble in the door are the common causes.

Software, firmware and technical documents stay where the manufacturer publishes them, on the official website. KSEDCO does not host copies of firmware files.

Discuss a commercial security engagement

Tell us about the doors, buildings, users, existing equipment, operational requirements and desired completion date. We will help organize the right discovery and system engineering conversation.

Contact KSEDCO