Re: [USRP-users] N310 and set_time_source()

2018-09-20 Thread Rob Kossler via USRP-users
Rather than a try/catch block, I just changed my code from usrp->set_time_source(val,mboard); to if (usrp->get_time_source(mboard)!=val) usrp->set_time_source(val,mboard); This seems to handle it for me. I also did the same for usrp->set_clock_source() because I was experiencing some long d

Re: [USRP-users] N310 and set_time_source()

2018-09-20 Thread Rob Kossler via USRP-users
Yes. I can do that. On Thu, Sep 20, 2018 at 12:14 PM Michael West wrote: > Hi Rob, > > Thanks for letting us know. We will look into that. It is hard to tell > from the error if MPM is doing the work and the RPC call is just timing out > or it is failing to execute in MPM altogether. We will

Re: [USRP-users] N310 and set_time_source()

2018-09-20 Thread Michael West via USRP-users
Hi Rob, Thanks for letting us know. We will look into that. It is hard to tell from the error if MPM is doing the work and the RPC call is just timing out or it is failing to execute in MPM altogether. We will try to reproduce it and see what is going on. In the meantime, is it possible for yo

[USRP-users] N310 and set_time_source()

2018-09-20 Thread Rob Kossler via USRP-users
With the latest 3.13 release and the N310, I get an exception when calling usrp->set_time_source(). It seems that this should just be a warning (or nothing at all if the requested source is equal to the current source). I realize that with the N310, it is necessary to set the time source in the a