Re: [Discuss-gnuradio] Using DDC/DUC in N210 with LFTX/LFRX
Just set the center frequency in the UHD sink/source. UHD will handle the tuning. On Thu, Oct 18, 2018 at 5:52 PM Wheberth Damascena Dias wrote: > Hi all, > I have to generate a narowband signal around 13.57MHz using LFTX/LFRX > frontend (no LO), but don't want to use a high samplerate due to CPU > constraints. > I suppose the Interpolator + DUC/DDC on the FPGA can translate the narrow > baseband to this center frequency, but I don't know to set the parameters > to use it in the sink block in gnuradio. > I don't have the hardware yet so I cant use the "cut and try" method. Can > someone just point me the right direction? > > Best Regards > > -- > > *Wheberth Damascena Dias* > linkedin.com/in/wheberth > whebe...@gmail.com > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Using DDC/DUC in N210 with LFTX/LFRX
Hi all, I have to generate a narowband signal around 13.57MHz using LFTX/LFRX frontend (no LO), but don't want to use a high samplerate due to CPU constraints. I suppose the Interpolator + DUC/DDC on the FPGA can translate the narrow baseband to this center frequency, but I don't know to set the parameters to use it in the sink block in gnuradio. I don't have the hardware yet so I cant use the "cut and try" method. Can someone just point me the right direction? Best Regards -- *Wheberth Damascena Dias* linkedin.com/in/wheberth whebe...@gmail.com ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Simulation to compute BER of a Modulator/Demodulator Encoding/Decoding system
On 10/17/2018 07:20 PM, Christian BusquielSanz wrote: > Good day again > > First of all, thank you very much, Mr Simson > Seeing a graph working doing what I wanted to do helped me a lot on > how to solve the problem that I had with mine > I actually expected a reply in one week and I got it in a couple of > days, so it was of great help and I wanted to thank you for that > > Second of all > Since I am writing long E-Mails... Should I delete the previous > E-Mails appended to this message after the signature to clean the > mailing list? > Also to free some weight from the messages > > I have been working on the flowgraph these days too > > I was using "Pack K bits" and I should have used "Unpack K Bits", as > you showed me, > because GMSK Demodulator demodulates each symbol providing one bit of > the result on consecutive bytes, > so I need to use only the last bits of each output to generate back the data > So that was my mistake > > Since the delay that works for me is 2, I set it as a variable so I > already have the proper value when running the flowgraph > But... > > A thing that I have noticed is that, when I run the flowgraph, I need > to click on the arrows of the delay, > change it and return it to the value 2, > to get the BER plotted on the QT GUI Time Sink If the BER icon is grey, you need to put your cursor on the BER icon, right click, and select enable. And you need to do the same thing for the two yellow icons for the CRC32 if you haven't already done so. All the icons in the flowgraph should have a white background. > > I have this Modulation/Demodulation flowgraph working > > Now I want to add an encoder, Reed-Solomon or Convolutional Coding > One at a Time > And later on, both of them > > But, as I stated earlier, I would like to ask for a way to convert > "Integer 8"/"Char" outputs from blocks into "Async Message" > to be able to use CCSDS Reed-Solomon Encoder/Decoder from "\Satellites\FEC" In the search box, enter "Async" and see pops up. Also, see the examples in the source code directory for gr-satellites. > > I have also found another Reed-Solomonn Encoder/Decoder here: > https://github.com/gnuradio/gnuradio/tree/master/gr-fec/lib/reed- That code is from the core source code for gnuradio - you already have it installed on your computer. > But I do not know how to install it, since I cannot find a way to > download the whole library and install it using the standard block > procedure: Don't even try to install it. > https://wiki.gnuradio.org/index.php/Guided_Tutorial_GNU_Radio_in_Python#3.2.6._Installing_Python_Blocks > mkdir build > cmake ../ > make > sudo make install > sudo ldconfig > > If I do this downloading all the files in a separate folder, I am > getting this output when runing the command "cmake ../": > " > CMake Error at /usr/share/cmake-3.10/Modules/CMakeDetermineSystem.cmake:174 > (file): > file failed to open for writing (No such file or directory): > > > /home/cbusquielsanz/GNURadio/work/Reed-Solomon/build/CMakeFiles/CMakeOutput.log > Call Stack (most recent call first): > CMakeLists.txt > > > CMake Error: Could not open file for write in copy operation > /home/cbusquielsanz/GNURadio/work/Reed-Solomon/build/CMakeFiles/3.10.2/CMakeSystem.cmake.tmp > CMake Error: : System Error: No such file or directory > CMake Error at /usr/share/cmake-3.10/Modules/CMakeDetermineSystem.cmake:186 > (configure_file): > configure_file Problem configuring file > Call Stack (most recent call first): > CMakeLists.txt > > > CMake Error at > /usr/share/cmake-3.10/Modules/CMakeDetermineCompilerId.cmake:145 > (file): > file problem creating directory: > > /home/cbusquielsanz/GNURadio/work/Reed-Solomon/build/CMakeFiles/3.10.2/CompilerIdC > Call Stack (most recent call first): > /usr/share/cmake-3.10/Modules/CMakeDetermineCompilerId.cmake:31 > (CMAKE_DETERMINE_COMPILER_ID_BUILD) > /usr/share/cmake-3.10/Modules/CMakeDetermineCCompiler.cmake:112 > (CMAKE_DETERMINE_COMPILER_ID) > CMakeLists.txt > > > CMake Error at > /usr/share/cmake-3.10/Modules/CMakeDetermineCompilerId.cmake:145 > (file): > file problem creating directory: > > /home/cbusquielsanz/GNURadio/work/Reed-Solomon/build/CMakeFiles/3.10.2/CompilerIdC > Call Stack (most recent call first): > /usr/share/cmake-3.10/Modules/CMakeDetermineCompilerId.cmake:31 > (CMAKE_DETERMINE_COMPILER_ID_BUILD) > /usr/share/cmake-3.10/Modules/CMakeDetermineCCompiler.cmake:112 > (CMAKE_DETERMINE_COMPILER_ID) > CMakeLists.txt > > > CMake Error at > /usr/share/cmake-3.10/Modules/CMakeDetermineCompilerId.cmake:145 > (file): > file problem creating directory: > > /home/cbusquielsanz/GNURadio/work/Reed-Solomon/build/CMakeFiles/3.10.2/CompilerIdC > Call Stack (most recent call first): > /usr/share/cmake-3.10/Modules/CMakeDetermineCompilerId.cmake:31 > (CMAKE_DETERMINE_COMPILER_ID_BUILD) > /usr/share/cmake-3.10/Modules/CMakeDetermineCCompiler.cmake:112 > (CMAKE_DETERMINE_COMPILER_ID) >
Re: [Discuss-gnuradio] Windows Crashing while Installing and Running GNU Radio
Rensi, I have never run into this problem. What happens if you physically disconnect the USRP and boot the device? This has to be a driver problem as obviously GNURadio isn't running when your are just logging in. Sounds like a problem between the UHD drivers and the USB chipset. Boot in safe made and remove the drivers, then try a reinstall. Which version of the GNURadio installer are you using? There is a recent version posted that has recent UHD drivers (don't recall this moment which ones) Geof On Tue, Oct 16, 2018 at 4:33 AM Rensi Mathew wrote: > Dear all > > I have installed Windows and then Ubuntu 16.04, as second OS. (Windows > booting fine at this point) > > Then I installed GNU radio and UHD drivers.(Windows booting fine at this > point) > > Then I connected my USRP and run an FM receiver program. > > After this when I tried to login to Windows, Windows has crashed and > doesn't boot. > > I has this experience twice. > > Has anyone experienced such as mine? What is the possible reason? Can > someone suggest how to avoid this. > > Thanking you > Rensi > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] macOS Mojave 10.14 and GNU Radio / UHD / Volk
Apple's latest OSX, macOS Mojave 10.14, was officially released on September
24, 2018 -- just under a month ago. I've been running the public beta for a few
months on a separate partition to make sure GR / UHD / Volk work on this new
release ... and, the good news is that that they do!
There has been very little discussion (at least that I've seen or heard of) in
any of our various forums about macOS Mojave 10.14 and issues with GNU Radio /
UHD / Volk, which either indicates the lack of interest / users or the fact
that they mostly work out of the box .. or, truth be told, probably more of the
latter but somewhere in between ;)
The primary point of issue that I know of is that the default PyQt4 Qt4
rendering configuration is "raster", which for some reason results in the GUI
window flashing a lot & sometimes being unresponsive. The solution is to create
or edit the file `~/.gnuradio/config.conf` and add (or tweak) the following:
{{{
[qtgui]
style = native
}}}
or use `opengl` if that works. The default is "raster", which is the fastest
and, generally, the most compatible, but for some reason this setting is borked
on macOS Mojave 10.14. For me, "native" works but "opengl" doesn't. No idea why
& it's not worth my time tracking down the issue since we're moving to Qt5 in
the 3.8 release -- and thus away from Qt4 except for legacy support -- and Qt5
should provide between rendering compatibility for OSX (both newer and older).
The primary limitation of moving to macOS Mojave 10.14 is that the new Xcode 10
does not provide 32-bit build support (macOS Mojave 10.14 itself still provides
32-bit runtime compatibility in its libraries). One can use an older macOS SDK
to get this support for the purposes of building as 32-bit, but any resulting
binaries may not function on macOS Mojave 10.14 due to API and/or ABI changes.
I really don't think this is a major issue for most folks.
So, if you're into OSX, GR / UHD / Volk can be made to play nicely with them
without too much compromise or extra work. Cheers! - MLD
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
