This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TRPGR30ATGC: How to read UID of TRPGR30ATGC and TRPGR40ATGC

Part Number: TRPGR30ATGC
Other Parts Discussed in Thread: MRD2EVM, TRPGP40ATGC

Hello E2E community,

 

I would like to know how to read the UID of 12mm LF glass encapsulated transponder below,I dont know what to begin.

 

So, please give some advices.

These may include the protocol specification sheet and tool.

 

   ・TRPGR30ATGC

   ・TRPGR40ATGC

 

Best regards,

Taka

  • Hello Takamichi,

    Are you asking for device recommendations to read the tags or do you have a specific device in mind you want to use?

  • Hello Ralph,

    Thank you for your prompt reply.

    I am asking for your device recommendation.

    Would you please let me know it?

    Best regards,

    Taka

  • Hello Taka,

    The MRD2EVM would be the best device for this: http://www.ti.com/tool/MRD2EVM

    The User Manual and Software can be downloaded from the EVM page as well.

  • Hello Ralph,

    Thank you for your support.

    I understood and I will try it.

    Best regards,

    Taka

  • Hello Ralph,

    I read the data which TRPGR30ATGC and TRPGP40ATGC by MRD2EVM.

    So, I have two questions.

    #1)

    I need to know the each data block which we read by MRD2.

    would you please let me know each transponder's memory map and corresponding commands, command response ?

    #2)

    Regarding to the above,

    Are TRPGR30ATGC and TRPGP40ATGC perfect ISO14223-2(code and command strcuture) standard ?

    Best regards,

    Taka

  • Hello Taka,

    1) There is no memory map for those tags. One is a read only tag with just the 80 bits of memory, and the other is a Customer Configurable transponder designed for animal tracking applications which allows the customer to One Time Program the 80 bit memory based on their requirements.

    The MRD2EVM GUI is probably misleading a bit about the memory map, when reading it kind of implies there is more memory when reality there is not.

    2) They are not. I'm going to send you a friend request on the topic though as we don't want to discuss possible roadmap devices on the public E2E forums.

  • Hello Ralph,

    Thank you for your prompt reply.

    I have a question about datas of when I clicked "Read Tag" on MRD2EVM GUI.

    I infer "Config Byte 2,1" of which attached following shows Tag Type , I don't know the kind of conbination for Tag Type and Config Byte.

    I would like to deternine Tag Type by our GUI Softwarem, please let me know it ?

    ( Config Byte 2,1 : 00 02 → HDX+ R/O industrial ? )

    Best regards,

    Taka

  • Hello Taka,

    For the transponders in question, the data you need to be concerned with that you see is the 64 bit ID in the first pages.

    As far as knowing the type of tag, that is not part of the config bytes. There is a start byte which is not shown that is decoded to determine that.

    If you want to make your own GUI, you would want to do is have the GUI issue a Charge Only Read.

    From there, you will get 16 prebits, and then an 8 byte start byte. That start byte will tell you the type of transponder.

    Afterwards, you will get the 64 bit ID and 16 bit CRC.

    Also, the first of the ID determines if it's industrial or for animal tagging. If the first bit is set to 1, then it is an animal transponder. If the first bit is set to 0, then it is for industrial.

    Hopefully this information helps you put together the GUI.