Hi!
today I discovered that the gr-osmosdr package in debian unstable contains
a whooping list of 96 patches. This is due to the fact that since November
2014 there hasn't been any tagged versions in the repository.
I'd like to suggest to tag releases a bit more often.
@horizon: What about jumping to 1.0.0 right away?
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
== OsmoCon 2018 ==
OsmoCon (Osmocom Conference) 2018 is the technical conference for
Osmocom users, operators and developers!
We are happy to announce the date of OsmoCon 2018. It has been scheduled
on October 18 + 19, 2018 and will happen in Berlin, Germany.
For the second time, the Osmocom Conference brings together users,
operators and developers of the Osmocom Open Source cellular
infrastructure projects, such as OsmoBTS, OsmoBSC, OsmoSGSN, OpenGGSN
and others.
Join us for two days of presentations and discussions with the main
developers behind Open Source Mobile Communications, as well as
commercial and non-profit users of the Osmocom cellular infrastructure
software.
You can find some initial information in our wiki at
http://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2018
which will be updated as more information becomes available.
== Call for Participation ==
We're also at the same time announcing the Call for Participation and
call on everyone with experiences to share around the Osmocom member
projects to submit talks, workshops, discussions or other proposals.
You can find the CfP at https://pretalx.sysmocom.de/osmocon2018/cfp
We are particularly looking for contributions about:
* updates on features/functionality/status of individual Osmocom projects
* success stories on how Osmocom projects are deployed in practice
* migration from OsmoNITB to the post-NITB architecture
* tutorials / workshops on how to setup / analyze Osmocom projects
* statistics, reporting, operations aspects of Osmocom projects
* third-party open source utilities to be used with Osmocom projects
Looking forward to meeting many existing and new Osmocom users at OsmCon
this October!
Regards,
Harald Welte
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hello
I'm trying to get the osmo-trx-lms to work with my LimeSDR. the setup is the latest version of LimeSDR and osmo-trx built from source with the command (./configure --with-lms) .
I can see the device through LimeUtil but when I try the command it fails with the following error
Info: SSE3 support compiled in and supported by CPU
Info: SSE4.1 support compiled in and supported by CPU
Sun Jul 29 07:01:27 2018 DLGLOBAL <0002> telnet_interface.c:104 telnet at 127.0.0.1 4237
Sun Jul 29 07:01:27 2018 DLCTRL <0009> control_if.c:887 CTRL at 127.0.0.1 4236
Config Settings
Log Level… 3
Device args…
TRX Base Port… 5700
TRX Address… 127.0.0.1
GSM BTS Address… 127.0.0.1
Channels… 1
Tx Samples-per-Symbol… 4
Rx Samples-per-Symbol… 4
EDGE support… 0
Reference… 0
C0 Filler Table… 1
Multi-Carrier… 0
Tuning offset… 0
RSSI to dBm offset… 0
Swap channels… 0
Tx Antennas… 'BAND1’
Rx Antennas… ‘LNAW’
Setting SCHED_RR priority(18)
Sun Jul 29 07:01:27 2018 DMAIN <0000> osmo-trx.cpp:379 [tid=140014553808704] Config: Setting SCHED_RR failed
I tried using the configuration file from the osmo-trx git url and the below file as well. both gave the same result.
https://osmocom.org/attachments/3219/limesdr.cfg1
Any ideas?
Thanks
Bahaeddin Sagar
Hello
I submitted a pull request on Github[1] which fixes bug with bias-T
power. The bias-T voltage was staying on after rtl tools ended. This
is dangerous and can lead to damage device.
[1] https://github.com/steve-m/librtlsdr/pull/47
Hi,
I have submitted a pull request on Github[1] which improves the
performance of the hackrf source. With this patch the conversion
int8_t -> float is done in realtime instead of looking up values in
the "_lut" lookup table.
In this way the compiler is able to generate AVX/SSE code (-O3
-march=native) to perform the conversion.
In [2] you can find a benchmark to show the differences.
Using -Ofast (or -O3) and -march=native I get ~2.8x using an
Intel i7 (4th gen) and 3.1x on a Core i5 (6th gen).
Gqrx with the patched library can play a WFM radio without any
interruption even with just 3 buffers (option="hackrf=0,buffers=3").
Best regards,
Alain
[1] https://github.com/osmocom/gr-osmosdr/pull/14
[2] https://gist.github.com/carpikes/cad029c338605f70d9f687aeee447db4
For anyone using the willcode/gr-osmosdr sdrplay2 branch, the SDRplay
API/SDK version 2.13 is now required. Previously, any 2.X version would
work.
There was a change to a function signature in 2.13, and since there
aren't a lot of users of this branch, I decided not to sprinkle ifdefs
around the code.
Thanks to krippendorf for the fix.