Vår blogg

RFID / Barcode Interoperabilitet

bc-RFID

Den här artikeln är lite mer teknisk än de flesta av vad vi lägger ut, men vi tyckte att det skulle vara användbart att dela med andra.

When customers order EPC-GEN2 Type UHF RFID tags from us, they often want a product that also has both a human readable number as well as a barcode. And in their mind the electronic number should match the barcode and printed number. In most cases, they do not need to implement the EPC Tag Data Standard to ensure each of their UHF RFID tags are unique among the billions of tags around the world. They just care that the number is unique in their system.

Below is an example of an UHF RFID tag that shows the different technologies used in a tag – with matching numbers for all technologies.

  1. UHF RFID (visas i blå skugga) - Snabba lagerförmåga, förmåga att hitta ett objekt
  2. Streckkoder (1D och 2D) - Möjlighet att läsa ett visst nummer som pekas på av en läsare - det här är svårt att göra med en RFID-läsare eftersom flera taggar ofta läses samtidigt.
  3. Tryckt textnummer - för att människor ska kunna läsa utan utrustning.
tagg exempel
Full 96 Bit / 12 Byte UHF RFID-data representation

However, in most cases, customers don’t want such a long number. They prefer a short and easy to read number as is shown in the next image:

kort data representation
Kort data representation

So what do we do in these cases with the UHF RFID tag number, which is always 96 bits? Telaeris has an internal data standard that allows us to read a number of different UHF RFID tags standards simultaneously, supporting both long data types and short data types.

  1. If the data is string data XCHARX such as something you could type on a keyboard XCHARX we encode this as a string and put it at the front of the 12 bytes and fill the last bytes (minimum of 2) with zero values. This is our preferred encoding and it is good for up to 10 characters which covers most of our use cases. For a chart showing the mapping from string characters and their hex representations, Klicka här.
  2. Many of our partners encode the data at the end of the 12 bytes. If we find zero values at the start (minimum of 2), we assume it is using this type of encoding and display the data as hex data.
  3. Om båda dessa strukturer misslyckas, standardiserar vi de råa data och visar den som 23 hex-data tecken.

Detta visas genom exempel nedan:

Kodningstyp 1: 
54  33  35  30  30  30  00  00  00  00  00  00 
'T' '3' '5' '0' '0' '0' <---- Nollvärden --->
<------- Data --------> <---- Nollvärden --->
Kodningstyp 2:
00  00  00  00  00  00  00  00  0A  12  34  56
<--------- Zero Values ---------><--- Data -->

Kodningstyp 3:
11  22  33  44  55  66  77  88  99  00  AA  BB
<------------------- Data ------------------->

Can there be problems where these assumptions cause overlap? Yes, but they are few and far between. And in our experience, having a shorter to read number will ultimately provide the end customer with a better overall user experience.

Av David Carta, Telaeris VD

Lämna en kommentar

*

Blogguppdateringar

nyhetsbrev


prata med en representant

Kontakta Oss

Telefon: 858-627-9700
Fax: 858-627-9702
-------------------------------
9123 Chesapeake Dr.
San Diego, Kalifornien 92123
-------------------------------
sales@telaeris.com