Hello,
When I use heatmap.py with output from rtl_power I get regularly spaced
vertical lines that do not appear to be related to any signal. They
look they like repeat at the dongle bandwidth (2048000Hz in this case).
The crop option for rtl_power reduces the presence but I am not sure f
that is intended by that option. Even at -c of 70% they are still there
(see attachment).
Is this because of small bin width? If I use a larger bin (32k) they
are still there. In this case there is no frequency legend along top so
can't compare if they happen more often.
Are these lines to be expected?
John
Hi there,
In debian, sdrangelove is having some build issues on mipsel [0].
At first, there was an issue regarding the '-msse2' switch.
If I delete the switch, then another build error happens:
======== 8< ========
[...]
[ 21%] Building CXX object CMakeFiles/sdrbase.dir/sdrbase/dsp/interpolator.cpp.o
/usr/bin/c++ -DQT_CORE_LIB -DQT_GUI_LIB -DQT_MULTIMEDIA_LIB
-DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB
-DUSE_FFTW -Dsdrangelove_EXPORTS -g -O2 -fstack-protector-strong
-Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG
-fPIC -isystem /usr/include/mipsel-linux-gnu/qt5 -isystem
/usr/include/mipsel-linux-gnu/qt5/QtCore -isystem
/usr/lib/mipsel-linux-gnu/qt5/mkspecs/linux-g++ -isystem
/usr/include/mipsel-linux-gnu/qt5/QtWidgets -isystem
/usr/include/mipsel-linux-gnu/qt5/QtGui -isystem
/usr/include/mipsel-linux-gnu/qt5/QtOpenGL -isystem
/usr/include/mipsel-linux-gnu/qt5/QtMultimedia -isystem
/usr/include/mipsel-linux-gnu/qt5/QtNetwork
-I/tmp/buildd/sdrangelove-0.0.1.20140824/obj-mipsel-linux-gnu
-I/tmp/buildd/sdrangelove-0.0.1.20140824/include
-I/tmp/buildd/sdrangelove-0.0.1.20140824/include-gpl -fPIC -o
CMakeFiles/sdrbase.dir/sdrbase/dsp/interpolator.cpp.o -c
/tmp/buildd/sdrangelove-0.0.1.20140824/sdrbase/dsp/interpolator.cpp
In file included from
/tmp/buildd/sdrangelove-0.0.1.20140824/sdrbase/dsp/interpolator.cpp:4:0:
/tmp/buildd/sdrangelove-0.0.1.20140824/include-gpl/dsp/interpolator.h:4:23:
fatal error: immintrin.h: No such file or directory
#include <immintrin.h>
^
compilation terminated.
[...]
======== 8< ========
Do you have any hint for this?
Thanks, best regards.
PS: Please keep me in CC, i'm not subscribed.
[0] https://buildd.debian.org/status/fetch.php?pkg=sdrangelove&arch=mipsel&ver=…
--
Arturo Borrero González
Oops, forgot to CC the mailing list.
On 09/21/2015 12:47 PM, Nikolay Dimitrov wrote:
> Hi Dimitri,
>
> On 07/04/2015 03:42 PM, Nikolay Dimitrov wrote:
>> Add scanner progress, including signal and squelch levels.
>> Rename demod_state->conseq_squelch to demod_state->squelch_conseq.
>>
>> The scanner progress feature can be tested like this:
>>
>> ./rtl_fm -f 144.000M:146.000M:25k -M fm -s 48k -l 100 -t 5 | aplay \
>> -r 48k -f S16_LE -t raw -c 1
>>
>> Signed-off-by: Nikolay Dimitrov <picmaster(a)mail.bg>
>> ---
>> src/rtl_fm.c | 43 +++++++++++++++++++++++++++++--------------
>> 1 file changed, 29 insertions(+), 14 deletions(-)
>
> Can you please take a look at this patch and decide whether it's worthy
> of applying to the rtl-sdr tree?
>
> Thanks in advance. Regards,
> Nikolay
This just removes few annoying warnings.
About the conversion of string to signed int.
- dev_index = boost::lexical_cast< unsigned int >( hackrf_serial );
+ dev_index = boost::lexical_cast< int >( hackrf_serial );
hackrf_device_list_open checks if value of dev_index is out
of range (eg negative) and returns proper error. In future negative value
can be used for something so this check is not necessary nor wanted.
P
Hi,
there is in gr-osmosdr a lot of code like:
hackrf_source_c::~hackrf_source_c ()
{
...
free(_buf);
_buf = NULL;
}
}
Setting value in destructor have sense in two case:
- they are used in some way in destructor of parent class
- You set then to something like 0xDEADBEEF and when pointer
from already destroyed class is used it will cause segfault.
Setting value to NULL is contraproductive because there is a lot of
checks if value is not NULL, this actually can hide some troubles of
calling something using already freed pointer.
I'm suggesting to remove this kind of code. I will prepare patch but now
I'm waiting if those two pending patches I have send before would be
accepter or not.
Is there any opinion which oppose previous claim?
With best regards,
JP.
It looks like I'm not the first person to have notices this, because after
I submitted a PR to the github project, I noticed another pull request
dating from May that has yet to make it into master.
Essentially what it boils down to is that char on arm systems, in my case
the raspberry pi, are treated as unsigned characters. So right now we have
a fix for the hackrf firmware update that only works on x86 systems. A
simple change to the source and sink typecasting from char to explicit
int8_t on the lookup table on the source.cc should fix this issue for all
platforms. In addition, I believe a typecast in the convert function for
the sink.cc would do it as well but I have not tested it and I don't
believe my current PR reflects that either.
Hi all,
I've created a simple little change for rtl_fm which outputs values of 0
(instead of nothing) when the output is squelched. Use the command
option "-E nullsquelch" to enable.
This is useful when live streaming output to icecast or similar which
requires a constant stream of data (such as
http://rtl-sdr.com/forum/viewtopic.php?f=7&t=141 or
http://www.windytan.com/2013/07/squelch-it-out.html).
Hopefully someone can merge this into the git repo, otherwise just patch
and build yourself.
Cheers,
Wilson
--
*Wilson Waters* | Software Engineer
*Alintech*
e: wilson.waters(a)alintech.com.au
w: www.alintech.com.au
Hi,Can someone inform us if the VTY configuration commands to change parameters e.g. cell id, location area code, MS power etc. that are run on OpenBSC VTY telnet interface take effect on next restart of the OpenBSC session or during the same session? If former is the case, is there any way to dynamically change Cell ID, LAC, MS TX power etc i.e. without restarting the OpenBSC session?
Regards,
Amber & Sarosh
Hi all,
I've created a simple little change for rtl_fm which outputs values of 0
(instead of nothing) when the output is squelched. Use the -E
nullsquelch option to enable.
This is useful when live streaming output to icecast or similar which
requires a constant stream of data (such as
http://rtl-sdr.com/forum/viewtopic.php?f=7&t=141).
Cheers,
Wilson.
