你好伊万，
谢谢你的提问。
什么版本的
您使用的是ST25R3911B Discovery.exe程序吗？
您是否已经知道要检测并失败的卡的UID？它们是4,7或10字节长吗？你能给我们一个UID格式的例子吗？
ST25 SDK包含一个独立于读者的RF库。如您的代码摘录所示，每个读者必须提供RFReaderInterface实现。
ST25 SDK中提供的STReader库包含ST25R3911B-DISCO板的实现。 Java本机接口（JNI）用于库与本机ST25R3911 dll交互。 JNI使用自己的防冲突算法，与原生ST25R3911固件不同。所以这已经是一个区别。
ST25 SDK的1.0.1版专注于ST25系列的标签。它尚未使用EMV卡进行测试，但如果这些标签符合ISO和NFC论坛协议，则基本发现应该起作用。
今天，ST25 SDK和ST Reader实现仅支持ISO15693和ISO14443-A协议。 ISO 14443-B（用于某些EMV卡）尚未涵盖。因此，基于ISO 14443-B的EMV卡不会响应库存请求。
但是，您在邮件中提到所有卡都是Iso14443-A类型。
您可以尝试改变卡与阅读器天线的距离。该
ST25R3911B Discovery.exe程序以最有效的方式调整阅读器。这种调整不是通过ST25 SDK实现完成的，可能导致读取器校准错误。
有关信息，我们正在重写JNI以提供更好的Iso14443-A支持。这可以改善EMV卡检测。
几周后再次检查SDK.Cheers的新版本。
以上来自于谷歌翻译
以下为原文
Hello Ivan,
Thanks for your question.
What version of the
ST25R3911B Discovery.exe program are you using?
Do you already know the UIDs of the cards that you are trying to detect and fail? Are they 4, 7 or 10 byte long? Could you please give us an example of UID format?
The ST25 SDK contains a RF library that is independent from readers. As shown in your code excerpt, each reader must provide a RFReaderInterface implementation.
The STReader library provided in the ST25 SDK contains an implementation for the ST25R3911B-DISCO board. A Java Native Interface (JNI) is used for the library to interact with the native ST25R3911 dll. The JNI uses its own anti-collision algorithm, different from the native ST25R3911 firmware. So this is already one difference.
Version 1.0.1 of the ST25 SDK focuses on tags from the ST25 family. It has not been tested with EMV cards but basic discovery should function if those tags follow ISO and NFC Forum protocols.
Today, only ISO15693 and ISO14443-A protocols are supported by the ST25 SDK and the ST Reader implementation. ISO 14443-B (used in some EMV cards) is not yet covered. So EMV cards based on ISO 14443-B will not respond to the inventory request.
However you mention in your mail that all cards are of type Iso14443-A.
You can try varying the distance of the cards to the reader's antenna. The
ST25R3911B Discovery.exe programs tunes the reader in the most efficient way. This tuning is not done with the ST25 SDK implementation and may result in a bad reader calibration.
For information, we are in the process of rewriting the JNI to provide better Iso14443-A support. This may improve EMV cards detection.
Check again in a few weeks for a new version of the SDK.Cheers.
你好伊万，
谢谢你的提问。
什么版本的
您使用的是ST25R3911B Discovery.exe程序吗？
您是否已经知道要检测并失败的卡的UID？它们是4,7或10字节长吗？你能给我们一个UID格式的例子吗？
ST25 SDK包含一个独立于读者的RF库。如您的代码摘录所示，每个读者必须提供RFReaderInterface实现。
ST25 SDK中提供的STReader库包含ST25R3911B-DISCO板的实现。 Java本机接口（JNI）用于库与本机ST25R3911 dll交互。 JNI使用自己的防冲突算法，与原生ST25R3911固件不同。所以这已经是一个区别。
ST25 SDK的1.0.1版专注于ST25系列的标签。它尚未使用EMV卡进行测试，但如果这些标签符合ISO和NFC论坛协议，则基本发现应该起作用。
今天，ST25 SDK和ST Reader实现仅支持ISO15693和ISO14443-A协议。 ISO 14443-B（用于某些EMV卡）尚未涵盖。因此，基于ISO 14443-B的EMV卡不会响应库存请求。
但是，您在邮件中提到所有卡都是Iso14443-A类型。
您可以尝试改变卡与阅读器天线的距离。该
ST25R3911B Discovery.exe程序以最有效的方式调整阅读器。这种调整不是通过ST25 SDK实现完成的，可能导致读取器校准错误。
有关信息，我们正在重写JNI以提供更好的Iso14443-A支持。这可以改善EMV卡检测。
几周后再次检查SDK.Cheers的新版本。
以上来自于谷歌翻译
以下为原文
Hello Ivan,
Thanks for your question.
What version of the
ST25R3911B Discovery.exe program are you using?
Do you already know the UIDs of the cards that you are trying to detect and fail? Are they 4, 7 or 10 byte long? Could you please give us an example of UID format?
The ST25 SDK contains a RF library that is independent from readers. As shown in your code excerpt, each reader must provide a RFReaderInterface implementation.
The STReader library provided in the ST25 SDK contains an implementation for the ST25R3911B-DISCO board. A Java Native Interface (JNI) is used for the library to interact with the native ST25R3911 dll. The JNI uses its own anti-collision algorithm, different from the native ST25R3911 firmware. So this is already one difference.
Version 1.0.1 of the ST25 SDK focuses on tags from the ST25 family. It has not been tested with EMV cards but basic discovery should function if those tags follow ISO and NFC Forum protocols.
Today, only ISO15693 and ISO14443-A protocols are supported by the ST25 SDK and the ST Reader implementation. ISO 14443-B (used in some EMV cards) is not yet covered. So EMV cards based on ISO 14443-B will not respond to the inventory request.
However you mention in your mail that all cards are of type Iso14443-A.
You can try varying the distance of the cards to the reader's antenna. The
ST25R3911B Discovery.exe programs tunes the reader in the most efficient way. This tuning is not done with the ST25 SDK implementation and may result in a bad reader calibration.
For information, we are in the process of rewriting the JNI to provide better Iso14443-A support. This may improve EMV cards detection.
Check again in a few weeks for a new version of the SDK.Cheers.
举报
举报
