The charge inlet lock and temperature sensors form a small but critical safety module in AC, Combo and ChaoJi interfaces. Together they keep the plug mechanically secured and keep long-term thermal risks visible to the charging ECU and vehicle safety logic.

Mechanical role of the charge inlet lock

• Prevents unplugging while current is flowing, reducing arcing and contact damage.
• Discourages theft, tampering or curious children from pulling the plug mid-charge.
• Supports OEM requirements for plug retention and safe user experience in unattended parking.

Why temperature monitoring is a second safety layer

• Rising contact resistance at the inlet pins raises local temperature and can lead to insulation damage or fire if it is not detected early.
• Ageing of cables, plastics and contact surfaces slowly changes their thermal behaviour, so continuous temperature sensing is needed to decide when to derate or stop charging.

Typical safety expectations from the system

• Lock and unlock actions are coordinated with main contactor closing and opening (details remain on the BDU and contactor driver pages).
• Normal, warning and fault states from the lock and temperature module feed into the higher-level charging state machine and diagnostic trouble codes.

From a system point of view, the charge inlet lock and temperature module sits between the charging ECU or CP logic on one side and the vehicle network and safety outputs on the other. It converts lock and unlock commands into actuator motion and turns Hall and NTC readings into status information and protection actions.

Command and power inputs

The module receives a lock or unlock request from the charging ECU or CP logic together with a low-voltage supply, typically from the 12 V domain. Higher-level state machines decide when it is safe to lock or release the inlet; this page focuses on how those commands are executed, not on the full charging protocol.

Lock actuator drive

Inside the module, a driver stage controls a small DC motor or solenoid that moves the mechanical lock. A bidirectional H-bridge or smart low-side driver applies current in the lock or unlock direction, while protection features such as over-current limiting and stall detection keep the actuator within safe limits.

Position and temperature sensing paths

One or two Hall sensors provide digital position feedback for locked and unlocked states into a microcontroller or safety input. Around the inlet, one to three NTCs or similar sensors feed an ADC through simple resistor dividers, allowing the ECU to monitor local heating at the contact pins, housing and cable entry.

Status reporting and protection outputs

The module aggregates these signals into discrete status lines, a LIN or CAN interface, and optional dedicated over-temperature outputs. This lets the vehicle diagnose lock and temperature faults, log trouble codes and, when necessary, stop charging independently of the rest of the charger implementation.

The charge inlet lock is typically driven by a compact actuator such as a small DC motor with gears, a screw mechanism or a solenoid-style latch. Each actuator type brings its own current profile, mechanical behaviour and driver IC requirements, so the lock drive must be sized and protected with these differences in mind.

Actuator types for the inlet lock

• Small DC motor with gears: offers smooth motion and larger travel, but has a pronounced stall current that requires bidirectional current control.
• Screw mechanism: adds self-locking behaviour so the lock can hold position without continuous current, at the cost of higher risk of mechanical jamming.
• Solenoid-style latch: gives fast, simple on/off motion but can draw high peak current and generate more heat and acoustic noise.

Driver topologies and current planning

Low-voltage H-bridge drivers are the most common choice for DC motor or screw actuators, because they provide clean direction control, current limiting and the option to ramp current with PWM. Dual high-side switches or back-to-back MOSFETs can reduce voltage drop and improve EMC in more demanding platforms, while relay-based solutions are typically limited to simpler latches in low-cost systems.

Typical lock currents are in the ampere range, but stall current can be several times higher. The driver and wiring must be rated for worst-case stall at low battery voltage and high ambient temperature, with sufficient margin to avoid nuisance trips and thermal overstress over the life of the vehicle.

Protection, diagnostics and automotive constraints

A robust lock drive implementation combines over-current, over-voltage and reverse polarity protection with stall and timeout detection. Monitoring current or driver status allows the system to detect a jammed mechanism or blocked motion, while soft start or current ramping helps reduce mechanical shock, acoustic click and EMI when the lock engages. Driver ICs are expected to comply with automotive requirements such as AEC-Q100 or AEC-Q101, wide temperature range and high immunity to electrical stress.

