U173E – Occupant detection function restriction due to implausible message (Skoda)

Skoda-specific code — factory diagnostic data

U173E means the Skoda Enyaq has limited occupant detection because one control unit received a message that did not make sense. In plain terms, the vehicle may not trust seat occupancy information, so passenger restraint or related warning functions can operate in a restricted mode. According to Skoda factory diagnostic data, this is a manufacturer-specific code for occupant detection function restriction due to an implausible message. The code came from the 19-Gateway, which matters because the gateway monitors network traffic between modules. That means this fault points to a communication plausibility problem first, not proof that the seat sensor, airbag module, or gateway itself has failed.

U173E Quick Answer

U173E sets when the Skoda gateway sees occupant detection information that is present but not believable. Focus on the message source, network integrity, and power or ground quality before replacing any seat-related parts.

What Does U173E Mean?

The official Skoda definition is occupant detection function restriction due to implausible message. That means the vehicle did not simply lose communication. Instead, it received data tied to occupant detection and judged that data as inconsistent, out of range, contradictory, or otherwise not plausible for current operating conditions.

From a diagnostic standpoint, the 19-Gateway is checking message validity on the vehicle network. It looks at whether expected data arrives in the right format and in a believable state. That matters because occupant detection affects restraint decisions and system status reporting. The code does not identify the failed part by itself. It only tells you the gateway detected a suspect message path related to occupant detection.

Theory of Operation

Under normal conditions, the Skoda Enyaq exchanges occupant-related data between the seat system, restraint system, and other networked modules through the gateway. Each module sends timed messages with expected identifiers and logical values. The gateway routes and supervises those messages so other modules can trust the information they use.

This code appears when the message still exists on the network, but its content fails a plausibility check. That can happen if a module sends corrupted data, if voltage or ground problems distort operation, or if wiring and connector faults disrupt message quality without causing a full communication loss. A software mismatch can also create believable communication traffic with unbelievable content. That is why this fault demands message validation and circuit checks, not blind module replacement.

Symptoms

Symptoms usually involve network behavior, restraint warnings, and inconsistent seat occupancy status.

• Scan tool behavior: The scan tool may show intermittent communication issues, related gateway faults, or changing status in occupant-related data blocks.
• Warning message: The cluster may display an airbag, passenger restraint, or occupant detection warning.
• Function restriction: Passenger occupant detection may switch to limited operation or become unavailable.
• Status mismatch: Live data can show seat occupancy states that do not match the actual seat condition.
• Intermittent fault: The code may reset after a key cycle, then return when the seat is used or system checks run again.
• Stored companion codes: Other communication, plausibility, restraint, or seat-system faults may appear in related Skoda modules.
• Customer complaint: The driver may report a warning that appears with no obvious drivability issue, yet safety-system status has changed.

Common Causes

• Intermittent message fault from the occupant detection system: The 19-Gateway stores U173E when the data it receives from the occupant detection function does not make sense for current operating conditions.
• Low system voltage during module wake-up: A weak power supply can corrupt startup communication and create implausible network messages on the Skoda platform.
• Poor ground at a related control module: High resistance at a ground point can distort module operation and cause invalid or conflicting status data.
• Connector fit or terminal tension problem: A loose, spread, or partially backed-out terminal can interrupt message integrity without creating a complete communication loss.
• Harness damage in a seat or body wiring path: Flexing, pinching, or abrasion can affect signal quality and create intermittent plausibility faults tied to occupant detection data.
• Corrosion or moisture intrusion in a connector: Corrosion increases resistance and can alter the message stream enough for the gateway to reject it as implausible.
• Related module storing its own internal or plausibility DTCs: The gateway often reports the network symptom while the originating module stores the more useful root-cause code.
• CAN network disturbance: A partial short, skewed bias voltage, or poor bus integrity can let communication continue but corrupt message content.
• Coding, adaptation, or software inconsistency: Incorrect configuration or outdated software can make one module interpret occupant status data differently from another.

Diagnosis Steps

Use a scan tool with full Skoda module access, a quality digital multimeter, a test light, and wiring information. A lab scope helps with intermittent network issues. You also need terminal inspection tools and access to seat and body harness connectors. For this code, freeze frame and a road-test snapshot both matter.

