[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ntrip and sending position

From: Gary E. Miller
Subject: Re: ntrip and sending position
Date: Mon, 16 Dec 2019 13:29:06 -0800

Yo Greg!

On Mon, 16 Dec 2019 16:14:08 -0500
Greg Troxel <address@hidden> wrote:

> I recently tried to use the ntrip support, and have a few questions.
> 1) The man page says: to use a form like:
>   ntrip://foo:address@hidden:80/example-stream

Yup.  I have a NTRIP feed to one a NEO-M8T that I run almost all the
time that way.  From Oregon Real-time GNSS Network (ORGN).

> and I wonder what happens if one's username foo is an email address.

That URL is just used verbatim.  So whatever your NTRIP server wants is
what you put there.

> 2) I am using a service provided by the Massachusetts Department of
> Transportation called MaCORS.  It has a "Virtual Reference Station"
> feature where it synthesiszes corrections for your location based on
> multiple reference stations, and it can also pick the closest,
> depending on the ntrip mountpoint.  See
> if you are interested; it's available to the public, but only covers
> MA.

A bit too far from oregon to be useful to me.  Hopefully others from MA
give it a try.

> The man page doesn't address sending position.  The Emlid Reach RTK
> has options to 1) not send 2) send a static lat/lon and 3) send the
> current position solution.

For ORGN, that just goes in the URL.  So ask MaCORS what to use as your URL.

> 3) I wonder how to monitor the ntrip stream.

gpspipe.  The NTRIP will show up as another "DEVICE".

Here is what mine looks like, note the 2nd device:

# gpspipe -w pi8
 EXT CORE 3.01 (111141),HW 00080000","subtype1":",ROM BASE 2.01 
(75331),FWVER=TIM 1.10,PROTVER=22.00,MOD=NEO-M8T-0,FIS=0xEF4015 

> I am sure it has carrier
> phase, as people talk about RTK with it.  I think it also has
> pseudorange corrections.

RTK is like NMEA 0183.  It defines a few standard sentence types, then
vendors (Leica, u-blox, etc.) add their own proprietary sentences.

Here is what mine looks like, note the 2nd device:

# gpspipe -w pi8

The type 1 is the corrections.  The type 18 is not decoded.

> While I realize the primary path should be
> the MaCORS docs, it seems the gpsd way would have some sort of
> monitor.

For now, just gpspipe, which can give you the raw and/or JSON of the data.

Patches welcome!  If you figure it out, a howto would be nice.

Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        address@hidden  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin

Attachment: pgpDKWGV74Riu.pgp
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]