Protocol scope and method
Only bytes between frame delimiters are escaped. The tool does not add a checksum unless you use the frame builder.
7e → 7d02; 7d → 7d01; reverse in the opposite direction.
Diagnostic scenario
Use payload mode on bytes between the frame delimiters. Escape a known payload containing both 0x7e and 0x7d, reverse it, and confirm that the original byte sequence is restored before combining the operation with checksum and framing logic.
How to interpret the result
The output changes byte length because reserved bytes become two-byte sequences. BCC belongs to the unescaped content but is itself escaped if its value requires it. The tool deliberately does not add delimiters or generate a checksum.
Input reference
- Mode
- Example default: Escape payload
- Hex input
- Example default: Sample input included
Common mistakes
- Using an unredacted production capture with vehicle, credential or network identifiers.
- Escaping an already escaped payload a second time.
- Treating a successfully parsed sample as standards compliance or interoperability proof.
Before using the result
- Confirm the protocol edition, transport framing and vendor profile before interpreting fields.
- Round-trip a payload containing both reserved byte values.
- Keep a redacted known-good and known-bad sample as a regression pair.
Questions to check during diagnosis
Does the JT/T 808 Escape & Unescape leave my browser?
No application upload is used. Avoid putting sensitive production data in shareable URLs.
Is this a standards compliance test?
No. Confirm the edition and vendor profile with licensed documents and your target platform.
Offline diagnostic aid. Verify fields, version and vendor extensions before production use.