On 2022-10-19 17:51, Jonathan Pratt wrote:

Thanks for the information. we would be surprised if it wasn’t a hardware issue.

A more full story  is that we have three systems deployed and are not physically accessible (and not returnable) so that we cannot do any hardware diagnostics. The other two systems have died and are not visible on their network interfaces. They actually died before deployment but the team responsible for the enclosure and power supply sequencing failed to let us know prior to the deployment date that they were non-functioning. One of these we have tried to recover through JTAG reprogramming but no success there. As for this last one that was working at the time of deployment, a insignificant (incidental) amount of investigation showed that the power sequencing affected whether or not the x310 was functioning. Now it appears but is failing with the error as described. The people responsible for the enclosure also made it exceedingly difficult for us to do even software diagnostics by choosing a USB port for their convenience rather than the alternative one we specified resulting in limited access of the processing platform (that is running gnu radio) so that the only thing we can do is insert a USB drive with arbitrary code on it which will get executed when the power is cycled. This makes reprogramming UHD difficult and treacherous. We only have access to these systems in this way for one more day, so everything is looking grim.

Personally, I suspect that the power switching has fried 2 ½ x310s and this project is a dead loss for us.

thanks - JP


It would be useful to the rest of us to know exactly how you believe the power sequencing led to the failure of these devices.   I understand, given the domain of use, that such information may not be readily available.

But if the power-sequencing to an X310 can fry it, I think this community would surely like to know how...

_______________________________________________
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