Rtklibexplorer Github

3 views

Skip to first unread message

Piperion Giles

unread,

Aug 3, 2024, 4:46:48 PM8/3/24

to micasampsu

All the previous code changes are also there as well as a couple I have not yet posted about. The receiver data I have been using for these posts is also there in the rtklib/data/demo1 folder. The solution file updates for VS2010 c++ are in the rtklib/app/rnx2rtkp/msc folder and the modified executable is in the rtklib/bin folder.

Anyway I am still using my old M8Ns with the 2.01 firmware so I can still used the TREK-MEAS. My question is how can I send correction data back to the M8N from rtklib based on the solution generated. Not sure if this is even possible.

Just a quick update. I manually converted the makefile to a .sln file using the rnx2rtkp sln file as the base. So I was able to get it to open and build. Yea. But got a bunch of errors with the included .h files, such as all the net stuff, termios.h..

rtkexplorer
Believe it or not got it to compile with termiWin and pthreads but having a problem with it getting hung up sending data to the console. Keeps wanting a login password? Took a small break from it. But it I ever get it to be fully functional I will definitely put in a pull request.

Hi. Well I got it compiled and it sort of runs. By that I mean it seems to be connecting and reading the GPS and creating and writing to the appropriate files. But not sure about ntrip connection. The problem I have is that I am not sure if its me just not knowing how it should work or something with the program. I tried to send an email to rtklibexplorer.gmail with the attachment but it keeps giving me undeliverable. Was wondering if you had some time to look at the config file to see if its me or something I have to change in the cmd file (I am using the m8n_1hz.cmd file from your version). I also use this to start it rtkrcv -t 5 -r 2 -s -o rtk.conf.

What saved me time was I found someone on DIYDRONES that actually had it completed for windows which was where I was working to but without those changes would be longer: -rover-and-base-configuration-web-interface
Mike

Hi all. Ok got a pull request in for what I have so far. Unfortunately -d option will not work because there is no native console like \dev for windows but you can use the -p option to set up a tcp connection to act as the console. Works great. -s option is connected to /dev since it asks to overwrite files if they already exist. So for now I disabled it for windows but you can start the server when you use the -p option. If anyone has any ideas for code changes have a look at the pull request.

Also, I have added a fair bit of commenting to the core routines in rtkpos.c and lambda.c where most of the solution computations are done. You can find my comments in the demo1 branch of my Github repository.

I would be very interested in hearing about other similar work, so please leave a comment or send me an email at rtklibe...@gmail.com if you are working in this area or if you have anything to add to any of the posts. My goal is also to document as completely as possible the work I have done, so if there is something I have skipped over that would be of interest to others, please let me know, and I will try to add a post.

All of the code changes and configuration files described in my posts are available in my Github repository. The most recent executables are available here and most of the data sets I reference in the blog are here.

I am happy to take a quick look at raw data at no charge if you are having trouble getting decent solutions or do my best to answer questions you have about RTKLIB or any of the material covered here. I interact with quite a few of my readers and enjoy being able to help out when I can.

If you are looking for help with a project involving a larger commitment of time I am also available on a consulting basis. My rates are reasonable as my primary goal is to find interesting projects to work on and continue to improve my understanding of precision GPS and RTKLIB. I can help with data analysis, configuration optimization, code customization, feature enhancements, tool development, training, or any other RTKLIB or low cost RTK related task and normally work on an hourly basis with a minimum of 10 hours.

Thanks. The problem as we later discovered was that PPPstatic was not really enabled in RTKlib version 2.4.3. It works pretty well in version 2.4.2. The Version 2.4.3 is unstable. Thanks for explaining that PPPFixed does output a *.pos solution except residuals (.stat). I will examine your demo codes.

Thank you very much for the nice work on GNSS!
I am a graduate student working on GNSS, and I am interested in using the data for my research (e.g., publication) that you kindly shared on this website. Just wondering if there are any restrictions or requirements on the use of your data?

Would you please recheck the dropbox link. It seems to be broken.
It is appreciated if you could re-upload the document as I am working on real-time positioning with RTKlib and currently struggling to get it work.
Thanks in advance

