From MAILER-DAEMON Mon Oct 23 09:30:38 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1e6coQ-0003Vc-K0
	for mharc-gpsd-dev@gnu.org; Mon, 23 Oct 2017 09:30:38 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:49857)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <valizadeh.hs@gmail.com>) id 1e6c4B-0003ST-T2
	for gpsd-dev@nongnu.org; Mon, 23 Oct 2017 08:42:52 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <valizadeh.hs@gmail.com>) id 1e6c4B-0002D1-1t
	for gpsd-dev@nongnu.org; Mon, 23 Oct 2017 08:42:51 -0400
Received: from mail-qt0-x233.google.com ([2607:f8b0:400d:c0d::233]:56804)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <valizadeh.hs@gmail.com>)
	id 1e6c4A-0002CJ-TH
	for gpsd-dev@nongnu.org; Mon, 23 Oct 2017 08:42:50 -0400
Received: by mail-qt0-x233.google.com with SMTP id z28so25861928qtz.13
	for <gpsd-dev@nongnu.org>; Mon, 23 Oct 2017 05:42:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:from:date:message-id:subject:to;
	bh=H3EhT3HKt3EOIT7WX3E8ECsiOnzWE70fwO4gpYlSxhI=;
	b=llNt3AM8UDZYLzNFYdCFjcuP9PVWUL8n9IXF6kOT4bCh4yJHGb6YFhFYkxL/k4Mq30
	B30nIVUST4cBuJHgZYTy5LiimqHwUxA0iBDDNkTXJARTay5TYNuopNsS9RRPFgOq+W2M
	OBUW+e6RAkpoLUsKdL/Y8Ge07dKhopSLysDftSuSgQeJ1A7S/IewHUbeLKmK08z7CH93
	gur3OYWQ6MbGfz40U2YDc1DEA7AedfRzNdzv4mLgRGUWtt1Wa56EiIoFF9+rnVoRanzK
	y2r/3YT4yk+dfX/NWciADPtxekgrO9dbTp9cJo18gUwmjupH52k1pcaLCepH6X45PeVJ
	YtYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
	bh=H3EhT3HKt3EOIT7WX3E8ECsiOnzWE70fwO4gpYlSxhI=;
	b=XrmFexlNmexSrjS1UKNgwKdP3UzfeCpyx222yrUQGT0W1TNADiuAOycCjShWXEzMDv
	S1sKw0ekDxxK6PFJ3Rt9q873/BKFi5ZJgtxJ9h6JnVqbGg/BO1at9DDEfTjFyXv5Ikot
	1HhME80SlQsvphldL9HAi54VQfKbcVVY6sKqMNmTXYDW/1f0LRqToSe9ORNvkyKFK2oO
	bm2Z0HrGDCDRd3NJUCqe5pRnF48TKagYv1//X+TqE7TsFpG9euZurI+wfgUKvGpJncM0
	RMRV0T6auSzd13aaa1eVZGPYCGQblBY/J6j5InN77uaOkc3xus6XvFDtG3GK/Cq1iT+w
	q3fQ==
X-Gm-Message-State: AMCzsaUyrZjRj8kt8gGX8RLz7rsqhYzcNUhpMPTocBNdJutFw9bqwSII
	aRu4zq+QbixWha4nLvb3QlywOYfiGuxxGnmnk5BxdA==
X-Google-Smtp-Source: ABhQp+T469cmPFG7LhKVygFN/TgX9OH5WZIoKiu4mB21NBb4dik4DQWQvgSAdqzaaD9zie3flf7RXlA5/C9FSk4zu9Q=
X-Received: by 10.200.46.58 with SMTP id r55mr19650965qta.244.1508762568842;
	Mon, 23 Oct 2017 05:42:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.41.68 with HTTP; Mon, 23 Oct 2017 05:42:48 -0700 (PDT)
