P1AC0 – Airbag ECU collision alarm (BYD)

P1AC0 means the car saw a crash-related alarm signal from the airbag system, and it can change how the vehicle drives. You may see warning lights and reduced performance until you diagnose it correctly. According to BYD factory diagnostic data, this code indicates an Airbag ECU collision alarm on BYD vehicles such as the Atto 3. Even though it shows under the powertrain system, this is an SRS safety-related event. Treat it as safety-critical. Follow BYD depowering procedures before touching any SRS connector. Use only OEM-approved test methods around airbag circuits and crash inputs.

P1AC0 Quick Answer

P1AC0 on a BYD means the powertrain side received a collision alarm status from the Airbag ECU. Diagnose why the Airbag ECU reported a collision event before replacing anything.

What Does P1AC0 Mean?

Official definition (BYD): Airbag ECU collision alarm. In plain terms, one module on the car believes a collision event occurred or got reported. That report can trigger warning indicators and powertrain safety actions, even if no airbags deployed.

What the module actually checks: the powertrain controller does not “sense” the crash directly. It monitors collision status coming from the Airbag ECU over the vehicle network and flags P1AC0 when that status looks active, invalid, or not plausible for current conditions. Why that matters: you must confirm whether the Airbag ECU truly logged a collision event, or the powertrain side received a corrupted message due to power, ground, or network faults.

Theory of Operation

Under normal conditions, the BYD Airbag ECU monitors crash sensors and internal accelerometers. It decides when to arm pretensioners and deploy airbags. It also broadcasts crash status to other modules so they can take protective actions.

When the Airbag ECU sets a collision alarm, the powertrain system may limit torque, change high-voltage behavior, or store event data. P1AC0 sets when that collision alarm information appears active or unreliable. Wiring issues, low module voltage, or network communication problems can create a false collision alarm at the powertrain level.

Symptoms

Drivers and technicians usually notice one or more of these symptoms with P1AC0 on a BYD Atto 3.

• Warning lights SRS/airbag light, master warning, or fault messages on the cluster
• Reduced power torque limitation or limp-style response after the event
• Drive mode limits restricted acceleration or forced conservative mode selection
• Event history crash or impact-related event entries stored in module memory
• Multiple DTCs companion network or power-supply codes in several ECUs
• Scan tool access limited access to SRS data on generic scanners or failure to clear related SRS faults
• Intermittent faults code resets after bumps, moisture, or low 12V battery conditions

Common Causes

• Actual collision event logged by the Airbag ECU: The SRS control unit can store a collision alarm when it detects a qualifying impact input or deployment logic event.
• Hard fault from an impact sensor input: A short, open, or biased signal from a crash sensor circuit can mimic an impact and trigger a collision alarm decision.
• High resistance in SRS power or ground feeds: Voltage drop during key-on self-check can corrupt sensor data and make the Airbag ECU flag a collision-related alarm.
• Connector seating or terminal tension problems at SRS components: Loose terminals or partial engagement can create intermittent contact that the ECU interprets as a severe event input.
• Harness damage in impact-prone zones: Pinched, stretched, or chafed wiring near the front structure or cabin can distort crash sensor and ECU signals.
• Water intrusion or corrosion at SRS connectors: Corrosion increases resistance and introduces noise, which can upset plausibility checks tied to collision detection.
• Network message plausibility issue between SRS and powertrain gateway: If BYD routing shares crash status over the in-vehicle network, missing or implausible messages can set a collision alarm DTC in a non-SRS module.
• Low system voltage events during cranking or wake-up: A weak 12V battery or unstable DC-DC output can cause the SRS self-test to record an alarm event.

Diagnosis Steps

Use a scan tool that supports full BYD SRS and powertrain data, plus module network scan. Follow OEM SRS depower procedures before touching any SRS connector. Use a DVOM for fused power checks and voltage-drop testing under load. Avoid probing SRS circuits with standard test leads. Use OEM-approved breakout methods and terminals only.

