Flomio ACR35 iOS SDK receiving unexpected errors

[ErkanParticipant]

Hi Team,

My name is Erkan i’m part of Boomset Inc. mobile development team. We have Guest checkin application used all around the world everyday. We wanted to add NFC functionality to our product.

So my story is ; we buy one Flomio – FloJack it’s hardware model ACR35 and implemented it to our product.

We are using APDU command to communicate with the NFC reader and we have – currently – two kind of tags Ultralight and Standard 1K.

My problem is ; Everything works great even we finished implementing UI and it’s almost product ready but device sometimes giving me error out of blue when we send command, and it’s breaking our UI chain then i have to stop the process wait few second and start again or reset the reader.

Fact check ; APDU commands are correct because everything is working fine but device can’t answer to same command sometimes or throw error “The parameter is invalid.”

Is it possible device getting over heated because of continuously requests coming from app or is there any known hardware problem?

Is there a way to or this hardware -ACR35- capable of detecting card and sending notification to interface before we asking / sending the APDU command.

Thanks for your help.

[HongbinModerator]

Why don’t using FloBLE? as I know, the bluetooth communication is better than audiojack, since the audiojack has compatibility issue, thanks

[RichardKeymaster]

@Erkan, there are several things that could be causing the issue. Intermittent performance is generally a result of low battery, low audio jack volume, interference across the audio jack or a combination of them all. Can you send me your console log output for us to study the behavior and give you some more insight on the issue?

As @Ben pointed out, the FloBLE readers are immune to problems like this since the BLE connection is more robust. That said, what you have described is definitely within the capabilities of the FloJack MSR. We have many customers using the reader continuously in the field with positive results. Most prominantly, Royal Caribbean:

thanks,
Richard

[ErkanParticipant]

Hey Richard thank you for response.

Sure;

The error code i’m getting from didNotifyResult:(ACRResult *)result is 254

Normally it giving me 0 when i sent read APDU for Ultralight FF B0 00 04 04h by using piccTransmitWithTimeout or request keys for Standard 1K and didSendPiccResponseApdu:(const uint8_t *)responseApdu length:(NSUInteger)length returns with response APDU and i’m using that data.

But sometimes it returns 254 error code in didNotifyResult and it did not enter to didSendPiccResponseApdu so i’m catching that error and re-sending the same command but device continuously giving me same error code until i stop the process and start again.

[HongbinModerator]

@Richard Thanks for your answer, sounds great of your solution, understood now. Thanks,

[Author]

Posts