Vehicle Identity
Record-anchored
Deterministic data
Pre-sale fault timestamps
CPO Case #24691
This page documents records, dates, and technical outputs. Claims are anchored to artifacts — not assumptions. The full interactive diagnostic report is available at formant.ca/p/odis.
Documents Referenced
- VW ODIS Diagnostic Log — Guided Fault Finding session, November 17, 2025. Contains fault memory entries with individual embedded timestamps and odometer readings per fault. View Interactive Report →
- CPO Response Letter — March 17, 2026 — Bibiana Bernal, Consumer Services Officer, Manitoba Consumer Protection Office. CPO Case #24691. View PDF
- CARFAX Car Care Report — Timeline anchors including entries at 2025-09-10 and 2025-09-19.
- VW Recall 37M2 — Selector lever park-position interlock recall. Directly adjacent to fault B116229.
- Bill of Sale — September 17, 2025. Odometer baseline 173,045 km.
- Bumper Vehicle History Report — Multiple MPI-reported incidents referenced in CPO letter.
Chronological Timeline
- October 8, 2024 — 156,662 km: C113B00 (Hill Descent Control Button fault, ESC module, Address 0003) recorded in ECU fault memory. This is the oldest dated fault in the scan — 11 months and 16,383 km before the sale.
- May 30, 2025 — 170,346 km: B147A18 (Remote Key 2 — Insufficient Current) recorded as active/static — confirmed present at scan time. Logged 3.5 months before sale.
- June 24, 2025 — 170,999 km: U112300 (CAN data bus error) recorded in Access/Start module (Address 00B7). 59 occurrences. Logged 2.5 months before sale.
- July 17, 2025 — 171,778 km: B116229 (Selector lever park position lock switch — implausible signal) recorded. Frequency counter: ×135. Logged 2 months before sale. Subject of VW Recall 37M2.
- August 19, 2025 — 172,641 km: B147918 (Remote Key 1 — Insufficient Current) recorded. Logged 4 weeks before sale.
- August 28, 2025: CARFAX record indicates front damage event while vehicle in dealership possession.
- September 10, 2025: CARFAX dealer entry — inspection or brake-related work performed.
- September 17, 2025 — 173,045 km: Sale executed. Bill of Sale signed.
- September 19, 2025 — 173,045 km: CARFAX entry at sale mileage, post-sale date window.
- November 2, 2025 — 175,858 km: U112300 recorded in Brake Electronics module (Address 0003). Post-sale.
- November 6, 2025 — 176,295 km: U140100 (Overvoltage — function restriction) recorded in Access/Start module. Post-sale.
- November 12, 2025 — 176,436 km: B132054 (Rear window regulator — no basic setting, active/static) recorded. Post-sale.
- November 17, 2025: ODIS diagnostic session performed. Scan reads accumulated fault memory — all entries above retrieved with their original embedded dates and mileage.
- March 17, 2026: CPO issues final response. Determines faults "do not reasonably demonstrate a failure before September 17, 2025."
CPO Response — Contradiction Analysis
The March 17, 2026 letter from Bibiana Bernal (Consumer Services Officer, CPO Case #24691) makes a technical determination about fault timing that contradicts the internal data structure of the ODIS document it reviewed. The following breaks down each claim against the record.
Contradiction 1 — Scan Date vs. Fault Date
"…the errors reported in the ODIS document in November 2025, including error B116229, do not reasonably demonstrate a failure in the vehicle before September 17, 2025…"
The record: The ODIS scan was performed in November 2025, but the scan does not generate fault data — it reads it from ECU non-volatile memory. Each fault entry in the ODIS log contains two separate data fields embedded by the ECU at the time of the event: an individual timestamp and an odometer reading. These fields are distinct from the session date.
The scan session date of November 17, 2025 is when the technician connected the tool. The fault entry for C113B00 contains its own embedded date of October 8, 2024 and its own embedded mileage of 156,662 km — written to ECU memory at the time the fault occurred, over a year before the scan was conducted.
The scan session date of November 17, 2025 is when the technician connected the tool. The fault entry for C113B00 contains its own embedded date of October 8, 2024 and its own embedded mileage of 156,662 km — written to ECU memory at the time the fault occurred, over a year before the scan was conducted.
Contradiction 2 — C113B00 Is Definitively Pre-Sale
"…do not reasonably demonstrate a failure in the vehicle before September 17, 2025…"
The record: C113B00 (Hill Descent Control Button — Brake Electronics module, Address 0003) has an embedded fault date of October 8, 2024 at 156,662 km. The vehicle was sold September 17, 2025 at 173,045 km. This places the fault 346 days and 16,383 km before the sale. This is not an inference — it is the timestamp the ECU wrote to memory when the fault was detected. It is the oldest fault in the scan by date.
Contradiction 3 — B116229 ×135 Is Not a Post-Sale Event
"…including error B116229, do not reasonably demonstrate a failure in the vehicle before September 17, 2025…"
The record: B116229 (Selector lever park position lock switch — implausible signal) carries a frequency counter of 135. This counter represents the number of separate ignition or drive cycles in which the ECU detected and re-logged this specific fault condition. It is a cumulative register in ECU memory.
The embedded fault date is July 17, 2025 at 171,778 km — eight weeks before the sale. The interval from sale to scan is approximately nine weeks (September 17 to November 17, 2025). For 135 events to have occurred entirely post-sale within nine weeks would require the fault to trigger on average more than twice per day, every single day — with no entries showing prior to sale in the fault memory. The embedded July 2025 date directly contradicts this interpretation. This fault is also the subject of VW Recall 37M2, which addresses the park-position interlock mechanism on this platform.
The embedded fault date is July 17, 2025 at 171,778 km — eight weeks before the sale. The interval from sale to scan is approximately nine weeks (September 17 to November 17, 2025). For 135 events to have occurred entirely post-sale within nine weeks would require the fault to trigger on average more than twice per day, every single day — with no entries showing prior to sale in the fault memory. The embedded July 2025 date directly contradicts this interpretation. This fault is also the subject of VW Recall 37M2, which addresses the park-position interlock mechanism on this platform.
Contradiction 4 — Filtered Display Does Not Alter Underlying Data
(Implicit in the CPO's treatment of the ODIS document as a November 2025 snapshot rather than a fault memory readout)
The record: ODIS display filters (e.g., "active only," "stored only," "all faults") control which entries are shown in the interface. They do not modify, delete, or rewrite the underlying ECU fault memory. The data is deterministic — the same fault memory read on a different day or through a different display filter produces the same entries, because the source is the ECU's non-volatile storage, not the diagnostic tool.
Characterizing the ODIS output as representing only what was occurring in November 2025 misunderstands the architecture. The tool is a reader. The ECU is the recorder. The fault memory contains a history — not a snapshot of the session date.
Characterizing the ODIS output as representing only what was occurring in November 2025 misunderstands the architecture. The tool is a reader. The ECU is the recorder. The fault memory contains a history — not a snapshot of the session date.
Contradiction 5 — Technical Determination Without Technical Expertise
"It is important to note that the Consumer Protection Office analyses evidence to the best of its abilities and in accordance with the principles of administrative justice; however, we do not possess technical expertise in specific fields or industries."
The record: The CPO explicitly disclaimed technical expertise in automotive diagnostics, then proceeded to make a technical determination about when fault events occurred relative to the sale date — a determination that requires understanding the difference between a scan session date and an individual fault entry timestamp within the ODIS data format. The disclaimer and the determination are in direct conflict within the same letter.
The appropriate response to lacking technical expertise, when technical data is the core of the dispute, is to obtain technical interpretation — not to apply a lay reading and issue a determination on that basis.
The appropriate response to lacking technical expertise, when technical data is the core of the dispute, is to obtain technical interpretation — not to apply a lay reading and issue a determination on that basis.
The finding that faults "do not reasonably demonstrate a failure before September 17, 2025" is not consistent with the fault data in the document reviewed. C113B00 at October 8, 2024 @ 156,662 km is a pre-sale fault by its own embedded timestamp — 16,383 km before the sale. That entry exists in the same ODIS document the CPO reviewed.
Diagnostic Summary — What the Scan Shows
The ODIS scan identifies four cascading failure patterns. These are not isolated faults — they are interconnected failure chains with shared root causes. The full interactive analysis is at formant.ca/p/odis.
- Transmission Mechatronic Contamination — P2B9F00 (Coolant Pump B underspeed, captured at 97°C with full ambient data) feeding into B116229 ×135 (park position lock switch). This is the documented signature of VW MQB platform mechatronic sleeve contamination, the subject of VW Canada class action proceedings affecting 2017–2019 Jetta, Golf, Tiguan, and Passat with Aisin 09S/09G transmissions.
- Cascading Electrical System Failure — U140100 overvoltage event triggering U112300 CAN bus errors across three separate modules (59 and 22 occurrences). Downstream: key fob current faults (B147918, B147A18 active/static), alarm/immobilizer undefined state (B131DF7), seat heater safety circuit tripping (B1399F0), window regulator active fault (B132054).
- Thermal Management Failure — Auxiliary coolant pump running below spec at 97°C (normal idle: 85–92°C). Risk of turbocharger heat damage and contribution to mechatronic contamination chain above.
- Brake Electronics / ESC Fault — C113B00 (oldest fault, October 2024, 16,383 km pre-sale) plus subsequent U112300 in the same module linking it to the electrical cascade.
ODIS captures electronic and electrical system state only. Physical and mechanical inspection — brake wear, suspension, fluid condition — is not represented in this data and requires separate assessment.
Inspection Integrity
- Electronic governance reality: This vehicle's safety-relevant systems — transmission park lock, ESC/ABS, steering column lock, key/immobilizer — are electronically governed and self-reporting. When these systems carry active or high-frequency fault states, visual inspection alone cannot verify their operational status.
- Tool neutrality: A Manitoba Certificate of Inspection does not require ODIS specifically. It requires that safety outcomes were verified. The mechanism of verification is secondary. The question is whether the electronic safety states were confirmed as operational at the time of certification.
- Recall 37M2: B116229 is directly adjacent to the park-position interlock mechanism addressed by VW Recall 37M2. A safety certification issued while this fault was present at ×135 frequency warrants an audit of the certification basis.
- Auditability: If a certificate was issued, the basis for its issuance should be reproducible and documented. The CARFAX entry at sale mileage (173,045 km) immediately post-sale is a date intersection that requires record-based explanation, not assumption.
The dispute is not about which diagnostic tool was used. The dispute is that electronically monitored safety outcomes must be verified when the system is defined by electronic self-monitoring — and that verification must be documented.
Requested Audit Actions
- Obtain technical interpretation of the ODIS fault entry data format — specifically the distinction between session date and individual fault entry timestamps — before issuing a final determination on fault timing.
- Address C113B00 at October 8, 2024 @ 156,662 km directly: this entry predates the sale by its own embedded timestamp. Explain the basis on which the CPO concluded faults do not demonstrate a pre-sale failure.
- Address B116229 ×135 in context of Recall 37M2 and the frequency counter's cumulative nature.
- Audit the inspection certificate for this VIN: worksheet, basis for pass determination, and documentation of how electronically monitored safety states were verified.
- Cross-reference certification date against internal service records and the CARFAX entry at 173,045 km.
Public Note
This archive exists to prevent narrative drift. Every claim on this page is anchored to a document or data field. If any party disputes a claim, the correction path is simple: provide record-based counter-evidence that can be appended alongside the original artifacts.
The ODIS data is deterministic. Changing the display filter does not change what the ECU recorded. The timestamps and mileage figures in each fault entry were written by the vehicle's own control modules at the time the faults occurred. They are not generated by the diagnostic tool and are not affected by how the tool's output is displayed.
Contact: [email protected] · Interactive Diagnostic Report · CPO Letter — March 17, 2026
Disclaimer: This page is documentation and factual commentary based on collected records. It is not legal advice.
Part of a record archive hosted on Formant.
Return to formant.ca