Re: Change from 3.23 to 3.24 - program doesn't work?

[David Taylor]

On 26/06/2022 05:21, Gary E. Miller wrote:
> > I'm open to suggestions for official OIDs.  At the moment I have:
>
> >     #define OID_VISIBLE ".1.3.6.1.2.1.25.1.31"
> [...]
> Those do not use our PEN, so not valid.
>
> > for a single GPS device attached to a system.
> And soee will want lat/lon/altHAE,/altMSL, etc.
>
> RGDS
> GARY

Thanks, Gary.  I'm not familiar with PEN so I'm happy with your suggestions as
to how the new OIDs should be numbered.  I'd suggest keeping the same trailing
numbers (31..38) for the ones I've defined, and perhaps a preceding "1", "2"
etc. for multiple GPS devices in a system (does anyone have that?).

   #define OID_VISIBLE ".1.3.6.1.2.1.25.1.31"
   #define OID_USED ".1.3.6.1.2.1.25.1.32"
   #define OID_SNR_AVG ".1.3.6.1.2.1.25.1.33"
   #define OID_PDOP ".1.3.6.1.2.1.25.1.34"
   #define OID_HDOP ".1.3.6.1.2.1.25.1.35"
   #define OID_VDOP ".1.3.6.1.2.1.25.1.36"
   #define OID_EPH ".1.3.6.1.2.1.25.1.37"
   #define OID_EPV ".1.3.6.1.2.1.25.1.38"

This would leave 1..30 available for other GPSD uses, plus anything higher, of
course.  Yes, the basics lat/lon/.. which you list

How to progress this, and how important is it?

Cheers,
David
--
SatSignal Software - Quality software for you
Web: https://www.satsignal.eu
Email: david-taylor@blueyonder.co.uk
Twitter: @gm8arv