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.

MRD2EVM: Unable to write to transponder

Part Number: MRD2EVM
Other Parts Discussed in Thread: RI-STU-MRD2

Tool/software:

Hi all,

I am currently using the Protagd PRDG23WS Read/Write transponder with the MRD2EVM Reader with own custom C# code, sending bytes to the reader to perform read/write actions. I’m having troubles with sending the bytes to the reader to write the transponder.

Reading using ECM and LMP methods both work, but I am unable to write using either methods. Here are my bytes for the following functions. Data fields (8 bytes) and the BCC field are added dynamically so they're just set to 0 for the command format. These are written with reference to the RI-STU-MRD2 Reference Manual:


ECM Read
(Pg42): { 0x01, 0x03, 0x80, 0x01, 0, 0 }

ECM Write (Protagd Manual Pg12) { 0x01, 0x0B, 0x80, 0x21, 0x15, 0, 0, 0, 0, 0, 0, 0, 0, 0 }

(For ECM Write (Pg43), I am not sure what is the 'Keyword' and 'Password' field. I have tried using the ECM Write command and using 0, 0 for the 'Keyword' and 'Password' field, and I have also tried reducing the length to 0x0B and omitting the 'Keyword' and 'Password fields', but both does not work.)

For ECM Write, I am getting a response code 01-02-05-00-07, giving me error code 0x05.

LMP Read (Pg24): { 0x01, 0x02, 0x08, 0xFF, 0 }

LMP Write (Pg25): { 0x01, 0x11, 0xE8, 0x06, 0xFF, 0x0F, 0x0C, 0xBB, 0xEB, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0x03, 0 }

(I am not too entirely sure what byte numbers 17 and 18 (Data field 14-15: Write Frame) is supposed to be, but according to old source code by my colleague, it was set to 0, 3. I've also tried to use the command without both fields, did not work either)

I've reached out to Protagd, and was told that the TI MRD2EVM reader is not compatible with the Protagd transponders, however, we do have another version of the custom software that is able to read and write to a Protagd transponder using the same TI reader. Only problem is that nobody is able to find the source code for that.

Would appreciate if anyone could advise on whether the bytes sent were wrong, or where should I look for the error. Thank you in advance!

Edit: attached both manuals for your reference

Protagd MRD2+ Reference Guide V1_1.pdf

ri-stu-mrd2 reference manual scbu049.pdf

  • Hi,

      Today is a public US holiday. I will look into your post tomorrow. 

  • Hello Customer, thank you for your question and interest in our products.

    This product has limited design support. I think Microreader EVM User's guide should answer your question. 

    The forum support of this product has been reduced to first reference our existing documentation and collateral. For support, please take a look to the “Similar Topics” section at the lower right of the thread page. In addition, please consult the existing collateral in the “Technical Documentation” section of the  RI-TRP-DR2BMRD2EVM. Alternatively, you can use the search engine of your choice to look for related E2E threads. With each of these resources we believe it will help with your question.

     Reading this post https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1031967/mrd2evm-non-ti-transponders-compatibility answered by Helfried, MRD2EVM is only compatible with HDX and not FDX transponder.

  • Hi Charles,

    Thanks for the information, and thank you for your help!

    The transponder is indeed HDX:

    However, as per Protagd, it seems like the transponder is not compatible with TI readers at all. 

    however, we do have another version of the custom software that is able to read and write to a Protagd transponder using the same TI reader.

    Turns out the other TI Reader that we had houses a Protagd MRD2, which explains why it was able to read/write the transponder. 

    Reading using ECM and LMP methods both work, but I am unable to write using either methods. Here are my bytes for the following functions. Data fields (8 bytes) and the BCC field are added dynamically so they're just set to 0 for the command format.

    Also, these bytes have no issue reading and writing the Protagd transponders - as long as its paired with a Protagd MRD2, if somehow anyone else is facing the same issue as me!

    Thank you for your help again!