I am new to RTKLIB and facing some issue while using it. I am using ublox 7P modules for base station and for rover. I have configured modules only for RAW data & SFRBX data, all NMEA messages are disabled (assuming we dont need them for RTKLIB). Please refer the screen shots for RTKNAVI settings.
The satellite visibility is good but still I am not getting accurate position. Please let me know if I am missing any settings or how can I improve the accuracy and stability.

Thanks a lot. I have ordered two cgs kits and lets see how it fares. BTW would you mind being in touch. I can share my results with you perhaps for the broader understanding. If you would like just drom me a hello mail at ashish_2083(@)yahoo(dot)com

Just one last opinion from you. Ublox has two variant M8N that you used and M8T. Both have the capability to throw raw gps data. Then what is the main difference between them in terms of Kinematics. Is it so that M8T is more accurate due to better Radio/Crystal ?

Hi Ashish. Since M8N does not officially support raw GPS data, there is nothing available from Ublox describing the differences between M8N and M8T. I did just come across some comments on the Emlib forum from Tomoji Takasu with his observations on the differences between the two. The biggest difference appears to be that GLONASS ambiguity resolution works on M8T but not on M8N.

I think what you did as this estimate relative position of one ublox relative to cors base and same for other ublox. And then you subtracted
Both the estimated position to get the circle. And you got perfect circle !

I guess, this is a bit different from the demo 1. I am yet to receive eval kits from ublox. Before that I wanted to have an good opinion if this setup will work or not not worried about accuracy thought at the moment.

Hi Ashsih. I did use CORS base data in one of my posts just to confirm I could get good results with the more traditional base/rover configuration. In that case I am using one of my recievers as rover and a CORS station as base. In all my other posts and analysis, I am using one of the moving receivers as base and the other as rover and not using a CORS station at all.

Very quick reply ! Thanks . However, my application is little different. What you have is a base station some where far away from the two rovers. However, I wish to make one of the neo block as base station and other neo block as rover keeping the distance between then at 30 to 50 cm. Using correction from one neo to to differential with other neo with out using any other central base as you have done in you demo. Do you this setup will yeild ?

What I have is a rover and base separated by 30-40 odd cm and I wish to figure out the direction this setup is pointing to. Like a compass. Do you think this configuration might work ? Or this too short of a baseline to work with.

Hi Ashish. Take a look at my demo1 results. The distance between the two receivers is about 35 cm (both are attached to the rover). I get very accurate results that could be used to generate quite precise compass headings.

In my last post I described building the RTKLIB code in Windows. In this post I will describe building the code in Linux. Unlike for Windows, pre-built executables are not available for either the demo5 or the official 2.4.3 versions of RTKLIB, so building your own code is more of a necessity on this platform.

I have built Linux versions of RTKLIB on both a PC running Ubuntu and on a Raspberry Pi and will describe these experiences. My description may be somewhat specific to these platforms but I believe the process should be very similar on any other Linux system.

The original RTKLIB did not support Linux for the GUI apps but a few years ago Jens Reimann created a version using Qt that supports Linux as well. Those changes are now in both the demo5 and the 2.4.3 versions of RTKLIB and I will describe building these on the Ubuntu platform below.

The first line pulls the source code from the Github repository, the second line gets you into the Linux build folder for RTKRCV, and the third line builds the code. The default compiler warning threshold is pickier than for Windows, so you will see some warning messages but you can ignore these. You can build the STR2STR, CONVBIN, RNX2RTKP, and POS2KML in the same way by changing the app name in the second line.

If you do get any build errors it is most likely going to be because you are missing one of the build tools. However I have found that if you are using one of the standard releases of Debian Linux for the Pi, this should not be a problem.

Before building either the CUIs or the GUIs you will most likely need to update your build tools. I used the following commands to resolve various build errors I ran into when I started with a fresh installation of Ubuntu 20.04

The first line pulls the source code from Github and is not necessary if you have already done this to build the CUIs. The second line gets you to the app folder in the RTKLIB code where the third line creates a makefile for the Qt apps. The fourth line gets you back to the top level folder where the fifth line creates the makefile for the full build process. The last line builds all the CUI and GUI apps.