Other Parts Discussed in Thread: RI-STU-MRD2, , MRD2EVM
Hello,
I am using the RI-TRP-DR2B transponder with the RI-STU-MRD2 Reader. I have the development kit MRD2EVM as well. We are developing a product that intends to use the transponder for equipment management.
When using the development kit, I can READ and WRITE to my transponders using the software Microreader II. I only need to write 2 bytes of data to the first page. In the development console we are prototyping, I can READ the first page perfectly using the Easy Code Mode (ECM) command of:
0x01 0x06 0x88 0x80 0x00 0x00 0x32 0x0D 0x31 (010688800000320D31)
This is also the command found in the command line of the Microreader II program, and the response is correct and READ works every time. So I figure I must have things configured and working properly?
However, when I go to WRITE, the data doesn't WRITE. So I start with a transponder that has 0x00 0x00 0x00 0x00 0x00 0x00 0x05 0xBB for is first page data, then I want to WRITE new bytes. An example code for WRITE I am using is:
0x01 0x0C 0x80 0x02 0x15 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x07 0xBB 0x26 (010C8002150100000000000007BB26) This should WRITE 0x00 0x00 0x00 0x00 0x00 0x00 0x07 0xBB to the first page. The response from the reader i get is:
0x01 0x10 0x00 0x7E 0xBB 0x05 0x00 0x00 0x00 0x00 0x00 0x00 0xA5 0x71 0x04 0x24 0x46 0x02 0x60
Basically I get the data read back unchanged, still the initial 0x00 0x00 0x00 0x00 0x00 0x00 0x05 0xBB. According to the manual, a 0x00 for STATUS 1 byte (the third byte) means no error. I get 0x00.
The page is not locked and I can still READ and WRITE to the transponder with the development kit. Any ideas? This is becoming a bit of a headache!
Thanks in advance for any help.
Jon