SYSTEM_AUDIT: PROJECT BLACK PEARL

by

// SYSTEM_AUDIT: PROJECT BLACK PEARL //

SUBJECT: EJ205 + TD04 CALIBRATION STRATEGY

You have successfully mapped the user journey from “Start” to “Calibration Data.” To align the technical backend with the Forensic/Cyberpunk aesthetic, the following refinements are required for the EJ205 load model and subaructl integration.

01_TECHNICAL_AUDIT // THE LOAD MODEL

The Throttle vs. RPM table is the “Forensic Core” of this system. For the Mitsubishi TD04, the scaling must respect physical hardware constraints:

  • The TD04 Plateau: On the 2.0L EJ205, peak boost hits early, but volumetric efficiency falls off a cliff past 5,500 RPM.
  • Load Calculation Correction: Your “System Interpretation” should explicitly state that Calculated Load (g/rev) will drop at high RPM—even at 100% throttle—as the turbocharger reaches its flow limit.

Forensic Guardrails:

  • Transient Logic: Incorporate a section for Throttle Tip-in Enrichment. This is the primary failure point for “jerky” DIY tunes.
  • IDC Criticality: With factory 440cc injectors, an 11.2 AFR target at 7,000 RPM approaches the 90%+ Injector Duty Cycle (IDC) danger zone if pushing 12+ PSI.

02_ANALYSIS_INTEGRATION // SUBARUCTL_V3

The analyze_telemetry snippet is the foundation of your automated framework. To elevate it to “Forensic-Grade,” implement a Calculated Engine Load Validator:

Load (g/rev)=RPMMAF (g/s)×60​

Logic Gate: If the logged MAF deviates from the target Load table by >5%, subaructl should trigger a CRITICAL_WARNING for boost leaks or MAF scaling corruption before the user proceeds to timing adjustments.

03_UX_VALIDATION // CREDIBILITY LAYERS

To maintain the “Pro” forensic feel of the Revision Log (v1.3.1):

  • The Ultimate Judge: In Step 4 of the “Process Framework,” emphasize IAM (Ignition Advance Multiplier). If IAM <1.0, the protocol has failed; if IAM =1.0, the system is validated.
  • Hardware Parity: Ensure the MAF Housing Warning is prominent. A mere 1mm variance in intake diameter can shift fueling by ~10%, moving the engine from a safe 11.5 AFR to a catastrophic 12.6 AFR.

04_DEVELOPMENT_ROADMAP // SCALING THE STACK

With the Audi A3 (8P) and the WRX in your stable, the roadmap raises a strategic question:

  • Cross-Platform Expansion: Is “Black Pearl” evolving into a multi-platform protocol (e.g., adding MED9.1 support for the Audi), or is it remaining a specialized Subaru/EJ205 ecosystem?
  • Deployment Vector: Will the subaructl engine be distributed as a Local Python CLI tool for privacy-conscious tuners, or a Web-based Telemetry Uploader for broader accessibility?

// STATUS: READY FOR REVISION_V4 //
// LOGIC_GATE: OPEN //

🛠️ The Calibration Revision Log (v1.4 – TD04 Edition)

We have optimized the maps to capitalize on the TD04’s lightning-fast spool.

FeatureLogic GateTarget Outcome
Idle Management875 RPM TargetBalanced for CAI airflow noise and catless exhaust pulse.
Boost Target12 PSI (Tapering)Peak 12 PSI hit @ 3,200 RPM, tapering to 9.5 PSI @ 6,000 RPM.
WGDC ScalingDynamic Comp.Aggressive Wastegate Duty Cycle (WGDC) for 0-lag spool.
Throttle ResponseTip-in EnrichmentRefined to prevent lean spikes during rapid “blip” maneuvers.
Thermal StrategyFan Trigger (-5°C)Early cooling to manage the TD04’s higher intake temps under load.

Deploying the TD04 Response Protocol

💻 The Linux Workflow (Terminal Method)

Using the subaructl logic framework, we deploy the flash via the terminal. This ensures that the TD04-specific boost control tables are written with 100% integrity.

./black_pearl_deploy.py –rom impreza_td04_stage1_response_875.bin –mode write

📊 System Diagnostics: The TD04 Profile

The diagnostic metrics show the classic TD04 “Punch” profile, optimized for safe 12 PSI street use:

  • Target Boost: 12.0 PSI (Quick Hit, Linear Taper)
  • WOT AFR: 11.2 – 11.4 (Slightly richer for TD04 thermal safety)
  • IAM / DAM: 1.0 (Rock Solid)
  • Knock Correction: 0.0 (Clean timing ramp)

“Speed isn’t just about peak numbers; it’s about how fast you get there.” By raising the idle to 875 RPM, we’ve smoothed out the transition from off-throttle to boost, making the car feel 500lbs lighter in city traffic.

🏁 Final Assessment

The car is now a “Response King.” The TD04 hits peak boost almost instantly, and the 875 RPM idle provides the stability needed for the intake and catless exhaust to coexist without stalling or surging.

Next Phase: Fueling stability testing and Injector Duty Cycle (IDC) audit.

Leave a Comment