At 01:53 PM 12/30/2010, you wrote (Hal Murray):
>If the NMEA signal says no-good, gpsd should ignore the PPS pulses.

Yes, that makes sense. I solved the problem for my system by 
modifying the gpsd code to stop delivering PPS during the interval of 
no fix. The last version of gpsd I built (2.96~dev) continues to send 
PPS during a no fix period.

I am not a maintainer of gpsd nor ntpd and I assume that the mailing 
lists are the best way to alert the maintainers of a problem. I 
started with the gpsd list because the Placer 450 was not properly 
reporting loss of fix.

Do you have contacts at gpsd with which you work out problems? If 
not, I would be glad to provide the email addresses of the people who 
were helping me. I can provide info about the problem, my solution, 
and a test bed for a fix.

Bruce

Bruce Dale <bdale@stny.rr.com> wrote:
>
> At 01:53 PM 12/30/2010, you wrote (Hal Murray):
>>If the NMEA signal says no-good, gpsd should ignore the PPS pulses.
>
> Yes, that makes sense. I solved the problem for my system by 
> modifying the gpsd code to stop delivering PPS during the interval of 
> no fix. The last version of gpsd I built (2.96~dev) continues to send 
> PPS during a no fix period.

It probably is the result of the problem with your GPS's NMEA output,
as the PPS code is checking the validity of the fix.  Maybe that
variable is not properly set in your case.

In article <201101011238.p01Ccalc009203@heartache.daihls.com>,
 Bruce Dale <bdale@stny.rr.com> writes:
....

>Do you have contacts at gpsd with which you work out problems? If 
>not, I would be glad to provide the email addresses of the people who 
>were helping me. I can provide info about the problem, my solution, 
>and a test bed for a fix.

There haven't been enough interesting problems to worry about it.

The SHM "api" is pretty simple.

-- 
These are my opinions, not necessarily my employer's.  I hate spam.