<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Dear Tomoji,<div>thanks a lot for your help and very quick reply. I very appreciate your comments.</div><div>Could you please also let me know whether<u> ntrip mount point can have slash in its name</u>? ("/")</div><div>As an example:</div><div>Mountpoint:</div><div>Test/RTK</div><div><br></div><div>Ntrip Browser shows mount points successfully ("Test/RTK"), but after that in ntrip client options part of the mount point name goes to Port field (81/Test). </div><div>And of course after that no mountp error occurs.</div><div><br></div><div>Please check screenshot for your reference.</div><div><br></div><div>Thanks a lot!</div><div><img height="330" width="608" apple-width="yes" apple-height="yes" id="9a4c5e95-5327-4bdf-bfdc-e8400be9268c" src="cid:9E0ED562-28E3-4D4A-BC3C-5485F6AC34D3"><br><div><div>On Mar 19, 2013, at 3:37 PM, "Tomoji TAKASU" <<a href="mailto:ttaka@yk.rim.or.jp">ttaka@yk.rim.or.jp</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Dear oddpost<br><br><blockquote type="cite">When working with Type 18 and Type 19 messages, should Input<br>Stream be set as (2) Base Station or (3) Correction?<br></blockquote><br>Please set (2).<br><br><blockquote type="cite">Options for positioning mode should be set as "Kinematic"?<br></blockquote><br>If moving, set "Kinematic".<br>If stationary, set either "Kinematic" or "Static".<br><br>Tomoji TAKASU<br><br>--------------------------------------------------<br>From: "oddpost" <<a href="mailto:oddpost@ya.ru">oddpost@ya.ru</a>><br>Sent: Tuesday, March 19, 2013 4:22 PM<br>To: "Open Source GPS-related discussion and support" <<a href="mailto:foss-gps@lists.osgeo.org">foss-gps@lists.osgeo.org</a>><br>Subject: Re: [FOSS-GPS] impressed<br><br><blockquote type="cite">Hello,<br>I am trying to figure out rtknavi settings. I am using openmoko freerunner and would like to get relatively precise positioning (using RTK).<br>I have access to ntrip, providing Type 1 (differential GPS corrections), Type 3 (BS parameters), Type 18 (uncorrected carrier phase measurements),<br>Type 19 (virtual distance uncorrected observations).<br><br>When working with Type 18 and Type 19 messages, should Input Stream be set as (2) Base Station or (3) Correction?<br>Options for positioning mode should be set as "Kinematic"?<br><br>The idea is to get the following simple architecture:<br>freerunner --> rtknavi <---- ntrip<br><br>Thanks a lot for your help<br>On Mar 16, 2013, at 11:46 PM, Artyom G <<a href="mailto:gnsssdr@gmail.com">gnsssdr@gmail.com</a>> wrote:<br><br><blockquote type="cite">Dear all,<br><br>I also want to thank developers of RTKlib.<br>During last month one the students under my control tested nvs08c-csm with<br>RTKlib. At first we tried to get our coordinates relative to RTCM base<br>station. During 3 days the difference in fix-position coordinates didn't<br>exceed 1cm (on each coordinate). Distance between RTCM station and our<br>antenna was about 3 km. Then we determined coordinates between RTCM station<br>and second reciever. And at the end we determined coordinates between two<br>nvs08c-csm receivers (baseline about 8m).<br><br>We also checked manually baseline distance between two nvs08c-csm receivers<br>by subtracting coordinates of the first nvs08c-csm receiver (that were got<br>relative to RTCM station) from the coordinates of the second nvc08c-csm<br>receiver (that were also got relative to RTCM station). The result was the<br>same as RTKlib outputed.<br><br>I also appreciated strongly the posibility to stream data from receiver<br>through "strsvr". It was very comfortable to work with receivers output in<br>parallel with the student.<br><br>Thanks a lot for RTKlib.<br><br>On Sat, Mar 16, 2013 at 1:40 PM, Michele Bavaro <<a href="mailto:mic.bavaro@yahoo.co.uk">mic.bavaro@yahoo.co.uk</a>>wrote:<br><br><blockquote type="cite">Great, thank you!<br><br>Too many times we hear the opposite.<br>I am glad that - for once - someone has been willing to share his good<br>results with RTKLIB combined with low cost receivers.<br>To cool down you enthusiasm a bit, I anticipate that you should not expect<br>much difference between a LEA-4T and a NV08C-CSM. Carrier phase noise is<br>similar and despite tracking Glonass, that is still hardly usable by RTKLIB<br>since it is affected by the well-known biases any Glonass receiver RF<br>receive path is subject to. And RTKLIB "auto-calibration" feature is still<br>not implemented.<br><br>If I am allowed, I am under the impression that Tomoji's development<br>road-map is adding more and more features to RTKLIB so that now resembles<br>very much a professional product rather than an open-source *one-man*effort. Surely having multiple frequencies, multiple constellations, super<br>standalone post-processing (PPP), and beautifully coloured GUIs is great<br>and we are always grateful to him for that. But I wonder how many users<br>desire to have a robust and very lean single frequency GPS RTK algortihm.<br>One that can run headless on Android perhaps, or even on a STM32F4 bare<br>metal. One that can fill the gap with the most common quirks of low-cost<br>receivers (e.g. random phase slips) and use some sort of pre-processing<br>RAIM to indentify and exclude outliers. One that can be integrated in<br>robotic automatic guidance projects.<br><br>Back to receivers, the only real difference between NV08C-CSM and LEA-4T<br>is that the latter is gone out of production several years ago, and uBlox<br>has not replaced it with an equally performing module. 5T and 6T in fact<br>can only measure at 10Hz under certain conditions and they are not<br>certified to do that anyway.<br>So if you need a module to build a commercial product you only have three<br>choices right now: NVS NV08C-CSM, ublox 6T/P, and Skytraq S1315F-RAW.<br>Of the three, only the first has to my knowledge a clear development and<br>upgrade path. There are rumors that the new revision of NV08C -to come out<br>later this year- will fully support Galileo and, as most of us know,<br>Galileo Signal In Space specifications guarantee interoperability with GPS<br>by design. Thus, as soon as there will be a sensible number of Galileo<br>birds in the sky, dual constellation low-cost RTK will become easily<br>useable by all of us. Not to mention dual frequency of course, as L5 and<br>E5a bands overlap.<br><br>Congratulations again and keep it up,<br>Michele<br><br><br><br>On 16/03/2013 09:04, napoleon wrote:<br><br>Hello,<br>My setup is:<br>Rover:40db tallysman antenna, lea-4t receiver<br>Base: leica 1202gg antenna ntrip caster connection,rtcm 3 data.<br>baseline 6.68 m<br>base -kinimatic solution<br>I searched for the lea-4t configuration, i set it up, i pressed ''start''and<br>i had first fix after 1.5 minute and stable fix after 7 minutes....(less<br>than 2.5cm)-MY FIRST TRY<br>Looks like a joke.<br>I am totally impressed.<br>I am planning a new config with tallysman gnss antenna and nvs-08 and i am<br>afraid to imagine the result.<br>I will also test vrs and max solutions from the base network (i guess i can<br>feed max solution through rtcm 3 to rtklib)<br>Anyway i have to say again that i am impressed and to thank you ttakasu and<br>team.<br><br><br><br>--<br>View this message in context: <a href="http://open-source-gps-related-discussion-and-support.1099874.n2.nabble.com/impressed-tp7572660.html">http://open-source-gps-related-discussion-and-support.1099874.n2.nabble.com/impressed-tp7572660.html</a><br>Sent from the Open Source GPS-related discussion and support mailing list archive at <a href="http://Nabble.com">Nabble.com</a>.<br>_______________________________________________<br>This message is sent to you from <a href="mailto:FOSS-GPS@lists.osgeo.org">FOSS-GPS@lists.osgeo.org</a> mailing list.<br>Visit <a href="http://lists.osgeo.org/mailman/listinfo/foss-gps">http://lists.osgeo.org/mailman/listinfo/foss-gps</a> to manage your subscription<br>For more information, check <a href="http://wiki.osgeo.org/wiki/FOSS-GPS">http://wiki.osgeo.org/wiki/FOSS-GPS</a><br><br><br><br>_______________________________________________<br>This message is sent to you from <a href="mailto:FOSS-GPS@lists.osgeo.org">FOSS-GPS@lists.osgeo.org</a> mailing list.<br>Visit <a href="http://lists.osgeo.org/mailman/listinfo/foss-gps">http://lists.osgeo.org/mailman/listinfo/foss-gps</a> to manage your<br>subscription<br>For more information, check <a href="http://wiki.osgeo.org/wiki/FOSS-GPS">http://wiki.osgeo.org/wiki/FOSS-GPS</a><br><br><br></blockquote>_______________________________________________<br>This message is sent to you from <a href="mailto:FOSS-GPS@lists.osgeo.org">FOSS-GPS@lists.osgeo.org</a> mailing list.<br>Visit <a href="http://lists.osgeo.org/mailman/listinfo/foss-gps">http://lists.osgeo.org/mailman/listinfo/foss-gps</a> to manage your subscription<br>For more information, check <a href="http://wiki.osgeo.org/wiki/FOSS-GPS">http://wiki.osgeo.org/wiki/FOSS-GPS</a><br></blockquote><br>_______________________________________________<br>This message is sent to you from <a href="mailto:FOSS-GPS@lists.osgeo.org">FOSS-GPS@lists.osgeo.org</a> mailing list.<br>Visit <a href="http://lists.osgeo.org/mailman/listinfo/foss-gps">http://lists.osgeo.org/mailman/listinfo/foss-gps</a> to manage your subscription<br>For more information, check <a href="http://wiki.osgeo.org/wiki/FOSS-GPS">http://wiki.osgeo.org/wiki/FOSS-GPS</a> <br></blockquote><br>_______________________________________________<br>This message is sent to you from <a href="mailto:FOSS-GPS@lists.osgeo.org">FOSS-GPS@lists.osgeo.org</a> mailing list.<br>Visit <a href="http://lists.osgeo.org/mailman/listinfo/foss-gps">http://lists.osgeo.org/mailman/listinfo/foss-gps</a> to manage your subscription<br>For more information, check <a href="http://wiki.osgeo.org/wiki/FOSS-GPS">http://wiki.osgeo.org/wiki/FOSS-GPS</a><br></blockquote></div><br></div></body></html>