Binary fingerprinting • intake lane 01

Drop the file in.
The forge reads the steel.

This lane is built to identify ECU files from the binary itself, not the filename circus. Upload a read and ECU-Forge will attempt to pull visible identifiers, classify the family and hand you back a clean ECU information panel.

MVP intake live UI-first build Analyzer hook ready

Drop ECU file or click to upload Random filename is fine. We care about the binary guts, not the fancy hat. Accepted for now: BIN, ORI, MOD, EEP, FLASH, HEX and whatever else you want to throw at the anvil.

No file selected Awaiting ignition

Heating forge 0%

ECU information

Awaiting analysis

Upload a file and strike Analyse file. For now this page can run in demo mode, and the UI is already wired so the backend can later return JSON into the same fields.

How this lane behaves

Built for your dev site first.

Matches the existing ECU-Forge header, glow, cards and forge palette.
Lives as its own route at /ecu-id/.
Uses a fake analyzer sequence now, ready for real backend wiring next.
Returns a result card styled from the panel you showed me, without looking bolted on by a drunken goblin.

What the backend will return

Core IDMake group, ECU family, manufacturer, processor.

IdentifiersHW, SW, version, ODX and visible metadata strings.

ConfidenceConfident, probable or unknown. No fantasy football scores.

Intake bridgePipe this into IMMO, tuning or solutions once identified.

Drop the file in.The forge reads the steel.

Drop the file in.
The forge reads the steel.