I am having a similar issue. I have an Octoclock-G that is a bit older. I
followed the steps to reflash the MCU using the Altera-ICE programmer,
enabling Ethernet access in the older device. I have a similar issue to Bob
where I still can't see the GPSDO sensor in the probe. Are there any legacy
tricks for this?

Thanks,
Pat

On Mon, Jul 19, 2021 at 2:00 PM Tillson, Bob (US) via USRP-users <
[email protected]> wrote:

> I have an octoclock-g with gps lock light on and all other lights
> functioning “normally”.
>
>
>
> I want to get nmea strings from it, but when I probe it, it tells me there
> is no gpsdo J
>
>
>
> See below, any thoughts?
>
>
>
> uhd_usrp_probe --args type=octoclock,addr=192.168.100.134
>
> [INFO] [UHD] linux; GNU C++ version 4.8.5 20150623 (Red Hat 4.8.5-39);
> Boost_105300; UHD_3.14.1.1-0-unknown
>
> [INFO] [OCTOCLOCK] Opening an OctoClock device...
>
> [INFO] [OCTOCLOCK] Detecting internal GPSDO...
>
> [INFO] [GPS] No GPSDO found
>
> [WARNING] [OCTOCLOCK] Device reports that it has a GPSDO, but we cannot
> communicate with it.
>
> [INFO] [OCTOCLOCK] Detecting external reference...false
>
> [INFO] [OCTOCLOCK] Detecting switch position...Prefer external
>
> [INFO] [OCTOCLOCK] Device is using internal reference
>
>   _____________________________________________________
>
> /
>
> |       Device: OctoClock Device
>
> |     _____________________________________________________
>
> |    /
>
> |   |       Mboard: OctoClock
>
> |   |   mac-addr: 00:80:2f:24:79:e3
>
> |   |   ip-addr: 192.168.100.134
>
> |   |   gateway: 192.168.100.1
>
> |   |   netmask: 255.255.255.0
>
> |   |   serial: 3183E75
>
> |   |   revision: 4
>
> |   |   FW Version: 3
>
> |   |
>
> |   |   Sensors: ext_ref_detected, gps_detected, using_ref, switch_pos
>
>
>
>
> _______________________________________________
> USRP-users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
_______________________________________________
USRP-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to