[prev in list] [next in list] [prev in thread] [next in thread]
List: usrp-users
Subject: [USRP-users] Re: [EXTERNAL] Re: Multiple Streamers
From: "Rohde, Zach (US 333G) via USRP-users" <usrp-users () lists ! ettus ! com>
Date: 2024-02-22 23:20:43
Message-ID: SA1PR09MB9275492D17EA18AAE90BACC092562 () SA1PR09MB9275 ! namprd09 ! prod ! outlook ! com
[Download RAW message or body]
[Attachment #2 (text/plain)]
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 <rkossler@nd.edu>
Date: Thursday, February 22, 2024 at 3:13 PM
To: Rohde, Zach (US 333G) <zachary.s.rohde@jpl.nasa.gov>
Cc: usrp-users@lists.ettus.com <usrp-users@lists.ettus.com>
Subject: [EXTERNAL] Re: [USRP-users] Multiple Streamers
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 only have one streamer per channel. Rob
On Thu, Feb 22, 2024 at 5:08 PM Rohde, Zach (US 333G) via USRP-users \
<usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com>> wrote: 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 is the documentation<https://urldefense.us/v3/__https:/files.ettus.com/man \
ual/classuhd_1_1device.html*a66d1bf289dd03a03df3860f3eee578c0__;Iw!!PvBDto6Hs4WbVuu7!M \
XEfHO7LaEESM1gY0e9LRsk-dpWTIlz99pVQMh2wh6fVV6FRDjt23acYEhLtjRuAJl3tjfDFtGFkaUP6rAV99F5HpCU$> \
states: "Note: There can always only be one streamer. When calling get_tx_stream() a \
second time, the first streamer must be destroyed beforehand." Is this true? Why am I \
not seeing any undefined behavior or errors/warnings?
In the documentation for \
multi_usrp_rfnoc<https://urldefense.us/v3/__https:/github.com/EttusResearch/uhd/blob/m \
aster/host/lib/usrp/multi_usrp_rfnoc.cpp*L78__;Iw!!PvBDto6Hs4WbVuu7!MXEfHO7LaEESM1gY0e9LRsk-dpWTIlz99pVQMh2wh6fVV6FRDjt23acYEhLtjRuAJl3tjfDFtGFkaUP6rAV9F_MMrvg$>, \
I noticed a documentation stub that mentioned, "If there is only ever one Tx \
streamer, this will work as expected. For multiple streamers, only the last \
streamer's async messages will make it through." So, it seems the documentation is \
sort of contradicting one another on whether multiple TX streams are allowed.
Thanks,
Zach
_______________________________________________
USRP-users mailing list -- \
usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> To unsubscribe send an \
email to usrp-users-leave@lists.ettus.com<mailto:usrp-users-leave@lists.ettus.com>
[Attachment #3 (text/html)]
<html xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"> <head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks Rob. I agree. The \
documentation needs to be reworded to, "</span><span style="font-size:11.0pt">Note: \
There can always only be one streamer per channel…". That would probably help \
people out.<o:p></o:p></span></p> <p class="MsoNormal"><span \
style="font-size:11.0pt"><o:p> </o:p></span></p> <p class="MsoNormal"><span \
style="font-size:11.0pt">Regards,<o:p></o:p></span></p> <p class="MsoNormal"><span \
style="font-size:11.0pt">Zach</span><span \
style="font-size:11.0pt"><o:p></o:p></span></p> <p class="MsoNormal"><span \
style="font-size:11.0pt"><o:p> </o:p></span></p> <div \
id="mail-editor-reference-message-container"> <div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span \
style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">From: \
</span></b><span style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">Rob \
Kossler <rkossler@nd.edu><br> <b>Date: </b>Thursday, February 22, 2024 at \
3:13</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span><span \
style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">PM<br> \
<b>To: </b>Rohde, Zach (US 333G) <zachary.s.rohde@jpl.nasa.gov><br> <b>Cc: \
</b>usrp-users@lists.ettus.com <usrp-users@lists.ettus.com><br> <b>Subject: \
</b>[EXTERNAL] Re: [USRP-users] Multiple Streamers<o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Hi Zach,<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">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 only have one streamer per channel.<o:p></o:p></span></p> \
</div> <div>
<p class="MsoNormal"><span style="font-size:11.0pt">Rob<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">On Thu, Feb 22, 2024 at 5:08 PM \
Rohde, Zach (US 333G) via USRP-users <<a \
href="mailto:usrp-users@lists.ettus.com">usrp-users@lists.ettus.com</a>> \
wrote:<o:p></o:p></span></p> </div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in \
6.0pt;margin-left:4.8pt;margin-right:0in"> <div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span \
style="font-size:11.0pt">Hello,<o:p></o:p></span></p> <p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span \
style="font-size:11.0pt"> <o:p></o:p></span></p> <p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span \
style="font-size:11.0pt">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.<o:p></o:p></span></p> \
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span \
style="font-size:11.0pt"> <o:p></o:p></span></p> <p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span \
style="font-size:11.0pt">My question is <a \
href="https://urldefense.us/v3/__https:/files.ettus.com/manual/classuhd_1_1device.html \
*a66d1bf289dd03a03df3860f3eee578c0__;Iw!!PvBDto6Hs4WbVuu7!MXEfHO7LaEESM1gY0e9LRsk-dpWTIlz99pVQMh2wh6fVV6FRDjt23acYEhLtjRuAJl3tjfDFtGFkaUP6rAV99F5HpCU$" \
target="_blank"> the documentation</a> states: "Note: There can always only be one \
streamer. When calling get_tx_stream() a second time, the first streamer must be \
destroyed beforehand." Is this true? Why am I not seeing any undefined behavior or \
errors/warnings?<o:p></o:p></span></p> <p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span \
style="font-size:11.0pt"> <o:p></o:p></span></p> <p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span \
style="font-size:11.0pt">In the <a \
href="https://urldefense.us/v3/__https:/github.com/EttusResearch/uhd/blob/master/host/ \
lib/usrp/multi_usrp_rfnoc.cpp*L78__;Iw!!PvBDto6Hs4WbVuu7!MXEfHO7LaEESM1gY0e9LRsk-dpWTIlz99pVQMh2wh6fVV6FRDjt23acYEhLtjRuAJl3tjfDFtGFkaUP6rAV9F_MMrvg$" \
target="_blank"> documentation for multi_usrp_rfnoc</a>, I noticed a documentation \
stub that mentioned, "If there is only ever one Tx streamer, this will work as \
expected. For multiple streamers, only the last streamer's async messages will make \
it through." So, it seems the documentation is sort of contradicting one another on \
whether multiple TX streams are allowed.<o:p></o:p></span></p> <p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span \
style="font-size:11.0pt"> <o:p></o:p></span></p> <p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span \
style="font-size:11.0pt">Thanks,<o:p></o:p></span></p> <p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span \
style="font-size:11.0pt">Zach<o:p></o:p></span></p> </div>
</div>
<p class="MsoNormal"><span \
style="font-size:11.0pt">_______________________________________________<br> \
USRP-users mailing list -- <a href="mailto:usrp-users@lists.ettus.com" \
target="_blank"> usrp-users@lists.ettus.com</a><br>
To unsubscribe send an email to <a href="mailto:usrp-users-leave@lists.ettus.com" \
target="_blank"> usrp-users-leave@lists.ettus.com</a><o:p></o:p></span></p>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</body>
</html>
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com
--===============8290564019075290245==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic