New-Energy Commercial Vehicle Electronics: HV Conversion, Control and Cockpit

New-energy commercial vehicles — battery-electric trucks, electric buses, hybrid tippers, fuel-cell platforms — keep almost every low-voltage function the diesel version had, and add a domain that has to be brought up in a defined order before any of it works. Youlai supplies the layer between the two: the converters that feed the 24 V bus from the traction pack, the fusing that terminates a pack fault, the control domain that sequences the start-up, and the cockpit hardware that shows the driver which state the vehicle is in. Manufacturing is under an IATF 16949 certified quality system in Changsha, China. This page is the horizontal view of how those pieces fit on one vehicle; the buyer guides linked at the end of each section go deeper into individual selection.

1. How an electric commercial vehicle splits electrically

Electrification does not remove the low-voltage system. It removes its source. With no alternator, the 24 V bus is derived from the traction pack through a DC/DC converter, which promotes that converter from an accessory to a primary component. The low-voltage battery still buffers the bus, so a converter that drops out is not an instant blackout — but nothing is replenishing that battery either, and when it sags the lighting, braking electronics and cluster go with it. How long that window lasts, and what the vehicle has to do inside it, belongs in the specification rather than on a datasheet. The second change is that the vehicle no longer simply switches on. Between key-on and a usable 24 V bus there is a sequence — pre-charge, main contactor closure, converter enable, then everything downstream — and agreeing who owns each step is a bigger integration question than any single box on this page.

Two boundaries decide most of the integration effort. The first is the high-voltage to low-voltage interface, which is not just a voltage step: the HV side carries its own rule set for insulation coordination, interlock loops, service disconnection, creepage and clearance, shielded and orange-identified cabling, and separate technician qualifications. Anything spanning that interface — the DC/DC, an export-power inverter — inherits both rule sets and is expensive to change late. The second is who owns the sequence: the battery system holds contactor authority, the vehicle controller decides when to ask for it, and the converter has to report that it has converged before the main contactor closes. Three parties, one handshake, worth writing down before hardware is quoted.

Beyond those two, where on the vehicle a part lives decides its enclosure and the evidence behind it as much as its function does. Four positions, and one domain that runs through all of them:

Does a hybrid or fuel-cell platform change this picture?

It changes the source side rather than the structure. A hybrid keeps an engine, and depending on the architecture the 24 V bus may still sit behind a conventional alternator, may be fed entirely through the converter as on a battery-electric platform, or may have both. Where there are two sources the question moves from what happens if the converter stops to which source has priority, who arbitrates between them, and what the converter has to carry alone while the engine is off — and that last condition, not the average, is what sizes it.

A fuel-cell platform keeps the battery-electric structure: an HV bus, a DC/DC feeding the auxiliary side, the same insulation and interlock rules. What it adds is a source that cannot be switched on by closing a contactor — the stack needs air, pressure and temperature before it delivers, and it runs its own purge and shutdown sequence afterwards. Every high-voltage platform needs the low-voltage side alive first, because the contactors and the battery system run from it; on a fuel-cell vehicle that window is longer and carries real auxiliary load, which is what makes the start-up handshake and the hard-wired converter enable in section 2 worth fixing in the specification rather than in the integration phase.

2. From the traction pack to the 24 V bus

Size the converter from the low-voltage side, not the high-voltage side. The pack voltage sets which input window you need; the continuous 24 V load with everything running — HVAC, lighting, steering and brake electronics, body loads, cab equipment — sets the power rating, and that figure is routinely underestimated on the first pass because the diesel platform's alternator absorbed the error.

EBX-2314 is the reference at heavy-duty scale, and two lines of its specification decide more than the headline power does. It is rated for Class I duty — 100 % of rated output continuously, which is the figure that matters where auxiliaries never idle — and it holds ≥ 95 % efficiency at full load, because the remainder leaves as heat in an equipment bay that has to absorb it. Diagnostics are dispatched both ways: UDS (ISO 14229) for a service tool and J1939-73 DM1 onto the vehicle bus, so a converter fault reaches the cluster as an active fault rather than as silence. Where auxiliary demand is smaller — a medium-duty platform, or a second converter on an isolated branch — EBX-2512 is the 6 kW part, and its wider input window also makes it the one to look at on a 900 V platform. The three conversion modules side by side:

What does pre-charge actually have to do?

Closing a main contactor straight onto the DC link of a converter or inverter means charging its capacitance from a near-zero-impedance source. The inrush welds contacts and ages the pack connection, so the bus is first brought up through a current-limiting path until the two sides are close enough in voltage. The specification question is not whether to pre-charge but who runs it. EBX-2314 hosts the function on board: the same controller that runs the DC/DC stage drives the pre-charge enable, monitors the voltage rise and signals the battery system to close the main contactor once pre-charge has converged. That removes a separate pre-charge box, but it also makes the handshake with the battery system part of the converter's specification — agree the message set and its timing, not just the power rating.

