Mitsubishi-specific code — factory diagnostic data| DTC Data Sheet | |
| System | Body |
| Standard | Manufacturer Specific |
| Fault type | General |
| Official meaning | Collision decision (high voltage cut) |
Definition source: Mitsubishi factory description · Autel MaxiSys Ultra & EV. Diagnostic guidance is based on factory-defined fault logic for this code.
B1698 means the vehicle thinks a crash event occurred and it may shut down the high-voltage system. You may see warning messages, reduced power, or a no-start condition after an impact or even a hard jolt. According to Mitsubishi factory diagnostic data, this code indicates a “Collision decision (high voltage cut)” event on the 2016 Outlander platform. This is a manufacturer-specific body DTC, so the exact module logic can vary by Mitsubishi platform. Treat it as a safety-related command. Diagnose the inputs and network messages that triggered the high-voltage cut before you consider any part replacement.
Decode any Mitsubishi Outlander VIN — free recalls, specs & safety ratings — free VIN decoder with NHTSA data
B1698 Quick Answer
B1698 sets when Mitsubishi’s control logic decides a collision occurred and commands a high-voltage cut. Confirm whether a real crash event, sensor input, or communication fault triggered the cut before clearing codes.
What Does B1698 Mean?
Official definition: “Collision decision (high voltage cut).” In plain terms, a Mitsubishi module saw data that matched a collision decision. It then requested or confirmed a high-voltage shutdown for safety. In practice, this can disable the hybrid/EV high-voltage system, prevent READY mode, or force reduced operation depending on how the Outlander is equipped.
What the module checks and why it matters: The module does not “find a bad part” with this DTC. It verifies a collision decision using inputs and inter-module messages, then it confirms that a high-voltage cut action occurred or was requested. That distinction matters. Your diagnosis must focus on the trigger path, such as impact sensor decisions, SRS-related status, and the communication and power feeds that allow modules to agree on the event.
Theory of Operation
Under normal conditions, Mitsubishi’s body and restraint-related modules share status over the vehicle network. When the vehicle detects an impact that meets collision criteria, the system commands protective actions. One action involves disabling the high-voltage system to reduce shock and fire risk. The high-voltage system then opens contactors and prevents re-energizing until conditions look safe.
B1698 sets when the collision decision logic says “cut high voltage” and the module records that decision. A real crash can cause it. A false decision can also set it. Power or ground faults, a disturbed harness, or missing network messages can make modules disagree. The control unit then takes the safe path and shuts high voltage down.
Symptoms
Drivers usually notice a safety warning and a change in high-voltage readiness or power delivery.
- Warning messages related to SRS, EV/Hybrid system, or “service required” prompts
- No READY condition or a no-start state on electrified configurations
- Reduced power with limited propulsion or forced limp strategy
- High-voltage disabled with the system refusing to re-enable after key cycles
- Stored crash-related DTCs in SRS/airbag, ETACS/body, and HV/EV control modules
- Intermittent behavior after a hard pothole hit or minor bump if wiring has poor contact
- Post-repair lockout after body work if connectors or grounds were left loose
Common Causes
- Crash signal input stuck active: A short to power or an internal sensor fault can hold the collision decision line active and trigger a high-voltage cut request.
- Open or high resistance in crash decision circuit: Corrosion or a partially broken wire can distort the signal and make the module interpret a collision decision.
- Damaged SRS/impact sensor wiring: Harness damage near the front structure or radiator support can alter impact sensor communication and lead to a collision decision flag.
- Loose or contaminated connectors at related modules: Poor terminal tension or water intrusion can create intermittent signals that set B1698 during key cycles or bumps.
- Low system voltage during key-on: A weak battery or poor power distribution can cause module reset behavior and false collision logic, especially during cranking.
- Power or ground integrity issue at the controlling module: High resistance in the module ground or power feed can corrupt internal logic and force a high-voltage cut decision.
- Event memory not cleared after a prior collision decision: Some Mitsubishi platforms retain a collision decision status until the correct reset procedure completes.
- Network message plausibility fault between body/SRS/EV control modules: If a required collision-status message drops out or becomes implausible, the receiving module can default to a high-voltage cut strategy.
Diagnosis Steps
Use a scan tool that can read Mitsubishi body and SRS data, not just generic OBD. Have a DVOM, a fused test light, and back-probing pins. Plan for voltage-drop testing under load. Use wiring diagrams and connector views for the Outlander platform you service. Follow safety procedures around SRS and high-voltage systems.
- Confirm B1698 and note whether the code shows as pending, stored, or history. Record freeze frame conditions tied to this type of fault, especially battery voltage, ignition state, vehicle speed, and any related body/SRS/high-voltage cut DTCs. Freeze frame shows the conditions when the DTC set. Use a scan tool snapshot during a road test to catch an intermittent signal drop that freeze frame cannot show.
- Check fuses and power distribution first. Inspect the under-hood and interior fuse blocks for any body/SRS/related control fuses that feed the collision decision logic. Look for heat damage, loose fuse fitment, and signs of water intrusion. Perform a quick visual inspection of the suspected circuit path before meter work, especially around the front structure and areas with prior repairs.
- Verify module power and ground integrity under load. Back-probe the module power feed and ground circuits while the system operates. Use voltage-drop testing, not continuity alone. Target less than 0.1V drop on grounds with the circuit active. Load the feed with a fused test light if needed to expose high resistance that a DVOM can miss.
- Run a full module scan and record all DTCs, not only body codes. Pay close attention to SRS and any high-voltage cut related codes because B1698 often sets as a result of another input. Use the scan tool network scan to confirm all expected modules communicate. If a related module fails to appear, diagnose that communication or power issue first.
- Use live data to find the collision decision source. In Mitsubishi data lists, look for items that indicate crash status, collision decision, high-voltage cut request, and SRS event status. Compare those values key-on engine-off and during cranking. If the collision decision shows active with no event, treat that as a hard fault and focus on the input circuit or message source.
- Perform a careful connector inspection at the modules involved in collision decision and cut logic. Disconnect only after following SRS and high-voltage safety procedures. Check for backed-out terminals, water trails, green corrosion, and bent pins. Tug-test the wiring near each connector and inspect harness routing for pinch points and chafe marks.
- Check the suspected crash decision signal circuits for shorts and opens using the wiring diagram. Test for short-to-power and short-to-ground with the connectors disconnected where appropriate. Do not rely on continuity alone on long runs. Wiggle-test the harness while watching the meter and live data to catch intermittent opens.
- If the platform uses network messages for collision decision, verify network integrity next. Check related CAN wiring for damage, poor splices, or aftermarket device taps. Make measurements with ignition ON because network bias voltage only appears when the circuit powers up. If the bus shows instability, resolve that before condemning any module logic.
- Confirm the condition that sets the code. Clear DTCs and cycle the ignition. For continuously monitored circuits, a hard fault often returns immediately at key-on. If the code returns only after a drive, recreate the freeze frame conditions and capture a scan tool snapshot at the moment the status changes.
- Verify the repair without guessing parts. After correcting wiring, power, ground, or connector issues, clear codes and run the same key cycles and drive conditions that previously set B1698. Confirm that collision decision and high-voltage cut request data stay normal. Re-scan all modules to ensure no related SRS or network codes remain.
Professional tip: Treat B1698 as a “suspected trouble area” code, not a part verdict. On Mitsubishi platforms, collision decision logic can come from an input circuit or a network message. Start by proving clean power and ground with voltage-drop under load. Then prove the signal integrity. A stable supply often prevents false collision decisions.
Possible Fixes
- Clean, repair, and secure affected connectors, then restore terminal tension where needed.
- Repair open circuits, shorts, or high-resistance wiring in the collision decision or related harness routing.
- Correct power distribution faults, including damaged fuse terminals, weak grounds, or poor feed connections proven by voltage-drop testing.
- Address the root cause DTC in the SRS or related module that triggers the collision decision status.
- Perform the correct Mitsubishi reset or relearn procedure if the collision decision status remains latched after repairs.
- Replace a sensor or module only after you prove inputs, wiring integrity, and network health match specifications.
Can I Still Drive With B1698?
B1698 on a 2016 Mitsubishi Outlander points to a collision decision that commanded a high voltage cut. Treat that as a safety-related event first, not a convenience fault. The vehicle may drive normally, but it may also limit or disable the hybrid/EV high-voltage system and trigger warning messages. Do not continue driving if you smell smoke, see damaged wiring, or notice fluid leaks. Stop driving if the vehicle stalls, loses propulsion, or shows a “ready” or HV warning that does not clear. If the code set after a real impact or curb strike, arrange a tow and perform a full damage inspection before any road test.
How Serious Is This Code?
This code ranges from inconvenient to safety-critical, depending on why Mitsubishi logic made the “collision decision.” If it set from a minor event, you may only see warning lights and limited high-voltage operation. If it set from an actual collision signal, the system may have intentionally isolated high voltage to reduce shock and fire risk. That makes the fault serious by design. Do not treat B1698 like a simple sensor code. Confirm the event data, related DTCs, and the state of the high-voltage interlock and cutoff control before clearing anything. A wrong reset can hide damage and create a hazardous condition during later driving or charging.
Common Misdiagnoses
Technicians often misread B1698 as a failed battery, inverter, or “bad ECU” and start replacing expensive parts. The code does not prove any module failed. It only reports that the collision decision logic requested a high-voltage cut. Another common mistake involves clearing codes before saving freeze-frame and event records, which erases clues about what input triggered the decision. Shops also skip basic power and ground checks at the responsible module, then chase CAN or sensor theories. Avoid wasted spending by verifying the cutoff command path, checking connector integrity for impact damage, and confirming related impact, restraint, and interlock inputs with scan-tool data.
Most Likely Fix
The most common confirmed repair direction involves correcting the input that falsely indicates a collision, then restoring proper high-voltage enable logic. Start with a visual and electrical inspection of impact-damaged connectors and wiring in the front structure and engine bay. Next, confirm the high-voltage interlock loop and any cutoff control circuits show clean continuity and stable signals under light harness movement. If the vehicle experienced a real impact, repair physical damage first and then follow Mitsubishi service steps to reset collision-related latched states. Do not assume a module needs replacement until you prove correct power, ground, and signal integrity at its pins.
Repair Costs
Hybrid and EV high-voltage system repairs require certified technicians and specialist equipment. Costs vary widely depending on whether the fault is wiring, a sensor, a module, or a high-voltage assembly.
| Repair Type | Estimated Cost |
|---|---|
| Specialist diagnosis (HV-certified technician) | $150 – $300 |
| HV wiring / connector / sensor repair | $150 – $800+ |
| HV module / inverter / battery management repair | $500 – $3000+ |
| HV battery pack replacement | $2000 – $8000+ |
Key Takeaways
- B1698 indicates a commanded high-voltage cut, based on Mitsubishi collision decision logic.
- The code reports a detected condition, not a confirmed failed part.
- Treat it as safety-related until you rule out actual impact damage and HV isolation causes.
- Save event data first before clearing codes or disconnecting the 12V battery.
- Verify wiring, connectors, and interlocks with tests, not guesses.
FAQ
Does B1698 mean the Outlander was in a crash?
No. It means Mitsubishi collision decision logic saw inputs consistent with a collision and requested a high-voltage cut. A real crash can cause that, but so can wiring damage, a disturbed connector, or an interlock signal fault. Confirm with a full scan for related codes and review event records before you draw conclusions.
What should I check first before clearing B1698?
Capture all codes from every module and save freeze-frame or event data first. Then inspect for impact signs and check 12V battery condition, since low voltage can corrupt module decisions. Next, inspect connectors and harness routing near front body structures and the high-voltage service/interlock areas for pull-out, corrosion, or pin damage.
Can my scan tool still communicate with the module involved?
Communication matters. If your scan tool cannot access key Mitsubishi modules, diagnose power, ground, and network integrity before anything else. A dead or offline module can trigger collision decision logic indirectly. If communication works, use live data to confirm which collision-related inputs changed and whether the HV cut state remains latched.
How do I confirm the repair is complete after fixing the cause?
After repairs, clear codes only after you correct the root input and verify stable signals. Then road test under safe conditions and re-scan for pending codes. Some Mitsubishi collision or HV cut states require a specific reset procedure. Drive long enough for the system to run its self-checks; enable criteria vary by platform, so follow service information for confirmation.
Will this require module programming or initialization on a Mitsubishi Outlander?
Sometimes. If diagnosis proves a module needs replacement, Mitsubishi-level scan equipment typically handles coding, initialization, and post-repair checks. Collision decision and high-voltage control systems may store configuration and event data that generic tools cannot manage. Plan for a factory-capable scan tool to complete setup and verify the high-voltage system returns to normal operation.