Almost every control a driver reaches for on a truck or bus door — raising a window, locking the cab, aiming and heating the mirrors — runs through one small controller sitting behind the door trim. It is easy to overlook next to the engine ECU or the instrument cluster, but the power-window and door control module is the part that turns a switch press into a motor moving, and it is where most cab-comfort sourcing decisions are actually made.
This guide is the version of that conversation we have with OEM engineering buyers when a cab program is scoping its door electronics, written down. It assumes you know what a CAN bus and a BCM are, and that your program is deciding how to drive windows, central locking and mirrors on a new cab — whether that is a 24 V heavy truck, a 12 V light-commercial platform, or a bus where the door functions are shared across a body network.
1. What a power-window and door control module does
A power-window and door control module is the controller for the cab-door comfort group. It reads the switch inputs the driver operates, drives the motors and actuators those switches command, and — on a networked cab — reports the door state to the body network and takes commands back from it. On a commercial vehicle the module is usually responsible for some or all of:
- Electric windows. Up and down drive on the door windows, with one-touch auto-up / auto-down and the switch-held manual mode, and the master-side cross-control that lets the driver work the passenger window.
- Central locking. Lock and unlock drive on the door actuators, taking commands from the in-cab switch, the mechanical key barrel and — where fitted — the RKE remote fob, with door-state and lock-state feedback.
- Mirror adjust and heat. Four-axis adjust (up / down / left / right) on the left and right mirrors through a shared selector, plus the mirror-defogger heat drive for cold-weather de-ice.
- Anti-pinch, where required. Torque or current monitoring on the up stroke that reverses the window when it detects an obstruction — a distinct certification scope, not a default on every module.
- Network and housekeeping. A CAN link to the body backbone (and often a LIN line to a switch panel), plus self-diagnosis, fault-flag storage and the protection logic that guards each motor drive.
On the Youlai catalogue this role is filled at several tiers. The EBX‑2163 platform DCM owns window, mirror, central-locking and RKE on one 24 V controller; the EBX‑2315 is a dedicated 24 V window, mirror and central-locking controller; the EBX‑2206 is the 12 V anti-pinch window controller; and the driver touches it all through a switch panel such as the EDK‑908 door & window control switch on a 24 V cab — or, where the door only needs its windows and central lock, the leaner EDK‑914 LIN power-window switch — while a 12 V car or new-energy platform uses the TDK‑2202/2203 power-window & central-lock switch. Which tier fits is the sourcing decision, covered in sections 3 and 4.
2. How the switch, controller and motors connect
The door comfort group is a three-stage chain: the switches the driver touches, the controller that decides what to do, and the motors and actuators that move. Understanding that chain is what lets you tell a switch-panel question from a control-module question later.
The switch panel
The driver's-door master switch — a panel such as the EDK-908 — gathers the window-lift, central-lock and mirror keys into one unit at the armrest. It carries a LIN data line so it can sit on the cab's low-speed network, and it also has direct outputs, so on a simple local harness it can switch some loads itself. Its job is to turn a positive, tactile key press (the EDK-908 uses a 5 ± 1.5 N action qualified past 50,000 operations) into a clean signal.
The control module
The controller reads those switch inputs and drives the loads. This is where the current actually flows: a drive stage for each window motor, the lock and unlock drive for the central-locking actuators, the four-axis mirror drives and the mirror-heat channel. It is also where the protection lives — the EBX-2163 carries a four-fold set (over-voltage, over-current, short-circuit, over-temperature) on each high-current channel, which matters most on the window and lock motors where stall current is a routine event. On a networked cab the module publishes door, lock and window state onto CAN and takes the central-lock and cabin-state commands back.
The motors and the feedback loop
The window regulators, lock actuators and mirror motors are the output. On a module with anti-pinch, this stage also closes a feedback loop: the controller watches motor torque or current on the up stroke and reverses out when it sees the obstruction signature. That loop is why anti-pinch is a controller function, not a switch function — the switch cannot know a window is jammed, but the controller driving the motor can. The drive stage underneath it — a reversing bridge, stall current and current feedback — is the same one behind every actuator on the vehicle that has to move both ways, not only the door group, and is worked through in the DC motor & actuator control guide.
3. Where the function lives: dedicated module, BCM or switch panel
The first real sourcing decision is not which part number, but where the window / lock / mirror function should physically live. There are three patterns, and picking the wrong one shows up later as either a redesigned BCM or an over-built controller.
| Pattern | Best fit | Reference part |
|---|---|---|
| Dedicated module — the door group on its own controller | A cab that already has a separate BCM, or that wants the window / lock / mirror drive isolated on one box close to the door harness. Keeps the motor-drive and protection off the main BCM. | EBX‑2315 — 24 V, single 36-pin housing, 4-window drive, central locking, mirror adjust + defogger. |
| Integrated into the BCM — the door group as part of a wider controller | A program that wants one ECU to own the whole body group (lighting, locking, windows, mirrors, RKE) so the door functions stop needing a separate box and harness. | EBX‑2163 platform DCM, or a full body module such as the heavy-truck BCM. |
| Switch panel with local outputs — the driver controls, minimal logic | A simpler cab where the door master switch drives some loads directly and only needs a LIN line to report to a body-adjacent controller, rather than a full drive-and-protect module. | EDK‑908 door & window control switch (LIN + direct outputs). |
The integrated route is cleaner when one ECU can reasonably own the body group, because every function on that board stops needing a CAN message and a connector to talk to its neighbour. The dedicated route is right when the main BCM was never built for motor drive or a smart key: adding a controller such as the EBX-2315 keeps the existing BCM and lets the door module own the window, lock and mirror drive on its own board, reporting over one CAN link. The switch-panel route fits a cab that only needs the driver controls plus a low-speed report, where a full module would be over-built.
4. 12 V, 24 V and anti-pinch: choosing the tier
Once you know where the function lives, two parameters decide the exact part: the system voltage, and whether anti-pinch with self-learning is mandatory. Those two together separate the Youlai window / door tiers cleanly.
| Model | System | Scope | Anti-pinch | Interface |
|---|---|---|---|---|
| EBX‑2206 | 12 V (9–16 VDC) | Dedicated 4-door window controller | Yes — torque-detect + self-learn | CAN (7–18 V front-end) + RKE |
| EBX‑2315 | 24 V (18–32 VDC) | Window + mirror + central-locking | No (driver-stage drive) | Single 36-pin; 90 s power-latch |
| EBX‑2163 | 24 V (18–32 VDC) | DCM: window + mirror + lock + RKE | Not default — confirm per program | 44-pin TE + 1×CAN @ 250 kbps |
| EDK‑908 | 24 V (18–32 VDC) | Switch panel (window / lock / mirror) | n/a (switch, not drive) | LIN + direct outputs, IP54 |
| EDK‑914 | 24 V (18–32 VDC) | Switch (windows / central lock only) | n/a (switch, not drive) | LIN data line + switching outputs, IP53 |
| TDK‑2202/3 | 12 V (9–16 VDC) | Switch (window / central lock) | n/a (switch, not drive) | LIN + direct outputs |
Read the table by voltage first. A 12 V passenger or light-commercial platform where anti-pinch is mandatory points to the EBX-2206: it runs four-door up / down with torque-detect anti-pinch and self-learning travel calibration on its own ECU (9–16 VDC, with a 7–18 V CAN front-end that holds the link through cranking sags), which suits a regulator-driven anti-pinch certification scope. A 24 V heavy-truck or bus cab that needs window, mirror and central-locking on a dedicated box points to the EBX-2315, which adds the configurable post-ignition-off power-latch (a reference 90 s "courtesy window" retention) that commercial cabs often ask for. A 24 V program that wants the door group folded into a platform DCM with RKE and key-learning points to the EBX-2163. And whichever module drives the loads, the EDK-908 is the panel the driver actually touches — the switch side of the same sub-system, not an alternative to the module. Where that door only needs its windows and central lock rather than the full mirror set, the leaner EDK-914 is the same LIN switch family in single- and dual-button variants.
The mistake buyers make here is treating anti-pinch as a checkbox that any window module carries. It is a distinct certification scope with its own torque-detection and self-learning logic — present as a dedicated function on the EBX-2206, but not a default on a driver-stage controller like the EBX-2315, and something to confirm per program on a platform DCM like the EBX-2163 rather than assume. If a market mandates anti-pinch, say so in the requirement; it changes which tier answers.
5. Where these modules show up on commercial vehicles
The door comfort group looks similar across vehicles, but the reason it is specified — and the tier it needs — changes with the platform.
- Heavy trucks. A 24 V cab with a rugged BCM that was never built for motor drive is the classic case for a dedicated window / mirror / lock controller such as the EBX-2315, or for folding the door group into a platform DCM like the EBX-2163. The powered mirrors on a long-haul tractor carry the mirror-heat load through the cold, which is why the defogger drive is part of the module scope, not an afterthought.
- Bus and coach. The driver-area door functions sit on a body network shared with passenger-door and destination-sign systems, so the LIN switch-panel-plus-module split (an EDK-908-class panel reporting to a networked module) tends to win over a fully local harness.
- New-energy platforms. On a 12 V body network these often want the anti-pinch window function isolated on its own ECU — the EBX-2206 pattern — both to meet an anti-pinch certification scope cleanly and to keep the pinch-detection loop close to the motor. Central locking and RKE frequently coordinate with the wider smart-key stack; see the PEPS keyless entry module guide for where that overlaps.
- Passenger-car and light-commercial. Anti-pinch is usually mandatory, one-touch auto-up / down is expected, and member-window lock-out (child-safety) is part of the spec — the full function set the EBX-2206 carries on a 12 V ECU.
The common thread is that the voltage and the network topology decide the tier before the feature list does. A 24 V rugged cab and a 12 V new-energy body are different problems even when the driver-facing feature — windows, locks, mirrors — reads the same on the brochure.
6. How to write a specification a supplier can quote
A window / door module requirement a supplier can quote against, rather than guess at, covers six things. Skipping any one of them is what turns a quick quote into a round of questions.
- System voltage. 12 or 24 V nominal and the tolerance band. This is the first fork: 12 V with anti-pinch points to the EBX-2206 tier; 24 V window / mirror / lock points to the EBX-2315 or EBX-2163 tier.
- Function scope. Windows only, or windows plus central locking, mirror adjust, mirror heat and RKE. State each function explicitly, because it sets the channel count and the connector size.
- Anti-pinch and self-learning. Whether torque-detect anti-pinch and self-learning travel calibration are mandatory — a distinct certification scope, not a default. If a destination market mandates it, name the profile.
- Vehicle interface. The CAN protocol to the BCM, whether a LIN switch panel (an EDK-908-class part) is in the harness, and how the door-handle, lock and ignition signals arrive.
- Connector and harness preference. A single-housing footprint like the 36-pin EBX-2315, or a split drive / signal pair like the 44-pin EBX-2163 — plus any power-latch ("courtesy window") retention the cab wants after ignition-off.
- Destination market. The region the vehicles run in, which fixes any radio type approval an RKE path must carry, and any market-specific material or EMC standard. Settle it early; it is the section most often left blank.
The decision buyers leave until last and regret is the anti-pinch scope in point three. It changes the controller tier, the motor-side sensing and the validation plan, and adding it after the harness is drawn is expensive. Decide it with the function scope, not after.
7. What to look for in a supplier
A window / door module drives motors, guards the security boundary of the cab and — where RKE is fitted — depends on a radio subject to per-market approval. The supplier questions that matter are about capability and honesty, not headline price.
- Motor-drive and protection design. The window and lock motors see stall current as a routine event, so the drive stage needs real protection — the four-fold set (over-voltage, over-current, short-circuit, over-temperature) on the EBX-2163, or the thermal de-rating on the EBX-2206 H-bridge. A supplier should discuss stall handling concretely.
- Anti-pinch experience, if you need it. Torque-detection thresholds, reverse-out behaviour and self-learning calibration are their own discipline. A supplier that has shipped anti-pinch should talk about the certification scope and the learn cycle, not promise a blanket "anti-pinch" feature.
- Standards and EMC capability. The 24 V modules here build against QC/T 413, ISO 16750 and ISO 7637, while the 12 V EBX-2206 adds material compliance to GB/T 30512. Confirm in-house EMC pre-compliance and environmental testing rather than outsourced-only validation. Youlai validates in an in-house environmental laboratory with EMC pre-compliance equipment.
- Region-specific approvals. Any radio type approval for an RKE path is available upon project requirement, confirmed per market on a project basis rather than blanket-claimed across the catalogue.
Quality system and PPAP level are on the IATF 16949 and OEM sourcing pages.
Questions you will be asked at RFQ stage
- MOQ and samples. A configurable variant of an existing EBX platform can usually move to samples quickly; a connector, key-map or anti-pinch profile unique to your program follows the firmware and validation timeline.
- Lead time. Driven mostly by any RKE radio approval and the harness / connector confirmation, not by the hardware build itself.
- Customisation scope. Variants on an existing platform — channel count, connector, CAN matrix, power-latch profile, key legend on the switch side — are routine, not an exception.
If you are scoping the door comfort group, the most useful things to bring to a first conversation are your system voltage and your function scope from section 6 — whether anti-pinch is mandatory, and whether the door group should live on its own module, in the BCM, or behind a switch panel. That lets us map your requirement onto the EBX‑2206, EBX‑2315 or EBX‑2163, pair it with the EDK‑908 switch panel, or tell you honestly where a custom variant is needed. For how the door group sits among the BCM, VCU, PMU and gateway, the Smart Control Modules technical guide covers the full module stack. And for the switch side of the same door — how a buyer picks between the EDK-908, the leaner EDK-914 and the 12 V TDK-2202/2203 — see the companion power-window & door switch panels guide.
For drawings, a function-scope and connector review or a sample request against your vehicle program, please use the contact page or message +86 134 6767 4786 on WhatsApp. Typical reply within one business day.