One more line is worth protecting: EBX-2314 carries a high-level hard-wired enable alongside its two CAN channels, so the auxiliary bus can be brought up when the network is not yet available. On a vehicle whose 24 V supply comes through this box, a converter that can only be enabled over CAN creates a circular dependency at exactly the wrong moment.

Protection at the pack boundary is a separate discipline from anything downstream. JDK-2509 is a 1500 VDC battery-pack fuse in the aBat utilisation category of IEC 60269-7, rated 1250–3000 A continuous with 250 kA breaking capacity and type-tested for short circuit at a TÜV-accredited laboratory. Two properties make it a pack part rather than a large fuse: aBat is defined for battery-system protection specifically, so its time-current behaviour is matched to a pack fault rather than to a generic overload; and a mechanical striker shows fuse state physically, which is how a depot technician confirms the condition without interrogating an energised HV circuit. Where the requirement is to break the control side of a contactor or isolator rather than the HV path itself, JDK-2425 is the direct-acting mushroom-head device for that job.

Going deeperThe smart control modules guide has a dedicated section on VCU, DC/DC and battery-equaliser selection on new-energy commercial vehicles, and the power distribution guide covers what happens downstream of the 24 V output.

3. The low-voltage side: 12 V branches and dual batteries

Most new-energy commercial platforms are 24 V vehicles with a 12 V problem: telematics, a radio, a camera or a customer-fit accessory expects 12 V, and the answer chosen at design is much cheaper than the one improvised at build.

EBX-2407 handles the case where two 12 V batteries sit in series to make the 24 V system: it steps 24 V down to 12 V and equalises the state of charge between the two batteries in one IP67 unit, in 100 A and 30 A versions, with CAN self-diagnostics so an imbalance is reported rather than discovered when one battery fails early. Where the requirement is a small isolated rail instead — a sensor group, an instrument, a subsystem that must not share a ground return — EBX-2515 is a 180 W potted IP67 converter giving 12 V at 15 A from a 9–36 V input, with 1000 VDC isolation between input and output.

Everything downstream of that point is conventional commercial-vehicle distribution, and the NBX series serves it the same way it serves a diesel platform — by way count and sealing class, matched to the mounting zone. The one habit worth changing is load-list discipline: on an electric vehicle the auxiliary load list is not just a fusing exercise, it is the input that sizes the converter in section 2, so it needs to be frozen earlier than it usually is.

Going deeperFuse box guide for what goes inside a distribution box, relay vs fuse vs junction box for which enclosure a position needs, and the selector for every NBX model side by side.

4. The control domain: VCU, VBU and where the BMS boundary sits

On a diesel platform the engine ECU arrives with the engine and the body controller is a separate purchase. On an electric platform that split is open: the vehicle control unit is a genuine programme decision, and what it absorbs from its neighbours decides how many boxes, connectors and CAN segments the vehicle ends up with.

EBX-960 is the conventional answer — a new-energy VCU covering torque arbitration, regeneration and the HV/LV power-up and power-down sequencing among its functions, on a 7–48 VDC supply with two ISO 11898 CAN channels, CAN-Bootloader firmware update and an IP65 housing rated to +105 °C. The wide supply window is worth noting: it is one of the few modules here that does not care whether the platform is 12 V or 24 V.

EBX-960B is the domain-fusion variant, and it is a different architectural proposition rather than a bigger VCU. It runs the vehicle-control strategy and the battery-management strategy on a single 200 MHz automotive MCU with 2.5 MB of flash, using two individually isolatable CAN channels — typically one to the vehicle network and one dedicated to the battery-pack network. Collapsing two boxes into one removes the inter-box harness, the second housing and the CAN traffic that used to run between them, for a typical ~10 % reduction in vehicle-CAN bus load, on the same footprint as EBX-960. Two constraints come with it: it is a 9–16 VDC part, so it does not drop into a 24 V platform unchanged, and merging two strategies onto one scheduler is a programme-level decision about validation and change control, not a drop-in substitution.

Which parts of a battery system do we supply, and which do we not?

Worth stating plainly, because “BMS” is used for two different things. Youlai supplies the controller that can host battery-management strategy (EBX-960B), the pack-side fusing that terminates a fault (JDK-2509), and the HV-to-LV conversion and pre-charge control in section 2. Youlai does not supply cells, pack assemblies, cell-sensing front ends, module monitoring boards, balancing hardware or traction inverters — EBX-960B reaches cell and module data over its dedicated pack-network CAN, which means a sensing architecture supplied by someone else already exists in the design. If a programme needs a complete battery system rather than the controller that runs its strategy, that is a pack-supplier conversation, and saying so early is cheaper than discovering the gap at integration.

Going deeperThe vehicle control unit guide covers VCU scope and its interfaces to BMS, charging and inverter control, BCM vs VCU vs PMU sets the three controller types apart, and the power management unit guide covers the load-switching side.