1. Confirm P1AC0 and record all DTCs from every module. Save freeze frame for P1AC0 and any related codes. Focus on battery voltage, ignition state, vehicle speed, and any crash or restraint status parameters. Freeze frame shows conditions when the fault set. Use a scan-tool snapshot later to capture an intermittent event during a road test.
2. Check whether the Airbag ECU and gateway modules appear in a full network scan. If a module drops off the list, diagnose power, ground, and network first. A collision alarm flag may route through a gateway on some BYD platforms.
3. Perform a visual inspection of the power distribution path before any ECU testing. Inspect 12V battery connections, main fusing, DC-DC related fuses, and ground points. Look for loose fasteners, heat damage, or aftermarket add-ons on shared feeds.
4. Verify all fuses that feed SRS and the gateway with the circuit powered. Do not rely on an ohmmeter check. Use a load method or measure for voltage on both sides of each fuse during key-on self-check.
5. Verify Airbag ECU power and ground integrity with voltage-drop testing under load. Backprobe only where BYD allows it, or use approved breakout tools. Command the vehicle to an ignition-on state that energizes the SRS system. Measure ground drop while the circuit operates and keep it under 0.1V. Also measure power-side drop across feeds and junctions under load.
6. Depower the SRS system using OEM steps and wait the specified capacitor discharge time. Then inspect Airbag ECU connectors, impact sensor connectors, and any inline connectors in the related harness paths. Check CPA locks, terminal push-out, bent pins, and corrosion. Do not insert standard probes into SRS terminals.
7. Inspect the harness routing in likely damage areas. Pay attention to front structure zones, radiator support routing, and kick panel passes. Look for rubbing, crushing, prior body repair, or water trails. Repair wiring using OEM-approved methods and sealing.
8. Use the scan tool to review SRS data that relates to collision alarm logic. Check any available “crash status,” “event record,” “impact sensor status,” and “system voltage history” PIDs. Compare left-to-right sensor status for plausibility if the scan tool provides it. Do not assume a sensor failed based on a single PID.
9. If the scan tool supports guided tests, run the Airbag ECU self-test and any impact sensor circuit checks. Follow BYD precautions exactly. If the tool allows actuator tests, do not trigger any pyrotechnic devices. Only run non-deployment diagnostic routines.
10. For an intermittent concern, create a controlled test plan. Use a scan-tool snapshot to record system voltage, ignition state, network status, and SRS crash status while reproducing the event. Drive only when safe and legal. Avoid harsh maneuvers that could risk deployment logic.
11. After repairs, reassemble connectors with correct locks and routing. Restore power, then clear DTCs only with a tool that supports BYD SRS. Cycle ignition and confirm P1AC0 stays cleared. Recheck for pending or history codes and confirm all modules report normal status.

Professional tip: Treat P1AC0 as a “suspected trouble area” code, not a confirmed failed module. Start by proving clean power and ground to the Airbag ECU and gateway under load. Many BYD collision-alarm reports trace back to voltage drop, connector tension, or water intrusion. Those faults can mimic crash inputs during the key-on self-check.

Possible Fixes

• Repair power or ground voltage-drop issues: Clean and tighten grounds, repair damaged power feeds, and correct loose battery or fusebox connections after verifying drops under load.
• Correct connector and terminal faults: Reseat connectors, restore CPA locks, and replace terminals only after confirming poor pin fit, corrosion, or push-out.
• Repair harness damage and restore routing: Fix chafed, pinched, or water-intruded wiring with OEM-approved splices, seals, and retention to prevent recurrence.
• Address low 12V system stability problems: Test the 12V battery and charging/DC-DC performance per BYD procedures, then correct undervoltage causes that coincide with the freeze frame.
• Resolve network or gateway issues when crash status messaging fails: Repair power/ground or communication faults that cause the SRS or gateway to drop off the network scan.
• Perform module programming or configuration only when verified necessary: If diagnostics prove a module logic or configuration issue, follow BYD service information for initialization, coding, and post-repair checks.

Can I Still Drive With P1AC0?

You can often move the BYD Atto 3 with P1AC0 present, but you should treat the SRS as compromised. This code means the powertrain side logged an Airbag ECU collision alarm message or status. Do not assume airbags and pretensioners will work normally. Drive only as needed to reach a safe location or a qualified shop. Avoid unnecessary trips and avoid carrying passengers if possible. Do not try “quick checks” at home on SRS connectors. Follow BYD depower procedures before any inspection, and use OEM-approved SRS test methods.

How Serious Is This Code?

P1AC0 ranges from a warning that needs confirmation to a serious safety event, depending on what triggered the Airbag ECU collision alarm. If a minor impact or road event triggered the message, the vehicle may drive normally but the SRS may store crash-related data. If the Airbag ECU reports an actual collision status, some functions may change. The powertrain may limit torque or disable certain features on some BYD platforms. Treat this as safety-critical. Diagnosis requires SRS-certified equipment, proper depowering steps, and technician training. Do not DIY repairs on squib or pretensioner circuits.

Common Misdiagnoses

Technicians often blame the Airbag ECU first because the description says “collision alarm.” That wastes time and money. P1AC0 usually reflects a message or status the powertrain module received, not a confirmed failed ECU. Another common miss involves skipping a full vehicle scan. Shops fix a powertrain code and ignore SRS history codes that explain the alarm source. Many also probe SRS wiring with standard test leads and create new faults. Avoid guesswork by confirming network communication, checking for related SRS DTCs, and verifying power and grounds with approved methods.

Most Likely Fix

The most common confirmed repair direction involves restoring correct communication and status reporting between the Airbag ECU and other BYD modules. Start by resolving any active SRS DTCs and CAN or power supply faults that accompany the collision alarm. Next, verify Airbag ECU power and ground integrity with voltage drop testing under load. Only after those checks should you consider module configuration issues, such as a collision status that did not reset due to stored event data. Verify the repair by re-scanning all modules and confirming the collision alarm status returns to normal.

Repair Costs

SRS/airbag repair costs vary significantly by component. Diagnosis must be performed by a qualified technician with SRS-capable equipment. Do not attempt airbag system repairs without proper training and safety procedures.