search

kaichen686 / GINav

GNSS and GNSS/INS integration algorithms
BSD 2-Clause "Simplified" License
206 stars 79 forks source link

Problems with GINav PPK/LC mode @kaichen686 #2

Open zcsti30 opened 3 years ago

zcsti30 commented 3 years ago

Dear Kai Chen!

I am a student from Hungary and I use GINav for studying (for my bachelor thesis). I have some measurement files (GNSS rover, base and IMU) and I try to postprocess the data but I have some problems.

The PPK solution worked well but when I try sensor fusion postprocessing it fails (both PPK/LC and PPK/TC). When I start the program, it reads the input files successfully but then nothing happens. It says "processing" and the progress bar proceeds but the figure remains empty and the result file too. I attach the screenshots.

Processing Finished

I also noticed when using your sample files the program writes: "Info: INS initial alignment OK" But this line is missing when I run GINav with my files. I think the format of my IMU file is fine and I tried many variations of settings in the config file. But I still do not know what the problem is.

I attach my data with a drive link. https://drive.google.com/file/d/1i9AAj2amrw6A43-H01nh1yOpnFStreFO/view It contains the files I use with the GINav, the PPK solution (and the raw data files which I converted to .obs and .nav). I would highly appreciate your help.

Yours faithfully, Zoltan Csoti

zcsti30 commented 3 years ago

I also noticed something when I tested the tokyo sample files with PPK/TC. The interval of the solutions in the result file was 1 second with any config settings. Is there a way to get solutions with higher frequency?

na851998 commented 2 years ago

Did you find what the problem is?

na851998 commented 2 years ago

I found the solution to your problem: 1) In the configuration file, exclude GLONASS navsys (R) to avoid jumping in searchgeph.m function 2) Comment line 54 in giprocessor (||obsr(1).time.sec~=0) 3) Comment line 128, 195 to avoid undefined variables error