5. Export power and the cockpit

Two things a diesel cab never had show up here: a vehicle that can supply mains power to the outside world, and a cluster that has to describe an electrical state rather than an engine.

EBX-2514 is the export-power path — a 30 kW HV-to-AC inverter delivering 220 VAC at 50 Hz from the same 400–1100 VDC window as EBX-2512, in an IP68 housing. On service, utility and municipal vehicles this replaces a separate generator set, and the specification question is usually not the inverter but its terms of use: which loads, for how long, and what state of charge the vehicle refuses below. That policy lives in the vehicle controller, not in the inverter.

In the cab, PBX-2301 is the cluster built for this content: an 8-inch combined instrument on 9–32 VDC with two CAN channels and CAN-FD support, self-heating for a −45 °C start and rated for altitudes above 5000 m, carrying nine dedicated EV indicators — ready-to-drive, stop, HV power-up, insulation resistance, traction-battery charging and fault, imminent HV cut-off, DBS and APU. Those nine are the reason it is worth specifying a purpose-built EV cluster rather than adding icons to a diesel one: each is a state published by a node the cluster does not own, so the content agreement matters more than the panel. Read its catalogue position before quoting it — it is listed in plateau and new-energy configurations, so the variant for your platform is agreed at RFQ rather than assumed.

Three smaller parts complete the cab. EDK-916 is a shift-by-wire P/R/N/D selector for new-energy drivelines, with shift interlock, catalogued as a 12 V part — a 24 V variant is a quotation item, not a listing. EBX-2406 combines the acoustic vehicle alerting function with turn and blind-spot warning in one CAN-controlled external unit at 85 ± 3 dB, which matters because a quiet vehicle at low speed is a regulated condition in a growing number of markets rather than a comfort feature. And EBX-2305 is the 12 V body controller for new-energy platforms, covering lighting, wipers, locking and RKE/PKE.

Going deeperThe instrument cluster guide covers cluster selection including EV content, HUD vs digital cluster compares formats, and the heavy-truck BCM guide covers the body-control layer these platforms inherit.

6. What makes a new-energy specification different

Most of what separates an electric programme from its diesel equivalent is not the part list. It is that several components now depend on each other in a defined order, and that a second set of rules applies to anything within reach of the high-voltage domain.

What has to be agreed before hardware is quoted?

Body type adds a second layer on top of all this. On an electric bus the passenger request layer, door and accessibility functions carry their own approval and duty-cycle requirements, and bus and coach electronics covers that side of the same vehicle; where the platform is an electric tractor unit or tipper, the cab, chassis and distribution layer is largely the one described in heavy truck electronics. Route and climate conditions are a specification input rather than a boundary on where we work — the Middle East / GCC and Southeast Asia pages show how one catalogue is filtered for heat and dust versus humidity. See sourcing OEM vehicle electronics for how IATF 16949, APQP and PPAP divide responsibility, and IP65 / IP67 protection for how sealing claims are validated.

7. Specifying a new-energy programme

Quotes come back accurate when the request carries the facts that decide the hardware. For an electric or hybrid commercial vehicle that means:

What should a new-energy electronics RFQ include?

• Platform and architecture — vehicle type and duty, battery-electric, hybrid or fuel-cell, and whether the chassis, pack and body come from the same organisation.
• Both voltage classes — the HV nominal and operating window, and the LV nominal, stated separately rather than implied by vehicle type.
• The auxiliary load list — every 24 V and 12 V load with its current and duty, and the continuous total with HVAC running, because this figure sizes the converter.
• The power-up sequence — who owns contactor authority, who runs pre-charge, which messages confirm each step, and the behaviour on timeout.
• Battery-system scope — who supplies cells, pack, sensing and balancing, and whether the vehicle controller is expected to host battery-management strategy.
• Network architecture — CAN channel count and application layer, whether the pack network is separated, the DBC or signal list if one exists, and the diagnostic protocol expected.
• Export power, if any — load type, continuous and peak demand, expected duration and the state-of-charge policy that limits it.
• Cockpit content — which EV states must be displayed, which are regulated in your markets, and which node publishes each one.
• Mounting and thermal conditions per part — zone, ambient, airflow, orientation, vibration profile, and the reports required at each validation gate.
• Commercial inputs — markets, annual and lifetime volume, sample stages, tooling ownership, PPAP level and SOP date, which decide validation depth and timing.

The OEM RFQ checklist puts this in a form you can send. Manufacturing is IATF 16949 certified with in-house environmental and EMC pre-compliance testing, and PPAP deliverables and the submission level are agreed against the customer-specific requirements and the released drawing revision.

Send the auxiliary load list, the platform voltage classes and the power-up sequence as you have defined it, and we will come back with a proposed split across conversion, protection, control and cockpit. Use the contact page or message +86 134 6767 4786 on WhatsApp — typical reply within one business day.