[USRP-users] connecting to USRP through multiple 10GbE link

2023-05-03 Thread h57jafari
Hi,

Can anyone share a sample GNU Radio flowgraph or .py for the case of connecting 
USRP to PCIe with several 10GbE link. I am trying to send and receive to USRP 
through more than one 10GbE link. my PCIe has four 10GbE link. thank you.
___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com


[USRP-users] Re: connecting to USRP through multiple 10GbE link

2023-05-03 Thread Marcus D. Leech

On 03/05/2023 08:57, h57jaf...@gmail.com wrote:


Hi,

Can anyone share a sample GNU Radio flowgraph or .py for the case of 
connecting USRP to PCIe with several 10GbE link. I am trying to send 
and receive to USRP through more than one 10GbE link. my PCIe has four 
10GbE link. thank you.



___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com

https://kb.ettus.com/USRP_X410_Getting_Started_Guide#Network_Connectivity

Use both the "addr" and "second_addr" device arguments.

___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com


[USRP-users] Re: Full duplex issues with X310

2023-05-03 Thread Marcus D. Leech

On 03/05/2023 13:05, david.fernan...@viveris.fr wrote:


Hi Marcus,

I have tested downgrading UHD to 3.15 and it works ! (I’ve tried with 
UHD 4.4 as well but its doesn’t work)


Now that the reception works everytime in a full-duplex communication, 
I observe that the TX/Rx antenna creates a lot of interferences to the 
RX2 antenna in the same channel.


For examples, I tested sending :

 *

1 sin signal of 50KHZ from channel 0 to channel 1, at center freq 1GHz

 *

1 sin signal of 80KHZ from channel 1 to channel 0, at center freq 2GHz

The result is available in the picture attached (the green circles are 
the carriers received, the red circles are the interferences caused by 
the TX) . Is this a normal behaviour ? Is there any 
configuration/customization that can be applied to attenuate those 
interfereances ?


Thanks again for your support, it is really appreciated.


___
USRP-users mailing list --usrp-users@lists.ettus.com
To unsubscribe send an email tousrp-users-le...@lists.ettus.com
The center frequency labels on your QT GUI frequency sinks aren't 
consistent with what the source is actually tuned to.



___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com


[USRP-users] RFNOC Block Not found

2023-05-03 Thread jmaloyan
Hello,

\
I currently have a custom RFNOC module. When I try to initialize my block 
however, I am unable to find it. I get an error that seems to match up with the 
block id I set on my module, but it still seems that it cannot be found. This 
is the error that is shown…

`[WARNING] [RFNOC::BLOCK_FACTORY] Could not find block with Noc-ID 0xde30, 
0x`

To test if my block was working properly, I used a NOC_ID used for the 
prepackaged modules and it worked fine, but I would however like to use a 
seperate NOC_ID for my own modules. I set the NOC ID in my yml file and 
block_control.cpp file to 0xde30 as per the RFNOC 4.0 Introduction guide.

Thanks

Joe
___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com


[USRP-users] Re: RFNOC Block Not found

2023-05-03 Thread Brian Padalino
On Wed, May 3, 2023 at 2:07 PM  wrote:

> Hello,
>
>
> I currently have a custom RFNOC module. When I try to initialize my block
> however, I am unable to find it. I get an error that seems to match up with
> the block id I set on my module, but it still seems that it cannot be
> found. This is the error that is shown…
>
> [WARNING] [RFNOC::BLOCK_FACTORY] Could not find block with Noc-ID 0xde30,
> 0x
>
> To test if my block was working properly, I used a NOC_ID used for the
> prepackaged modules and it worked fine, but I would however like to use a
> seperate NOC_ID for my own modules. I set the NOC ID in my yml file and
> block_control.cpp file to 0xde30 as per the RFNOC 4.0 Introduction guide.
>

What is the output of uhd_usrp_probe?  Do you see your block listed there?

Brian
___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com


[USRP-users] Re: RFNOC Block Not found

2023-05-03 Thread jmaloyan
This is the output of uhd_usrp_probe

/

|   Device: N300-Series Device

| _

|/

|   |   Mboard: ni-n3xx-3255102

|   |   dboard_0_pid: 338

|   |   dboard_0_serial: 3252A17

|   |   dboard_1_pid: 338

|   |   dboard_1_serial: 3252A18

|   |   eeprom_version: 3

|   |   fs_version: 20230131233809

|   |   mender_artifact: v4.4.0.0_n3xx

|   |   mpm_sw_version: 4.4.0.0-g5fac246b

|   |   pid: 16962

|   |   product: n320

|   |   rev: 10

|   |   rpc_connection: remote

|   |   serial: 3255102

|   |   type: n3xx

|   |   MPM Version: 4.4

|   |   FPGA Version: 8.1

|   |   FPGA git hash: 5fac246.dirty

|   |   RFNoC capable: Yes

|   |   

|   |   Time sources:  internal, external, gpsdo, sfp0

|   |   Clock sources: external, internal, gpsdo

