Has anyone else had their MediaTek GPS lock up, refuse commands, and send unrecognizable garbage?
While working to track down the "longitude error when in binary mode" bug, I noticed that my GPS would suddenly stop sending NMEA text messages and send garbage. Cycling the power sometimes fixed it. Letting it sit a while sometimes fixed it. Usually it took several tries to get it going again.
Symptom #2 is that instead of blinking at 1Hz (while trying to lock) or being solid on, the blue LED on the GPS will blink much slower. I'd say 0.5 Hz.
And a ps to Jordi: You may have a battery issue or a battery killing process issue. When I started seeing this I checked the back up battery voltage, one GPS was just 0.17 volts, the other was 2.97 volts. These units arrived less than a week ago.
I pulled the dead battery and ran a jumper from pin 1 (Vcc) to pin 4 (Vbackup) since the docs say in red that Vbackup must be present. That unit "resets" sooner than the unit with a battery, but also fails faster.
Here is a trimmed log of the output, right at the point where it locks up.
$GPGSA,A,1,,,,,,,,,,,,,,,*1E
$GPRMC,232523.422,V,,,,,0.00,0.00,210810,,,N*44
$GPVTG,0.00,T,,M,0.00,N,0.00,K,N*32
$GPGGA,232524.422,,,,,0,0,,,M,,M,,*4C
$GPGSA,A,1,,,,,,,,,,,,,,,*1E
$GPRMC,232524.422,V,,,,,0.00,0.00,210810,,,N*43
$GPVTG,0.00,T,,M,0.00,N,0.00,K,N*32
$GPGGA,232525.422,,,,,0,0,,,M,,M,,*4D
$GPGSA,A,1,,,,,,,,,,,,,,,*1E
$GPRMC,232525.422,V,,,,,0.00,0.00,210810,,,N*42
$GPVTG,0.00,T,,M,0.00,N,0.00,K,N*32
l’Žòl‚b⌐Œrlr’rlàl‚bŽ‚’n’€’ll<ðrlr’rlàl€bà‚Œlr쐀’’€‚bâìŒlŽŒ|ސüœbœbœbàbàbœbŽ‚bœlìpb’ŽŒl`ŒòŽ’€‚b€‚â‚bœbœbœbœ