t2 compatibility

[LinusU]

process.binding('hw') is removed and can no longer be used.

We need to write a pure JS NMEA parser or port the old one to a Node C++ addon.

[rwaldron]

https://github.com/jamesp/node-nmea

[johnnyman727]

Will be fixed with #21.

[dtex]

I've been playing with the GPS module on the T2 and not having any luck. I had been working on adding serial to tessel-io but wasn't getting any data so I came back to this repo and tried the examples but am not seeing any data that way either. So first question, has anyone else tried the example here on a T2 and had success?

[dtex]

Made sure that firmware, OS and CLI were all up to date. Turned on debugging and saw this output:

INFO Running bundled project...
high
GPS module powered and ready. Waiting for satellites...
low

And then nothing ever happens.

Then I wired up the a2235h to an Arduino and saw bytes coming in over serial. I need to get all my bit shifting happening properly to make sure I'm actually getting valid data, but I expect that I am.

[johnnyman727]

@dtex thanks for reporting your troubles! It was working for me when I updated the module a few weeks ago but haven't tried it since then. Could you put a console log within this data event and see if it's getting any data?

[dtex]

I'm seeing line after line of this:

<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>

[johnnyman727]

Interesting, that's what tessel/t2-firmware#126 was intended to fix. The GPS module starts at one UART baudrate but then switches to another after initialization. The old firmware wasn't allowing that switch so the data wasn't being interpreted correctly. I'll have to try this out with my own T2.

[johnnyman727]

@dtex I'm still able to get coordinates:

Can you open up /usr/lib/node/tessel-export.js on your Tessel and confirm these changes are there?

Also, you are sure that you are running off of the master branch of this repo, right?

[dtex]

Yes, I cloned this repo, but I see that I don't even have that file. Just tessel.js so maybe I didn't update my OS properly?

[dtex]

Sorry, My response was confusing...

I am using the master branch of this repo and it is the latest.

I looked in /usr/lib/node/ on my Tessel and only have tessel.js

I had used the prebuilt image of the OS. I'm going to try building from the repo.

[johnnyman727]

@dtex yeah, I suppose it's possible and a little worrying. I really need to get around to rewriting t2 update because it's been super flaky lately.

[dtex]

I didn't use t2 update. I downloaded the image, copied over to the tmp directory on my T2 and installed from there. I'm gonna' give t2 update a try

[dtex]

I'm seeing data now... So much for it being "flaky", it worked better than me updating it manually. I was grabbing my image from the link to the prebuilt binary on this page is that not the latest perhaps?

[johnnyman727]

Oh wow I forgot that page exists! Yes, that binary is super old. After you update, t2 version should return 0.0.7.

I fixed the docs in a PR here. Can you review it @dtex?

[dtex]

I think that's totally clear (and easy!).