C1693 – ESC Signal error (Hyundai)

Hyundai-specific code — factory diagnostic data

C1693 means the Hyundai IONIQ 5 has logged an ESC signal error that can disable or limit stability-control related features. You may notice warning lights and reduced driver-assist functions, even if the vehicle still drives normally. According to Hyundai factory diagnostic data, this is a Hyundai-defined chassis code that points to a problem with an ESC-related signal the CR (Corner Radar) module expects to see. The key point matters for repairs. This code does not prove a failed radar. It tells you the module detected an invalid, missing, or inconsistent ESC signal and stored a fault.

🔍Decode any Hyundai IONIQ 5 VIN — free recalls, specs & safety ratings — free VIN decoder with NHTSA data

C1693 Quick Answer

C1693 on Hyundai indicates an ESC signal error seen by the CR (Corner Radar) module. Start by verifying power, grounds, and the communication path for the ESC-related message before replacing any components.

What Does C1693 Mean?

Official meaning: C1693 – ESC Signal error (Hyundai). In plain terms, the CR (Corner Radar) module reports that an ESC-related signal it relies on does not look right. In practice, the IONIQ 5 may limit stability-related coordination with driver-assist features, and it may turn on ESC/ADAS warnings.

What the module is checking: The CR module monitors one or more ESC-related inputs that arrive as network messages or discrete status lines, depending on Hyundai platform design. It expects correct timing, valid status, and plausible content. Why that matters: Per SAE J2012-DA guidance, a DTC points to a suspected trouble area, not a root cause. Treat C1693 as a direction to test the ESC signal path, message integrity, and module power/ground stability before you condemn the radar, ESC unit, or wiring.

Theory of Operation

Under normal conditions, Hyundai ESC calculates vehicle stability corrections and shares status and requests across the chassis and ADAS network. Other modules, including the CR (Corner Radar), use that ESC status to coordinate functions that depend on stable vehicle dynamics data. The radar module needs consistent vehicle-state context so it can filter targets and manage feature availability.

C1693 sets when the CR module receives an ESC-related signal that fails validity checks. The module may see a message drop-out, an implausible status, or corrupted content. Power or ground instability at the radar often causes this. Network issues also trigger it, because the CR module depends on message timing and data integrity.

Symptoms

Drivers and technicians usually notice one or more of these issues with C1693.

• Scan tool behavior CR (Corner Radar) shows C1693 stored, and the fault may switch between current and history with key cycles
• ESC warning ESC or stability-control warning lamp may illuminate or display a message
• ADAS limitation Driver-assist features that rely on radar may show “limited” or “unavailable” messages
• Traction behavior Traction and stability interventions may feel reduced or disabled during low-traction events
• Intermittent faults Warnings may appear after bumps, rain, or after a car wash due to connector moisture
• No drivability change Vehicle may drive normally, but safety features may not operate as designed
• Multiple chassis codes Other chassis or ADAS DTCs may set alongside C1693 when the network drops messages

Common Causes

• ESC message missing on the network: The CR (Corner Radar) stops seeing a required ESC status message, so it flags an ESC signal error.
• CAN bus open circuit near the front/rear harness runs: An open in CAN wiring prevents the ESC-related data from reaching the radar module consistently.
• CAN bus short to ground or short to power: A rubbed-through harness can pull the bus down or bias it high, corrupting ESC data and triggering the fault.
• High-resistance power or ground to the CR (Corner Radar): Voltage drop under load can reset the module or distort its network transceiver operation.
• Connector pin fit or corrosion at the radar or junction connector: Slight terminal spread or moisture increases resistance and creates intermittent “no signal” events.
• ESC/ABS module offline or rebooting: If the ESC controller drops off the network, the radar module reports an ESC signal error even when its own wiring is intact.
• Incorrect coding or variant configuration after repairs: A “not configured” condition can occur if module setup does not match vehicle options, so expected ESC messages do not align.
• Aftermarket electrical device or poor repair affecting the network: Non-OEM splices and add-on power taps can inject noise or disturb CAN integrity.

Diagnosis Steps

You need a scan tool that can access Hyundai chassis modules, including CR (Corner Radar) and ESC/ABS. Use a quality DVOM, a test light or load tool, and back-probing leads. Have wiring diagrams and connector views for the radar and ESC circuits. If you have a scope, use it to confirm CAN waveform integrity during an intermittent fault.

