C2123 – Transmitter ID 3 not received (main) (Toyota)

Toyota-specific code — factory diagnostic data

C2123 means your Toyota Auris may stop “seeing” one of its registered wireless transmitters, so a safety feature can turn off or warn you. You will often notice a tire pressure warning and missing sensor data on the scan tool. According to Toyota factory diagnostic data, this code indicates “Transmitter ID 3 not received (main)”. This is a manufacturer-specific Toyota chassis code, so the exact logic and module strategy can vary by platform. Treat it as a direction to test the transmitter signal path, receiver function, and related wiring first. Do not assume the transmitter itself failed.

🔍Decode any Toyota Auris VIN — free recalls, specs & safety ratings — free VIN decoder with NHTSA data

C2123 Quick Answer

C2123 on a Toyota points to a missing wireless message from Transmitter ID 3 as learned by the main system. Confirm the ID registration, receiver operation, and power/ground integrity before replacing any sensor.

What Does C2123 Mean?

Official meaning: “Transmitter ID 3 not received (main).” In plain terms, the main Toyota chassis system expects to hear from a specific learned transmitter, but it does not. In practice, the vehicle can show a warning and stop displaying valid data tied to that transmitter. The code does not prove a bad sensor. It only proves the module could not receive that transmitter’s ID message.

What the module checks: the module monitors for periodic radio transmissions that match stored transmitter IDs. When it misses ID 3 beyond its internal time and plausibility rules, it sets C2123. Why that matters: diagnosis must focus on reception and configuration first. A dead transmitter, an unregistered ID, RF interference, or a receiver/power issue can all create the same “not received” result.

Theory of Operation

On Toyota platforms, the system stores transmitter IDs and listens for each ID’s radio messages. The receiver path can live in a dedicated ECU or inside another chassis-related module, depending on platform. Each learned ID must report often enough for the module to keep the system “trusted.”

C2123 sets when the main system cannot match received messages to stored Transmitter ID 3. The breakdown can come from a transmitter that stopped transmitting, a stored ID that does not match the actual transmitter, or a receiver path problem. A power, ground, or network issue can also stop the module from processing valid messages.

Symptoms

You will usually see a warning and missing data tied to one learned transmitter.

• Scan tool behavior Live data shows one transmitter missing, not updating, or reporting “not received” while others update normally
• Warning indicator Tire pressure warning light on, or TPMS warning message depending on cluster configuration
• Stored DTCs Additional transmitter-not-received or receiver-related chassis codes may store with C2123
• Intermittent operation Data returns briefly after a drive, then drops out again
• Recent service link Code appears after tire rotation, wheel replacement, sensor service, or an ID registration procedure
• Failed readiness The system will not complete its internal checks for that transmitter during a drive cycle
• Reduced feature confidence The vehicle may flag the related monitoring function as unavailable until communication returns

Common Causes

• Unregistered or mismatched transmitter ID 3: The TPMS ECU expects ID 3 but does not find it in its registered ID list, so it flags a missing ID.
• Transmitter battery weak or intermittent: A low-power transmitter may not send reliably, which prevents the receiver from confirming ID 3.
• Transmitter not transmitting due to internal fault: A failed transmitter can stop broadcasting its ID, even if the tire holds air normally.
• RF interference or shielding near the vehicle: Strong RF noise or metal shielding can block reception and make the ECU think the ID never arrived.
• Receiver path issue between antenna/receiver and TPMS ECU: An open, short, or high resistance in the receiver circuit can stop the ECU from receiving the decoded ID.
• Poor TPMS ECU power or ground under load: Voltage drop on B+ or ground can disrupt RF processing and cause intermittent “ID not received” events.
• Corrosion or poor pin fit at TPMS-related connectors: Terminal fretting or corrosion adds resistance and creates intermittent communication inside the TPMS receive chain.
• Recent wheel/tire service without completing initialization: A tire rotation, wheel swap, or sensor replacement can leave the system looking for the wrong ID position mapping, depending on Toyota platform logic.

Diagnosis Steps

You need a scan tool that can access Toyota TPMS data and perform ID registration or initialization. Use a TPMS trigger tool only if your platform supports it. Have a DVOM for voltage-drop testing under load. A wiring diagram and connector views matter here because Toyota routes TPMS receiver signals differently by platform.