From: hossein vz <valizadeh.hs@gmail.com>
Date: Mon, 23 Oct 2017 16:12:48 +0330
Message-ID: <CAK3H06FSiAiB7D6=aVoq6-7nSui=Vtp+eoiC3LgB3Od95kf53w@mail.gmail.com>
To: gpsd-dev@nongnu.org
Content-Type: multipart/alternative; boundary="001a1137b440f76293055c36289a"
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2607:f8b0:400d:c0d::233
X-Mailman-Approved-At: Mon, 23 Oct 2017 09:30:37 -0400
Subject: [gpsd-dev] gpsctl via gpsd
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev/>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Oct 2017 12:42:52 -0000

--001a1137b440f76293055c36289a
Content-Type: text/plain; charset="UTF-8"

hi
i have connected a GPS to raspberry pi and installed gpsd afterwards.
by default the gps is sending nmea messages
i am able to change it to binary protocol using
gpsctl -f -n /dev/ttyAMA0

how am i able to do this via gpsd service? so that when PI is powered on
this there be no need to o this manually?

--001a1137b440f76293055c36289a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>hi=C2=A0</div><div>i have connected a GPS to raspberr=
y pi and installed gpsd afterwards.</div><div>by default the gps is sending=
 nmea messages</div><div>i am able to change it to binary protocol using=C2=
=A0</div><div>gpsctl -f -n /dev/ttyAMA0</div><div><br></div><div>how am i a=
ble to do this via gpsd service? so that when PI is powered on this there b=
e no need to o this manually?</div></div>

--001a1137b440f76293055c36289a--


From MAILER-DAEMON Mon Oct 23 14:43:15 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1e6hgx-0003hc-Nv
	for mharc-gpsd-dev@gnu.org; Mon, 23 Oct 2017 14:43:15 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:57850)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1e6hgv-0003hI-9y
	for gpsd-dev@nongnu.org; Mon, 23 Oct 2017 14:43:14 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1e6hgu-0000wm-EL
	for gpsd-dev@nongnu.org; Mon, 23 Oct 2017 14:43:13 -0400
Received: from rellim.com ([2001:470:e815::19]:58517 helo=spidey.rellim.com)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <gem@rellim.com>) id 1e6hgu-0000tF-6c
	for gpsd-dev@nongnu.org; Mon, 23 Oct 2017 14:43:12 -0400
Received: from spidey.rellim.com (dave.rellim.com
	[IPv6:2001:470:e815:0:0:0:0:19] (may be forged))
	(authenticated bits=0)
	by spidey.rellim.com (8.15.2/8.15.2) with ESMTPSA id v9NIgrgV010168
	(version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO)
	for <gpsd-dev@nongnu.org>; Mon, 23 Oct 2017 11:42:58 -0700
DKIM-Filter: OpenDKIM Filter v2.10.3 spidey.rellim.com v9NIgrgV010168
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=rellim.com; s=kong;
	t=1508784178; bh=BFGIt4c5qZO0gFrZQ8qkMesazGlhqGSlvp2ahKQq6KU=;
	h=Date:From:To:Subject:In-Reply-To:References;
	b=f0p4qd0ylsOIldjwVvyHohSEg/QUzjrruTTh/5XD974e/UQtZunP+mn5vo8nL2P7o
	ykfn+3k0F27xucyVaVsIuPe454jhjFyfWO0DjjHwzIUoWhCWXQf6wianvVbTxPezvW
	Eqng1k+w+LeYaNz1IcR7gsA3Wgcuj4V/3fKm0iSI=
Date: Mon, 23 Oct 2017 11:42:47 -0700
From: "Gary E. Miller" <gem@rellim.com>
To: gpsd-dev@nongnu.org
Message-ID: <20171023114247.3c244783@spidey.rellim.com>
In-Reply-To: <CAK3H06FSiAiB7D6=aVoq6-7nSui=Vtp+eoiC3LgB3Od95kf53w@mail.gmail.com>
References: <CAK3H06FSiAiB7D6=aVoq6-7nSui=Vtp+eoiC3LgB3Od95kf53w@mail.gmail.com>
Organization: Rellim
X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	boundary="Sig_/qQBa5B/cZsER_hN5cDzkMYI";
	protocol="application/pgp-signature"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2
	(spidey.rellim.com [IPv6:2001:470:e815:0:0:0:0:19]);
	Mon, 23 Oct 2017 11:42:58 -0700 (PDT)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2001:470:e815::19