1. Confirm C1693 in the CR (Corner Radar) and record freeze frame data. Focus on ignition state, battery voltage, vehicle speed, and any related ESC/ABS, CAN, or power supply DTCs. Freeze frame shows conditions when the fault set. Use a scan tool snapshot later to capture live data during a road test if the concern acts intermittent.
2. Run a full network scan and verify the scan tool can communicate with both the CR and the ESC/ABS module. If the ESC module does not appear, treat this as a network or power issue first. If only the radar reports faults, keep the radar’s power, ground, and local harness high on the list.
3. Check fuses and power distribution that feed the CR (Corner Radar) and any shared chassis power circuits. Inspect for incorrect fuse ratings and heat damage. Do this before probing module connectors. A weak supply can create signal errors without blowing a fuse.
4. Verify CR power and ground with voltage-drop testing under load. Command an output, run a radar self-test, or keep the system awake to load the circuit. Measure voltage drop on the ground side while the module operates. Keep ground drop under 0.1V with the circuit loaded. Do not rely on continuity alone.
5. Inspect the CR connector and harness routing closely. Look for water intrusion, bent pins, terminal push-out, pin drag issues, and corrosion. Follow the harness to nearby clips and grommets. Pay attention to areas that flex or rub near bumper supports and body seams.
6. Identify the specific FTB suffix if your scan tool displays it and use it to guide the next test. For SAE J2012DA FTB examples, -11 points to short to ground, -12 to short to battery, -13 to open circuit, -1C to erratic/intermittent, -2E to not configured, and -31 to no signal. Treat the subtype as direction, not a confirmed failed part.
7. If the subtype or symptoms suggest a network problem, check CAN integrity at an accessible connector. With ignition OFF and battery disconnected, measure resistance between CAN+ and CAN- on the affected network at the CR connector or a convenient junction. A healthy network reads about 60 ohms. Readings near 120 ohms, very low resistance, or OL indicate an open or short that you must locate.
8. With ignition ON, verify CAN bias voltage at the same access point. Measure CAN+ to ground and CAN- to ground with the circuit powered. Healthy networks sit near 2.5V on both lines. Do not use ignition-OFF voltage readings as a reference because the bias only appears when modules power up.
9. Check for ESC message plausibility using live data. Compare CR live data items related to ESC status, vehicle dynamics, or network status to what the ESC module reports. Look for “not available,” “invalid,” or a status that drops out during steering input or bumps. If the scan tool supports it, log a snapshot while recreating the issue.
10. If wiring and network tests pass, verify configuration and module initialization. Check for recent alignment, radar aiming, bumper work, or module replacement history. Confirm the CR configuration matches the vehicle variant and that calibration procedures completed. A mismatch can create a “not configured” pattern without wiring faults.
11. Clear DTCs and perform a controlled verification drive. Recheck for pending versus confirmed behavior. Some faults require repeat conditions to confirm, while a hard wiring fault often returns immediately at key-on. Confirm the repair by ensuring C1693 stays cleared and ESC-related data remains stable in CR live data.

Professional tip: If C1693 returns immediately after clearing with key-on, treat it like a hard fault. Focus on power, ground, and bus integrity at the CR first. If it only returns while driving, use a scan tool snapshot and a harness wiggle test. Intermittent terminal tension problems often mimic an “ESC signal” issue.

Possible Fixes

• Repair power or ground feed to the CR (Corner Radar): Clean and tighten grounds, repair damaged wiring, and confirm low voltage drop under load.
• Restore CAN wiring integrity: Repair opens, shorts to ground, or shorts to power, then confirm proper resistance and ignition-on bias voltage.
• Service connectors and terminals: Remove corrosion, correct pin fit, replace damaged terminals, and add proper sealing where moisture entered.
• Correct module configuration and complete calibrations: Recode or configure the radar as required and perform aiming or initialization procedures per Hyundai service information.
• Repair the ESC/ABS module power or network issue: If the ESC module drops offline, correct its power/ground or network fault before condemning the radar.
• Replace the CR (Corner Radar) only after verification: Replace the module only after you prove correct power/ground, good network integrity, and correct configuration.

Can I Still Drive With C1693?

You can usually drive with C1693 on a Hyundai, but treat it as an ADAS stability-related fault. This code comes from the CR (Corner Radar) and references an ESC Signal error. That means the radar module cannot trust a stability-control related signal it expects to see. Your IONIQ 5 may still accelerate, brake, and steer normally. However, driver-assist features that depend on ESC status can reduce function or shut off. Drive conservatively and leave extra space. Avoid relying on safety assists until you confirm the fix. If the dash shows ESC warnings, braking feels abnormal, or the vehicle enters a reduced-assist mode, stop driving and diagnose it.

How Serious Is This Code?

C1693 ranges from inconvenient to safety-relevant, depending on what failed. If the CR only lost a valid ESC message, you may only lose some ADAS functions. If the vehicle also logs ESC-related chassis codes in other modules, the stability system may limit interventions. That changes how the vehicle behaves on wet or loose roads. Because this code sits in the chassis/ADAS space, do not ignore it. Also plan for calibration. After any corner radar removal, bracket work, bumper work, or module replacement, Hyundai ADAS systems often require calibration or initialization before they operate safely. Confirm proper operation with a scan tool and road test.

Common Misdiagnoses

Technicians often replace the corner radar after seeing “ESC Signal error.” That wastes money when the real fault sits in shared inputs. Another common miss involves ignoring the FTB suffix. For example, an FTB of -31 (No Signal) or -1C (Erratic/Intermittent) points you toward message presence and integrity, not a bad sensor. Shops also skip basic power and ground voltage-drop tests under load at the CR connector. A weak ground can corrupt message interpretation. Another trap involves bumper repairs. Paint thickness, bracket bend, or water intrusion can trigger repeated faults. Finally, some clear codes without checking if the ESC-related data PID returns and stays stable during a drive cycle.

Most Likely Fix

The most frequent confirmed direction involves restoring a clean, consistent ESC-related signal to the CR (Corner Radar). Start with connector and harness repairs at the radar and any inline connectors. Focus on terminal fit, corrosion, water tracks, and tension. Next, verify CR power and grounds with a loaded voltage-drop test. If the FTB suffix indicates -31 (No Signal), confirm the message appears on the network and that the scan tool shows valid ESC status in live data. If wiring and network checks pass, then consider CR initialization, software update, or module replacement followed by the required Hyundai calibration procedure.

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 10, 2026

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