1234567.png http://gnuradio.4.n7.nabble.com/file/n40046/1234567.png
Hi,
I have this GRC file and i how would i know the number of bits
transmitted
through this file.
Your help is appreciated.
Thanks.
1234567.png http://gnuradio.4.n7.nabble.com/file/n40046/1234567.png
Hi,
I have this GRC file and i how would i know the number of bits
transmitted
through this file.
Your help is appreciated.
Thanks.
A small correction to the GRC file. vector_source.png
http://gnuradio.4.n7.nabble.com/file/n40048/vector_source.png
On 07 Mar 2013 15:55, manjusha wrote:
A small correction to the
GRC file. vector_source.png
http://gnuradio.4.n7.nabble.com/file/n40048/vector_source.png
Manjusha
View this message in context:
http://gnuradio.4.n7.nabble.com/Number-of-bits-tranmitted-tp40046p40048.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
So much
confusion in that flow-graph.
o 50k isn’t a valid sample-rate for a
USRP device of any kind
o Signal flows within Gnu Radio are usually
scaled into {-1.0,+1.0}, so your X 3000 multiplier isn’t likely to help
you with anything other than driving stuff into clipping
o The vector
source repeats, so, again, there are an infinite number of bits sent,
encoded in GMSK “symbols” and there are two samples per symbol
Thank you so much for guiding me since i am new to this…Here is the
updated
grc file modified_vector.png
http://gnuradio.4.n7.nabble.com/file/n40052/modified_vector.png
Thanks
if you know how to find the transmitted and received number of bits
through
grc…please let me know…
Need help with my project
is there no wat to do it?
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
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs