Hi Anabel,
In my opinion, the error you are experiencing has nothing to do with
streaming performance settings (such as "performance" governor, network
descriptors, MTU size, etc). The issue seems to be that the two X310
devices do not have synchronized clocks. In addition to the physical
synchronization using OctoClock, you must also configure each device to use
external synchronization and you must tell each device to reset its FPGA
clock count at a common PPS. The typical sequence is: (1) wait for a PPS to
occur (by querying either device), (2) tell each device to reset its FPGA
clock at the subsequent PPS (this step must complete before the next PPS
arrives).

You mentioned that you are using rx_samples_to_file. Did you modify it in
any way?  What is your exact command line with all parameters?
Rob

On Thu, Dec 14, 2023 at 10:29 AM Anabel Almodovar <
anabel.almodo...@gmail.com> wrote:

> Dear Rob
>
> Thank you for your answer.
> I make use of the CDA-2990 octoclock as a source of synchronization
> between both USRPs, in addition to local oscillator sharing. I use dual
> 10GigEth connections and a MTU of 9000 to connect the USRPs to the PC.
>
> Due to various compatibility issues I am unable to upgrade the system.
>
> When I work with a sample rate of 10MSps I don't get problems but when I
> increase to 25MSps I start to get the error. I need them working with
> 100MSps. I have tried changing the CPU governor to "performance" to get the
> maximum working frequency (*sudo cpupower frequency-set --governor
> performance*), as well as changing the number of network interface
> descriptors to maximum (*sudo ethtool -G <interface> tx <max> rx <max>*),
> or increasing the dirty memory buffer (*sudo sysctl -w vm.dirty_ratio=80;
> sudo sysctl -w vm.dirty_background_ratio=50*), but I still get the same
> problem.
>
> Regards,
> Anabel
>
> El jue, 14 dic 2023 a las 15:38, Rob Kossler (<rkoss...@nd.edu>) escribió:
>
>> Hi Anabel,
>> How are you sync-ing the clocks on the two units? Do you have an external
>> PPS source and are you configuring both devices to use this external source?
>>
>> Finally, do you have the ability to upgrade your OS and your UHD
>> versions? There aren't many user's that are using UHD 3.12 so if you have
>> issues, it will be hard to get support.
>> Rob
>>
>> On Thu, Dec 14, 2023 at 5:20 AM Anabel Almodovar <
>> anabel.almodo...@gmail.com> wrote:
>>
>>> Dear all,
>>>
>>> I am trying to make an acquisition with two X310 equipped with two
>>> TwinRx. I am using Ubuntu 16.04 LTS 64-bit and UHD 3.12. My PC contains
>>> 128GB RAM and an Intel® Xeon(R) Silver 4114 CPU @ 2.20GHz × 40 and a 4TB
>>> SSD. I have modified the example rx_samples_to_file.cpp code to get 8
>>> channels and I get the following error:
>>>
>>> *D*
>>> *[ERROR] [STREAMER] The receive packet handler failed to time-align
>>> packets. 1002 received packets were processed by the handler. However, a
>>> timestamp match could not be determined.*
>>> *Timeout while streaming*
>>>
>>> *[ERROR] [X300] 192.168.60.2 <http://192.168.60.2>: x300 fw
>>> communication failure #1*
>>> *EnvironmentError: IOError: x300 fw poke32 - reply timed out*
>>> *[ERROR] [UHD] An unexpected exception was caught in a task loop.The
>>> task loop will now exit, things may not work.AssertionError: reply.sequence
>>> == request.sequence*
>>> *  in virtual void
>>> x300_ctrl_iface_enet::__poke32(uhd::wb_iface::wb_addr_type, uint32_t)*
>>> *  at
>>> /home/rs3_lab/workarea-uhd/uhd/host/lib/usrp/x300/x300_fw_ctrl.cpp:135*
>>>
>>> I don't know how to solve the Timeout problem, I have tried to start the
>>> acquisition 1.1 sg in time. But it didn't work.
>>>
>>>
>>> *        stream_cmd.stream_now = false;        stream_cmd.time_spec =
>>> usrp->get_time_last_pps(0)+1.1;*
>>>
>>> What is the problem and how can I fix it?
>>>
>>> Regards,
>>> Anabel
>>>
>>> _______________________________________________
>>> USRP-users mailing list -- usrp-users@lists.ettus.com
>>> To unsubscribe send an email to usrp-users-le...@lists.ettus.com
>>>
>>
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com

Reply via email to