Sounds good. Can you please run your “txrx” simulation or separate “tx”
“rx” simulation and screenshot me the output because I feel like what I
am seeing is wrong. I want to be sure the output of the fft is correct.
On the receiver side I am getting the message debug that tells me the
packet number and packet length as well as if it’s detecting a failed
packet.
On Tuesday, January 27, 2015 12:11 PM, Achilleas A.
[email protected] wrote:
Frank,
you can perform simulations and plot BER vs SNR using either of the two
apps provided (ie, either the txrx or the separate tx and rx apps that
communicate through FIFO). The file vs FIFO is irrelevant here: the
FIFOs are just used for “emulating”
the communication between the two different tx and rx applications.
In both cases you can either dump the rx results to a file and compare
with the “known” tx transmission, or you can add BER GRC blocks…
All the above are not gr-cdma related, so i am sure you can find plenty
of examples of how this is done in this list and in the gnuradio
examples.
Achilleas
On Mon, Jan 26, 2015 at 10:01 PM, Frank P. [email protected]
wrote:
Sounds good! I figured this already just wanted to be sure. And will I
be able to plot the BER vs. Eb/NO by using the writing and reading to
fifo or simply reading and writing to a file and importing the data to
matlab for the BER vs Eb/NO plot?
On Friday, January 23, 2015 5:59 PM, Frank P.
[email protected] wrote:
|
Sounds good! I figured this already just wanted to be sure. And will I
be able to plot the BER vs. Eb/NO by using the writing and reading to
fifo or simply reading and writing to a file and importing the data to
matlab for the BER vs Eb/NO plot?
Sent from Yahoo Mail for iPhone
At Jan 23, 2015, 5:53:58 PM, Achilleas A. wrote:The
beautiful thing about open source is that all the detail are there for
you to see!
Looking at the cdma_parameters.py file,
you can see:
pulse_training = numpy.array((1,1,1,1,-1,1,1,-1))+0j
pulse_data =numpy.array((-1,1,-1,1,-1,-1,-1,-1))+0j
so we are using 8 chips per symbol with two orthogonal codes for
training and data.
You can change them and put anything you like (they better be orthogonal
AND each should have good
autocorrelation properties-- or at least the training code should)
best,
Achilleas
|