Rfid Encoding Problems
Hi guys,
I am trying to print RFID lables where the RFID element contains a serial number. The label is able to print fine, I don't see any errors from the printer, however when I then scan the label back I get the generic data, not the information I'm trying to put there. What am I doing wrong?
I'm currently using BarTender version 9.10. The printer is a SATO GL408e. I'm using text encoding US, Western Europe (ANSI, 1252). I have attached an example file of what I'm trying to print.
-
What do you mean exactly with "When I scan the label I get the generic data"? Do you mean that when you scan the RFID tag the encoded value is incorrect / inexistant?
If I print to file your BarTender document I see the following for the RFID command:
IP0e:z,d:383B5A3830313B31315333315031383430594D31584247334243303035;H63V155
Please note that when encoding to the EPC segment, the EPC number should be either Hex 16 or Hex 24 long. However, the data you're trying to encode is much larger than 24 hex long, so this doesn't seem to be a valid EPC number to me. Are you sure that you're wanting to encode to the EPC segment and not to the User one?
0 -
When I scan a tag I get a string like: E2009002530C00490720CCB. After I try to print to the RFID tag I get the same string back, not the value I'm trying to print.
What I am trying to encode onto the tag has now changed, now I am trying to get two, three digit numbers separated by a colon, but I'm still having difficulties.
I don't seem to have any others options to encode on anything else but the EPC segment, so I'm not sure what this User segment thing is.I have attached a new file containing the label I'm trying to print.
0 -
Does your RFID chip has a User segment? Please verify this.
The data you're trying to encode is still no valid EPC number and therefore cannot be encoded to the EPC segment of your RFID chip. Valid EPC values are e.g. 96 and 128 bits, which translates to 16 and 24 HEX characters respectively. You're trying to encode 8 HEX characters, which isn't a correct length.
0
Please sign in to leave a comment.
Comments
3 comments