Re : Discuss-gnuradio Digest, Vol 124, Issue 9

USRP2 IP new address
Message-ID: [email protected]
Content-Type: text/plain; charset=ISO-8859-1

On 03/08/2013 06:48 AM, guelord ingala wrote:

Hi,
Can you please assist me to change the usrp2 IP address. I went through the
application note.
Method 1 responds that I don’t have permission.

Method 2 goes well loading the new IP address: 192.168.10.3. But when I
checked with uhd_find_devices, it shows that the IP address has not
changed. It’s still 192.168.10.2.

Even after power cycle?

-josh
Hi Josh,
I don’t know about power cycle. What does it means. Please help.
Thanks.

Your help will be appreciated.

— En date de: Sam 9.3.13, [email protected]
[email protected] a crit:

De: [email protected] [email protected]
Objet: Discuss-gnuradio Digest, Vol 124, Issue 9
: [email protected]
Date: Samedi 9 mars 2013, 18h00

Send Discuss-gnuradio mailing list submissions to
[email protected]

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
or, via email, send a message with subject or body ‘help’ to
[email protected]

You can reach the person managing the list at
[email protected]

When replying, please edit your Subject line so it is more specific
than “Re: Contents of Discuss-gnuradio digest…”

Today’s Topics:

  1. Re: RF/Data Acquisition Hardware Supported (Nathan W.)
  2. Re: USRP2 IP new address (Josh B.)
  3. Re: In need of signal samples (Marcus M?ller)
  4. Re: How to get transmitted packet time in USRP? (Josh B.)
  5. Re: Terminal commands (Marcus M?ller)
  6. Re: LibUSRP vs LibUHD Performance on older machines (Tom H.)
  7. Re: Number of bits tranmitted (manjusha)
  8. How to know the number of bits/packets transmitted (manjusha)
  9. Re: How to know the number of bits/packets transmitted (manjusha)
  10. Re: How to know the number of bits/packets transmitted
    (Tommy T. II)
  11. Re: How to know the number of bits/packets transmitted (manjusha)
  12. Re: How to know the number of bits/packets transmitted
    (Nathan W.)
  13. bit error rate (manjusha)
  14. Any one know rfx board i q imbalance value (James Jordan)
  15. Re: bit error rate (Brian P.)
  16. Re: bit error rate (Nathan W.)
  17. Re: Number of bits tranmitted (Tommy T. II)
  18. Re: Any one know rfx board i q imbalance value (Matt E.)

Message: 1
Date: Fri, 8 Mar 2013 11:21:44 -0600
From: Nathan W. [email protected]
To: Juan Daniel Fernandez M. [email protected]
Cc: “[email protected][email protected]
Subject: Re: [Discuss-gnuradio] RF/Data Acquisition Hardware Supported
Message-ID:
[email protected]main.invalid
Content-Type: text/plain; charset=“ISO-8859-1”

2013/3/8 Juan Daniel Fernandez M. [email protected]:

Hi everyone,

Which is the harware supported by GNU Radio for data acquisition? (besides
USRP)

http://gnuradio.org/redmine/projects/gnuradio/wiki/Hardware


Message: 2
Date: Fri, 08 Mar 2013 11:32:18 -0600
From: Josh B. [email protected]
To: [email protected]
Subject: Re: [Discuss-gnuradio] USRP2 IP new address
Message-ID: [email protected]
Content-Type: text/plain; charset=ISO-8859-1

On 03/08/2013 06:48 AM, guelord ingala wrote:

Hi,
Can you please assist me to change the usrp2 IP address. I went through the
application note.
Method 1 responds that I don’t have permission.

Method 2 goes well loading the new IP address: 192.168.10.3. But when I checked
with uhd_find_devices, it shows that the IP address has not changed. It’s still
192.168.10.2.

Even after power cycle?

-josh

https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Message: 3
Date: Fri, 08 Mar 2013 19:17:52 +0100
From: Marcus M?ller [email protected]
To: [email protected]
Subject: Re: [Discuss-gnuradio] In need of signal samples
Message-ID: [email protected]
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi Matt,

