[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-users] After RELEASE_TIME device closed, gpsd reports error on

From: Bin Guo
Subject: Re: [gpsd-users] After RELEASE_TIME device closed, gpsd reports error on next open
Date: Mon, 9 Sep 2019 14:40:47 +0000

Sorry for clicking reply too early, again my edited reply below...

Not gonna see much with no antenna.

I did later tested with antenna, and got 3d fix. though still trying to confirm PPS working...

> root@5gsb:~# /usr/sbin/gpsd -F /var/run/gpsd.sock -P
> /var/run/ /dev/ttyPS1 -N

Why are you doing that?
Why use "-F /var/run/gpsd.sock" and "/dev/ttyPS1"?

I was using yocto project packaged gpsd script. I don't think we really need -F to edit device list  since we are running on a customized board with a fixed u-blox chip communicating using UART: ttyPS1 is the name chosen by device tree.

Why are you not using "-n"?  You should always use "-n" unless you
are on battery and power is very important.

Will try -n, thanks for the advice! I hope that in that case I only need to look at shm...

All normal because you did not use "-n".

> next gpspipe call shows that gpsd never gets back to UBX-... mode but
> gets stuck in a bad state:

That can happen, so use "-n" to avoid it.  Might be related to whatever
/dev/PS1 is.  How long did you wait?  resync can take minutes.

I did make a patch attached to handle reactive event inside ubx driver which seems to fix this mode issue. This should be enough for us now (prefer -n and will test it), but is this applicable to general ublox driver?

Thanks again for the help!

Attachment: z020-ublox-reactivate-hook.patch
Description: z020-ublox-reactivate-hook.patch

reply via email to

[Prev in Thread] Current Thread [Next in Thread]