Code database
The Database keeps the codes you have read, so you can find a module's memory again and reuse it. Every read is saved automatically.
What is stored
- Every read — each time a module is read, its pages are saved.
- Chains — the pages of one module are linked together into a chain, keeping a
complete record of that module.
- A backup before writing — a copy is taken before a module is written, so the
previous state is always recoverable.
Searching
Find a saved module by:
- vendor and part or serial numbers,
- module type and standard,
- wavelength,
- a HEX pattern in memory.
Why it helps
When you meet the same module again — or a compatible one — you can pull a known-good dump from the database instead of building it by hand. Combined with the Editor, it makes repeat work fast and repeatable.