e92 emulator and tuning assistant

[enslaved87]

Hey all,

First time posting here, long time lurker. This has a somewhat narrow scope initially, specifically to the e92 family of ECM's to start. Some of this message below is the same message I've shared on other forums to try and get some help. Although, this seems like the most realistic place since you guys are doing the real work and have the knowledge base to work with.

I am working on a wide scope of programs to assist the community with tuning. At a high level - the program will ingest log data and your bin file from ecm, analyze it and output real values to then paste into hptuners.

Before you jump to conclusions - no, this is not some scam that plugs your inputs into chatgpt and gives you a BS semi-educated guess.

I have built a fully operational e92 and e92A hardware level emulator (HIL lab). This program takes your logged input, runs it against the REAL ve/vt/maf/et/idle, etc math exactly as GM designed it and provide outputs that are based in truth. No guesses. No 'try this and see what it does' stabbing in the dark.

My Goals, Rationale and Intentions behind undertaking this endeavor:

1) I want and expect ZERO compensation in any way, shape or form. Genuinly helping people is plenty payment enough.
2) Code contains ZERO IP and/or other people's work. Written in a clean room environment with significant local compute time dedicated to figuring out the e92 behaviors.
3) End goal is to make e92 tuning accesible to EVERYBODY who wants to partake. Not just the minority that has deep pockets or the technical edge that others may not possess.
4) intitial release will be compiled and obfuscated, and for only one reason - to get YOUR inputs on what you'd like to see improved and/fixed to ensure bad code doesnt get out into the wild.
5) Once beta is done and the foundation is solid, I will fully open source the project on git.
6) I have ~5 other program stacks I'm working in parallel to this one. They are all GM vehicle related, but all serve various other purposes. More to come as those near completion.
7) initital launch will not contain the emulator package, as there is no need for it once deployed to already characterized OS's.
8) HPtuners/EFIlive - whatever your tuning flavor, remains the path forward for actual tuning/reading/writing/interfacing with the vehicle, etc.
9) This is and will remain, a full tuning suite assistant backed with real math and a lot of hard work. I have zero desire (or need, quite frankly) to duplicate their efforts in the ecu reading/flashing department.
10) as a bonus, the hardwork has been done (for the most part) - additional ECU versions can be ported in with some work. But I will likely just let the community further development there.


I currently have these OS's fully integrated and turn key:
12696753
12682377
12686391
12678648
12699552

I need YOUR help to get this program as useful as possible for the community prior to alpha launch. I need more factory BINs - NOT hpt files, NOT ctz files, NOT BINs that have already been modified. If you have Factory e92 BIN files and would like to help the cause, feel free to PM me. Unsure if the Forum admin's like the idea of posting BIN files here - so I'd advise against that unless it's already a common occurence.

[ironduke]

Here's some E92's zipped up..
If it says stock in the filename it should definitely be stock.
If it doesn't say anything it is still likely stock.
If i accidently added anything that says something like DOD off, then it is NOT stock..
Looking forward to seeing your work with this.. Thanks for contributing!!!

E92 bin files.7z

E92 5 byte below.

E92 5 Byte.7z

[enslaved87]

You sir, are a gentleman and a Scholar.

This helps a great deal with the Truck side of things.

Camaro/Corvette/Cadi Bins are the meat of what I need next to round this out.

Many thanks, ironduke!

[enslaved87]

Anybody happen to have xdf/a2l, etc handy for e92 OS's?

Some of these OS's are written VERY differently. some have PACKED (scattered hex locations), while others have embedded grids. If not, I will chew threw it at the expense of my poor GPU's lol.

figured it's worth asking.

[Gatecrasher]

2017 Grand Sport OS

[Tre-Cool]

I've got a few e92's on in my stockpile. I've not even looked or offered to tune vehicles with these ecu's because im not willing to learn on someone elses property, unlike other local workshops.
Only car we get locally here is the Silverado 1500's & Gen-6 camaro's & they are expensive units here in Australia.

Plus i also hate the HPT interface with a passion, I'll be curious to see how you go with the project.

[enslaved87]

I've got a few e92's on in my stockpile. I've not even looked or offered to tune vehicles with these ecu's because im not willing to learn on someone elses property, unlike other local workshops.
Only car we get locally here is the Silverado 1500's & Gen-6 camaro's & they are expensive units here in Australia.

Plus i also hate the HPT interface with a passion, I'll be curious to see how you go with the project.

Couldn't agree more with you, on both fronts. I actually started down this road because all these companies and 'tuners' keep any uncovered information internal/behind pay walls. While it's GREAT that they offer the tools and equipment to get the job done - I am not a fan of keeping this type of stuff private. ESPECIALLY when I know NONE of it came from the OEM (the original IP owner(s)) - meaning they didnt pay for the right to do what they are doing - they methodically reverse engineered OEM's work and are selling the rights. A bizarre grey area for sure.

I am easily motivated by that behavior

Anyways, thanks for the grandsport bin Gatecrasher.

Keep'em comin' boys and girls.

[kur4o]

Tuning some abstract VE coefficients manually is a real pain if at all possible. Not sure how this emu works, but as long it works should be a great addition.

Some details what it does will be great.

I am not sure you are familiar with this program

https://github.com/joukoy/UniversalPatcher

