I agree, @sparky.
In fact, I considered it more reliable than rtk2go, but it’s given me headaches in the last 15 days.
@Matthew_Kruse - Below is what I see when connecting to our mountpoint on Emlid’s caster:
NTRIP server 0: NTRIP_SERVER_WAIT_GNSS_DATA → NTRIP_SERVER_CONNECTING
Batt (39%): Voltage: 3.82V Charging: 18.30%/hr Yellow
Batt (39%): Voltage: 3.90V Charging: 13.73%/hr Yellow
NTRIP Server 0 connecting to caster.emlid.com:2101
NTRIP Server 0 sending authorization credentials
NTRIP server 0: NTRIP_SERVER_CONNECTING → NTRIP_SERVER_AUTHORIZATION
Server 0 Response: ICY 200 OKNTRIP Server 0 connected to caster.emlid.com:2101 MP1979a
NTRIP server 0: NTRIP_SERVER_AUTHORIZATION → NTRIP_SERVER_CASTING
Batt (39%): Voltage: 3.90V Charging: 13.73%/hr Yellow
NTRIP Server 0 transmitted 524 RTCM bytes to Caster
NTRIP Server 0 transmitted 524 RTCM bytes to Caster
NTRIP Server 0 transmitted 534 RTCM bytes to Caster
NTRIP Server 0 transmitted 524 RTCM bytes to Caster
Note the server response ICY 200 OK after NTRIP Server 0 sending authorization credentials
In your output:
NTRIP Server 0 sending authorization credentials
NTRIP server 0: NTRIP_SERVER_CONNECTING → NTRIP_SERVER_AUTHORIZATION
ntripServerStop server 0 start requested
Which indicates a server response timeout. The Emlid caster is not responding to your request for some reason.
Just got back in the office and it is working now. I will work on getting rtk2go set up in the event emlid goes down again. I feel like I have a better understanding of how to diagnose now if it drops again.