Hello Dominik,
Dominik Auras schrieb:
Did you test this with Linux? Are there any plans to support Linux/GCC
etc.?
Nope, we have not done anything on Linux with this interface.
If somebody wants to maintain a Linux-Version of simulink-usrp, we could
add this as a project on e.g. SourceForge
Dear Gnuradio hackers,
I have problems with the DBSRX module of the USRP: I see GSM on all
frequencies. I hope somebody can answer my questions: Is there an
antialiasing filter somewhere in the design? If so, what is its nominal
efficiency? Where can I find data sheets for the MAX211x
Hi
Can anyone please help me? I am using gnuradio3.1.3.
When I try to run usrp_benchmark_usb.py, I get the a RuntimeError:
Unable to find USRP #0.
When I issue
ls -lR /dev/bus/usb | grep usrp,
I didn't get any message.
This is the first time that I connect USRP board to PC.
Please help me.
Hello,
I want to record a FM sample that I am receiving from my USRP.I have
attached a file_sink block in the grc to the fm receiver
simulation.The file extension that I am using is .dat.When I convert this
.dat file to mp3 using sox or lame,my sample is highly degraded than the
sample I can
On Mon, May 18, 2009 at 4:28 AM, Teodora Petrovic li...@ruby-forum.com wrote:
Can anyone please help me? I am using gnuradio3.1.3.
When I try to run usrp_benchmark_usb.py, I get the a RuntimeError:
Unable to find USRP #0.
When I issue
ls -lR /dev/bus/usb | grep usrp,
I didn't get any
Hello
This is for Matt.
I'm not aware about USRP requirement's history, hence I'm asking.
I apologise immediately if the question is stupid enough... :-)
have you ever think about a simplified USRP, or 1/2 USRP, having only 1 side TX
and RX?
Would it make a cost difference (maybe on a large
Hi Alberto,
the USRP2 is only 1xTX and 1xRX. However, the USRP2 costs more than
the USRP1 because of its bigger FPGA and faster ADC/DAC (in addition
to SDRAM and other hardware). In short, the cost savings are minimal
if you would remove one RX and one TX from the USRP1 (you might be
able to
Hi Enno,
If somebody wants to maintain a Linux-Version of simulink-usrp, we could
add this as a project on e.g. SourceForge (see below). So if anybody is
interested in porting this to Linux _and_ maintaining the Linux-specific
parts, please let us know.
I already ported it to linux today,
On Sun, May 17, 2009 at 07:34:16PM -0700, Ling Huang wrote:
To get it to stop, send it a message with
type=1. The message source will indicate that it is done and the flow
graph will terminate.
I set transmit path message with type = 1, but it still not work, it hang in
wait()
On Mon, May 18, 2009 at 12:08:01PM +0200, Andreas Bogk wrote:
Dear Gnuradio hackers,
I have problems with the DBSRX module of the USRP: I see GSM on all
frequencies. I hope somebody can answer my questions: Is there an
antialiasing filter somewhere in the design? If so, what is its
Eric Blossom wrote:
Hi Andreas! Welcome!
Thanks! :)
Try turning the Rx gain down.
Been there, done that. It doesn't get rid of the images.
The datasheets should be on Maxim's site, though I think they're
discontinuing the part. If you can't locate them, let me know and
I'll see
On Mon, May 18, 2009 at 07:11:43PM +0200, Andreas Bogk wrote:
Eric Blossom wrote:
Hi Andreas! Welcome!
Thanks! :)
Try turning the Rx gain down.
Been there, done that. It doesn't get rid of the images.
The datasheets should be on Maxim's site, though I think they're
have you ever think about a simplified USRP, or 1/2 USRP, having only 1 side
TX and RX?
Would it make a cost difference (maybe on a large volume basis)? Would it
save some space?
Reason for asking is that many (most?) applications are 1+1 channel, and
saving space may allow more compact
Eric Blossom wrote:
[datasheets]
OK, I'll look for them later on today.
Matt sent me the correct part number (MAX2118), and I've found the data
sheet.
The chip has a controllable IF-filter bandwidth. It can be controlled
using the set_bw method on the daugherboard subdevice. Pass it
Eric Blossom wrote:
Hi Andreas! Welcome!
Try turning the Rx gain down.
The datasheets should be on Maxim's site, though I think they're
discontinuing the part. If you can't locate them, let me know and
I'll see if I can't find one for you.
Eric
Arh! I knew it had to happen
Marcus D. Leech wrote:
Eric Blossom wrote:
Hi Andreas! Welcome!
Try turning the Rx gain down.
The datasheets should be on Maxim's site, though I think they're
discontinuing the part. If you can't locate them, let me know and
I'll see if I can't find one for you.
Eric
Arh! I
have you ever think about a simplified USRP, or 1/2 USRP, having only 1 side
TX and RX?
How about a 64 x USRP? It would be cool if there was a USRP that had
many receiver channels, and it would also have a simple beam-former
built into the FPGA.
All of the schematics for the USRP and
About a month ago, our USRP1 Rev. 4.5 (Ser. #2728) became erratic in it USB
connection and communications. A short while after, USB failed altogether. I
put scope probes on the USB + and - data lines and observed that one of the
signals had a much different sort of signal than the other. Following
Paul Mathews wrote:
About a month ago, our USRP1 Rev. 4.5 (Ser. #2728) became erratic in it USB
connection and communications. A short while after, USB failed altogether. I
put scope probes on the USB + and - data lines and observed that one of the
signals had a much different sort of signal
Matt Ettus wrote:
Paul Mathews wrote:
Paul,
Thanks for your analysis of the situation. C73 and C74 are not
actually capacitors, they are, as you say, electrostatic discharge
protectors, part number PESD0402-060. I have not seen any fail in the
manor you mention, but I suppose enough
On Mon, 18 May 2009 19:26:58 -0400, Marcus D. Leech mle...@ripnet.com
wrote:
Matt Ettus wrote:
Paul Mathews wrote:
Paul,
Thanks for your analysis of the situation. C73 and C74 are not
actually capacitors, they are, as you say, electrostatic discharge
protectors, part number PESD0402-060. I
sorry, I'm not familiar with gdb, I can't get many useful infomation from
that.
The topblock start 6 threads (exept the mainloop) . After tb.stop(), five
threads has exited, but leaving one.
Here is the gdb infomation after tb.stop()
And here is the gdb after tb.wait()
---gdb
wait---
#0 0xb7f1f430 in __kernel_vsyscall ()
#1 0xb7e1bdf1 in select () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7efbbc9 in ?? () from
On Sat, 2009-05-16 at 03:44 +0200, Changkyu Seol wrote:
It will be grateful if python bindings for config_mimo,
sync_every_pps are added to usrp2_base.h and usrp2.i in gr-usrp2.
These calls are now visible (as of trunk r11050) in the Python API as:
from gnuradio import usrp2
u =
Hi,
Could you please inform about when we can access USRP2 schematic files.
Thanks in advance.
Regds,
Sudhir
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
25 matches
Mail list logo
