scan

Have a folder full of files from cars' computers, and no idea which is which? scan reads every file in a folder in one pass and sorts each one into a group.

It is like a post-office sorting machine for ECU files: each file is checked against everything OpenRemap knows, then placed into one of five boxes — fully identified, family known but version missing, claimed by several extractors, unknown, or wrong file type.

The best part: by default it only previews — it shows you what it would do and moves nothing until you say so.

When do I need it?

• Organising a big collection. You have hundreds of dumps; you want them sorted into manufacturer/family folders so you can find one later.
• Triaging a batch. Which files are supported? Which are suspicious? Which are junk? One command, one report.
• Before a project. A tidy library makes identify/cook/tune much easier to run on the right files.

Try it (2 minutes)

First, the safe preview — nothing moves:

openremap scan ./my_bins/

You will see one line per file with its outcome: SCANNED, SW MISSING, CONTESTED, UNKNOWN or TRASH. When the results look right, actually sort the files:

openremap scan ./my_bins/ --move --organize

--organize builds the tidy manufacturer/family tree (for example scanned/Bosch/EDC17/). Files are never overwritten — if a name is taken, a counter is appended (file__1.bin, file__2.bin, …).

Understanding the answer

Identified files also carry a confidence tag: [HIGH] looks like an original factory file, [SUSPICIOUS] means something raised a red flag (like a filename containing "stage" or "remap"). A tag is a hint — run identify on a flagged file to see the full reasoning.

For developers

The same batch classification is one method of openremap.api — but the API only classifies and reports; it never moves files. Moving is a terminal-only feature:

Where to go next