What is new in the SNIP 1_2_0 release [January 13th 2017]
This is another minor service release of SNIP following after the rev 1_1_0 release of last month (December 2nd). It is recommended for all users and is now the primary download. At this writing, SNIP is now being used in over one hundred countries to operate NTRIP Caster networks.
The primary improvements made from release 1_1_0 are as follows:
- When a SNIP operator used the Remote-Relay method to connect to a simple TCP/IP data stream (which does not support the NTRIP protocol), the resulting final Caster Table Entry was less than ideal. In the Parse mode was enabled, then SNIP would do an analysis of the data stream and correctly fill out the caster table entries message content detail automatically. But it left the message format as “RAW” (rather than RTCM). That can be a problem for several brands of rover NTRIP Client that expected to see the term RTCM. In this release of SNIP the format entry is also corrected to be RTCM. Connecting a simple TCP/IP data stream into SNIP is a common event for some SNIP operators who have reference stations which do not offer an NTRIP Server functionality.
- A new tab labeled “nearest” and various associated logic has been added to SNIP in anticipation of a major new feature (see below). This new tab, and some controls, are visible in this release, however the new functionality remains disabled at this time.
- A number of changes were made to how the map display works. The most noticeable of these is that SNIP can now display the location of any NTRIP Clients that periodically send NEMA-183 $GGA sentences. This provides a fast and simple way to view your currently connected user population.
- When reporting connected users in the console (see the Caster and Clients tab), SNIP now also provides the most current (last) $GGA sentence from each user, a running count of how many such sentences have been sent, and it also now displays the resulting Lat-Long in a more readable decimal DD.ddd format. The current baseline distance to each users mountPt is also displayed.
- A new ability to perform slow periodic logging of connected users into the weekly log has been added. This allows reporting where user account connected from over a historical basis similar to the way weekly caster connections can be logged as a future feature.
- Minor corrections were made to the way time was displayed in the console when more than a 24 hour period had elapsed. A calculation error was also corrected.
- Adjustment were made in how rapid client disconnect-reconnect logic handled such disconnect events when the connection was “lost” and never closed. There have been reports of both new and “old” client connections persisting for a few seconds when an active connection was “lost” (rather then disconnecting).
- Changes to the way the weekly PUSH-In connections were logged and displayed in the Log Viewer were made to associate the same individual data stream in on summary entry across repeated connections when only the port number used changed.
The past month’s development effort to deploy a NEARest function in SNIP has started in-house testing at this time and will be released in another two weeks for more general testing and use. This has been the primary focus of development efforts during the past month, but we did not want to delay the above useful changes being released to those who needed them.
The set of categories used in the Knowledge Base part of the site were resorted to better support user needs.
New to SNIP? Take a quick tour.
You can always obtain the most current release of SNIP here.