Re: NMEA error on cat /dev/ttyACM0

[Lucien Van Elsen]

Seán-

  If you're looking at the data straight from /dev/ttyACM0, gpsd is not involved - that's straight from your GPS.  When you say it's giving wrong results, that's an issue with your receiver, not gpsd.

  Do you have an example of one of the bad GPRMC sentences?  Of particular interest is the third field, which is the status - is it 'A' (valid data) or 'V' (not valid)?

On Tue, Aug 30, 2022 at 4:46 AM Seán Mac Suibhne <smacsuibhne@yahoo.com> wrote:

Sorry I should have said that the laptops rub XUbuntu 22.04, the Raspberry Pis are using Bullseye and are fully updated running GPSD 3.22-4

Beir bua

Seán

On Tuesday 30 August 2022 at 00:02:14 IST, Seán Mac Suibhne <smacsuibhne@yahoo.com> wrote:

Hi,

I have several GPS usb dongles and use them on laptops and raspberry pis

This the output of lsusb for one of the dongles

    Bus 004 Device 003: ID 1546:01a7 U-Blox AG [u-blox 7]

for some time now I notice the result of

    cat /dev/ttyACM0

gives the wrong latitude and longitude which wasnt a problem as I use them to get time and date on the raspberry pis

When I

    telnet  localhost 2947

and put in

    ?WATCH={"enable":true,"nme":true}

I also get the same errors

However if I put in

    ?WATCH={"enable":true,"json":true}

I get the correct lat and long

When I use gpsmon cgps and xgps I also get the correct lat and long.

Why is cat /dev/ttyACM0 not giving the correct values for lat and long anymore and how can I correct it?

All the best

Seán Mac Suibhne

BTW I use  

    cat /dev/ttyACM0 | grep -a GPRMC >> gps.log 

to record my location when I move locations on a raspberry pi