The lock driver typically runs from a 12 V supply that may originate from the body 12 V bus, a DC-DC converter or the on-board charger. Detailed planning of this supply, its redundancy and transient protection is handled on the relevant power and BDU pages; this section focuses on the actuator and driver IC level.

Hall-based position sensing gives the charge inlet lock a durable, sealed way to signal whether the mechanism is locked or unlocked. Compared with simple mechanical switches, Hall sensors tolerate vibration, moisture and long lifetimes while providing clean logic levels to the microcontroller or safety inputs.

Single versus dual Hall configurations

A single Hall sensor can distinguish between a locked and non-locked state at low cost, but it cannot detect all failure modes. Dual Hall configurations, implemented as separate locked and unlocked signals or as A/B encoded positions, allow illegal combinations to be detected and improve diagnostic coverage, which is important for higher safety targets.

Analogue Hall plus AFE versus digital Hall ICs

Analogue Hall elements followed by a discrete analogue front end provide flexibility in threshold and filtering, but require more components and careful tolerance analysis. Digital Hall ICs integrate the amplifier, comparator and hysteresis, exposing a simple open-drain or push-pull output that can be wired directly into microcontroller or safety inputs. Many automotive-grade Hall families from suppliers such as Melexis, NXP or onsemi are available with wide voltage range and extended temperature ratings.

Key diagnostics for lock position sensing

• Open or short circuits: input circuitry and software monitor can detect lines stuck at ground, battery or mid-rail, flagging wiring faults and sensor failures.
• Inconsistent states: with dual Hall, combinations such as both locked and unlocked high, or both low, are treated as illegal and reported as position sensing faults.
• Mechanical jam: a lock or unlock command that is not followed by a valid change in Hall state within a defined time window indicates a jammed or blocked mechanism.
• Tamper detection: lock feedback changing without any command from the ECU can point to external force, magnetic interference or an attempted tamper event.

IC selection direction and HVIL boundary

Suitable Hall ICs for inlet locks include automotive-grade digital switches and latches with diagnostic options, wide supply range and full –40 °C to 150 °C capability. In some architectures, one Hall channel is also tied into the high-voltage interlock loop to correlate physical lock status with HV permission, but the full HVIL topology and safety analysis are handled on the dedicated HVIL monitor page.

NTC-based temperature sensing turns the charge inlet into an early warning system for contact resistance growth, material ageing and overload conditions. Choosing the right sensing points, NTC characteristics and ADC front end is just as important as setting meaningful warning and shutdown thresholds that interact properly with the on-board charger and BDU.

Temperature sensing points around the inlet

• Metal contacts: NTCs close to the power pins react quickly to rising contact resistance and local heating, but must respect insulation and creepage constraints.
• Plastic housing: sensors near the inlet body give a smoother view of overall thermal load and material limits, at the expense of some response time.
• DC pins in combo inlets: dedicated NTCs near high-current DC pins monitor the most heavily loaded paths during fast charging.

NTC selection and ADC front end

Automotive NTCs with common 10 kΩ or 100 kΩ curves are typically used, with accuracy and tolerance chosen to keep error in the critical 50–120 °C range under control. A simple voltage divider into the microcontroller ADC, combined with modest RC filtering, usually provides sufficient resolution and stability. Multiple NTCs can be sampled on separate ADC channels or multiplexed through an analogue switch, as long as the sampling rate keeps up with the expected rate of temperature change.

Thresholds, zones and interaction with OBC and BDU

In practice, inlet temperature handling is divided into three zones: a normal region where temperatures are tracked but no action is taken, a warning region where power may be derated and the user notified, and a shutdown region where charging must stop. When NTC readings cross the warning threshold, the module can ask the on-board charger or DC charger to reduce current. Crossing the shutdown threshold triggers a hard stop request to the charger and BDU, allowing high-voltage contactors to open before any decision is made about unlocking the inlet for unplugging.

This section focuses on the inlet-side sensing and threshold planning. The detailed power path, high-voltage contactor timing and charger derating strategies are handled on the dedicated OBC and BDU pages, which use these temperature states as key inputs.

