Where can I find RFX2400.bom file?
It was here before:
http://gnuradio.org/trac/browser/usrp-hw/trunk/rfx/rfx2400.bom
Not anymore.
Thanks in advance,
Tom
On Fri, Feb 5, 2010 at 7:40 PM, Don Fanning wrote:
So I guess I should be the first one to ask:
How will this affect the GPL an
Blocks in Flowgraphs for transmission and receiving are are connected using
python. (examples: benchmark_rx.py & benchmark_tx.py)
Has someone glued those blocks (for TX & RX) using C++? I cannot find
examples with C++.
BR,
Tom
--
View this message in context:
http://old.nabble.com/glue-blocks-u
Hello,
I do IQ plotting for DBPSK, DQPSK, 8PSK. (Please have a look below):
For DBPSK:
http://omploader.org/vMm16Zg/dbpsk_IQ_plotting.png
For QPSK:
http://omploader.org/vMm16Zw/dqpsk_IQ_plotting.png
Can someone explain why for DQPSK positions of ideal points are wrong? It
should be [1,1], [-1,1
Can anyone confirm whether block diagram that I draw for TX path implemented
for dbpsk modulation is correct:
http://omploader.org/vMmV5NQ/TX_path_block_diagram.PNG
I check dbpsk.py and I don't see any hook up to code in
gr_phase_modulator_fc.cc
Even no gr_phase_modulator_fc objects are created.
Can anyone confirm block diagram that I did for TX path implemented for dbpsk
modulation:
http://omploader.org/vMmV5NQ/TX_path_block_diagram.PNG
I check dbpsk.py and I don't see any hook up to code in
gr_phase_modulator_fc.cc
Even no code in gr_phase_modulator_fc objects are created.
For what mo
Hello,
I am using dBPSK modulation, and I don't see that PM modulation written in
C++ is used. It seems that code in gr_phase_modulator_fc.cc is not used for
dBPSK. How come?
Which c++ code for PM is used for dBPSK modulation?
Tom
--
View this message in context:
http://www.nabble.com/dBPSK-m
Eric, I am also able to run this 2 lines of code.. but problem occures when
this object is created in one of the benchmark examples (tx or rx).
Those benchmarks also create usrp objects.
The error I get when second time such object is created is following:
[LOG]
usrp_open_interface:usb_claim_i
OK, there is not problem with inheritance in C++.
There is something strange in SWIG interface or python.
I am able to create objects and call method read_aux_adc() in C++.
but whenever I create second object in python I got errors:
./streamer_rx_tx_t.py -f 2.4G
usrp_open_interface:usb_claim_in
Hello,
I don't understand one think.. Class usrp_sink_c inherit from usrp_base a
public method read_aux_adc(int,int).
[code]
int usrp_base::read_aux_adc (int which_dboard, int which_adc)
{
return d_usrp_basic->read_aux_adc (which_dboard, which_adc);}
[/code]
According to my OO knowledge obj