|   |   Sensors: ref_locked, gps_locked, temp, fan, gps_gpgga, gps_sky, 
gps_time, gps_tpv

| _

|/

|   |   RFNoC blocks on this device:

|   |   

|   |   \* 0/Block#0

|   |   \* 0/Block#1

|   |   \* 0/Radio#0

|   |   \* 0/Radio#1

|   |   \* 0/Replay#0

| 
___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com


[USRP-users] Re: RFNOC Block Not found

2023-05-03 Thread Brian Padalino
Try doing:

  uhd_usrp_probe --interactive-ref-iface 0/Block#0

And inside there, try:

  peek32 0

What does it print out?  Does it match your NOC_ID in your controller?

Brian

On Wed, May 3, 2023 at 4:03 PM  wrote:

> This is the output of uhd_usrp_probe
>
>
> /
>
> | Device: N300-Series Device
>
> | _
>
> | /
>
> | | Mboard: ni-n3xx-3255102
>
> | | dboard_0_pid: 338
>
> | | dboard_0_serial: 3252A17
>
> | | dboard_1_pid: 338
>
> | | dboard_1_serial: 3252A18
>
> | | eeprom_version: 3
>
> | | fs_version: 20230131233809
>
> | | mender_artifact: v4.4.0.0_n3xx
>
> | | mpm_sw_version: 4.4.0.0-g5fac246b
>
> | | pid: 16962
>
> | | product: n320
>
> | | rev: 10
>
> | | rpc_connection: remote
>
> | | serial: 3255102
>
> | | type: n3xx
>
> | | MPM Version: 4.4
>
> | | FPGA Version: 8.1
>
> | | FPGA git hash: 5fac246.dirty
>
> | | RFNoC capable: Yes
>
> | |
>
> | | Time sources: internal, external, gpsdo, sfp0
>
> | | Clock sources: external, internal, gpsdo
>
> | | Sensors: ref_locked, gps_locked, temp, fan, gps_gpgga, gps_sky,
> gps_time, gps_tpv
>
> | _
>
> | /
>
> | | RFNoC blocks on this device:
>
> | |
>
> | | * 0/Block#0
>
> | | * 0/Block#1
>
> | | * 0/Radio#0
>
> | | * 0/Radio#1
>
> | | * 0/Replay#0
>
> | 
> ___
> USRP-users mailing list -- usrp-users@lists.ettus.com
> To unsubscribe send an email to usrp-users-le...@lists.ettus.com
>
___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com


[USRP-users] Re: RFNOC Block Not found

2023-05-03 Thread Brian Padalino
Mistype:

  uhd_usrp_probe --interactive-reg-iface 0/Block#0

... also assuming 0/Block#0 and 0/Block#1 are the same and your own custom
blocks.

Unsure if this assumption is correct.

Brian

On Wed, May 3, 2023 at 4:21 PM Brian Padalino  wrote:

> Try doing:
>
>   uhd_usrp_probe --interactive-ref-iface 0/Block#0
>
> And inside there, try:
>
>   peek32 0
>
> What does it print out?  Does it match your NOC_ID in your controller?
>
> Brian
>
> On Wed, May 3, 2023 at 4:03 PM  wrote:
>
>> This is the output of uhd_usrp_probe
>>
>>
>> /
>>
>> | Device: N300-Series Device
>>
>> | _
>>
>> | /
>>
>> | | Mboard: ni-n3xx-3255102
>>
>> | | dboard_0_pid: 338
>>
>> | | dboard_0_serial: 3252A17
>>
>> | | dboard_1_pid: 338
>>
>> | | dboard_1_serial: 3252A18
>>
>> | | eeprom_version: 3
>>
>> | | fs_version: 20230131233809
>>
>> | | mender_artifact: v4.4.0.0_n3xx
>>
>> | | mpm_sw_version: 4.4.0.0-g5fac246b
>>
>> | | pid: 16962
>>
>> | | product: n320
>>
>> | | rev: 10
>>
>> | | rpc_connection: remote
>>
>> | | serial: 3255102
>>
>> | | type: n3xx
>>
>> | | MPM Version: 4.4
>>
>> | | FPGA Version: 8.1
>>
>> | | FPGA git hash: 5fac246.dirty
>>
>> | | RFNoC capable: Yes
>>
>> | |
>>
>> | | Time sources: internal, external, gpsdo, sfp0
>>
>> | | Clock sources: external, internal, gpsdo
>>
>> | | Sensors: ref_locked, gps_locked, temp, fan, gps_gpgga, gps_sky,
>> gps_time, gps_tpv
>>
>> | _
>>
>> | /
>>
>> | | RFNoC blocks on this device:
>>
>> | |
>>
>> | | * 0/Block#0
>>
>> | | * 0/Block#1
>>
>> | | * 0/Radio#0
>>
>> | | * 0/Radio#1
>>
>> | | * 0/Replay#0
>>
>> | 
>> ___
>> USRP-users mailing list -- usrp-users@lists.ettus.com
>> To unsubscribe send an email to usrp-users-le...@lists.ettus.com
>>
>
___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com