The idea was if both the receivers are at different distances then when we perform correlation between the received signals then we expected to see some lag in the peak with which to estimate the time difference of arrival of the two signals.

For a coarse estimate, you can also use you tx/rx leakage, which should be approximately at 0 m in your range/Doppler plot. Cheers, Martin On 03/03/2016 03:17 AM, Simon Olvhammar via USRP-users wrote: > Hello, > > We are currently trying to implement FMCW Radar functionality using the > Ettus USRP N210 and LabView.

It seems like the signal is gaited by Correlation Estimator and once it gets the correct sync word - the signal goes to Polyphase Clock Sync and CPU dies - it is 100% loaded all the time. If I run only loop back simulation the whole flow graph seems working fine. I wonder if noise or not very good signal destroys Polyphase Clock Sync.

Millions of receivers have been sold, but there's evidentially no good estimates of the number of users (at least there weren't a few years ago). Warner

The main effect of a slightly off position seems to be a diurnal component to the estimated uncertainty more than an actual component to the PPS output.

Also, the E-bolt does not supply per-satellite clock bias error estimates and has some different version and receiver health status messages. ---------------------------------------- _________________________________________________________________ Use video conversation to talk face-to-face with Windows Live Messenger. http://www.windowslive.com/messenger/

The book states that based on the entire Apollo program, they later estimated the units MTBF to be in excess of 50,000 hours (which is actually not a lot compared to what typical GPSDO's can achieve today). A single transistor, ROM bit, solder-joint, or resistor failure could have killed them. Scary considering they went for 2 week+ missions..

Several multiples of the estimated age of the universe. The potassium-40 in your own body is a much greater threat, followed by C-14, and various natural sources, smoke detectors, camping lantern mantles, etc... I understand the average person has several thousand K40 decay events in their body per second.

0.1847 0,00117 >> -0.18576 0,00116 >> -0.18674 0,00098 >> -0.18763 0,00109 >> -0.18842 0,00079<=== 11/3 day of the quake >> -0.18912 0,00090 >> -0.1897 0,00059 >> -0.1903 0,00060 >> -0.19103 0,00073 >> -0.192 0,00079 >> -0.19324 0,00124 I did a different exercise, I tossed the numbers into Gnumeric, removed the offset of the first sample and linear slope was estimated

The tbolt firmware does not attempt to estimate the oscillator aging rate. The alarm is based only upon the control voltage value.