with gps_time, I also got once

UHD Error:
  get_nmea(): unsupported GPS or no GPS detected
UHD Error:
  get_token: too few token in reply
UHD Error:
  get_token: too few token in reply

then it prints out always the same value, which is not the right time

After this, I make another run, UHD does not says anymore "found Jackson
Labs GPS", but "found a generic NMEA GPS device"
Though the gps_time query returns a correct value

Only a power cycle brings the starting string "Found a Jackson Labs GPS"
I have also seen an uncorrect value returned once or twice (I query gps_time
or gps_locked 100 times in a row in my code)

I start to wonder if the GPSDO is inserted properly ? (but it's hard to
mistake on that)
If the GPSDO is broken ?
Or is it only a SW issue ?

Also, if this issue can not be solved, there should be a way to check if
sensor_value_t is valid or not (by adding an isValid field for example ? )

By the way I use Windows7

On 2 August 2011 17:44, Nick Foster <n...@ettus.com> wrote:

> Bastien,
>
> Does gps_time work correctly 100% of the time for you?
>
> --n
>
> On Tue, 2011-08-02 at 17:08 +0000, Bastien Auneau wrote:
> > Hi All
> >
> > On USRP N210, UHD 3.2.1
> > GPS does lock, because it gets the right time (not the 01/01/2006 set at
> > init)
> > using get_mboard_sensors("gps_locked") fails sometimes
> >
> > 1.
> > It may print on console :
> >
> > UHD Error:
> >   get_nmea(): unsupported GPS or no GPS detected
> >
> > while at the start of the code, it always prints :
> >
> > Found a Jackson Labs GPS
> >
> > At this pont, I have to reboot the USRP. I have seen this error twice on
> > 20 to 25 runs
> >
> > 2. Or :
> >
> > UHD Error:
> >   get_token: too few tokens in reply $GPGGA,  [etc... then there are
> > more or less args after that, randomly)
> > GPS lock status: locked
> >
> > This second error occurs 1% of the time, but following
> > get_mboard_sensors("gps_locked") succeed (no need to restart USRP)
> >
> > 3. Which leads me to :
> > How do you check if a get_mboard_sensors(...) fails or not ?
> > Because even when it fails, the value returned seems ok. And there is no
> > error field.
> > Or should this not happen ?
> >
> > Thanks and Regards
> > Bastien
> >
> > _______________________________________________
> > Discuss-gnuradio mailing list
> > Discuss-gnuradio@gnu.org
> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
>
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to