2023-08-31 09:49 AM
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
Solved! Go to Solution.
2023-09-04 05:54 AM
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 :
You should receive : 1.2
You should receive : 0003030701 (3.7.1) Firnware version
You should receive : 000F4E4643204653324A41535434002ACE = CR95HF identification number
Best regards,
NFC Customer support
2023-09-04 05:54 AM
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 :
You should receive : 1.2
You should receive : 0003030701 (3.7.1) Firnware version
You should receive : 000F4E4643204653324A41535434002ACE = CR95HF identification number
Best regards,
NFC Customer support
2023-09-05 12:20 AM
Hi,
also make sure to have the latest HW revision of the board. When starting the CR95HF development software, you should see something like:
The IDN should be "NFC FS2JAST4"
Rgds
BT