[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gpsd-dev
Subject:    [Gpsd-dev] Correction to my description of how Ntrip works
From:       Eric Raymond <esr () snark ! thyrsus ! com>
Date:       2011-02-28 0:37:01
Message-ID: 20110228003701.5B54E20C245 () snark ! thyrsus ! com
[Download RAW message or body]

In previous mail, I wrote:
>The [RTCM2] bitstream recognizer does not update the session buffer,

This is incorrect.  It *does* update the session [packet] buffer.
When an RTCM2 packet is recognized, the session output packet buffer
will contain the portion of the raw input bitstream that decoded to
the RTCM2 packet (this is gpsd passes to DGPS-capable GPSes).  The
special isgps buffer will contain the packet payload after the magic
bit extractions and inversions necessary to pull it out of the
bitstream.

I should also have emphasized that each device has separate packet
and isgps buffers, so there is no way data from multiple devices can
get intermingled.

Confirmation from you (Andre) that Ntrip is working in head is all
I'm waiting on before the pre-release freeze.  If there are remaining
problems, let's fix them ASAP.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

In every country and in every age, the priest has been hostile to
liberty. He is always in alliance with the despot, abetting his abuses
in return for protection to his own.	-- Thomas Jefferson, 1814
_______________________________________________
Gpsd-dev mailing list
Gpsd-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/gpsd-dev
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic