Realizing continous sending application in low power mode of ndef data with ST25R3911B

[BWolf]

Hello all,

for test purposes I want to realize a communication of small data amount with the ST25R3911B-Disc​o board.

yet I already:

• installed the gui and updated firmware
• tested nfcip with my smartphone (so the board is working)
• tried to use integrated script tool for sending (didn't work yet)

Im not sure which standard is apropriate to realize the project and how to define it in the script tool.

For testing I use an ST25TA64K Tag.

Regards, Ben

[NFC/RFID Customer support · Accepted solution]

H​ello,

Scripts can be used to communicate with ST25TA64K tags.

First part of your script is correct (DLL, MCU and Hardware revision) allow to be sure that the ST25R3911B-DISCO kit is well connected. You are now able to communicate with the Tag.

Second part of the script must be the Protocol Select. For ST25TA64K, you must select ISO14443-A RF protocol. Uses 02000280 instead of 01D0 = ST25R3911B_PROTOCOL_SELECT, 02000280. You are now able to communicate with the Tag since the RF reader is configured to manage ISO14443-A RF protocol.

The third step is to run the ISO14443-A anticollision process. Then send the RATS command to enter the tag in NFC world. ST25R3911B_ANTICOLSELECT123 is used to send the whole anticollision process.

Then the RATS can be sent using ST25R3911B_SENDRECEIVE, E0803173 08 command.

Now the tag is in NFC TYPE 4A world, you can manage it (CC file, NDEF file).

You can use ST25R3911B_ISO14443-A_SEND_APDU to send APDU commands and let the script manage PCB & CRC or you can use  ST25R3911B_SENDRECEIVE  to send APDU commands managing PCB (last byte will be 28 to allow the ST25R3911B to manage CRC).

For APDU & NFC methods to read the tag, I suggest you to read the ST25TA64K datasheet and NFC Forum type4A.

You also can to read the Log file when using the User Interface in ISO14443-A/ST25TA64K menu.

Attached file,

Best regards

NFC/RFID Customer support

---> Below, updated script for ST25TA64K.

CLEAR_LOG

ST25R3911B_GETDLLREV

ST25R3911B_GETMCUREV

ST25R3911B_GETHARDWAREVERSION

WAIT, 30000

REM, ISO14443-A RF PROTOCOL

ST25R3911B_PROTOCOL_SELECT, 02000280

REM, ISO14443-A PROTOCOL

ST25R3911B_ISO14443-A_AnticolSelect123

REM, RATS

ST25R3911B_SENDRECEIVE, E0803173 08

REM, THERE ARE 2 METHODS TO SEND APDU :

REM, 1ST METHOD : SELECT NDEF APPLICATION USING SEND APDU SCRIT COMMAND (PCB MANAGED BY APPLI, CRC MANAGED BY APPLI)

REM, ST25R3911B_ISO14443-A_SEND_APDU, 00A4040007D276000085010100

REM, 2ND METHOD : SELECT NDEF APPLICATION USING SEND APDU SCRIT COMMAND (PCB MANAGED BY APPLI, CRC MANAGED BY APPLI)

ST25R3911B_SENDRECEIVE, 0200A4040007D276000085010100 28

[BWolf]

Thank you for your help!

The next step for me would be to communicate in P2P mode with a android device.

( this is possible with the script tool? )

I want to transmit a few Information ​to my phone as ndef message ( the st25 app is suitable for that?)

I really approciate your great work in helping and supporting

Best Regards

[NFC/RFID Customer support]

​Hello,

Tag Editor software is mainly used to read and write tags and dynamic tags.

Anyway, if you send ISO14443-A anticollision process and RATS command to an Android phone, you will be able to communicate with it using APDU commands. In this case, the phone is in CE mode (Card emulation mode).

Best regards

NFC/RFID Customer Support

[BWolf]

Hello ,

Thank you for your answer. But now a couple of new questions are occuring

• I tried to realize the code as you have sudgested but with no result ( Have attached a picture)

      The anti colision adjustment ist similar to this one here:

        https://www.youtube.com/watch?v=tuMjCsIyyuw  ?

• is there a list anywhere with the APDU commands in ST25R3911B ?
• How could I use/controll the other functions for example on NFCIP to send pictures and so on with ST25R3911B?

       ( For Example to send data if a apropriate device is in range) this means especially which tool is adecuate for confuguring that?)

Best Regards

[NFC/RFID Customer support]

​Hello,

yes, you're true. Anticollision's process shown in the youtube video is the same as it is iso14443-A anticollision. The only difference is that, using an Android phone in CE mode, the UID is only 4 bytes length instead of 7 bytes length.

About the attached picture, I suspect that the ST25R3911B-DISCO has been removed (USB plug and unplugged) and the main software (ST25R3911B Discovery GUI) has taken the USB handle. You need to close ST25 Tag Editor software and launch it again.

Last point : the main goal of the script is to evaluate the communication between the RF reader and the tags. You can use it to exchange any data between the reader and the tags (or android phone in CE mode) but you will need to code all frames to be able to transfer a picture or any NDEF message to the tag.

Best regards

NFC / RFID Customer support

[BWolf]

​Unfortunately I alsways reiceive this error as well when I have plugged and unplugged the board an have adjusted the version settings.

I couldn't get the script working you've sent me to communicate with ST25TA64K Tag because i got the same error. It worked in the normal reader writer mode but not with the scripttool.

Regarding the communication to an andriod phone the four byte means in the protocol send_receive 2604 ?

To be honest I'm a bit depressed after trying hours with no result.

I just tried to poll the ID of the phone but it's continously changing , I don't know if it's the same with the UID.

As I saw in the video he used a 4byte mi fare tag and choosed 2607 ?

Regards from Germany