ICODE ILT inventory reading

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

ICODE ILT inventory reading

1,716 Views
mahesh2
Contributor I

Hello ,

I am using CLEV6630A V2.0 board for ICODE - ILT evaluation. i want to read a stack of ilt cards (100 cards). i didnt find any icode ilt inventory reading  example in SW2978 . i do find the example in sw335613, but its not working with the above mentioned evaluation board. can anybody help me in solving this issue ?

Labels (1)
0 Kudos
Reply
3 Replies

1,558 Views
estephania_mart
NXP TechSupport
NXP TechSupport

Hello,

Which errors are you getting when you try to run the examples ?

By any chance did you checked and confirm that you have all the hardware setup necessary to deploy those examples? There is a Readme.txt file in the examples you downloaded in the sw335613, there are some necessary changed for the blueboard that you will need to adapt to your redboard.

Also, have you tried taking one of the examples and add the ILT functionality ?

If you are using more than 100 tags, it is most likely you will also need this application note.

Regards,
Estephania

0 Kudos
Reply

1,558 Views
mahesh2
Contributor I

Hello Estephania,

In the readme.txt  of sw335613, mentioned that need to swap r34 to r35 to make IRq enable. but there is no resistor with that name in the redboard and the IRq is already connected to LPC1769. interms of communication, red board is already configured to SPI mode . but in the ISO15693(sw2978) example , its detecting the reader IC as 0x18, but showing error is sw335613 example as 0xFF which is an error.

The error,

The Initialization is complete.

The version number of reader ic is :FF

The version number of reader ic is incorrect.

Please check the connection of reader and MCU, then relaunch the software.

0 Kudos
Reply

1,558 Views
estephania_mart
NXP TechSupport
NXP TechSupport

Hello,

Currently the  NXP NFC Reader Library also implements the Type-V anticollision. If you follow the path of the Discovery Loop you will end up at the anticollision function for Type-V in a file called 'phacDiscLoop_SW_Int_V.c', the method 'phacDiscLoop_Sw_Int_CollisionResolutionV(...)' implements the anticollision.

Also, you can check in the internal ticket for another example.

Regards,

Estephania

0 Kudos
Reply