July 29, 2016 at 9:51 am #56098
We are reading NDEF into NFC tag but we have discovered that we can only read 16 byte. We have 32 byte NDEF and we must read all the message.
We have found the follow post in your blog (https://flomio.com/forums/topic/ndef-parsing-problem/) but there is no limit explicated into the specification about your product (we have bought it without imagine this problem).
Can you help us? There is a solution?
ThanksJuly 29, 2016 at 10:29 am #56101
If you don’t mind, I need to ask you a few questions before I can help you with this. What type of tags are you using? Also, what reader are you using?
ScottAugust 1, 2016 at 3:39 am #56116
I’am using FloJack MSR : NFC Reader w/ SDK and Swiper
I’am using NFC tag, which in my case, contains the code 8048C682AF6A046
Thanks for your helpAugust 1, 2016 at 10:27 am #56120
Thanks for that info. Do you know any more details of the tag, is it Mifare Ultralight or NFC Forum Type 4 etc.? The most common tag that is used by our customers is Mifare Ultralight.
We currently don’t support reading NDEF with the FloJack MSR but we will be adding support in the coming weeks. I will release a beta this week for you to try as we begin to add 32 byte NDEF support for the MSR.
~ScottAugust 4, 2016 at 3:10 am #56144
the features of the tag are:
– NXP Mifare Ultralight (Ultralight C)
– NFC forum Tpe 2 and 4
Tell me if you need any more information.
RosannaAugust 4, 2016 at 12:08 pm #56150
Thank you for that info. Some type 4 tags currently do not work, and will not work for reading data yet.
This is in very early beta but the MSR can now read data from Mifare Ultralight. We will be adding support for reading more tags in the coming weeks.
Here is a link to v2.1 beta to begin reading NDEF data using your FloJack MSR.
Flomio SDK v2.1 (beta)
Please note that there has been changes to the structure of the SDK so you will need to refer to the README to configure your app correctly.
Please let me know if you have any issues.
ScottOctober 17, 2016 at 4:59 am #56890
I am a colleague of Rosanna,
We continue to have trouble in reading NDEF, with both version 1.9 and version 2.0.
In 2.0 we found the new didFindADataBlockWithNdef event but is never raised by our FlojackMSR.
We have seen that in the new version 2.1 the NDEF recognition has been improved, we followed the README’s example and finally didFindADataBlockWithNdef event fires but with parameter (NdefMessage *) ndef always null.
What can we try?
We wanted to try again with SendAPDU but in the new version there’s a “deviceId” parameter that we don’t have at the time of the call and the deviceId must be dynamic.
Where we must launch the call sendAPDU with the deviceId?
Do you have an example of correct use of sendAPDU command in 2.1 sdk?
Thank you in advance.
Softeco.October 17, 2016 at 11:34 am #56903
You do not need to send APDUs to trigger the didFindADataBlockWithNdef delegate.
When configuring your device, you can use @”Reader State” : kReadData and then the data will be read upon tap. As for the NdefMessage not being parsed correctly, this is frustrating to solve as we would need a sample of your tag to correctly identify the issue. Potentially the MSR is unreliably reading the data but it is likely an issue with the Ndef parser not working reliably with the data on your tags.
If you do want to send Apdus, when the device attaches, you can get the deviceId in the didUpdateConnectedDevices delegate.
FmDevce *thisDevice = connectedDevices; NSString *deviceId = thisDevice.serialNumber;
ScottOctober 18, 2016 at 7:47 am #56942
Do you want to try this update for Flomio SDK v2.1 (beta)
There has been a small fix added which should improve the BZR by detecting when a tag has left the range, this is only possible with the latest BZR firmware update. There has been no updates to the NDEF parser so any issues your tags were having with that will persist.
You must be logged in to reply to this topic.