Tool · Map Editors
Map Profile Loader
Supply a profile and matching byte sequence to preview offset-selected values. The profile does not identify a vehicle or establish what the data means.
1. Load profile JSON
Paste a JSON profile with an ecu name and a maps array. Each map needs a name, byte offset, rows and columns; axis labels, unit, scale, notes and version are optional. No file upload is supported.
Supported format: this tool’s JSON driver profile schema. Unknown properties and invalid types are rejected.
2. Provide matching source bytes
Paste whitespace or comma separated hex bytes (00–FF), including bytes from offset zero. Maximum 16,384 bytes; processing stays in this browser.
Validation checks this JSON structure and whether selected ranges fit the supplied bytes. It does not confirm that a definition identifies a real ECU map, gives correct scaling, or is safe to modify or use.
Worked example
Apply an offset-addressed profile to synthetic bytes
Input
Supply bytes from offset zero:
10 20 30 40 50 60 70 80Operation
The profile names the selected range with required fields name, offset, rows and cols. The ecu property is a required text label supplied by the user.
{
"ecu": "Example label",
"maps": [{
"name": "Example range",
"offset": 2,
"rows": 2,
"cols": 2
}]
}Output
Offset 2 and 2 × 2 dimensions select four values: offsets 2–5.
| Row | Column 1 | Column 2 |
|---|---|---|
| 1 | 30 | 40 |
| 2 | 50 | 60 |
What this tells us
The loader checks that the profile schema is supported and that the selected range fits the supplied bytes. Optional names, labels, units and scale values are profile metadata.
It does not infer a profile from bytes or verify the label, map identity, scaling, vehicle compatibility, or calibration safety.