B16AE – Ignition encryption (BYD)

B16AE means the car does not accept the “authorized start” security check, so it may not power up or it may shut down the start request. For most owners, this feels like a no-start or an intermittent “won’t go READY” condition. According to BYD factory diagnostic data, B16AE is a BYD-defined body DTC meaning “Ignition encryption.” On the 2020 BYD Dolphin, the code points to a problem with the ignition authorization handshake between the start control path and the security/immobilizer logic. The code does not prove a bad module. It flags a failed verification that you must confirm with testing.

B16AE Quick Answer

B16AE on a BYD indicates the ignition authorization encryption check failed. Diagnose it like a security handshake issue first: confirm power/ground, network communication, and key/credential recognition before replacing parts.

What Does B16AE Mean?

Official definition: “Ignition encryption.” In plain terms, the vehicle did not validate the encrypted ignition authorization it expects during an ON/START request. In practice, that can block ignition ON, READY mode, or start authorization, even though other lights and accessories may work. What the module detected: a mismatch, missing response, or invalid authentication result during the ignition enable process.

What the module is actually checking: BYD uses module-to-module security logic so the start request, key/credential recognition, and body control authorization agree. The controlling module monitors message presence, timing, and authentication status on the vehicle network. It also checks that the expected “encryption/authorization OK” state arrives when the driver requests ignition ON. Why that matters: you must treat B16AE as a suspected trouble area in the authorization path. Wiring, grounds, network integrity, and credential recognition cause more faults than the modules themselves.

Theory of Operation

Under normal operation, the BYD Dolphin recognizes a valid key/credential, then the body control and security logic authorize ignition ON. The vehicle exchanges encrypted or authenticated messages between modules. Once the authorization passes, the car allows the normal ignition state transition and enables downstream systems.

This code sets when that authorization step fails. A low-voltage event, network dropouts, connector resistance, or a key recognition problem can break the handshake. A module can also reject authorization if it sees corrupted data or inconsistent states. You must confirm the failure mode with scan data and circuit checks, not guess.

Symptoms

Drivers and technicians usually notice one or more of these symptoms with B16AE.

• No-start/No-READY the vehicle refuses to enter READY or start after a button press
• Intermittent start starts sometimes, then fails without a clear pattern
• Start request ignored the start button changes lighting, but ignition state does not progress
• Security indicator immobilizer or security-related warning appears or behaves abnormally
• Multiple body DTCs other body or security codes store during the same event
• After 12V disturbance the issue appears after jump starting, battery service, or a low 12V battery
• Key/credential sensitivity the problem changes with a different key, fob position, or cabin RF conditions

Common Causes

• Key authentication failure between smart key and vehicle: If the BYD key ID or cryptographic handshake does not validate, the body system flags an ignition encryption fault and may block READY/ignition authorization.
• Low 12V system voltage during wake-up: A weak auxiliary battery or voltage dip during module wake-up can corrupt the encryption exchange and trigger B16AE even when the key is valid.
• High resistance at body control module power or ground: Corrosion or a loose ground point can pass a quick continuity test but fail under load, causing intermittent security logic resets and failed encryption checks.
• Immobilizer/anti-theft antenna or receiver circuit fault: An open, short, or poor connector fit at the key reader/antenna path can reduce signal quality and prevent the module from completing the ignition encryption process.
• CAN/LIN communication issue between body modules: If the gateway or body controller cannot exchange authorization data with related modules, the system may log an ignition encryption fault due to missing or invalid messages.
• Water intrusion at connectors near the dash or steering column area: Moisture can create leakage paths and intermittent shorts that disrupt the key verification and encryption routine.
• Aftermarket electrical additions interfering with wake/sleep logic: Poorly integrated alarms, remote starters, or accessory wiring can backfeed ignition or disturb network traffic, causing the encryption routine to fail.
• Software/configuration mismatch after module replacement or coding: If a control module gets replaced or configured incorrectly, the stored security credentials may not match and B16AE can set during the authorization attempt.

Diagnosis Steps

Use a scan tool that supports BYD body/immobilizer functions, including network scan and key/authorization data PIDs. Have a DVOM for voltage-drop testing, a test light or fused jumper for loading circuits, and basic back-probing tools. If available, use an oscilloscope for network integrity checks. Keep the smart key and a known-good 12V support source nearby.

