Hi, Marcus.1. usrp_list_sensorsI didn't give any aruguments, I just typed "sudo 
./usrp_list_sensors"-------------------OUTPUT 
1---------------------------------Device contains 1 motherboard(s).  
_____________________________________________________ /|       Sensors for 
motherboard 0: |   |   * GPS_GPGGA: 
$GPGGA,140136.00,0000.0000,N,00000.0000,E,0,99,1.0,0.0,M,0.0,M,,*5D |   * 
GPS_GPRMC: $GPRMC,140136.00,V,0000.0000,N,00000.0000,E,0.0,0.0,010106,,*23 |   
* GPS epoch time: 1136124097 seconds|   * GPS lock status: unlocked|   * 
GPS_SERVO: 06-01-01 0 39517 0.00 1.00E-08 0 0 1 0x38 |   * Ref: locked|     
_____________________________________________________|    /|   |       RX 
Sensors: |   |   |   |   Chan 0: |   |   * temp: 47.485382 C|   |   * RSSI: 
-50.750000 dB|   |   * LO: locked|   |     
_____________________________________________________|    /|   |       TX 
Sensors: |   |   |   |   Chan 0: |   |   * temp: 47.485382 C|   |   * LO: 
locked-------------------OUTPUT 2---------------------------------Device 
contains 1 motherboard(s).  
_____________________________________________________ /|       Sensors for 
motherboard 0: |   |   * GPS_GPGGA: 
$GPGGA,140311.00,0000.0000,N,00000.0000,E,0,99,1.0,0.0,M,0.0,M,,*5A |   * 
GPS_GPRMC: $GPRMC,140311.00,V,0000.0000,N,00000.0000,E,0.0,0.0,010106,,*24 |   
* GPS epoch time: 1136124192 seconds|   * GPS lock status: unlocked|   * 
GPS_SERVO: 06-01-01 0 39518 0.00 1.00E-08 0 0 1 0x38 |   * Ref: unlocked|     
_____________________________________________________|    /|   |       RX 
Sensors: |   |   |   |   Chan 0: |   |   * temp: 45.730995 C|   |   * RSSI: 
-50.750000 dB|   |   * LO: locked|   |     
_____________________________________________________|    /|   |       TX 
Sensors: |   |   |   |   Chan 0: |   |   * temp: 46.023392 C|   |   * LO: 
locked2. test_clock_synchI didn't give any arugument. I typed "sudo 
./test_clock_synch"------------------------------------OUTPUT---------------------------------Creating
 the Clock device with: [INFO] [UHD] linux; GNU C++ version 4.8.4; 
Boost_105400; UHD_3.11.0.1-0-ge00f1f37[INFO] [OCTOCLOCK] Opening an OctoClock 
device...[INFO] [OCTOCLOCK] Detecting internal GPSDO...[INFO] [GPS] Found an 
internal GPSDO: LC_XO, Firmware Rev 0.929a[INFO] [OCTOCLOCK] Detecting external 
reference...false[INFO] [OCTOCLOCK] Detecting switch position...Prefer 
internal[INFO] [OCTOCLOCK] Device is using internal referenceCreating the USRP 
device with: [INFO] [B200] Detected Device: B200[INFO] [B200] Operating over 
USB 3.[INFO] [B200] Detecting internal GPSDO.... [INFO] [GPS] Found an internal 
GPSDO: GPSTCXO , Firmware Rev 0.929a[INFO] [B200] Initialize CODEC 
control...[INFO] [B200] Initialize Radio control...[INFO] [B200] Performing 
register loopback test... [INFO] [B200] Register loopback test passed[INFO] 
[AD936X] Performing CODEC loopback test... [INFO] [AD936X] CODEC loopback test 
passed[INFO] [B200] Setting master clock rate selection to 'automatic'.[INFO] 
[B200] Asking for clock rate 16.000000 MHz... [INFO] [B200] Actually got clock 
rate 16.000000 MHz.Checking USRP devices for lock. * 3113D41: falseWARNING: One 
or more devices not locked.Querying Clock for time and setting USRP 
times...Running 10 comparisons at random intervals.Comparison #1 * Clock time: 
1136131150 * 3113D41 time: 1136131150Comparison #2 * Clock time: 1136131155 * 
3113D41 time: 1136131155Comparison #3 * Clock time: 1136131162 * 3113D41 time: 
1136131162Comparison #4 * Clock time: 1136131166 * 3113D41 time: 
1136131166Comparison #5 * Clock time: 1136131175 * 3113D41 time: 
1136131175Comparison #6 * Clock time: 1136131180 * 3113D41 time: 
1136131180Comparison #7 * Clock time: 1136131189 * 3113D41 time: 
1136131189Comparison #8 * Clock time: 1136131191 * 3113D41 time: 
1136131191Comparison #9 * Clock time: 1136131201 * 3113D41 time: 
1136131201Comparison #10 * Clock time: 1136131211 * 3113D41 time: 
1136131211Number of matches: 10/103. I use UHD_3.11.0.1-0-ge00f1f374. The weird 
thing is that when I executed the test_clock_synch "without reference clock/PPS 
connection"(i.e. the usrp does not get reference clock and PPS from 
octoclock),It also showed that Octoclock time == usrp time, this does not make 
sense. For example,Running 10 comparisons at random intervals.Comparison #1 * 
Clock time: 1136131502 * 3113D41 time: 1136131502Comparison #2 * Clock time: 
1136131505 * 3113D41 time: 1136131505....This is totally weird.. Am I something 
doing wrong?FYI, when I typed "sudo uhd_find_device"the 
output:---------------------------------------------------- UHD Device 
0--------------------------------------------------Device Address:    serial: 
3113D41    name: syssec_b200_1    product: B200    type: 
b200---------------------------------------------------- UHD Device 
1--------------------------------------------------Device Address:    serial: 
312D3E7    addr: 192.168.10.3    name:     type: octoclockHojoon
-----------------------Original Message-----------------------From: "Marcus D. 
Leech via USRP-users" <usrp-users@lists.ettus.com>To: 
usrp-users@lists.ettus.comSent date: 2018-04-25 02:51:18 GMT +0900 
(ROK)Subject: Re: [USRP-users] Octoclock reference unlock
  
   
  
  
  
   On 04/24/2018 11:34 AM, Hojoon Yang via USRP-users wrote:
    
   
   
   Hi. 
    
   I got an octoclock-G (GPSDO included) yesterday. 
    
   I connected the octoclock (without external antenna) to usrp b210 properly. 
    
   However, when I executed the usrp_list_sensors.cpp or test_clock_synch.cpp 
which are included in examples, 
    
   sometimes I got that Reference is not locked, sometimes I got ref is locked. 
    
   Why is this so unstable? is this a normal behavior?  
    
   If I use GPS antenna, the reference lock status would be stable as "locked"? 
    
   Hojoon.  
   
   Could you share the exact arguments you used with these two applications?
   
   What version of UHD are you using?
   
   
   
     
 
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Reply via email to