Creating and Inspecting Synthetic Byte Tables
This synthetic example shows how a user-selected range and dimensions shape a rectangular view. It does not reveal that the bytes are an ECU map or what any row, column or value means.
From a bounded region to a table
A selected byte range becomes a table view
Hex bytes at zero-based decimal offsets become a rectangular view only after a user chooses a range and dimensions.
Raw sequence
- Offset 0
0AOutside range - Offset 1
14Selected - Offset 2
1ESelected - Offset 3
28Selected - Offset 4
32Selected - Offset 5
3COutside range
Selected range
Start at zero-based offset 1; take 4 consecutive bytes through offset 4.
- Offset 1
14 - Offset 2
1E - Offset 3
28 - Offset 4
32
The starting offset and range are supplied by the user.
Dimensions
2 rows × 2 columns
4 cells use the selected values in order, row by row.
Table view
| Row | Column 1 | Column 2 |
|---|---|---|
| 1 | Offset 114 | Offset 21E |
| 2 | Offset 328 | Offset 432 |
Text equivalent
The synthetic sequence has 6 bytes at zero-based offsets 0 through 5: 0: 0A; 1: 14; 2: 1E; 3: 28; 4: 32; 5: 3C. The selected range is Offsets 1–4, containing 14 1E 28 32. The 2-row by 2-column table uses those values in order, row by row; each table cell repeats its source offset.
What the map tools contribute
- Map Extractor validates supplied hexadecimal or decimal bytes, then applies the chosen dimensions to format them as a table. The user provides the region and shape; extraction is not semantic boundary detection. It supports CSV and JSON downloads and a handoff to Map Viewer. A handoff does not preserve an absolute source-file offset.
- Map Viewer displays supplied values in a table and supports local input/recent-map storage, in-session undo/redo, and CSV, JSON or SVG downloads. Its share URL contains the values and labels, is readable by recipients and browser history, and is limited to 8,000 characters. A viewed or edited shape does not establish map identity; values are not written back to an original binary by this view.
- Map Definer records a user-selected byte range, dimensions and optional names/labels, and can preview, copy its definition JSON or send values to the Viewer. This is a supplied definition, not an automatically discovered or verified map. Its JSON format is not the Map Profile Loader schema.
Axis labels can help describe a synthetic exercise, but they are user-supplied metadata. Naming columns “load” does not show that the bytes encode load values. A display multiplier and unit offered during extraction are also descriptive metadata; exported byte values remain raw.
Continue through the concepts
The guide to synthetic byte tables and map concepts walks through the larger sequence. The next lesson applies percentage and offset arithmetic to byte tables in Byte-Table Scaling: Percentages, Offsets and Clamping. Neither a rectangular shape, plausible label nor transformed value proves a real ECU map, its purpose, compatibility or safe use.
Progress is self-reported and stored in this browser.