Hi,
We are in the process of prototyping a setup using an X300 with two
UBX-40 daughterboards to be used in the validation of an externally
provided signal source. The daughterboards are each dedicated to one of
two tasks: transmitting a pre-recorded reference signal in a loop at 50
MSps, and capturing that same signal again after passing through a chain
of devices under test at 25MSps. This is to run continuously up to 24 hours.
The X300 is connected to the (dedicated) host computer via a 10Gbps
connection to an Intel X520-DA2 NAC over SFP+. On the host, we are
currently using the /kitchen_sink/ utility included with UHD to run the
system in multi-channel mode. We are using UHD 3.11.0.1.
The system works flawlessly when performing short measurements (say, up
to an hour or so). However, having recently started setting up the
system for long 24 hour tests, we are seeing timeouts from which UHD is
unable to recover. These timeouts occur randomly: sometimes they occur
after ~1 hours, other times they occur after ~18 hours and everywhere in
between. Naturally, this random behaviour makes it difficult to debug.
The error message retrieved from UHD is as follows:
[ERROR] [X300] 192.168.50.2: x300 fw communication failure #1
EnvironmentError: IOError: x300 fw poke32 - reply timed out
UUU[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 /usr/uhd/uhd-release_003_011_000_001/host/lib/usrp/x300/x300_fw_ctrl.cpp:134
[ERROR] [X300] 192.168.50.2: x300 fw communication failure #1
EnvironmentError: IOError: x300 fw peek32 - reply timed out
[ERROR] [X300] 192.168.50.2: x300 fw communication failure #2
EnvironmentError: IOError: x300 fw peek32 - reply timed out
UDOterminate called after throwing an instance of ‘uhd::assertion_error’
what(): AssertionError: reply.sequence == request.sequence
in virtual uint32_t x300_ctrl_iface_enet::__peek32(uhd::wb_iface::wb_addr_type)
at /usr/uhd/uhd-release_003_011_000_001/host/lib/usrp/x300/x300_fw_ctrl.cpp:163
As previous messages on this list have mentioned varying the MTU
settings (for example:
http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2014-November/039561.html),
this was the first thing we tried. Unfortunately, these timeouts occur
more often at lower MTU values.
Hopefully someone is able to point us in the right direction. Perhaps we
are dealing with hardware issues here, but I'd I hope we are able to
solve this through software.
Thanks,
Stefan van der Linden
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
