jt3232
jt3232
> I'll be honest, I don't exactly know what `Channels.in_acquisition=1` does, but I had a similar issue with tracking and I commented it out and got much better response. YMMV...
Setting signalsource_enable_throttle=true has helped. Running 12 channels feels pretty stable. I do have an issue of if it loses position but then restarts tracking satellites, it cannot get its position....
> Thanks for the reply. I can try to capture the DLL output. Would that parameter be located in the config file somewhere? I am using the Nooelec TCXO on...
> [GNSS-SDR] > > ;######### GLOBAL OPTIONS ################## > GNSS-SDR.internal_fs_sps=2000000 > GNSS-SDR.telecommand_enabled=true > GNSS-SDR.telecommand_tcp_port=3333 > > ;######### SIGNAL_SOURCE CONFIG ############ > SignalSource.implementation=Osmosdr_Signal_Source > SignalSource.item_type=gr_complex > SignalSource.sampling_frequency=2000000 > SignalSource.freq=1575420000 > SignalSource.gain=40...
> I have a question myself if you don't mind. I'm trying to plot something similar to yours. I've generated a simulated file with gps-sdr-sim and played it first into...
Also, I inherited the HRF1 code. I can guarantee the HRF1s were typical stock with Nooelec external TCXOs as I had bought them myself from Amazon.
@ZiglioUK I thought I'd give an update. I took quite a long break from this, but I tried using a USRP E310 receiver and here are my results:  By...
This image shows the oscillation is due to the clock error's oscillations. This graph corresponds to the HRF1 4 above. 
From the GNSS-SDR website, it appears that the way the pseudorange is calculated may be the cause of this. It appears to only use one time correction across all the...
I have since found that the user clock offset, which is output by the monitor_pvt.proto file can be used to correct the pseudorange. To my best guess, the known sources...