osmocom-sdr

osmocom-sdr@lists.osmocom.org

1 participants
910 discussions

Re: [Discuss-gnuradio] [GREP] Remove log4cpp
by Müller, Marcus (IEH) 29 Dec '18

29 Dec '18

Hi Martin, hi Community, first of all: thanks for all the fish err GREPs! We need to kick off this discussion. So, this PR is very dear to my heart, because I consider log4cpp to be an especially problematic dependency. And I consider our logging to be subpar considering the size of the code base, user base and the fact that people are using GNU Radio in infrastructure for rather expensive things. So, I took the opportunity (being at 35c3, just to pose around a little bit) and talked to a couple Osmocom folks. Osmocom people, please correct me if I make any mistakes. What they have in osmocore is essentiall logging in both quantized severity and in categories, and logging routing. For them, that's very important, as they use that to supply resilient infrastructure. I hope I'm representing the idea kinda correctly here: They might want to log system events ("SUPERVISOR: INFO system load surpassing 75%") somewhere, and development info ("gr-6G: TRACE found a preamble") on-screen, and critical messages ("gr-digital: FATAL run out of developer coffee") everywhere. I want that too. I want this to be easily integratable into software that uses GNU Radio as library. And if I'm already making wishes here, I want loggers that interface to modern logging systems, be it journald, graylog or SNMP. Something. So, I think that's pretty similar to what UHD does (correct me please, Martin). I think that UHD is a bit more flexible on the logging "categories" than I'd like to be, but that really just means we need to set a convention. So, I'm stuck wondering whether we adopt the self-implemented system that UHD uses, or the self-implemented system that osmocore uses, or implement our own. Familiarity suggests UHD, maturity osmocore. Best regards, Marcus On Thu, 2018-12-27 at 13:49 -0800, Martin Braun wrote: > This GREP was recently submitted here: > > https://github.com/gnuradio/greps/blob/master/grep-0013-remove-log4cpp.md > > We may or may not go through with this. However, we like to kill > dependencies (hey there node.js developers :D ), and log4cpp has some > issues of its own that we're currently inheriting. > > Personally, I use GR logging only for debugging purposes. But I know > that others use it for other reasons, and this thread is a good place > to discuss: > - Alternatives to log4cpp (I've listed Boost.Log and hand-spun as > options) > - What people need it for > - Is the current logging in a good shape as it is > - Who wants to own this task? > - etc. > > Cheers, > Martin > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio(a)gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

1 0

Android SDR server
by Семашко Максим 24 Dec '18

24 Dec '18

Hello! I made SDR server on my android TV BOX. WOrks great! (by ethernet!). I am connecting to RTL SDR v3 dongle via network from my windows pc running sdr sharp! Could you say, how can i automate server starting? Because every time i disconnect sdr sharp (on my pc), i should turn connect display to android box and click START STREAM button. It would be great if it possible to make sdr server independent with no need to start ir every time. Youre server and driver are great! -- Sincerely, Max Semashko

1 0

RFSpace SDR-IQ Question on Gain settings GNU Radio osmocom Source
by Greg 22 Dec '18

22 Dec '18

Hello, I hope this is the correct list to ask this question. I have an SDR-IQ connected via USB to Ubuntu 18.04 and version 3.7.13.4 GNU Radio. I am getting data from the source at correct center frequency and sampling rate, however ... I am having trouble find 3 of 4 gain controls. I believe these to be the settings affecting the device gain: 1. RF Gain: -20, -10, 0, 10 dB. These I can successfully change via the RF Gain setting in the Osmocom source. It's good! 2. IF Gain: 24, 18, 12, 6, and 0 dB. This is a "digital gain" and changes a coefficient of the "6620 Digital Downconverter", which apparently is hardware in the SDR-IQ which does filtering and decimation. 3. Preamp Gain, via a "GN Code" of range 0-127, which goes from Off, and then a range of -8.08 to 34 dB. 4. A step attenuator with 0 and 10 dB settings. I got the above by examining the "SpectraVue" Windows application for the SDR-IQ provided by RFSpace. #1 is no problem, it works. What about 2, 3, and 4? So is there any hope of controlling these settings with the osmocom source? Regards, Greg R

1 0

ld error when building latest git version. undefined reference to log4cpp::Appender ...
by Doron Behar 14 Dec '18

14 Dec '18

