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 From: Jonathon Pendlum <jonathon.pend...@ettus.com> Sent: Thursday, 20 October 2022 01:04 To: Jonathan Pratt <jpr...@srcaus.com> Cc: usrp-users@lists.ettus.com Subject: Re: [USRP-users] Re: [ERROR] [RFNOC::GRAPH] Error during initialization of block 0/Radio#0 WARNING: This message has originated from an untrusted source. Be mindful of attachments and embedded links. Hello JP, You can try updating UHD and the FPGA image to UHD 4.3. If that doesn’t help, then this issue is very likely a hardware failure and you’ll want to contact supp...@ettus.com<mailto:supp...@ettus.com> about RMAing the device. Jonathon On Tue, Oct 18, 2022 at 7:57 PM Jonathan Pratt <jpr...@srcaus.com<mailto:jpr...@srcaus.com>> wrote: To clarify, the communication has previously worked with the same software/radio configuration. This is an evolved error and we would just like to know what it means so that we have the hope of fixing it - needs to be a remote fix as we no longer have physical access to the radio. thanks - JP -----Original Message----- From: Marcus D. Leech <patchvonbr...@gmail.com<mailto:patchvonbr...@gmail.com>> Sent: Wednesday, 19 October 2022 09:52 To: usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> Subject: [USRP-users] Re: [ERROR] [RFNOC::GRAPH] Error during initialization of block 0/Radio#0 WARNING: This message has originated from an untrusted source. Be mindful of attachments and embedded links. On 2022-10-18 19:41, Jonathan Pratt wrote: > Hi > We are trying to talk to an x310. Access to the device is limited to the > ethernet connection. > The message we get back when starting a gnuradio flow graph is [ERROR] > [RFNOC::GRAPH] Error during initialization of block 0/Radio#0! > [ERROR] [RFNOC::GRAPH] Caught exception while initializing graph: > RuntimeError: self_cal_adc_capture_delay: Self calibration failed. > Convergence error. > > The X310 has ONE TwinRx RF Daughterboard attached. > > Can someone please indicate what the error means and suggest a > workaround? Please ignore any prefix that we have added > > thanks - JP > _______________________________________________ > USRP-users mailing list -- > usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> To unsubscribe > send an email to > usrp-users-le...@lists.ettus.com<mailto:usrp-users-le...@lists.ettus.com> What version of UHD are you using? What version of Gnu Radio? I've been using an X310 with UHD 4.1.0.5 and GR version 3.10.1.1 with two TwinRX installed, without any issues. I'm using the first SFP port (SFP0) but at 10Gbit. I've previously used it at 1GBit without any issues. _______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> To unsubscribe send an email to usrp-users-le...@lists.ettus.com<mailto:usrp-users-le...@lists.ettus.com> _______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> To unsubscribe send an email to usrp-users-le...@lists.ettus.com<mailto:usrp-users-le...@lists.ettus.com> -- Jonathon DISCLAIMER: Any attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system, or for use in hazardous environments. You assume all risks for use of the Code. Use of the Code is subject to terms of the licenses to the UHD or RFNoC code with which the Code is used. Standard licenses to UHD and RFNoC can be found at https://www.ettus.com/sdr-software/licenses/. NI will only perform services based on its understanding and condition that the goods or services (i) are not for the use in the production or development of any item produced, purchased, or ordered by any entity with a footnote 1 designation in the license requirement column of Supplement No. 4 to Part 744, U.S. Export Administration Regulations and (ii) such a company is not a party to the transaction. If our understanding is incorrect, please notify us immediately because a specific authorization may be required from the U.S. Commerce Department before the transaction may proceed further.
_______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
