Re: [Discuss-gnuradio] Sample Type Conversions

2018-08-18 Thread CEL
Hi Peter, >I have a rather dumb question, I'm a bit confused by that statement, because the rest of your email doesn't contain a dumb question. Instead, you just ask clever questions?! So, yes, your suspicion is right: > [if the floats span [-1,+1] inclusively]: Does this mean that I now have

Re: [Discuss-gnuradio] FPGA compatibility

2018-08-18 Thread CEL
The Ubuntu gnuradio package does install libgnuradio-uhd with it, and that in turn installs UHD. So, this was unnecessary! Also, it can't work: software must be run with the library versions that it was linked against, not some other random version. So, what you've done is exactly what you're obs

[Discuss-gnuradio] Plea for fun code: Replacement for the gr-digital/examples/narrowband/ examples

2018-08-17 Thread CEL
Hello coolest SDR mailing list known to sapient beings, it turns out that while cleaning up our code base, we broke most of our "narrowband" examples[1]. That's kind of OK, because these weren't overly representative of the "GNU Radio ways" one would pick today. Still, it's kind of said that we n

Re: [Discuss-gnuradio] installing gnuradio using pybombs

2018-08-15 Thread CEL
18-08-14 um 21:31 schrieb Müller, Marcus (CEL): > > ... are best submitted to > > https://github.com/gnuradio/gr-recipes/issues > > to Pybombs itself: > > https://github.com/gnuradio/pybombs/issues/ > > Ok, did it. Will see what happens. > > ... > > &g

Re: [Discuss-gnuradio] installing gnuradio using pybombs

2018-08-14 Thread CEL
your distro's package manager: Nah. building an OOT from source normally isn't that complicated. Best regards, Marcus On Tue, 2018-08-14 at 18:20 +0200, Roland Schwarz wrote: > > Am 2018-08-14 um 17:50 schrieb Müller, Marcus (CEL): > > Hi Roland, > > > > is the

Re: [Discuss-gnuradio] Probe Rate block

2018-08-14 Thread CEL
There's no relationship, unless you have *hardware* that you configure to that sampling rate. In a GNU Radio flowgraph without SDR hardware, every block just calculates as fast as it can. The sampling rate only has a *numerical* meaning to some blocks – for example, the signal source block uses th

Re: [Discuss-gnuradio] installing gnuradio using pybombs

2018-08-14 Thread CEL
Hi Roland, is there a specific reason you prefer building quite everything from source rather than going for the binary packages Ubuntu ships? For usage and module development, I generally recommend that people just use the packages that their distros offer. Now, as usual, Ubuntu lags quite a bit

Re: [Discuss-gnuradio] Any memory related block to compare datas ?

2018-08-14 Thread CEL
Sounds like a job for Vector Sink. Best regards, Marcus On Tue, 2018-08-14 at 14:02 +0300, ogün levent wrote: > Hello there, > > Is there any type of block in the GRC that allows us to record and > compare the incoming data on the fly without writing/reading a file > outside the flowgraph? The p

Re: [Discuss-gnuradio] Trying to connect USRP200 to Ubuntu18.04.1 in VM

2018-08-10 Thread CEL
Dear Luis, that's not necessary. If Linda uses the device from within the VM, then the host operating system (Windows) doesn't need to "know" how to talk to a USRP. What's important is that the virtualizer is told to "reach through" the USB port to the VM. Best regards, Marcus On Fri, 2018-08-1

Re: [Discuss-gnuradio] "Give me a ping, Vasili. One ping only, please."

2018-08-10 Thread CEL
Hi Markus, Well, the shortest possible pulse has duration 1/sampling rate and can be sent with 0…010…0 Now, that pulse has incredibly little power; and thus, the LO leakage and all negative effects will probably make that unnecessary hard to detect. I really recommend pulse compression: Can't

Re: [Discuss-gnuradio] Generating hexadecimal data and printing directly on the terminal

2018-08-09 Thread CEL
This would allow us to use some already validated codes and give a > more modular approach. > > Regards, > > Guilherme > > On Wed, Aug 8, 2018 at 9:01 PM Müller, Marcus (CEL) > wrote: > > Hi Guilherme, > > > > 1) "unpacked to packed" is

Re: [Discuss-gnuradio] Generating hexadecimal data and printing directly on the terminal

