It's either fixed or in review. At least on GNU Radio master branch. On Fri, 12 Mar 2021, 22:48 Marcus D. Leech, <[email protected]> wrote:
> On 03/12/2021 04:39 PM, Jerrid Plymale wrote: > > Ok, so what you're saying is I need to update Gnuradio to a newer version? > The way I have my software setup is everything is installed into virtual > environments. So when I initially started using the USRP, I created an > environment that had UHD 3.15 and Gnuradio 3.8 installed. When I saw UHD > 4.0 released, I created a new environment with UHD 4.0 and Gnuradio 3.8 > installed. So do I need to update Gnuradio to 3.9? > > Best Regards, > > Jerrid > > TBH, I'm not sure which versions of gr-uhd will prompt the message, that > is coming from the UHD library. > > But, like I said, it's just a *WARNING*. Things will still work just > fine. It's basically saying the "in the future, this will stop working". > > I'll note that in my current code base (GR 3.8.2, > 55621a9709b219551b908e67ee88f6f7ad2593cb) the recv_async_msg() call is > still tied > to the underlying multi_usrp device, and NOT the streamer. > > Perhaps the current maintainer of gr-uhd can comment on whether this is > fixed in a subsequent gr-uhd version (after GR 3.8.2) > > > > Sent from my Verizon, Samsung Galaxy smartphone > Get Outlook for Android <https://aka.ms/ghei36> > > ------------------------------ > *From:* Marcus D Leech <[email protected]> <[email protected]> > *Sent:* Friday, March 12, 2021 12:41:41 PM > *To:* Jerrid Plymale <[email protected]> > <[email protected]> > *Cc:* [email protected] <[email protected]> > <[email protected]> > *Subject:* Re: [USRP-users] Where do I find this call to change it. > > ok so this is likely a case of your gr-UHD assuming an older API for > recv_async_msg. > > This is just a warning that eventually that older API will go away. > > Probably if you had totally up to date everything, or a UHD library that > was of an earlier vintage that matched he-UHD, yiu wouldn’t get this > message. > > Sent from my iPhone > > On Mar 12, 2021, at 3:20 PM, Jerrid Plymale <[email protected]> > <[email protected]> wrote: > > > > Hello Marcus, > > > > This is coming from a Gnuradio flowgraph that I created myself. It’s got > USRP Rx and Tx blocks, a block that takes samples of the signal and > preforms some DSP, and a bunch of GUI variable control and variable display > blocks. > > > > Best Regards, > > > > Jerrid > > > > *From:* Marcus D Leech <[email protected]> <[email protected]> > *Sent:* Friday, March 12, 2021 12:17 PM > *To:* Jerrid Plymale <[email protected]> > <[email protected]> > *Cc:* [email protected] > *Subject:* Re: [USRP-users] Where do I find this call to change it. > > > > I think we need more context. > > > > Is this from a program you write yourself? > > > > Someone else’s code? > > > > A Gnuradio flow graph? Your own? Someone else’s? > > > > > > > > Sent from my iPhone > > > > On Mar 12, 2021, at 3:02 PM, Jerrid Plymale <[email protected]> > wrote: > > > > Hello All, > > > > Here is the warning message I am trying to solve: > > > > [WARNING] [MULTI_USRP] Calling multi_usrp::recv_async_msg() is deprecated > and can lead to unexpected behaviour. Prefer calling > tx_stream::recv_async_msg(). > > > > I am trying to solve this warning message when I am running my USRP X310, > but I have not had any luck finding the file I need to edit. Can anyone > direct me on how to solve this problem? > > > > Best Regards, > > > > Jerrid Plymale > > > > _______________________________________________ > USRP-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > > > _______________________________________________ > USRP-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ USRP-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
