<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
Fred:<br>
I do not see why it would not work.<br>
The line<br>
inpstr3-path
=anonymous:passwd@cddis.gsfc.nasa.gov/gps/products/%W/igu%W%D_%hb.sp3.Z::T=-14400,21600,7200,600<br>
seems correct to me. <br>
<br>
I need to review how the SP3 formats differs to be sure that RTK can
consume it, we normally use Bcast orbits here, somewhere in the back
of my mind was a mental note that SP3 was not supported in all the
tools and all the flows. If yoy are still seeing it work then now
work in odd conditions, track down the temp directory and look very
close at any other file it might be keeping a prior set of ephemeris
in. <br>
<br>
<br>
Regards<br>
David Kelley <br>
<br>
<div class="moz-cite-prefix">On 11/2/2015 1:00 AM, Fred Labrosse
wrote:<br>
</div>
<blockquote cite="mid:1693622.PoGIyhHMfs@pcp2ffl" type="cite">
<pre wrap="">Hi David,
Thank you for this very useful answer. See below.
On Friday 30 October 2015 12:05:23 David Kelley wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">If I make it display the satellites, I most of the time don't get any,
sometimes 1, sometimes a full set.
</pre>
</blockquote>
<pre wrap="">Two questions to consider. This makes me wonder if you are reliability
getting ephemeris data. Is that what you mean when you say you can not
display the satellite? In the configuration you have created, can you
describe what is the path over which the ephemeris messages get to the
navigation filter?
</pre>
</blockquote>
<pre wrap="">
I have no idea. The only thing I can see that refers to ephemeris is set
to broadcast. I attach my config, in case it helps.
</pre>
<blockquote type="cite">
<pre wrap="">
[Aside: It took me quite a bit of trial and error and the help of other
folks on this list to find out that RTKLIB stores recent past ephemeris
data in the .ini files. Sometime a config worked, sometimes it did
not. Turned out the data from a recent past run was still present. I
learned to edit the end of the ini file to remove this when I wanted to
test out cold starting issues. Perhaps you are seeing something of the
same sort.
PS these lines look like:
eph_01=G02,38,38,0,0,14460624...0,
eph_04=G05,96,96,0,0,14460......
eph_11=G12,63,63,0,0,1446.... etc. ]
</pre>
</blockquote>
<pre wrap="">
This is interesting. I was wondering about that because it seems that the
receivers I use do not store that (NV08C). What would be the eequivalent
for rtkrcv? I have looked but couldn't find an equivalent.
Cheers,
Fred
</pre>
<blockquote type="cite">
<pre wrap="">
On 10/30/2015 10:19 AM, Fred Labrosse wrote:
</pre>
<blockquote type="cite">
<pre wrap="">All,
I have been trying to use the unix applications, after getting good
results with the Windows ones.
I now have a (unix) server that serves data from one receiver for now
and if I connect rtknavi (windows) to it in PPP-static I get a fix
quite quickly. If at the same time I connect rtkrcv to the same
server, the result is not so good. If I make it display the
observations (observ 1), I do get data that is similar to what I see
in rtknavi. If I make it display the satellites, I most of the time
don't get any, sometimes 1, sometimes a full set. This seems to be
random between stop/starts. Waiting does not seem to help. If I
manage to get a fix in rtkrcv, stop and restart it, usually I don't
get a fix. However, if I do the same in rtknavi, I get a fix almost
immediately.
What have I missed?
Cheers,
Fred
_______________________________________________
This message is sent to you from <a class="moz-txt-link-abbreviated" href="mailto:FOSS-GPS@lists.osgeo.org">FOSS-GPS@lists.osgeo.org</a> mailing list.
Visit <a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/foss-gps">http://lists.osgeo.org/mailman/listinfo/foss-gps</a> to manage your
subscription For more information, check
<a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/FOSS-GPS">http://wiki.osgeo.org/wiki/FOSS-GPS</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
This message is sent to you from <a class="moz-txt-link-abbreviated" href="mailto:FOSS-GPS@lists.osgeo.org">FOSS-GPS@lists.osgeo.org</a> mailing list.
Visit <a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/foss-gps">http://lists.osgeo.org/mailman/listinfo/foss-gps</a> to manage your
subscription For more information, check
<a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/FOSS-GPS">http://wiki.osgeo.org/wiki/FOSS-GPS</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
This message is sent to you from <a class="moz-txt-link-abbreviated" href="mailto:FOSS-GPS@lists.osgeo.org">FOSS-GPS@lists.osgeo.org</a> mailing list.
Visit <a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/foss-gps">http://lists.osgeo.org/mailman/listinfo/foss-gps</a> to manage your subscription
For more information, check <a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/FOSS-GPS">http://wiki.osgeo.org/wiki/FOSS-GPS</a></pre>
</blockquote>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Regards,
David Kelley</pre>
</body>
</html>