我们的博客

RFID /条形码互操作性

BC-RFID

这篇文章比我们提出的大多数文章更具技术性,但我们认为与其他人分享是有用的。

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标签数据标准 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(以蓝色阴影显示) - 快速库存能力,能够找到物体
  2. 条形码(1D和2D) - 能够读取读者指向的特定数字 - 这对于RFID读取器来说很难做到,因为通常会同时读取多个标签。
  3. 印刷文字编号 - 供人们在没有任何设备的情况下阅读。
标签示例
完整的96 Bit / 12 Byte UHF RFID数据表示

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:

短数据表示
短数据表示

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, 点击这里.
  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. 如果这两个结构都失败,我们默认为原始数据并将其显示为23十六进制数据字符。

这通过以下示例显示:

编码类型1: 
54  33  35  30  30  30  00  00  00  00  00  00 
'T''3''5''0''0''0' <----零值--->
<------- Data --------> <----零值--->
编码类型2:
00  00  00  00  00  00  00  00  0A  12  34  56
<--------- Zero Values ---------><--- Data -->

编码类型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.

作者:Telaeris CEO David Carta

发表评论

*

博客更新

新闻简报


与代表交谈

联系我们

电话:858-627-9700
传真:858-627-9702
-------------------------------
9123切萨皮克博士
San Diego, CA 92123
-------------------------------
sales@telaeris.com