06-21-2020, 07:19 AM
(This post was last modified: 06-21-2020, 07:32 AM by wibble.
Edit Reason: forgot to mention it wan't showing time
)
Ok - sensible looking output in ModemManager too, but taking too long to get a fix. It took several minutes even to get sats listed as in view in GPGSV messages, and after 10 minutes there was still no fix. Previous experiments have been a quick check to see that I was getting NMEA out of the gps tty, not expecting a fix as I was doing it indoors. This time I took it outside, so sky view but still within wifi range, phone with screen to the sky and powered from a USB battery. This is with Mobian, last updated Friday, installed on eMMC, with a SIM but without uSD.
If past experience is anything to go by, first fix without priming with downloaded ephemeris data is the trickiest phase, and local noise sources can push the signal to noise ratio just the wrong side of being able to get a fix. As an example the Openmoko GTA02 needed the drive strength of the uSD connection reducing before reliable gps fix was possible.
Still no fix...or time for that matter
If past experience is anything to go by, first fix without priming with downloaded ephemeris data is the trickiest phase, and local noise sources can push the signal to noise ratio just the wrong side of being able to get a fix. As an example the Openmoko GTA02 needed the drive strength of the uSD connection reducing before reliable gps fix was possible.
Code:
GPS | nmea: $GPGSA,A,1,,,,,,,,,,,,,,,,*32
| $GPRMC,,V,,,,,,,,,,N*53
| $GPGSV,3,1,09,08,57,286,23,20,41,067,26,21,45,068,25,27,82,111,27,1*6A
| $GPGSV,3,2,09,01,02,237,,07,17,291,,10,48,116,,11,27,260,,1*68
| $GPGSV,3,3,09,13,04,002,,1*59
| $GPVTG,,T,,M,,N,,K,N*2C
| $GPGGA,,,,,,0,,,,,,,,*66