On 02/25/2020 03:59 PM, Simon G4ELI via USRP-users wrote:
Hi,
Question is in two related parts.
1 Closing Connection
In 3.10.0 when I was finished streaming data I would call
1. m_usrp->reset() and
2. m_rx_stream->reset()
but in 3.15 LTS I don’t see a way to reset / discard the pointers
returned from uhd::usrp::multi_usrp::make and m_usrp->get_rx_stream.
The reset calls no longer exist.
So, how do I correctly do this?
You should just be able to call the destructor:
https://files.ettus.com/manual/classuhd_1_1usrp_1_1multi__usrp.html#a6c904057108e52d685b27496a11518db
2 X310
[Note – only a problem with the X310, B200 works well]
When I want to change the sample rate, for example from 1 Msps to 10 Msps:
1. Close (see above)
2. Create new m_usrp via uhd::usrp::multi_usrp::make
3. Set new sample rate
4. Call m_usrp->get_rs_stream but I get an exception: exception
0000054F (1359), RuntimeError: On node 0/DDC_0, output port 0 is
already connected
So this refers back to 1 – how do I get the connection to the X310
fully closed?
The X310 takes 15-20 seconds to reset itself internally when you close
the session with it. There's never any reason to recreate the USRP
object just to change the sample rate. So if your frequency-changing
code does that, and expects the USRP to "come back" immediately
after you've reset it, there'll be some strange behavior at the
network level. So, yeah, sample-rate change shouldn't need anything so
"drastic".
TIA
Simon Brown, G4ELI
https://www.sdr-radio.com
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
