An LF animal-identification reader can show a plausible number while the receiving application stores a different string or fails to find the animal record. The procurement question is not only whether the transponder can be energized. It is whether the specified reader and interface deliver an identifier that the application can parse and match without changing its meaning.
This guide follows the output path from an ISO 11784/11785 transponder to a business record. It complements LF RFID 125 kHz and 134.2 kHz Compatibility, which addresses RF and protocol compatibility. It does not claim that an AIDC GO handheld includes an LF animal-identification reader.
Separate the transmitted code from the displayed number
Microchip's ATAN0086 explains the standards boundary: ISO 11784 defines the code structure and information content, while ISO 11785 defines transponder activation and transfer to the transceiver. Its FDX-B example uses a 128-bit telegram containing an identification-code section, CRC and trailer. A reader may validate and decode that telegram before presenting a shorter human-readable identity.
That presentation is another layer. A reader screen may separate the transponder type, country or manufacturer code and remaining identifier. A host interface may send one continuous decimal string, delimited fields, binary values or a vendor-specific message. Procurement therefore needs the exact output specification, not only an image of a successful read.
Identify the code authority and expected field boundaries
ICAR's device registry reflects its role as the ISO registration authority for ISO 11784/11785 animal-identification devices and records manufacturer codes, product codes, technology such as FDX-B and ranges of RFID digits. ICAR's country-code guidance also distinguishes authorized country-code use from manufacturer-code use. Those governance rules matter when deciding what the leading digits mean; they do not define the local database key by themselves.
The business system may store the full international identity, a national presentation format or an internal animal number mapped to the transponder. The Allflex RS420 manual is one bounded reader example that separates transponder type, country/manufacturer code and identity digits on its display. Document which representation is authoritative. Do not remove leading zeros, change numeric bases or discard a prefix merely because two screens appear to refer to the same animal.
Use Replacing a Damaged RFID Tag when the project must change the transponder-to-record relationship. A successful read of the replacement does not by itself approve the mapping.
Follow one complete editorial example
Consider an editorial test animal whose approved record contains a full 15-digit electronic identity. The reference reader shows the technology, a three-digit leading code and the remaining number in separate fields. Its USB export sends the same digits as one string. The receiving application is configured to look up the full 15-digit value, but an early parser converts the value to an integer and removes a leading zero.
The RF read has succeeded, yet the lookup fails because the application changed the identifier. The correction is not to rename the tag or invent a second animal record. The team preserves the raw interface message, parses the documented fields as identifiers rather than quantities and compares the resulting full value with the authoritative record.
This is an editorial example, not a customer result or a statement about a particular AIDC GO device. The exact field order, delimiters, byte order and display format must come from the named reader and software version.
Compare evidence at every output layer
| Output layer | Evidence to retain | What it does not establish alone |
|---|---|---|
| Known transponder | Approved identity and documented FDX-B or HDX type | It does not establish that the candidate reader supports that transponder. |
| Reader decode | Read status, technology and decoded identity fields | It does not establish what the host interface transmitted. |
| Host message | Exact bytes or text, delimiters, terminator and interface version | It does not establish that the application parsed the fields correctly. |
| Application value | Parsed identifier before database lookup | It does not establish that the identifier is mapped to the correct animal record. |
| Business record | Matched record, mapping authority and acceptance evidence | It does not establish that every permitted transponder format follows the same path. |
A pass joins all five rows. Comparing only the reader display with an application screen can hide truncation, base conversion, character encoding or a mapping change between them.
Use controls that reveal silent formatting errors
Test at least one known-good FDX-B sample and, where the candidate explicitly supports it, one known-good HDX sample. Preserve their authoritative identities before testing. Include values that exercise leading zeros and field boundaries. Capture the screen, raw host output and application lookup result for the same scan event.
Also use a bounded negative control: a known tag outside the configured reader support or a correctly read identifier absent from the test database. The candidate reader may return no data rather than a precise diagnostic. Record "no valid reader output" when that is the observed fact; do not infer an unsupported protocol, failed antenna or bad tag from silence alone.
For application input behavior after the reader produces text, use Barcode Scanner Integration Methods as a general interface reference. Its keyboard, Intent and SDK distinctions do not prove LF-reader compatibility.
Keep display formatting out of identity decisions
Separators, spaces and labels can improve readability, but the transformation must be reversible and documented. If the UI shows only the final digits, retain the full identity elsewhere and make the abbreviated display explicit. If reports export a different presentation, test that import and reconciliation do not create duplicate animals.
Do not use the transponder's country or manufacturer code as an unverified species, ownership or location field. ICAR's country-code guidance concerns authorization and uniqueness within the standards framework; the project's animal record still needs its own controlled business attributes.
Bring the output contract to the purchase discussion
Provide the exact transponder examples, their approved identities, required FDX-B or HDX support, reader model and firmware, host interface, sample raw messages, application/parser version, database key format and expected exception behavior. State whether operators need the full identity on screen, in a file or through an SDK.
Ask for the reader's ISO 11784/11785 scope, output protocol, field layout, delimiter and terminator settings, supported host interfaces and a versioned integration guide. Use Integration & Support to frame the interface questions, then contact AIDC GO with the exact tags, country, workflow and acceptance records.
The decision is complete only when one known transponder produces the correct full identity at the reader, host, application and authoritative animal record. A beep or a plausible display number is useful evidence, but it is not the whole data path.