The page is not incredibly verbose so I will add some verbosity here. First off download and decompress the data from the link provided on the page. Inside the folder you will find the raw data file (.dat) along with a configuration file (.conf) USRP recording output log (.log) and output from their gnss-sdr run (.txt), Google Earth output (.kml) and NMEA messages (.nmea)
Unfortunately the provided configuration file doesn't work with the current gnss-sdr. However the default configuration file provided with gnss-sdr works just fine. So do the following
- Copy gnss-sdr.conf from the installation location (typically /usr/local/share/gnss-sdr/conf/gnss-sdr.conf) to the directory containing the raw data file you downloaded
- Update the line SignalSource.filename to the full path filename of the data file
- Set GNSS-SDR.SUPL_read_gps_assistance_xml=false
Once you made those two tweaks you can execute the example by running
gnss-sdr --config_file=/path/to/my/gnss-sdr.conf
You should see similar but not identical output to the output provided with the data file. Once the run completes you should have a number of new files. The KML and NMEA files were already described, but you will also see some files named GSDR350w40.15N and GSDR350w40.15O. The file ending in "N" is the navigation solution and the file ending in "O" is the observables. Basically, the navigation solution is your 'fix' and the observables are what information you received from the satellite to generate that fix. Lastly, the gps_ephemeris.xml is an ephemeris which is a description of the satellites' orbit in space.
Im getting thjis when I try to callibrate it:
ReplyDeleteSignalSource.Osmosdr_Signal_Source: Undefined implementation for block
You need to run 'cmake' with the following parameter:
ReplyDeletecmake -DENABLE_OSMOSDR=ON ../
prior to building
Cool, I made it work, on a Kali Linux vbox. Thanks.
ReplyDeleteWhat if i want try to create my record file? and then test gnss?
ReplyDeleteWhat should I do if I want to use my own recorded file?
ReplyDelete