• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 16 subscribers
  • Views 2127 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: With TMS3705 read TRPGR30ATGC and TMS37157 with one charge up

Felipe Oliveira72
Prodigy 200 points
Part Number: TRPGR30ATGC
Other Parts Discussed in Thread: TMS3705, , TMS37157

We develop and sell solution using TMS3705 to read TRPGR30ATGC. Initially I only send charge up and wait for the answer, this worked.

Now we want use TMS37157 in our products, but I am have problem to read both using same code.

Maybe problem is the TRPGR30ATGC. Studying TRPGR30ATGC´s datasheet we see it is a one page read only TAG but my TAGs sound have more pages.

To use TMS37157 in my solution I only add command to read page 3. ( I created other CRC type and I took care to sell how CRC use.

With this line I cannot read TRPGR30ATGC TAG. I can read TMS37157 and other types of TAG (Ampole with 24 and 32 mm , for example), but only TRPGR30ATGC no work.

I have MICROREADER in my lab too, and I used it to make more tests.

Using MICROREADER SW2.21 I noticied something wrong with TRPGR30ATGC.

Look:

Why I have more one page in my TRPGR30ATGC ??

 

Lastly I read scbu020 doc and see command to read ID TAG in multipage TAG, So I change command to:


With this I make work but bad range performance.

Initially I want know if have something wrong with my  TRPGR30ATGC, because datasheet of the TRPGR30ATGC show only one page.

 

 

  • 0
    TI__Guru*** 134965 points

    Hello Felipe,

    Thank you for providing all the details including the code snippets.

    The TMS37157 and the TRPGR30ATGC have different processes for reading them as they use Pulse Position Modulation and Pulse Width Modulation respectively. The TMS37157 is a PaLFI device that needs more steps to communicate with whereas the TRPGR30ATGC is a read-only transponder that works with the single charge up you described.

    Since the TMS37157 is going to use a different protocol, you cannot read the TRPGR30ATGC  with same command set which you will need for the TMS37157. Therefore you will need to have two separate read processes. This is common in RFID - more so at HF (13.56MHz) where you need to search for each supported protocol individually.

    I would recommend keeping the firmware which originally worked to read the TRPGR30ATGC as is, and then restart the communication with the process to read the TMS37157.

    Regarding the Microreader II GUI and how it claims there are 'Pages 1-4': this seems to be an issue with how the GUI presents that data. We tested this with a tag ourselves and found that it displayed similarly. Thus I have no reason to believe your tag is bad or something is wrong with it. It should still have just one page, but the GUI is not properly displaying that on the PC screen. I'll check with the GUI creator about why the data is presented in that manner and then get back to you.

  • 0 in reply to Ralph Jacobi
    TI__Guru*** 134965 points
    Hello Felipe,

    To follow-up on the GUI: There is nothing wrong with the TRPGR30ATGC, it is a 64-bit R/O transponder and if you are using the standard charge only read command you will see the standard response of a 64bit ID number and the 16 bit CRC.

    The Microreader GUI is using a special command which shows additional memory pages of the transponder which are not available for customer use in the 64 bit R/O configuration.
  • 0 in reply to Ralph Jacobi
    Prodigy 200 points
    Ah okay,
    So, thank you so much for your help, Ralph.
    I did what you said and now I can read both TAG templates.