Subject: Re: [gpsd-dev] gpsctl via gpsd
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev/>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Oct 2017 18:43:14 -0000

--Sig_/qQBa5B/cZsER_hN5cDzkMYI
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Yo hossein!

On Mon, 23 Oct 2017 16:12:48 +0330
hossein vz <valizadeh.hs@gmail.com> wrote:

> i have connected a GPS to raspberry pi and installed gpsd afterwards.
> by default the gps is sending nmea messages

OK.

> i am able to change it to binary protocol using
> gpsctl -f -n /dev/ttyAMA0

Yup.  But why bother?  The lat/lon/time is still the same.

> how am i able to do this via gpsd service?  so that when PI is powered
> on this there be no need to o this manually?

I assume you mean you are running under systemd?  You negelected to
mention the OS, distro and versions you are using.  So hard to give specific
advice.

gpsctl will work whether gpsd is running or not.  So you can just get that
by any means at startup.  For example, and gentoo, I put startup stuff
in /etc/local.d/baselayout.start

But, why bother?  The GPS output, whether NEMA or binary is still
the same data.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem@rellim.com  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can=E2=80=99t measure it, you can=E2=80=99t improve it." - Lord=
 Kelvin

--Sig_/qQBa5B/cZsER_hN5cDzkMYI
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENqCjEoytAEAuFCk8DQ7ZSUHRedgFAlnuOCcACgkQDQ7ZSUHR
edgCtAf9GZRGU8GA/bKKcVa5WQsbbfjQtEEAyV06cZ4Caz0pfuuezTmFEiwbzMZm
ueN+hOS7t4NQ0jfM3POgQPEtZ/OWiMa5WQY4ZvWwPOwt3CQVDtSQepZJrFeNpTMo
ZYA3AOcqtcxuLBYQi5y2XCuFoKmIpKfQqxIYl7mxE1dKalzCA/wDxrw4C2hicPpw
HJJrpayXXwJBzCPIGCt+5eiYe0eAHJK/wC/5uE75n1MBj46SHLPuFnkbRYA3V681
QmVweSoL1xTBmyGd/CJDAzXfIObCwyW7dtwtrSN4lR3xzGiTT30pGrr4B3TLJZr0
4xNSZUF6lHMzuBvH5WVInB8oOuaFhQ==
=z6Hy
-----END PGP SIGNATURE-----

--Sig_/qQBa5B/cZsER_hN5cDzkMYI--


From MAILER-DAEMON Sun Oct 29 09:24:51 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1e8na7-0002dN-9j
	for mharc-gpsd-dev@gnu.org; Sun, 29 Oct 2017 09:24:51 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:43046)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mike@thorcom.co.uk>) id 1e8kCl-0002OE-0N
	for gpsd-dev@nongnu.org; Sun, 29 Oct 2017 05:48:32 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mike@thorcom.co.uk>) id 1e8kCh-0001r5-Rk
	for gpsd-dev@nongnu.org; Sun, 29 Oct 2017 05:48:31 -0400
Received: from relay1.thorcom.net ([195.171.43.32]:33951)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <mike@thorcom.co.uk>) id 1e8kCh-0001nP-HW
	for gpsd-dev@nongnu.org; Sun, 29 Oct 2017 05:48:27 -0400
