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