It can log tune and do much more. Not many parameters are supported for e92, but that can change with some work.
And it is open source too, so you can adapt it the way you like.

[enslaved87]

Tuning some abstract VE coefficients manually is a real pain if at all possible. Not sure how this emu works, but as long it works should be a great addition.

Some details what it does will be great.

I am not sure you are familiar with this program

https://github.com/joukoy/UniversalPatcher

It can log tune and do much more. Not many parameters are supported for e92, but that can change with some work.
And it is open source too, so you can adapt it the way you like.

Appreciate the feedback. I am familiar with UniversalPatcher(and all others as well, im pretty sure). It's a very nice suite of tools! But as you mentioned, its still lacking in the e92+ world. I think i will be able to help them with that very soon once this goes live. Heres some high level higlights of current state:

TorqueModeler (TM) — community highlights (July 2026)

Open-source tuning workbench for GM E92 (developed on a 2019 Camaro LT1 + supercharger). It sits alongside HP Tuners VCM Scanner — load tunes and logs, analyze torque/airmass paths, and cross-check against real datalogs. Not a flash tool replacement; an analysis and modeling layer.

Core idea
• One app, one log — load a VCM Scanner CSV or HPL once; all assistants share it (shared_datalog.py).
• Load an HPT tune (.hpt) — auto-populates VVE, Virtual Torque, Driver Demand, MAF, ET, and Idle sections from the cal.
• E92 ECM math built in — bilinear table lookup, VE scaling, baro correction, and cross-links between modules (vehicle-specific tables extracted from your OS flash).


UI & workflow
• Basic / Advanced / Expert modes — progressive tab and config exposure.
• Session gating — assistants unlock as tune + log readiness is met (sensible dependency order).
• Coeff paste → auto tables — paste VVE/VTT coefficients; E92 backbone generates consistent 2D tables and cross-links.

Assistant modules (GUI tabs)
• VVE Assistant — volumetric efficiency zones, trims, coefficient ↔ table workflows; ties airmass truth to the log.
• Virtual Torque (VTT) — HPT-style graphical torque tables (spark grids, 2D/3D views); analyze log vs model with corroboration scoring (logged torque PIDs vs predicted virtual torque).
• Driver Demand (DD) — pedal/load demand editing with VTT context (community DD-editor lineage integrated).
• MAF Assistant — log MAF vs VVE airmass for calibration checks.
• Electronic Throttle (ET) — throttle-path analysis tied to the tune workflow.
• Idle Assistant — idle tables, drivability, impact vs VTT low-load torque reserve.
• Fuel / EQ — equivalence-ratio table support in the expert workflow.

Log & tune I/O
• VCM Scanner CSV — primary, production-grade log path (RPM, MAP, torque PIDs, inlet, baro, etc.).
• Direct .hpl import — channel catalog + numeric decode when decompress succeeds; shareable HPL export (stable zlib format for non-beta Scanner).
• HPT .hpt cal reader — pulls VVE/VTT/DD/MAF/ET/Idle sections into TM without manual xlsx paste.


E92 Emulator — highlights & capabilities


The E92 Emulator loads your BIN, predicts VE/virtual torque/spark/TMG behavior at any RPM/MAP/pedal point, replays whole VCM or CAN logs against logged torque PIDs, and scores fidelity — a bench virtual ECM for understanding what your tune and logs are actually doing.

Core engine
• Flash-backed tables — carves u16 cal surfaces from a full-read BIN (or in-memory “virtual flash” without writing the ECU).
• E92 ECM backbone — bilinear VE/VTT lookup, MAP scaling, baro-aware airmass, virtual torque % clamping.
• Optional tune overlay — inject your VVE / VTT / DD tables from TM assistants; emulator cross-links VE→VTT when both are loaded.
• Single-row prediction — predict_row(RPM, MAP, pedal, load) → VE, virtual torque %, torque source, power-reduction spark floor, engine-torque proxy (lb·ft), TMG ceiling hints.
• Full torque path — predict_torque_path() merges backbone prediction with driver demand → TMG arbitration state machine.

Spark & torque management (flash-resident)
• Run spark base — octane-blended MBT proxy (high ↔ low statistical surface).
• TMG spark pull stack — base − TMG pull − knock retard, then spark floor (power-reduction B5153 vs TMG bank vs stat-min).
• Immediate torque decreasing limit — 13×9 u8 bilinear rate-limit lookup from flash.
• Knock retard model — predicted knock-based timing pull.
• PE mode evaluation — power-enrichment channel gating.
• Rev-match / launch scalars — flash probes (where carved).

Log replay modes
• Arbitration replay — batch replay of driver / immediate / predicted / delivered torque PIDs through the arbitration model.
• Log oracle — row-by-row timing stack reconstruction + virtual torque vs logged torque channels (sampled for speed).
• Fidelity score (0–100) — weighted composite:
• timing stack residual
• TMG mechanism correlation
• torque source match
• engine-torque proxy error
• arbitration coverage
• HPT reference compare — workbook/slice compare against known VTT reference layouts.

[Tre-Cool]

hopefully all this follows on to the E99 used in the C8 platform. The latest release of the TCM tuning is now of interest, but I'm in no hurry to void my warranty just yet. but a twin turbo setup is definitely on the cards for the future.