There isnt any QA code for QAM modulator or demodulator.
They do not work for me.
I think if they worked, then their would be QA code.
On Sat, Dec 14, 2013 at 12:08 PM, Henry Jin wrote:
> Hi Wayne
>
> I agree with every point you mentioned in your reply. For the variable
> Bits per symbol, that
Hello GNU Radio enthusiasts,
some time after the GNU Radio 3.7 release I started to move the code for
'gr-lte' to the new API. Besides moving it to the new API, I wanted to
clean up code and rework a lot of tests. Thus, the whole transition took
a lot of time and work.
Now, all current blocks are
Hey,
Thanks,
I have got that fixed.
Now I am using the 3.7.2.1
When it loads it display this :
Warning (from warnings module):
File
"C:\Python27\lib\site-packages\cheetah-2.4.4-py2.7.egg\Cheetah\Compiler.py",
line 1509
"\nYou don't have the C version of NameMapper installed! "
U
Hi Wayne
I agree with every point you mentioned in your reply. For the variable Bits
per symbol, that was a mistake since I previously used it to test QAM.
So, have you tested QAM? In my test, the two files didn't match as
discussed in my previous post. Just curious about why this mismatch can
ha
Hi, I have an RFX1800 board with modifications allowing it to work in 900MHz and 1800MHz band.
What I find annoying is that if I want to use it in both bands, each time I have to reprogram EEPROM.
Life would be a lot easier if I had one driver that tunes the board in the whole freq range 750-2100
I i try that DQPSK schema myself, but i notice that in your image you have
Bits per symbol in packet encoder set to 4, but the help of packet encoder
says 2 for DQPSK.
I try 2, and i get no errors until the end, probably because of file
buffering.
--- sent.hex2013-12-14 10:11:41.308775941 -080
On 12/14/2013 06:46 AM, Nasi wrote:
---
Ubuntu 13.04, gnuradio 3.7, usrp N200
---
It is very annoying that sometimes I can not connect to the device
using this
---
Ubuntu 13.04, gnuradio 3.7, usrp N200
---
It is very annoying that sometimes I can not connect to the device using this
command:
~$ sudo ifconfig eth0 192.
It is very annoying that sometimes I can not connect to the device using this
command:
~$ sudo ifconfig eth0 192.168.10.1
I can ping 192.168.10.1, but ping 192.168.10.2 fails:
~$ sudo ifconfig eth0 192.168.10.1
~$ ping 192.168.10.2
PING 192.168.10.2 (192.168.10.2) 56(84) bytes of data.
From 19
Hi Marcus,
Everything you said I'm already thought about during last days and finally
came to conclusion, that buffer estimation model is the only reliable (it
solves issue directly by its nature) and universal one (many drivers provide
required functions in their API). Since it involves control l
10 matches
Mail list logo
