How not to succeed, RTKLIB

This article is motivated by an increasing number of users, often with RTKLIB based tools, who are unable to connect their Base Station data to SNIP.  And as a consequence, are unable to connect their Rover device(s) as well. A common ‘bad’ setup Consider the following two log entries taken […]

Release 2_02_00 Changes

What is new in the SNIP 2_02_00 release  [released April 24th 2018] This is the next release of SNIP following the Rev 2_01_00 release of March 30th.  It is a routine service release. It contains a number of improvements stemming from user feedback on the 2_01 release.  This release supports […]

Blank Screens with Maps

Problems with Blank screens when displaying maps We have had recent reports (March and April of 2018) of a blank screen being displayed when a Google base map is used in SNIP.  These issues seem to be limited to those who are running SNIP in a remote virtual Windows machine […]

Release 2_01_00 Changes

What is new in the SNIP 2_01_00 release  [released March 30th 2018] This is the next release of SNIP following the Rev 2_00_00 release of March 13th.  It is a routine service release. It contains a number of improvements stemming from user feedback on the 2_00 release.  This release supports […]

PFAT: Main Dialog

The the P.F.A.T.™ control system provides several innovative ways to control the messages present in every data stream.  The PFAT features are available in the Pro, Basic, editions of SNIP.  Lite copies of SNIP share the same code base, but many of these innovative features are disabled in the freely […]

Release 2_00_00 Changes

What is new in the SNIP 2_00_00 release  [released March 13th 2018] This is the next release of SNIP following the Rev 1_12_1 release of January 5th and including various pre-release Beta copies used as the run up for this formal 2.xx release.  This release supports for both 32-bit and […]

Removing GLONASS Message Content

This article shows how to set the the PFAT controls to remove classical GLONASS RTCM 3.x messages (message types 1009~1012) from a stream, leaving only the GPS types. This action is often desired to create a new (smaller) stream without GLONASS message payloads for end users who do not need […]

PFAT: Use with Lite models of SNIP

The PFAT feature provides a number of proprietary methods to control the Base Station Data stream content sent to your end users (NTRIP Clients).  Using PFAT, a single data stream can be replicated in several ways, with different message contents and a different frame of reference.   SNIP is the only […]

PFAT: Adjusting the Datum for a Network

In this article we review the process to align the reported Base Station ECEF locations for a network of six stations to all use a common IGS08 frame of reference.   This is commonly necessary when the stations are managed by other parties who have selected another datum for use. The […]

PFAT: Translate Settings and Uses

The P.F.A.T.™ control system provides several innovative ways to control the messages present in every data stream.  The PFAT features are available in the Pro, and Basic, editions of SNIP. Lite copies of SNIP share the same code base, but many of these innovative features are disabled in the freely […]

How to Remove a Stream

Just right click on the stream, then select Disconnect or Remove. New users have asked how to remove a Base Station data stream.  When an Evaluation copy of SNIP is registered as Lite, the number of allowed streams (slots) is reduced to three, often bringing this issue to the forefront. […]

PFAT, Used to create multiple streams

The most common use of the PFAT™ ability is to modify the source NTRIP Caster data stream from a single Base Station for use, and place the resulting stream out on the SNIP Caster. A typical PFAT use A typical example of that is shown below where the PFAT setting […]

PFAT: Add Settings and Uses

The the P.F.A.T.™ control system provides several innovative ways to control the messages present in every data stream.  The PFAT features are available in the Pro, Basic, editions of SNIP.  Lite copies of SNIP share the same code base, but many of these innovative features are disabled in the freely […]

Installing SNIP on non-English platforms

Installing SNIP on non-English platforms At this time SNIP is shipped with only English language textual strings (there are no translations).  SNIP will make use of various local conventions for numbers, times, and currency – but all message textual content is in US English.  SNIP can be run with whatever […]

Editing PUSH-In Reservations when live

It is fairly common to edit or to create a PUSH-In reservation when the end user of the reservation (the remote NTRIP Server) is either connected or trying to connect to your SNIP node at the same time.   Both parties cannot edit the same data at the same time, and […]

Release 1_12_0 Changes

What is new in the SNIP 1_12_0 release  [released December 21st 2017] Includes the SNIP 1_12_1 release  with full support for 32 /64 bit restored  [released January 5th 2018] This is the next release of SNIP following the Rev 1_10_0 release on July 12th. This is the final release of […]

SNIP Beta 1_11_9 completed

Update The 1.11.9 Beta release code has been passed for production, and will be released as 1.12 on December 21, 2018.  This page is kept only for historical needs.  The most current download of SNIP contains all of these feature improvements.   You can read about key 1.12 features here (link […]

Mixed data types with uBlox

Many people use RTKLIB and its STRSVR program to convert uBlox into RTCM 3.x message types before sending them to SNIP for distribution. This data can then be used by any devices that consumes RTCM 3.x data, although it contains only L1 observations. Others prefer to send the raw uBlox […]

Orbit and Clock corrections feeds

The number of SNIP users, both SNIP Caster operators, and those connecting to SNIP nodes with NTRIP Clients, have been asking about orbital and clock corrections (the so called ‘State Space Representation’ (SSR) messages found in RTCM 3.3 messages and beyond).  SNIP handles every defined and adopted SSR message, as […]