{"id":3231,"date":"2026-09-22T19:00:00","date_gmt":"2026-09-22T11:00:00","guid":{"rendered":"https:\/\/sayoon-dc.com\/?p=3231"},"modified":"2026-09-22T19:00:00","modified_gmt":"2026-09-22T11:00:00","slug":"hvil-ev-contactor-control","status":"publish","type":"post","link":"https:\/\/sayoon-dc.com\/ar\/blog\/hvil-ev-contactor-control\/","title":{"rendered":"How HVIL Signals Interact with EV Contactors"},"content":{"rendered":"

Quick answer:<\/strong> A robust HVIL strategy prevents a main contactor from closing when the interlock is open, opens the contactors when a valid interlock is lost, and verifies that the load-side bus has discharged before service access. The software should distinguish an intentional service opening from a broken wire or connector, but all unsafe states must inhibit high-voltage operation.<\/p>\n

HVIL contactor control is a sequence problem: the high-voltage interlock loop tells the controller whether covers, connectors, service plugs, and related safety links are closed, while contactor commands connect or isolate the battery. HVIL is not a replacement for contactor feedback and it is not a high-voltage measurement. It is a low-voltage permission and fault signal that must be interpreted with the pack state.<\/p>\n

\"MZJ-800A
MZJ-800A normally-open DC contactor reference image from the Sayoon product image library.<\/figcaption><\/figure>\n
\"MZJ-800A
Alternate angle used to verify terminals, enclosure and mounting details.<\/figcaption><\/figure>\n

At-a-glance design map<\/h2>\n\n\n\n\n\n\n\n\n
Element<\/th>\nWhat it does<\/th>\nSelection or diagnostic focus<\/th>\n<\/tr>\n<\/thead>\n
HVIL loop<\/td>\nSeries low-voltage continuity through covers and plugs<\/td>\nPermission and tamper\/fault indication<\/td>\n<\/tr>\n
Contactor command<\/td>\nHigh-side or low-side coil driver output<\/td>\nRequests mechanical state; does not prove it<\/td>\n<\/tr>\n
Auxiliary feedback<\/td>\nMechanism-position contact<\/td>\nConfirms movement with debounce and plausibility<\/td>\n<\/tr>\n
Bus sensing<\/td>\nPack and load-side voltage measurements<\/td>\nConfirms electrical isolation and discharge<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Product reference and scope<\/h2>\n

The MZJ-800A normally-open DC contactor shown in this article is a real Sayoon product reference. See the MZJ-800A normally-open DC contactor product page<\/a> and the high-voltage DC contactor range<\/a> for the family context. The image does not replace a model-specific drawing review; voltage, coil, current, insulation, duty, and mounting must be confirmed for the application.<\/p>\n

What HVIL can and cannot prove<\/h2>\n

An HVIL circuit normally runs a monitored low-voltage signal through high-voltage connectors, covers, service disconnects, and sometimes coolant or battery junction-box interfaces. Opening one item interrupts the loop. The controller can then inhibit new contactor commands or open an already closed path. This protects technicians from a connector being opened while the pack is still actively driving the bus.<\/p>\n

HVIL continuity does not prove that a main contactor opened, that a fuse is intact, or that the bus is at zero volts. A welded contactor can exist with a healthy HVIL loop, and a broken HVIL wire can exist with perfectly healthy contactor contacts. Keep the three signals\u2014interlock, mechanism feedback, and voltage\u2014separate in the design and diagnostics.<\/p>\n

Recommended control sequence<\/h2>\n

At wake-up, check HVIL, service-disconnect state, isolation status, and pack diagnostics before energizing any coil. If the path is valid, run precharge, monitor the DC-link rise, close the main contactor, and verify auxiliary feedback. When HVIL opens, remove the close permission immediately, command the contactors open according to the approved fail-safe strategy, and start a discharge timer. The system should not report \u201csafe\u201d until the measured voltage and time conditions are satisfied.<\/p>\n

The order matters. A fixed delay before opening can leave energy present if a converter is sourcing the bus. Conversely, opening a contactor while a large current is flowing can increase arc stress. The controller should use the measured state and hardware protections rather than relying on a single software timer.<\/p>\n

Debounce, diagnostics and fault ownership<\/h2>\n

Connectors vibrate and service plugs can bounce during insertion. Debounce HVIL transitions in a way that cannot mask a real open event, and record raw and filtered state. A persistent open loop should identify the segment or connector if the harness supports localization. A sudden open during drive should latch a high-voltage interlock fault, store the state of contactor commands and feedback, and prevent an automatic reclose until the service procedure allows it.<\/p>\n

Do not let a noisy auxiliary contact clear an HVIL fault. Each diagnostic input should have a defined owner: the interlock monitors physical access paths, auxiliary contacts monitor mechanism position, and voltage sensing monitors electrical energy. This separation makes root-cause analysis faster.<\/p>\n

Driver hardware and polarity<\/h2>\n

The coil-driver architecture can be high-side, low-side, or a dedicated automotive switch. Verify coil polarity, suppression, current limiting, open-load detection, short-to-battery and short-to-ground behavior, and the driver\u2019s response when HVIL drops. A flyback diode can slow release; an active clamp or economizer changes the waveform. Validate the selected network with the exact contactor coil and harness.<\/p>\n

The MZJ-800A reference shown here is a normally-open product example. Its coil option, auxiliary arrangement, and allowable suppression must be confirmed from the ordering code and drawing. Do not infer a safe release time from a different coil voltage or model.<\/p>\n

Contactor feedback versus HVIL<\/h2>\n

A healthy close sequence should satisfy all of the following: HVIL remains valid, the coil command is present, the auxiliary contact changes within the expected time, and the load-side voltage follows the precharge and main-close profile. If HVIL is valid but auxiliary feedback is missing, investigate the coil, driver, mechanism, wiring, and contact rating. If both feedback and command look correct but voltage is wrong, investigate the main path, fuse, precharge branch, or measurement.<\/p>\n

On opening, a valid HVIL loop does not permit the software to assume zero energy. Confirm the auxiliary transition and the bus discharge threshold. This layered plausibility check also catches a welded main contactor that would otherwise hide behind a normal HVIL signal.<\/p>\n

Service and crash behavior<\/h2>\n

A service disconnect may open the HVIL before the main contactors can be commanded. The pack should enter a defined sequence: remove torque permission, open contactors if possible, discharge the bus, and communicate the remaining voltage to the service tool. A crash controller may require a faster hardware path, such as a pyrofuse trigger, but the HVIL state still helps prevent re-energization during recovery.<\/p>\n

Write the timing and ownership into the system safety concept. The signal source, pull-up, diagnostic coverage, and default state should be clear to the person troubleshooting the pack months later.<\/p>\n

Commissioning checklist<\/h2>\n

With the pack de-energized, verify every HVIL segment and connector pin. With current limited, open one segment at a time and confirm that no close command is accepted. Exercise precharge and main close while recording HVIL, commands, auxiliary feedback, source voltage, load voltage, and timestamps. Then remove the interlock during an approved controlled test and verify contactor opening, discharge, fault latching, and recovery behavior.<\/p>\n

Use lockout and the vehicle maker\u2019s service instructions. The related Sayoon guides on safe contactor testing and opening\/closing time are useful references, but neither replaces the vehicle-specific safety procedure.<\/p>\n

Acceptance record for the engineering team<\/h2>\n

Before approving this hvil contactor control decision, create one controlled record that can be read by the design engineer, test engineer, production team, and service technician. List the exact part number and coil option, drawing revision, terminal labels, bus voltage range, current waveform or duty profile, ambient and enclosure temperatures, mounting orientation, conductor size, terminal torque, driver and suppression details, auxiliary logic, HVIL state, measurement instruments, calibration dates, and the pass\/fail thresholds. Separate catalogue values from measured values and identify every assumption. If a value is not available, mark it as an open engineering action instead of filling the gap with a typical number.<\/p>\n

Run the sequence at the boundaries that matter: minimum and maximum low-voltage supply, cold and warm equipment, the longest approved harness, repeated cycles, and the abnormal state that the safety concept names. Capture command, coil current, feedback, pack voltage, load-side voltage, and fault flags on one time base. After a failed event, stop automatic retries, isolate stored energy, and preserve the first-fault data. A later successful cycle does not erase evidence of a welded contact, slow release, intermittent interlock, or driver protection event. Release the product only when the complete record is reviewed against the current data sheet and vehicle-level requirements. Include photographs of the terminal layout and probe locations, the software build and calibration state, and a short explanation of why the chosen threshold is safe. This makes the result repeatable when a replacement sample, new harness, or firmware revision is introduced.<\/p>\n

Related engineering guidance<\/h2>\n

Use the DC contactor selection guide<\/a> for the broader sizing workflow, the safe contactor test guide<\/a> for isolation and measurement, and the opening and closing time guide<\/a> when setting diagnostic windows. For PLC-connected control logic, see the PLC coil-control guide<\/a>. These internal links support the decision without replacing the device data sheet or the vehicle safety procedure.<\/p>\n

Educational video<\/h2>\n

This neutral training video is included for visual context. It is not a product endorsement and the written, model-specific requirements above control the engineering decision.<\/p>\n