Some questions about ST25RU3993

[MYoun.4]

Hi.

I'm graduate student, researching UHF passive RFID tag, in Dongguk university, Seoul, Korea.

Thanks to offer materials like documentations, video. It was really helpful for my study. 

Before purchase the ST25RU3993-HPEV to measure research results, I want to check some questions. 

At page 39 and 49 of ST25RU3993 datadheet, document says "In EPC Class 1 Gen2 protocol, the decoder supports long Rx preamble (TRext=1) for FM0" and "Short preamble is supproted for Miller 4 and Miller 8 coding". I wondering it means "FM0 coding can't use short Rx preamble (TRext=0) to communicate with ST25RU3993".

At page 48 of same document, if I set Rx_crc_n=1 (Rx without CRC), does it mean ST25RU3993 never check CRC for all received data from a tag?

Finally, at UM2268 User manual (about ST25RU3993 GUI software), I want to know can I custom commands like Read/Write.

Thanks for your help.

[Bart Herse · Accepted solution]

Hello MYoun.4

• for FM0 it is required to set TRext = 1

• in case Rx_crc_n=1 (Rx without CRC) the CRC-16 can be fetched form the FIFO so that the MCU can check the CRC. The reader IC will not check the CRC with this configuration.

• Read and Write commands are already implemented to perform read and write on the memory banks. If special commands are needed It is possible to entirely customize reader commands. So it also possible to manually replicate Read and Write commands.

Cheers,

B

[MYoun.4]

Hi Bart Herse.

I really appreciate your answer.

I want to know three more things about ST25RU3993-HPEV.

1. In case of Rx_crc_n=1(Rx without CRC), which does it mean "tag shall not append CRC data in its reply" or "tag shall append CRC, but RFID reader does not check it"?
2. According to EPC Gen-2 protocol, FM0 coding (tag to reply communication) shall ends with "dummy-1", is it valid with ST25RU3993-HPEV?
3. At page 37 of UM2268 User manual ST25RU3993 evaluation board software, Figure 34 shows four scanned tags with 1word(2bytes) or 6words (12bytes) or more words EPC length. Dose ST25RU3993 get these EPC data through tag reply to ACK command? Also, I'm wondering there is a minimum length of EPC data that shall be appended to communicate with ST25RU3993-HPEV, i.e., is it possible to append just 1bit EPC data in tag reply to ACK command?

I'm really thanks for your help.

[MYoun.4]

Hi Bart Herse.

I read all documentations about ST25RU3993-HPEV​.

Sorry to bother you, but I have three last questions.

At page 56 of User manual ST25RU3993 evaluation board software, Figure 49 shows tag settings dialog window.

1. At here, if I use truncated EPC for tag reply to ACK command, what is shown in 'Information panel', truncated EPC data or whole EPC data in EPC memory bank?
2. Is the information displayed on the 'Information panel' obtained through the Read command for TID memory?
3. If I use only EPC data for tag, i.e., no PC and no other memory banks, how is information displayed in 'Information panel' and 'Functions panel'? Or is it possible to communicate with ST25RU3993 only by providing all TID, User, and Reserved memory bank?

I'm really thanks for your help :)

[Bart Herse]

Dear MYoun.4,

1.: CRC-16 will not be checked by the reader IC. The CRC-16 will be put into the FIFO so that the MCU can fetch it and process it.

2.: How the tag ends its frame cannot be altered by the reader. If the question is , if ST25RU3993 can decode FM0, then the answer is yes.

3.: The EPC data is received upon the ACK command. As the length field in the PC defines the EPC ´length in number of WORDS (2 bytes), a 1-bit EPC data length is per my knowledge not possible.

Cheers,

B

[Nick K]

Hello MYoun.4,

ad 1

EPC truncation is currently not supported. In the GUI you can not send a select with truncation enabled. The SDK has this parameter for the select command, but only for future use, not yet implemented in FW.

ad 2

yes, when the TAG settings dialog pop-up then the GUI select the TAG and read the TID in background.

ad 3

The TAG settings dialog in the Reader Suite GUI shall provide some information about the TAG and allow an user to access TAG memory with the Gen2 access command as defined in the Gen2 specification.

All you see in this dialog is a visual presentation of the execution of the Gen2 Read/Write/Lock/Kill and Access commands. Except the Generic command that allows user to built up their own commands

BR

Nick