Open GoogleCodeExporter opened 9 years ago
Or just we just erase PSTR.
Original comment by mail.ima...@gmail.com
on 23 Feb 2013 at 3:35
My comments are based on I2C_GPS_NAV_v2.2Beta1-r62.rar and using the UBlox
CN-06 GPS unit that has no EEPROM fitted.
Indeed PSTR doesn't work with Serial.Write(). I have added a helper function to
allow the strings still to be stored in program memory.
There are other problems to:
1) I think line no:1513 in I2C_GPS_NAV_v2_2.ino "lastframe_time = millis();"
is in the wrong place. It should be moved up to after line no: 1477
The way it is in r62 the variable lastframe_time is only updated when we have a
(3D fix && we have 5 or more sats). This stops the single led blink from
indicating a good packet, and the double led blink from indicating a 2D fix.
2) I find the delay(5); on line no:1283 essential, without it the GPS fails.
3) I find bridging of pins 13 and 14 on the NEO-6M module essential also.
Attached are my changes with comments.
Original comment by th9...@gmail.com
on 5 Apr 2013 at 2:13
Attachments:
Bang on! #2 th9 your version fixed the issues I was having with my v2 CN-06 as
well.
Additionally I had to change the definition of UBLOX_INIT to:
const char UBLOX_INIT[] PROGMEM = {
I think that's because I am using Linux and GCC does not support the older
progmem typedefs, but I am no expert so I'm not sure.
I think your point about moving lastframe_time was spot-on as well but I
haven't dug deep on that - indeed it looks like it was a bug.
Are any fixes likely to be committed? I see no changes to the repo since last
year.
Thanks for your tips, certainly restored my sanity after a few late nights
trying to get this puppy going!
Original comment by goo...@purple.dropbear.id.au
on 23 Jul 2013 at 2:52
No problem, glad it helped. I have no idea if this will ever get commited. I
would have thought raising an issue and then posting the fix would have spurred
some action !
Original comment by th9...@gmail.com
on 24 Jul 2013 at 11:23
I'm guessing that EOSBandi has plenty of other things on his plate. At least
with your fix now "tested" by another user it might make it easier to consider
for inclusion.
I've taken the liberty of attaching your changes as a patch which also includes
my change to the progmem stuff, hopefully that will make it easier to merge in.
Original comment by goo...@purple.dropbear.id.au
on 24 Jul 2013 at 11:07
Attachments:
Hi,
Sorry to resurrect an old thread, but I found this key to getting GPS working
for me.
Your suggested changes are DEFINITELY needed to get the Crius I2C-GPS Nav board
talking to a ublox based GPS module (i.e. VK16D) that does not have EEPROM (it
was supposed to have one, but with the config WORKING with your changes, it is
not needed!!!!) I was dead in the water until I made your changes. As a bonus
I can run the GPS at 57200 the optimal rate. THANK YOU!!!!
Original comment by kirkb4...@gmail.com
on 6 Nov 2014 at 1:13
Attachments:
It's good to here this is still helping people out. Thanks for the thanks !
Original comment by th9...@gmail.com
on 6 Nov 2014 at 10:08
Original issue reported on code.google.com by
mail.ima...@gmail.com
on 23 Feb 2013 at 3:31