1. Confirm B16AE and record all codes from every module. Save freeze frame data if the tool provides it. Focus on battery voltage, ignition state (OFF/ACC/ON/READY request), key recognition status, and any network-related DTCs captured at the set time. Freeze frame shows the conditions when the fault set, not what happens now.
2. Perform a quick visual inspection before meter work. Check the 12V battery terminals for looseness, corrosion, and evidence of recent jump-starting. Inspect related fuses and power distribution for the body/immobilizer/keyless system, and look for water tracks near the dash, steering column, and fuse box areas.
3. Verify 12V system health with the vehicle waking up. Measure battery voltage during unlock, door open, and during an ignition/READY request. If voltage sags sharply, charge and test the 12V battery and retest for B16AE. Low voltage can cause a failed encryption handshake without any hard wiring fault.
4. Check module power and ground with voltage-drop testing under load. Keep the circuit operating while you measure. Target the body control/security module power feeds and grounds that support key authorization. A good ground shows less than 0.1V drop under load. Do not rely on continuity alone.
5. Run a network scan on the scan tool and confirm all expected body/security modules appear. Note any modules that intermittently drop offline. If B16AE sets with other communication codes, address network power/ground and CAN wiring issues first because missing messages can look like an encryption failure.
6. Use live data to evaluate the ignition encryption process. Watch key detected status, key ID learned/authorized status, immobilizer authorization, and any “start/ready allowed” parameters while you attempt an ignition/READY request. Compare behavior with a second key if available. If one key fails and another passes, the fault points toward the key, not the vehicle.
7. Inspect connectors and harness routing tied to key detection and security authorization. Focus on the steering column/dash area, receiver/antenna connections, and the body control module connectors. Look for backed-out pins, poor terminal tension, fretting, bent pins, and corrosion. Reseat connectors and retest before any parts decisions.
8. Perform circuit checks for suspected open/short conditions found during inspection. Verify power supply integrity at the receiver/antenna or related security circuits with the circuit loaded. If you suspect a short-to-ground or short-to-power, isolate the branch by disconnecting the component and rechecking the circuit behavior. Avoid probing in a way that spreads terminals.
9. If the concern is intermittent, use a scan tool snapshot during a controlled test. Trigger a snapshot while you reproduce the symptom (lock/unlock cycles, door open, ignition request). Snapshot data captures the moment you provoke the issue. Freeze frame already captured the moment the DTC set, so use both to triangulate the failure.
10. Clear codes and perform a repeat ignition/READY request after each correction. For a hard fault, B16AE often returns immediately on key-on or at the next authorization attempt. If the code returns as pending first, continue testing until it either confirms/stores or the system completes several normal authorization events without a fault.
11. Only after power/ground, wiring, and key verification checks pass, evaluate software and configuration. Check for BYD service actions or updates related to immobilizer/keyless authorization. If a module was recently replaced, confirm correct configuration and security credential learning procedures per BYD service information.

Professional tip: Treat B16AE as a security authorization process fault, not a single part failure. Voltage quality and ground integrity often decide whether encryption completes. Load-test power and ground paths first, then judge the key and receiver using live data. When one key works consistently, stop chasing wiring and focus on that specific key or its programming.

Possible Fixes

• Restore 12V power quality: Charge, test, or replace the 12V battery as needed, then verify stable voltage during wake-up and ignition/READY requests.
• Repair power or ground voltage-drop issues: Clean and tighten ground points, repair corrosion, and correct loose terminals found during loaded voltage-drop testing.
• Repair wiring or connector faults in the key authorization path: Fix backed-out pins, poor terminal tension, water intrusion damage, or chafed harness sections affecting the receiver/antenna or body module circuits.
• Correct network faults that block authorization messaging: Address CAN/LIN wiring issues, module power supply faults, or intermittent module dropouts found during a network scan.
• Relearn/program key credentials when indicated: If testing proves the key fails authentication and wiring checks pass, perform the correct BYD key learning procedure with a compatible scan tool.
• Update software or correct configuration after verified prerequisites: Apply BYD-approved updates or configuration steps only after you confirm stable power/ground and verified circuit integrity.

Can I Still Drive With B16AE?

You can usually drive a BYD Dolphin with B16AE stored, but you should treat it as a starting and authorization risk. This code points to “Ignition encryption,” which relates to the vehicle’s key/immobilizer-style authorization and start-enable logic in the Body system. If the car starts and stays in READY, you may be able to move it to a safe place or a shop. Do not rely on it for repeated stop-and-go trips. A marginal encryption handshake can fail without warning, which can leave you unable to restart after you shut it off. If the vehicle shows “key not detected,” refuses READY, or cycles power unexpectedly, stop driving and diagnose it.

How Serious Is This Code?

B16AE ranges from an inconvenience to a no-start event. When it acts up only at first start and then runs normally, it often behaves like an intermittent authorization fault. That situation still matters, because the next key-on may fail. When the fault escalates, the Body control logic may block READY, disable start requests, or limit certain body functions tied to security. You rarely face an immediate driving safety hazard while already driving, but you can create a safety situation if you shut down in an unsafe location and the car will not restart. Prioritize diagnosis if the code resets quickly, if you see security warnings, or if you must rely on the vehicle daily.

Common Misdiagnoses

Technicians often replace the smart key fob, start switch, or a security module too early. B16AE does not prove a failed part. It only flags a problem area in the ignition encryption process. The most common wasted spend comes from skipping basic electrical checks. Low system voltage during wake-up, poor ground integrity, or a loose connector can corrupt the authorization exchange. Another trap involves clearing codes and calling it “fixed.” The encryption fault may only occur after a sleep cycle or a cold soak. Avoid guesses by verifying battery health under load, checking voltage drop on main grounds, inspecting security-related connectors for fretting or moisture, and confirming the fault repeats under the same conditions.

Most Likely Fix

The most frequent confirmed repair directions involve restoring clean power and signal integrity to the body/security authorization path. Start with battery state-of-health, terminal fit, and ground voltage-drop testing during wake-up and start attempts. Next, inspect and reseat connectors for the Body/security control path and related harness segments, focusing on pins with spread, corrosion, or water entry. If the wiring and power supply pass, the next step often involves BYD-level scan tool functions to re-learn or re-synchronize key/authorization data. Do not schedule module replacement until the scan tool shows stable inputs and the encryption error returns with verified power and ground integrity.

Repair Costs

Repair cost depends on whether the confirmed root cause is wiring, connector condition, a sensor, a module, or the labor needed to diagnose the fault correctly.