nuestro blog

Interoperabilidad RFID / Código de Barras

bc-rfid

Este artículo es un poco más técnico que la mayoría de lo que publicamos, pero pensamos que sería útil compartirlo con otros.

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 Estándar de datos de etiqueta 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. RFID UHF (se muestra en la sombra azul): capacidad de inventario rápido, capacidad de encontrar un objeto
  2. Códigos de barras (1D y 2D): capacidad para leer un número específico al que apunta un lector: es difícil hacerlo con un lector RFID, ya que muchas etiquetas se leen a la vez.
  3. Número de texto impreso: para que las personas puedan leer sin ningún equipo.
ejemplo de etiqueta
Representación completa de datos 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:

representación de datos cortos
Representación de datos cortos

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, haga clic aquí.
  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. Si estas dos estructuras fallan, los datos en bruto se muestran de forma predeterminada y se muestran como caracteres de datos hexadecimales 23.

Esto se muestra en el siguiente ejemplo:

Tipo de codificación 1: 
54  33  35  30  30  30  00  00  00  00  00  00 
'T' '3' '5' '0' '0' '0' <---- Valores cero --->
<------- Data --------> <---- Valores cero --->
Tipo de codificación 2:
00  00  00  00  00  00  00  00  0A  12  34  56
<--------- Zero Values ---------><--- Data -->

Tipo de codificación 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.

Por David Carta, CEO de Telaeris

Deja un comentario

*

Actualizaciones del blog

Newsletters


hable con un representante

Contáctenos

Teléfono: 858-627-9700
Fax: 858-627-9702
-------------------------------
9123 Chesapeake Dr.
San Diego, CA 92123
-------------------------------
sales@telaeris.com