Replies to This Discussion

Permalink Reply by Fabien Bruning on July 21, 2010 at 11:21am

Is it possible to flash the diydrones firmware onto another MT3329? Since it could be out of stock for weeks I was thinking of ordering another one and flashing the firmware.

• ▶ Reply

ModeratorPermalink Reply by Chris Anderson on July 21, 2010 at 11:38am

We just got 500 units in. It should be back in stock in a few days.

• ▶ Reply

Permalink Reply by Fabien Bruning on July 21, 2010 at 11:44am

That's great, thanks for the quick response!

• ▶ Reply

Permalink Reply by Christopher Beasley on July 21, 2010 at 6:22pm

Is it supported by the Alpha code drop that just came out?

• ▶ Reply

Permalink Reply by Mario on November 6, 2010 at 5:36pm

Hi Guys/Girls

I do not know how much you might be interested in this because you seem to do mostly embedded control of the MTK GPS, but my multiplatform opensource program BT747 might interest you.
BT747 knows most of the MTK NMEA commands and it can fetch and upload AGPS data. You might not be logging data, but it is also built do download and convert logged data.

You can check it out at http://www.bt747.org.

• ▶ Reply

Permalink Reply by Rick M on May 12, 2012 at 9:50pm

Can someone clarify the time field in the DIYDrones custom binary protocol? Looking at the doc, it's some kind of binary-coded time, but the AP_GPS_MTK16.cpp code treats it as a long integer and does some math. The comment isn't clear, but it looks like it's trying to convert the time to millisecond time-of-day. I'm not sure why they chose to do that. It's much more useful to have a full time from some epoch for later log analysis.

The code does this:

long time_utc = _buffer.msg.utc_time;
long temp = (time_utc/10000000);
time_utc -= temp*10000000;
time = temp * 3600000;
temp = (time_utc/100000);
time_utc -= temp*100000;
time += temp * 60000 + time_utc;

It would be much easier to understand the final logged timestamp if the doc here was clear, but it seems unsure of itself, and what it's showing seems...lame.

https://docs.google.com/Doc?docid=0ASI4WbhJsiyqZDk3MndtYl8yNmczbXFm...

• ▶ Reply

Permalink Reply by Rick M on May 13, 2012 at 12:06am

OK, I found the protocol specification for the MTK v1.6. The times are indeed binary-coded HH:MM:SS.SSS, which I find incredibly cumbersome, but whatever.

One problem I did see was that the altitude returned from the MTK was (for my location) "1864", which, according to the docs, is 18.64 m above MSL. But in NMEA mode, it's reporting 175.5 M. I'm pretty close to sea level here, so I don't know what either mode is doing. Any ideas?

• ▶ Reply

Permalink Reply by Grunt on May 14, 2012 at 6:53pm

18.64 m ...I would say that is close to sea level...Compared to 7200 feet. How many satalites did you have locked?

• ▶ Reply

• ‹ Previous
• 1
• …
• 3
• 4
• 5
• Next ›
• Page