I have noticed when I start echos with a config using the -s option it doesn't appear to actually tune in the RTL.
I press start and my system sees no over-the-air test signals. However, if I use the control panel to -10khz followup by a +10khz then it starts receiving over-the-air test signals.
I haven't dug into the code as yet to see why this happens but thought I'd post this here for now.
regards,
--Andy
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I start it in auto mode (Shots After = 1) and then send an over-the-air ping it does in fact detect it. Does the screen grab and emits the audiable "ping" notifiy sound. However, the waterfall doesn't show the actual detection. It's as though the waterfall is showing a different spectrum even though the frequencies displayed are as tuned.
Setting Shots After to 2 and restarting, the waterfall doesn't display the echo on first test ping, quickly doing a freq adjust -10k then +10k and sending a second test ping and this one displays on the waterfall.
So, to recap, sending two test pings, the first doesn't appear on the waterfall (but is detected) a quick workaround fix adjusting the freq down/up and the second ping is, again, detected but this does appear on the waterfall.
I am not at all sure if this is a bug or if I am doing something wrong. However, after adjusting the bandwidth and offset I always need to tune up and then down again for the waterfall to display echos.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I am using a trunk based build.
I have noticed when I start echos with a config using the -s option it doesn't appear to actually tune in the RTL.
I press start and my system sees no over-the-air test signals. However, if I use the control panel to -10khz followup by a +10khz then it starts receiving over-the-air test signals.
I haven't dug into the code as yet to see why this happens but thought I'd post this here for now.
regards,
--Andy
More info:-
When I start it in auto mode (Shots After = 1) and then send an over-the-air ping it does in fact detect it. Does the screen grab and emits the audiable "ping" notifiy sound. However, the waterfall doesn't show the actual detection. It's as though the waterfall is showing a different spectrum even though the frequencies displayed are as tuned.
Setting Shots After to 2 and restarting, the waterfall doesn't display the echo on first test ping, quickly doing a freq adjust -10k then +10k and sending a second test ping and this one displays on the waterfall.
So, to recap, sending two test pings, the first doesn't appear on the waterfall (but is detected) a quick workaround fix adjusting the freq down/up and the second ping is, again, detected but this does appear on the waterfall.
I am not at all sure if this is a bug or if I am doing something wrong. However, after adjusting the bandwidth and offset I always need to tune up and then down again for the waterfall to display echos.