使用Android SDK的ST24DV标签问题解答

你好安德烈亚斯，
首先，对于所有快速传输命令，必须使用ST25DVTag.enableMailbox（）命令启用邮箱。
问题1：
myST25DVTag.readMailboxMessage（0,0）将读取I2C接口写入的邮箱的完整内容。以下陈述是等效的。
 
 response = myST25DVTag.readMailboxMessage（0,0）;
完成相同的结果：
 int len = myST25DVTag.readMailboxMessageLength（）;
 
 response = myST25DVTag.readMailboxMessage（0，len）;
问题2：
myST25DVTag.readMailboxMessage（0,1）将抛出BAD_PARAMETER STException。
这是因为这一事实
ST25DVTag。
readMailboxMessage（int address，int size）获取要从邮箱中读取的实际字节数。标签理解的RF命令返回（大小+ 1）字节。
要使用RF命令读取字节，您需要发送（大小+ 1）值为0.当对地址0执行此操作时，该命令将实际返回邮箱的全部内容，如问题1所示。
 
由于标记的行为，决定为参数元组（0,1）抛出BAD_PARAMETER异常。
如果要读取第一个字节，建议读取邮箱的完整内容，然后选择第一个字节。
关于你的问题3：
ST25 SDK可用于Android或任何Java应用程序。
readers 目录中的库为ST和FEIG ELECTRONIC的USB读卡器提供支持。
ST类型5读卡器支持快速命令，但不适用于Android手机。
有关快速传输模式流程的更多信息，请参阅本应用笔记：
 
http://www.st.com/resource/en/application_note/dm00328899.pdf
 最好的祝福



以下为原文




Hello Andreas,
First, for all the fast transfer commands , you must enable the mailbox with the ST25DVTag.enableMailbox() command.
For question 1:

myST25DVTag.readMailboxMessage(0,0) will read the full content of the mailbox as written by the I2C interface. The following statements are equivalent.
      
      response = myST25DVTag.readMailboxMessage(0, 0);

accomplishes the same result as:
      int len = myST25DVTag.readMailboxMessageLength();

       response = myST25DVTag.readMailboxMessage(0, len);
For question 2:


myST25DVTag.readMailboxMessage(0,1) will throw a BAD_PARAMETER STException.

This arises from the fact that
ST25DVTag.
readMailboxMessage(int address, int size) takes the actual number of bytes that you want to read from the mailbox. The RF command understood by the tag returns (size + 1) bytes.


To read a byte with the RF command, you would need to send a (size + 1) value of 0. When doing so for address 0, the command will actually return the whole content of the mailbox, as seen in question 1.



Because of the tag's behavior, it was decided to throw a BAD_PARAMETER exception for the parameter tuple (0, 1).


If you want to read the first byte, it is recommended to read the full content of the mailbox then select the first byte.
Regarding your question 3:
The ST25 SDK can be used for Android or any Java applications.
Libraries in the readers directory provide support for USB readers from ST and FEIG ELECTRONIC.
Fast commands are supported by ST type 5 readers but do not apply to Android phones.
More information on the fast transfer mode flow can be found in this application note:

http://www.st.com/resource/en/application_note/dm00328899.pdf
Best regards

你好Damien，
非常感谢你非常详细的答案！然而，我仍然不明白，为什么
byte [] sendByte = {0xAA};
 
mST25DV.writeMailboxMessage（sendByte）;
 
byte [] recByte = mSt25DV.readMailboxMessage（0,0）;
回报
{0x00,0xAA}
 对于recByte
。为什么第一个零字节被添加？另外我有一个新问题：在测试填充整个256字节邮箱所需的时间时，我来到了
java.io.IOException：收发长度超过支持的最大值
尝试发送超过241个字节时发生异常。我认为这是一个Android / Java问题，你能证实这一点吗？
期待着听到您的意见，
安德烈亚斯



以下为原文




Hello Damien,
thank you very much for the very detailed answer! However what I still dont understand is, why

byte[] sendByte = {0xAA};

