CRC Register Bit Reflection
Reflect exactly the supplied CRC register word width, including leading zeros; distinct from reciprocal-polynomial coefficient reversal.
Description
Reflect exactly the supplied CRC register word width, including leading zeros; distinct from reciprocal-polynomial coefficient reversal.
Reflecting a CRC register reverses a fixed number of bit positions, including leading zeros in that width.
When to use this tool
Reflect exactly the supplied CRC register word width, including leading zeros; distinct from reciprocal-polynomial coefficient reversal.
- Prepare the supplied register, width fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter register, width. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.register. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require width 1 to 128 and a nonnegative register below 2^width. Read each bit from low to high while shifting it into the reflected integer; return decimal text.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| register | Exact decimal integer text; keep it quoted in JSON rather than converting through a floating-point number. | Optional leading + or - and 1 to 256 decimal digits; no whitespace |
| width | width. | Integer from 1 to 128 inclusive |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.register | The register value under the stated formula or text convention. |
{
"input": {
"register": "3",
"width": 4
},
"output": {
"result": {
"register": "12"
}
}
}Limitations and assumptions
- This reverses register bits without performing CRC division, selecting parameters or reversing byte order.
- All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
- JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.
Alternative or Complementary methods
Use the complete specified checksum algorithm and independent test vectors when verifying a payload. Field packing, parameter shape and arithmetic agreement are separate checks; none supplies cryptographic authenticity.
References
Similar or alternative tools
- CRC Parameter Record Audit
Audit explicit CRC parameter width evidence under the omitted-leading-coefficient convention; no CRC computation, polynomial quality or catalog identification.
- CRC Polynomial Degree Check
Audit the degree and constant coefficient of a full CRC GF(2) polynomial integer including its leading coefficient; not an omitted-leading-bit parameter.