[USRP-users] Re: OFDM signal transmission by x310 presents a peak

2024-02-22 Thread Ron Economos
It's the DC offset of the direct conversion transmitter. With the X310, you can move it out of the signal with a tune_request(). You can move the spike up to 1/2 the sample rate in either direction. Here's an example at 6.912 Msps. uhd.tune_request(center_freq, 340) ATSC 3.0 OFDM This is

[USRP-users] OFDM signal transmission by x310 presents a peak

2024-02-22 Thread Pedro Vieira
An ofdm signal, which is generated in python, presents a peak in the central part of the spectrum. What could it be? This same behavior appears on USRP X310 and HackRFOne. ___ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an e

[USRP-users] Re: [EXTERNAL] Re: Multiple Streamers

2024-02-22 Thread Rohde, Zach (US 333G) via USRP-users
Thanks Rob. I agree. The documentation needs to be reworded to, “Note: There can always only be one streamer per channel…”. That would probably help people out. Regards, Zach From: Rob Kossler Date: Thursday, February 22, 2024 at 3:13 PM To: Rohde, Zach (US 333G) Cc: usrp-users@lists.ettus.co

[USRP-users] Re: Multiple Streamers

2024-02-22 Thread Rob Kossler via USRP-users
Hi Zach, There can definitely be multiple tx streamers (& rx streamers). Take a look at the Ettus rx_samples_to_file example which does this with rx streamers. You are probably doing everything right already. The documentation might be just poorly worded such that maybe it should say that you can

[USRP-users] Multiple Streamers

2024-02-22 Thread Rohde, Zach (US 333G) via USRP-users
Hello, I have been running tests with multiple TX channels so that each channel can run at a different sample rate, using multiple calls to get_tx_stream() to generate a unique streamer for each thread. This has been successful using the X440 and results in no errors or warnings. My question i

[USRP-users] Re: Getting started with RFNoc block (adding an additional RFnoc block )

2024-02-22 Thread Brian Padalino
On Thu, Feb 22, 2024 at 3:02 PM wrote: > CRITICAL WARNING: [Route 35-39] The design did not meet timing > requirements. Please run report_timing_summary for detailed reports. > > [01:09:55] Current task: Routing +++ Current Phase: 22 Post Router Timing > > [01:09:55] Current task: Routing +++ Cur

[USRP-users] Re: Getting started with RFNoc block (adding an additional RFnoc block )

2024-02-22 Thread yguruprasad
Could anyone guide me to fix through the critical warning? ___ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com

[USRP-users] Getting started with RFNoc block (adding an additional RFnoc block )

2024-02-22 Thread yguruprasad
CRITICAL WARNING: \[Route 35-39\] The design did not meet timing requirements. Please run report_timing_summary for detailed reports. \[01:09:55\] Current task: Routing +++ Current Phase: 22 Post Router Timing \[01:09:55\] Current task: Routing +++ Current Phase: Finished \[01:09:55\] Executing