Safety behaviour for the charge inlet lock and temperature module is defined not only by its normal operation, but also by how it reacts to faults and how clearly it reports them to the vehicle ECU and charger. Lock motion, Hall feedback and NTC measurements must be combined into clear states and fault flags that higher-level safety concepts can rely on.

Typical faults and system reactions

• Lock cannot close: the ECU issues a lock command, but Hall feedback does not change within the allowed time. Charging is limited or blocked, and a fault is logged to prevent high-power operation with an unsecured plug.
• Lock cannot open: a release command does not produce a valid unlocked state after HV is removed. The vehicle warns the user, and service or manual release may be required to unplug safely.
• Hall signals inconsistent or noisy: dual Hall channels produce illegal combinations or excessive toggling, so lock status is treated as unreliable and charging modes may be restricted.
• Temperature over limit or NTC failure: readings cross shutdown thresholds or fall outside plausible ranges, triggering an immediate stop-charge request and a thermal fault code.

Fail-safe strategies for AC and DC charging

Fail-safe behaviour depends on whether the vehicle is in AC charging or high-power DC fast charging. In both cases, the system should avoid situations where the user can unplug under load, but DC faults carry higher arc and thermal risk. Many platforms keep the lock engaged whenever HV is present and only release it after contactors open and the charger confirms that current has stopped.

For AC charging, some OEMs may allow more flexibility, while DC fast charging typically favours default-locked behaviour when in doubt. The choice of whether a mechanical design should hold the lock position on loss of power or relax to an unlocked state is made at vehicle level, and the lock module must support that safety concept rather than define it on its own.

Reporting to ECU and charger

Internally, the lock module aggregates actuator status, Hall states, temperature zones and diagnostics into local status registers and optional fault pins. Externally, it exposes these as discrete signals and as structured information over LIN or CAN so the main ECU and charger can understand whether the lock is engaged, whether temperature is in warning or shutdown and whether any sensing or driver path has become unreliable.

High-level FMEA view

A simple failure analysis starts with asking what happens if the lock status is wrong, temperature is under-reported, the actuator jams or communication is lost. In each case, the module should either prevent high-power charging, limit operation or fall back to a conservative mode while raising a fault for service. This section does not replace a full ISO 26262 analysis, but outlines how the lock and temperature module behaves as a safety-relevant building block with clear inputs, outputs and fault reactions.

Instead of searching for random motor drivers or Hall sensors, it is more effective to define each functional block in the charge inlet lock module and then map it to the right IC families. This section summarizes the main blocks and the kind of automotive ICs you will typically look for across TI, ST, NXP, Renesas, onsemi, Microchip and Melexis.

Lock driver: H-bridge and low-voltage motor drivers

The lock driver IC is responsible for driving a small DC motor, screw mechanism or solenoid in a controlled way, providing forward and reverse motion, current limiting and basic diagnostics. For this block you typically look for automotive H-bridge or half-bridge motor drivers with peak current capability sized for the lock’s stall current, support for PWM and soft-start, and protection against over-current, short circuits and over-temperature.

Across TI, ST, NXP, Renesas, onsemi and Microchip you will find families of small automotive H-bridge and brushed DC motor drivers originally targeted at door, window and latch actuators. These are well suited for charge inlet locks when their current range, diagnostics and voltage rating match your requirements. Melexis, while best known for sensing, also offers actuator-related reference designs and solutions that can be combined at platform level with its sensors.

Hall sensors: integrated automotive Hall switches and linear sensors

Hall sensors provide contactless position feedback for locked and unlocked states. For this block you typically need single or dual digital Hall switches or latches, and in some cases linear Hall sensors combined with an analogue front end. Key selection points include supply voltage range, output type (open-drain or push-pull), hysteresis behaviour, operating temperature and the availability of self-test features or safety documentation.

Melexis has a wide portfolio of automotive Hall switches, latches and position sensors that are well suited to lock mechanisms. NXP and onsemi also offer robust automotive Hall switch families used in locks, doors and seat modules. TI, ST, Renesas and Microchip contribute additional Hall switches and linear Hall sensors that can be matched to different magnetic layouts and interface requirements in the inlet lock.