So I wanted to compile gr-osmosdr from source. I created a build directory and I ran `cmake ..` and then `make`. These are the errors I got: ``` [ 57%] Linking CXX shared library libgnuradio-osmosdr-0.1.5git.so /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/source_impl.cc.o: in function `_GLOBAL__sub_I_source_impl.cc': source_impl.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: source_impl.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/sink_impl.cc.o: in function `_GLOBAL__sub_I_sink_impl.cc': sink_impl.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: sink_impl.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/device.cc.o: in function `_GLOBAL__sub_I_device.cc': device.cc:(.text.startup+0x60): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: device.cc:(.text.startup+0x67): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/osmosdr/osmosdr_src_c.cc.o: in function `_GLOBAL__sub_I_osmosdr_src_c.cc': osmosdr_src_c.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: osmosdr_src_c.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/file/file_source_c.cc.o: in function `_GLOBAL__sub_I_file_source_c.cc': file_source_c.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: file_source_c.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/file/file_sink_c.cc.o: in function `_GLOBAL__sub_I_file_sink_c.cc': file_sink_c.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: file_sink_c.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/rtl/rtl_source_c.cc.o: in function `_GLOBAL__sub_I_rtl_source_c.cc': rtl_source_c.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: rtl_source_c.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/rtl_tcp/rtl_tcp_source_c.cc.o: in function `_GLOBAL__sub_I_rtl_tcp_source_c.cc': rtl_tcp_source_c.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: rtl_tcp_source_c.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/uhd/uhd_sink_c.cc.o: in function `_GLOBAL__sub_I_uhd_sink_c.cc': uhd_sink_c.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: uhd_sink_c.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/uhd/uhd_source_c.cc.o: in function `_GLOBAL__sub_I_uhd_source_c.cc': uhd_source_c.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: uhd_source_c.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/miri/miri_source_c.cc.o: in function `_GLOBAL__sub_I_miri_source_c.cc': miri_source_c.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: miri_source_c.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/hackrf/hackrf_source_c.cc.o: in function `_GLOBAL__sub_I_hackrf_source_c.cc': hackrf_source_c.cc:(.text.startup+0x58): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: hackrf_source_c.cc:(.text.startup+0x5f): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/hackrf/hackrf_sink_c.cc.o: in function `_GLOBAL__sub_I_hackrf_sink_c.cc': hackrf_sink_c.cc:(.text.startup+0x58): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: hackrf_sink_c.cc:(.text.startup+0x5f): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/bladerf/bladerf_source_c.cc.o: in function `_GLOBAL__sub_I_bladerf_source_c.cc': bladerf_source_c.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: bladerf_source_c.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/bladerf/bladerf_sink_c.cc.o: in function `_GLOBAL__sub_I_bladerf_sink_c.cc': bladerf_sink_c.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: bladerf_sink_c.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/rfspace/rfspace_source_c.cc.o: in function `_GLOBAL__sub_I_rfspace_source_c.cc': rfspace_source_c.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: rfspace_source_c.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/airspy/airspy_source_c.cc.o: in function `_GLOBAL__sub_I_airspy_source_c.cc': airspy_source_c.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: airspy_source_c.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/soapy/soapy_source_c.cc.o: in function `_GLOBAL__sub_I_soapy_source_c.cc': soapy_source_c.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: soapy_source_c.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/soapy/soapy_sink_c.cc.o: in function `_GLOBAL__sub_I_soapy_sink_c.cc': soapy_sink_c.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: soapy_sink_c.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/redpitaya/redpitaya_source_c.cc.o: in function `_GLOBAL__sub_I_redpitaya_source_c.cc': redpitaya_source_c.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: redpitaya_source_c.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/redpitaya/redpitaya_sink_c.cc.o: in function `_GLOBAL__sub_I_redpitaya_sink_c.cc': redpitaya_sink_c.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: redpitaya_sink_c.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/freesrp/freesrp_source_c.cc.o: in function `_GLOBAL__sub_I_freesrp_source_c.cc': freesrp_source_c.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: freesrp_source_c.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' /usr/bin/ld: CMakeFiles/gnuradio-osmosdr.dir/freesrp/freesrp_sink_c.cc.o: in function `_GLOBAL__sub_I_freesrp_sink_c.cc': freesrp_sink_c.cc:(.text.startup+0x54): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()' /usr/bin/ld: freesrp_sink_c.cc:(.text.startup+0x6b): undefined reference to `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()' collect2: error: ld returned 1 exit status make[2]: *** [lib/CMakeFiles/gnuradio-osmosdr.dir/build.make:555: lib/libgnuradio-osmosdr-0.1.5git.so.0.0.0] Error 1 make[1]: *** [CMakeFiles/Makefile2:141: lib/CMakeFiles/gnuradio-osmosdr.dir/all] Error 2 make: *** [Makefile:141: all] Error 2 ``` As you can see, all error messages refer to the same reference to a log4cpp appender function. I have log4cpp version 1.1.3 installed by my package manager on Arch Linux. It is installed in /usr/lib. It seems like a missing library in CMakeLists.txt . Am I correct? Thanks for creating this software.

2 2

[PATCH] import time library, fixes NameError Exception
by Tony Do 17 Nov '18

17 Nov '18

Error Message in osmocom_spectrum_sense command line tool: tune: Exception: global name 'time' is not defined Undefined command: "tune", Try "help" Simple fix for the osmocom_spectrum_sense utility, the message queue is really good at clearing itself, but for low tune/dwell delays the threads need to sleep while it clears. --- apps/osmocom_spectrum_sense | 1 + 1 file changed, 1 insertion(+) diff --git a/apps/osmocom_spectrum_sense b/apps/osmocom_spectrum_sense index ea365bb..0d280bd 100755 --- a/apps/osmocom_spectrum_sense +++ b/apps/osmocom_spectrum_sense @@ -30,6 +30,7 @@ from gnuradio.eng_option import eng_option from optparse import OptionParser import sys import math +import time import struct import threading from datetime import datetime -- 2.19.1