Received: from [2a00:2381:19c6::2000] (helo=mail.thorcom.co.uk)
	by relay1.thorcom.net with esmtps (TLSv1.2:DHE-RSA-AES256-SHA256:256)
	(Exim 4.89) (envelope-from <mike@thorcom.co.uk>) id 1e8kCY-00060B-K2
	for gpsd-dev@nongnu.org; Sun, 29 Oct 2017 09:48:18 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=thorcom.co.uk; s=thorcom; 
	h=Sender:Content-Transfer-Encoding:Content-Type:MIME-Version:Date:Message-ID:Subject:From:To;
	bh=tURHPxcrEx4GC6QYKWl2aA2byYiqeR4ENYpFdMK+wZM=; 
	b=uowNqOTHnSxhd0b21ztaFCgee2+/82qrl156EW9BCMKhSV4KUhpMjX9ISLWG5xULHUcyBGzzQW5FDtWbBPjY8fQ1/XOqTv7tLiIKNe9+EvR3fuAZmmsIA1dcL0JGChDhLEVUz9sk2ojH8C0/3JyqiA2ef8d99+QS39h+d1pFXUCJZ6OjjZQAYaZpOJc7uqssupcxoma0W91n4mKn0HZltE1/X6J1rgyR7gxZuF72hweLD6A5e3f8/D81ySu+Itf4A9k1ctsX8FUPLBdtyuXsr+efjZ/xjW7AmNhScO9dc9NIZDSge75NmYfNBwzkud8eeFQ5wUJ0cSux/6qsEcRnjA==;
Received: from gate.tubby.org ([82.68.212.65] helo=[192.168.144.20])
	by mail.thorcom.co.uk with esmtpsa
	(TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.82)
	(envelope-from <mike@thorcom.co.uk>) id 1e8kCX-0006fS-Q3
	for gpsd-dev@nongnu.org; Sun, 29 Oct 2017 09:48:17 +0000
To: gpsd-dev@nongnu.org
From: "Michael J. Tubby B.Sc. MIET" <mike.tubby@thorcom.co.uk>
Message-ID: <c0e3a79e-dd39-c435-3237-200d96f75187@thorcom.co.uk>
Date: Sun, 29 Oct 2017 09:48:15 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
	Thunderbird/52.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Sender: mike@thorcom.co.uk
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 195.171.43.32
X-Mailman-Approved-At: Sun, 29 Oct 2017 09:24:49 -0400
Subject: [gpsd-dev] GPDS hand hardware fault/alarm reporting
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev/>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Oct 2017 09:48:32 -0000


We have been using GPS receivers in vehicle location systems since the 
early 1990s and the Trimble Advanced Navigation Sensor (TANS) - if 
anyone remembers that - and have worked through multiple generations 
from SVeeSix, ACE to Lassen-iQ and have always used Timble's TSIP binary 
code.

We have a new product design and we've switched to Ublox MAX-M8W and I 
face a but of a dilemma, I could:

     a) keep our codebase and write a new UBX binary driver; or

     b) switch to using GPSD as effectively a Hardware Abstraction Layer 
(HAL) - our preferred route

Our platforms are ARM-based (i.MX6, Linux 4.1, Ubuntu 14.04 LTS server) 
and I have downloaded and built GPSD 3.19, got working with MAX-M8W on 
out platform, got NTPD working with shared memory and built a prototype 
test client - all in one evening!  While I'm impressed with the quality 
and ease of use of both GPSD and libgps it leaves us with a challenge 
for GPS receiver and antenna fault monitoring and reporting.

Our products are designed for business-critical and mission-critical 
users (e.g. Emergency Services and other government agencies). Equipment 
gets broken both accidentally and (on occasions) deliberately we need to 
monitor the hardware for faults as we generally need to get faulty 
installations fixed asap.

All of our products use an external antenna with active pre-amp and we 
monitor the power consumption of the pre-amp to determine whether the 
antenna is good or faulty, there are three conditions - "good", "open 
circuit" (not plugged in) and "short circuit".  These are reported via 
status bits in TSIP and UBX - some chips have the hardware built in 
while other's you have to add bits around the GPS receiver.

When using the proprietary binary interfaces, e.g. Trimble TSIP and 
Ublox UBX, additional instrumentation is available for faults and alarms 
and we use these as well.

Several receivers support 'battery backup failed' and or 'system RAM 
corrupt' at start-up along with 'DSP faults' and many newer GPS 
receivers support jamming detection by detecting the presence of in-band 
RF interference and flag this also.

