Hi,
Apology if this is a redundant question.
With the latest UHD version, is it possible to use B210 as a quad channel
receiver.
Dual channel, I understood, it exists, and I verified also.
Regards
Sumit
___
USRP-users mailing list
USRP-users@lists.ett
ceive channels. So, I'm afraid
> that no software update ever will change that!
>
> Best regards,
>
> Marcus
>
> On 09/15/2017 02:41 PM, Sumit Kumar via USRP-users wrote:
>
> Hi,
>
> Apology if this is a redundant question.
>
> With the latest UHD versio
ia USRP-users <
>> usrp-users@lists.ettus.com> wrote:
>>
>>> A single B210 has exactly two hardware receive channels. So, I'm afraid
>>> that no software update ever will change that!
>>>
>>> Best regards,
>>>
>>> Marcus
>
Hi,
I was wondering if anyone has the materials for the famous talk by Matt
Ettus in 2011 GRCon.
*"Why Doesn't My Signal Look Like the Textbook?"*
I remember it was hosted on Tom's webpage. The link is still there, however
the files are missing.
http://www.trondeau.com/grc2011-abstracts/
Go to
der. Slides here:
> https://drive.google.com/file/d/0B6ccrJyAZaq3UHpEQld1YmZjbWs/view
>
> On Mon, Oct 16, 2017 at 1:56 PM, Sumit Kumar via USRP-users <
> usrp-users@lists.ettus.com> wrote:
>
>> Hi,
>>
>> I was wondering if anyone has the materials for the
Hi,
I want to create a deterministic collision scenario between wifi and
zigbee. I am using gr-ieee 80211 and gr-ieee 802154 along with USRP B210.
I have a constraint that my wifi preambles should always collide with an
ongoing zigbee transmission.
In order to do that, I am thinking of synchroni
Hi,
Yesterday I installed on one machine using pybombs, it was good, no issues.
Today I tried in another machine it fails.
Here are the logs
CMakeOutput.log -- https://paste.ubuntu.com/26511650/
CMakeError.log -- https://paste.ubuntu.com/26511662/
~~~
srp-users@lists.ettus.com> wrote:
> The error messages says Boost was not found. Do you have the boost dev
> package installed on this machine?
>
>
> On 02/03/2018 04:53 AM, Sumit Kumar via USRP-users wrote:
>
>> Hi,
>>
>> Yesterday I installed on one machin
I am using a UHD source in GRC. I configured it to stream from both the RX
ports.
The first port is tuned to 2.437 GHz and the another to 2.435 by providing
a lo_offset of 2MHz.
Samples from first port go under some processing and then have to be added
to samples coming from the second port. When
Hi,
I have 3 bricked N210 to be recovered. I was following the post
https://kb.ettus.com/N200/N210_Device_Recovery
It says JTAG programmer and in the picture I can see the model no. is
DLC9G.
I found something on Amazon which has the same model number but does not
looks the same. Can anyone confi
> Nick
>
> On Fri, Feb 28, 2020 at 2:19 AM Sumit Kumar via USRP-users <
> usrp-users@lists.ettus.com> wrote:
>
>> Hi,
>> I have 3 bricked N210 to be recovered. I was following the post
>> https://kb.ettus.com/N200/N210_Device_Recovery
>>
>>
Hi,
I am also having the issue. Can anyone please help with the information :)
For N310, there is FP0 available but for N320 I get following run time
error:
" what(): RuntimeError: The hardware has no GPIO bank `FP0' "
Regards
Sumit
On Mon, Jan 27, 2020 at 11:02 PM Nowicki, Ed H. via USRP-use
Just now I tried to print the available GPIO available. For N310 it shows:
FP0
RXA
TXA
RXB
TXB
But for N320 it shows:
RXA
TXA
RXB
TXB
On Wed, Sep 2, 2020 at 7:58 PM Sumit Kumar wrote:
> Hi,
>
> I am also having the issue. Can anyone please help with the information :)
>
> For N310, there is F
Hello Pratik,
Were you able to find the solution ?
BR
Sumit
On Wed, Oct 17, 2018 at 9:41 PM Pratik Chatterjee via USRP-users <
usrp-users@lists.ettus.com> wrote:
> Hello all,
>
> I have used pybombs in the past and it worked just fine. But recently I
> get compatibility issues of uhd and fpga,
Hi,
I got Ettus N200 from my colleague. I din't know the ip address so I did a
reset. After the reset, the ip of N200 became 192.168.10.2 and I was able
to ping and do all regular stuff with it. But whenever I do a power cycle
of the N200, it is undetectable at 192.168.10.2. Then again I have to r
PM, Sumit Kumar via USRP-users wrote:
> >
> > Hi,
> >
> > I got Ettus N200 from my colleague. I din't know the ip address so I
> > did a reset. After the reset, the ip of N200 became 192.168.10.2 and I
> > was able to ping and do all regular stuff with it. But
;
>
>
>
> On Thu, Jun 13, 2019 at 9:38 PM Marcus D. Leech via USRP-users <
> usrp-users@lists.ettus.com> wrote:
>
>> On 06/13/2019 03:33 PM, Sumit Kumar via USRP-users wrote:
>> >
>> > Hi,
>> >
>> > I got Ettus N200 from my colleague. I din'
Hi,
I am trying transmit using Ettus N200 (call it A) but getting this error
message on the console
SSU...
com> wrote:
> I am not really an N-series guy, so this probably won't be helpful. Have
> you tried doing a uhd_usrp_probe on both devices and seen that the
> responses are consistent?
>
> --
> *From:* USRP-users on behalf of
> Sumit Kumar via
pful. Have
> you tried doing a uhd_usrp_probe on both devices and seen that the
> responses are consistent?
>
> --
> *From:* USRP-users on behalf of
> Sumit Kumar via USRP-users
> *Sent:* Wednesday, July 17, 2019 7:15 AM
> *To:* usrp-users@lists.ettus.com
> *Subject:*
Yes already tried different cable. Same issue :(
One usrp is good but the other says S!.
On Wed, Jul 17, 2019 at 3:18 PM Marcus D. Leech via USRP-users <
usrp-users@lists.ettus.com> wrote:
> On 07/17/2019 07:45 AM, Sumit Kumar via USRP-users wrote:
>
> Hi Jason,
>
> Ye
on_USRP_Devices#N200.2F210_EEPROM
>
> Do they match?
>
> --
> *From:* Sumit Kumar
> *Sent:* Wednesday, July 17, 2019 7:45 AM
> *To:* Jason Matusiak
> *Cc:* usrp-users@lists.ettus.com
> *Subject:* Re: [USRP-users] Sequence Errors N200
>
> Hi Jaso
---
> *From:* USRP-users on behalf of
> Sumit Kumar via USRP-users
> *Sent:* Wednesday, July 17, 2019 7:06 AM
> *To:* Jason Matusiak
> *Cc:* usrp-users@lists.ettus.com
> *Subject:* Re: [USRP-users] Sequence Errors N200
>
> Following is what I am getting after
xx
>
>
> What is the command you're using to transmit(which utility and args?)
>
>
> Regards,
> Nate Temple
>
> On Wed, Jul 17, 2019 at 7:06 AM Sumit Kumar via USRP-users <
> usrp-users@lists.ettus.com> wrote:
>
>> Following is what I am getting after
e run: sudo sysctl -w net.core.wmem_max=250
>>> [WARNING] [UDP] The send buffer could not be resized sufficiently.
>>> Target sock buff size: 250 bytes.
>>> Actual sock buff size: 1048576 bytes.
>>> See the transport application notes on buffer resizing.
>
io)_on_Linux#Thread_priority_scheduling
>>>>>
>>>>>
>>>>> 2) Adjust your network buffers
>>>>>
>>>>> "
>>>>> [WARNING] [UDP] The send buffer could not be resized sufficiently.
>>>>> Target soc
Tried 3 different power supplies, still the same. SS :-/
On Wed, Jul 17, 2019 at 5:20 PM Marcus D. Leech via USRP-users <
usrp-users@lists.ettus.com> wrote:
> On 07/17/2019 11:10 AM, Sumit Kumar via USRP-users wrote:
>
> Sorry, here it is.
>
> Benchmark rate summary:
>
Sumit,
>>>>>>>
>>>>>>> A couple things to address:
>>>>>>>
>>>>>>> 1) Enable Thread priority scheduling on your host
>>>>>>>
>>>>>>> Note it is throwing a wa
frame size: 1472 bytes
>>>>>>>>
>>>>>>>> No gain specified.
>>>>>>>> Setting gain to 15.75 (from [0.00, 31.50])
>>>>>>>>
>>>>>>>> .............
>>>>>>> Yes I addressed the first 2 points you mentioned.
>>>>>>>>>>
>>>>>>>>>> john@john-Precision-M4600:~/pybombs/src/gnuradio/gr-digital/examples/narrowband$
>>>>>>>>>> sudo ./ben
x_rate 10e6
>>>>>>>>>> --duration 600
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Nate Temple
>>>>>>>>>>
>&g
Hi,
I have received a brand new USRP-2974 and looking for getting started
guides.
I went thru https://kb.ettus.com/USRP-2974_Getting_Started_Guide but cudn't
get much info apart from making connections with uhd via PCIe. There is no
note on making connection with 1GB ethernet. I was able to ping a
32 matches
Mail list logo
