It takes 10a of minutes from a cold start for the GPSDO to be locked to the GPS satellite signals. The process is inherently slow because the PLL only gets a new phase/frequency estimate once per second.
Sent from my iPhone > On Sep 10, 2020, at 1:50 PM, Xiang Ma <[email protected]> wrote: > > > Great thanks. I moved my computer out of the building, it works. I can get > the GPS signals with ./query_gpsdo_sensors command. > However, ./sync_to_gps command still failed. > > hu@hu:/usr/local/lib/uhd/examples$ ./sync_to_gps > Creating the USRP device with: ... > [INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; > UHD_3.15.0.HEAD-0-gaea0e2de > [INFO] [X300] X300 initialization sequence... > [INFO] [X300] Maximum frame size: 1472 bytes. > [INFO] [X300] Radio 1x clock: 200 MHz > [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929b > [WARNING] [UDP] The send buffer could not be resized sufficiently. > Target sock buff size: 2426666 bytes. > Actual sock buff size: 1048576 bytes. > See the transport application notes on buffer resizing. > Please run: sudo sysctl -w net.core.wmem_max=2426666 > [WARNING] [UDP] The send buffer could not be resized sufficiently. > Target sock buff size: 2426666 bytes. > Actual sock buff size: 1048576 bytes. > See the transport application notes on buffer resizing. > Please run: sudo sysctl -w net.core.wmem_max=2426666 > [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D00000000000) > [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1300 MB/s) > [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1302 MB/s) > [WARNING] [UDP] The send buffer could not be resized sufficiently. > Target sock buff size: 2426666 bytes. > Actual sock buff size: 1048576 bytes. > See the transport application notes on buffer resizing. > Please run: sudo sysctl -w net.core.wmem_max=2426666 > [WARNING] [UDP] The send buffer could not be resized sufficiently. > Target sock buff size: 2426666 bytes. > Actual sock buff size: 1048576 bytes. > See the transport application notes on buffer resizing. > Please run: sudo sysctl -w net.core.wmem_max=2426666 > [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000000001) > [WARNING] [UDP] The send buffer could not be resized sufficiently. > Target sock buff size: 2426666 bytes. > Actual sock buff size: 1048576 bytes. > See the transport application notes on buffer resizing. > Please run: sudo sysctl -w net.core.wmem_max=2426666 > [WARNING] [UDP] The send buffer could not be resized sufficiently. > Target sock buff size: 2426666 bytes. > Actual sock buff size: 1048576 bytes. > See the transport application notes on buffer resizing. > Please run: sudo sysctl -w net.core.wmem_max=2426666 > [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000000001) > [WARNING] [UDP] The send buffer could not be resized sufficiently. > Target sock buff size: 2426666 bytes. > Actual sock buff size: 1048576 bytes. > See the transport application notes on buffer resizing. > Please run: sudo sysctl -w net.core.wmem_max=2426666 > [WARNING] [UDP] The send buffer could not be resized sufficiently. > Target sock buff size: 2426666 bytes. > Actual sock buff size: 1048576 bytes. > See the transport application notes on buffer resizing. > Please run: sudo sysctl -w net.core.wmem_max=2426666 > [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000) > [WARNING] [UDP] The send buffer could not be resized sufficiently. > Target sock buff size: 2426666 bytes. > Actual sock buff size: 1048576 bytes. > See the transport application notes on buffer resizing. > Please run: sudo sysctl -w net.core.wmem_max=2426666 > [WARNING] [UDP] The send buffer could not be resized sufficiently. > Target sock buff size: 2426666 bytes. > Actual sock buff size: 1048576 bytes. > See the transport application notes on buffer resizing. > Please run: sudo sysctl -w net.core.wmem_max=2426666 > [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000) > [WARNING] [UDP] The send buffer could not be resized sufficiently. > Target sock buff size: 2426666 bytes. > Actual sock buff size: 1048576 bytes. > See the transport application notes on buffer resizing. > Please run: sudo sysctl -w net.core.wmem_max=2426666 > [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000000) > [WARNING] [UDP] The send buffer could not be resized sufficiently. > Target sock buff size: 2426666 bytes. > Actual sock buff size: 1048576 bytes. > See the transport application notes on buffer resizing. > Please run: sudo sysctl -w net.core.wmem_max=2426666 > [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000000) > [WARNING] [UDP] The send buffer could not be resized sufficiently. > Target sock buff size: 2426666 bytes. > Actual sock buff size: 1048576 bytes. > See the transport application notes on buffer resizing. > Please run: sudo sysctl -w net.core.wmem_max=2426666 > Using Device: Single USRP: > Device: X-Series Device > Mboard 0: X310 > RX Channel: 0 > RX DSP: 0 > RX Dboard: A > RX Subdev: UBX RX > RX Channel: 1 > RX DSP: 0 > RX Dboard: B > RX Subdev: UBX RX > TX Channel: 0 > TX DSP: 0 > TX Dboard: A > TX Subdev: UBX TX > TX Channel: 1 > TX DSP: 0 > TX Dboard: B > TX Subdev: UBX TX > > Synchronizing mboard 0: X310 > > **************************************Helpful Notes on Clock/PPS > Selection************************************** > As you can see, the default 10 MHz Reference and 1 PPS signals are now from > the GPSDO. > If you would like to use the internal reference(TCXO) in other applications, > you must configure that explicitly. > You can no longer select the external SMAs for 10 MHz or 1 PPS signaling. > **************************************************************************************************************** > > Waiting for reference lock...LOCKED > WARNING: GPS not locked - time will not be accurate until locked > USRP time: 1136073603.000000000 > GPSDO time: 1136073600.000000000 > > ERROR: Failed to synchronize USRP time to GPS time > > >> On Thu, Sep 10, 2020 at 10:17 AM Marcus D. Leech <[email protected]> >> wrote: >>> On 09/10/2020 12:12 PM, Xiang Ma wrote: >>> I double checked the installation, I think it is ok. When I start the USRP, >>> There will be two green lights on, several seconds later, 1 light off, and >>> 1-2 seconds later, another light is also off. >>> >>> also if there is a GPSDO installation problem, why [INFO] [GPS] Found an >>> internal GPSDO: LC_XO, Firmware Rev 0.929b appears? >> Because it can "find" the GPSDO and there can still be problems with the >> electrical interface to it. There are several signals between the >> motherboard and the GPSDO module. So, if the NMEA signals work, the >> motherboard can still "find" the GPSDO, but other things will >> go wrong despite that. That's what the message at the bottom of your test >> shows--it cannot see the GPSDO-Locked signal--which in this >> case might be expected, since you reported that you're running this inside >> a building--no GPS LOCK is possible in that case, since the GPSDO >> cannot see the sky (and, hence, the satellites that provide GPS service). >> >> >>> >>> Thanks. >>> >>> On Thu, Sep 10, 2020 at 10:07 AM Marcus D Leech <[email protected]> >>> wrote: >>>> To me the message at the end suggests even more strongly that there’s a >>>> hardware problem with the GPSDO installation. >>>> >>>> Sent from my iPhone >>>> >>>>> On Sep 10, 2020, at 11:50 AM, Xiang Ma <[email protected]> wrote: >>>>> >>>>> >>>>> But you can see there is an info: >>>>> [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929b >>>>> >>>>> Also, when I run /usr/local/lib/uhd/examples/sync_to_gps >>>>> >>>>> It shows: >>>>> Creating the USRP device with: ... >>>>> [INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; >>>>> UHD_3.15.0.HEAD-0-gaea0e2de >>>>> [INFO] [X300] X300 initialization sequence... >>>>> [INFO] [X300] Maximum frame size: 1472 bytes. >>>>> [INFO] [X300] Radio 1x clock: 200 MHz >>>>> [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929b >>>>> [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: >>>>> 0xF1F0D00000000000) >>>>> [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1300 MB/s) >>>>> [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1317 MB/s) >>>>> [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000000001) >>>>> [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000000001) >>>>> [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000) >>>>> [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000) >>>>> [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000000) >>>>> [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000000) >>>>> Using Device: Single USRP: >>>>> Device: X-Series Device >>>>> Mboard 0: X310 >>>>> RX Channel: 0 >>>>> RX DSP: 0 >>>>> RX Dboard: A >>>>> RX Subdev: UBX RX >>>>> RX Channel: 1 >>>>> RX DSP: 0 >>>>> RX Dboard: B >>>>> RX Subdev: UBX RX >>>>> TX Channel: 0 >>>>> TX DSP: 0 >>>>> TX Dboard: A >>>>> TX Subdev: UBX TX >>>>> TX Channel: 1 >>>>> TX DSP: 0 >>>>> TX Dboard: B >>>>> TX Subdev: UBX TX >>>>> >>>>> Synchronizing mboard 0: X310 >>>>> >>>>> **************************************Helpful Notes on Clock/PPS >>>>> Selection************************************** >>>>> As you can see, the default 10 MHz Reference and 1 PPS signals are now >>>>> from the GPSDO. >>>>> If you would like to use the internal reference(TCXO) in other >>>>> applications, you must configure that explicitly. >>>>> You can no longer select the external SMAs for 10 MHz or 1 PPS signaling. >>>>> **************************************************************************************************************** >>>>> >>>>> Waiting for reference lock...LOCKED >>>>> >>>>> Error: ValueError: locked(): unable to determine GPS lock statusThis >>>>> could mean that you have not installed the GPSDO correctly. >>>>> >>>>> Visit one of these pages if the problem persists: >>>>> * N2X0/E1X0: http://files.ettus.com/manual/page_gpsdo.html * X3X0: >>>>> http://files.ettus.com/manual/page_gpsdo_x3x0.html >>>>> >>>>> * E3X0: http://files.ettus.com/manual/page_usrp_e3x0.html#e3x0_hw_gps >>>>> >>>>> On Thu, Sep 10, 2020 at 9:38 AM Marcus D. Leech via USRP-users >>>>> <[email protected]> wrote: >>>>>> On 09/10/2020 10:12 AM, Xiang Ma via USRP-users wrote: >>>>>>> Hi, >>>>>>> >>>>>>> I am using the /usr/local/lib/uhd/utils/query_gpsdo_sensors to get >>>>>>> gps information, but it shows: Waiting for the GPSDO to warm >>>>>>> up........... >>>>>>> No response from GPSDO in 30 seconds >>>>>>> >>>>>>> This is the whole information: >>>>>>> >>>>>>> hu@hu:~$ /usr/local/lib/uhd/utils/query_gpsdo_sensors >>>>>>> >>>>>>> Creating the USRP device with: ... >>>>>>> [INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; >>>>>>> UHD_3.15.0.HEAD-0-gaea0e2de >>>>>>> [INFO] [X300] X300 initialization sequence... >>>>>>> [INFO] [X300] Maximum frame size: 1472 bytes. >>>>>>> [INFO] [X300] Radio 1x clock: 200 MHz >>>>>>> [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929b >>>>>>> [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: >>>>>>> 0xF1F0D00000000000) >>>>>>> [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1304 MB/s) >>>>>>> [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1306 MB/s) >>>>>>> [INFO] [0/Radio_0] Initializing block control (NOC ID: >>>>>>> 0x12AD100000000001) >>>>>>> [INFO] [0/Radio_1] Initializing block control (NOC ID: >>>>>>> 0x12AD100000000001) >>>>>>> [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000) >>>>>>> [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000) >>>>>>> [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000000) >>>>>>> [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000000) >>>>>>> Using Device: Single USRP: >>>>>>> Device: X-Series Device >>>>>>> Mboard 0: X310 >>>>>>> RX Channel: 0 >>>>>>> RX DSP: 0 >>>>>>> RX Dboard: A >>>>>>> RX Subdev: UBX RX >>>>>>> RX Channel: 1 >>>>>>> RX DSP: 0 >>>>>>> RX Dboard: B >>>>>>> RX Subdev: UBX RX >>>>>>> TX Channel: 0 >>>>>>> TX DSP: 0 >>>>>>> TX Dboard: A >>>>>>> TX Subdev: UBX TX >>>>>>> TX Channel: 1 >>>>>>> TX DSP: 0 >>>>>>> TX Dboard: B >>>>>>> TX Subdev: UBX TX >>>>>>> >>>>>>> Setting the reference clock source to "gpsdo"... >>>>>>> Clock source is now gpsdo >>>>>>> Setting the reference clock source to "gpsdo"... >>>>>>> Time source is now gpsdo >>>>>>> Waiting for ref_locked...USRP Locked to Reference. >>>>>>> **************************************Helpful Notes on Clock/PPS >>>>>>> Selection************************************** >>>>>>> As you can see, the default 10 MHz Reference and 1 PPS signals are now >>>>>>> from the GPSDO. >>>>>>> If you would like to use the internal reference(TCXO) in other >>>>>>> applications, you must configure that explicitly. >>>>>>> **************************************************************************************************************** >>>>>>> Waiting for the GPSDO to warm up........... >>>>>>> No response from GPSDO in 30 seconds >>>>>>> >>>>>>> I do plug the GPSDO to the board, and I plug the 5V active GPS antenna >>>>>>> in the `GPS ANT` connector at the rear panel. But I am not sure why. I >>>>>>> just want to get the location information. (btw, is it because I am in >>>>>>> the indoor area?) >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> Xiang Ma >>>>>>> >>>>>>> -- >>>>>>> Xiang Ma, Ph.D. Student >>>>>>> College of Engineering >>>>>>> Utah State University >>>>>>> E-mail:[email protected] >>>>>>> >>>>>>> >>>>>> I would re-check the GPSDO installation. You may have bent one of the >>>>>> pins when you installed it. >>>>>> >>>>>> Also, it won't be able to get a "fix" unless the antenna can "see" the >>>>>> sky. Most buildings are not that transparent at 1575MHz. >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> USRP-users mailing list >>>>>> [email protected] >>>>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >>>>> >>>>> >>>>> -- >>>>> Xiang Ma, Ph.D. Student >>>>> College of Engineering >>>>> Utah State University >>>>> E-mail:[email protected] >>> >>> >>> -- >>> Xiang Ma, Ph.D. Student >>> College of Engineering >>> Utah State University >>> E-mail:[email protected] >> > > > -- > Xiang Ma, Ph.D. Student > College of Engineering > Utah State University > E-mail:[email protected]
_______________________________________________ USRP-users mailing list [email protected] http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
