blog kami

Interoperabilitas RFID / Barcode

bc-rfid

Artikel ini sedikit lebih teknikal daripada kebanyakan yang kami sampaikan, tetapi kami fikir ia berguna untuk dikongsi dengan orang lain.

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 Standard Data Tag EPC 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 (ditunjukkan dalam bayangan biru) - Keupayaan inventori cepat, keupayaan untuk mencari objek
  2. Barcode (1D dan 2D) - Keupayaan untuk membaca nombor tertentu yang ditunjuk oleh pembaca - ini sukar dilakukan dengan pembaca RFID kerana berbilang tag sering dibaca sekaligus.
  3. Nombor teks bercetak - untuk orang boleh membaca tanpa apa-apa peralatan.
contoh tag
Perwakilan data 96 Bit / 12 Byte UHF RFID penuh

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:

perwakilan data pendek
Perwakilan Data Ringkas

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, tekan di sini.
  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. Jika kedua-dua struktur ini gagal, kami lalai kepada data mentah dan memaparkannya sebagai aksara data 23 hex.

Ini ditunjukkan dengan contoh di bawah:

Jenis Pengekodan 1: 
54 33 35 30 30 30 00 00 00 00 00 00 
'T' '3' '5' '0' '0' '0' <---- Nilai Zero --->
<------- Data --------> <---- Nilai Zero --->
Jenis Pengekodan 2:
00  00  00  00  00  00  00  00  0A  12  34  56
<--------- Zero Values ---------><--- Data -->

Jenis Pengekodan 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.

Oleh David Carta, Ketua Pegawai Eksekutif Telaeris

Leave A Comment

*

Maklumat Blog

Surat berita


bercakap dengan seorang wakil

Hubungi Kami

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