Decoding contracts and payload evidence

Knowledge check · self-test
Decoding contracts and payload evidence
Check the decoding contract: match field types to evidence, decode temperature and signed integers, and compare field layouts.
Check the decoding contract: match field types to evidence, decode temperature and signed integers, and compare field layouts.
Incremental Practice
Beginner
Decode the single byte 0x19 after confirming the notation is hexadecimal and the field is one byte wide. State the decimal value.
Intermediate
Decode the bytes 01 2C twice: once as one big-endian unsigned 16-bit value, and once as two separate one-byte fields. Note how the contract changes the meaning.
Advanced
Review a small structured payload with a numeric field, a text field, and a flag byte, and write a one-line contract for each before decoding.
Send one known negative, zero, and maximum value through old and new versions. Keep raw payload, width, signedness, byte order, scale, unit, firmware version, decoded result, and rejection reason.
You will explain how raw bytes become sensor values and identify the decoding rules that sender and receiver must share. Start with a payload and record its units, field widths, signedness, and byte order.
Back to From Bytes to Meaning: Extend the Contract to Text, Flags, and Schemas