Responder ID Scanner
Offline Windows app for the Toughbook CF-33 that decodes PDF417/AAMVA IDs, with no automatic PII storage, no telemetry and no network services.
Release
Section titled “Release”Release details
- Version
- TBD
- Platform
- Windows on Panasonic Toughbook CF-33
- Language
- Python
- UI
- Tkinter
- Tests
- pytest
- Packaging
- PyInstaller
- Network
- None
Source: Project repository (link TBD)
Give responders a fast, offline way to read the PDF417 barcode on a driver license or state ID and see the AAMVA fields on screen, without the data ever leaving the device unless the operator chooses to export it.
Constraints
Section titled “Constraints”- Hardware: Panasonic Toughbook CF-33 running Windows.
- Offline only: no network services and no telemetry.
- Privacy: no automatic persistence of personal information. Exports are explicit and operator-initiated.
- Stability: changes are small and isolated, with regression tests and release candidates, so the stable core is never broken.
Privacy statement
Section titled “Privacy statement”The Responder ID Scanner does not store scanned personal information automatically, does not send telemetry, and does not open network connections. Data leaves the app only when the operator explicitly exports it. All screenshots and examples on this site use synthetic sample IDs, never a real license or a real person.
Architecture
Section titled “Architecture”The diagram for this section will show the data flow below.
Scanner hardware ─► Input capture ─► PDF417 payload ─► AAMVA parser ─► Tkinter display │ Explicit export (operator action only)Parts list
Section titled “Parts list”| Part | SKU | Price paid | Key specs | Source | Status |
|---|---|---|---|---|---|
| Panasonic Toughbook CF-33 | TBD | TBD | TBD | TBD | TBD |
| Barcode scanner hardware (model TBD) | TBD | TBD | TBD | TBD | TBD |
Configuration
Section titled “Configuration”- Dependencies: to be listed from the project’s requirements file.
- Build settings: PyInstaller spec settings to be documented from the repository.
- Runtime settings: to be documented.
Build steps
Section titled “Build steps”- Set up the Python environment and install dependencies.
- Run the pytest suite.
- Build the Windows executable with PyInstaller.
- Install the release candidate on the CF-33 and test with synthetic IDs.
Testing and verification
Section titled “Testing and verification”| Area | Status |
|---|---|
| Automated tests (pytest) | Results not yet published |
| Packaged build (PyInstaller) | Not yet documented |
| Physical scanner on the CF-33 | Not yet documented |
Each release will report test results, packaging status, privacy checks, physical-scanner status and the rollback path.
Safety notes
Section titled “Safety notes”- Use synthetic sample IDs for every test, screenshot and demo.
- Treat any real scan as sensitive data. Do not export unless there is an operational need.
Lessons learned
Section titled “Lessons learned”None recorded yet.
Open items
Section titled “Open items”- Decide whether the repository will be public, and add the link.
- Add the current release version and test summary.
- Document the scanner hardware model and input method.
- Produce synthetic sample IDs for screenshots.
- Add the start date.
Changelog
Section titled “Changelog”Project page published.
Rollback: Revert the commit that added this page.