justin/obdash
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

diagnostics: FICM healthy (>48V), ether-start signature narrows to ICP path

Browse Source 
- FICM measured >48V on M during cranking AND key-ON. Healthy. Removed
  as a suspect.
- Truck starts cleanly on starting fluid (ether) every time, then idles
  and runs normally until shut off -- then needs ether again, even when
  warm. This is a textbook signature for high-pressure oil (ICP) bleed
  during cranking that the HPOP can outrun at running RPM.
- Updated working hypothesis to focus on STC fitting / oil rail O-rings /
  HPOP / IPR. Compression, FICM, CMP/CKP, fuel supply all confirmed good
  by virtue of the engine running cleanly once started.
- Reordered open items to put visual inspection of valve covers + STC
  fitting first.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
Justin Paul
2026-06-29 21:51:58 -04:00
parent e15e22a825
commit 2fe3f1100e
2 changed files with 97 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files
handoff.md
+14 -7
View File
@@ -51,8 +51,12 @@ The 6.0 needs, to fire: **good batteries → FICM ~48V → ICP ~500 psi → fuel
- **2026-06-29 in-cab session:** added `--watch`, `--ford`, `--pid`, and `--scan`
modes. Captured cranking voltages + ran a Mode-22 brute scan (46 PIDs hit).
Full session writeup + raw data in [diagnostics/2026-06-29-no-start/](diagnostics/2026-06-29-no-start/README.md).
**Headline:** not batteries, not fuel — almost certainly ICP / FICM / CMP.
**Unfinished:** FICM meter test on M/S/L was started but readings never logged.
**Headline:** FICM measured >48V (healthy). Truck **starts on ether every
time** and runs/idles fine until shut off — then needs ether again. That
signature ⇒ **high-pressure oil (ICP) bleed-off during cranking** — STC
fitting / oil rail O-rings / HPOP-related. Compression, FICM, CMP/CKP,
fuel supply all confirmed good. Next: visual under valve covers + STC
fitting inspection.
- Pushed to `git.jpaul.io/justin/ford-obd`, branch `main`. Files: `obd_reader.py`,
`RUN_OBD.bat`, `README.md`, `README.txt`, `handoff.md`, `diagnostics/`.
@@ -63,11 +67,14 @@ no-crank, hot vs. cold, what changed before it died, and FICM/ICP readings if yo
## To resume from the desktop (after the 2026-06-29 session)
Read [diagnostics/2026-06-29-no-start/README.md](diagnostics/2026-06-29-no-start/README.md)
first — that's the full state. Top open items:
1. Get FICM M/S/L meter readings (key-ON and during a short crank).
2. Re-probe the clean scan hits (1310, 1440-1451, 11Bx) with `--pid XXXX`
for uncontaminated data, then map them to known engine conditions.
3. Look at FORScan via the CyanLabs mirror to capture ground-truth PIDs.
first — that's the full state. Top open items, in order:
1. **Visual under valve covers + STC fitting** — looking for the high-pressure
oil bleed source. That's where the diagnosis lands.
2. Re-probe the clean scan hits (`1310`, `1440-1451`, `11Bx`) with `--pid XXXX`
for uncontaminated data; map them to known engine conditions to identify
ICP / IPR.
3. FORScan via the CyanLabs mirror once available — ICP and IPR live data
would confirm a high-pressure leak in seconds.
## Open follow-ups (when off the truck)
- FORScan from the CyanLabs mirror once forscan.org is back — useful as the