1. Confirm U173E in 19-Gateway and record all stored, pending, and related DTCs across every module. Save the freeze frame. For this communication-type plausibility fault, focus on vehicle speed, ignition state, network status, and any occupant restraint or seat-related codes. Freeze frame shows the conditions when the gateway set the fault. A scan-tool snapshot is different. Trigger a snapshot during a road test if the fault acts intermittent.
2. Check whether all expected modules appear on the network scan before deeper testing. Then inspect power distribution. Verify relevant fuses, fuse feeds, and wake-up supplies for the gateway and any occupant detection related module. Do this before measuring at a control unit. If the suspected module drops off the scan intermittently, treat that as a primary clue.
3. Verify module power and ground under load. Use voltage-drop testing, not continuity alone. Load the circuit while testing. Ground drop should stay below 0.1 volt with the circuit operating. Check both the 19-Gateway feeds and the power and ground circuits for the module that supplies occupant detection data. A weak ground can support module wake-up but still corrupt message plausibility.
4. Inspect connectors and harness routing next. Pay close attention to seat-related wiring paths, body pass-through points, and any connector that shows movement, moisture, or previous repair. On the Enyaq, seat-area harness movement deserves close attention because repeated travel can stress terminals and insulation. Look for backed-out pins, spread female terminals, corrosion, and pinch damage.
5. Review live data from the gateway and from any accessible related module. Compare occupant status, seat occupancy information, plausibility flags, restraint status, and communication counters if the scan tool provides them. You want a mismatch pattern. If one module reports a stable occupant state while the gateway rejects that message, suspect wiring, network quality, coding, or the sending module.
6. Check for related DTCs in the originating module before condemning the gateway. The gateway often reports the receiving symptom, not the root cause. If another control unit stores internal faults, sensor plausibility faults, or power supply codes, solve those first. Per J2012 logic, the DTC identifies a trouble area. It does not identify the failed part.
7. Test CAN bus integrity if the data stream looks unstable or multiple communication codes appear. With ignition off and the battery disconnected, measure resistance between CAN+ and CAN- at an accessible module connector. A healthy bus reads about 60 ohms. A reading near 120 ohms or open loop points to an open conductor or missing termination. Then switch ignition on and check bias voltage to ground on both CAN lines. Healthy circuits sit near 2.5 volts. Ignition-off voltage readings do not give a valid reference.
8. Perform targeted wiggle tests while watching live data and network status. Move the seat through its range if service information permits and observe whether occupant-related values drop out, freeze, or become implausible. Flex harness sections and connectors one area at a time. If the fault sets during movement, isolate that exact section before any part replacement.
9. Verify coding and software status if the wiring and network tests pass. Compare installed equipment, coding, and adaptation values to service information. A configuration mismatch can make valid data look implausible to the gateway. On Skoda vehicles, software issues can also create message interpretation faults without a hard circuit failure.
10. Confirm the repair by clearing all codes, cycling ignition, and repeating the operating conditions from the freeze frame. Run another full network scan. Then road test the vehicle and capture a snapshot if needed. Make sure U173E does not return as pending or confirmed. A hard communication fault usually returns quickly. An intermittent plausibility fault may need a longer validation drive.

Professional tip: Do not replace the gateway first just because it set U173E. On Skoda systems, the gateway often acts as the messenger. The real problem usually sits in the sending module, its power or ground, or the harness path between the seat area and the rest of the network.

Possible Fixes

• Repair a verified power or ground fault: Clean and tighten the affected connection, repair the feed or ground path, and confirm proper voltage-drop under load.
• Repair connector or terminal damage: Correct backed-out pins, poor terminal tension, corrosion, or moisture intrusion at the affected module or harness connector.
• Repair damaged harness sections: Fix open, shorted, pinched, or high-resistance wiring in the verified occupant detection or network path, then retest message stability.
• Correct CAN network faults: Repair the bus open, short, or bias problem only after resistance and ignition-on voltage checks prove the issue.
• Update or correct module coding or software: Recode or reflash the affected control unit when testing shows the hardware and circuits are sound but message plausibility remains invalid.
• Address related module faults first: Resolve stored DTCs in the module that originates occupant detection data before considering any gateway action.
• Replace a module only after confirmation: Replace the sending module or, less commonly, the gateway only when circuit integrity, power, grounds, network health, and configuration all test good.

Can I Still Drive With U173E?

You can usually drive a Skoda Enyaq with U173E, but you should not ignore it. This code tells you the 19-Gateway received an implausible message related to the occupant detection function, so the vehicle may restrict that function until the signal becomes believable again. That matters because occupant classification affects restraint strategy and related warning logic. The vehicle will often remain drivable, and you may notice no engine or braking problem. Even so, treat this as a safety-related network fault, not a convenience issue. If the airbag or passenger restraint warning lamp is on, stop treating the system as fully reliable. Arrange diagnosis with proper Skoda-capable scan equipment before regular use.

How Serious Is This Code?

U173E ranges from moderate to serious, depending on what other faults appear with it. By itself, it often means the occupant detection function has limited operation because message content does not match what the gateway expects. That can be a temporary communication plausibility problem, a power or ground issue, or a disagreement between modules after low voltage or disturbed connectors. If no restraint warnings appear, the fault may act like a restricted feature with little effect on drivability. If restraint, passenger airbag, or occupant status warnings appear, treat the safety system as potentially compromised. Diagnosis then requires the correct Skoda service information, a full-function scan tool, and a technician with restraint-system training. Do not attempt DIY repairs on safety restraint wiring or connectors. If any related module replacement or coding becomes necessary, the Enyaq may also require setup, adaptation, or guided functions before the system can be trusted again.

Common Misdiagnoses

Technicians often misread U173E as proof that the occupant detection sensor mat, seat module, or gateway has failed. The code does not prove that. It only reports an implausible message on a Skoda network path. Another common mistake is skipping basic electrical checks because the fault sounds software-related. Low system voltage, poor grounds, loose under-seat connectors, recent interior work, or harness tension near the seat frame can corrupt message content and trigger a plausibility fault. Some shops also clear the code, see it stay gone briefly, and return the car without checking live data or running the conditions that enable the monitor. Avoid wasted spending by checking all related module DTCs first, verifying powers and grounds under load, inspecting seat-area wiring carefully, and confirming whether the gateway can communicate consistently with the relevant module before replacing anything.

Most Likely Fix

The most common repair direction is not module replacement. It is correction of the cause behind the implausible occupant-detection message. On a Skoda Enyaq, that often means repairing a poor connection, terminal fit problem, harness damage, or power and ground issue affecting the seat or restraint-related module that supplies occupant status data. A second common repair direction is software correction or module setup after battery events, seat removal, interior repairs, or prior module work, but only after network integrity checks pass. After the repair, clear faults and verify operation during a complete drive cycle or use pattern that allows the relevant monitor to run. Enable criteria vary by vehicle and system, so consult Skoda service information to confirm exactly when the fault logic runs and when the repair counts as proven.

Repair Costs

Network and communication fault repairs vary by root cause — wiring/connectors are often the source, but module-level repairs or replacements can be significantly more expensive.

Last updated: April 11, 2026