mST25DV.writeMailboxMessage(sendByte);

byte[] recByte = mSt25DV.readMailboxMessage(0,0);
returns
{0x00, 0xAA}
  for recByte
. Why is that first zero-byte added?Plus I  have a new question: While testing how much time it takes to fill the whole 256 bytes of the mailbox, I came to the point where a
java.io.IOException: Transceive length exceeds supported maximum
exception occured when trying to send more than 241 bytes. I think this is a Android/Java problem, can you confirm this?
Looking forward to hear from you,
Andreas

嗨安德烈亚斯，
返回的第一个字节
 
byte [] recByte
mSt25DV.readMailboxMessage（0,0）;
 实际上是Iso命令的状态字节。值0x00表示操作成功。
错误值以字节0x01开头，后跟Iso15693规范文档中描述的错误字节。
要检索实际的邮箱消息，请复制不带第一个字节的字节数组：
byte [] message = Arrays.copyOfRange（
recByte
，1，recByte
。长度）;
但是，我认为您刚刚指出API中的不一致，因为在读取大小= 1的情况下不返回状态字节...这有点乱。正确的解决方法是删除所有读取大小的状态字节，但需要主要版本的st25sdk库（并打破现有的应用程序）。感谢您提请我们注意这一点。
对于Android Transceive长度错误，这可能来自智能手机上的IsoDep实施。虽然ST25DV标签可以发送高达256字节数据的响应+ 7字节协议= 263字节，但并非所有NFC读取器和控制器都可以容纳这个长度。
这就是我们在RFReaderInterface API中添加了getMaxTransmitLengthInBytes（）和getMaxReceiveLengthInBytes（）方法的原因。调用那些来获取设备支持的最大值，然后相应地设置max read命令（考虑到ST25DV数据表中详细说明的readMessage命令的7字节开销）。
最好的祝福，
达米安



以下为原文




Hi Andreas,
The first byte returned by


byte[] recByte
mSt25DV.readMailboxMessage(0,0);
is actually the Iso command's status byte. A value of 0x00 means a successful operation.

Error values start with byte 0x01 followed by the error byte described in the Iso15693 specification document.

To retrieve the actual mailbox message, copy the byte array without the first byte:
byte[] message = Arrays.copyOfRange(
recByte
, 1, recByte
.length);
However, I think you just pointed out an inconsistency in the API as the status byte is NOT returned in the case of a read size = 1... It's a bit of a mess. The correct fix would be to remove the status byte for all read sizes but would require a major release of the st25sdk library (and break existing apps). Thanks for bringing up this point to our attention.

For the Android Transceive length error, this may come from the IsoDep implementation on your smartphone. While the ST25DV tag can send responses up to 256 bytes of data + 7 bytes of protocol = 263 bytes, not all NFC  readers and controllers can accommodate this length.

This is why we have added getMaxTransmitLengthInBytes() and getMaxReceiveLengthInBytes() methods in the RFReaderInterface API. Call those to get the max value supported by your device then set your max read command accordingly (taking into account those 7 bytes of overhead detailed in the ST25DV's datasheet for the readMessage command).

Best regards,

Damien

非常感谢你！ SD25 SDK非常好用，但文档可能会更好一些。另一方面，如果有一个代码（大多数情况下）解释自己，并且这个代码无法通过代码回答的问题论坛，谁需要一个文档

嗨安德烈亚斯，
我们已经考虑了你的评论。
SDK 1.2.0版删除了不连贯的返回
readMailboxMessage（n，1）。
从现在开始，在所有读取大小的情况下，在数据之前返回状态字节。
请参阅以下帖子：
https://community.st.com/message/198545-st25-sdk-v120-available-online



以下为原文




Hi Andreas,
we have taken your remark into account.
Version 1.2.0 of the SDK removes the incoherent return of the
readMailboxMessage(n, 1).
The status byte is returned before the data in all cases of read sizes from now on.
See the following post:

https://community.st.com/message/198545-st25-sdk-v120-available-online