I am only across the Trimble and Ublox GPS/GNSS receivers that we 
currently use but an approach for adding generic support these 
faults/alarms would be to add a new set of flags as a uint32_t called 
'gps.fault' or similar and define a set of values:

     GPS_FAULT_BATTERY_BACKUP_FAIL 0x00000001
     GPS_FAULT_SYSTEM_RAM_CORRUPT0x00000002
     GPS_FAULT_DSP_FAILURE             0x00000004
     GPS_FAULT_ANTENNA_OPEN 0x00000008
     GPS_FAULT_ANTENNA_SHORT           0x00000010
     GPS_FAULT_JAMMING_DETECTED        0x00000020

that the drivers could set.

Before we go off hacking GPSD and libgps too much I thought I'd check if 
we're going in the right direction or overlapping with anyone else.

Does anyone else want to work on this?  Does anyone want to contribute 
to the list of faults/fault codes for other receivers?


Mike



From MAILER-DAEMON Mon Oct 30 23:37:44 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1e9NN2-0003Jm-Ag
	for mharc-gpsd-dev@gnu.org; Mon, 30 Oct 2017 23:37:44 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:60282)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1e9NMz-0003Jf-Qn
	for gpsd-dev@nongnu.org; Mon, 30 Oct 2017 23:37:43 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gem@rellim.com>) id 1e9NMy-0002DN-Ix
	for gpsd-dev@nongnu.org; Mon, 30 Oct 2017 23:37:41 -0400
Received: from rellim.com ([2001:470:e815::19]:44931 helo=spidey.rellim.com)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <gem@rellim.com>) id 1e9NMy-00025C-9q
	for gpsd-dev@nongnu.org; Mon, 30 Oct 2017 23:37:40 -0400
Received: from spidey.rellim.com (rellim.com [IPv6:2001:470:e815:0:0:0:0:19])
	(authenticated bits=0)
	by spidey.rellim.com (8.15.2/8.15.2) with ESMTPSA id v9V3bK5Z016902
	(version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); 
	Mon, 30 Oct 2017 20:37:26 -0700
DKIM-Filter: OpenDKIM Filter v2.10.3 spidey.rellim.com v9V3bK5Z016902
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=rellim.com; s=kong;
	t=1509421046; bh=YECGhik41dKWUE8SjEZYfQBuXTcj+/0qG/uD29k3lOk=;
	h=Date:From:To:Cc:Subject:In-Reply-To:References;
	b=vgNTouZv75vUeX/8ElTug7IxBEvUXnML0ErLddMboBX+nT4OIcRv4rjSqQBCvNqyZ
	6fDS3trZG2AVYDH5vnRUkNQbHvtelmqnzblsQJUMFQ6k/2OlwOqFx8rBgkcVqHYNcu
	b56hyuAfVC34eubB1HE7LrrOK/Vdnt7ez6Scqa1I=
Date: Mon, 30 Oct 2017 20:37:19 -0700
From: "Gary E. Miller" <gem@rellim.com>
To: "Michael J. Tubby B.Sc. MIET" <mike.tubby@thorcom.co.uk>
Cc: gpsd-dev@nongnu.org
Message-ID: <20171030203719.771db2aa@spidey.rellim.com>
In-Reply-To: <c0e3a79e-dd39-c435-3237-200d96f75187@thorcom.co.uk>
References: <c0e3a79e-dd39-c435-3237-200d96f75187@thorcom.co.uk>
Organization: Rellim
X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	boundary="Sig_/jo+KScbkqXzNeJVfl06MJW9";
	protocol="application/pgp-signature"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2
	(spidey.rellim.com [IPv6:2001:470:e815:0:0:0:0:19]);
	Mon, 30 Oct 2017 20:37:26 -0700 (PDT)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 2001:470:e815::19
Subject: Re: [gpsd-dev] GPDS hand hardware fault/alarm reporting
X-BeenThere: gpsd-dev@nongnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: <gpsd-dev.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/gpsd-dev/>
List-Post: <mailto:gpsd-dev@nongnu.org>
List-Help: <mailto:gpsd-dev-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/gpsd-dev>,
	<mailto:gpsd-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Oct 2017 03:37:43 -0000

