| DTC Data Sheet | |
| System | Chassis |
| Standard | Manufacturer Specific |
| Fault type | General |
| Official meaning | Function restriction caused by safety functions for charging management mechanical |
| Definition source | Skoda factory description · Autel MaxiSys Ultra&EV |
C1249 means the Skoda Enyaq has limited part of its charging-related mechanical function for safety reasons. In plain terms, the vehicle sees a problem in the charging management system and responds by restricting operation rather than risking damage or an unsafe charging event. According to Skoda factory diagnostic data, this is a manufacturer-specific code for “Function restriction caused by safety functions for charging management mechanical.” On this platform, the 19-Gateway logged the condition, so the code points to a monitored system state, not an automatic verdict on one failed part. Diagnosis must confirm which input, actuator, wiring path, or network message triggered that safety restriction.
C1249 Quick Answer
C1249 tells you the Skoda charging management system has invoked a safety restriction tied to a mechanical charging function. The 19-Gateway recorded that restriction, so you need to verify the affected charging hardware, related inputs, and message integrity before replacing anything.
What Does C1249 Mean?
The official Skoda definition is “Function restriction caused by safety functions for charging management mechanical.” That means the vehicle did not simply see a minor fault. It saw a condition serious enough for the charging system to reduce or block part of normal operation. In practice, the Enyaq may limit AC charging, stop a charging session, refuse to release or lock charging hardware correctly, or store related warnings in multiple modules.
Technically, this code does not name a single failed component. It tells you the gateway recognized a safety-driven restriction in the charging management path. The module checks status information shared across the vehicle, including actuator feedback, charging lock or flap status where equipped, plausibility of related inputs, and networked fault states from other controllers. That matters because the root cause may sit in a mechanical actuator, its power or ground, a position signal, a connector issue, or a missing or implausible message on the vehicle network.
Theory of Operation
Under normal conditions, the Skoda Enyaq coordinates charging through several control units. The charging system monitors connector engagement, locking functions, actuator movement, and safety interlocks. The 19-Gateway acts as a central traffic manager. It receives status messages from the modules involved and stores faults when one system reports a condition that affects safe charging operation.
This code sets when a safety function limits a mechanical part of charging management. That usually means the vehicle expected a valid status or completed movement and did not get it. The fault can come from a mechanical bind, weak actuator operation, corrupted feedback, poor power or ground delivery, or a communication problem between modules. The key point is simple: the code reports a restriction decision, not the exact failed item that caused it.
Symptoms
You may notice one or more of these symptoms when C1249 is present on a Skoda Enyaq:
- Charging fault message appears in the instrument cluster or infotainment display during plug-in or charge start.
- Charge session refusal occurs when the vehicle will not begin charging even with a known-good charging source.
- Interrupted charging shows up as a session that starts, then stops after the system runs its safety checks.
- Mechanical lock issue may prevent the charge connector from locking or releasing correctly.
- Restricted function can affect charging flap or related mechanical charging hardware, depending on platform configuration.
- Stored related codes often appear in charging, body, or gateway modules alongside C1249.
- No obvious drivability change may occur while charging functions remain limited or unavailable.
Common Causes
- Charging-port mechanical binding: A sticking flap, latch, lock pin, or related moving part can trigger a charging-management safety restriction when the system cannot complete a mechanical action correctly.
- Misaligned charging inlet components: Poor alignment at the inlet or locking mechanism can make the Gateway register a restricted charging function because the commanded and actual mechanical states do not match.
- Connector corrosion or moisture intrusion: Corrosion or water at charging-management connectors can add resistance, distort status signals, and cause the Skoda control network to block charging functions for safety.
- Damaged wiring in the charging-area harness: Chafed, pinched, or partially open wiring near the charge port or body pass-through can interrupt feedback from the mechanical charging-management hardware.
- Weak power or ground supply to the related charging subsystem: A voltage supply issue or high-resistance ground can make actuators move slowly or sensors report implausible states, which then sets a restriction fault.
- Faulty position or status feedback from the mechanical charging assembly: An internal switch or sensor can report the wrong state even when the mechanism physically moves, leading the module to invoke a safety function.
- Intermittent network communication between involved modules: The 19-Gateway may log this code when a charging-related control unit drops messages or sends conflicting status information during a mechanical charging event.
- Software logic or adaptation mismatch: Incorrect coding, outdated software, or lost adaptations can cause the Skoda charging-management system to interpret a normal mechanical condition as a safety-related restriction.
Diagnosis Steps
Use a full-function scan tool, wiring diagram, DVOM, and a test light or other loaded test method. You also need service information for the Skoda Enyaq charging-management layout. If the concern appears intermittently, use both freeze frame and a technician-triggered snapshot. Freeze frame shows the exact conditions when the DTC set. A snapshot captures live data during your road or charging test.
- Confirm C1249 in 19-Gateway and record all stored, pending, and related charging or network DTCs. Save freeze frame data, especially battery voltage, ignition state, charge status, and any companion module faults. If your scan tool supports it, record which modules reported charging-related restrictions at the same time.
- Check fuses, power distribution paths, and the visible charging-system circuit path before any meter work. On the Enyaq, inspect the charge-port area, harness routing, and obvious signs of impact, moisture, or mechanical interference. If another charging-related module does not appear on the network scan, address that issue first because the Gateway may only report the downstream restriction.
- Verify power and ground quality at the involved charging-related control unit or actuator circuit under load. Do not trust unloaded voltage or continuity alone. Perform voltage-drop tests with the circuit operating. Ground drop should stay below 0.1 volt under load. A high-resistance feed or ground can pass a static check and still cause slow actuator movement or false status reporting.
- Inspect connectors at the charge-port assembly, nearby junctions, and any charging-management module in the service information path. Look for backed-out terminals, spread pins, corrosion, water tracks, poor terminal tension, and heat damage. Move the harness gently while watching scan data for the mechanical status to change unexpectedly.
- Use the scan tool to view live data for charging flap status, lock or unlock status, charge authorization state, and any mechanical position feedback that the Skoda platform makes available. Compare commanded states to actual states. A mismatch during actuation points you toward a circuit, sensor, actuator, or alignment problem rather than a Gateway failure.
- Command the relevant charging mechanical function, if bi-directional controls allow it, and observe whether the mechanism completes its travel cleanly. Listen for weak or repeated actuator attempts. If the mechanical action stalls, inspect for binding, misalignment, or a physical obstruction before condemning an electrical part.
- Test the suspect circuits directly. Check for opens, shorts to ground, shorts to power, and excessive resistance in the feed, ground, signal, or control wires. If the scan report included the FTB suffix -F6, treat it as subtype information only and use it to refine your test path. On this code family, it supports a more specific trouble-area direction but does not prove the failed part.
- If live data suggests a feedback fault, compare the mechanical position or status signal to the actual physical state of the inlet or lock mechanism. A switch or sensor can report locked when the lock pin never fully moved. Confirm the discrepancy with circuit tests before replacing the assembly.
- Check network integrity if related module communication faults accompany C1249. Verify that all involved modules stay present on the network scan during the event. For communication line voltage checks, measure with ignition on because bus bias voltage only exists when the circuit is powered. Follow Skoda service information for the exact network branch used by the charging subsystem.
- After repairs, clear the code and repeat the same charging event that set the fault. Confirm the mechanical action completes normally, live data agrees with the physical state, and C1249 does not reset. If the fault was intermittent, perform several key cycles and charging attempts. Compare the new results to the original freeze frame or snapshot to prove the fix.
Professional tip: Do not replace the Gateway first. In this Skoda fault path, 19-Gateway often reports a restriction that another charging-related component or circuit actually caused. Prove the power supply, ground quality, connector integrity, mechanical freedom, and feedback accuracy before you consider a module or coding issue.
Need HVAC actuator and wiring info?
HVAC door and actuator faults often need connector views, wiring diagrams, and step-by-step test procedures to confirm the real cause before replacing parts.
Possible Fixes
- Repair the verified wiring fault: Fix any open, shorted, pinched, or high-resistance wire in the charging-port or charging-management harness, then retest under the same operating conditions.
- Clean and restore connector integrity: Remove corrosion, correct poor terminal tension, address moisture intrusion, and secure connector fit where the charging mechanical system loses reliable feedback or control.
- Correct mechanical binding or misalignment: Adjust or repair the charging flap, inlet, latch, or lock mechanism if testing proves the commanded movement does not match the actual mechanical travel.
- Restore proper power and ground delivery: Repair the affected fuse feed, splice, ground point, or distribution issue if voltage-drop testing shows excessive loss under load.
- Replace the failed sensor, switch, actuator, or charging assembly only after confirmation: If commands, supplies, grounds, and wiring test good but the component still reports the wrong state or fails to move, replace the verified failed part.
- Update software or perform required coding and adaptation: If Skoda service information identifies a known software or adaptation issue, complete the update or relearn procedure and then confirm normal charging operation.
- Repair related network faults first: If another charging-related module drops offline or sends implausible status data, correct that communication issue before judging C1249 as a standalone fault.
Can I Still Drive With C1249?
You can usually drive a Skoda Enyaq with C1249 if the vehicle charges, shifts, and moves normally, but you should not ignore it. This code tells you the 19-Gateway has recognized a function restriction triggered by a charging management mechanical safety function. In plain terms, the vehicle has limited some operation because it sees a charging-related safety concern. That may only show up as reduced convenience, such as charging interruption or a warning message. It can also point to a condition that affects charge-port locking, charging authorization, or interlock logic. If the Enyaq shows charging faults, refuses to charge, displays red warnings, or limits drive functions, stop and inspect it before continued use. Do not force the connector, bypass a lock, or continue repeated charge attempts until you verify the cause.
How Serious Is This Code?
C1249 ranges from moderate to serious, depending on what safety function triggered the restriction. At the low end, it may act like a convenience fault. The vehicle may simply block charging until it sees a valid mechanical status. At the higher end, the code can reflect a real safety lockout involving charging hardware movement, lock position feedback, or interlock plausibility. That matters because Skoda uses protective logic to prevent charging under unsafe conditions. Treat it as more than a nuisance if the Enyaq will not release or lock the charge connector correctly, repeatedly aborts charging, logs related gateway or charging-system faults, or shows warnings tied to electrical safety. This is not an SRS code and not an ADAS calibration code, but any repair that touches charging control components still requires scan-tool verification and a successful charge cycle afterward.
Common Misdiagnoses
Technicians often misread C1249 as a failed charge port actuator and replace hardware before testing the circuit. That wastes time and money. The gateway only reports that a safety function restricted operation. It does not prove the mechanical unit failed. Another common mistake is ignoring companion faults in the charging control system and working from the gateway code alone. On the Enyaq, you need the full fault map, live status for charging lock or mechanical position, and basic circuit checks. Corrosion, connector drag, poor terminal tension, harness damage near the charge port, or low system voltage can all create the same complaint. Shops also miss intermittent faults because they do not load-test power and ground or monitor status while commanding the mechanism. Verify the input, output, feedback, and network message path before replacing any part.
Most Likely Fix
The most common confirmed repair direction is not module replacement. It is correcting a verified problem in the charging management mechanical path. That may mean repairing charge-port lock wiring, cleaning and tightening a connector, correcting poor power or ground delivery under load, or fixing a sticking mechanical latch after inspection confirms restricted movement. A second common direction is software-guided relearn or adaptation after repairing the underlying issue, followed by a complete functional check. If replacement becomes necessary, verify the command reaches the component, verify the feedback signal changes correctly, and confirm the gateway no longer logs C1249 through several charge connection and release cycles. The exact drive or charge conditions needed to confirm the repair vary by platform, so use Skoda service information to match the enable criteria.
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.
| Repair Type | Estimated Cost |
|---|---|
| Basic DIY inspection | $0 – $50 |
| Professional diagnosis | $100 – $180 |
| Wiring / connector repair | $80 – $350+ |
| Component / module repair | $120 – $600+ |
Key Takeaways
- C1249 on Skoda is a manufacturer-specific code, not a universal SAE meaning.
- The 19-Gateway reports a charging management mechanical safety restriction, not an automatically failed part.
- Start with related codes, live data, connector checks, and loaded power and ground tests.
- Do not replace a charge-port lock or actuator until command, feedback, and wiring tests prove the fault.
- Verify the repair with repeated charge connect and release events under the correct enable conditions.
FAQ
Does C1249 mean the charge port lock motor has failed?
No. C1249 does not confirm a failed actuator. It tells you the Skoda gateway saw a function restriction caused by a charging management mechanical safety function. The actual cause may be wiring damage, poor terminal contact, a sticky latch, invalid feedback, or a related control issue. Test command, power, ground, and position feedback before replacing anything.
Can my scan tool still communicate with the affected module if C1249 is stored in 19-Gateway?
Usually yes, but you need to confirm which charging-related modules still respond. Because the code sits in 19-Gateway, the gateway may be reporting a restriction seen elsewhere on the network. If communication with the charging module drops out, that shifts diagnosis toward network, power, ground, or module wake-up faults. If communication remains stable, focus more on mechanical status and circuit plausibility.
How do I confirm the repair after fixing the wiring or mechanism?
Clear the faults, then perform several complete charging connection and release events while monitoring live data for lock status, command state, and related safety inputs. The monitor only runs when the right conditions exist. Those enable criteria vary by vehicle and system. Use Skoda service information to confirm exactly when the fault test runs and when the repair passes.
Will C1249 keep the vehicle from charging every time?
Not always. Some Enyaq vehicles store this code after an intermittent mechanical or feedback problem, so charging may work sometimes and fail other times. That pattern often points to connector issues, temperature-sensitive resistance, latch drag, or harness movement near the charge port. Watch live data during repeated plug-in and unplug events to catch the fault when it happens.
Does a replacement charging-related module need programming on a Skoda Enyaq?
In many cases, yes. On this platform, replacement of gateway-related or charging-control components may require coding, parameterization, or guided functions with a factory-level scan tool or an equivalent tool that supports Skoda platform functions. After replacement, complete any required adaptation steps and then verify operation through a successful charge cycle and fault-free rescans.