NTC front-end and ADC: MCU and AFE options

NTC temperature sensing needs an analogue path and an ADC that can reliably capture multiple channels and apply thresholds. In many designs this is handled by a small automotive microcontroller with multi-channel ADC, while other designs use a dedicated analogue front-end or power monitor that combines multiple inputs and built-in threshold comparators.

TI, ST, Renesas, NXP and Microchip all offer automotive microcontroller families with enough ADC channels and resolution to monitor Hall and NTC signals, along with built-in diagnostics and self-test capabilities. They also supply power monitor and AFE devices that can offload temperature and voltage supervision. onsemi contributes AFE and monitor ICs from its battery and power portfolios that are suitable for inlet temperature and supply monitoring, and some Melexis intelligent sensor devices combine a small MCU core with sensing and diagnostics for highly integrated implementations.

Interface and protection: LIN/CAN, PMIC and ESD/TVS

The interface and protection block covers LIN or CAN transceivers to communicate with the vehicle ECU, small PMIC or LDO devices to generate local supply rails, and ESD/TVS components to protect connector pins and supply lines. Selection focuses on automotive qualification, EMC and ESD performance, and compatibility with the OEM’s network and power architecture.

TI, ST, NXP, Renesas, onsemi and Microchip all provide automotive LIN and CAN transceivers and 12 V to 5 V/3.3 V regulators appropriate for charge inlet modules. onsemi and ST are also strong sources of automotive TVS and ESD components for connector and bus protection. By treating interface and protection as a defined block in the design, you can consciously choose parts that meet OEM EMC and ESD requirements rather than relying on generic industrial components.

Before you send a request for quotation or freeze the charge inlet lock design, it helps to collect all key requirements in one place. The checklist below is written from a practical design point of view, and the BOM notes show how to turn those requirements into clear, procurement-friendly descriptions instead of generic part names.

Design checklist for the inlet lock and temperature module

• Supply and current limits: define the nominal and extreme supply voltage range, the expected running current and stall current of the lock actuator, and the typical duty cycle during a charge session.
• Lock timing and behaviour: specify target lock and unlock times, required lifetime in number of operations, and whether you want soft-start or soft-release to reduce noise and mechanical shock.
• Hall channels and diagnostics: decide how many Hall channels you need (single or dual), whether you require redundant encoding, and what level of diagnostics is expected for open/short circuits, jams and tamper events.
• Temperature channels and thresholds: count how many NTC channels are needed, where they are placed (pins, housing, cable) and which warning and shutdown thresholds should be used, including whether rate-of-rise checks are required.
• Environmental conditions: capture ingress protection level, water and car-wash exposure, salt spray and corrosion expectations, and vibration and shock levels at the mounting location.
• ECU and network interface: define whether the module connects via GPIO, LIN or CAN, whether a dedicated fault pin is required and how fault and warning codes are expected to map into the vehicle diagnostic system.
• Safety and functional safety level: identify if lock status is tied into the high-voltage interlock loop, whether the function contributes to an ASIL goal, and what safety documentation (such as safety manual or FMEDA summary) you expect from IC suppliers.

BOM and procurement notes for clear RFQs

When you build a BOM or RFQ, describing each line item in terms of its role and key parameters makes it easier for suppliers to propose appropriate devices. The examples below illustrate how to phrase lock-related components for charge inlet applications.

Lock driver IC

Example wording:  “Charge inlet lock driver IC – automotive H-bridge for up to xx A peak lock actuator current, integrated over-current and stall diagnostics, supply xx–xx V, qualified to AEC-Q100.”

Suggested BOM fields: actuator peak and stall current, required diagnostics (over-current, short to battery/ground, stall, thermal shutdown), supply voltage range and automotive qualification level.

Position sensor (Hall)

Example wording:  “Position sensor – dual redundant automotive Hall switches for lock and unlock detection, supply xx V, open-drain outputs, operating –40 to 150 °C, suitable for magnet distance of approximately xx mm.”

Suggested BOM fields: number of channels (single/dual), output type, operating temperature range and mechanical arrangement or target magnet distance.

