Decode emulated device frame integers with explicit byte order
A synthetic device length reads as 512 instead of 2 because endpoints disagree on byte order. Specify and implement the format.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Binary protocols · Encoding
Estimated field mix
- Embedded and edge60%
- Networking40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
Fictional environmental-display devices send synthetic noncritical readings to a local gateway. Implement a byte-stream emulator; no physical device, radio, credentials or safety-critical control is involved.
Setup prerequisites
- Specify a small frame format with length sequence payload and checksum.
- Generate local byte streams with fragmentation corruption and reconnects.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Length and sequence use documented order
- Valid boundary values round-trip
- Truncated integer fields fail explicitly
Implementation constraints
- Use byte fixtures rather than host-native integer casts.
Verification to include
- Decode known two-byte values
- Provide truncated header
Deliverables
- Integer codec and format examples
Rollout and recovery
Reject frames from unknown format versions.
Value of the work
For the engineer: Practice incremental parsing, fixed resource limits and protocol recovery.
For the team: Inspect whether a device adapter survives malformed input without corrupting accepted readings.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.