sorry, since P25 is not really available somewhere in Europe,
I can’t help you with samples but: The folks over
at http://op25.osmocom.org/wiki used to link to samples
(But that link’s gone now), best ask them :slight_smile:

Happy receiving, decoding and p25ing,

Marcus M?ller
Am 08.03.2013 16:29, schrieb [email protected]:

[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Message: 4
Date: Fri, 08 Mar 2013 12:21:57 -0600
From: Josh B. [email protected]
To: john jade [email protected]
Cc: [email protected]
Subject: Re: [Discuss-gnuradio] How to get transmitted packet time in
USRP?
Message-ID: [email protected]
Content-Type: text/plain; charset=ISO-8859-1

On 03/07/2013 09:19 PM, john jade wrote:

boost::shared_ptr<tag_source_demo> tag_source =
boost::make_shared<tag_source_demo>(
time_now.get_full_secs() + 1, time_now.get_frac_secs(), //time now

  • 1 second
    samp_rate, idle_dur, burst_dur
    );
    to get time.
  1. Here TIME_NOW is mother board time or something else?

it was the time on the motherboard

  1. What should i do if i have to get time in nanoseconds?

The time format of the tag is just a tuple of full and fractional
seconds,

But if you are taking about that time_now, that was just to get an idea
of what time the device was on. You can read this value, or set it to a
known starting point like UTC. In any case, see the
uhd/types/time_spec.hpp, you can readily convert between that and
seconds if need be.

3.Is there any option to do it in python?

Yes, tags can be created in python, I hope this is documented in the
blocks coding guide

Hope that helps!

I am using 2 USRPN210 devices one for transmitting and one for receiving

Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Message: 5
Date: Fri, 08 Mar 2013 19:30:41 +0100
From: Marcus M?ller [email protected]
To: [email protected]
Subject: Re: [Discuss-gnuradio] Terminal commands
Message-ID: [email protected]
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi Manjusha,

what you most propably want to do is something of the like

ncat -l -u 12346

to see what your deframer spits out.

To see what your transmitter is going to transmit, you should
use whatever software generates the data and sends it to port 12345.
Presuming you’re using the ubiquitous bash, you can use something like

ncat -u 12345 < mylovelettertognuradio.txt

Three Notes anyway:

  1. That data will be binary. If you don’t input bytes that map to
    “readable” characters, you won’t see much meaningfulness on your
    terminal.
  2. Transmitting and receiving simultaneously on the same daughterboard
    is tough, to be honest. The crosstalk is most propably stronger than
    your reception. Be warned.
  3. Is UDP really the protocol of your choice in both cases?

Happy Hacking!

Marcus M?ller

Am 07.03.2013 18:36, schrieb manjusha:


Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Message: 6
Date: Fri, 8 Mar 2013 12:44:21 -0800 (PST)
From: Tom H. [email protected]
To: “[email protected][email protected]
Cc: “[email protected][email protected]
Subject: Re: [Discuss-gnuradio] LibUSRP vs LibUHD Performance on older
machines
Message-ID:
[email protected]
Content-Type: text/plain; charset=“iso-8859-1”

Hi Josh,

Would you happen to suggest any more setting changes I could try before
just deciding I need to depend on the older libusrp/gnuradio for
recording 4 channels to disk from a USRP?
Thanks, - Tom


From: Josh B. [email protected]
To: Tom H. [email protected]
Cc: “[email protected][email protected]
Sent: Saturday, March 2, 2013 9:18 AM
Subject: Re: [Discuss-gnuradio] LibUSRP vs LibUHD Performance on older
machines

On 03/01/2013 05:16 PM, Tom H. wrote:

Josh,

Thank you so much for the suggestion. I will try this.? I have 4GB of
ram and a 4GB swapfile size.? Do you recommend any particular setting
for set_max_output_buffer(long max_output_buffer)?

Make it 10s of megabytes, see if it helps.

Should I leave tb.run() as is, or modify the number of n_output_items
in conjunction with the

I think that part of the API is deprecated (the argument to run). There
is a similar call on top block, but Im recommending just the usrp source
block.

older gnuradio version had the fusb_block and? fusb_nblocks both set
to 512*32

Go with the default while trying the above.

-josh

I’ve made this 4 channel work successfully with the same exact
leave my dual boot setup intact.
set_max_output_buffer(long max_output_buffer)
mailing list [email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

-------------- next part --------------
An HTML attachment was scrubbed…
URL:
http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20130308/369da39a/attachment.html


Message: 7
Date: Fri, 8 Mar 2013 16:02:05 -0800 (PST)
From: manjusha [email protected]
To: [email protected]
Subject: Re: [Discuss-gnuradio] Number of bits tranmitted
Message-ID: [email protected]
Content-Type: text/plain; charset=us-ascii

is there no wat to do it?


Manjusha

View this message in context:
http://gnuradio.4.n7.nabble.com/Number-of-bits-tranmitted-tp40046p40082.html
Sent from the GnuRadio mailing list archive at Nabble.com.


Message: 8
Date: Fri, 8 Mar 2013 16:09:14 -0800 (PST)
From: manjusha [email protected]
To: [email protected]
Subject: [Discuss-gnuradio] How to know the number of bits/packets
transmitted
Message-ID: [email protected]
Content-Type: text/plain; charset=us-ascii

I have the attached GRC file.i know it is transmitting a certain number
of
bits.But i want to see the number of bits being transmitted.Is there any
way
to do it? No_of_bits_transmitted.png
http://gnuradio.4.n7.nabble.com/file/n40083/No_of_bits_transmitted.png


Manjusha

View this message in context:
http://gnuradio.4.n7.nabble.com/How-to-know-the-number-of-bits-packets-transmitted-tp40083.html
Sent from the GnuRadio mailing list archive at Nabble.com.


Message: 9
Date: Fri, 8 Mar 2013 16:11:29 -0800 (PST)
From: manjusha [email protected]
To: [email protected]
Subject: Re: [Discuss-gnuradio] How to know the number of bits/packets
transmitted
Message-ID: [email protected]
Content-Type: text/plain; charset=us-ascii

or do i have to go through the entire .py code ,find the variables and
print
it??

Please help!!

Thanks.


Manjusha

View this message in context:
http://gnuradio.4.n7.nabble.com/How-to-know-the-number-of-bits-packets-transmitted-tp40083p40084.html
Sent from the GnuRadio mailing list archive at Nabble.com.


Message: 10
Date: Fri, 8 Mar 2013 19:19:55 -0500
From: Tommy T. II [email protected]
To: manjusha [email protected]
Cc: [email protected]
Subject: Re: [Discuss-gnuradio] How to know the number of bits/packets
transmitted
Message-ID: [email protected]
Content-Type: text/plain; charset=“us-ascii”

You have your input on repeat, so it’ll keep transmitting as long as the
program is running. Are you looking for the rate, or the total bit
count?

Tommy James Tracy II
Ph.D Student
High Performance Low Power Lab
University of Virginia
Phone: 913-775-2241

On Mar 8, 2013, at 7:11 PM, manjusha [email protected] wrote:

Manjusha

View this message in context:
http://gnuradio.4.n7.nabble.com/How-to-know-the-number-of-bits-packets-transmitted-tp40083p40084.html
Sent from the GnuRadio mailing list archive at Nabble.com.


Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

-------------- next part --------------
An HTML attachment was scrubbed…
URL:
http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20130308/a25bf280/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed…
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL:
http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20130308/a25bf280/attachment.pgp


Message: 11
Date: Fri, 8 Mar 2013 16:33:14 -0800 (PST)
From: manjusha [email protected]
To: [email protected]
Subject: Re: [Discuss-gnuradio] How to know the number of bits/packets
transmitted
Message-ID: [email protected]
Content-Type: text/plain; charset=us-ascii

Yes,you are right…I attached the wrong screen shot…My vector source
doesn’t
repeat and
I would like to know both Bit rate and Number of bits transmitted.

thanks.


Manjusha

View this message in context:
http://gnuradio.4.n7.nabble.com/How-to-know-the-number-of-bits-packets-transmitted-tp40083p40086.html
Sent from the GnuRadio mailing list archive at Nabble.com.


Message: 12
Date: Fri, 8 Mar 2013 18:37:59 -0600
From: Nathan W. [email protected]
To: manjusha [email protected]
Cc: [email protected]
Subject: Re: [Discuss-gnuradio] How to know the number of bits/packets
transmitted
Message-ID:
[email protected]
Content-Type: text/plain; charset=“ISO-8859-1”

On Fri, Mar 8, 2013 at 6:33 PM, manjusha [email protected]
wrote:

Yes,you are right…I attached the wrong screen shot…My vector source doesn’t
repeat and
I would like to know both Bit rate and Number of bits transmitted.

I’ve gotten the impression you’re looking for a bit count after some
amount of time has passed, similar to ifconfig’s “TX packets:”.

Mangusha, from other posts I’m thinking maybe you’re trying to connect
a socket to a modulator and transmitter and you want to know how many
bits have been transmitted. I’m certainly not going to be a definite
source on this, but I don’t think you can do this in grc without
writing any code.

Each of these blocks does have a variable (probably called something
similar to noutput_items) that you can use to accumulate a total and
add an output. If it’s really critical to your application I don’t
think it’s very difficult to edit one of these blocks to do it for
you. Or even better, just make your own block that does nothing but
count the number of items that goes through it.

If I’m over complicating things and you’re just trying to understand
your flowgraph…
I think your number of bits transmitted is 2.
Your bit rate is, uh I think something like samples/symbol / samp_rate.


Message: 13
Date: Fri, 8 Mar 2013 17:47:12 -0800 (PST)
From: manjusha [email protected]
To: [email protected]
Subject: [Discuss-gnuradio] bit error rate
Message-ID: [email protected]
Content-Type: text/plain; charset=us-ascii

ber_before_tx.png
http://gnuradio.4.n7.nabble.com/file/n40088/ber_before_tx.png
ber_tx.png http://gnuradio.4.n7.nabble.com/file/n40088/ber_tx.png

I am trying to find the Bit error rate for a vector signal.I get a error
rate of 0.528(i am assuming it to be 52%) when i don’t transmit and an
error rate of 0.625000 when i transmit.

Am i right on this??i dont understand the logic behind it…

Also,is 52% not too high??!!!

thank you


Manjusha

View this message in context:
http://gnuradio.4.n7.nabble.com/bit-error-rate-tp40088.html
Sent from the GnuRadio mailing list archive at Nabble.com.


Message: 14
Date: Sat, 9 Mar 2013 09:54:31 +0800
From: James Jordan [email protected]
To: discuss-gnuradio [email protected]
Subject: [Discuss-gnuradio] Any one know rfx board i q imbalance value
Message-ID:
[email protected]
Content-Type: text/plain; charset=ISO-8859-1

Hi list,
Anyone know rfx board i q phase imbalance value and amplititude
imbalance value,
I do not have equiment to measure these value.


Message: 15
Date: Fri, 8 Mar 2013 21:00:04 -0500
From: Brian P. [email protected]
To: manjusha [email protected]
Cc: GNURadio D.ion List [email protected]
Subject: Re: [Discuss-gnuradio] bit error rate
Message-ID:
[email protected]
Content-Type: text/plain; charset=“iso-8859-1”

On Fri, Mar 8, 2013 at 8:47 PM, manjusha [email protected]
wrote:

ber_before_tx.png
http://gnuradio.4.n7.nabble.com/file/n40088/ber_before_tx.png
ber_tx.png http://gnuradio.4.n7.nabble.com/file/n40088/ber_tx.png

It doesn’t look like you’re doing any carrier recovery?

Before putting USRP blocks in there, maybe you should try a straight
simulation that adds noise and some frequency offset artificially. Get
that working, and then connect up the USRP source/sink?

I am trying to find the Bit error rate for a vector signal.I get a error
rate of 0.528(i am assuming it to be 52%) when i don’t transmit and an
error rate of 0.625000 when i transmit.

Am i right on this??i dont understand the logic behind it…

Also,is 52% not too high??!!!

Around 50% BER is what you would expect from a random signal. 100% BER
is
very good since you just need to flip all the bits and you get the right
answer! That is also given the input signal statistics are sufficiently
whitened/random.

thank you

You might want to take a step away from putting blocks in GRC and just
take
a look at some of the resources on the GNU Radio wiki about suggested
reading:

http://gnuradio.org/redmine/projects/gnuradio/wiki/SuggestedReading
http://gnuradio.org/redmine/projects/gnuradio/wiki/SuggestedReadingOrder

Sanity is hard to come by if you’re dealing with magic.

Good Luck!

Brian
-------------- next part --------------
An HTML attachment was scrubbed…
URL:
http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20130308/631cd080/attachment.html


Message: 16
Date: Fri, 8 Mar 2013 21:15:27 -0600
From: Nathan W. [email protected]
To: Brian P. [email protected]
Cc: GNURadio D.ion List [email protected]
Subject: Re: [Discuss-gnuradio] bit error rate
Message-ID:
[email protected]
Content-Type: text/plain; charset=“ISO-8859-1”

very good since you just need to flip all the bits and you get the right
answer! That is also given the input signal statistics are sufficiently
whitened/random.

Just tagging on here… The way you have it set up is compare the
incoming bit to 1, next compare the incoming bit to 0. And it will
alternately compare incoming bits between 1 and 0. This BER block will
probably not be useful if you don’t have access (within this
flowgraph) to the source generating data.

http://gnuradio.org/redmine/projects/gnuradio/wiki/SuggestedReading
http://gnuradio.org/redmine/projects/gnuradio/wiki/SuggestedReadingOrder

Sanity is hard to come by if you’re dealing with magic.

If you haven’t looked at examples yet you should do that too. They are
probably located in /usr/local/share/gnuradio/examples/

There’s a BER example at
/usr/local/share/gnuradio/examples/digital/demod/ber_simulation.grc

Good Luck!

Brian


Message: 17
Date: Fri, 8 Mar 2013 23:42:03 -0500
From: Tommy T. II [email protected]
To: manjusha [email protected]
Cc: [email protected]
Subject: Re: [Discuss-gnuradio] Number of bits tranmitted
Message-ID: [email protected]
Content-Type: text/plain; charset=“us-ascii”

One idea would be to have a file sink also attached to the GMSK Mod
block. All samples you send to your USRP would be copied in the file.
Just check the file for byte count.

Tommy James Tracy II
Ph.D Student
High Performance Low Power Lab
University of Virginia
Phone: 913-775-2241

On Mar 8, 2013, at 7:02 PM, manjusha [email protected] wrote:


Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

-------------- next part --------------
An HTML attachment was scrubbed…
URL:
http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20130308/d83027bd/attachment.html


Message: 18
Date: Fri, 8 Mar 2013 21:23:49 -0800
From: Matt E. [email protected]
To: James Jordan [email protected]
Cc: discuss-gnuradio [email protected]
Subject: Re: [Discuss-gnuradio] Any one know rfx board i q imbalance
value
Message-ID:
[email protected]
Content-Type: text/plain; charset=“iso-8859-1”

The imbalance will vary board to board, which is why we provide the
ability
to calibrate the IQ balance. Running the calibration utility will get
you
the best performance.

Matt

On Fri, Mar 8, 2013 at 5:54 PM, James Jordan
[email protected]wrote:

Hi list,
Anyone know rfx board i q phase imbalance value and amplititude imbalance
value,
I do not have equiment to measure these value.


Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

-------------- next part --------------
An HTML attachment was scrubbed…
URL:
http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20130308/48111912/attachment.html



Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

End of Discuss-gnuradio Digest, Vol 124, Issue 9


We are working on IEEE 802.11 module on GNU Radio using wireshark
software. This was a readymade module which has been downloaded from
gnuradio official website (Link:
https://github.com/bastibl/gr-ieee802-11) .The Receiver WiFi block is
running well. The received data (ASCII code) is shown on the Gnuradio
companion but when the data is stored in .pcap files through wireshark
connector it shows “malformed packet”. How can I resolve this issue?
Please help.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs