On 27/03/2025 14:55, Chris Rogers wrote:
I'm not super familiar with the RFNoC stuff or the python workflow,
but the real key is to do timed frequency tuning of each channel, as
seen in the changes from this commit :
https://github.com/EttusResearch/uhd/commit/de1542331ff5f9dc29e252814ddeaa645f5641f3
I had (incorrectly) assumed that the original complaint included timed
tuning. That's absolutely necessary across various
USRPs, because of the nature of synthesizers and various other
components. Even just tuning a digital DDC/DUC, there's
no way it can be doing the tuning at the same clock phase unless it's
happening at the same time for every channel, and
there's also the issue of the phase accumulator in the DDC/DUC. You
set it to zero at some time T, and then it just starts
running, then the adjacent channel has its phase-accumulator reset,
and starts running, but not at precisely the same time.
SOoooooo, if phase-coherency and zero-phase offset are your goal,
timed tuning is kind of a minimal requirement.
As long as the API you're using provides the flexibility to do this -
which I'm pretty sure it does - then you should be good. It could also
be worth a shot to just run the fixed tx_waveforms example program to
prove it does what you want.
On Thu, Mar 27, 2025 at 2:44 PM <heath.j.st...@gmail.com> wrote:
Thanks for that reminder. I took a look at that example. We are
using the RFNoC API (using the python bindings) and not the
MultiUSRP API. I assume the same sequence can be achieved setting
up the SDR through RFNoC?
_______________________________________________
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 tousrp-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
