Flomio SDK

Tagged: Documentation, SDK

Viewing 7 posts - 1 through 7 (of 7 total)

Author

Posts
February 28, 2017 at 8:52 am #58880
Reece
Participant
Is there any other documentation for the SDK other than the README file?

For instance in the console log I can see Response APDU but I don’t know where to access the data. the ‘didRepspondToAPDUCommand’ does not seem to provide.

I am using Objective C but any additional documentation thats is available would be of great help.

Thank you

P.S here is an extract of the console output with a filter on ‘APDU’
```
2017-02-28 12:21:50.425776 NFC Test[455:85989] Command Apdu sent: FF CA 00 00 00
2017-02-28 12:21:50.607987 NFC Test[455:86093] in didSendPiccResponseApdu
2017-02-28 12:21:51.019442 NFC Test[455:86093] Response Apdu: CC 2C 33 01 90 00
2017-02-28 12:21:51.033414 NFC Test[455:85989] Command Apdu sent: 00 A4 04 00 07 D2 76 00 00 85 01 01
2017-02-28 12:21:51.033793 NFC Test[455:85989] Command Apdu sent: E0 00 00 60 00
2017-02-28 12:22:06.701154 NFC Test[455:85989] Command Apdu sent: 00 A4 04 00 07 D2 76 00 00 85 01 01
2017-02-28 12:22:06.701529 NFC Test[455:85989] Command Apdu sent: FF CA 00 00 00
2017-02-28 12:22:06.915217 NFC Test[455:86249] in didSendPiccResponseApdu
2017-02-28 12:22:07.324182 NFC Test[455:86249] Response Apdu: 63 00
2017-02-28 12:22:09.045224 NFC Test[455:85989] Command Apdu sent: 00 A4 04 00 07 D2 76 00 00 85 01 01
2017-02-28 12:22:09.045665 NFC Test[455:85989] Command Apdu sent: FF CA 00 00 00
2017-02-28 12:22:14.684339 NFC Test[455:85989] Command Apdu sent: 00 A4 04 00 07 D2 76 00 00 85 01 01
2017-02-28 12:22:14.684791 NFC Test[455:85989] Command Apdu sent: FF CA 00 00 00 00 00
2017-02-28 12:22:14.898852 NFC Test[455:86144] in didSendPiccResponseApdu
2017-02-28 12:22:15.281123 NFC Test[455:86144] Response Apdu: 63 00
```
February 28, 2017 at 9:00 am #58881

Scott
Keymaster

Hi Reece,

Because you are getting an error APDU Status Word: 63 00, it may be being returned in the error parameter of the delegate method. I would suggest updating to the Flomio SDK v2.2 if you have not already done so. You may need to alter the APDU to get a successful response from the reader.

Please let me know if you have any further questions,
Kind Regards,
Scott

February 28, 2017 at 9:14 am #58882

Reece
Participant

Hi Scott,

Thank you for the prompt response, I have tried upgrading to the v2.2 SDK, however I was not getting any console output so I have switched back to v2 for now in development.

Okay that makes sense, how do I access the error from the delegate is there is a particular syntax such as
readerManager.xxxx
or
[readerManager xxxx]

I have got a textfield for user input to the APDU so I was just testing any random string to see where the response was originating from. Sending APDUs such as FF CA 00 00 00 works correctly without throwing the 90 00 error response.

The README file is great for inital setup but does give much insight into how to use the classes in the SDK for development with. Is there any form of documentation for the SDK?

Thanks
Reece

February 28, 2017 at 9:35 am #58883
Scott
Keymaster
Hi Reece,

Unfortunately not at the moment, this is something we are working towards. You can look into the class header files to see methods / properties of each class but I wouldn’t really advise it because it may just confuse more.

Strange that you were not getting console logs, the SDK v2.2 is a big improvement on v2.0 and should not have affected the logs.

SDK v2.0:
I have just reproduced your error and I was able to get the 63 00 response in the
```
- (void)didRespondToApduCommand:(NSString *)response fromDevice:(NSString *)deviceId withError:(NSError *)error{
    dispatch_async(dispatch_get_main_queue(), ^{
        NSLog(@"%@",response); //APDU Response
        
    });
}
```
delegate method.

You would use the NSError parameter to get access to the error if there is one but the 63 00 (apdu error) is in the NSString response.

Kind Regards,
Scott
- This reply was modified 7 years, 9 months ago by Scott.
- This reply was modified 7 years, 9 months ago by Scott.
- This reply was modified 7 years, 9 months ago by Scott.
February 28, 2017 at 9:55 am #58887

Reece
Participant

Hi Scott,

Okay I might have a quick look at them for reference. Is there any other reports of v2.2 not producing logs and anything I could try to fix it?

That method was the one I thought would have the error response I will try accessing the response string and the NSError error.

Thank you for your help today

Kind Regards
Reece

February 28, 2017 at 1:23 pm #58889

Scott
Keymaster

There is a step in the README which mentions DEBUGLOGS, try this step to see if it changes anything and let me know.

Kind Regards,
Scott

March 1, 2017 at 8:59 am #58894
Reece
Participant
Hi Scott,

Console Output

As you can see from the console I have a line printing out:
2017-03-01 13:41:59.952161 NFC Test[618:164397] Response Apdu: 63 00
Also shown in the picture is the didRespondToApduCommand’
The response is not coming from there, and as you pointed out previously 63 00 is an error, but this is also not being shown.
```
- (void)didRespondToApduCommand:(NSString *)response fromDevice:(NSString *)deviceId withError:(NSError *)error{
   NSLog(@"%@", [NSString stringWithFormat:@"MyTest repsonse = %@, MyTest devideID = %@, MyTest error = %@", response, deviceId, error]);
```
Please could you advise where this APDU repsonse is accessed for use in the application.

Thanks
Reece
- This reply was modified 7 years, 9 months ago by Reece.
Author

Posts

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.

Forum Statistics

Recent Replies

140 CHAR WISDOM!