• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 16 subscribers
  • Views 275 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.

Original question:

ISO 15693-3 Write single block response reception with RI-R6C-001A

RI-R6C-001A: Write single block (0x21) no response even though data was written normally

Elly Lee
Prodigy 20 points

Part Number: RI-R6C-001A

Hello, 

I faced a problem when writing single block (0x21) to TI-tag using RI-R6C-001A. 

Writing data is a success, but transceiver IC(RI-R6C-001A) does not send a response. (No response flags) 

(The data is correct when I read the block after writing )

When I looked up the Q&A related to this problem, it was stated that the TI tag should give more than 10 ms of delay before the EOF.

As far as I know, EOF and SOF are sent by transceiver IC,  not MCU.  How can I handle this? 

I also saw the document "LOWBAUD_WRITE_SINGLE_BLOCK_UNADDRESSED.pdf". 

In this document, the DIN is changed to Low after a 40 ms delay, and who is changing this signal? 

After "TRANS1", who handles 40ms delay? MCU?  If so, what should the MCU do after a 40 ms delay? 

Could you explain how can I get response from transceiver IC after wiring command?  

  • 0
    TI__Mastermind 18265 points

    Hi Elly,

    are you working on a new design with the RI-R6C-001A? I would not recommend this device for a new development. I recommend for new designs the TRF70xx series as Reader IC instead.

    I do not have any target board to verify the behavior of the device but would recommend to use the screenshots of the mentioned pdf document as reference for your software implementation.

    From my understanding the MCU has to handle the 40ms delay by setting the DIN line to high.

    There is also a dependence of the transponder type you are using. The screenshots are referring to our Tag-It transponders. These transponders require in the request flags that the option bit is set and need a programming time >10ms before EOF is send to the tag. I assume that the handling of the DIN line is used to send a delayed EOF to the transponder.

    Best regards,

    Helfried

  • 0 in reply to Helfried Vollbrecht
    Prodigy 20 points

    RI-R6C-001ArefGuide.pdf

    Hi, Helfried

    Thank for reply. 

    Unfortunately, I cannot change the part to new one. 

    I already tested the following conditions. But it did not succeed. 

    1) add 40ms delay before "TRANS1" . 

    2) add 40ms delay before "ES1" 

    I uses Tag-it HF-I Plus transponder.  0x41 (set option flag) was also sent as a request flag. 

    Could you clarify of the meaning of EOF ? 

    Does this mean ES1 defined in the attached reference guide? 

    Otherwise, does it mean the ISO protocol 's EOF?  If so, it is generated by the transceiver IC (RI-R6C-001A) and cannot be handled by the MCU. 

  • 0 in reply to Elly Lee
    TI__Mastermind 18265 points

    Hi Elly,

    I found in the following thread (second page) the source code of the firmware written for the RI-R6C-001 (S6700) reader asic:

    https://e2e.ti.com/support/wireless-connectivity/other-wireless/f/667/t/368377

    There are two files, hfasic.c and HFASIC.h maybe these files are helpful for you.

    The EOF is the ISO protocol EOF. Please see the Reference Guide page 33:

    "ES1 is then sent to modulate an EOF towards the TAG".

    From my understanding the ES1 has to be delay but this is different from what I see in the screenshots.

    Because I do not have a target system to check that, I am not able to give your more detailed information.

    Best regards,

    Helfried