Sean Lynch

I think I might see the issue in your code... ```js var commandBuffer = [ commAsTarget, mode, mifareParams, felicaParams, nfcId3t, generalBytesLength, historicalBytesLength ]; ``` Things such as `mifareParams`, `felicaParams`, etc...

You should wait for `emulateTag()`'s promise to resolve (wait on its ACK) before sending `emulateGetData()`. ``` rfid.emulateTag().then(function() { console.log('emulateTag initialized'); rfid.emulateGetData().then(function(data) { console.log('dataRead : ', data); }); ```

Nothing is jumping out at me so far. Receiving the `8D` (141) command after the `8C` (140) looks correct. 8C command mode (request): 5 (`00000101`) - not used (`0000`) -...

Well, incremental progress 😄. Hmm, so looking at the data of command `0x87` (`135`): `00 a2 04 03 1a 91 01 4f`, it looks like the first byte is for...

You were writing the NDEF messages mentioned above right? ``` messages: [ { tnf: 1, type: 'U', id: [], payload: [ 1, 103, 111, 111, 103, 108, 101, 46, 99,...

I read a little more into Seeed-Studio's emulatetag.cpp and I don't believe the last byte (`0x4f`/`79`) is a checksum, but I'm not sure why it's not `11`. It would be...

Btw, I also have this [spreadsheet](https://docs.google.com/spreadsheets/d/1IJNzGNl7qdgCePklrghU54n4hOx5E6y20rEpZw0gJhc/edit#gid=0) that I created a while back to help me decipher NFC tag data / NDEF messages. If you look at the second tab (NDEF...

I need this documented better, but currently what is in master (and released on NPM) is not working. There is an I2C branch that I had working, but it still...

@cthayer Thanks for the PR. I'm not sure it's needed though since I2C on master is not functional (with or without the PR). I would rather merge in the I2C...

@justgeek that looks great. The reason I created this library was to have a pure node-native library that didn't depend on LibNFC (which I was having trouble building/configuring correctly last...