<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>I like your idea of using the 1PPS output to sync an external event logger. Please keep us posted if you make progress in the stop-and-go hardware part, perhaps better at the NavSpark forum:</div><div><<a href="http://www.navspark.com.tw/forum/event-marker-for-post-processed-stop-and-go-rtk?context=category-NS-RAW">http://www.navspark.com.tw/forum/event-marker-for-post-processed-stop-and-go-rtk?context=category-NS-RAW</a>></div><div>I might be able to help with the software part if necessary, especially the matrix/vector weighted averaging code.<br></div><div>All the best,</div><div>-F.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Date: Mon, 20 Apr 2015 17:14:28 -0700<br>
From: julio menezes <<a href="mailto:yjmenezes@yahoo.com.br">yjmenezes@yahoo.com.br</a>><br>
To: Open Source GPS-related discussion and support<br>
<<a href="mailto:foss-gps@lists.osgeo.org">foss-gps@lists.osgeo.org</a>><br>
Subject: Re: [FOSS-GPS] rtklib kinematic Stop Go post-processing with<br>
rnx2rtkp<br>
Message-ID:<br>
<<a href="mailto:1429575268.54261.YahooMailBasic@web140303.mail.bf1.yahoo.com">1429575268.54261.YahooMailBasic@web140303.mail.bf1.yahoo.com</a>><br>
Content-Type: text/plain; charset=iso-8859-1<br>
<br>
Dear Dr. Felipe Nievinski,<br>
<br>
<br>
<<<<<br>
--------------------------------------------<br>
Em seg, 20/4/15, Felipe G. Nievinski <<a href="mailto:fgnievinski@gmail.com">fgnievinski@gmail.com</a>> escreveu:<br>
<br>
Assunto: [FOSS-GPS] rtklib kinematic Stop Go post-processing with rnx2rtkp<br>
Para: <a href="mailto:foss-gps@lists.osgeo.org">foss-gps@lists.osgeo.org</a><br>
Data: Segunda-feira, 20 de Abril de 2015, 1:58<br>
<br>
Let me resurrect<br>
this old thread.<br>
The processing could be done in kinematic mode<br>
(either forward-only or forward+backward combined).? That<br>
way, initialization tricks (antenna-swap, fixed-length bar)<br>
as well as ambiguity reinitialization (cycle slips) are less<br>
of an issue.?<br>
Then stop-and-go could be implemented forming<br>
weighted averages of the kinematic position coordinates and<br>
precision (3-by-1 vectors and 3-by-3 matrices).<br>
It'd require a time table of occupation<br>
start and end times (and marker name), which could be<br>
obtained simply grepping the rover RINEX observation file to<br>
extract event flags.<br>
If I were to implement this, I'd be easier<br>
for me to do it Octave rather than built into RTKLIB's C<br>
code.<br>
-Felipe.<br>
PS: the non-integer epoch seconds can be handled<br>
by teqc, see, e.g.:<<a href="http://postal.unavco.org/pipermail/teqc/2012/001310.html" target="_blank">http://postal.unavco.org/pipermail/teqc/2012/001310.html</a>><br>
>>>>><br>
<br>
Thank you for your explanation.<br>
<br>
I agree, instead build inside rtklib C code, i am using GNU utils ( grep, awk,sed, octave,... ).<br>
<br>
I plan to use 1PPS signal to sync trigger events. ( closed loop ) and will write my own occupation time table logger (gps time sync and epoch count... ).<br>
<br>
best regards,<br>
<br>
julio menezes<br>
<br></blockquote></div></div></div>