1 0

fl2k_test sample rate speeds up on Windows
by Francesco Gugliuzza 03 Nov '18

03 Nov '18

Hi, I encountered this strange behavior when running fl2k_test on Windows 7: basically after a while the sample rate drifts and speeds up considerably. Sometimes it even starts up directly like that. In the command prompt I get: C:\Users\Francesco Gugliuzza\Downloads\Sviluppo\FL2000fl2k_win_2018-08-09>fl2k_test.exe -s 138e6 Reporting PPM error measurement every 10 seconds... Press ^C after a few minutes. real sample rate: 146656386 current PPM: 62727 cumulative PPM: 62727 real sample rate: 150803676 current PPM: 92780 cumulative PPM: 77858 real sample rate: 149716182 current PPM: 84900 cumulative PPM: 80218 real sample rate: 150107883 current PPM: 87738 cumulative PPM: 82104 real sample rate: 150526750 current PPM: 90774 cumulative PPM: 83843 The same thing happens if I compile the latest osmo-fl2k myself using Cygwin. I'm running everything on a laptop with an i7 4710HQ CPU and 8 GB of ram, and I'm using a RayCue HDMI+VGA box. Do you have an idea why the real sample rate drifts so much? Thanks! -- Francesco Gugliuzza

2 3

(no subject)
by Tom Nash 31 Oct '18

31 Oct '18

Request sibscription

1 0

RTL_SDR dongle not being working with gnuradio
by MB 31 Oct '18

31 Oct '18

I have a rtl_sdr.com RTL2832U R820T2 dongle. It works with HDSDR and SDRSHARP programs. Using win10 64 BIT 10.0.17134.345 and GNURadio 3.7.13.4/V1.5Windows reports VID_0BDA, PID_2838 When I run GNUradio, I get [R82XX] PLL not locked! When I open the GNUradio command prompt and run rtl_test -t, I get this: setting gnuradio environmentMicrosoft Windows [Version 10.0.17134.345] (c) 2018 Microsoft Corporation. All rights reserved. C:\Program Files\GNURadio-3.7\bin>rtl_test -t Found 1 device(s): 0: Realtek, RTL2838UHIDIR, SN: 00000001 Using device 0: Generic RTL2832U OEM Found Rafael Micro R820T tuner Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6 Sampling at 2048000 S/s. No E4000 tuner found, aborting. C:\Program Files\GNURadio-3.7\bin> At this page, https://osmocom.org/projects/rtl-sdr/wiki/Rtl-sdr shows this table : VID PID tuner device name 0x0bda 0x2832 all of them Generic RTL2832U (e.g. hama nano) 0x0bda 0x2838 E4000 ezcap USB 2.0 DVB-T/DAB/FM dongle Is it possible RTL_TEST is looking for a E4000 because of it's dongle's screwy PID, even though it sees a R820T. If not, why is it not working?thanks. | | Virus-free. www.avast.com |

3 2

Disable internal AGC in AirSpy HF+
by Richard Hedlund 30 Oct '18

30 Oct '18

Hello, For my purposes in GNU Radio using the osmocom source block i would like to disable the internal AGC in my AirSpy HF+. I see that i can choose the "Gain Mode" setting, however i am not sure that will disable (when set to manual) the AGC on the AirSpy HF+. Do you know of any good way to achieve this? I have installed the following library for the AirSpy HF+, where there is an API which enables you to disable the AGC, however i am not sure how to achieve this in GNU Radio: https://github.com/airspy/airspyhf *$airspyhf_info* AirSpy HF library version: 1.4.2 S/N: "removed" Part ID: 0x00000001 Firmware Version: R1.7.2 Available sample rate: 768 kS/s *$uname -a* Linux hedric-dev 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Hopefully this is enough information for you, otherwise let me know. Kind regards, Richard

1 0

OSMOCOM-fft
by Babak Mafakheri 29 Oct '18

29 Oct '18

Dear all, I am confused about some parameters of osmocom fft spectrum analyzer. I am wonder what exactly the vertical axis shows? It is written Power(dB); if so, what is the reference power? Is it 1dBW? Moreover, by changing the PGA Gain, I will have different values of power (dB). What is the relation between PGA gain and the received power in dBm? In general, does anyone know how should I find the received power in dBm, having the PGA gain(dB) and the value on vertical axis. (Picture in attach) Looking forward to your reply. Bests, -- -- Le informazioni contenute nella presente comunicazione sono di natura privata e come tali sono da considerarsi riservate ed indirizzate esclusivamente ai destinatari indicati e per le finalità strettamente legate al relativo contenuto. Se avete ricevuto questo messaggio per errore, vi preghiamo di eliminarlo e di inviare una comunicazione all’indirizzo e-mail del mittente. -- The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you received this in error, please contact the sender and delete the material.

2 1

← Newer
1
...
19
20
21
22
23
24
25
...
91
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-sdr