Re: [Discuss-gnuradio] RTTY receiver
Yeah, char signedness is compiler-dependent (and can be configured with
-f[un]signed-char in GCC). Neither C nor C++ specify a "default"
signedness in the standard.
So, if you want to do arithmetic on chars, you need to specify which
data type you'd want – signed char or unsigned char.
That's what Kyeong's change does.
If it works without, it's by luck.
If you look into embedded software, you'll often find that C developers
prefer to use `int8_t` instead of `signed char` and `uint8_t` instead
of `unsigned char` if they're using these datatypes to (logically)
transport bytes of data or actually numbers, as opposed to dealing with
character data ("text" in the human sense, not the ld sense).
Here it's kind of a hybrid, so explicity saying you want unsigned char
is probably the most intuitive :)
Thanks for this discussion!
Best regards,
Marcus
On Mon, 2019-06-10 at 23:27 -0700, Cinaed Simson wrote:
> On 6/10/19 9:05 PM, Kyeong Su Shin wrote:
> > Hello Barry,
> >
> >
> > Apparantly, the module has portability issues (will build on x86
> > but
> > won't build on ARM) due to data type issues.
>
> It builds find on my ARM 64 Odroid running jessie. Maybe it just
> doesn't
> build on the raspberry pi 3. I'm running a slightly dated version of
> gnuradio - 3.7.12git-295-ga0adcd33.
>
> -- Cinaed
>
> To build the package, you
> > will have to edit lib/baudot_encode_bb_impl.h:
> >
> >
> > "static const char ascii_to_letters[128]" should become
> >
> >
> > "static const *signed* char ascii_to_letters[128]", and
> >
> >
> > "static const char ascii_to_figures[128]" should become
> >
> >
> > "static const *signed* char ascii_to_figures[128]".
> >
> >
> > That will allow the module to build, although you may have to make
> > further changes to get "Boudot Encode" block working correctly (I
> > didn't
> > test that; maybe I should make a pull request after that).
> >
> >
> > Regards,
> >
> > Kyeong Su Shin
> >
> >
> > -
> > ---
> > *보낸 사람:* ba...@dcsmail.net
> > *보낸 날짜:* 2019년 6월 11일 화요일 오전 2:56:02
> > *받는 사람:* Kyeong Su Shin
> > *참조:* discuss-gnuradio@gnu.org
> > *제목:* Re: [Discuss-gnuradio] RTTY receiver
> >
> > Thank you for your response. Since this is my first issue on
> > 'discuss-gnuradio', I am not sure how to get my reply to you posted
> > in
> > the thread. This looks like it might work. If not, please let me
> > know
> > what to do.
> >
> > I did the "sudo ldconfig" and it got rid of the "include could not
> > find
> > load file: GrPython", but not the other problem, so I decided to
> > start
> > from scratch.
> >
> > I have
> > Raspberry Pi 3 B+
> > Rasbian Linux (v2)
> >
> > I deleted the folder 'gr-radioteletype'
> > download zip from https://github.com/bitglue/gr-radioteletype
> >
> >
> > GitHub - bitglue/gr-radioteletype: GNU Radio blocks for RTTY and
> > PSK31
> >
> > github.com
> > GNU Radio blocks for RTTY and PSK31. Contribute to
> > bitglue/gr-radioteletype development by creating an account on
> > GitHub.
> >
> >
> > extract zip to /home/pi
> > cd ~/gr-radioteletype-master
> > mkdir build
> > cd build
> > cmake ../
> > make
> > [ 5%] Building CXX object
> > lib/CMakeFiles/gnuradio-
> > radioteletype.dir/async_word_extractor_bb_impl.cc.o
> > [ 10%] Building CXX object
> > lib/CMakeFiles/gnuradio-
> > radioteletype.dir/baudot_decode_bb_impl.cc.o
> > [ 15%] Building CXX object
> > lib/CMakeFiles/gnuradio-
> > radioteletype.dir/baudot_encode_bb_impl.cc.o
> > In file included from
> > /home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.cc:26:0:
> > /home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.h:65:5:
> > error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ inside { }
> > [-Wnarrowing]
> > };
> > ^
> > /home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.h:100:5:
> > error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ inside { }
> > [-Wnarrowing]
> > };
> > ^
> > /home/pi/gr-radioteletype-master/lib/baudot_encode_bb_impl.h:100:5:
> > error: narrowing conversion of ‘-1’ from ‘int’ to ‘char’ inside { }
> > [-Wnarrowing]
> > lib/CMakeFiles/gnuradio-radioteletype.dir/build.make:110: recipe
> > for
> > target
> > 'lib/CMakeFiles/gnuradio-
> > radioteletype.dir/baudot_encode_bb_impl.cc.o'
> > failed
> > make[2]: ***
> > [lib/CMakeFiles/gnuradio-
> > radioteletype.dir/baudot_encode_bb_impl.cc.o]
> > Error 1
> > CMakeFiles/Makefile2:137: recipe for target
> > 'lib/CMakeFiles/gnuradio-radioteletype.dir/all' failed
> > make[1]: *** [lib/CMakeFiles/gnuradio-radioteletype.dir/all] Error
> > 2
> > Makefile:138: recipe for target 'all' failed
> > make: *** [all] Error 2
> >
> > Both of the error messages were repeated *many* times. I looked at
> > the
> > code for baudot_encode_bb_impl.h, but could not see any problems
> > with
> > it.
> >
> > I appreciate any
Re: [Discuss-gnuradio] Store in a variable the output of the grinspector's blocks.
There's the function probes. Using that is almost always a sign of bad design; what do you want to achieve that way? Best regards, Marcus On Sun, 2019-06-09 at 19:23 -0500, Daniel Andres Palacios wrote: > > Hi everyone > it is there a way to get and store in a variable the output of gr- > inspector's blocks. > > -- > Daniel Andrés Palacios Carabalí > Student of Telemathics engineering > Icesi University- Cali, Colombia > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio smime.p7s Description: S/MIME cryptographic signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] RTTY receiver
Cinaed Simson wrote: It builds find on my ARM 64 Odroid running jessie. Maybe it just doesn't build on the raspberry pi 3. I'm running a slightly dated version of gnuradio - 3.7.12git-295-ga0adcd33. Just out of curiosity, I built using MSVC-2017. The only issue I found was the need to add a '#include ' in some place due to things like: if (bits_eaten >= bits_per_word and sample) Otherwise it links fine; not tested. -- --gv ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Store in a variable the output of the grinspector's blocks.
Hi. Thanks for your reply. The signal extractor block's output is a vector of tuples with center frequency an band width. I want to know the length of the vector without using the debug block. And store the data for further processing. On Tue, Jun 11, 2019, 02:22 Müller, Marcus (CEL) wrote: > There's the function probes. > > Using that is almost always a sign of bad design; what do you want to > achieve that way? > > Best regards, > Marcus > > On Sun, 2019-06-09 at 19:23 -0500, Daniel Andres Palacios wrote: > > > > Hi everyone > > it is there a way to get and store in a variable the output of gr- > > inspector's blocks. > > > > -- > > Daniel Andrés Palacios Carabalí > > Student of Telemathics engineering > > Icesi University- Cali, Colombia > > > > ___ > > 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
Re: [Discuss-gnuradio] Store in a variable the output of the grinspector's blocks.
But the debug block does exactly what you need: store the data and thus allow for analysis. Why don't you want to use it? Sounds like the right tool. On Tue, 2019-06-11 at 03:03 -0500, Daniel Andres Palacios wrote: > Hi. Thanks for your reply. > > The signal extractor block's output is a vector of tuples with center > frequency an band width. I want to know the length of the vector without > using the debug block. And store the data for further processing. > > On Tue, Jun 11, 2019, 02:22 Müller, Marcus (CEL) wrote: > > There's the function probes. > > > > Using that is almost always a sign of bad design; what do you want to > > achieve that way? > > > > Best regards, > > Marcus > > > > On Sun, 2019-06-09 at 19:23 -0500, Daniel Andres Palacios wrote: > > > > > > Hi everyone > > > it is there a way to get and store in a variable the output of gr- > > > inspector's blocks. > > > > > > -- > > > Daniel Andrés Palacios Carabalí > > > Student of Telemathics engineering > > > Icesi University- Cali, Colombia > > > > > > ___ > > > 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 smime.p7s Description: S/MIME cryptographic signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Output files in the VITA 49 format
Hi, I'm very new to gnu radio. I have gnu radio companion running in Ubuntu on a VM via VirtualBox. I'm using a USRPB200. I'm not understanding how I take the raw IQ data received by my USRP B200 and output it into a file that's in the VITA 49 format within gnu radio companion. There are some file sinks available within gnu radio companion, but they don't seem to be what I am looking for, or are they? Thanks! Sara ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] names to use for ubuntu package manager to get install GNURadio
2019-06-11 I have successfully installed GNURadio on my Windows 10 machine and also have a live usb thumb drive for two versions of ubuntu (18.04.2 and 19.04). I now wish to use the package manager for these ubuntu systems to apt get install GNURadio and companion. I do not know the names to use for the package nor how to find them out. Help would be appreciated. Please note that after I do that, I want to install (from his git repository) the Michael Ossmann add on for GNURadio to use HackRF One with GNURadio to follow his course. I have not had any success with getting a working version of Pentoo Linux to a Live USB Drive and/or getting Live SDR of GNURadio (which does contain the necessary blocks) but says in its wikipedea that it is "retired". i.e. not available. I presume that I will run into some problems with dependencies (but will gain experience) when I try to "compile" the material from his Git repository. Thank you ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] names to use for ubuntu package manager to get install GNURadio
Hi geraldfenkell - On modern Ubuntu, you should be able to just issue "sudo apt install gnuradio" and after some ado GNU Radio will be installed. See also < https://wiki.gnuradio.org/index.php/InstallingGR#Linux >. The HackRF software interface should be pretty easily installable on Ubuntu (or any other UNIX-y system), and then you can use a GR out-of-tree (OOT) such as "gr-osmosdr" to get a GR interface to your HackRF One. Hope this is useful & good luck! - MLD On Tue, Jun 11, 2019, at 10:05 AM, geraldfenkell wrote: > 2019-06-11 > > I have successfully installed GNURadio on my Windows 10 machine and also have > a live usb thumb drive for two > versions of ubuntu (18.04.2 and 19.04). I now wish to use the package manager > for these ubuntu systems to apt get install > GNURadio and companion. I do not know the names to use for the package nor > how to find them out. > > Help would be appreciated. > > Please note that after I do that, I want to install (from his git repository) > the Michael Ossmann add on > for GNURadio to use HackRF One with GNURadio to follow his course. I have not > had any success with > getting a working version of Pentoo Linux to a Live USB Drive and/or getting > Live SDR of GNURadio (which > does contain the necessary blocks) but says in its wikipedea that it is > "retired". i.e. not available. I presume > that I will run into some problems with dependencies (but will gain > experience) when I try to "compile" the > material from his Git repository. > > Thank you ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] names to use for ubuntu package manager to get install GNURadio
Hi, a full agreement from my side: especially when using Ubuntu 19.04, you get a pretty recent GNU Radio. If you want to talk to your hackRF, you need gr-osmosdr, too, so sudo apt install gnuradio gr-osmosdr and the thing is set up. Best regards, Marcus On Tue, 2019-06-11 at 10:18 -0400, Michael Dickens wrote: > Hi geraldfenkell - > > On modern Ubuntu, you should be able to just issue "sudo apt install > gnuradio" and after some ado GNU Radio will be installed. See also < > https://wiki.gnuradio.org/index.php/InstallingGR#Linuxux >. > > The HackRF software interface should be pretty easily installable on Ubuntu > (or any other UNIX-y system), and then you can use a GR out-of-tree (OOT) > such as "gr-osmosdr" to get a GR interface to your HackRF One. > > Hope this is useful & good luck! - MLD > > On Tue, Jun 11, 2019, at 10:05 AM, geraldfenkell wrote: > > 2019-06-11 > > > > I have successfully installed GNURadio on my Windows 10 machine and also > > have a live usb thumb drive for two > > versions of ubuntu (18.04.2 and 19.04). I now wish to use the package > > manager for these ubuntu systems to apt get install > > GNURadio and companion. I do not know the names to use for the package nor > > how to find them out. > > > > Help would be appreciated. > > > > Please note that after I do that, I want to install (from his git > > repository) the Michael Ossmann add on > > for GNURadio to use HackRF One with GNURadio to follow his course. I have > > not had any success with > > getting a working version of Pentoo Linux to a Live USB Drive and/or > > getting Live SDR of GNURadio (which > > does contain the necessary blocks) but says in its wikipedea that it is > > "retired". i.e. not available. I presume > > that I will run into some problems with dependencies (but will gain > > experience) when I try to "compile" the > > material from his Git repository. > > > > Thank you > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio smime.p7s Description: S/MIME cryptographic signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] OFDM
Hi Farid - I'll reply off list since this is pretty technical; we can summarize
back on list if appropriate. - MLD
On Sat, Jun 8, 2019, at 1:19 PM, farid mihoub wrote:
> Hello,
> I am trying to change the OFDM_tx_rx payload modulation by a custom 64kQAM,
> I implemented the block in several ways, it works fine but I had issues using
> it with OFDM_tx_rx:
> /*1- sync:
> taking a short item and produce a complex item
> modulation:
> **signatures:***
> 64kQAM_code_impl::64kQAM_code_impl( )
> : gr::sync_block("64kQAM_code",
> gr::io_signature::make(1, 1, sizeof(unsigned short int)),
> gr::io_signature::make(1, 1, sizeof(gr_complex)))
> {}
> **work function:***
> int
> 64kQAM_code_impl::work(int noutput_items,
> gr_vector_const_void_star &input_items,
> gr_vector_void_star &output_items)
> {
> const unsigned short int *in = (const unsigned short int *) input_items[0];
> gr_complex *out = (gr_complex *) output_items[0];
> for(int i = 0;i out[i].real((float(in[i]&0x00FF)-128.0)*level);
> out[i].imag((float((in[i]&0xFF00)>>8)-128.0)*level);
> }
> return noutput_items;
> }
> demodulation:
> taking a complex item and produce a short item
> **signature:***
> 64kQAM_decode_impl::64kQAM_decode_impl( )
> : gr::sync_block("64kQAM_decode",
> gr::io_signature::make(1, 1, sizeof(gr_complex)),
> gr::io_signature::make(1, 1, sizeof(unsigned short int)))
> {}
> **work function:***
> int
> 64kQAM_decode_impl::work(int noutput_items,
> gr_vector_const_void_star &input_items,
> gr_vector_void_star &output_items)
> {
> const gr_complex *in = (const gr_complex *) input_items[0];
> unsigned short int *out = (unsigned short int *) output_items[0];
> unsigned short int tmp;
> for(int i =0; i {
> tmp = int((in[i].imag()/level)+128.5);
> tmp = (tmp<<8) | int((in[i].real()/level)+128.5);
> out[i] = tmp;
> }
> return noutput_items;
> }
> Problem: -I got the write samples in the QT time sink, and in the
> file sink, but the transmission stops after some amount
> of data has been transmitted (repeat set to yes), the
> packet_len tag is displayed
>
> /*2- interpolator/decimator:***
> modulation:
> takes 2 bytes and produce one complex item
> demodulation:
> takes one complex item and produce 2 bytes.
> my decimaition and interpolation factor is 2
> Problems: same as 1.
>
> /**2-general:**
> modulation:
> taking two byte items and produce a complex item
> void
> 64kQAM_code_impl::forecast (int noutput_items, gr_vector_int
> &ninput_items_required)
> {
> ninput_items_required[0] = noutput_items*2;
> }
>
> int
> 64kQAM_code_impl::general_work (int noutput_items,
> gr_vector_int &ninput_items,
> gr_vector_const_void_star &input_items,
> gr_vector_void_star &output_items)
> {
> const unsigned char *in = (const unsigned char*) input_items[0];
> gr_complex *out = (gr_complex *) output_items[0];
>
> for(int i = 0;i {
> out[i].real(in[2*i]*level);
> out[i].imag(in[2*i+1]*level);
> }
> consume_each (noutput_items);
>
> // Tell runtime system how many output items we produced.
> return noutput_items;
> }
> demodulation:
> void
> 64kQAM_decode::forecast (int noutput_items, gr_vector_int
> &ninput_items_required)
> {
> ninput_items_required[0] = noutput_items/2;
> }
>
> int
> 64kQAM_decode_impl::general_work (int noutput_items,
> gr_vector_int &ninput_items,
> gr_vector_const_void_star &input_items,
> gr_vector_void_star &output_items)
> {
>
> const gr_complex *in = (const gr_complex *) input_items[0];
> unsigned char *out = (unsigned char *) output_items[0];
>
>
> for(int i =0; i {
> out[2*i]=in[i].real()/level;
> out[2*i+1] =in[i].imag()/level;
> }
> consume_each (noutput_items);
>
> // Tell runtime system how many output items we produced.
> return noutput_items*2;
> }
> taking a complex item and produce two byte items
>
> problem: -It writes quickly a large amount of data to the disk.
> -In the QT display I get the correct samples but in a sink file
> I got additionnal data generally this type (^@^@), also packet_len tag
> is not displayed on the QT time GUI.
>
> 4-trying with tagged stream block, tagged stream mux block gives an error : "
> Buffer too small for min_noutput_items"
>
> Thank you.
>
> ___
> 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
Re: [Discuss-gnuradio] Output files in the VITA 49 format
On 06/11/2019 09:22 AM, Sara Kim wrote: Hi, I'm very new to gnu radio. I have gnu radio companion running in Ubuntu on a VM via VirtualBox. I'm using a USRPB200. I'm not understanding how I take the raw IQ data received by my USRP B200 and output it into a file that's in the VITA 49 format within gnu radio companion. There are some file sinks available within gnu radio companion, but they don't seem to be what I am looking for, or are they? Thanks! Sara None of the file sinks product VITA-49 format, although there may be module "out there" that does that. I'm going to guess that very few people need VITA-49 as a file format, so it's never been added to core Gnu Radio functionality. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Output files in the VITA 49 format
Hi Sara, stock GNU Radio indeed doesn't include any VITA49 I/O capabilities. I'm not aware of any GNU Radio out-of-tree module that you could use to gain that. I know that Josh Blum wrote a VITA49 serializer for GREX, but that's not compatible with GNU Radio. It might serve you as inspiration for writing your own block, however: Since you only need to write very basic VITA49 packets, writing such a block should be no big deal – Josh simply pieces together the binary header manually in his grex/network/serializer.cpp; I find that aesthetically unpleasing, to be honest. (I hope Josh doesn't mind me saying that.) However, Eric Blossom, former GNU Radio maintainer of lore, has written https://github.com/eblossom/vita-49, which should be an easy to use C++ library. But really, a C struct with bit alignment specifiers would probably do for your limited use case. Upstream contributions more than welcome! Best regards, Marcus M On Tue, 2019-06-11 at 09:22 -0400, Sara Kim wrote: > Hi, > I'm very new to gnu radio. I have gnu radio companion running in Ubuntu on a > VM via VirtualBox. I'm using a USRPB200. I'm not understanding how I take the > raw IQ data received by my USRP B200 and output it into a file that's in the > VITA 49 format within gnu radio companion. There are some file sinks > available within gnu radio companion, but they don't seem to be what I am > looking for, or are they? > > Thanks! > Sara > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio smime.p7s Description: S/MIME cryptographic signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Gnuradio life cycle
Hello to everyone. Could somebody explain me what is the life cycle of a gnuradio program? I understand that all the action occurs in the constructor of the main class. Am I right? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Store in a variable the output of the grinspector's blocks.
Ok. Thank you. I managed to get the messages from the debug block. Now, I have to deal with types conversation. Thanks On Tue, Jun 11, 2019 at 7:59 AM Müller, Marcus (CEL) wrote: > But the debug block does exactly what you need: store the data and thus > allow for analysis. Why don't you want to use it? Sounds like the right > tool. > > > On Tue, 2019-06-11 at 03:03 -0500, Daniel Andres Palacios wrote: > > Hi. Thanks for your reply. > > > > The signal extractor block's output is a vector of tuples with center > frequency an band width. I want to know the length of the vector without > using the debug block. And store the data for further processing. > > > > On Tue, Jun 11, 2019, 02:22 Müller, Marcus (CEL) > wrote: > > > There's the function probes. > > > > > > Using that is almost always a sign of bad design; what do you want to > > > achieve that way? > > > > > > Best regards, > > > Marcus > > > > > > On Sun, 2019-06-09 at 19:23 -0500, Daniel Andres Palacios wrote: > > > > > > > > Hi everyone > > > > it is there a way to get and store in a variable the output of gr- > > > > inspector's blocks. > > > > > > > > -- > > > > Daniel Andrés Palacios Carabalí > > > > Student of Telemathics engineering > > > > Icesi University- Cali, Colombia > > > > > > > > ___ > > > > 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 > -- *Daniel Andrés Palacios Carabalí* *Student of Telemathics engineering* *Icesi University- Cali, Colombia* *===* *Estudiante de Ingeniería Telemática* *Universidad Icesi. - Cali, Colombia* ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Gnuradio life cycle
Hi Daniel, no, that's not right. In your program, whatever that is, if it wants to use GNU Radio: You set up a bunch of blocks – to even instantiate them, their constructors must return – and then tell the GNU Radio top_block to connect them. After you've done with that, you tell the top_block to run() or start() (and wait() until finished). That in turn allocates all the buffers between blocks, and then calls every block's start() method (most blocks you'll see don't even implement that) to make the block "ready". After that, the scheduler starts doing its thing, which is calling all the blocks' work() (or general_work()) methods, whenever there's new input for a block and/or enough output space. Maybe [1] helps a bit. Best regards, Marcus [1] https://www.gnuradio.org/blog/2017-01-05-buffers/ On Tue, 2019-06-11 at 12:30 -0500, Daniel Andres Palacios wrote: > Hello to everyone. > > Could somebody explain me what is the life cycle of a gnuradio program? I > understand that all the action occurs in the constructor of the main class. > Am I right? > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio smime.p7s Description: S/MIME cryptographic signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Live fm detection gr-inspector
Hi to everyone. What is the best way to receive all fm modifications. I'm usigin an B200 USRP. I think that putting the center frequency at 98M and a bandwidth of 20M is a good way,but I'm not getting a good result. The idea is to detect all fm center frequencies using gr-inspector ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Live fm detection gr-inspector
Hi Daniel, please remember to be specific when asking a question: "best way" is a bit ambiguous, and "I'm not getting a good result" definitely is insufficient for us to help you make things work better. What doesn't work sufficiently well? What happens instead? Best regards, Marcus On Tue, 2019-06-11 at 12:36 -0500, Daniel Andres Palacios wrote: > Hi to everyone. > > What is the best way to receive all fm modifications. I'm usigin an B200 USRP. > I think that putting the center frequency at 98M and a bandwidth of 20M is a > good way,but I'm not getting a good result. > > The idea is to detect all fm center frequencies using gr-inspector > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio smime.p7s Description: S/MIME cryptographic signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] USRP source gain vs osmocom source gain?
Hey all, I'm trying to turn the wifi receiver flowgraph in this repo ( https://github.com/bastibl/gr-ieee802-11/blob/maint-3.8/examples/wifi_rx.grc) into one that will work with the HackRF. The example uses a USRP source, with a normalized gain of .75. I'm not sure how to translate that into parameters for the osmocom source, which has 3 gain options: RF gain, IF gain, and BB gain, all in dB. I tried setting the RF gain = 20log(.75) = -2.49877, but that just resulted in mangled packets. Any suggestions? -- Eamon Heaney *Fleet Commander* *President, Model UN at Virginia Tech* ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP source gain vs osmocom source gain?
On 6/11/19 3:33 PM, Eamon Heaney wrote: > Hey all, > > I'm trying to turn the wifi receiver flowgraph in this repo > (https://github.com/bastibl/gr-ieee802-11/blob/maint-3.8/examples/wifi_rx.grc) > into one that will work with the HackRF. > > The example uses a USRP source, with a normalized gain of .75. I'm not > sure how to translate that into parameters for the osmocom source, which > has 3 gain options: RF gain, IF gain, and BB gain, all in dB. RF gain=0, IF gain=32, and BB gain=32. These are general purpose settings, i.e., don't use the RF gain unless you absolutely have to - and you're certain there isn't a strong radio source nearby. Type hackrf_transfer --help for the gain ranges and the step sizes. -- Cinaed > > I tried setting the RF gain = 20log(.75) = -2.49877, but that just > resulted in mangled packets. > > Any suggestions? > > -- > Eamon Heaney > / > /Fleet Commander/ > // > /President, Model UN at Virginia Tech/ > / > > ___ > 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
