[USRP-users] Re: using rfnoc_graph and usrp

2023-02-24 Thread jmaloyan
i found that I needed to create a timekeeper, within the mb_controller. i.e `uhd::rfnoc::mb_controller::timekeeper::sptr tk = graph->get_mb_controller(0)->get_timekeeper(0);` This seems to do the trick. Im now getting a late error, but it is probably another kind of issue. _

[USRP-users] Re: using rfnoc_graph and usrp

2023-02-24 Thread Marcus D. Leech
On 24/02/2023 11:05, jmalo...@umass.edu wrote: Hello, I am currently getting the following error, but I am lost as to how to work around it… |[ERROR] [RPC] Someone tried to claim this device again (From: 192.168.10.1)| |[WARNING] [MPM.RPCServer] Someone tried to claim this device again (

[USRP-users] Re: using rfnoc_graph and usrp

2023-02-24 Thread Marcus D. Leech
On 24/02/2023 11:05, jmalo...@umass.edu wrote: Hello, I am currently getting the following error, but I am lost as to how to work around it… |[ERROR] [RPC] Someone tried to claim this device again (From: 192.168.10.1)| |[WARNING] [MPM.RPCServer] Someone tried to claim this device again (

[USRP-users] Re: libuhd - read IQ samples without discontinuities

2023-02-24 Thread Marcus D. Leech
On 24/02/2023 11:06, Rob Kossler wrote: Hi Peter, Each recv() call returns metadata with a timestamp. You can verify each receive has advanced exactly the right amount of time corresponding to 16k samples. If this verifies, you haven't dropped anything. The metadata also includes the Overflow i

[USRP-users] Re: libuhd - read IQ samples without discontinuities

2023-02-24 Thread Rob Kossler
Hi Peter, Each recv() call returns metadata with a timestamp. You can verify each receive has advanced exactly the right amount of time corresponding to 16k samples. If this verifies, you haven't dropped anything. The metadata also includes the Overflow indication. To be honest, I have no idea wh

[USRP-users] using rfnoc_graph and usrp

2023-02-24 Thread jmaloyan
Hello, I am currently getting the following error, but I am lost as to how to work around it… `[ERROR] [RPC] Someone tried to claim this device again (From: 192.168.10.1)` `[WARNING] [MPM.RPCServer] Someone tried to claim this device again (From: 192.168.10.1)` It appears the problem comes fr

[USRP-users] Re: libuhd - read IQ samples without discontinuities

2023-02-24 Thread Marcus D. Leech
On 24/02/2023 03:40, Peter Featherstone (XENINT) wrote: Hi Marcus, /To clarify.    You are in a loop, reading exactly 16K of data, then going to sleep for 5 seconds, and you have a   STREAM_MODE_START_CONTINUOUS stream?/// Exactly that. So do you reckon it’s possible to get no OVERFLOW erro

[USRP-users] Re: REF IN and PPS IN signals work on X300, fail to lock on N300

2023-02-24 Thread Marcus D. Leech
On 24/02/2023 04:14, Vermeulen, Bas (Consultant) via USRP-users wrote: Hi, I am trying to get a working multi-usrp setup with both X300 and N300. I currently have a signal generator generating a 10 MHz clock and a 1PPS signal. Those are connected to a splitter (each), and then connected to bot

[USRP-users] REF IN and PPS IN signals work on X300, fail to lock on N300

2023-02-24 Thread Vermeulen, Bas (Consultant) via USRP-users
Hi, I am trying to get a working multi-usrp setup with both X300 and N300. I currently have a signal generator generating a 10 MHz clock and a 1PPS signal. Those are connected to a splitter (each), and then connected to both X300s REF IN and 1PPS IN. This setup works, and with srsRAN I can use t