Demo5 b26a code release

I’ve just released a new version of the demo5 code.  It has the time tag adjustments for RTCM conversion described in the last post as well as a few new features that I will describe in future posts.

You can download the binaries from here.  There is also a short description of the new features on that page.  The source code is available on my  Github page.

 

Advertisements

11 thoughts on “Demo5 b26a code release”

  1. Hi,

    Do not know if anyone is facing the same problem but there seems to be a problem with 2.4.3 b26 in rtklib upstream.
    I usually work with Andalusia (Spain) government RINEX CORS files. They are 2.11 and works fine with 2.4.2 p12. However if I use rtklib 2.4.3 b26 they does not work and says “no obs”.

    I have created an issue and attached test files.
    https://github.com/tomojitakasu/RTKLIB/issues/289

    Regards from Spain!

    Like

    1. Hi Sravan. The rtkrcv file has a comment at the top that the “current version does not support win32 without pthread library”. There does appear to be versions of pthread that have been ported over to Windows so it may be possible to build using one of these libraries but I have not tried to do it.

      Like

  2. Posted results of real-time Emlid Reach tests on their Forum under Reach beta v2.2.2 and
    Using your Demo5 b26a post processing. Did not get into Kinematics much. Mostly Static..
    Do not think it can get much better……
    Thanks to all….

    Like

  3. I could help, as I can realize the double GPS differentiation in RTKLIB

    2017-02-10 14:11 GMT-05:00 FrankResurection k16 :

    > ​ > Rinex.rar > > ​ > Hello, good afternoon, you could help me with post processing in GPS > differential of the following files in RTKPOST. Obvious correction is not > obtained. > > 2017-02-06 20:19 GMT-05:00 rtklibexplorer : > >> rtklibexplorer posted: “I’ve just released a new version of the demo5 >> code. It has the time tag adjustments for RTCM conversion described in the >> last post as well as a few new features that I will describe in future >> posts. You can download the binaries from here. There is als” >>

    Like

  4. ​ Rinex.rar ​ Hello, good afternoon, you could help me with post processing in GPS differential of the following files in RTKPOST. Obvious correction is not obtained.

    2017-02-06 20:19 GMT-05:00 rtklibexplorer :

    > rtklibexplorer posted: “I’ve just released a new version of the demo5 > code. It has the time tag adjustments for RTCM conversion described in the > last post as well as a few new features that I will describe in future > posts. You can download the binaries from here. There is als” >

    Like

  5. Hi, rtklibexplorer! I am glad to emergence of the new version and modernization of the static-start mode. But you could is more detailed to explain as this mode works now? I have noticed that after 5 minutes of lack of a signal from rover and after his emergence the Kinematic mode changes on Static Start. But if rover before and after remains on one place, then the mode changes not always. Rover has to be surely moved to other place?

    Like

    1. Hi Max. Your description of the new static-start is correct. It should always switch back to static-start when rover activity resumes after being inactive for at least five minutes. That is true regardless of rover location. Does it have a fix when it appears not to switch? If so, my guess is that in the case when the rover did not move, the solution is re-converging very quickly and is switching to static-start and then back to kinematic so quickly you don’t see it. If you have data that shows that is not what is happening, please send me a copy and I will take a look.

      Like

      1. In my yesterday’s experiment, apparently, and was (as you write) because Fix appeared right after rover activity resumes, thanks for an explanation.
        But today in the 1st experiment of RTKNAVI has been turned into tray and after resume rover of the return switching to Static-Start hasn’t occurred (solution was floating several minutes), but in the 2nd experiment I didn’t turn RTKNAVI in a tray and switching has worked. In both experiments time of inactivity of rover – more than 20 minutes, the receiver has been located in different places. I haven’t understood yet why so occurs, but I will experiment still.
        If I sign up raw (.ubx) data in RTKNAVI of it will be enough or switching of the modes doesn’t remain in raw data?

        Like

        1. Hi Max. Whether you are transmitting the data in a raw format or RTCM format shouldn’t matter, the code is just using the time since the last rover measurement to decide on switching. If you’ve got some data that demonstrates the problem you are seeing, I’d be interested in taking a look.

          Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s