Re: ✘Draft GPSD-MIB

[Mike Simpson]

Excuse the top posting. 

Im not sure why you would want to use a network monitoring protocol to relay 
that information. 

Wouldn’t you want fix/no fix, rtk/ no rtk etc on the basis that you could then 
be aware of a problem without being on the box which is what snmp was for? 

Including data that gpsd gives out freely already seems an odd way to skin the 
cat. 

Mike


> On 7 Jul 2022, at 06:40, David Taylor <davidtaylor@writeme.com> wrote:
> 
> On 07/07/2022 01:46, Gary E. Miller wrote:
>> Yo All!
>> 
>> First cut at GPSD-MIB:
>> 
>> https://gitlab.com/gpsd/gpsd/-/blob/master/man/GPSD-MIB
>> 
>> It uses our own, registered OID space:
>> 
>>     iso(1) org(30) dod(6), internet(1) private(4) enterprises(1) gpsd(59054)
>> 
>> Any comments?
>> 
>> I find the program "mbrowse" is a good way to see how that MIB is
>> structured.
>> 
>> No changes in gpssnmp, yet.  gpssnmp is using someone else's address
>> space:
>>     iso(1) org(30) dod(6) internet(1) mgmt(2) mib-2(1) host(25) hrSystem(1)
>> 
>> RGDS
>> GARY
> 
> That's a good start, Gary.
> 
> From my own and user's requests, could I suggest including:
> 
> - average SNR
> - horizontal DOP
> - vertical DOP
> - horizontal EPE
> - vertical EPE
> 
> It could be helpful to see a few sample OIDs in a purely numeric form, as the
> MIB isn't the easiest of things to read.
> 
> Should the standard OID values be included in a header file?  New file, or
> extending an existing one?
> 
> Cheers,
> David
> --
> SatSignal Software - Quality software for you
> Web: https://www.satsignal.eu
> Email: david-taylor@blueyonder.co.uk
> Twitter: @gm8arv
>