cancel
Showing results for 
Search instead for 
Did you mean: 

VB.Net application not able to read more than 61 bytes

anilbhide
Associate

Dear Sir,

I am trying to develop my own VB.NET application to communicate with st25dv64k through CR95HF board.

I am using latest DLL Version 1.2 & the firmware loaded in CR95HF is also latest i.e. 3.7.1.

The Sequence I am trying to follow to setup the CR95HF is as below,

1. Get DLL version using CR95HFDll_GetDLLrev

2. USB Connect using CR95HFDLL_USBconnect

3. Reset SPI using CR95HFDll_ResetSPI

4. ISO 15693 selection using CR95HFDll_Select

5. Long Frames using CR95HFDll_STCmd ("02A8" and getting answer as 00020397)

6. Inventory using CR95HFDll_SendReceive ("260100" and getting TAG UID as answer)

7. Read Dynamic Config using CR95HFDll_SendReceive (02AD020D)

8. Write Dynamic to enable MB using CR95HFDll_SendReceive (02AE020D01)

8. Read Dynamic again to confirm (Getting answer as 80050001CE1E)

9. Sending Mailbox write using CR95HFDll_SendReceive (02AA020A and application bytes)

10. Read Dynamic Register to check the response from device (Getting answer as 80050043D87F)

11. Read Message Length using CR95HFDll_SendReceive (02AB02 and getting answer as 800500D6FCBC, so basically "D6" bytes are available to read i.e. 214 bytes)

12. Read Mailbox using CR95HFDll_SendReceive (02AC020000 and getting response as 803D00 followed by bytes)

13. So I am able to get only "3D" bytes i.e. 61 bytes whereas I am expecting 214 bytes.

14. If I further give Read Mailbox command by specifying Address & Length then I am able to read whole 214 bytes but in 3 read mailbox operations.

Can you please check & confirm, why I am able to read only "3D" i.e. 61 bytes in one go although Tag has 214 bytes in Mailbox?

Best Regards,

Anil Bhide

1 ACCEPTED SOLUTION

Accepted Solutions

Hello,

unfortunately, I cannot reproduce the issue you are experiencing. I suspect that the firmware version of your CR95HF reader is not the good one (lower than 3.7.1).

Can you please add to you application the following instructions :

  • CR95HFDll_GetDllRev

You should receive :  1.2

  • CR95HFDll_GetMCURev

You should receive :  0003030701 (3.7.1) Firnware version

  • CR95HFDll_IDN

You should receive :  000F4E4643204653324A41535434002ACE = CR95HF identification number

Best regards,

NFC Customer support

View solution in original post

2 REPLIES 2

Hello,

unfortunately, I cannot reproduce the issue you are experiencing. I suspect that the firmware version of your CR95HF reader is not the good one (lower than 3.7.1).

Can you please add to you application the following instructions :

  • CR95HFDll_GetDllRev

You should receive :  1.2

  • CR95HFDll_GetMCURev

You should receive :  0003030701 (3.7.1) Firnware version

  • CR95HFDll_IDN

You should receive :  000F4E4643204653324A41535434002ACE = CR95HF identification number

Best regards,

NFC Customer support

Brian TIDAL
ST Employee

Hi,

also make sure to have the latest HW revision of the board. When starting the CR95HF development software, you should see something like:

BrianTIDAL_0-1693898255149.png

The IDN should be "NFC FS2JAST4"

Rgds

BT

In order to give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.