-
-
-
Which app were you using with your Nexus 10 to test @Gordon? I used both NFC Tools and NFC TagInfo by NXP, the latter of which created far more NFC events.
With both apps and @AntiCat's FW, I can see Select CL1 commands reaching the JS event system (would have expected these to be handled and not propagated).
-
-
-
Playing with this more, crashes appear to be more common when the reader is removed, such as tapping the phone against the Puck then lifting it again.
Doing this with
digitalPulse(LED3, true, 300)
being called in response to the event, I managed to get the Puck to crash with the LED remaining on until the battery was pulled. -
-
I can reproduce this same issue using the Web IDE command pane and
1V92
.NRF.nfcURL('https://www.google.com');
- Touch tag to phone. Observe website is opened.
NRF.nfcURL();
- Touch tag to phone. Observe no website is opened.
NRF.nfcURL('https://www.google.com');
- Touch tag to phone. Observe no website is opened.
N.B. My Nexus 5X opens a new tab in the foreground with the URL, every time the tag is tapped, if the web browser is in the background.
-
It still experiences crashes when there's no
print
command but is connected to Web IDE (print
was the easiest for me to see in the browser, and to get readable messages). Using LEDs, but keeping it connected to the Web IDE, causes it to crash after a few repeated reads.Immediate commands work in the left pane - but not after it's crashed. Once it's crashed, it either disconnects immediately, or the Web IDE doesn't realise it's already disconnected until I try to issue a command.
Your example with
setTimeout
doesn't cause the Web IDE to crash. -
I'm experiencing an issue with my new Puck when using it's NFC while connected to the Web IDE.
While the Web IDE is connected to the Puck, if my phone attempts to read the Puck as an NFC tag, after one or two successive reads, the Puck will appear to crash. It will no longer be seen as an NFC tag by the phone, and the Web IDE will either disconnect automatically, or realise it's disconnected after trying to issue a command. I won't be able to detect the tag, or see it again in the Web IDE, until the battery is reinserted.
If I upload the code, save it, disconnect the Web IDE (and lift the battery on the Puck) the NFC tag will be correctly identified - and does not crash, even after a many successive reads. (Uploading the code and scanning the Puck without lifting the battery often meant the tag was not detected)
My example code:
NRF.on('NFCon', () => print('Hello world!')); NRF.nfcURL('https://www.google.com');
When the Web IDE is connected, I see a few
print
messages - but after 4 or 5 messages, the terminal output stops half way (Hello wo
) - and the Puck crashes. I don't have any issues with other functions when connected to the IDE, such as printing a message when the button is pressed, or setting LEDs.Has anyone else experienced issues with unreliable NFC behaviour when connected to the Web IDE?
Web IDE is running on a Macbook, using Chrome 58 and the internal Bluetooth.
Phone is a Nexus 5X, using Chrome to automatically open the URL in the NDEF message, and the "NFC Tools" app to read the Puck.
Puck is running the latest firmware available at the time of this post,1V92
.
Both - I was using
NFCon
events in1v92
(downloaded from here https://www.espruino.com/binaries/) andNFCrx
in AntiCat's.NFC TagInfo gives me more information on a tag - and was much easier to trigger crashes with.