2018-08-08 Thread CEL
Hi Guilherme, 1) "unpacked to packed" is probably what you want! 2) don't do that, unless you really want to "humanly read" that output. Re 2): I just happen to explain why you shouldn't do that and how you can circumvent the need to do that. In essence, the standard output (at this time, at leas

Re: [Discuss-gnuradio] how to read .dat file saved via the file sink

2018-08-03 Thread CEL
Dear Linda, we hope you're doing well and hope you succeed in your SDR endeavors! But: seriously, I strongly recommend you keep with your installation of GNU Radio via apt. The version of GNU Radio that Ubuntu18.04 ships is relatively new, and you will have much less problems than when you build

Re: [Discuss-gnuradio] how to read .dat file saved via the file sink

2018-08-02 Thread CEL
Linda, you're looking in some completely unrelated folder. It comes with GNU Radio, not with Boost::geometry. I'm not sure how you've ended up looking in that folder. You need to look into GNU Radio's source tree, in gnuradio/gr- utils/octave. A simple Google search for "read_complex_binary.m GN

Re: [Discuss-gnuradio] how to read .dat file saved via the file sink

2018-08-01 Thread CEL
Hi Linda, first off: https://wiki.gnuradio.org/index.php/FAQ is your friend! On Tue, 2018-07-31 at 13:42 -0400, Linda20071 wrote: > Where could I find this command? I started Octave from Ubuntu command window. > Sumit already answered that: > > On Tue, Jul 31, 2018 at 1:24 PM, sumit kumar wro

Re: [Discuss-gnuradio] _uhd_swig.so: undefined symbol

2018-07-31 Thread CEL
Most likely problem is that you've built GNU Radio against a different version of UHD than you've got installed. best regards, Marcus On Tue, 2018-07-31 at 14:36 +0200, Savino Piccolomo wrote: > Hi members of the GNURadio Discussion List, > > I am using an USRP x310 and installed gnuradio/uhd us

Re: [Discuss-gnuradio] Dynamically changing bandwidth of QT GUI Frequency Sink

2018-07-31 Thread CEL
Hi Jason, just to be sure to understand what you need: Do you mean "zoom in x-axis"? (because technically, the bandwidth of that display is always Nyquist, i.e. defined by the sampling rate) Best regards, Marcus On Mon, 2018-07-30 at 16:57 -0400, Jason Hein wrote: > I have a GNU radio flow graph

Re: [Discuss-gnuradio] Issue with swig in packet_headerparser block

2018-07-31 Thread CEL
Looks like your library doesn't export that symbol (in this case, the constructor of the packet_header_default class). Did you make sure that the class bears the SPERRY_API flag? Best regards, Marcus On Mon, 2018-07-30 at 16:35 -0500, Jebreel Salem wrote: > Hi, > I am trying to create packet_hea

Re: [Discuss-gnuradio] upsampling module in gnuradio companion?

2018-07-27 Thread CEL
Yes, there are several things that do something that I'd call "upsampling". However, often, people mean different things when they say "upsampling", so what are you mathematically referring to? Regarding constellation sink: Well, just use the float-to-complex block and set the imaginary part to n

Re: [Discuss-gnuradio] Help needed with message ports

2018-07-27 Thread CEL
Awesome! Folks, this is the way I always hoped the community works. Cheers to you! On Thu, 2018-07-26 at 16:36 -0400, Michael Dickens wrote: > A quick followup on progress on this query: > > The issue is in lib/flowgraph.cc, where message connection edges are not > being used when counting conne

Re: [Discuss-gnuradio] Deprecated valve block

2018-07-24 Thread CEL
from "Copy"s and "Multiply by Matrix"es. Regards, Marcus On Tue, 2018-07-24 at 08:12 -0700, Kevin Reid wrote: > On Tue, Jul 24, 2018 at 8:07 AM Müller, Marcus (CEL) wrote: > > In fact, that should be pretty simple: A block that just consumes > > equally on all input

Re: [Discuss-gnuradio] Installing older GnuRadio version

2018-07-24 Thread CEL
Oh, and since you mentioned USRPs in your last message: Don't expect your GNU Radio 3.6.0 to work with modern UHD, and don't expect an old UHD to work with your modern USRPs! Best regards, Marcus On Tue, 2018-07-24 at 14:53 +, Müller, Marcus (CEL) wrote: > Hi Ayaz, > > On

Re: [Discuss-gnuradio] Deprecated valve block

2018-07-24 Thread CEL
Hi Ignatius and Volker, because "Valve" was a bad design from the start ;) So, what valve does is hold the flowgraph, reconfigure it, so that all unused inputs terminate into a null sink, and all unused outputs are "hacked" into a "done" state by connecting a "null source"->"head (0 items)" block

Re: [Discuss-gnuradio] Installing older GnuRadio version

2018-07-24 Thread CEL
Hi Ayaz, On Mon, 2018-07-23 at 16:28 +, Ayaz Mahmud wrote: > > Hi, > > I wanted to install GnuRadio 3.6.0 to test some old projects that I found > online. > > Will I be able to install both the latest 3.7.10 and 3.6.0 on same machine ? That's up to your experience of handling installat

Re: [Discuss-gnuradio] Switching between signal source with Selector block

2018-07-18 Thread CEL
Hi, I already replied in the other thread, but because people will find this in the future and wonder: Please don't use blocks from the "Deprecated" category. a) this block is going away in the next version of GNU Radio b) it causes a teardown/setup behind the scenes, and not all is guaranteed t

