RS232 over the Internet

Connecting a GNSS serial port over the Internet to a remote SNIP NTRIP Caster is easily achieved using one of the many serial to internet adopter dongles available.  In this article we describe the setup process using the popular USR-TCP232-302 product made by Jinan USR IOT Technology and available from […]

Considerations for Creating NEAR Streams

This article covers some key considerations when creating Single Baseline NEAR streams with the SNIP NTRIP Caster.  A NEAR stream is a type of of RTK Network data stream where each end user (the rovers or NTRIP Clients) connects to a single mountPt (often with the word NEAR in its […]

Release 2_12_00 Changes

What is new in the SNIP 2_12_00 release – released November 22nd 2019 (updating the prior release of 2_11_00 of September 10th 2019): This is the next production release of SNIP following the Rev 2_11 release.  This release contains many new features as well as several minor SNIP corrections and […]

NEAR settings, Using Base Station Lists

When creating a NEAR stream, the SNIP operator can create a specific list of which Base Stations are to be considered for a given NEAR stream.  This article describes how to set up a list of possible Base Stations to be used in the stream.  The Base Stations on the […]

Using SNIP as a “bent pipe”

SNIP can be used in a “bent pipe” mode for any desired stream.  In this mode, any data sent to it is available to be relayed to any client connection (as well as being logged).  This mode of operation is commonly used where the Base Station data is not industry […]

PFAT: Legacy to MSM messages

The Legacy to MSM translation is used to translate older Legacy messages to newer MSM style message types (msm = multiple signals messages).  This has value to network operators with an installed base of older Base Station GNSS devices which cannot produce MSM messages directly.  Caster streams can be developed […]

PFAT: MSM to Legacy messages

The MSM to Legacy translation is used to translate newer MSM style messages (msm = multiple signals messages) to old Legacy style messages.  This has value to network operators whose rover communities (NTRIP Clients) contain older devices that cannot process the newer MSM message types.  Caster streams can be developed […]

PFAT: Removing L2 content in Legacy messages

The Remove all L2 Observation Content  translation is used remove L2 content from Legacy RTCM3 message types 1003~1004 (GPS) and 1011~1012 (GLONASS) to produce (smaller) 1002 and 1010 messages.   This has value to network operators whose rover communities (NTRIP Clients) are made up of L1-only devices by allowing them to […]

PFAT: Last Observation Flag

The Last Observation Flag translation is used to adjust the flags present in the RTCM3 messages which are used to indicate (to the rover devices) that the last set of observations at a given common time has been sent.  By convention, GPS observations are always sent first, followed by GLO […]

Release 2_11_00 Changes

What is new in the SNIP 2_11_00 release – released September 10th 2019 (updating the prior release of 2_10_00 of August 6th 2019): This is the next production release of SNIP following the Rev 2_10 release.  This release contains new features as well as several minor SNIP corrections and improvements […]

NTRIP Rev2 uses in SNIP

SNIP fully supports both NTRIP Rev1 and NTRIP Rev2 connection styles.  SNIP also provides an auto-fallback for connecting NTRIP Clients that need to use one or the other format.  From release 2_11_00 onward, SNIP allows you to select how it connects to other NTRIP Casters using either the Rev1 or […]

Misc. Caster Stream Reports

This article provides a quick review of several Stream Reports that the SNIP NTRIP Caster provides and their general usage. These are all invoked by using the Reports menu, and the All Streams sub-menu.  And each item displays its report in the document viewer window. The content and presentation varies […]

Pre Release SNIP editions, 2.x

You have found the SNIP 2.x BETA Release Channel  See also: release notes for 2_00_00,   2_01_00,   2_02_00,   2_03_00,   2.04_00,   2.05_00, 2.06_00,    2.07_00,   2.08_00 ,   2.09_00,   2.10_00,    2.11_00  and  2.12_00 Some of our licensed users have asked for the development team to post the […]

Reserving a Pushed-In Mountpoint

The pushed-in reservation list allows a SNIP operator to reserve a mountpoint name for future PUSH-In connections from specific devices which they wish to allow.  Once set up, only an NTRIP Server with the correct password and IP address combination will be able to PUSH-In with the preconfigured mount point […]

Release 2_10_00 Changes

What is new in the SNIP 2_10_00 release – released on August 6th 2019 (updating the prior release of 2_09_00 released on June 12th 2019) This is the next production release of SNIP following the Rev 2_09 release.  This release contains a few new features as well as the normal […]

IP and Port Forwarding

Often a SNIP NTRIP Caster is run on a machine which does not have a static IP address assigned to it.  In this article three ways to set the link address used in various reports created by SNIP are reviewed.   If your copy of SNIP operates behind a firewall, or […]

Release 2_09_00 Changes

What is new in the SNIP 2_09_00 release – released June 12th 2019 (updating the prior release of 2_08_00 of April 4th 2019) This is the next production release of SNIP following the Rev 2_08 release.  This release contains new features as well as several minor SNIP corrections and improvements […]

The AVL Server

The AVL Server controls are located in the AVL Tab and provide the means to control the server functions, including various access methods and the formats used to send data to subscribed clients.  The use of these controls is discussed further in this article. The AVL Server is independent of […]

The AVL tab

The Automatic Vehicle Location (AVL) tab is used to quickly see the last few NMEA $GGA reported locations for all connected NTRIP Client devices.  The tab also controls the AVL server which is used to send these locations to other connected machines (see Note A).   The AVL server provides a […]