--Sig_/jo+KScbkqXzNeJVfl06MJW9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Yo Michael!

On Sun, 29 Oct 2017 09:48:15 +0000
"Michael J. Tubby B.Sc. MIET" <mike.tubby@thorcom.co.uk> wrote:

> We have been using GPS receivers in vehicle location systems since
> the early 1990s and the Trimble Advanced Navigation Sensor (TANS) -
> if anyone remembers that - and have worked through multiple
> generations from SVeeSix, ACE to Lassen-iQ and have always used
> Timble's TSIP binary code.

Yeah, a common story.

> We have a new product design and we've switched to Ublox MAX-M8W and

Ublox is getting quite popular.

> While I'm
> impressed with the quality and ease of use of both GPSD and libgps it
> leaves us with a challenge for GPS receiver and antenna fault
> monitoring and reporting.

gpsd understands ublox binary. gpsd would like to add support for more
specialized ublox sentences, and some patches have been tried. past
time for gpsd to nail this down.  If one of our devs had a MAX-M8W the
process would be easier.

> I am only across the Trimble and Ublox GPS/GNSS receivers that we=20
> currently use but an approach for adding generic support these=20
> faults/alarms would be to add a new set of flags as a uint32_t called=20
> 'gps.fault' or similar and define a set of values:
>=20
>  =C2=A0=C2=A0=C2=A0 GPS_FAULT_BATTERY_BACKUP_FAIL 0x00000001
>  =C2=A0=C2=A0=C2=A0 GPS_FAULT_SYSTEM_RAM_CORRUPT0x00000002
>  =C2=A0=C2=A0=C2=A0 GPS_FAULT_DSP_FAILURE=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0x00000004
>  =C2=A0=C2=A0=C2=A0 GPS_FAULT_ANTENNA_OPEN 0x00000008
>  =C2=A0=C2=A0=C2=A0 GPS_FAULT_ANTENNA_SHORT=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0x00000010
>  =C2=A0=C2=A0=C2=A0 GPS_FAULT_JAMMING_DETECTED=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 0x00000020

By far most people use the JSON interface to gpsd.  We'd need to eventually
support both.  There needs to be a mapping from one to the other.

> Before we go off hacking GPSD and libgps too much I thought I'd check
> if we're going in the right direction or overlapping with anyone else.

I think once we get going we can find consensus, nothing set in
stone.

> Does anyone else want to work on this?=C2=A0 Does anyone want to
> contribute to the list of faults/fault codes for other receivers?

This list is low volume, but there has been repeated interest in this.

let's get a discussion going.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem@rellim.com  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can=E2=80=99t measure it, you can=E2=80=99t improve it." - Lord=
 Kelvin

--Sig_/jo+KScbkqXzNeJVfl06MJW9
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENqCjEoytAEAuFCk8DQ7ZSUHRedgFAln37+8ACgkQDQ7ZSUHR
ediU4wgAlR4kJKIMgHoX3l+Y2ifIyST75HJgwrOaatP/K3WyYxPR/mrs8iANblBT
Yh15NL7YjzqWeDoYsXt8Bqb/pjrnSzbZi4DmUT1/E3JbzB/f2F9gUHE6TXBOdYC6
BgYO8GFvOIFANaOgmH/JfWnA+foRXNmqX9OYkasjcgqV8Q8jt1+n3h85bzdd2WK/
FEjR4OzPZkD46mPd9Yy2rpAtY8edEcAxVq1XwnACavhZ7GQ69KId6TBO0Z1Fv7Ia
yocLdC5D5s2uvZNK1CCf27pXEL4R5/BhWHxA8GzOFQnfLsC8vUKy0NG0IqVjMgPF
DdYfGL5LQpSGxxwRpoYNJBz9Mx7Pug==
=bAW3
-----END PGP SIGNATURE-----

--Sig_/jo+KScbkqXzNeJVfl06MJW9--