Re: [Discuss-gnuradio] Enable/Disable TX ports in B210 in 2x2 setup

2018-07-18 Thread CEL
> > Ayaz > > > From: Ayaz Mahmud > > Sent: Tuesday, July 17, 2018 4:39 PM > > To: Marcus D. Leech; > "Müller, Marcus (CEL)"; discuss-gnuradio@gnu.org > > Subject: Re: [Discuss-gnuradio] Enable/Disable TX ports in B210 in 2x2 setup > >

Re: [Discuss-gnuradio] USRP S-Band RX

2018-07-17 Thread CEL
Hm, I'd agree, with 60 dB attenuation, we should at least see reduced intermod products. OK, you said you had a spectrum analyzer that shows the spectrum without these spurs, so I'm trying to rule out TX overload/clipping: Can you use the screenshot function of that spectrum analyzer (or make a goo

Re: [Discuss-gnuradio] USRP S-Band RX

2018-07-17 Thread CEL
The equidistant spurs do really indicate RX overloading. Overloading lead to the amplifier being non-linear. Non-linearity leads to intermodulation, intermodulation leads to equidistant spurs. Please add attenuation; you don't want to damage your receiver, right? Best regards, Marcus On Mon, 20

Re: [Discuss-gnuradio] Need help with CtrlPort Performance Monitor

2018-07-16 Thread CEL
Marcus On Sun, 2018-07-15 at 21:47 -0700, Jim Larsen wrote: > Hi Marcus, > > Thank you for your patience with my CtrlPort Performance Monitor > problems. I have been distracted by other projects and finally had > time to try your suggestion. > > > On Jul 4, 2018,

Re: [Discuss-gnuradio] Enable/Disable TX ports in B210 in 2x2 setup

2018-07-14 Thread CEL
Hey Marcus, yep, good catch: 64 kHz is far too low a sampling rate; Ayaz, start with something like 1 MS/s. (also, what kind of CSI will you be getting when observing a 64 kHz wide channel? Are you looking for reflections that have a path length difference larger than (sandy gears turning in my he

Re: [Discuss-gnuradio] QT GUI Entry Block issue

2018-07-13 Thread CEL
Hi John, thanks for the info! Please don't install 3.7.12, but directly go for the most recent release 3.7.13.3 Best regards, Marcus On Fri, 2018-07-13 at 11:16 -0400, John Makous wrote: > This is a final follow-up to my recent posts regarding the failure of > the QT GUI Entry block to work prop

Re: [Discuss-gnuradio] E310: Setting "master clock"

2018-07-12 Thread CEL
Hi Mike, Martin and Marcus, I'll argue that from a mile high that changing MCR at runtime of a GR flow graph is an *extreme* corner case: It de-facto requires teardown of the UHD streamer, right (when else would you need it)? And that really doesn't fit all too nicely with GNU Radio's streaming ar

Re: [Discuss-gnuradio] Missing uhd_swig

2018-07-09 Thread CEL
ps://copr.fedorainfracloud.org/coprs/marcusmueller/gnuradio/ On Mon, 2018-07-09 at 14:02 -0400, Mike Gilmer wrote: > IIRC > > I built from source both this time and previously (under Fedora 23) > because the "package" would not build successfully. > > Mike > > On

Re: [Discuss-gnuradio] Missing uhd_swig

2018-07-09 Thread CEL
Hm, did you also build UHD from source on your old Fedora? On Mon, 2018-07-09 at 13:46 -0400, Mike Gilmer wrote: > I updated my Fedora version release 28 > > Afterwards I had to rebuild GNU radio (of course) to get GNU radio companion > to even load. > I though my work was done, but now that I've

Re: [Discuss-gnuradio] Introducing gr-adapt

2018-07-07 Thread CEL
Hi Karel, wow, this looks interesting! Thank you for that contribution :) I haven't played around with it yet, just browsed the source code a tiny bit, and I've got to say: I love this module :) Things that I'd like to especially point out: * It's great that you actually have pretty much self-

Re: [Discuss-gnuradio] Use microphone as sound source for USRP

2018-07-06 Thread CEL
There's no "data rate" on these GPIO pins; you'd have to bitbang them. Interfacing with a digital microphone won't work, as you can't ask their binary states quick enough. Honest recommendation: Use anything else to connect your microphone to your PC – if you have a microphone for which an audio d

Re: [Discuss-gnuradio] Need help with CtrlPort Performance Monitor

2018-07-04 Thread CEL
gt; > On Jun 24, 2018, at 1:20 AM, Müller, Marcus (CEL) > > wrote: > > > > So, each time you run your flow graph, the following line should > > change: > > > > monitor::endpoints() = -h vmware -p 40161 > > > > at least in the port number at th

Re: [Discuss-gnuradio] "sample delay" in "Decimating FIR Filter" at GRC

2018-07-02 Thread CEL
Hi Ali, I went into the GRC file (in gnuradio/gr-filter/grc) and looked that up: It calls block::declare_sample_delay https://www.gnuradio.org/doc/doxygen/classgr_1_1block.html#acad5d6e62ea 885cb77d19f72451581c2 (this documentation isn't great and doesn't really say what declare_sample_delay act

Re: [Discuss-gnuradio] set_history() for multi-input blocks

2018-07-01 Thread CEL
The history is really just the same ring-alike buffer. Setting the history really does nothing but tell the scheduler that although you consumed N samples, it may only declare (N-history) as "done with", and will present you the last (history) samples as beginning of your new input item buffer on t

Re: [Discuss-gnuradio] making signal source based on a certain format

2018-07-01 Thread CEL
Hi Linda, Do you mean "sending 0 in between" or do you mean "switch transmission on some SDR device on and off"? First case: multiply with a (threshold(sawtooth from signal source)) Second case: see the gr-uhd examples on how to do bursty transmissions, if a USRP is what we're talking about! If

Re: [Discuss-gnuradio] Text transmission using usrp

2018-06-28 Thread CEL
use packet_loopback_hier.grc to send a text file in other > words is it possible to packetize a text file and use it? > On Wed, Jun 27, 2018, 11:49 AM Müller, Marcus (CEL) wrote: > > Hi Trueblues, > > > > the packet encoder and decoder blocks are known to be broken – tha

Re: [Discuss-gnuradio] Text transmission using usrp

2018-06-27 Thread CEL
Hi Trueblues, the packet encoder and decoder blocks are known to be broken – that's why they are in the "deprecated" category! It'll be gone with the next minor release of GNU Radio, even. (same will happen to WX GUI, so switch to Qt now!) So, please don't use them; I don't expect them to work. I

Re: [Discuss-gnuradio] QT Gui mem alloc error - runs OK if R, C hints deleted

2018-06-26 Thread CEL
bgsym` I was wrong, at that point it's totally OK to complain about missing symbol. Just say it's OK to set the breakpoint on future library load. On Tue, 2018-06-26 at 10:47 +, Müller, Marcus (CEL) wrote: > Hi Tom! > > Hm, no, I wouldn't be aware of any limitations, a

Re: [Discuss-gnuradio] QT Gui mem alloc error - runs OK if R, C hints deleted

2018-06-26 Thread CEL
Hi Tom! Hm, no, I wouldn't be aware of any limitations, and even if such exist, things shouldn't die with a std::bad_alloc! Ok, so I'm wondering how we can move forward with this. Let us try this: * Can you share a proof of failure flow graph with us? That way, everyone's definitely talking abou

[Discuss-gnuradio] Project Announcement: "master" will require C++11 soon

2018-06-25 Thread CEL
Hello greatest SDR community to roam the earth, as we're progressing towards a merge of the next branch into master, which will actually bring us new features and challenges like Python3, QT5, YAML instead of XML in GRC and many, many specific improvements, I'll announce that we're switching over

Re: [Discuss-gnuradio] Need help with CtrlPort Performance Monitor

2018-06-24 Thread CEL
Hope that helps us get forward, Best regards, Marcus On Sat, 2018-06-23 at 16:50 -0700, Jim Larsen wrote: > Marcus, > > Thank you for your reply. > > > On Jun 23, 2018, at 4:00 AM, Müller, Marcus (CEL) > > wrote: > > > > Can you share the full console output

Re: [Discuss-gnuradio] Import GNURadio data to matlab

2018-06-23 Thread CEL
Dear Priyanka, um, the whole point of that article is that you need to give the third parameter, the kind of date (Matlab docs erroneously call this precision, it's really the data type): fopen(your_filename_here, 'rb', 'float') The fact that you're even asking about quotes around the file name

Re: [Discuss-gnuradio] Need help with CtrlPort Performance Monitor

2018-06-23 Thread CEL
Hi Jim, Can you share the full console output of your flow graph? Also note that the most "fragile" dependency of GNU Radio right now is Thrift, if you can check whether your CMake output says that Thrift was used, it would be helpful. Thrift is the RPC middleware that ctrlport uses to expose its

Re: [Discuss-gnuradio] ImportError: No module named 'gnuradio'

2018-06-22 Thread CEL
Hi Evans, Just for clarification: You did install GNU Radio on your windows, right? Best regards, Marcus On Thu, 2018-06-21 at 08:37 +0300, evans ryanada wrote: > i am trying to run a .py file generated from GRC 3.7.11 but am getting an > error...displaying the following message.. > > C:\Use

Re: [Discuss-gnuradio] FIFO file , File sink , File souce

2018-06-20 Thread CEL
ersa , u can use both chain in same flowgragh .. > > > > On Wednesday, June 20, 2018, 4:55:31 PM GMT+4:30, Müller, Marcus (CEL) > wrote: > > > Please try to keep answers on the list. > Also, it's pretty frustrating to have helped you, but not knowing h

Re: [Discuss-gnuradio] FIFO file , File sink , File souce

2018-06-20 Thread CEL
gt; I split flowgraph in two part and it worked ...and it does'nt matter run > witch flowgraph first > > > Best Regards. > > > > > > > > > On Wednesday, June 20, 20

Re: [Discuss-gnuradio] FIFO file , File sink , File souce

2018-06-20 Thread CEL
graph, so in this situation i must run which side > of transfer first?? > > On Wednesday, June 20, 2018, 4:40:06 PM GMT+4:30, Müller, Marcus (CEL) > wrote: > > > Well, I don't know what problem you're solving. It works if you're not > doing this in the

Re: [Discuss-gnuradio] Error Linking UHD

2018-06-20 Thread CEL
ules/GrTest.cmake > > D cmake/Modules/UseSWIG.cmake > > > > but still no luck (the undefined symbol error still exists). > > > > It might be worth to mention, the version I use is 3.7.11.1. > > > > > > On Tue, Jun 19, 2018 at 2:47 PM Müller, Marcus (CEL)

Re: [Discuss-gnuradio] FIFO file , File sink , File souce

2018-06-20 Thread CEL
That's normal FIFO behaviour! From `man 3 mkfifo`: > Opening a FIFO for reading normally blocks until some other process opens the same FIFO for writing, and vice versa. Remember, the GRC file is just converted to a Python program, in which the different blocks are instantiated sequentially.

Re: [Discuss-gnuradio] Error Linking UHD

2018-06-20 Thread CEL
ook? > > On Tue, Jun 19, 2018 at 2:47 PM Müller, Marcus (CEL) > wrote: > > add a "message ()" directive that prints the GNURADIO_ALL_LIBRARIES > > that is actually used in your lib/CMakeLists.txt. If that is wrong: > > > > Move your OOT's cmake

Re: [Discuss-gnuradio] Error Linking UHD

2018-06-19 Thread CEL
ke ../; and make -j7; and > make install; popd" ~ 50 times since yesterday :) > > Any suggestions for debugging it? > > On Tue, Jun 19, 2018 at 2:33 PM Müller, Marcus (CEL) wrote: > > I must admit this is surprising to me, as the line of code where > > LIBS

Re: [Discuss-gnuradio] Error Linking UHD

2018-06-19 Thread CEL
I must admit this is surprising to me, as the line of code where LIBS=... is printed is pretty integrally coupled to the line that specifies what GNURADIO_ALL_LIBRARIES is. Maybe CMake got confused? I know this is kind of a "haveyoutriedturningitoffandonagain" answer, but have you tried completely

Re: [Discuss-gnuradio] Unable to see GSM signals in USRP Spectrum Scanner (FFT)

2018-06-18 Thread CEL
Hi Amrit, Well, usrp_spectrum_sense is a hopping observer, and GSM is a hopping system: your probability of intercept is rather low. Your probability of intercept is in fact, really zero, if your phone doesn't do GSM (2G), but uses 3G (UMTS) or 4G (LTE): these use other frequencies altogether. So

Re: [Discuss-gnuradio] USRP Digital Modulation - Loopeback Constellation

2018-06-14 Thread CEL
rpah for a complete 16QAM modulator/demodulator? > > Kind regards. > > On Thu, Jun 14, 2018 at 12:46 PM, Müller, Marcus (CEL) > wrote: > > Hi Luis, > > On Thu, 2018-06-14 at 12:29 +0200, Luis Felipe Albarracin Sanchez > > wrote: > > > Hello Marcus, > >

Re: [Discuss-gnuradio] USRP Digital Modulation - Loopeback Constellation

2018-06-14 Thread CEL
Hi Luis, On Thu, 2018-06-14 at 12:29 +0200, Luis Felipe Albarracin Sanchez wrote: > Hello Marcus, > > Thanks for the response, > > I am not using an attenuator, because i font have one , i am only with my > cable, but i have meassured the Power before connecting to the RX in my USRP, > so it wo

Re: [Discuss-gnuradio] USRP Digital Modulation - Loopeback Constellation

2018-06-14 Thread CEL
Hi Luis, I hope you're using an attenuator with a cable or antennas in your feedback, not to risk damaging your receiver! What you need to do to get a similar constellation is the whole dance that is taught in your average digital communication basics lecture: Synchronization in time, and phase

Re: [Discuss-gnuradio] Faster FPGA clock rates

2018-06-14 Thread CEL
Dear Maria, no, GNU Radio is a pure software framework; it doesn't directly talk to any hardware, but has a gr-uhd component which uses UHD, Ettus' own driver, to talk to your USRP. Anyway, you can't simply reprogram the FPGA to give you higher clock rates. 61.44 MHz is physically the most that t

Re: [Discuss-gnuradio] GNURadio Help

2018-06-13 Thread CEL
> > > > > I need to rebuild the frequency, do fft and then transfer the whole > > > > > array from 70 to 6GHz to the host machine. I do not quite imagine how > > > > > you can do this with standard blocks in gnuradio. > > > > &

Re: [Discuss-gnuradio] GNURadio Help

2018-06-13 Thread CEL
ed, 2018-06-13 at 17:42 +0300, Ivan Zahartchuk wrote: > I need to rebuild the frequency, do fft and then transfer the whole array > from 70 to 6GHz to the host machine. I do not quite imagine how you can do > this with standard blocks in gnuradio. > > > 2018-06-13 17:32 GMT+

Re: [Discuss-gnuradio] GNURadio Help

2018-06-13 Thread CEL
Dear Ivan, you don't pass data to a block yourself. You write a block that does a clearly-limited signal processing job, and use GNU Radio to connect that to other blocks: https://tutorials.gnuradio.org In your case, instantiating a USRP source in your block makes absolutely no sense, for exam

Re: [Discuss-gnuradio] GR-UHD Compatibility Issue

2018-06-12 Thread CEL
s available at that one > was one of the closest to the top. > > I will checkout the others. > > Is there any stable Version you would recommend? > > Kind regards. > > On Tue, Jun 12, 2018 at 10:06 AM, Müller, Marcus (CEL) du> wrote: > > As Marcus said, 3.0.4

Re: [Discuss-gnuradio] GR-UHD Compatibility Issue

2018-06-12 Thread CEL
As Marcus said, 3.0.4 is somewhere between "ancient" and "archaic". Is there a specific reason you consider that version? On Tue, 2018-06-12 at 03:01 -0400, Marcus D. Leech wrote: > On 06/12/2018 02:49 AM, Luis Felipe Albarracin Sanchez wrote: > > Hello to all, > > > > i just did, what the stable

Re: [Discuss-gnuradio] volk float32->int8 kernel and thus float_to_char block round or floor, depending on VOLK machine

2018-06-09 Thread CEL
Oh wait, it gets better: while the float->int16 does indeed use rintf, float->int32 doesn't… now we don't have a majority situation pro- rounding anymore… argh. On Sat, 2018-06-09 at 19:24 +, Müller, Marcus (CEL) wrote: > Hi Paul, > > I agree with everything you

Re: [Discuss-gnuradio] volk float32->int8 kernel and thus float_to_char block round or floor, depending on VOLK machine

2018-06-09 Thread CEL
their flowchart break because of this. Then again, in the current > situation the outcome depends on which optimizations your machine > happens to have available, so that's also quite bad. > > Possibly there is also an optimization opportunity of never using > 'generic&#x

[Discuss-gnuradio] volk float32->int8 kernel and thus float_to_char block round or floor, depending on VOLK machine (was: Re: Incorrect quantizations when converting from float to char)

2018-06-09 Thread CEL
nd of the routine, e.g.: > > https://github.com/gnuradio/volk/blob/master/kernels/volk/volk_32f_s3 > 2f_convert_8i.h#L200 > > I had not really looked into that before because having run the > volk_profile seemed to make no difference. > > Regards, Paul Boven. > > On 06/09/201

Re: [Discuss-gnuradio] Incorrect quantizations when converting from float to char

2018-06-09 Thread CEL
_sse2 > > Regards, Paul Boven. > > On 06/09/2018 05:30 PM, Müller, Marcus (CEL) wrote: > > Hi Paul, > > > > hm, OK, considering the actual conversion is done in VOLK, can you > > tell > > us > > > > * whether ~/.volk/volk_config exists (and if s

Re: [Discuss-gnuradio] Incorrect quantizations when converting from float to char

2018-06-09 Thread CEL
If possible, please track progress on https://github.com/gnuradio/volk/issues/188 On Sat, 2018-06-09 at 15:30 +, Müller, Marcus (CEL) wrote: > Hi Paul, > > hm, OK, considering the actual conversion is done in VOLK, can you > tell > us > > * whether ~/.volk/volk_config e

Re: [Discuss-gnuradio] Incorrect quantizations when converting from float to char

2018-06-09 Thread CEL
Hi Paul, hm, OK, considering the actual conversion is done in VOLK, can you tell us * whether ~/.volk/volk_config exists (and if so, its contents regarding volk_32f_s32f_convert_8i ) * what the output of `volk-config-info --machine` is? Thanks, Marcus On Sat, 2018-06-09 at 17:13 +0200, Paul Bov

Re: [Discuss-gnuradio] Bug in fmdet_cf_imp.cc

2018-06-09 Thread CEL
Hello Eugene, Thanks! I.. uh. wat?! There's a lot of interesting things in the code of that block. d_8 being a constant with value 8 not being the largest surprise; I see that this should be a derivative-approximating filter, right, which inherently needs to have high-pass characteristics, and hon

Re: [Discuss-gnuradio] GNU Radio not installing: Build Failed

2018-06-09 Thread CEL
Hello Jason and Derek! What Derek wrote very much sums up what is going on in my head; I should probably write that down. So, knowing fully this is everything but an official announcement, 3.8 will need C++11. Just wanted to confirm that. On the way to 3.8, we'll thus need to "weed out" the syst

Re: [Discuss-gnuradio] make maint-3.7 fails

2018-06-08 Thread CEL
Hi Tom, got a bit of worries about this one: On Fri, 2018-06-08 at 09:17 -0700, Tom McDermott wrote: > modified: volk (new commits) Which basically means that the Volk submodule isn't in the state the main module's branch expects it to be, and that's exactly what's going wrong there. Best

Re: [Discuss-gnuradio] Visualising data with GNURadio

2018-06-08 Thread CEL
Hi Jaco, this is really a reasonable thing to want, but to be honest, GNU Radio's visualizations are very much oriented along the streaming nature of GNU Radio – and scrollback doesn't fit all to well. I recommend https://github.com/miek/inspectrum , which is relatively new, and relatively cool :

Re: [Discuss-gnuradio] A few questions regarding gr-ieeee802-11

2018-06-08 Thread CEL
Hi Tal, 3.7 is the maint-3.7 branch, master works towards 3.8, and a milestone of that will be when next is merged into it. You can expect a 3.8 release when next is merged, and all the serious kinks that came with it are contained enough for us to risk a release :) Best regards, Marcus On Fri,

Re: [Discuss-gnuradio] Memory Blocks & Struct Variable

2018-06-07 Thread CEL
Sorry, I replied with an empty mail just now, confusion of keys. I added more coffee to solve the issue with the author. Steve, assuming your set_mag() is in C++: if you have control over the set_mag() method, write it so that it accepts vectors, for example. Then, you can just use Python lists o

Re: [Discuss-gnuradio] Memory Blocks & Struct Variable

2018-06-07 Thread CEL
On Thu, 2018-06-07 at 08:45 +0300, shachar J. brown wrote: > Hi Everyone, > > I'm sure someone has encountered one of the following questions. Please help > me figure this out: > At certain points in my flow graph I have different scenarios, each demanding > a set of different parameters. I now

Re: [Discuss-gnuradio] Correct way to add constructor parameter

2018-06-06 Thread CEL
Also, while you're at it: If you have parameters (like potentially your scaling) that you'd like to update externally, for example from a different block, it's not that bad an idea to add a "command" message port, with a message handler that does the setting. I mention this because messages are ha

Re: [Discuss-gnuradio] functions to generate random signals

2018-06-05 Thread CEL
Hi! Linda, you **must not** use rand(). It's not thread-safe, and GNU Radio is inherently multithreaded. For reference, I've pointed that out in a recent mail exchange [-1]; the recommendation was the same as Dave's: use C++11's std:: random generators; that email even has a small code example :)

Re: [Discuss-gnuradio] A small embedded python block which does frequency peak detect

2018-06-05 Thread CEL
Hello Ji-yeon, I think the best way to help you forward here is point out that the description of the block is very close to actually being an algorithmical description of what you need to do! So, maybe you're just missing the tools to build your own blocks and use the existing blocks; in that cas

Re: [Discuss-gnuradio] install issue with c++11

2018-06-05 Thread CEL
Then the answer is really, very likely, to use a container of sorts. Docker seems to be the choice for that these days. Best regards, Marcus On Tue, 2018-06-05 at 08:08 -0700, Jason Matusiak wrote: > I wasn't worried about my gnuradio builds as much as my system as a whole > when I was mucking w

Re: [Discuss-gnuradio] install issue with c++11

2018-06-05 Thread CEL
The whole purpose of using PyBOMBS is to work in PREFIXes, so no need to do that – PyBOMBS does that automatically. On Tue, 2018-06-05 at 10:38 -0400, Dave NotTelling wrote: > Check out > https://github.com/gnuradio/pybombs#configuring-a-prefix-environment-eg-for-cross-compiling. > You might be

Re: [Discuss-gnuradio] install issue with c++11

2018-06-05 Thread CEL
Hi Jason, to not hose my system every day, I simply work in prefixes. Basically, find my shell's RC file below. With options like `- DCMAKE_INSTALL_PREFIX=$GRPREFIX` (for CMake) or `export`ing PREFIX=$GRPREFIX (before running ./configure scripts) one can set the installation directory so that thin

Re: [Discuss-gnuradio] Selecting the precise sampling point from many samples

2018-06-04 Thread CEL
Hi Carlo, not quite sure I get what you mean with "bandlimiting"? What with "transposing"? Regarding "padding": do you mean interpolation? Again, you'd use a resampler, and in your case, the rational resampler with decimation=1, interpolation = 48 would do the trick. Best regards, Marcus On Mo

Re: [Discuss-gnuradio] How to modify the existing module and make it effective

2018-06-04 Thread CEL
Hello! If you've modified it, I guess you already have the GNU Radio source code. So, you must make sure that you're using the GNU Radio that you have built from source: https://www.gnuradio.org/doc/doxygen/build_guide.html Simply build your modified GNU Radio and install it :) How that works

[Discuss-gnuradio] Release 3.7.13.2 is out! (was: Release 3.7.13.1 is out!)

2018-06-01 Thread CEL
I messed up, and v3.7.13.1 was tagged off-branch, whereas I pushed a commit that incorrectly changed the version number to the maint-3.7 branch. I ask you to not use 3.7.13.1 but 3.7.13.2. Thank you! Best regards, Marcus On Thu, 2018-05-31 at 19:30 +, Müller, Marcus (CEL) wrote: > Dear b

[Discuss-gnuradio] Release 3.7.13.1 is out!

2018-05-31 Thread CEL
Dear best community of an SDR project known to mankind! It took me longer than I'd like to admit, but we've finally come to a release of GNU Radio's maintenance branch 3.7. I'm very thankful for the contributors we've had this time, especially because the amount of first-time code contributions is

Re: [Discuss-gnuradio] Resampling rate method assistance

2018-05-30 Thread CEL
Hi Carlo! On Wed, 2018-05-30 at 23:04 +1000, Carlo Manfredini wrote: > My hardware arrangement is fairly demanding, I think ? > I wish to resample between a Red Pitaya connected via ethernet running at > 100kSps and a USB-audio unit (UCA-202) running at 48kSps. That's not "much signal to process

Re: [Discuss-gnuradio] random number coding problem

2018-05-30 Thread CEL
Hi! So, I'm really not sure how to help you here: I have to expect you to be able to call a function in C++ to give you value. The level of understanding necessary to transfer my example to replace your usage of rand() in your code isn't really high. Maybe you'd want to read a good C++ introducto

Re: [Discuss-gnuradio] Resampling rate method assistance

2018-05-30 Thread CEL
C..and some breaks in the continuous signal) > > Regards. > > On 29 May 2018 at 23:19, Müller, Marcus (CEL) > wrote: > > Hi Carlo, > > > > if you're using GNU Radio's rational resampler, you're already > > using > > that method! > >

Re: [Discuss-gnuradio] debugging for gnuradio DSP programming

2018-05-30 Thread CEL
Hi Linda, for debugging *programmatic* things (i.e. crashes, program doesn't calculate what I think it should), you'd use a debugger: https://wiki.gnuradio.org/index.php/TutorialsDebugging https://wiki.gnuradio.org/index.php/TutorialsGDB for debugging *algorithmic* things (i.e. I don't know why

Re: [Discuss-gnuradio] Resampling rate method assistance

2018-05-29 Thread CEL
y and see how it compares. > Regards. > > On 29 May 2018 at 19:34, Müller, Marcus (CEL) wrote: > > Hi Carlo, hi Linda: > > > > as Linda said,the RR approach works really well and is numerically > > relatively stable until you hit really ugly ratios (after, of course

Re: [Discuss-gnuradio] Resampling rate method assistance

2018-05-29 Thread CEL
Hi Carlo, hi Linda: as Linda said,the RR approach works really well and is numerically relatively stable until you hit really ugly ratios (after, of course, cancelling the fraction as far as possible). But what is "ugly" here? In theory, rational resampling by M/N (note: M,N coprime!) would work

Re: [Discuss-gnuradio] Channel Coding

2018-05-29 Thread CEL
Hello Dewan! On Mon, 2018-05-28 at 16:09 -0400, Dewan Arif wrote: > 1. In FEC_extended_encoder, What is the Encoder Objective ?? How to put the > value in Encoder Objective ?? Small typo: it's "encoder object", not "objective" :) What you want there is to put the ID of a "Encoder Definition" (

Re: [Discuss-gnuradio] Underflow and Overflow

2018-05-28 Thread CEL
Hi Alvin, you've already gotten plenty of info on this list from where over- and underflows come. We've really addressed all this before[1,2,3,4,5,6,7,8,9,10,11,12,etc], and you've gotten sufficient recommendations. Please do avoid to spam the mailing list with redundant questions. Let me quickly

Re: [Discuss-gnuradio] a single source module to generate a random sequence with a pre-ample in the front

2018-05-26 Thread CEL
Hi Linda, Why should the Ettus website contain GNU Radio examples? Also, why should this specific example exist? Anyway, all you need is the "vector insert" block. Best regards, Marcus On Fri, 2018-05-25 at 21:05 -0400, Linda20071 wrote: > There is an example on ettus website that uses a single

Re: [Discuss-gnuradio] Changing delay block value over time

2018-05-25 Thread CEL
ns I need to calculate the slant > range over time. In order for me to get the propagation delay 2R/c. As a > result, I need to change the delays for 5 secs. > > Thank you in advanced! > > -Original Message----- > From: Müller, Marcus (CEL) [mailto:muel...@kit.edu] > Sent

<    1   2   3   4   5   6   7   8   9   10   >