Re: [Discuss-gnuradio] ofdm_sync and ofdm_sampler blocks
Hi, Martin Thanks. I will move to the new blocks. But if someone have encountered this kind of problem please let me know. Regards, - Monika On Wed, Apr 27, 2016 at 9:58 PM, Martin Braun wrote: > Monika, > > please be patient on this list. Also, the blocks you mention are very > old and not actively developed/maintained. I recommend switching to the > ofdm_tx and ofdm_rx blocks. > > Cheers, > Martin > > On 04/27/2016 04:09 AM, monika bansal wrote: > > Please help me with this. > > > > Thanks. > > > > Regards, > > -monika > > > > On Wed, Apr 27, 2016 at 4:37 PM, monika bansal > <mailto:monika19...@gmail.com>> wrote: > > > > Hi, > > > > I have connected benchmark_tx.py and benchmark_rx.py to make it > > loopback mode without USRPs. There is no channel block between the > > tx and rx chain. > > > > I checked all blocks in the Transmit chain. All are working as > > expected. But in Receiver chain i did not understand the output of > > /ofdm_sync_ml /and /digital.ofdm_sampler / blocks. > > > > I tried checking the output of port 1 of ofdm_sync. The sync signal > > is one on the following indexes: > > * 714, 7109, 13515, 19911, 26308, 32705, 39115, 45515,* > > *51910, 58315, 64715, 71115, 77515, 83915, 90315, > 96712,* > > * 103115, 109512, 115910, 122315, 128715, 135113, 141510, > 147915,* > > * 154288, 160711, 167112, 173515, 179912, 186315* > > * > > * > > I checked the output of port 1 of ofdm_sampler. The sync signal is > > one on the following indexes: > > *0, 5120, 10752, 15872, 20992, 26112, 31744, 36864,* > > *41984, 47616, 52736, 57856, 62976, 68096, 73216, > 78336,* > > *83968, 89088, 94208, 99840, 104960, 110080, 115200, > 120832,* > > * 125952, 131584, 136704, 142336, 147456, 153088* > > * > > * > > *I expected the output of *port 1 of ofdm_sync to be 639, 639+6400, > > 639+12800 , ... > > and output of port 1 of ofdm_sampler to be 0, 5120, 5120*2, 5120*3, > > > > > > General parameters are as follows: > > fft_len = 512 > > cp_len = 128 > > occupied_tones = 200 > > modulation = bpsk > > pkt_size = 200 bytes > > after CRC and Header pkt_length = 209 bytes > > 1 sync word for each packet > > > > Finally there will be 10 OFDM symbols per pkt and 512+128 = 640 > > complex symbols per OFDM symbol. > > > > > > > > > > ___ > > 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 mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] ofdm_sync and ofdm_sampler blocks
Please help me with this. Thanks. Regards, -monika On Wed, Apr 27, 2016 at 4:37 PM, monika bansal wrote: > Hi, > > I have connected benchmark_tx.py and benchmark_rx.py to make it loopback > mode without USRPs. There is no channel block between the tx and rx chain. > > I checked all blocks in the Transmit chain. All are working as expected. > But in Receiver chain i did not understand the output of *ofdm_sync_ml *and > *digital.ofdm_sampler * blocks. > > I tried checking the output of port 1 of ofdm_sync. The sync signal is one > on the following indexes: > * 714, 7109, 13515, 19911, 26308, 32705, 39115, 45515,* > *51910, 58315, 64715, 71115, 77515, 83915, 90315, 96712,* > * 103115, 109512, 115910, 122315, 128715, 135113, 141510, 147915,* > * 154288, 160711, 167112, 173515, 179912, 186315* > > I checked the output of port 1 of ofdm_sampler. The sync signal is one on > the following indexes: > *0, 5120, 10752, 15872, 20992, 26112, 31744, 36864,* > *41984, 47616, 52736, 57856, 62976, 68096, 73216, 78336,* > *83968, 89088, 94208, 99840, 104960, 110080, 115200, 120832,* > * 125952, 131584, 136704, 142336, 147456, 153088* > > *I expected the output of *port 1 of ofdm_sync to be 639, 639+6400, > 639+12800 , ... > and output of port 1 of ofdm_sampler to be 0, 5120, 5120*2, 5120*3, > > General parameters are as follows: > fft_len = 512 > cp_len = 128 > occupied_tones = 200 > modulation = bpsk > pkt_size = 200 bytes > after CRC and Header pkt_length = 209 bytes > 1 sync word for each packet > > Finally there will be 10 OFDM symbols per pkt and 512+128 = 640 complex > symbols per OFDM symbol. > > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] ofdm_sync and ofdm_sampler blocks
Hi, I have connected benchmark_tx.py and benchmark_rx.py to make it loopback mode without USRPs. There is no channel block between the tx and rx chain. I checked all blocks in the Transmit chain. All are working as expected. But in Receiver chain i did not understand the output of *ofdm_sync_ml *and *digital.ofdm_sampler * blocks. I tried checking the output of port 1 of ofdm_sync. The sync signal is one on the following indexes: * 714, 7109, 13515, 19911, 26308, 32705, 39115, 45515,* *51910, 58315, 64715, 71115, 77515, 83915, 90315, 96712,* * 103115, 109512, 115910, 122315, 128715, 135113, 141510, 147915,* * 154288, 160711, 167112, 173515, 179912, 186315* I checked the output of port 1 of ofdm_sampler. The sync signal is one on the following indexes: *0, 5120, 10752, 15872, 20992, 26112, 31744, 36864,* *41984, 47616, 52736, 57856, 62976, 68096, 73216, 78336,* *83968, 89088, 94208, 99840, 104960, 110080, 115200, 120832,* * 125952, 131584, 136704, 142336, 147456, 153088* *I expected the output of *port 1 of ofdm_sync to be 639, 639+6400, 639+12800 , ... and output of port 1 of ofdm_sampler to be 0, 5120, 5120*2, 5120*3, General parameters are as follows: fft_len = 512 cp_len = 128 occupied_tones = 200 modulation = bpsk pkt_size = 200 bytes after CRC and Header pkt_length = 209 bytes 1 sync word for each packet Finally there will be 10 OFDM symbols per pkt and 512+128 = 640 complex symbols per OFDM symbol. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Overflow error in benchmark receiver side "DDDD"
Hi Marcus, Exact model is RTL8111/8168/8411 and vendor is Realtek Semiconductor Co., ltd. OS: Ubuntu 14.04 Regards, Monika On Sat, Apr 16, 2016 at 10:27 PM, Marcus Müller wrote: > Hm, those are usually good. What's the exact model ("lspci" will tell)? > What's your OS? > > > > On 16.04.2016 18:10, monika bansal wrote: > > Hi Marcus > > The network card is PCI Express Gigabit Ethernet Controller with 1Gbps > capacity. > > Thanks, > Monika > > On Fri, Apr 15, 2016 at 6:38 PM, Marcus Müller > wrote: > >> No harm done :) So the point is that is still pretty bad, and >> usually shouldn't happen, unless your PC is *much* too slow, and usually >> would be preceeded by a couple of "O". >> There's two cases where this doesn't happen: >> * Too small network buffers >> * strangely misbehaving network hardware. >> >> So: what is your network card? >> >> Best regards, >> Marcus >> >> >> On 15.04.2016 14:32, monika bansal wrote: >> >> Yes my mistake :). Sorry for that. I just did not think of the python >> block at that time and then after i realized. >> >> Regards, >> Monika >> >> On Fri, Apr 15, 2016 at 5:17 PM, Marcus Müller < >> marcus.muel...@ettus.com> wrote: >> >>> Monika, >>> >>> no offense, but when you report a problem with software, it's pretty >>> crucial you point out whether you've modified the software or not :) >>> >>> Best regards, >>> Marcus >>> >>> >>> On 15.04.2016 06:28, monika bansal wrote: >>> >>> Hii, >>> >>> Thank you for your help. >>> That "" issue is not coming with original benchmark files. >>> I added one python block in between the chain in benchmark code. I think >>> due to which it was not fast enough to process the incoming data resulting >>> "" issue. >>> >>> Regards, >>> Monika >>> >>> On Tue, Apr 5, 2016 at 11:51 PM, < mle...@ripnet.com> >>> wrote: >>> >>>> What if you make the file "/dev/null" -- does this still happen? >>>> >>>> >>>> >>>> >>>> >>>> >>>> On 2016-04-05 14:12, monika bansal wrote: >>>> >>>> Hii, >>>> >>>> I am running benchmark code and on the receiver side after receiving >>>> some number of packets(8000 so), it starts showing overflow errors ("") >>>> on terminal. >>>> Following is the system configuration >>>> >>>> python benchmark_rx.py -f 1100M --args "addr=10.32.38.163" >>>> --to-file=/home/ashokbandi/GNU/a_rx.txt --bandwidth=50 >>>> >>>> Decreasing the bandwidth delays the error. >>>> >>>> I tried changing buffer size by setting net.core.rmem_max and >>>> net.core.wmem_max to 33445532 but to no avail. >>>> >>>> >>>> Following is the screen shot of terminal >>>> >>>> DDok: True pktno: 24116 n_rcvd: 9730 n_right: 9723 >>>> ok: True pktno: 24182 n_rcvd: 9731 n_right: 9724 >>>> DDok: True pktno: 24319 n_rcvd: 9732 >>>> n_right: 9725 >>>> ok: True pktno: 24442 n_rcvd: 9733 >>>> n_right: 9726 >>>> DDDok: True pktno: 24477 n_rcvd: 9734 n_right: 9727 >>>> Dok: True pktno: 24568 n_rcvd: 9735 n_right: 9728 >>>> Dok: >>>> False pktno: 22729 n_rcvd: 9736 n_right: 9728 >>>> >>>> >>>> Thanks >>>> >>>> ___ >>>> Discuss-gnuradio mailing >>>> listDiscuss-gnuradio@gnu.orghttps://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] Overflow error in benchmark receiver side "DDDD"
Hi Marcus The network card is PCI Express Gigabit Ethernet Controller with 1Gbps capacity. Thanks, Monika On Fri, Apr 15, 2016 at 6:38 PM, Marcus Müller wrote: > No harm done :) So the point is that is still pretty bad, and usually > shouldn't happen, unless your PC is *much* too slow, and usually would be > preceeded by a couple of "O". > There's two cases where this doesn't happen: > * Too small network buffers > * strangely misbehaving network hardware. > > So: what is your network card? > > Best regards, > Marcus > > > On 15.04.2016 14:32, monika bansal wrote: > > Yes my mistake :). Sorry for that. I just did not think of the python > block at that time and then after i realized. > > Regards, > Monika > > On Fri, Apr 15, 2016 at 5:17 PM, Marcus Müller > wrote: > >> Monika, >> >> no offense, but when you report a problem with software, it's pretty >> crucial you point out whether you've modified the software or not :) >> >> Best regards, >> Marcus >> >> >> On 15.04.2016 06:28, monika bansal wrote: >> >> Hii, >> >> Thank you for your help. >> That "" issue is not coming with original benchmark files. >> I added one python block in between the chain in benchmark code. I think >> due to which it was not fast enough to process the incoming data resulting >> "" issue. >> >> Regards, >> Monika >> >> On Tue, Apr 5, 2016 at 11:51 PM, < mle...@ripnet.com> >> wrote: >> >>> What if you make the file "/dev/null" -- does this still happen? >>> >>> >>> >>> >>> >>> >>> On 2016-04-05 14:12, monika bansal wrote: >>> >>> Hii, >>> >>> I am running benchmark code and on the receiver side after receiving >>> some number of packets(8000 so), it starts showing overflow errors ("") >>> on terminal. >>> Following is the system configuration >>> >>> python benchmark_rx.py -f 1100M --args "addr=10.32.38.163" >>> --to-file=/home/ashokbandi/GNU/a_rx.txt --bandwidth=50 >>> >>> Decreasing the bandwidth delays the error. >>> >>> I tried changing buffer size by setting net.core.rmem_max and >>> net.core.wmem_max to 33445532 but to no avail. >>> >>> >>> Following is the screen shot of terminal >>> >>> DDok: True pktno: 24116 n_rcvd: 9730 n_right: 9723 >>> ok: True pktno: 24182 n_rcvd: 9731 n_right: 9724 >>> DDok: True pktno: 24319 n_rcvd: 9732 n_right: >>> 9725 >>> ok: True pktno: 24442 n_rcvd: 9733 >>> n_right: 9726 >>> DDDok: True pktno: 24477 n_rcvd: 9734 n_right: 9727 >>> Dok: True pktno: 24568 n_rcvd: 9735 n_right: 9728 >>> Dok: >>> False pktno: 22729 n_rcvd: 9736 n_right: 9728 >>> >>> >>> Thanks >>> >>> ___ >>> Discuss-gnuradio mailing >>> listDiscuss-gnuradio@gnu.orghttps://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] Overflow error in benchmark receiver side "DDDD"
Yes my mistake :). Sorry for that. I just did not think of the python block at that time and then after i realized. Regards, Monika On Fri, Apr 15, 2016 at 5:17 PM, Marcus Müller wrote: > Monika, > > no offense, but when you report a problem with software, it's pretty > crucial you point out whether you've modified the software or not :) > > Best regards, > Marcus > > > On 15.04.2016 06:28, monika bansal wrote: > > Hii, > > Thank you for your help. > That "" issue is not coming with original benchmark files. > I added one python block in between the chain in benchmark code. I think > due to which it was not fast enough to process the incoming data resulting > "" issue. > > Regards, > Monika > > On Tue, Apr 5, 2016 at 11:51 PM, wrote: > >> What if you make the file "/dev/null" -- does this still happen? >> >> >> >> >> >> >> On 2016-04-05 14:12, monika bansal wrote: >> >> Hii, >> >> I am running benchmark code and on the receiver side after receiving some >> number of packets(8000 so), it starts showing overflow errors ("") on >> terminal. >> Following is the system configuration >> >> python benchmark_rx.py -f 1100M --args "addr=10.32.38.163" >> --to-file=/home/ashokbandi/GNU/a_rx.txt --bandwidth=50 >> >> Decreasing the bandwidth delays the error. >> >> I tried changing buffer size by setting net.core.rmem_max and >> net.core.wmem_max to 33445532 but to no avail. >> >> >> Following is the screen shot of terminal >> >> DDok: True pktno: 24116 n_rcvd: 9730 n_right: 9723 >> ok: True pktno: 24182 n_rcvd: 9731 n_right: 9724 >> DDok: True pktno: 24319 n_rcvd: 9732 n_right: >> 9725 >> ok: True pktno: 24442 n_rcvd: 9733 >> n_right: 9726 >> DDDok: True pktno: 24477 n_rcvd: 9734 n_right: 9727 >> Dok: True pktno: 24568 n_rcvd: 9735 n_right: 9728 >> Dok: >> False pktno: 22729 n_rcvd: 9736 n_right: 9728 >> >> >> Thanks >> >> ___ >> Discuss-gnuradio mailing >> listDiscuss-gnuradio@gnu.orghttps://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] Overflow error in benchmark receiver side "DDDD"
Hii, Thank you for your help. That "" issue is not coming with original benchmark files. I added one python block in between the chain in benchmark code. I think due to which it was not fast enough to process the incoming data resulting "" issue. Regards, Monika On Tue, Apr 5, 2016 at 11:51 PM, wrote: > What if you make the file "/dev/null" -- does this still happen? > > > > > > > On 2016-04-05 14:12, monika bansal wrote: > > Hii, > > I am running benchmark code and on the receiver side after receiving some > number of packets(8000 so), it starts showing overflow errors ("") on > terminal. > Following is the system configuration > > python benchmark_rx.py -f 1100M --args "addr=10.32.38.163" > --to-file=/home/ashokbandi/GNU/a_rx.txt --bandwidth=50 > > Decreasing the bandwidth delays the error. > > I tried changing buffer size by setting net.core.rmem_max and > net.core.wmem_max to 33445532 but to no avail. > > > Following is the screen shot of terminal > > DDok: True pktno: 24116 n_rcvd: 9730 n_right: 9723 > ok: True pktno: 24182 n_rcvd: 9731 n_right: 9724 > DDok: True pktno: 24319 n_rcvd: 9732 n_right: > 9725 > ok: True pktno: 24442 n_rcvd: 9733 n_right: > 9726 > DDDok: True pktno: 24477 n_rcvd: 9734 n_right: 9727 > Dok: True pktno: 24568 n_rcvd: 9735 n_right: 9728 > Dok: > False pktno: 22729 n_rcvd: 9736 n_right: 9728 > > > Thanks > > ___ > Discuss-gnuradio mailing > listDiscuss-gnuradio@gnu.orghttps://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] Overflow error in benchmark receiver side "DDDD"
Hii, I am running benchmark code and on the receiver side after receiving some number of packets(8000 so), it starts showing overflow errors ("") on terminal. Following is the system configuration python benchmark_rx.py -f 1100M --args "addr=10.32.38.163" --to-file=/home/ashokbandi/GNU/a_rx.txt --bandwidth=50 Decreasing the bandwidth delays the error. I tried changing buffer size by setting net.core.rmem_max and net.core.wmem_max to 33445532 but to no avail. Following is the screen shot of terminal DDok: True pktno: 24116 n_rcvd: 9730 n_right: 9723 ok: True pktno: 24182 n_rcvd: 9731 n_right: 9724 DDok: True pktno: 24319 n_rcvd: 9732 n_right: 9725 ok: True pktno: 24442 n_rcvd: 9733 n_right: 9726 DDDok: True pktno: 24477 n_rcvd: 9734 n_right: 9727 Dok: True pktno: 24568 n_rcvd: 9735 n_right: 9728 Dok: False pktno: 22729 n_rcvd: 9736 n_right: 9728 Thanks ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] About decoding qpsk symbol
Hi Martin, I am thinking of doing equalization and estimation in a single python code. For this i think, i may need to translate *ofdm_frame_equalizer_vcvc *block also in Python. But it would also be nice if i can use ofdm_frame_equalizer_vcvc block in conjunction with the Python-based equalizer. For now i am stuck at how to write *d_constellation->map_to_points(d_constellation->decision_maker(&sym_eq),** &sym_est); *in a python code for equalizer. Thanks. Regards, Monika On Fri, Jan 8, 2016 at 11:38 AM, Martin Braun wrote: > The tricky part would be to feed the Python back to C++ land, which is > necessary if you want to still use the ofdm_frame_equalizer_vcvc block > in conjunction with your Python-based equalizer. Is that something > you're trying to do? > > Cheers, > Martin > > > On 01/07/2016 02:08 PM, monika bansal wrote: > > Hi Marcus, > > > > I am trying to write the equivalent python code for the > > *ofdm_equalizer_simpledfe.cc *and *ofdm_chanest_vcvc_impl.cc* in a > > single python file. I have written the python code for > > *ofdm_chanest_vcvc_impl.cc *successfully. I am able to write the python > > code for *ofdm_equalizer_simpledfe.cc *except for the > > line > *d_constellation->map_to_points(d_constellation->decision_maker(&sym_eq), > > &sym_est);. > > > > * > > My question is, how can i convert this line from c++ to python ? Is > > there any python code to decode the constellation? What should i do? > > > > I am attaching the code written so far. > > Thanks. > > > > Regards, > > Monika > > > > > > > > > > > > > > > > > > > > On Wed, Dec 23, 2015 at 10:46 AM, monika bansal > <mailto:monika19...@gmail.com>> wrote: > > > > > > -- Forwarded message -- > > From: *Marcus Müller* > <mailto:marcus.muel...@ettus.com>> > > Date: Tue, Dec 22, 2015 at 8:30 PM > > Subject: Re: [Discuss-gnuradio] About decoding qpsk symbol > > To: monika bansal monika19...@gmail.com>> > > Cc: discuss-gnuradio@gnu.org <mailto:discuss-gnuradio@gnu.org> > > > > > > To ask this more explcitely: > > What *exactly* are you doing to produce the error? > > We will need your code to understand what goes wrong. > > > > > > On 22.12.2015 15:59, monika bansal wrote: > >> Hi Marcus, > >> I am creating a channel equalization block in python, trying some > >> different algorithms, and inside it I need to decode the modulated > >> symbols(mapped using qpsk). So I am looking for a python module, > >> which can be called inside the work function of my block, that can > >> do this. > >> > >> Thanks > >> > >> > >> > >> > >> On Tue, Dec 22, 2015 at 2:55 PM, Marcus Müller > >> mailto:marcus.muel...@ettus.com>> wrote: > >> > >> How are you including qpsk.py <http://qpsk.py>? > >> This does sound like your PYTHONPATH isn't set correctly, but > >> I'd assume Python stumbles over that before you can even > >> import qpsk.py <http://qpsk.py> > >> > >> Generally, for this kind of problem, a little background, > >> maybe at least a code excerpt and a higher level view on what > >> you're trying to do from the start would be very helpful. > >> > >> Best regards, > >> Marcus > >> > >> > >> Am 22. Dezember 2015 05:56:46 MEZ, schrieb monika bansal > >> <<mailto:monika19...@gmail.com>monika19...@gmail.com > >> <mailto:monika19...@gmail.com>>: > >> > >> Hii marcus, > >> > >> I am trying to decode the symbols and use the decoded > >> symbols for further processing in the same python written > >> module. I am not able to call the "constellation" related > >> functions. > >> How can i use them ? or is there any "decoder" written in > >> python ? > >> > >> Thanks !! > >> > >> > >> > >> On Tue, Dec 22, 2015 at 3:48 AM, Marcus Müller > >> <<mailto:marcus.muel...@ettus.com>marcus.muel...@ettus.com > >> <mailto:marcus.muel...@ettus.com>> wrote: > >
Re: [Discuss-gnuradio] About decoding qpsk symbol
Hi Marcus, I am trying to write the equivalent python code for the *ofdm_equalizer_simpledfe.cc *and *ofdm_chanest_vcvc_impl.cc* in a single python file. I have written the python code for *ofdm_chanest_vcvc_impl.cc *successfully. I am able to write the python code for *ofdm_equalizer_simpledfe.cc *except for the line * d_constellation->map_to_points(d_constellation->decision_maker(&sym_eq), &sym_est);.* My question is, how can i convert this line from c++ to python ? Is there any python code to decode the constellation? What should i do? I am attaching the code written so far. Thanks. Regards, Monika On Wed, Dec 23, 2015 at 10:46 AM, monika bansal wrote: > > -- Forwarded message -- > From: Marcus Müller > Date: Tue, Dec 22, 2015 at 8:30 PM > Subject: Re: [Discuss-gnuradio] About decoding qpsk symbol > To: monika bansal > Cc: discuss-gnuradio@gnu.org > > > To ask this more explcitely: > What *exactly* are you doing to produce the error? > We will need your code to understand what goes wrong. > > > On 22.12.2015 15:59, monika bansal wrote: > > Hi Marcus, > I am creating a channel equalization block in python, trying some > different algorithms, and inside it I need to decode the modulated > symbols(mapped using qpsk). So I am looking for a python module, which can > be called inside the work function of my block, that can do this. > > Thanks > > > > > On Tue, Dec 22, 2015 at 2:55 PM, Marcus Müller > wrote: > >> How are you including qpsk.py? >> This does sound like your PYTHONPATH isn't set correctly, but I'd assume >> Python stumbles over that before you can even import qpsk.py >> >> Generally, for this kind of problem, a little background, maybe at least >> a code excerpt and a higher level view on what you're trying to do from the >> start would be very helpful. >> >> Best regards, >> Marcus >> >> >> Am 22. Dezember 2015 05:56:46 MEZ, schrieb monika bansal < >> monika19...@gmail.com>: >>> >>> Hii marcus, >>> >>> I am trying to decode the symbols and use the decoded symbols for >>> further processing in the same python written module. I am not able to call >>> the "constellation" related functions. >>> How can i use them ? or is there any "decoder" written in python ? >>> >>> Thanks !! >>> >>> >>> >>> On Tue, Dec 22, 2015 at 3:48 AM, Marcus Müller < >>> marcus.muel...@ettus.com> wrote: >>> >>>> qpsk.py can't be run. >>>> It's just a python module containing functionality for QPSK, but no >>>> "main" function or similar. >>>> >>>> What are you actually trying to do? >>>> >>>> Best regards, >>>> Marcus >>>> >>>> >>>> On 21.12.2015 21:09, monika bansal wrote: >>>> >>>> Hii, >>>> >>>> I am trying to decode qpsk symbols for channel estimation block in >>>> python but there is error in importing digital_swig. >>>> This also happens when i run "qpsk.py" as shown below: >>>> >>>> *Traceback (most recent call last):* >>>> * File "qpsk.py", line 32, in * >>>> *import digital_swig as digital* >>>> *ImportError: No module named digital_swig* >>>> >>>> Is there some other way or what should i do ? >>>> >>>> >>>> >>>> >>>> ___ >>>> Discuss-gnuradio mailing >>>> listDiscuss-gnuradio@gnu.orghttps://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 mailing >>> listDiscuss-gnuradio@gnu.orghttps://lists.gnu.org/mailman/listinfo/discuss-gnuradio >>> >>> -- Sent from my Android device with K-9 Mail. Please excuse my brevity. >> > > import numpy as np from gnuradio import gr import pmt class ls_channel_estimation(gr.basic_block): """ docstring for block multiply_py_ff """ def __init__(self,sync_symbol1,sync_symbol2,n_data_symbols,max_carr_offset,force_one_sync_symbol,cp_le
Re: [Discuss-gnuradio] About decoding qpsk symbol
Hi Marcus, I am creating a channel equalization block in python, trying some different algorithms, and inside it I need to decode the modulated symbols(mapped using qpsk). So I am looking for a python module, which can be called inside the work function of my block, that can do this. Thanks On Tue, Dec 22, 2015 at 2:55 PM, Marcus Müller wrote: > How are you including qpsk.py? > This does sound like your PYTHONPATH isn't set correctly, but I'd assume > Python stumbles over that before you can even import qpsk.py > > Generally, for this kind of problem, a little background, maybe at least a > code excerpt and a higher level view on what you're trying to do from the > start would be very helpful. > > Best regards, > Marcus > > > Am 22. Dezember 2015 05:56:46 MEZ, schrieb monika bansal < > monika19...@gmail.com>: >> >> Hii marcus, >> >> I am trying to decode the symbols and use the decoded symbols for >> further processing in the same python written module. I am not able to call >> the "constellation" related functions. >> How can i use them ? or is there any "decoder" written in python ? >> >> Thanks !! >> >> >> >> On Tue, Dec 22, 2015 at 3:48 AM, Marcus Müller >> wrote: >> >>> qpsk.py can't be run. >>> It's just a python module containing functionality for QPSK, but no >>> "main" function or similar. >>> >>> What are you actually trying to do? >>> >>> Best regards, >>> Marcus >>> >>> >>> On 21.12.2015 21:09, monika bansal wrote: >>> >>> Hii, >>> >>> I am trying to decode qpsk symbols for channel estimation block in >>> python but there is error in importing digital_swig. >>> This also happens when i run "qpsk.py" as shown below: >>> >>> *Traceback (most recent call last):* >>> * File "qpsk.py", line 32, in * >>> *import digital_swig as digital* >>> *ImportError: No module named digital_swig* >>> >>> Is there some other way or what should i do ? >>> >>> >>> >>> >>> ___ >>> Discuss-gnuradio mailing >>> listDiscuss-gnuradio@gnu.orghttps://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 mailing list >> Discuss-gnuradio@gnu.org >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> >> > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] About decoding qpsk symbol
Hii marcus, I am trying to decode the symbols and use the decoded symbols for further processing in the same python written module. I am not able to call the "constellation" related functions. How can i use them ? or is there any "decoder" written in python ? Thanks !! On Tue, Dec 22, 2015 at 3:48 AM, Marcus Müller wrote: > qpsk.py can't be run. > It's just a python module containing functionality for QPSK, but no "main" > function or similar. > > What are you actually trying to do? > > Best regards, > Marcus > > > On 21.12.2015 21:09, monika bansal wrote: > > Hii, > > I am trying to decode qpsk symbols for channel estimation block in python > but there is error in importing digital_swig. > This also happens when i run "qpsk.py" as shown below: > > *Traceback (most recent call last):* > * File "qpsk.py", line 32, in * > *import digital_swig as digital* > *ImportError: No module named digital_swig* > > Is there some other way or what should i do ? > > > > > ___ > Discuss-gnuradio mailing > listDiscuss-gnuradio@gnu.orghttps://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 mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] About decoding qpsk symbol
Hii, I am trying to decode qpsk symbols for channel estimation block in python but there is error in importing digital_swig. This also happens when i run "qpsk.py" as shown below: *Traceback (most recent call last):* * File "qpsk.py", line 32, in * *import digital_swig as digital* *ImportError: No module named digital_swig* Is there some other way or what should i do ? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] undefined symbol error
Thank you for the reply... flat_fader_impl.h file is in lib I am not getting where i did mistake. Thanks again for your time. On Thu, Oct 15, 2015 at 3:35 PM, Gisle Vanem wrote: > when i am running QA test for a new module named "channels_w_tags" there >> is this error >> *undefined symbol: _ZN2gr15channels_w_tags15flat_fader_implC1Ejfbfi* >> > > cp-demangle.exe _ZN2gr15channels_w_tags15flat_fader_implC1Ejfbfi reports: > > gr::channels_w_tags::flat_fader_impl::flat_fader_impl(unsigned, float, > bool, float, int) > > Does that give you a clue? Look in any .map-file to see if it's > imported. If not, add the needed lib. > > I don't find any 'channels_w_tags' symbol here, so it's your call. > > -- > --gv > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] undefined symbol error
hii when i am running QA test for a new module named "channels_w_tags" there is this error *undefined symbol: _ZN2gr15channels_w_tags15flat_fader_implC1Ejfbfi* Please let me know what should i do. I am not able to find the answer. Thanks. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] How to know the true channel response.
Hii Should i add tag in the Channel model block to know the channel Taps as it done in the "ofdm channel estimation" block to convey the channel information or there is some other way of knowing these taps. Regards Monika On Sat, Oct 3, 2015 at 5:03 PM, monika bansal wrote: > Hii > > I want to compute Mean Square Error(MSE) between the true channel and the > estimated one. > > How can i get the true channel from the channel blocks such as from > "selective fading channel model" ? > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] How to know the true channel response.
Hii I want to compute Mean Square Error(MSE) between the true channel and the estimated one. How can i get the true channel from the channel blocks such as from "selective fading channel model" ? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] AttributeError: 'module' object has no attribute 'ofdm_chanest_MMSE_vcvc'
Hii I have added a new block and it is available in the block list of gnuradio. I am using it in the flow graph. When i run it, it shows the error : *self.Channel_Estimation_ofdm_chanest_MMSE_vcvc_0 = Channel_Estimation.ofdm_chanest_MMSE_vcvc((sync_word1), (sync_word2), 8, 0, -1, False, 0.1)* *AttributeError: 'module' object has no attribute 'ofdm_chanest_MMSE_vcvc'* ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] No tests were found!!!
* Thanks Marcus ... On Tue, Sep 15, 2015 at 2:24 PM, monika bansal wrote: > Thanks Martin for the nice explanation... > > On Tue, Sep 15, 2015 at 1:59 PM, Marcus Müller > wrote: > >> Hi Monika, >> >> man >> >> often gives instructions on how to use a program. >> >> man ctest >> >> yields something like the following: >> >>-R , --tests-regex >> Run tests matching regular expression. >> >> This option tells ctest to run only the tests whose names >> match the given regular expression. >> >> >> now, you ran "ctest -V -R square"; ctest only ran the tests that have >> "square" in their name (as you explicitly asked it to), and since there >> were no tests with square in their name, none could be run. >> >> Best regards, >> Marcus >> >> >> On 15.09.2015 10:19, monika bansal wrote: >> >> Hi Martin, >> I run *ctest -V -R qa_ofdm_chanest_MMSE_vcvc* >> It is giving the test results. >> >> So, do we need to give the QA test file name in place of square ? >> >> Thanks. >> >> On Mon, Sep 14, 2015 at 10:38 PM, Martin Braun >> wrote: >> >>> On 11.09.2015 21:51, monika bansal wrote: >>> > When i am running * ctest -V -R square, output* is : >>> > >>> > Constructing a list of tests >>> > Done constructing a list of tests >>> > Checking test dependency graph... >>> > Checking test dependency graph end >>> > No tests were found!!! >>> >>> Is there a test call 'square'? >>> >>> M >>> >>> >>> ___ >>> Discuss-gnuradio mailing list >>> Discuss-gnuradio@gnu.org >>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >>> >> >> >> >> ___ >> Discuss-gnuradio mailing >> listDiscuss-gnuradio@gnu.orghttps://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 mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] No tests were found!!!
Thanks Martin for the nice explanation... On Tue, Sep 15, 2015 at 1:59 PM, Marcus Müller wrote: > Hi Monika, > > man > > often gives instructions on how to use a program. > > man ctest > > yields something like the following: > >-R , --tests-regex > Run tests matching regular expression. > > This option tells ctest to run only the tests whose names > match the given regular expression. > > > now, you ran "ctest -V -R square"; ctest only ran the tests that have > "square" in their name (as you explicitly asked it to), and since there > were no tests with square in their name, none could be run. > > Best regards, > Marcus > > > On 15.09.2015 10:19, monika bansal wrote: > > Hi Martin, > I run *ctest -V -R qa_ofdm_chanest_MMSE_vcvc* > It is giving the test results. > > So, do we need to give the QA test file name in place of square ? > > Thanks. > > On Mon, Sep 14, 2015 at 10:38 PM, Martin Braun > wrote: > >> On 11.09.2015 21:51, monika bansal wrote: >> > When i am running * ctest -V -R square, output* is : >> > >> > Constructing a list of tests >> > Done constructing a list of tests >> > Checking test dependency graph... >> > Checking test dependency graph end >> > No tests were found!!! >> >> Is there a test call 'square'? >> >> M >> >> >> ___ >> Discuss-gnuradio mailing list >> Discuss-gnuradio@gnu.org >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> > > > > ___ > Discuss-gnuradio mailing > listDiscuss-gnuradio@gnu.orghttps://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 mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] No tests were found!!!
Hi Martin, I run *ctest -V -R qa_ofdm_chanest_MMSE_vcvc* It is giving the test results. So, do we need to give the QA test file name in place of square ? Thanks. On Mon, Sep 14, 2015 at 10:38 PM, Martin Braun wrote: > On 11.09.2015 21:51, monika bansal wrote: > > When i am running * ctest -V -R square, output* is : > > > > Constructing a list of tests > > Done constructing a list of tests > > Checking test dependency graph... > > Checking test dependency graph end > > No tests were found!!! > > Is there a test call 'square'? > > M > > > ___ > 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] No tests were found!!!
Hii I added new module named "Channel_Estimation" and block named"ofdm_chanest_MMSE_vcvc" using gr_modtool. I am attaching tha QA code file, which is same as the QA code file for "ofdm_chanest_vcvc". I am attaching that too. When i am running *ctest, output* is : Start 1: test_Channel_Estimation 1/2 Test #1: test_Channel_Estimation .. Passed0.00 sec Start 2: qa_ofdm_chanest_MMSE_vcvc 2/2 Test #2: qa_ofdm_chanest_MMSE_vcvc ***Failed0.05 sec 50% tests passed, 1 tests failed out of 2 Total Test time (real) = 0.05 sec The following tests FAILED: 2 - qa_ofdm_chanest_MMSE_vcvc (Failed) Errors while running CTest When i am running * ctest -V -R square, output* is : Constructing a list of tests Done constructing a list of tests Checking test dependency graph... Checking test dependency graph end No tests were found!!! What should i do ? Thanks.. #!/usr/bin/env python # -*- coding: utf-8 -*- # # Copyright 2015 <+YOU OR YOUR COMPANY+>. # # This is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 3, or (at your option) # any later version. # # This software is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this software; see the file COPYING. If not, write to # the Free Software Foundation, Inc., 51 Franklin Street, # Boston, MA 02110-1301, USA. # import sys import numpy import random import numpy from gnuradio import gr, gr_unittest, blocks, analog, digital import pmt import Channel_Estimation_swig as Channel_Estimation def shift_tuple(vec, N): """ Shifts a vector by N elements. Fills up with zeros. """ if N > 0: return (0,) * N + tuple(vec[0:-N]) else: N = -N return tuple(vec[N:]) + (0,) * N def rand_range(min_val, max_val): """ Returns a random value (uniform) from the interval min_val, max_val """ return random.random() * (max_val - min_val) + min_val class qa_ofdm_chanest_MMSE_vcvc (gr_unittest.TestCase): def setUp (self): self.tb = gr.top_block () def tearDown (self): self.tb = None def test_001_t (self): # set up fg #self.tb.run () # check data """ Add a frequency offset, check if it's correctly detected. Also add some random tags and see if they come out at the correct position. """ fft_len = 16 carr_offset = -2 sync_symbol1 = (0, 0, 0, 1, 0, 1, 0, -1, 0, 1, 0, -1, 0, 1, 0, 0) sync_symbol2 = (0, 0, 0, 1, -1, 1, -1, 1, 0, 1, -1, -1, -1, 1, 0, 0) data_symbol = (0, 0, 0, 1, -1, 1, -1, 1, 0, 1, -1, -1, -1, 1, 0, 0) tx_data = shift_tuple(sync_symbol1, carr_offset) + \ shift_tuple(sync_symbol2, carr_offset) + \ shift_tuple(data_symbol, carr_offset) tag1 = gr.tag_t() tag1.offset = 0 tag1.key = pmt.string_to_symbol("test_tag_1") tag1.value = pmt.from_long(23) tag2 = gr.tag_t() tag2.offset = 2 tag2.key = pmt.string_to_symbol("test_tag_2") tag2.value = pmt.from_long(42) src = blocks.vector_source_c(tx_data, False, fft_len, (tag1, tag2)) chanest = Channel_Estimation.ofdm_chanest_MMSE_vcvc(sync_symbol1, sync_symbol2, 1) #digital.ofdm_chanest_vcvc(sync_symbol1, sync_symbol2, 1) sink = blocks.vector_sink_c(fft_len) self.tb.connect(src, chanest, sink) self.tb.run() self.assertEqual(shift_tuple(sink.data(), -carr_offset), data_symbol) tags = sink.tags() ptags = {} for tag in tags: ptag = gr.tag_to_python(tag) ptags[ptag.key] = (ptag.value, ptag.offset) if ptag.key == 'ofdm_sync_chan_taps': ptags[ptag.key] = (None, ptag.offset) expected_tags = { 'ofdm_sync_carr_offset': (-2, 0), 'ofdm_sync_chan_taps': (None, 0), 'test_tag_1': (23, 0), 'test_tag_2': (42, 0), } self.assertEqual(ptags, expected_tags) def test_002_offset_1sym (self): """ Add a frequency offset, check if it's correctly detected. Difference to previous test is, it only uses one synchronisation symbol. """ fft_len = 16 carr_offset = -2 # This will not correct for +2 because it thinks carrier 14 is used # (because of interpolation) sync_symbol = (0, 0, 0, 1, 0, 1, 0, -1, 0, 1, 0, -1, 0, 1, 0, 0) data_symbol = (0, 0, 0, 1, -1, 1, -1, 1, 0, 1, -1, -1, -1, 1, 0, 0) tx_data = shift_tuple(sync_symbol, carr_offset) + \ shift_tuple(data_symbol, carr_offset)
Re: [Discuss-gnuradio] New module : error: expression cannot be used as a function d_fft_len(sync_symbol1.size())
Thank you Jeff. On Fri, Sep 11, 2015 at 5:46 PM, Jeff Long wrote: > You're missing a close paren on line 60 in the cc file. Compare the syntax > to the other cc file you included. > > - Jeff > > On 09/11/2015 06:37 AM, monika bansal wrote: > >> ok, >> I am attaching the file "ofdm_chanest_vcvc_imp.cc" and related files >> from gr-digital in gnuradio tree. >> >> I made new module named "gr-Channel_Estimation" and added a block named >> "ofdm_chanest_MMSE_vcvc". I am attaching these files as well. >> >> Thanks. >> >> >> On Fri, Sep 11, 2015 at 3:38 PM, Jeff Long > <mailto:willco...@gmail.com>> wrote: >> >> The statement is fine. If you post more info, for example the file >> containing this statement, someone should be able to figure out why >> it doesn't work in context. >> >> - Jeff >> >> On 09/11/2015 05:59 AM, monika bansal wrote: >> >> hii >> >> I am making a new module using gr_modtool. i am getting an * >> error: >> expression cannot be used as a function >> d_fft_len(sync_symbol1.size()).* >> * >> * >> But the same expression is used in ofdm_chanest_vcvc_imp.cc . >> >> How this statement is different for new module. >> I am new to C++ so this question may be a stupid one :). >> >> please let me know what should i do... >>Thanks >> >> >> ___ >> Discuss-gnuradio mailing list >> Discuss-gnuradio@gnu.org <mailto:Discuss-gnuradio@gnu.org> >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> >> >> >> ___ >> Discuss-gnuradio mailing list >> Discuss-gnuradio@gnu.org <mailto: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 mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] New module : error: expression cannot be used as a function d_fft_len(sync_symbol1.size())
ok, I am attaching the file "ofdm_chanest_vcvc_imp.cc" and related files from gr-digital in gnuradio tree. I made new module named "gr-Channel_Estimation" and added a block named "ofdm_chanest_MMSE_vcvc". I am attaching these files as well. Thanks. On Fri, Sep 11, 2015 at 3:38 PM, Jeff Long wrote: > The statement is fine. If you post more info, for example the file > containing this statement, someone should be able to figure out why it > doesn't work in context. > > - Jeff > > On 09/11/2015 05:59 AM, monika bansal wrote: > >> hii >> >> I am making a new module using gr_modtool. i am getting an * error: >> expression cannot be used as a function d_fft_len(sync_symbol1.size()).* >> * >> * >> But the same expression is used in ofdm_chanest_vcvc_imp.cc . >> >> How this statement is different for new module. >> I am new to C++ so this question may be a stupid one :). >> >> please let me know what should i do... >> Thanks >> >> >> ___ >> 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 > /* -*- c++ -*- */ /* * Copyright 2012,2013 Free Software Foundation, Inc. * * This file is part of GNU Radio * * GNU Radio is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation; either version 3, or (at your option) * any later version. * * GNU Radio is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. * * You should have received a copy of the GNU General Public License * along with GNU Radio; see the file COPYING. If not, write to * the Free Software Foundation, Inc., 51 Franklin Street, * Boston, MA 02110-1301, USA. */ #ifdef HAVE_CONFIG_H #include "config.h" #endif #include #include "ofdm_chanest_vcvc_impl.h" namespace gr { namespace digital { ofdm_chanest_vcvc::sptr ofdm_chanest_vcvc::make(const std::vector &sync_symbol1, const std::vector &sync_symbol2, int n_data_symbols, int eq_noise_red_len, int max_carr_offset, bool force_one_sync_symbol) { return gnuradio::get_initial_sptr ( new ofdm_chanest_vcvc_impl( sync_symbol1, sync_symbol2, n_data_symbols, eq_noise_red_len, max_carr_offset, force_one_sync_symbol ) ); } ofdm_chanest_vcvc_impl::ofdm_chanest_vcvc_impl( const std::vector &sync_symbol1, const std::vector &sync_symbol2, int n_data_symbols, int eq_noise_red_len, int max_carr_offset, bool force_one_sync_symbol ) : block("ofdm_chanest_vcvc", io_signature::make(1, 1, sizeof (gr_complex) * sync_symbol1.size()), io_signature::make(1, 2, sizeof (gr_complex) * sync_symbol1.size())), d_fft_len(sync_symbol1.size()), d_n_data_syms(n_data_symbols), d_n_sync_syms(1), d_eq_noise_red_len(eq_noise_red_len), d_ref_sym((sync_symbol2.size() && !force_one_sync_symbol) ? sync_symbol2 : sync_symbol1), d_corr_v(sync_symbol2), d_known_symbol_diffs(0, 0), d_new_symbol_diffs(0, 0), d_first_active_carrier(0), d_last_active_carrier(sync_symbol2.size()-1), d_interpolate(false) { // Set index of first and last active carrier for (int i = 0; i < d_fft_len; i++) { if (d_ref_sym[i] != gr_complex(0, 0)) { d_first_active_carrier = i; break; } } for (int i = d_fft_len-1; i >= 0; i--) { if (d_ref_sym[i] != gr_complex(0, 0)) { d_last_active_carrier = i; break; } } // Sanity checks if (sync_symbol2.size()) { if (sync_symbol1.size() != sync_symbol2.size()) { throw std::invalid_argument("sync symbols must have equal length."); } if (!force_one_sync_symbol) { d_n_sync_syms = 2; } } else { if (sync_symbol1[d_first_active_carrier+1] == gr_complex(0, 0)) { d_last_active_carrier++; d_interpolate = true; } } // Set up coarse freq estimation info // Allow all possible values: d_max_neg_carr_offset = -d_first_active_carrier; d_max_pos_carr_offset = d_fft_len - d_last_active_carrier - 1; if (max_carr_offset != -1) { d_max_neg_carr_offset = std::max(-max_carr_offset, d_max_neg_carr_offset); d_max_pos_carr_offset = std::min(max_carr_offset, d_max_pos_carr_offset); } // Carrier offsets
[Discuss-gnuradio] New module : error: expression cannot be used as a function d_fft_len(sync_symbol1.size())
hii I am making a new module using gr_modtool. i am getting an * error: expression cannot be used as a function d_fft_len(sync_symbol1.size()).* But the same expression is used in ofdm_chanest_vcvc_imp.cc . How this statement is different for new module. I am new to C++ so this question may be a stupid one :). please let me know what should i do... Thanks ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Inverse of cyclic prefix adder
I am not using Header/Payload Demux. On Sat, Sep 5, 2015 at 1:06 AM, Martin Braun wrote: > On 04.09.2015 01:20, monika bansal wrote: > > Hii > > > > In OFDM system, at the receiver side i want to remove initial 'x' > > symbols from the every 'x+fft_len' symbols. How can i do this ? Is there > > any block? or i need to create one... > > If you're using the Header/Payload Demux, that'll take care of the CP. > > Cheers, > Martin > > > ___ > 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] Inverse of cyclic prefix adder
Hii Thanks :) On Fri, Sep 4, 2015 at 3:00 PM, Marcus Müller wrote: > Hi Monika, > > personally, I'd use the "Keep M in N" block. > > Best regards, > Marcus > > > On 04.09.2015 10:20, monika bansal wrote: > > Hii > > In OFDM system, at the receiver side i want to remove initial 'x' symbols > from the every 'x+fft_len' symbols. How can i do this ? Is there any block? > or i need to create one... > > Thanks. > > > ___ > Discuss-gnuradio mailing > listDiscuss-gnuradio@gnu.orghttps://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 mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Inverse of cyclic prefix adder
Hii In OFDM system, at the receiver side i want to remove initial 'x' symbols from the every 'x+fft_len' symbols. How can i do this ? Is there any block? or i need to create one... Thanks. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Impulse Response of wide band wireless channel
Hii Is the Impulse Response of wide band wireless channel has only few significant components as compared to the channel delay spread ? This question is not related to gnu radio. I asked it, just to know the opinion of the people from this group who have good experiences in this field of communication. Thanks.. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Channel Model
Yes .. Thanks ! On Thu, Aug 6, 2015 at 3:07 PM, Johannes Demel wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > As a rule of thumb with expected error rate BERe: > > num simulation bits: (1 / BERe) * 100 > that's more like a minimum. It's probably better to go for * 1000. > Also if you use BER block, it has a parameter ' BER Min. Errors'. As > long as it didn't count at least this amount of errors it'll not > output anything. > Depending on your code and your SNR 8-12dB I'd expect you need at > least 1Gbit or in case of SNR=12dB more towards 100Gbit in order to > obtain meaningful results. > Hope that helps. > > On 06.08.2015 11:31, monika bansal wrote: > > 16 bits for all snr values.,... > > > > On Thu, Aug 6, 2015 at 2:45 PM, Marcus Müller > > wrote: > > > >> Taking a blind guess here: How many samples do you simulate for > >> Eb/N0 = 8dB? And for 10dB? And for 12dB? > >> > >> Best regards, Marcus > >> > >> > >> On 06.08.2015 10:58, monika bansal wrote: > >> > >> Yes Marcus... and i used delay block at the output of the > >> demodulator to make output bits align with input bits. Now it is > >> tracing the theoretical curve till 9 db but after that error is > >> not reducing. > >> > >> I am attaching the curve. Why is this happening ?? > >> > >> On Thu, Aug 6, 2015 at 2:03 PM, Marcus Müller > >> wrote: > >> > >>> How should i calculate the error now? > >>> > >>> That pretty much depends on what *you* want to measure -- > >>> obviously, these bits are lost, so practically, this increases > >>> your BER. If you want to demonstrate asymptotic behaviour, > >>> however, then you could just increase the length of your > >>> simulation until a few bits lost at start and end just don't > >>> matter anymore. > >>> > >>> Greetings, Marcus > >>> > >>> > >>> On 06.08.2015 06:47, monika bansal wrote: > >>> > >>> Hii Thanks for your responses. > >>> > >>> The problem is this channel model is eating some initial 6 > >>> bits(3 qpsk symbols) and last 10 bits(5 qpsk symbols). Because > >>> of this index of output symbol is different fron input which > >>> is resulting in error for all snr ranges. You can see the > >>> output for noise_volage =0.0 > >>> > >>> Input = (0L, 0L, 2L, 3L, 1L, 2L, 1L, 1L, 2L, 3L, 0L, 1L, 0L, > >>> 1L, 1L, 3L, 2L, 3L, 1L, 0L, 2L, 0L, 3L, 2L, 2L, 1L, 3L, 2L, 3L, > >>> 0L, 2L, 2L, 0L, 1L, 2L, 3L, 3L, 0L, 2L, 2L, 0L, 2L, 3L, 3L, 2L, > >>> 2L, 3L, 0L, 0L, 0L, 1L, 0L, 2L, 2L, 2L, 0L, 3L, 0L, 1L, 1L, 3L, > >>> 0L, 1L, 3L, 3L, 3L, 0L, 0L, 2L, 0L, 1L, 1L, 0L, 2L, 3L, 2L, 2L, > >>> 3L, 2L, 3L) > >>> > >>> Output = (3L, 1L, 2L, 1L, 1L, 2L, 3L, 0L, 1L, 0L, 1L, 1L, 3L, > >>> 2L, 3L, 1L, 0L, 2L, 0L, 3L, 2L, 2L, 1L, 3L, 2L, 3L, 0L, 2L, 2L, > >>> 0L, 1L, 2L, 3L, 3L, 0L, 2L, 2L, 0L, 2L, 3L, 3L, 2L, 2L, 3L, 0L, > >>> 0L, 0L, 1L, 0L, 2L, 2L, 2L, 0L, 3L, 0L, 1L, 1L, 3L, 0L, 1L, 3L, > >>> 3L, 3L, 0L, 0L, 2L, 0L, 1L, 1L, 0L, 2L, 3L) > >>> > >>> > >>> Input = (0L, 1L, 0L, 2L, 0L, 1L, 1L, 3L, 2L, 3L, 3L, 1L, 0L, > >>> 2L, 2L, 0L, 0L, 1L, 1L, 1L, 0L, 0L, 3L, 2L, 3L, 1L, 1L, 2L, 1L, > >>> 0L, 3L, 0L, 0L, 0L, 3L, 0L, 3L, 2L, 1L, 0L, 3L, 1L, 3L, 1L, 1L, > >>> 3L, 1L, 2L, 0L, 1L, 0L, 3L, 1L, 0L, 3L, 2L, 1L, 2L, 3L, 3L, 2L, > >>> 1L, 3L, 0L, 1L, 2L, 3L, 3L, 0L, 0L, 0L, 2L, 3L, 3L, 1L, 3L, 3L, > >>> 1L, 0L, 3L) > >>> > >>> Output = (2L, 0L, 1L, 1L, 3L, 2L, 3L, 3L, 1L, 0L, 2L, 2L, 0L, > >>> 0L, 1L, 1L, 1L, 0L, 0L, 3L, 2L, 3L, 1L, 1L, 2L, 1L, 0L, 3L, 0L, > >>> 0L, 0L, 3L, 0L, 3L, 2L, 1L, 0L, 3L, 1L, 3L, 1L, 1L, 3L, 1L, 2L, > >>> 0L, 1L, 0L, 3L, 1L, 0L, 3L, 2L, 1L, 2L, 3L, 3L, 2L, 1L, 3L, 0L, > >>> 1L, 2L, 3L, 3L, 0L, 0L, 0L, 2L, 3L, 3L, 1L) > >>> > >>> How should i calculate the error now? Should i use Delay > >>> block? > >>> > >>> On Thu, Aug 6, 2015 at 2:34 AM, Johnathan Corgan < > >>> johnat...@corganlabs.com> wrote: > >>> > >>>> On Wed, Aug 5, 2015 at 12:51 PM, Martin Braun < > >>>> martin.br...@ettus.com> wrote: > >>>> > >>>> > >>>>> Try > >>>>> > >>
Re: [Discuss-gnuradio] Channel Model
16 bits for all snr values.,... On Thu, Aug 6, 2015 at 2:45 PM, Marcus Müller wrote: > Taking a blind guess here: > How many samples do you simulate for Eb/N0 = 8dB? And for 10dB? And for > 12dB? > > Best regards, > Marcus > > > On 06.08.2015 10:58, monika bansal wrote: > > Yes Marcus... > and i used delay block at the output of the demodulator to make output > bits align with input bits. > Now it is tracing the theoretical curve till 9 db but after that error is > not reducing. > > I am attaching the curve. > Why is this happening ?? > > On Thu, Aug 6, 2015 at 2:03 PM, Marcus Müller > wrote: > >> How should i calculate the error now? >> >> That pretty much depends on what *you* want to measure -- obviously, >> these bits are lost, so practically, this increases your BER. >> If you want to demonstrate asymptotic behaviour, however, then you could >> just increase the length of your simulation until a few bits lost at start >> and end just don't matter anymore. >> >> Greetings, >> Marcus >> >> >> On 06.08.2015 06:47, monika bansal wrote: >> >> Hii >> Thanks for your responses. >> >> The problem is this channel model is eating some initial 6 bits(3 qpsk >> symbols) and last 10 bits(5 qpsk symbols). >> Because of this index of output symbol is different fron input which is >> resulting in error for all snr ranges. >> You can see the output for noise_volage =0.0 >> >> Input = (0L, 0L, 2L, 3L, 1L, 2L, 1L, 1L, 2L, 3L, 0L, 1L, 0L, 1L, 1L, 3L, >> 2L, 3L, 1L, 0L, 2L, 0L, 3L, 2L, 2L, 1L, 3L, 2L, 3L, 0L, 2L, 2L, 0L, 1L, 2L, >> 3L, 3L, 0L, 2L, 2L, 0L, 2L, 3L, 3L, 2L, 2L, 3L, 0L, 0L, 0L, 1L, 0L, 2L, 2L, >> 2L, 0L, 3L, 0L, 1L, 1L, 3L, 0L, 1L, 3L, 3L, 3L, 0L, 0L, 2L, 0L, 1L, 1L, 0L, >> 2L, 3L, 2L, 2L, 3L, 2L, 3L) >> >> Output = (3L, 1L, 2L, 1L, 1L, 2L, 3L, 0L, 1L, 0L, 1L, 1L, 3L, 2L, 3L, 1L, >> 0L, 2L, 0L, 3L, 2L, 2L, 1L, 3L, 2L, 3L, 0L, 2L, 2L, 0L, 1L, 2L, 3L, 3L, 0L, >> 2L, 2L, 0L, 2L, 3L, 3L, 2L, 2L, 3L, 0L, 0L, 0L, 1L, 0L, 2L, 2L, 2L, 0L, 3L, >> 0L, 1L, 1L, 3L, 0L, 1L, 3L, 3L, 3L, 0L, 0L, 2L, 0L, 1L, 1L, 0L, 2L, 3L) >> >> >> Input = (0L, 1L, 0L, 2L, 0L, 1L, 1L, 3L, 2L, 3L, 3L, 1L, 0L, 2L, 2L, 0L, >> 0L, 1L, 1L, 1L, 0L, 0L, 3L, 2L, 3L, 1L, 1L, 2L, 1L, 0L, 3L, 0L, 0L, 0L, 3L, >> 0L, 3L, 2L, 1L, 0L, 3L, 1L, 3L, 1L, 1L, 3L, 1L, 2L, 0L, 1L, 0L, 3L, 1L, 0L, >> 3L, 2L, 1L, 2L, 3L, 3L, 2L, 1L, 3L, 0L, 1L, 2L, 3L, 3L, 0L, 0L, 0L, 2L, 3L, >> 3L, 1L, 3L, 3L, 1L, 0L, 3L) >> >> Output = (2L, 0L, 1L, 1L, 3L, 2L, 3L, 3L, 1L, 0L, 2L, 2L, 0L, 0L, 1L, 1L, >> 1L, 0L, 0L, 3L, 2L, 3L, 1L, 1L, 2L, 1L, 0L, 3L, 0L, 0L, 0L, 3L, 0L, 3L, 2L, >> 1L, 0L, 3L, 1L, 3L, 1L, 1L, 3L, 1L, 2L, 0L, 1L, 0L, 3L, 1L, 0L, 3L, 2L, 1L, >> 2L, 3L, 3L, 2L, 1L, 3L, 0L, 1L, 2L, 3L, 3L, 0L, 0L, 0L, 2L, 3L, 3L, 1L) >> >> How should i calculate the error now? >> Should i use Delay block? >> >> On Thu, Aug 6, 2015 at 2:34 AM, Johnathan Corgan < >> johnat...@corganlabs.com> wrote: >> >>> On Wed, Aug 5, 2015 at 12:51 PM, Martin Braun < >>> martin.br...@ettus.com> wrote: >>> >>> >>>> Try >>>> >>>> noise_voltage = self.EbN0_to_noise_voltage(EbN0)/sqrt(2) >>>> >>>> the original berawgn.py was already buggy, because it didn't follow a >>>> recent change in the noise power. I've submitted a patch, but it >>>> probably won't be merged before the release cycle is reset (cf >>>> >>>> https://github.com/gnuradio/gnuradio/compare/master...mbr0wn:digital/berawgn_fix_noisepower?expand=1 >>>> ). >>> >>> >>> This did get merged for 3.7.8 release. >>> >>> >>> -- >>> Johnathan Corgan >>> Corgan Labs - SDR Training and Development Services >>> Intro to SDR Class - Aug. 31-Sep. 1, Columbia, MD >>> Intro to SDR Class - Sep. 3-4, Santa Clara, CA >>> <http://corganlabs.com>http://corganlabs.com >>> >>> ___ >>> Discuss-gnuradio mailing list >>> Discuss-gnuradio@gnu.org >>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >>> >>> >> >> >> ___ >> Discuss-gnuradio mailing >> listDiscuss-gnuradio@gnu.orghttps://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 mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Channel Model
Yes Marcus... and i used delay block at the output of the demodulator to make output bits align with input bits. Now it is tracing the theoretical curve till 9 db but after that error is not reducing. I am attaching the curve. Why is this happening ?? On Thu, Aug 6, 2015 at 2:03 PM, Marcus Müller wrote: > How should i calculate the error now? > > That pretty much depends on what *you* want to measure -- obviously, > these bits are lost, so practically, this increases your BER. > If you want to demonstrate asymptotic behaviour, however, then you could > just increase the length of your simulation until a few bits lost at start > and end just don't matter anymore. > > Greetings, > Marcus > > > On 06.08.2015 06:47, monika bansal wrote: > > Hii > Thanks for your responses. > > The problem is this channel model is eating some initial 6 bits(3 qpsk > symbols) and last 10 bits(5 qpsk symbols). > Because of this index of output symbol is different fron input which is > resulting in error for all snr ranges. > You can see the output for noise_volage =0.0 > > Input = (0L, 0L, 2L, 3L, 1L, 2L, 1L, 1L, 2L, 3L, 0L, 1L, 0L, 1L, 1L, 3L, > 2L, 3L, 1L, 0L, 2L, 0L, 3L, 2L, 2L, 1L, 3L, 2L, 3L, 0L, 2L, 2L, 0L, 1L, 2L, > 3L, 3L, 0L, 2L, 2L, 0L, 2L, 3L, 3L, 2L, 2L, 3L, 0L, 0L, 0L, 1L, 0L, 2L, 2L, > 2L, 0L, 3L, 0L, 1L, 1L, 3L, 0L, 1L, 3L, 3L, 3L, 0L, 0L, 2L, 0L, 1L, 1L, 0L, > 2L, 3L, 2L, 2L, 3L, 2L, 3L) > > Output = (3L, 1L, 2L, 1L, 1L, 2L, 3L, 0L, 1L, 0L, 1L, 1L, 3L, 2L, 3L, 1L, > 0L, 2L, 0L, 3L, 2L, 2L, 1L, 3L, 2L, 3L, 0L, 2L, 2L, 0L, 1L, 2L, 3L, 3L, 0L, > 2L, 2L, 0L, 2L, 3L, 3L, 2L, 2L, 3L, 0L, 0L, 0L, 1L, 0L, 2L, 2L, 2L, 0L, 3L, > 0L, 1L, 1L, 3L, 0L, 1L, 3L, 3L, 3L, 0L, 0L, 2L, 0L, 1L, 1L, 0L, 2L, 3L) > > > Input = (0L, 1L, 0L, 2L, 0L, 1L, 1L, 3L, 2L, 3L, 3L, 1L, 0L, 2L, 2L, 0L, > 0L, 1L, 1L, 1L, 0L, 0L, 3L, 2L, 3L, 1L, 1L, 2L, 1L, 0L, 3L, 0L, 0L, 0L, 3L, > 0L, 3L, 2L, 1L, 0L, 3L, 1L, 3L, 1L, 1L, 3L, 1L, 2L, 0L, 1L, 0L, 3L, 1L, 0L, > 3L, 2L, 1L, 2L, 3L, 3L, 2L, 1L, 3L, 0L, 1L, 2L, 3L, 3L, 0L, 0L, 0L, 2L, 3L, > 3L, 1L, 3L, 3L, 1L, 0L, 3L) > > Output = (2L, 0L, 1L, 1L, 3L, 2L, 3L, 3L, 1L, 0L, 2L, 2L, 0L, 0L, 1L, 1L, > 1L, 0L, 0L, 3L, 2L, 3L, 1L, 1L, 2L, 1L, 0L, 3L, 0L, 0L, 0L, 3L, 0L, 3L, 2L, > 1L, 0L, 3L, 1L, 3L, 1L, 1L, 3L, 1L, 2L, 0L, 1L, 0L, 3L, 1L, 0L, 3L, 2L, 1L, > 2L, 3L, 3L, 2L, 1L, 3L, 0L, 1L, 2L, 3L, 3L, 0L, 0L, 0L, 2L, 3L, 3L, 1L) > > How should i calculate the error now? > Should i use Delay block? > > On Thu, Aug 6, 2015 at 2:34 AM, Johnathan Corgan < > johnat...@corganlabs.com> wrote: > >> On Wed, Aug 5, 2015 at 12:51 PM, Martin Braun >> wrote: >> >> >>> Try >>> >>> noise_voltage = self.EbN0_to_noise_voltage(EbN0)/sqrt(2) >>> >>> the original berawgn.py was already buggy, because it didn't follow a >>> recent change in the noise power. I've submitted a patch, but it >>> probably won't be merged before the release cycle is reset (cf >>> >>> https://github.com/gnuradio/gnuradio/compare/master...mbr0wn:digital/berawgn_fix_noisepower?expand=1 >>> ). >> >> >> This did get merged for 3.7.8 release. >> >> >> -- >> Johnathan Corgan >> Corgan Labs - SDR Training and Development Services >> Intro to SDR Class - Aug. 31-Sep. 1, Columbia, MD >> Intro to SDR Class - Sep. 3-4, Santa Clara, CA >> http://corganlabs.com >> >> ___ >> Discuss-gnuradio mailing list >> Discuss-gnuradio@gnu.org >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> >> > > > ___ > Discuss-gnuradio mailing > listDiscuss-gnuradio@gnu.orghttps://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 mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Channel Model
Hii Thanks for your responses. The problem is this channel model is eating some initial 6 bits(3 qpsk symbols) and last 10 bits(5 qpsk symbols). Because of this index of output symbol is different fron input which is resulting in error for all snr ranges. You can see the output for noise_volage =0.0 Input = (0L, 0L, 2L, 3L, 1L, 2L, 1L, 1L, 2L, 3L, 0L, 1L, 0L, 1L, 1L, 3L, 2L, 3L, 1L, 0L, 2L, 0L, 3L, 2L, 2L, 1L, 3L, 2L, 3L, 0L, 2L, 2L, 0L, 1L, 2L, 3L, 3L, 0L, 2L, 2L, 0L, 2L, 3L, 3L, 2L, 2L, 3L, 0L, 0L, 0L, 1L, 0L, 2L, 2L, 2L, 0L, 3L, 0L, 1L, 1L, 3L, 0L, 1L, 3L, 3L, 3L, 0L, 0L, 2L, 0L, 1L, 1L, 0L, 2L, 3L, 2L, 2L, 3L, 2L, 3L) Output = (3L, 1L, 2L, 1L, 1L, 2L, 3L, 0L, 1L, 0L, 1L, 1L, 3L, 2L, 3L, 1L, 0L, 2L, 0L, 3L, 2L, 2L, 1L, 3L, 2L, 3L, 0L, 2L, 2L, 0L, 1L, 2L, 3L, 3L, 0L, 2L, 2L, 0L, 2L, 3L, 3L, 2L, 2L, 3L, 0L, 0L, 0L, 1L, 0L, 2L, 2L, 2L, 0L, 3L, 0L, 1L, 1L, 3L, 0L, 1L, 3L, 3L, 3L, 0L, 0L, 2L, 0L, 1L, 1L, 0L, 2L, 3L) Input = (0L, 1L, 0L, 2L, 0L, 1L, 1L, 3L, 2L, 3L, 3L, 1L, 0L, 2L, 2L, 0L, 0L, 1L, 1L, 1L, 0L, 0L, 3L, 2L, 3L, 1L, 1L, 2L, 1L, 0L, 3L, 0L, 0L, 0L, 3L, 0L, 3L, 2L, 1L, 0L, 3L, 1L, 3L, 1L, 1L, 3L, 1L, 2L, 0L, 1L, 0L, 3L, 1L, 0L, 3L, 2L, 1L, 2L, 3L, 3L, 2L, 1L, 3L, 0L, 1L, 2L, 3L, 3L, 0L, 0L, 0L, 2L, 3L, 3L, 1L, 3L, 3L, 1L, 0L, 3L) Output = (2L, 0L, 1L, 1L, 3L, 2L, 3L, 3L, 1L, 0L, 2L, 2L, 0L, 0L, 1L, 1L, 1L, 0L, 0L, 3L, 2L, 3L, 1L, 1L, 2L, 1L, 0L, 3L, 0L, 0L, 0L, 3L, 0L, 3L, 2L, 1L, 0L, 3L, 1L, 3L, 1L, 1L, 3L, 1L, 2L, 0L, 1L, 0L, 3L, 1L, 0L, 3L, 2L, 1L, 2L, 3L, 3L, 2L, 1L, 3L, 0L, 1L, 2L, 3L, 3L, 0L, 0L, 0L, 2L, 3L, 3L, 1L) How should i calculate the error now? Should i use Delay block? On Thu, Aug 6, 2015 at 2:34 AM, Johnathan Corgan wrote: > On Wed, Aug 5, 2015 at 12:51 PM, Martin Braun > wrote: > > >> Try >> >> noise_voltage = self.EbN0_to_noise_voltage(EbN0)/sqrt(2) >> >> the original berawgn.py was already buggy, because it didn't follow a >> recent change in the noise power. I've submitted a patch, but it >> probably won't be merged before the release cycle is reset (cf >> >> https://github.com/gnuradio/gnuradio/compare/master...mbr0wn:digital/berawgn_fix_noisepower?expand=1 >> ). > > > This did get merged for 3.7.8 release. > > > -- > Johnathan Corgan > Corgan Labs - SDR Training and Development Services > Intro to SDR Class - Aug. 31-Sep. 1, Columbia, MD > Intro to SDR Class - Sep. 3-4, Santa Clara, CA > http://corganlabs.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] Channel Model
Hii I am using channels.channel_model as channels_channel_model_0 = channels.channel_model( noise_voltage = self.EbN0_to_noise_voltage(EbN0), frequency_offset=0.0, epsilon=1.0, taps=(1.0 + 0j, ), noise_seed=RAND_SEED, block_tags=True ) in the place of Add and Noise_Source in berawgn.py file.. But the BER is not following the theory curve. I am attaching the curve i got. What does this channel model do ? Can someone please explain it. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] OFDM channel Estimation Block
Hiii I did following : build% make build% make test gr-digital% gr-modtool makexml ofdm_chanestMMSE_vcvc build% make install everything seemed successful but WHEN opening GRC one block pop ups with : " Cannot import gnuradio. Is the python path environment variable set correctly? All OS: PYTHONPATH Is the library path environment variable set correctly? Linux: LD_LIBRARY_PATH Windows: PATH MacOSX: DYLD_LIBRARY_PATH " What happened ? Previously it was running... please help.. On Mon, Jul 20, 2015 at 6:56 PM, Marcus Müller wrote: > Probably you're in gnuradio/gr-digital instead of gnuradio/build. > > Best regards, > Marcus > > > Am 20. Juli 2015 12:12:20 MESZ, schrieb monika bansal < > monika19...@gmail.com>: >> >> Hiii >> >> The previous problem is solved. Now after >> >> gr-digital % make -j4 >> >> It is saying : >> make: *** No targets specified and no makefile found. Stop. >> >> But Configuring and Generating is done. >> >> What should i do ? >> >> >> >> On Mon, Jul 20, 2015 at 3:21 PM, Marcus Müller >> wrote: >> >>> Monika, >>> >>> obviously, there's a mistake in gr-digital/lib/CMakeLists.txt, line 189. >>> A little more trying to solve this yourself might probably help you find >>> the typo; we can't tell you what you've changed, so we can't help you :) >>> >>> Best regards, >>> Marcus >>> >>> >>> On 20.07.2015 11:29, monika bansal wrote: >>> >>> Hii >>> >>> After the command : >>> gnuradio % cmake .. >>> >>> Configuring for all other blocks except gr-digital is completed. I am >>> posting the output for gr-digital only : >>> >>> -- Configuring gr-digital support... >>> -- Dependency Boost_FOUND = 1 >>> -- Dependency ENABLE_VOLK = ON >>> -- Dependency ENABLE_GNURADIO_RUNTIME = ON >>> -- Dependency ENABLE_GR_FFT = ON >>> -- Dependency ENABLE_GR_FILTER = ON >>> -- Dependency ENABLE_GR_BLOCKS = ON >>> -- Dependency ENABLE_GR_ANALOG = ON >>> -- Dependency ENABLE_GR_BLOCKS = ON >>> -- Dependency ENABLE_GR_FILTER = ON >>> -- Enabling gr-digital support. >>> -- Override with -DENABLE_GR_DIGITAL=ON/OFF >>> CMake Error: Error in cmake code at >>> >>> /home/spclab/Desktop/Monika/GNURADIO/gnuradio-3.7.5.1/gr-digital/lib/CMakeLists.txt:189: >>> Parse error. Expected a command name, got unquoted argument with text >>> "${CMAKE_CURRENT_SOURCE_DIR}/qa_ofdm_chanestMMSE_vcvc.cc". >>> >>> Configuring incomplete, errors occurred! >>> >>> What should i do ? >>> >>> On Mon, Jul 20, 2015 at 2:39 PM, Marcus Müller >> > wrote: >>> >>>> Hi Monika, >>>> >>>> In-Tree components (like gr-digital) are meant to be built within the >>>> whole GNU Radio tree, so you don't make a "build/" directory under >>>> gr-digital, but under gnuradio: >>>> >>>> gr-digital % cd .. >>>> gnuradio % mkdir build >>>> gnuradio % cd build >>>> gnuradio % cmake .. >>>> gr-digital % make -j4 >>>> >>>> this will build all GNU Radio. You could selectively only build >>>> gr-digital, but you will probably want to install a complete GNU Radio, so >>>> that doesn't really help you much. >>>> >>>> Best regards, >>>> Marcus >>>> >>>> >>>> >>>> On 20.07.2015 10:58, monika bansal wrote: >>>> >>>> Hii >>>> >>>> After the following command : >>>> >>>> gr-digital % gr_modtool add -t general ofdm_chanestMMSE_vcvc >>>> >>>> >>>> and editing the files: include/.h , lib/.h , lib/.cc and >>>> python/digital/qa_ofdm_chanest_vcvc.py >>>> >>>> >>>> I run the command >>>> gr-digital % mkdir build >>>> >>>> gr-digital % cmake ../ >>>> >>>> >>>> It giving the following output : >>>> >>>> -- The C compiler identification is GNU 4.8.2 >>>> -- The CXX compiler identification is GNU 4.8.2 >>>> -- Check for working C compiler: /usr/bin/cc >>>> -- Check for working C compiler: /usr/bin/cc -- works >>>> -- Detecting C compiler ABI info >>>> -- Detectin
Re: [Discuss-gnuradio] OFDM channel Estimation Block
Hiii The previous problem is solved. Now after gr-digital % make -j4 It is saying : make: *** No targets specified and no makefile found. Stop. But Configuring and Generating is done. What should i do ? On Mon, Jul 20, 2015 at 3:21 PM, Marcus Müller wrote: > Monika, > > obviously, there's a mistake in gr-digital/lib/CMakeLists.txt, line 189. > A little more trying to solve this yourself might probably help you find > the typo; we can't tell you what you've changed, so we can't help you :) > > Best regards, > Marcus > > > On 20.07.2015 11:29, monika bansal wrote: > > Hii > > After the command : > gnuradio % cmake .. > > Configuring for all other blocks except gr-digital is completed. I am > posting the output for gr-digital only : > > -- Configuring gr-digital support... > -- Dependency Boost_FOUND = 1 > -- Dependency ENABLE_VOLK = ON > -- Dependency ENABLE_GNURADIO_RUNTIME = ON > -- Dependency ENABLE_GR_FFT = ON > -- Dependency ENABLE_GR_FILTER = ON > -- Dependency ENABLE_GR_BLOCKS = ON > -- Dependency ENABLE_GR_ANALOG = ON > -- Dependency ENABLE_GR_BLOCKS = ON > -- Dependency ENABLE_GR_FILTER = ON > -- Enabling gr-digital support. > -- Override with -DENABLE_GR_DIGITAL=ON/OFF > CMake Error: Error in cmake code at > > /home/spclab/Desktop/Monika/GNURADIO/gnuradio-3.7.5.1/gr-digital/lib/CMakeLists.txt:189: > Parse error. Expected a command name, got unquoted argument with text > "${CMAKE_CURRENT_SOURCE_DIR}/qa_ofdm_chanestMMSE_vcvc.cc". > > Configuring incomplete, errors occurred! > > What should i do ? > > On Mon, Jul 20, 2015 at 2:39 PM, Marcus Müller > wrote: > >> Hi Monika, >> >> In-Tree components (like gr-digital) are meant to be built within the >> whole GNU Radio tree, so you don't make a "build/" directory under >> gr-digital, but under gnuradio: >> >> gr-digital % cd .. >> gnuradio % mkdir build >> gnuradio % cd build >> gnuradio % cmake .. >> gr-digital % make -j4 >> >> this will build all GNU Radio. You could selectively only build >> gr-digital, but you will probably want to install a complete GNU Radio, so >> that doesn't really help you much. >> >> Best regards, >> Marcus >> >> >> >> On 20.07.2015 10:58, monika bansal wrote: >> >> Hii >> >> After the following command : >> >> gr-digital % gr_modtool add -t general ofdm_chanestMMSE_vcvc >> >> >> and editing the files: include/.h , lib/.h , lib/.cc and >> python/digital/qa_ofdm_chanest_vcvc.py >> >> >> I run the command >> gr-digital % mkdir build >> >> gr-digital % cmake ../ >> >> >> It giving the following output : >> >> -- The C compiler identification is GNU 4.8.2 >> -- The CXX compiler identification is GNU 4.8.2 >> -- Check for working C compiler: /usr/bin/cc >> -- Check for working C compiler: /usr/bin/cc -- works >> -- Detecting C compiler ABI info >> -- Detecting C compiler ABI info - done >> -- Check for working CXX compiler: /usr/bin/c++ >> -- Check for working CXX compiler: /usr/bin/c++ -- works >> -- Detecting CXX compiler ABI info >> -- Detecting CXX compiler ABI info - done >> CMake Error at CMakeLists.txt:23 (include): >> include could not find load file: >> >> GrBoost >> >> >> CMake Error at CMakeLists.txt:28 (include): >> include could not find load file: >> >> GrComponent >> >> >> CMake Error at CMakeLists.txt:29 (GR_REGISTER_COMPONENT): >> Unknown CMake command "GR_REGISTER_COMPONENT". >> >> >> CMake Warning (dev) in CMakeLists.txt: >> No cmake_minimum_required command is present. A line of code such as >> >> cmake_minimum_required(VERSION 2.8) >> >> should be added at the top of the file. The version specified may be lower >> if you wish to support older CMake versions for this project. For more >> information run "cmake --help-policy CMP". >> This warning is for project developers. Use -Wno-dev to suppress it. >> >> -- Configuring incomplete, errors occurred! >> See also >> "/home/spclab/Desktop/Monika/GNURADIO/gnuradio-3.7.5.1/gr-digital/build/CMakeFiles/CMakeOutput.log". >> >> >> >> What should i do ? have i done something wrong ? >> >> >> On Sat, Jul 18, 2015 at 11:37 AM, monika bansal < >> monika19...@gmail.com> wrote: >> >>> yes... i will. >>> >>> On Fri, Jul 17,
Re: [Discuss-gnuradio] OFDM channel Estimation Block
Hii After the command : gnuradio % cmake .. Configuring for all other blocks except gr-digital is completed. I am posting the output for gr-digital only : -- Configuring gr-digital support... -- Dependency Boost_FOUND = 1 -- Dependency ENABLE_VOLK = ON -- Dependency ENABLE_GNURADIO_RUNTIME = ON -- Dependency ENABLE_GR_FFT = ON -- Dependency ENABLE_GR_FILTER = ON -- Dependency ENABLE_GR_BLOCKS = ON -- Dependency ENABLE_GR_ANALOG = ON -- Dependency ENABLE_GR_BLOCKS = ON -- Dependency ENABLE_GR_FILTER = ON -- Enabling gr-digital support. -- Override with -DENABLE_GR_DIGITAL=ON/OFF CMake Error: Error in cmake code at /home/spclab/Desktop/Monika/GNURADIO/gnuradio-3.7.5.1/gr-digital/lib/CMakeLists.txt:189: Parse error. Expected a command name, got unquoted argument with text "${CMAKE_CURRENT_SOURCE_DIR}/qa_ofdm_chanestMMSE_vcvc.cc". Configuring incomplete, errors occurred! What should i do ? On Mon, Jul 20, 2015 at 2:39 PM, Marcus Müller wrote: > Hi Monika, > > In-Tree components (like gr-digital) are meant to be built within the > whole GNU Radio tree, so you don't make a "build/" directory under > gr-digital, but under gnuradio: > > gr-digital % cd .. > gnuradio % mkdir build > gnuradio % cd build > gnuradio % cmake .. > gr-digital % make -j4 > > this will build all GNU Radio. You could selectively only build > gr-digital, but you will probably want to install a complete GNU Radio, so > that doesn't really help you much. > > Best regards, > Marcus > > > > On 20.07.2015 10:58, monika bansal wrote: > > Hii > > After the following command : > > gr-digital % gr_modtool add -t general ofdm_chanestMMSE_vcvc > > > and editing the files: include/.h , lib/.h , lib/.cc and > python/digital/qa_ofdm_chanest_vcvc.py > > > I run the command > gr-digital % mkdir build > > gr-digital % cmake ../ > > > It giving the following output : > > -- The C compiler identification is GNU 4.8.2 > -- The CXX compiler identification is GNU 4.8.2 > -- Check for working C compiler: /usr/bin/cc > -- Check for working C compiler: /usr/bin/cc -- works > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ > -- Check for working CXX compiler: /usr/bin/c++ -- works > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > CMake Error at CMakeLists.txt:23 (include): > include could not find load file: > > GrBoost > > > CMake Error at CMakeLists.txt:28 (include): > include could not find load file: > > GrComponent > > > CMake Error at CMakeLists.txt:29 (GR_REGISTER_COMPONENT): > Unknown CMake command "GR_REGISTER_COMPONENT". > > > CMake Warning (dev) in CMakeLists.txt: > No cmake_minimum_required command is present. A line of code such as > > cmake_minimum_required(VERSION 2.8) > > should be added at the top of the file. The version specified may be lower > if you wish to support older CMake versions for this project. For more > information run "cmake --help-policy CMP". > This warning is for project developers. Use -Wno-dev to suppress it. > > -- Configuring incomplete, errors occurred! > See also > "/home/spclab/Desktop/Monika/GNURADIO/gnuradio-3.7.5.1/gr-digital/build/CMakeFiles/CMakeOutput.log". > > > > What should i do ? have i done something wrong ? > > > On Sat, Jul 18, 2015 at 11:37 AM, monika bansal > wrote: > >> yes... i will. >> >> On Fri, Jul 17, 2015 at 9:48 PM, Martin Braun < >> martin.br...@ettus.com> wrote: >> >>> Monika, >>> >>> please make sure you've gone through the tutorials at >>> http://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorials, to >>> make sure we're speaking the same terminology and all the basics are >>> clear. >>> >>> Cheers, >>> M >>> >>> On 17.07.2015 06:20, monika bansal wrote: >>> > Ok... Thanks :) >>> > >>> > On Fri, Jul 17, 2015 at 6:47 PM, Marcus Müller < >>> marcus.muel...@ettus.com >>> > <mailto:marcus.muel...@ettus.com>> wrote: >>> > >>> > You can of course add that later on, but don't forget to change >>> both >>> > your include/blockname.h, your lib/blockname_impl.h and your >>> > lib/blockname_impl.cc. If you want to work with GRC, remember to >>> > edit the .xml in grc/, too! >>> > >>> > Best regards, >>> > Marcus >>> > >>>
Re: [Discuss-gnuradio] OFDM channel Estimation Block
Hii After the following command : gr-digital % gr_modtool add -t general ofdm_chanestMMSE_vcvc and editing the files: include/.h , lib/.h , lib/.cc and python/digital/qa_ofdm_chanest_vcvc.py I run the command gr-digital % mkdir build gr-digital % cmake ../ It giving the following output : -- The C compiler identification is GNU 4.8.2 -- The CXX compiler identification is GNU 4.8.2 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done CMake Error at CMakeLists.txt:23 (include): include could not find load file: GrBoost CMake Error at CMakeLists.txt:28 (include): include could not find load file: GrComponent CMake Error at CMakeLists.txt:29 (GR_REGISTER_COMPONENT): Unknown CMake command "GR_REGISTER_COMPONENT". CMake Warning (dev) in CMakeLists.txt: No cmake_minimum_required command is present. A line of code such as cmake_minimum_required(VERSION 2.8) should be added at the top of the file. The version specified may be lower if you wish to support older CMake versions for this project. For more information run "cmake --help-policy CMP". This warning is for project developers. Use -Wno-dev to suppress it. -- Configuring incomplete, errors occurred! See also "/home/spclab/Desktop/Monika/GNURADIO/gnuradio-3.7.5.1/gr-digital/build/CMakeFiles/CMakeOutput.log". What should i do ? have i done something wrong ? On Sat, Jul 18, 2015 at 11:37 AM, monika bansal wrote: > yes... i will. > > On Fri, Jul 17, 2015 at 9:48 PM, Martin Braun > wrote: > >> Monika, >> >> please make sure you've gone through the tutorials at >> http://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorials, to >> make sure we're speaking the same terminology and all the basics are >> clear. >> >> Cheers, >> M >> >> On 17.07.2015 06:20, monika bansal wrote: >> > Ok... Thanks :) >> > >> > On Fri, Jul 17, 2015 at 6:47 PM, Marcus Müller < >> marcus.muel...@ettus.com >> > <mailto:marcus.muel...@ettus.com>> wrote: >> > >> > You can of course add that later on, but don't forget to change both >> > your include/blockname.h, your lib/blockname_impl.h and your >> > lib/blockname_impl.cc. If you want to work with GRC, remember to >> > edit the .xml in grc/, too! >> > >> > Best regards, >> > Marcus >> > >> > PS: gr_modtool doesn't do anything magical; it really just adds >> > files with the content you specify. I'd like to encourage you to try >> > around a bit more! You can't break much. And with version control >> > (git) having your back, you can hardly do any harm even to your own >> > work :) >> > >> > >> > On 17.07.2015 14:38, monika bansal wrote: >> >> Hii >> >> One more doubt... >> >> As the gr-digital / include/ ofdm_chest_vcvc.h file have the >> >> argument list given as >> >> static sptr make( >> >> const std::vector &sync_symbol1, >> >> const std::vector &sync_symbol2, >> >> int n_data_symbols, >> >> int eq_noise_red_len=0, >> >> int max_carr_offset=-1, >> >> bool force_one_sync_symbol=false >> >> ); >> >> Do we need to give Argument list at time of gr_modtool add when it >> >> asks... Or we can add it later if we are not sure at the time of >> >> adding new block. >> >> >> >> On Fri, Jul 17, 2015 at 5:42 PM, monika bansal >> >> mailto:monika19...@gmail.com>> wrote: >> >> >> >> Thanks... >> >> >> >> On Fri, Jul 17, 2015 at 5:16 PM, Marcus Müller >> >> mailto:marcus.muel...@ettus.com>> >> >> wrote: >> >> >> >> Hi Monika, >> >> >> >> absolutely the same method: >> >> >> >> cd gr-exisitingmodule >> >> gr_modtool add >> >> >> >> Note that this can only work with modules that follow >> >> gr_modtool's conventions (i.e. practically only with >>
Re: [Discuss-gnuradio] OFDM channel Estimation Block
yes... i will. On Fri, Jul 17, 2015 at 9:48 PM, Martin Braun wrote: > Monika, > > please make sure you've gone through the tutorials at > http://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorials, to > make sure we're speaking the same terminology and all the basics are clear. > > Cheers, > M > > On 17.07.2015 06:20, monika bansal wrote: > > Ok... Thanks :) > > > > On Fri, Jul 17, 2015 at 6:47 PM, Marcus Müller > <mailto:marcus.muel...@ettus.com>> wrote: > > > > You can of course add that later on, but don't forget to change both > > your include/blockname.h, your lib/blockname_impl.h and your > > lib/blockname_impl.cc. If you want to work with GRC, remember to > > edit the .xml in grc/, too! > > > > Best regards, > > Marcus > > > > PS: gr_modtool doesn't do anything magical; it really just adds > > files with the content you specify. I'd like to encourage you to try > > around a bit more! You can't break much. And with version control > > (git) having your back, you can hardly do any harm even to your own > > work :) > > > > > > On 17.07.2015 14:38, monika bansal wrote: > >> Hii > >> One more doubt... > >> As the gr-digital / include/ ofdm_chest_vcvc.h file have the > >> argument list given as > >> static sptr make( > >> const std::vector &sync_symbol1, > >> const std::vector &sync_symbol2, > >> int n_data_symbols, > >> int eq_noise_red_len=0, > >> int max_carr_offset=-1, > >> bool force_one_sync_symbol=false > >> ); > >> Do we need to give Argument list at time of gr_modtool add when it > >> asks... Or we can add it later if we are not sure at the time of > >> adding new block. > >> > >> On Fri, Jul 17, 2015 at 5:42 PM, monika bansal > >> mailto:monika19...@gmail.com>> wrote: > >> > >> Thanks... > >> > >> On Fri, Jul 17, 2015 at 5:16 PM, Marcus Müller > >> mailto:marcus.muel...@ettus.com>> > >> wrote: > >> > >> Hi Monika, > >> > >> absolutely the same method: > >> > >> cd gr-exisitingmodule > >> gr_modtool add > >> > >> Note that this can only work with modules that follow > >> gr_modtool's conventions (i.e. practically only with > >> modules generated with gr_modtool in the first place) > >> > >> Best regards, > >> Marcus > >> > >> > >> On 17.07.2015 13:01, monika bansal wrote: > >>> Hii > >>> > >>> I understood how to create new module and block within > >>> this new module using gr-modtool from > >>> > http://gnuradio.org/redmine/projects/gnuradio/wiki/OutOfTreeModules. > >>> I want to add new block in the existing module. How can i > >>> do that ? > >>> > >>> > >>> ___ > >>> Discuss-gnuradio mailing list > >>> Discuss-gnuradio@gnu.org <mailto:Discuss-gnuradio@gnu.org> > >>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > >> > >> > >> ___ > >> Discuss-gnuradio mailing list > >> Discuss-gnuradio@gnu.org <mailto: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 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] OFDM channel Estimation Block
Ok... Thanks :) On Fri, Jul 17, 2015 at 6:47 PM, Marcus Müller wrote: > You can of course add that later on, but don't forget to change both your > include/blockname.h, your lib/blockname_impl.h and your > lib/blockname_impl.cc. If you want to work with GRC, remember to edit the > .xml in grc/, too! > > Best regards, > Marcus > > PS: gr_modtool doesn't do anything magical; it really just adds files with > the content you specify. I'd like to encourage you to try around a bit > more! You can't break much. And with version control (git) having your > back, you can hardly do any harm even to your own work :) > > > On 17.07.2015 14:38, monika bansal wrote: > > Hii > One more doubt... > As the gr-digital / include/ ofdm_chest_vcvc.h file have the argument > list given as > static sptr make( > const std::vector &sync_symbol1, > const std::vector &sync_symbol2, > int n_data_symbols, > int eq_noise_red_len=0, > int max_carr_offset=-1, > bool force_one_sync_symbol=false > ); > Do we need to give Argument list at time of gr_modtool add when it > asks... Or we can add it later if we are not sure at the time of adding new > block. > > On Fri, Jul 17, 2015 at 5:42 PM, monika bansal > wrote: > >> Thanks... >> >> On Fri, Jul 17, 2015 at 5:16 PM, Marcus Müller >> wrote: >> >>> Hi Monika, >>> >>> absolutely the same method: >>> >>> cd gr-exisitingmodule >>> gr_modtool add >>> >>> Note that this can only work with modules that follow gr_modtool's >>> conventions (i.e. practically only with modules generated with gr_modtool >>> in the first place) >>> >>> Best regards, >>> Marcus >>> >>> >>> On 17.07.2015 13:01, monika bansal wrote: >>> >>>Hii >>> >>> I understood how to create new module and block within this new module >>> using gr-modtool from >>> http://gnuradio.org/redmine/projects/gnuradio/wiki/OutOfTreeModules. >>> I want to add new block in the existing module. How can i do that ? >>> >>> >>> ___ >>> Discuss-gnuradio mailing >>> listDiscuss-gnuradio@gnu.orghttps://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 mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] OFDM channel Estimation Block
Hii One more doubt... As the gr-digital / include/ ofdm_chest_vcvc.h file have the argument list given as static sptr make( const std::vector &sync_symbol1, const std::vector &sync_symbol2, int n_data_symbols, int eq_noise_red_len=0, int max_carr_offset=-1, bool force_one_sync_symbol=false ); Do we need to give Argument list at time of gr_modtool add when it asks... Or we can add it later if we are not sure at the time of adding new block. On Fri, Jul 17, 2015 at 5:42 PM, monika bansal wrote: > Thanks... > > On Fri, Jul 17, 2015 at 5:16 PM, Marcus Müller > wrote: > >> Hi Monika, >> >> absolutely the same method: >> >> cd gr-exisitingmodule >> gr_modtool add >> >> Note that this can only work with modules that follow gr_modtool's >> conventions (i.e. practically only with modules generated with gr_modtool >> in the first place) >> >> Best regards, >> Marcus >> >> >> On 17.07.2015 13:01, monika bansal wrote: >> >> Hii >> >> I understood how to create new module and block within this new module >> using gr-modtool from >> http://gnuradio.org/redmine/projects/gnuradio/wiki/OutOfTreeModules. >> I want to add new block in the existing module. How can i do that ? >> >> >> ___ >> Discuss-gnuradio mailing >> listDiscuss-gnuradio@gnu.orghttps://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 mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] OFDM channel Estimation Block
Hii I understood how to create new module and block within this new module using gr-modtool from http://gnuradio.org/redmine/projects/gnuradio/wiki/OutOfTreeModules. I want to add new block in the existing module. How can i do that ? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] OFDM channel Estimation Block
Hiii In the OFDM Channel estimation block, ML estimation has been used. I want to do MMSE estimation. How should i proceed? Should i make new module for this or I can add new block in gr-digital? For MMSE estimator i will need noise variance as well. How can i get that ? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Creating New Module
Yes, this should be the problem. On Wed, Jul 15, 2015 at 4:41 PM, Marcus Müller wrote: > This sounds like your upgrade was only half-complete. Ubuntu 14.04 > doesn't come with boost 1.48, but with the conflicting 1.54, so all the > 1.48 packages should have been auto-removed. > > > > On 15.07.2015 13:08, monika bansal wrote: > > Can't i just remove the existing Boost and install the new version > compatible with ubuntu 14.04 ? > > On Wed, Jul 15, 2015 at 4:24 PM, monika bansal > wrote: > >> My system has Ubuntu 14.04 which i upgraded from Ubuntu 12.04. >> This may be because of upgrade issue or something else that i don't >> know. >> >> On Wed, Jul 15, 2015 at 4:15 PM, Marcus Müller >> wrote: >> >>> Not necessarily, but you'd need to sort out why there is a single boost >>> package from Ubuntu 14.04 on your Ubuntu 12.04. That can be easy, but >>> often, these administrative problems turn out to be something strange >>> underneath, and you end up fixing things for hours, where a fresh >>> installation would have been done in a couple of minutes. It basically >>> depends on your willingness to repair your old system. >>> >>> Best regards, >>> Marcus >>> >>> >>> On 15.07.2015 12:39, monika bansal wrote: >>> >>> Thanks... >>> This means i need to re-install Ubuntu and then gnuradio for proper >>> working. >>> >>> On Wed, Jul 15, 2015 at 3:56 PM, Marcus Müller >> > wrote: >>> >>>> Hi Monika, >>>> >>>> there's something strange in your package versions: >>>> On 15.07.2015 07:57, monika bansal wrote: >>>> >>>> ii libboost-date-ti 1.48.0-3 amd64 set of date-time >>>> libraries based on ge >>>> ii libboost-date-ti 1.48.0-3 amd64 set of date-time >>>> libraries based on ge >>>> ii libboost-date-ti 1.54.0-4ubunt amd64 set of date-time >>>> libraries based on ge >>>> >>>> I know there were strange times when Ubuntu shipped packages that >>>> said "boost-something version 1.X" but contained a different version than >>>> X, but I though these days were over. >>>> Now, 1.48.0 is the Boost version of Ubuntu 12.04LTS, and we still do >>>> support that, but 1.54 is the Ubuntu 14.04LTS version; I think there might >>>> be something broken, here. >>>> >>>> To be honest, I'd rather do a clean install of Ubuntu 14.04LTS and >>>> start with that before I ran into more problems. >>>> >>>> Best regards, >>>> Marcus >>>> >>>> ___ >>>> 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] Creating New Module
Can't i just remove the existing Boost and install the new version compatible with ubuntu 14.04 ? On Wed, Jul 15, 2015 at 4:24 PM, monika bansal wrote: > My system has Ubuntu 14.04 which i upgraded from Ubuntu 12.04. > This may be because of upgrade issue or something else that i don't know. > > On Wed, Jul 15, 2015 at 4:15 PM, Marcus Müller > wrote: > >> Not necessarily, but you'd need to sort out why there is a single boost >> package from Ubuntu 14.04 on your Ubuntu 12.04. That can be easy, but >> often, these administrative problems turn out to be something strange >> underneath, and you end up fixing things for hours, where a fresh >> installation would have been done in a couple of minutes. It basically >> depends on your willingness to repair your old system. >> >> Best regards, >> Marcus >> >> >> On 15.07.2015 12:39, monika bansal wrote: >> >> Thanks... >> This means i need to re-install Ubuntu and then gnuradio for proper >> working. >> >> On Wed, Jul 15, 2015 at 3:56 PM, Marcus Müller >> wrote: >> >>> Hi Monika, >>> >>> there's something strange in your package versions: >>> On 15.07.2015 07:57, monika bansal wrote: >>> >>> ii libboost-date-ti 1.48.0-3 amd64 set of date-time libraries >>> based on ge >>> ii libboost-date-ti 1.48.0-3 amd64 set of date-time libraries >>> based on ge >>> ii libboost-date-ti 1.54.0-4ubunt amd64 set of date-time libraries >>> based on ge >>> >>> I know there were strange times when Ubuntu shipped packages that said >>> "boost-something version 1.X" but contained a different version than X, but >>> I though these days were over. >>> Now, 1.48.0 is the Boost version of Ubuntu 12.04LTS, and we still do >>> support that, but 1.54 is the Ubuntu 14.04LTS version; I think there might >>> be something broken, here. >>> >>> To be honest, I'd rather do a clean install of Ubuntu 14.04LTS and start >>> with that before I ran into more problems. >>> >>> Best regards, >>> Marcus >>> >>> ___ >>> 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] Creating New Module
My system has Ubuntu 14.04 which i upgraded from Ubuntu 12.04. This may be because of upgrade issue or something else that i don't know. On Wed, Jul 15, 2015 at 4:15 PM, Marcus Müller wrote: > Not necessarily, but you'd need to sort out why there is a single boost > package from Ubuntu 14.04 on your Ubuntu 12.04. That can be easy, but > often, these administrative problems turn out to be something strange > underneath, and you end up fixing things for hours, where a fresh > installation would have been done in a couple of minutes. It basically > depends on your willingness to repair your old system. > > Best regards, > Marcus > > > On 15.07.2015 12:39, monika bansal wrote: > > Thanks... > This means i need to re-install Ubuntu and then gnuradio for proper > working. > > On Wed, Jul 15, 2015 at 3:56 PM, Marcus Müller > wrote: > >> Hi Monika, >> >> there's something strange in your package versions: >> On 15.07.2015 07:57, monika bansal wrote: >> >> ii libboost-date-ti 1.48.0-3 amd64 set of date-time libraries >> based on ge >> ii libboost-date-ti 1.48.0-3 amd64 set of date-time libraries >> based on ge >> ii libboost-date-ti 1.54.0-4ubunt amd64 set of date-time libraries >> based on ge >> >> I know there were strange times when Ubuntu shipped packages that said >> "boost-something version 1.X" but contained a different version than X, but >> I though these days were over. >> Now, 1.48.0 is the Boost version of Ubuntu 12.04LTS, and we still do >> support that, but 1.54 is the Ubuntu 14.04LTS version; I think there might >> be something broken, here. >> >> To be honest, I'd rather do a clean install of Ubuntu 14.04LTS and start >> with that before I ran into more problems. >> >> Best regards, >> Marcus >> >> ___ >> 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] Creating New Module
Thanks... This means i need to re-install Ubuntu and then gnuradio for proper working. On Wed, Jul 15, 2015 at 3:56 PM, Marcus Müller wrote: > Hi Monika, > > there's something strange in your package versions: > On 15.07.2015 07:57, monika bansal wrote: > > ii libboost-date-ti 1.48.0-3 amd64 set of date-time libraries > based on ge > ii libboost-date-ti 1.48.0-3 amd64 set of date-time libraries > based on ge > ii libboost-date-ti 1.54.0-4ubunt amd64 set of date-time libraries > based on ge > > I know there were strange times when Ubuntu shipped packages that said > "boost-something version 1.X" but contained a different version than X, but > I though these days were over. > Now, 1.48.0 is the Boost version of Ubuntu 12.04LTS, and we still do > support that, but 1.54 is the Ubuntu 14.04LTS version; I think there might > be something broken, here. > > To be honest, I'd rather do a clean install of Ubuntu 14.04LTS and start > with that before I ran into more problems. > > Best regards, > Marcus > > ___ > 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] BER vs SNR graph
How to run berawgn.py in GRC ? I think this is a trivial question. I know that GRC makes the python file when we compile the flow graph . But i don't know how to run Python file in GRC... On Wed, Jul 15, 2015 at 1:52 PM, monika bansal wrote: > Thanks.. > I will look. I will ask again if got some problem or doubt :) > > On Wed, Jul 15, 2015 at 11:45 AM, monika bansal > wrote: > >> Thanks.. >> I will look. I will ask again if got some problem or doubt :) >> >> On Tue, Jul 14, 2015 at 11:50 PM, Arturo Rinaldi >> wrote: >> >>> Take a look at my thesis research in the academic papers section : >>> >>> https://app.box.com/s/5b8f1335df54af91b9cf >>> >>> "Emulation of a radio link by means of software radio". It might help >>> you understanding the used approach to the problem. >>> >>> Arturo >>> >> >> > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] BER vs SNR graph
Thanks.. I will look. I will ask again if got some problem or doubt :) On Wed, Jul 15, 2015 at 11:45 AM, monika bansal wrote: > Thanks.. > I will look. I will ask again if got some problem or doubt :) > > On Tue, Jul 14, 2015 at 11:50 PM, Arturo Rinaldi > wrote: > >> Take a look at my thesis research in the academic papers section : >> >> https://app.box.com/s/5b8f1335df54af91b9cf >> >> "Emulation of a radio link by means of software radio". It might help you >> understanding the used approach to the problem. >> >> Arturo >> > > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Creating New Module
iption available) ii libboost-seriali 1.46.1-7ubunt amd64 serialization library for C++ ii libboost-seriali 1.48.0-3 amd64 serialization library for C++ ii libboost-seriali 1.48.0-3 amd64 serialization library for C++ un libboost-signals (no description available) un libboost-signals (no description available) ii libboost-signals 1.48.0-3 amd64 managed signals and slots library for ii libboost-signals 1.48.0-3 amd64 managed signals and slots library for un libboost-system1 (no description available) un libboost-system1 (no description available) ii libboost-system1 1.48.0-3 amd64 Operating system (e.g. diagnostics sup ii libboost-system1 1.48.0-3 amd64 Operating system (e.g. diagnostics sup ii libboost-system1 1.54.0-4ubunt amd64 Operating system (e.g. diagnostics sup un libboost-test1.4 (no description available) un libboost-test1.4 (no description available) ii libboost-test1.4 1.48.0-3 amd64 components for writing and executing t ii libboost-test1.4 1.48.0-3 amd64 components for writing and executing t un libboost-thread1 (no description available) un libboost-thread1 (no description available) ii libboost-thread1 1.46.1-7ubunt amd64 portable C++ multi-threading ii libboost-thread1 1.48.0-3 amd64 portable C++ multi-threading ii libboost-thread1 1.48.0-3 amd64 portable C++ multi-threading ii libboost-thread1 1.54.0-4ubunt amd64 portable C++ multi-threading ii libboost-timer1. 1.48.0-3 amd64 C++ wall clock and CPU process timers ii libboost-timer1. 1.48.0-3 amd64 C++ wall clock and CPU process timers un libboost-wave1.4 (no description available) un libboost-wave1.4 (no description available) ii libboost-wave1.4 1.48.0-3 amd64 C99/C++ preprocessor library ii libboost-wave1.4 1.48.0-3 amd64 C99/C++ preprocessor library un libboost1.42-dev (no description available) un libboost1.46-dev (no description available) ii libboost1.48-all 1.48.0-3 amd64 Boost C++ Libraries development files ii libboost1.48-dev 1.48.0-3 amd64 Boost C++ Libraries development files un libboost1.48-doc (no description available) Do i need to update ? On Wed, Jul 15, 2015 at 11:25 AM, monika bansal wrote: > Hii, > > gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) > > I think Boost version is 1.48.0-3 > > > I run the command " dpkg -l '*boost*' " and i got > > > > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Name Version Architecture Description > +++--=-=-== > un boost-build (no description available) > ii libboost-chrono1 1.48.0-3 amd64 C++ representation of time > duration, t > ii libboost-chrono1 1.48.0-3 amd64 C++ representation of time > duration, t > un libboost-date-ti (no description available) > un libboost-date-ti (no description available) > ii libboost-date-ti 1.48.0-3 amd64 set of date-time libraries > based on ge > ii libboost-date-ti 1.48.0-3 amd64 set of date-time libraries > based on ge > ii libboost-date-ti 1.54.0-4ubunt amd64 set of date-time libraries > based on ge > un libboost-filesys (no description available) > un libboost-filesys (no description available) > ii libboost-filesys 1.48.0-3 amd64 filesystem operations > (portable paths, > ii libboost-filesys 1.48.0-3 amd64 filesystem operations > (portable paths, > un libboost-graph-p (no description available) > un libboost-graph-p (no description available) > ii libboost-graph-p 1.48.0-3 amd64 generic graph components and > algorithm > ii libboost-graph-p 1.48.0-3 amd64 generic graph components and > algorithm > un libboost-graph1. (no description available) > un libboost-graph1. (no description available) > ii libboost-graph1. 1.48.0-3 amd64 generic graph components and > algorithm > ii libboost-graph1. 1.48.0-3 amd64 generic graph components and > algorithm > un libboost-iostrea (no description available) > un libboost-iostrea (no description availa
[Discuss-gnuradio] Creating New Module
I am trying to make the module from https://gnuradio.org/redmine/projects/gnuradio/wiki/OutOfTreeModules I am following the same steps. Till "cmake ../ " everything has correctly done. But when i m running "make" the following error comes. please help :) Scanning dependencies of target gnuradio-howto [ 6%] Building CXX object lib/CMakeFiles/gnuradio-howto.dir/square_ff_impl.cc.o In file included from /usr/include/boost/smart_ptr/detail/yield_k.hpp:89:0, from /usr/include/boost/smart_ptr/detail/spinlock_sync.hpp:18, from /usr/include/boost/smart_ptr/detail/spinlock.hpp:41, from /usr/include/boost/smart_ptr/detail/spinlock_pool.hpp:25, from /usr/include/boost/smart_ptr/shared_ptr.hpp:37, from /usr/include/boost/shared_ptr.hpp:17, from /usr/local/include/gnuradio/types.h:27, from /usr/local/include/gnuradio/runtime_types.h:27, from /usr/local/include/gnuradio/io_signature.h:27, from /home/spclab/Desktop/Monika/gr-howto/lib/square_ff_impl.cc:25: /usr/include/boost/thread/xtime.hpp:23:5: error: expected identifier before numeric constant TIME_UTC=1 ^ /usr/include/boost/thread/xtime.hpp:23:5: error: expected ‘}’ before numeric constant /usr/include/boost/thread/xtime.hpp:23:5: error: expected unqualified-id before numeric constant In file included from /usr/include/boost/thread/pthread/mutex.hpp:14:0, from /usr/include/boost/thread/mutex.hpp:16, from /usr/include/boost/thread/pthread/thread_data.hpp:12, from /usr/include/boost/thread/thread.hpp:17, from /usr/local/include/gnuradio/thread/thread.h:26, from /usr/local/include/gnuradio/basic_block.h:31, from /usr/local/include/gnuradio/block.h:27, from /home/spclab/Desktop/Monika/gr-howto/include/howto/square_ff.h:26, from /home/spclab/Desktop/Monika/gr-howto/lib/square_ff_impl.h:24, from /home/spclab/Desktop/Monika/gr-howto/lib/square_ff_impl.cc:26: /usr/include/boost/thread/xtime.hpp:46:14: error: expected type-specifier before ‘system_time’ operator system_time() const ^ In file included from /usr/include/boost/thread/pthread/mutex.hpp:14:0, from /usr/include/boost/thread/mutex.hpp:16, from /usr/include/boost/thread/pthread/thread_data.hpp:12, from /usr/include/boost/thread/thread.hpp:17, from /usr/local/include/gnuradio/thread/thread.h:26, from /usr/local/include/gnuradio/basic_block.h:31, from /usr/local/include/gnuradio/block.h:27, from /home/spclab/Desktop/Monika/gr-howto/include/howto/square_ff.h:26, from /home/spclab/Desktop/Monika/gr-howto/lib/square_ff_impl.h:24, from /home/spclab/Desktop/Monika/gr-howto/lib/square_ff_impl.cc:26: /usr/include/boost/thread/xtime.hpp: In function ‘int xtime_get(xtime*, int)’: /usr/include/boost/thread/xtime.hpp:73:40: error: ‘get_system_time’ was not declared in this scope *xtp=get_xtime(get_system_time()); ^ /usr/include/boost/thread/xtime.hpp:73:40: note: suggested alternative: In file included from /usr/include/boost/thread/locks.hpp:12:0, from /usr/include/boost/thread/pthread/mutex.hpp:12, from /usr/include/boost/thread/mutex.hpp:16, from /usr/include/boost/thread/pthread/thread_data.hpp:12, from /usr/include/boost/thread/thread.hpp:17, from /usr/local/include/gnuradio/thread/thread.h:26, from /usr/local/include/gnuradio/basic_block.h:31, from /usr/local/include/gnuradio/block.h:27, from /home/spclab/Desktop/Monika/gr-howto/include/howto/square_ff.h:26, from /home/spclab/Desktop/Monika/gr-howto/lib/square_ff_impl.h:24, from /home/spclab/Desktop/Monika/gr-howto/lib/square_ff_impl.cc:26: /usr/include/boost/thread/thread_time.hpp:19:24: note: ‘boost::get_system_time’ inline system_time get_system_time() ^ In file included from /usr/include/boost/thread/pthread/mutex.hpp:14:0, from /usr/include/boost/thread/mutex.hpp:16, from /usr/include/boost/thread/pthread/thread_data.hpp:12, from /usr/include/boost/thread/thread.hpp:17, from /usr/local/include/gnuradio/thread/thread.h:26, from /usr/local/include/gnuradio/basic_block.h:31, from /usr/local/include/gnuradio/block.h:27, from /home/spclab/Desktop/Monika/gr-howto/include/howto/square_ff.h:26, from /home/spclab/Desktop/Monika/gr-howto/lib/square_ff_impl.h:24, from /home/spclab/Desktop/Monika/gr-howto
[Discuss-gnuradio] BER vs SNR graph
Hii I want to generate BER vs SNR graph for BPSK and match it with the theoritical result. Is there any block which i can use? If not what should i do ? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] stream ID in virtual source Block
Thanks... i got it. On Wed, Jun 3, 2015 at 7:08 PM, Francisco Albani wrote: > Hi Monika. > > Remember that the Virtual Source's output is just the input of the > Virtual Sink with the same ID. > > It is a convenient way of making a nicer and tidier graph without so > many "wires". > > I use them also as a "signal copier": > > (something X) ---> Virtual Sink ID 1 > > Virtual Source ID 1 > one copy of X > -> another copy of X > --> etc > [...] > --> etc > > This way I don't have to remake all the connections when I change X. > > Bye. > > 2015-06-03 9:18 GMT-03:00 Marcus Müller : > > That's because you made a loop, and that's illegal; why do you feed the > > output of the OFDM CP back into the carrier allocator? > > > > Best regards, > > Marcus > > > > > > On 06/03/2015 12:37 PM, monika bansal wrote: > > > > hii > > i made the following Flowgraph : > > > > Virtual Source -> OFDM Carrier allocator > FFT ---> OFDM > > Cyclic Prefixer -> Virtual Sink > > > > When i am executing the flowgraph it says -- "runtime error : flowgraph > has > > loops ! ". > > What should i do ? > > > > On Wed, Jun 3, 2015 at 3:26 PM, monika bansal > wrote: > >> > >> Thanks Marcus ... > >> > >> On Wed, Jun 3, 2015 at 3:23 PM, Marcus Müller > > >> wrote: > >>> > >>> That's totally up to you -- any text that you can remember. > >>> You'd put the same value into the Virtual Sink block's stream ID, so > that > >>> they are connected. > >>> > >>> On 06/03/2015 11:28 AM, monika bansal wrote: > >>> > >>> Hii > >>> What should i input in the "stream ID" field of Virtual Source block? > >>> > >>> > >>> ___ > >>> 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 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 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] stream ID in virtual source Block
hii i made the following Flowgraph : Virtual Source -> OFDM Carrier allocator > FFT ---> OFDM Cyclic Prefixer -> Virtual Sink When i am executing the flowgraph it says -- "runtime error : flowgraph has loops ! ". What should i do ? On Wed, Jun 3, 2015 at 3:26 PM, monika bansal wrote: > Thanks Marcus ... > > On Wed, Jun 3, 2015 at 3:23 PM, Marcus Müller > wrote: > >> That's totally up to you -- any text that you can remember. >> You'd put the same value into the Virtual Sink block's stream ID, so that >> they are connected. >> >> On 06/03/2015 11:28 AM, monika bansal wrote: >> >> Hii >> What should i input in the "stream ID" field of Virtual Source block? >> >> >> ___ >> Discuss-gnuradio mailing >> listDiscuss-gnuradio@gnu.orghttps://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 mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] stream ID in virtual source Block
Thanks Marcus ... On Wed, Jun 3, 2015 at 3:23 PM, Marcus Müller wrote: > That's totally up to you -- any text that you can remember. > You'd put the same value into the Virtual Sink block's stream ID, so that > they are connected. > > On 06/03/2015 11:28 AM, monika bansal wrote: > > Hii > What should i input in the "stream ID" field of Virtual Source block? > > > ___ > Discuss-gnuradio mailing > listDiscuss-gnuradio@gnu.orghttps://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 mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] stream ID in virtual source Block
Hii What should i input in the "stream ID" field of Virtual Source block? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio