Quick answer
First check that both systems read the same complete identifier. A hexadecimal string, an unsigned decimal number and a reversed byte sequence can display differently. Agree on the bytes, their order and the output format before changing readers or customer records.
The worked examples explain software handling. They are not reader measurements or proof of card authentication. Sources and scope · Read our editorial method
An old attendance system and a new USB reader may show different numbers for the same card. Before replacing hardware, identify what each number represents. A card activation identifier, a value stored in card memory and an application-assigned number need not be the same field.
Compare representations with explicit assumptions
The table uses two invented four-byte sequences. They are calculation inputs, not real card UIDs, manufacturer UID assignments or measured PR-301 output. Read each byte group from left to right. For the decimal column only, treat the displayed sequence as an unsigned big-endian integer: the leftmost byte has the largest weight. That convention is an example, not a universal NFC rule.
| Example interpretation | Byte sequence | Hexadecimal string | Unsigned decimal |
|---|---|---|---|
| A: original order | 01 23 45 67 |
01234567 |
19088743 |
| A: reversed byte order | 67 45 23 01 |
67452301 |
1732584193 |
| B: original order, zero retained | 00 01 02 03 |
00010203 |
66051 |
| B: reversed byte order | 03 02 01 00 |
03020100 |
50462976 |
For A, the original-order calculation is 1 × 256³ + 35 × 256² + 69 × 256 + 103 = 19088743. Hexadecimal and decimal strings can therefore differ while following an agreed interpretation of the same bytes. Reversing byte groups produces a different integer.
Download the four format-comparison rows. The column decimal_unsigned_be uses the convention above. Keep all reference fields as text when importing them; CSV quotation marks do not set the receiving software’s column type. For Excel storage and import checks, use the separate text and CSV article.
Keep byte order separate from character order
Reverse complete two-digit byte groups, not individual hexadecimal characters. Reversing the characters of 01234567 produces 76543210; this differs from the byte-reversed 67452301. A decimal string has no visible two-digit byte groups, so reversing its digits does not reverse the source bytes.
In B, an eight-character hexadecimal field retains the initial zero byte. The decimal text 66051 does not preserve that byte count by itself. Another invented sequence, 00 00 00 00 01 02 03, also evaluates to 66051 under the same convention, despite having seven bytes rather than four. Record the original byte length and the required output width separately. Do not guess missing bytes from an old decimal value or silently truncate a longer identifier to fit a legacy field.
NXP’s UID handling note gives no general rule for converting UID bytes into an integer. It also describes non-unique and random identifiers. If the captured identifier itself changes across presentations or resets, format conversion alone cannot explain or fix that change; check the card’s actual configuration and identifier source.
Capture a comparison before ordering samples
Use cards approved for the evaluation and label them without cardholder details. Record these four items for each comparison:
- The exact card protocol and the complete identifier bytes returned by each documented reading path, including byte count.
- Reader model, delivered firmware and mode, software version, representation, byte order, output width and any prefix or suffix.
- The text received by the application and the value it actually stores. Check for a mapped card number, whitespace or a numeric conversion.
- Expected and observed results after card removal, repeat presentation and reader reconnect. Record any changed identifier before choosing a transformation.
A matching example row only checks a formatting assumption. It does not establish card authenticity, identifier uniqueness or compatibility with your existing records.
Choose the reader around the required output
D-Logic lists HID, CDC ACM and UID-format configuration features for PR-301. Confirm the delivered mode, firmware and required setting with the actual sample; the manufacturer term “inverted” is not a substitute for a documented input/output pair. Our table does not predict a default PR-301 output.
Review the PR-301 USB model and the UID procurement checklist. The card-ID application connects identifier input to the receiving workflow. Protected memory operations and authentication need their own software and card requirements.
Discuss your expected card-ID format. Describe the old system’s documented format, desired output, target application, sample quantity and destination. Mark unknowns for review. Do not send card keys, passwords or personal cardholder records; the existing enquiry checklist is optional.
Sources and scope
Official references reviewed on 7 October 2026. The worked rows were checked as arithmetic and text fixtures; no card, reader or legacy system was tested for this article.
Questions to consider
Does a different displayed number prove that the reader is faulty?
No. Compare the actual identifier, byte count and agreed output format first. A representation difference, a mapped application number or a changing identifier needs a different diagnosis.
Can I reverse the printed characters to reverse the UID bytes?
No. Keep each two-digit hexadecimal byte together and reverse the byte groups only when that is the agreed transformation. Do not apply reversal to a decimal string.
