PN7462 Issue

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

PN7462 Issue

3,024 Views
teinsu
Contributor I

below is the PN7462 (reader mode) question:

1. If we enable the ISO18092 (P2P) card option in Code, plus Tx Power is set
GSN=1, about 15% of the machines can't read Type A cards.
2. However, if you disable the card option of ISO18092 (P2P), these machines that cannot read the card can read it.
Type A card.
3. Enable ISO18092 (P2P) card option, but do not drop Tx Power, maintain DPC Enable settings
Therefore, the machine that cannot read the card can also read the Type A card.

Is there a reasonable explanation?

4.Disable ISO18092 (P2P) and Enable ISO18092 (P2P) What is the difference in reader mode?

Disable P2P option is mark off NXPBUILD__PHPAL_I18092MPI_SW define:

>>NfcrdlibEx1_BasicDiscoveryLoop\intfs\ph_NxpBuild_App.h
//#define NXPBUILD__PHPAL_I18092MPI_SW /**< PAL
ISO18092 (P2P) SW Component is included. */

0 Kudos
Reply
13 Replies

2,734 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi Tein,

What is the Tx Power that you set? and what are the maintain DPC Enable settings values that you have?

Could you please explain your issue again?

Regards,

Mario

0 Kudos
Reply

2,734 Views
teinsu
Contributor I

Hi Mario:

About DPC, we set DPC Enable, RfDPC Lut size = 1 and 1st ConfigLUT value is 0x16.

Other setting please refer to attachment file: user_ee_GSN_1.bin

 

Issue re-explain:

With the user ee file...

If disable "NXPBUILD__PHPAL_I18092MPI_SW", type A cards can be detected.

If enable "NXPBUILD__PHPAL_I18092MPI_SW", type A cards can not be detected.

We want to know the root cause why more capacity cause low compatibility?

 

Regards,

Tein

0 Kudos
Reply

2,734 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi Tein,

You are using a Type A Card, as I am understanding you are using PSP, your card is waiting for the electric field from the PN7462. You need to increase the RFDPC Lut Size, you are using the lowest values. It is not enough for the cards Type A.

Please let me know your findings.

Regards,

Mario

0 Kudos
Reply

2,734 Views
teinsu
Contributor I

Hi Mario:

Actually, after disable NXPBUILD__PHPAL_I18092MPI_SW.

the type-A card can be detected and read id on our board,

event set tx power to lowest value.

 

Why enbale NXPBUILD__PHPAL_I18092MPI_SW, one of the default options,

cause card detection fail?

Regards,

Tein

 

0 Kudos
Reply

2,734 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi Tein,

You mention that it works correctly with two devices with P2P, those devices are self-powered, don't they? 

If that it's the case when using such as low TX Power how are you confirming you are providing enough current to activate the Type A tag? 

Please let me know your findings.

Regards,

Mario

0 Kudos
Reply

2,734 Views
teinsu
Contributor I

Hi Mario:

Our device is a contact less card reader and never test in P2P mode before.

 

The reason to enable NXPBUILD__PHPAL_I18092MPI_SW just only it is a default setting of NfcrdlibEx1_BasicDiscoveryLoop

If the tx Power is too low to activate a A tag,

 it means that enable NXPBUILD__PHPAL_I18092MPI_SW will comsume more power cause card activation fail?

Regards,

Tein

0 Kudos
Reply

2,734 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi Tien,

Let me see if I fully understand you, the issue you are having it’s that you do not have enough power to activate a card when it is set to the minimum?

All you want to do it’s to activate a card, is that correct? Could you please provide more information about the requirement about the lowest value.

Please consider that there will be some current and power requirements to activate the card due to electromagnetic necessities, the card will need a field strong enough to activate the card and be able to read or write it, also it will depend on the type A card you are using the current requirements so it is most likely that the card it’s not being activated as it needs more power than the low one you are setting.

Regards,

Mario

0 Kudos
Reply

2,734 Views
teinsu
Contributor I

Hi Mario:

In every mail I response before, the important is always be...


"Why type-A card cannot be activated since enable NXPBUILD__PHPAL_I18092MPI_SW (P2P)"?

Maybe lowest tx power is not a good idea,
but the NXPBUILD__PHPAL_I18092MPI_SW does effect the result...

Regards,

Tein

0 Kudos
Reply

2,734 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi Tein,

I run by my side and it works working on the default values.

Did you try working on the default TX power?

Please let me know your findings.

Regards,

Mario

0 Kudos
Reply

2,734 Views
teinsu
Contributor I

Hi Mario:

The default Tx power work fine with enable P2P setting,
I did not need to try it because I had written it inside the first question.

Could you please mind check again waht we want to know?

Regards,

Tein

0 Kudos
Reply

2,734 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi Tein,

As far as I understand,  what might be your problem it's that you are not providing enough power to the field to activate the card, how are you confirming you are providing enough current do so? 

 

Regards,

Mario

 

0 Kudos
Reply

2,734 Views
teinsu
Contributor I

Hi Mario:

Higher TX power will effect EMI, that's why we have to set GSN=1. Our question is why type-A card not active with NXPBUILD__PHPAL_I18092MPI_SW ?

As mentioned before. Type-A card active with GSN=1 and NXPBUILD__PHPAL_I18092MPI_SW disabled. But not active with GSN=1 and NXPBUILD__PHPAL_I18092MPI_SW enabled. The only difference is NXPBUILD__PHPAL_I18092MPI_SW enabled / disabled.

Seems TX power not the root cause of Type A card not active issue. Would you please help to find out the root cause.

Regards,

Tein

0 Kudos
Reply

2,734 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi Tein,

I have some question about the issue that you are facing, and I will try to replicate by my side.
Could you please provide the Gears DPC values that you have? is the set up that you have in your discovery loop? Did you modify it? In the MCU Settings. Are you defining the Read/Write and the P2P?

Regards,

Mario

0 Kudos
Reply