1. Confirm C2123 and record freeze frame data. Focus on ignition state, vehicle speed, battery voltage, and any related TPMS or body/chassis DTCs. Freeze frame shows the exact conditions when the ECU decided “ID 3 not received.” Use a scan tool snapshot later to catch intermittent dropouts during a road test.
2. Run a complete network scan and verify all chassis/body modules communicate. If the TPMS ECU does not appear, treat this as a power/ground or network problem first. Check fuses and power distribution feeding the TPMS ECU and any receiver/antenna amplifier circuit before you backprobe any ECU connector.
3. Verify TPMS ECU power and ground with a voltage-drop test under load. Turn the ignition ON and keep the circuit operating. Accept less than 0.1V drop on the ground side and minimal drop on the B+ feed while loaded. Do not rely on continuity checks alone.
4. Pull TPMS Data List and compare “received ID” information for all available transmitters. Look for a pattern where three IDs update and one never updates. If the scan tool shows an “ID not registered” or blank entry for ID 3, treat registration or initialization as a top suspect.
5. Check the obvious service-history items before digging into wiring. Confirm whether the vehicle recently had tire service, wheel swaps, or sensor replacement. On some Toyota platforms, a rotation or wheel change requires an initialization or ID registration step for the main set.
6. Perform a targeted visual inspection of the TPMS-related harness and connectors. Focus on areas with movement or water exposure, including connector locks, terminal tension, and any signs of green corrosion. Repair pin fit issues before you test deeper because intermittent contact can mimic an RF problem.
7. If the platform uses a separate receiver/antenna assembly, verify the receiver circuit integrity to the TPMS ECU. Check for opens, shorts to ground, and shorts to power on the receiver signal and power/ground circuits. Keep ignition ON during any communication-related checks because circuit bias and module wake-up states matter.
8. Test transmitter function for the suspected “ID 3” sensor without guessing wheel position. Use scan data to identify which ID fails to report, then use a TPMS tool to read that transmitter’s ID and status at the wheel. If the tool cannot wake or read it, move the vehicle away from RF sources and retry to rule out interference.
9. Cross-check registration accuracy. Compare the ID read at the wheel to the ID stored in the TPMS ECU for the “main” set. If they differ, correct the registration and complete the Toyota initialization procedure required for that platform.
10. Clear DTCs and perform a confirmation drive under similar conditions to the freeze frame. Use a scan tool snapshot to capture live TPMS reception status during the drive. A hard fault will typically return quickly after key-on, while an intermittent may only return at speed.
11. If the code returns with a known-good registered ID and proven power/grounds, isolate the fault by checking for intermittent dropouts. Wiggle-test the receiver/ECU harness while monitoring TPMS data updates. If the updates drop out with harness movement, repair the harness or terminals rather than replacing modules.

Professional tip: Treat “Transmitter ID 3 not received (main)” as a direction, not a verdict. Toyota systems can store IDs correctly yet fail to receive them due to power/ground voltage drop or connector fretting. Verify ECU power and ground under load first, then verify the stored ID matches the physical transmitter ID. Only after those checks should you suspect a transmitter or receiver hardware fault.

Possible Fixes

• Register the correct transmitter ID and perform required initialization: Program the TPMS ECU with the ID read from the wheel and complete the Toyota learn/initialization procedure for the main set.
• Repair power feed, ground, or fuse connection issues: Correct voltage-drop problems at the TPMS ECU or receiver circuits that disrupt reception and processing.
• Repair or repin corroded/loose connectors in the receiver-to-ECU path: Restore terminal tension and clean corrosion to eliminate intermittent “not received” events.
• Repair harness damage in TPMS-related wiring: Fix opens, shorts, or chafing found during continuity and wiggle testing, then confirm stable data updates.
• Replace the confirmed-failed transmitter: Replace the sensor only after you prove it will not transmit or cannot be read with a TPMS tool and the ID matches the ECU entry.
• Replace the receiver/antenna or TPMS ECU only after verification: Consider module replacement only after you prove correct IDs, stable power/grounds, good wiring, and persistent non-reception.

Can I Still Drive With C2123?

You can usually drive a 2015 Toyota Auris with C2123 stored, because this chassis code points to a missing TPMS transmitter ID message, not an engine control fault. Treat it as a tire-pressure monitoring concern first. The risk comes from what you cannot see. If the TPMS warning stays on, you lose early warning of a rapid leak or underinflation. That increases the chance of tire damage, poor wet braking, and heat-related failure at highway speed. Before any long trip, manually check all tire pressures with a reliable gauge and inspect for punctures. If the tire pressure warning flashes first and then stays on, prioritize diagnosis soon because Toyota often uses that pattern for a system fault, not low pressure.

How Serious Is This Code?

C2123 ranges from an inconvenience to a meaningful safety risk, depending on tire condition and driver habits. If all tires hold pressure and you check them routinely, the impact stays mostly informational. When a tire leaks slowly, this code becomes more serious because the car may not alert you at the right time. The vehicle will still steer, brake, and drive normally in most cases, but you operate without a key safety net. Shops should treat it as a chassis safety system fault. Verify whether the TPMS lamp indicates low pressure versus system malfunction, then confirm which transmitter ID the main TPMS logic expects. Toyota platform details vary, so use the scan tool’s TPMS data list and health checks to decide urgency.

Common Misdiagnoses

Technicians often misread C2123 as “sensor #3 failed” and order a transmitter without proving the car lost that ID. The code only says the main TPMS logic did not receive transmitter ID 3. A dead sensor can cause that, but so can a wheel swap, an unregistered ID, or a receiver or antenna issue on some Toyota setups. Another frequent mistake involves ignoring scan-tool data. If the data list shows three IDs reporting and one blank, you must still confirm registration status and matching wheel location logic where applicable. Many wasted parts come from skipping basics like checking sensor activation, verifying the correct frequency sensor type, and confirming the TPMS ECU power, ground, and connector condition.

Most Likely Fix

The most common confirmed repair direction for C2123 involves correcting ID registration, not replacing hardware. Start by verifying the transmitter IDs stored in the TPMS system match the sensors installed on the vehicle. If a tire shop recently installed wheels or a new sensor, register the correct ID with Toyota-capable scan software, then perform the required initialization procedure. When registration checks out, move to circuit verification. Inspect the TPMS ECU or receiver connectors for water intrusion and terminal tension issues, then confirm clean power and ground under load. Replace a transmitter only after you prove it will not wake up, will not broadcast, or reports no data when you trigger it with the correct TPMS tool.

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.

Last updated: April 3, 2026

Definition source: Toyota factory description · Autel MaxiSys Ultra & EV. Diagnostic guidance is based on factory-defined fault logic for this code.