Hello Marcus, Hello Geof,
Thanks a lot for your replies !
Indeed tried it on a Ubuntu 19.10 and everything looks fine there with latest
UHDs.
Benchmark_rate does not report any dropped samples even at 8 MSPS .
On W10, indeed I also got very nice audio results (no clicks, interruptions
etc) w
Michael,
I still have my USRP1, and ran the same test w/ 3.14 and got the same
results on Win10, dropped packets down to the minimum supported rate. Same
test, same driver against the B200 works fine up to about 20MSps which
appears to be my USB 3 chip's limit.
For kicks I downloaded the same old
Hi Michael,
GR 3.3?! Wow, that *is* retro :)
> Now I wanted to give it a try on W10 and a modern PC, but when I run a
RX benchmark_rate test with latest UHD 3.15 but also 3.10 the command
window gets filled up with DD messages and number of dropped samples
is huge.
That shouldn't happen. Th
Hello All,
I have been using my USRP1 mainly on an older Linux PC with GNU radio 3.3 .
Now I wanted to give it a try on W10 and a modern PC, but when I run a RX
benchmark_rate test with latest UHD 3.15 but also 3.10 the command window gets
filled up with DD messages and number of dropped sam
On 05/20/2011 03:28 PM, Colby Boyer wrote:
> Hey Guys,
>
> It seems that the USRP1 out with UHD is normalized to 1.0, vs some big
> number as with the old USRP drivers. I assume this is correct?
> Otherwise my cards are not kicking out any RF power.
>
Yup, float values are 1.0 to -1.0 -josh
>
Hey Guys,
It seems that the USRP1 out with UHD is normalized to 1.0, vs some big
number as with the old USRP drivers. I assume this is correct?
Otherwise my cards are not kicking out any RF power.
--Colby
___
Discuss-gnuradio mailing list
Discuss-gnura
to add it. I believe the UHD
documentation says if no address is specified then it uses udp to find the
USRP2, however if a firewall is running (as is my case), then it will never
find it and err out.
http://www.ettus.com/uhd_docs/manual/html/identification.html#identifying-usrps
--
View this m
e: [Discuss-gnuradio] gr-air-modes: problem with uhd and USRP1
On Wed, 2010-12-01 at 13:55 -0500, Allen Vinegar wrote:
I am getting output like the following:
(-35) Type 11 (all call reply) from ac85cc in reply to interrogator 4
(-34) Type 11 (all call reply) from ac85cc in reply to interroga
ically" and set the timeout to 4 or 5 seconds.
--n
>
>
> Any ideas on how to fix?
>
>
>
> Thank you,
>
> Al Vinegar
>
>
>
>
>
> - Original Message -
> From: "madengr"
> To:
> Sent: Monday, November 29
On Mon, 2010-11-29 at 20:16 -0800, madengr wrote:
> Nick,
>
> Got it working on my USRP2 by changing to line 57 to:
> self.u = uhd.single_usrp_source("addr=192.168.1.15",
> uhd.io_type_t.COMPLEX_FLOAT32)
>
> and line 119 to:
> result = self.u.set_center_freq(freq,0)
That's correct. The Github re
> and line 119 to:
> result = self.u.set_center_freq(freq,0)
>
I intended the channel parameters to default to 0 for the single usrp*
blocks. It looks like i missed that. Will fix, thanks. -Josh
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.o
(-40) Type 11 (all call reply) from e9fc9f in reply to interrogator 5
(-41) Type 11 (all call reply) from 2c4e09 in reply to interrogator 0
I assume these are Mode-S packets, thus no position info?
--
View this message in context:
http://old.nabble.com/gr-air-modes%3A-problem-wit
On Sun, 2010-11-28 at 17:25 -0500, Josh Blum wrote:
> Those were deprecated interfaces for several months. They were just
> removed: http://osdir.com/ml/discuss-gnuradio-gnu/2010-11/msg00490.html
>
> The method calls should be nearly identical. Just change the
> constructor. -Josh
>
Mea culpa, I
Those were deprecated interfaces for several months. They were just
removed: http://osdir.com/ml/discuss-gnuradio-gnu/2010-11/msg00490.html
The method calls should be nearly identical. Just change the
constructor. -Josh
On 11/28/2010 04:54 PM, Alexander List wrote:
> Hi,
>
> maybe the API has ch
Hi,
maybe the API has changed since gr-air-modes was written, or I'm doing
something stupid, but I tried:
$ ./uhd_modes.py -g 60
linux; GNU C++ version 4.4.5; Boost_104200; UHD_0001.20101124180824.2568efd
Traceback (most recent call last):
File "./uhd_modes.py", line 167, in
fg = adsb_rx_
15 matches
Mail list logo
