July 8, 2015 at 4:57 am #53121
I received the FloJack today, thank you for that. I’ve downloaded the NFC Actions App from the Apple Store, charged the FloJack and tried to communicate (“Read Tag” in you App) with different NFC tags (AMS AS3955 Tag, ST M24LR Tag etc… -> ISO14443A). But nothing happened. After that, I measured the resonance frequency with a “miniVNA pro” -> 14.2 MHz, that’s OK. But I didn’t measured any H-field (volume of the iPhone is max).
What should I try next to bring it to life?
MarcJuly 8, 2015 at 10:46 am #53122July 8, 2015 at 10:59 am #53123
Richard, thank you for the hint. Therefore it is possible to get the beta version of the app which support the FloJack V2? Could I send you my Apple e-mail address for TestFlight?July 8, 2015 at 11:02 am #53124
I just added the email we had on file for you to the TestFlight tester list.. let me know if you don’t get it or rather use a different account.July 8, 2015 at 11:19 am #53125
Richard, I use another e-mail address. But I don’t want to make it public here in the forum…July 8, 2015 at 11:20 am #53126July 8, 2015 at 11:21 am #53127
I’ve sent it to you by mail…July 8, 2015 at 11:45 am #53128
Sent out the invite.. let me know if you don’t see it.July 9, 2015 at 2:38 am #53135
I’ve downloaded the app, but the screen is just “white” and the LED on the FloJack doesn’t shine. How should I use the App to read out the UID of my tag?July 10, 2015 at 11:55 am #53147
Marc, once the app has been installed it should have asked for permission to access the microphone. Then plug/unplugging the FloJack should show you a notification of the state change and the green LED on the FloJack should turn on. At this point you should be able to place Mifare Ultralight, Classic, NTAG, or Mini tags on the surface of the reader, right over the Flomio logo. Within 1sec of doing so you should hear a scan sound and view tag data on the log screen (main white area). You can navigate the options in the settings screen by hitting the gear at the bottom of the screen.
Let me know if you still are having issues. There’s a chance that he latest version we pushed to TestFlight has an issue we missed during testing internally.
You must be logged in to reply to this topic.