Inlet NTC sensors

Example wording:  “Inlet NTC sensors – automotive grade NTCs for pin / housing / cable locations, R25 = xx kΩ, β = xxxx K, accuracy class xx, optimized for monitoring in the 50–120 °C range.”

Suggested BOM fields: R₂₅ value (for example 10 kΩ or 100 kΩ), β value, accuracy class and intended mounting locations on the inlet assembly.

Local controller / AFE and interface

Example wording:  “Local controller / AFE – automotive MCU or multi-channel ADC with at least xx channels for Hall and NTC sensing, xx-bit resolution, built-in input diagnostics, LIN or CAN interface to the vehicle ECU.”

Suggested BOM fields: number of ADC channels, resolution, required input diagnostics and the chosen vehicle interface (LIN or CAN) including any fault pin requirements.

Protection and transceivers

Example wording:  “Protection & interface – automotive LIN/CAN transceiver and TVS/ESD components rated for the charge inlet environment, compliant with OEM EMC and ESD standards.”

Suggested BOM fields: target EMC and ESD levels, required standards or OEM specifications and the number of protected lines (communication pins and supply lines) at the inlet module.

The same building blocks can be combined in different ways depending on vehicle segment and charging capability. This section highlights a few compact design patterns so you can quickly see how a low-cost AC-only inlet differs from a DC fast-charging solution, and how centralised versus distributed control changes IC selection and validation priorities.

Pattern A – Cost-focused AC-only platform

For vehicles that only support AC charging at modest power levels, the inlet lock can remain simple. A single automotive H-bridge or brushed DC motor driver powers the lock actuator, a single digital Hall switch reports the locked state and one NTC monitors temperature near the inlet pins or housing. All signals can be wired directly into an existing body ECU, which implements basic warning and shutdown thresholds in software.

Recommended IC set: one small automotive H-bridge driver, one digital Hall switch, one NTC, ADC resources on the main ECU and simple GPIO-based status reporting. Validation focuses on mechanical endurance, basic thermal testing before and after thousands of lock cycles, and detection of simple faults such as open or shorted sensors.

Pattern B – DC fast-charging / high-power AC platform

DC fast charging and high-power AC operation demand higher diagnostic coverage and more detailed thermal visibility. Here the lock module typically uses a smart H-bridge or dual high-side driver with stall diagnostics, dual Hall sensors for lock and unlock detection, and two or three NTC channels located at DC pins, housing and cable transitions. A small automotive MCU or AFE aggregates Hall and NTC data, applies normal, warning and shutdown thresholds and exchanges structured state information with the vehicle ECU and charger over LIN or CAN.

Recommended IC set: smart H-bridge driver, dual redundant Hall sensors, multi-channel NTC network, local MCU or AFE with ADC and diagnostics, and LIN or CAN transceiver. Validation needs to cover DC fast-charging thermal behaviour, derating and shutdown under worst-case conditions, fault-injection of Hall and NTC wiring issues and end-of-life tests after many thousands of plug cycles.

Pattern C – Centralised versus distributed control

In a centralised architecture, the lock actuator, Hall sensors and NTCs are directly connected to a central body or charging ECU, which runs all logic and diagnostics. This reduces component count in the inlet but pushes signal integrity and safety analysis into a larger ECU platform. In a distributed architecture, the inlet lock becomes a self-contained module with a small MCU, driver and sensing, exposing clean normal, warning and fault states over a simple interface.

Centralised control works well when wiring is short and ECU resources are abundant. Distributed modules add cost but simplify wiring, improve local diagnostics and can be reused across vehicle platforms. In both cases, the same IC families apply; what changes is how much decision-making is local and how much lives in the central ECU.

Recommended topics you might also need

• CP/PP Front-End (IEC 61851)
• ISO 15118 PLC Modem
• Battery Junction Box (BJB)
• HVIL Monitor

These twelve questions capture how I think about lock drivers, current margins, NTC placement, diagnostics, safety and procurement for a charge inlet lock and temperature module. I can reuse the answers as internal design notes, RFQ guidance or FAQ content, and the structured data below mirrors the visible text one-to-one for search engines.