By iCarsoft Official Store Technical Team, Automotive Diagnostics Editors · Updated September 23, 2026 · OEM technical references checked
Quick Answer
The C001C code means right rear inlet control. It does not prove a faulty right-rear wheel-speed sensor or a need to replace the whole ABS unit. Save the scan, identify the exact architecture, and test the physical and electrical paths before selecting a repair.
What Does the C001C Code Mean?
The C001C code means Right Rear Inlet Control. It names a monitored result, not a guaranteed failed part. The reporting module, suffix and companion faults determine the relevant test branch.
The right-rear inlet branch belongs to the hydraulic modulator on a conventional ABS system. A control fault in that branch is not the same as an inaccurate wheel-speed input. The full controller description and subfault determine what can be tested externally and what requires the manufacturer’s internal actuator procedure.
Right rear means the vehicle’s right-rear corner, but hydraulic-unit port routing must still come from its diagram. Do not identify a circuit by the nearest visible brake pipe or by where the unit sits in the engine bay. Incorrect routing assumptions can turn a useful fault description into testing the wrong branch.
Mitsubishi maps GST C001C to C104F-04, the right-rear ABS IN valve, in its 2023 Outlander PHEV service information. This is a limited application example, not proof that every scanner or brake controller uses the same alias, wiring or repair strategy.
When several inlet or outlet codes appear after a low-voltage event, start by preserving their order and checking the shared supply under the service procedure. A common event can explain why those checks come first; it does not prove that the battery is the sole cause or that every valve is damaged.
Save the full module wording and suffix before clearing; they can change the test path.
Separate C001C from adjacent fault families
| Code | General description | Key distinction |
|---|---|---|
| C001C | Right Rear Inlet Control | Inlet-control branch at the right rear. |
| C001D | Right Rear Outlet Control | Different valve role at the same corner. |
| C001E | Right Rear Hydraulic Release Too Long | Different response/timing monitor. |
| C0018 | Left Rear Inlet Control | Opposite rear corner. |
Record the complete C001C description. The suffix, reporting module and companion faults can change the diagnostic path. Use the manufacturer's full wording and test procedure for the exact vehicle.
C001C Symptoms and Likely Causes
C001C symptoms depend on fault status and the fallback strategy. Record what the driver and modules reported. A symptom list is not a parts list.
Compare current and history faults with the original conditions. Test a suspected shared cause rather than assuming every companion code needs a separate part.
The controller may flag a fault without a distinct sensation at the right-rear wheel. The lamp is an alert to diagnose, not a location test.
Record actual messages and related-module codes. Assistance availability cannot be inferred from a normal low-speed drive.
A cluster may make supply or connector checks relevant. It does not establish simultaneous internal valve failure.
Any leakage, drag, pull or altered pedal requires a safety inspection separate from interpreting the stored control code.
Practical cause-checking order
- Complete fault identity: Confirm C001C, its suffix and the reporting module before selecting the right-rear inlet branch.
- Shared supply and connection: Test shared unit power, ground and connector integrity under the specified conditions; do not judge a loaded circuit only from an unloaded reading.
- Electrical control evidence: Follow the inlet-control electrical or actuator test without substituting a wheel-speed comparison.
- Physical response evidence: Investigate any real hydraulic or wheel-end symptom through a separate approved branch instead of assuming it is caused by the code.
- Module and service information: Review matching service information, component compatibility and setup requirements before an internal-unit conclusion.
Did C001C appear after recent brake, battery, harness or hydraulic-unit service? Recheck the documented connections, parts and setup steps affected by that work. Record battery and software history; a post-repair code does not prove the new part is defective.
How Serious Is C001C, and Can You Drive?
An ABS or stability warning needs prompt professional diagnosis even when the pedal seems normal. Do not assume emergency braking assistance remains available. If pedal effort or travel changes, braking pulls, a wheel drags, fluid leaks or a red brake warning appears, stop safely and arrange recovery. No safe driving distance can be inferred from the code.
Record brake warnings, pedal changes, fluid loss and recent service. Do not induce wheel slip or emergency braking to test assistance on public roads; warning-state assessment comes before any functional verification.
Stop and arrange a tow if pedal feel changes, stopping is impaired, fluid leaks, a wheel drags or a red brake warning appears.
Brake circuits can retain pressure, and electrically controlled brakes can operate unexpectedly. Secure the vehicle and follow the exact shutdown, isolation and pressure-release procedure before touching hydraulic components. Never release a pipe to investigate a hot or dragging wheel, apply battery power to a valve, or trigger ABS on a public road as a diagnostic experiment.
How to Diagnose C001C in the Right Order
-
Save the inlet-control fault cluster
Save all accessible brake and related-module codes with suffixes, status and available event data. Record recent battery, hydraulic-unit or rear-brake work. Preserve the original order before clearing so shared faults remain distinguishable from faults introduced during testing.
-
Identify the correct right-rear circuit
Use VIN-specific documentation to map the right-rear inlet branch and hydraulic-unit ports. Confirm the installed controller and actual fault wording. Do not choose a wire, pipe or component merely because its physical position seems to match the wheel named in the code.
-
Check common feeds and grounds
Inspect relevant terminals and harness locking after the required isolation. Perform the specified supply and ground tests and inspect protection devices as directed. Multiple valve-control records justify investigating a common path, but only measurements can confirm the cause.
-
Evaluate the inlet-control branch
Follow the exact subfault routine. Where supported and prescribed, use the authorized active test and record its response. A scanner showing that a command was sent cannot establish that the electrical load and hydraulic response were correct.
-
Confirm any separate wheel-end fault
If the driver reports drag, heat or changed pedal feel, obtain a professional brake inspection before moving the vehicle further. Keep mechanical and hydraulic findings distinct from inlet-control evidence. Avoid direct-power tests or opening a line to provoke a change.
-
Complete setup and verify the original event
Repair the demonstrated cause, restore connections and complete required bleeding or configuration. Verify safe stationary braking before any approved road check. Repeat the fault-specific confirmation procedure and retain a final scan showing the tested conditions and results.
Specifications are vehicle-specific. Use the exact VIN specifications, approved test points and required operating state. No generic value or drive cycle can replace the applicable procedure. Manufacturer examples here do not establish specifications for other applications.
C001C Repairs and Cost Planning
The correct C001C repair follows the failed test. Wiring, a physical repair, a proven component, software and controller work are different outcomes. Do not replace an assembly from the generic code alone.
Recheck installation and required setup after repair. Replacing an integrated actuator does not automatically complete its configuration or bleeding requirements. Confirm the procedure before authorizing the part so the quote includes the work needed to restore braking.
Ask the shop to name the failed branch and the measurement supporting each proposed repair.
Authorize diagnosis before parts while the cause remains uncertain.
| Possible path | Quote basis |
|---|---|
| Repair a connector, feed or ground after its test fails | VIN-specific quote |
| Repair the proven hydraulic or mechanical brake fault | VIN-specific quote |
| Replace the confirmed component using the VIN-specific parts procedure | VIN-specific quote |
| Complete required bleeding, initialization and brake verification | VIN-specific quote |
These are alternative repair paths, not prices to add together. Request a VIN-specific quote separating diagnosis, parts, labor, fluids, taxes, required setup and verification. Ask which failed test supports the proposed repair and whether warranty coverage applies.
Using iCarsoft CR Eagle P for C001C
On a supported vehicle, iCarsoft CR Eagle P can retrieve accessible module faults, save available freeze frame, display ECU-provided live data and create a diagnostic report. For C001C, preserve the original evidence and compare related modules before clearing an erasable record.
Compare available brake-controller records before and after repair. The report supports diagnosis but cannot replace the OEM physical and functional checks.
Preserve the right-rear inlet control evidence
iCarsoft CR Eagle P
Review supported codes and relevant live data together. Confirm the exact VIN, controller access, PIDs and any requested active test with iCarsoft before purchase; generic product capabilities do not guarantee a C001C-specific function.
Check current CR Eagle P price and availabilityCheck CR Eagle P compatibility by VINThe official product page describes supported full-system diagnostics, available live data, freeze frame and diagnostic reports; exact controller coverage and active tests depend on the VIN and software. Confirm the requested function by VIN before purchase. Follow OEM prerequisites and stop for abnormal operation.
Know the measurement boundary. Scan data describes ECU-provided information; it does not directly prove the physical condition of the right-rear inlet control. Where required, use the specified electrical test equipment and, only where required, approved brake-pressure equipment and compare reported values with the relevant measured evidence.
Verify the C001C Repair
After repair, verify connectors, harness clearance, setup and controller supply. Save post-repair findings, then clear only erasable records through the approved procedure. Battery disconnection is not a repair.
Run the manufacturer's applicable verification conditions in a safe workshop or route. Compare the original operating state with current data for the right-rear inlet control, and check current and pending faults in related modules. One clean start or idle period does not prove that every conditional monitor has completed.
Compare the original and final scans, including fault status, operating conditions and required setup. Record whether the monitor completed and whether the original event returned.
If C001C returns, compare its suffix, status, failure order and operating conditions with the saved baseline before replacing another part. Revisit the failed branch and inspect anything disturbed. Confirm the prescribed brake-system verification separately from code clearing.
Stored and Active brake-control faults require different decisions. Preserve the original record and follow the OEM confirmation procedure. A cleared display does not prove restored assistance or safe braking.
Related Right-Rear Inlet Control Code Guides
Use related-code pages to compare monitor families, not to merge repairs. A nearby code can share a component, circuit, fluid path or operating condition, but its diagnostic conclusion still depends on its own status, suffix and test evidence.
C001C Frequently Asked Questions
Does the C001C code mean the named component is bad?
No. C001C describes right rear inlet control, not a confirmed part. It also does not prove a faulty right-rear wheel-speed sensor or a need to replace the whole ABS unit. Use the OEM test sequence to distinguish the circuit, load and controller before replacing parts.
What should I check first for C001C?
Save every module's codes and freeze frame before clearing. Confirm the full definition, suffix and VIN architecture. Then inspect recent brake, battery, harness or hydraulic-unit service, connectors and shared supplies. Those facts determine whether the next test needs the specified electrical test equipment and, only where required, approved brake-pressure equipment or a manufacturer-specific functional procedure.
Can I drive with the C001C code?
An ABS or stability warning needs prompt professional diagnosis even when the pedal seems normal. Do not assume emergency braking assistance remains available. If pedal effort or travel changes, braking pulls, a wheel drags, fluid leaks or a red brake warning appears, stop safely and arrange recovery. No safe driving distance can be inferred from the code.
Why did C001C return after a part was replaced?
The original shared connection, supply weakness or configuration issue may remain. Replacing a wheel-speed sensor does not establish a repair for an inlet-control fault unless the exact OEM test tree tied that sensor to the event.
What should a C001C repair estimate include?
Ask for the failed-test evidence and a VIN-specific breakdown of diagnosis, parts, labor, taxes, required setup and verification. A code alone cannot establish the repair price.
Can CR Eagle P diagnose and clear C001C?
On a supported vehicle, CR Eagle P can organize available faults, freeze frame, live data and reports, and can clear erasable records after repair. Confirm exact ECU coverage. It cannot establish safe braking from an erase command or replace physical measurements for the right-rear inlet control.
The iCarsoft Official Store Technical Team maintains the store's fault-code library. This guide organizes published manufacturer evidence and verified product information; it does not document a hands-on test of a particular vehicle or claim an individual engineer's review.
Technical and cost references
- NHTSA DOT HS 812 574 — Hydraulic Braking System Appendices, Appendix K. Selected standardized chassis-code descriptions; not a VIN-specific test procedure.
- Mitsubishi TSB-23-35-002 — 2023 Outlander PHEV service manual revision. GST-to-OEM brake-control mapping for the named model only.
Product information: Official iCarsoft CR Eagle P page.
Editorial note: General diagnostic education, not a substitute for the owner's manual, current VIN-specific service information or professional inspection. Test limits, procedures, coverage and costs vary. Related articles provide context; apply only the specifications and repair procedures that match the vehicle. No universal failure rate, repair price or outcome is implied.
