What is new in the SNIP 2_05_01 release – released October 9th
(updating the release of 2_05_00 on October 3rd 2018, due to an error found in the NEAR stream logic)
This is the next release of SNIP following the Rev 2_04_00 release of August 29th. This release contains a number of refinements to different areas of SNIP in response to user requests. Further refinements of the Caster table to support various older models of Rover is perhaps the most notable improvement in this release.
This release supports for both 32-bit and 64-bit installations in Windows. It is recommended that all Windows 32/64 SNIP installations now update to using this release. The 64-bit Ubuntu release with identical features remains pending at this time.
Notable changes in the release include
Changes were made to several key areas of SNIP including
Rev 01 Update
An error was found in the _00 release which necessitated the current _01 release. If was found that NTRIP Clients (Rovers) could not connect to NEAR streams due to an internal indexing issue. MountPt names (an alias name when a mountPt was given a new name) are now correctly indexed.
Minor improvements present in this release also include
- When testing for L2 observable data content, MSM messages are now tested (not just older 1003/1004 and 1011/12) for all GNSS types.
- Streams that are not parsed (typically non RTCM3 message content) are now visually indicated with a background pattern.
- All serial streams are parsed upon startup, returning to any default settings if RTCM3 contents is not found.
NTRIP Rev2 NTRIP Client Improvements
- Improved support for NTRIP Rev2 Caster connections added for Basic and Pro models. This includes support for the $GNGGA NMEA string which some of the newest devices use (although its use is not part of the adopted standard at this time).
- Support for returning NTRIP Rev2 Caster Tables formats when requested (or Basic and Pro models). While backwards compatibility is defined by the NTRIP standard, some devices either require the Rev style or make the end user jump over additional obstacles to work with Rev1 tables. Hence SNIP now returns table in either format when asked.
Other Changes of Note
- Streaming data from a mountPt now continues during the Analysis phase (in bent pipe mode), thereby not depriving current subscribers of data. Some operators like to toggle the parse switch during operations, and change was made in order to not impact connected users.
- A change was made to the weekly charting tools to allow optionally merging a mountPt across multiple connection IPs. Some user Base Station devices are not simply able to main a stable connection using local cellular links and often reconnect with different IPs. The option allows the sequence of connection to be displayed as one, along with the drop outs.
- A change was made to correct an sign error the GEOID correction model used in NMEA sentences.
- A modification was made to the re-connection logic during slow reconnect periods to ensure that a progressive backup rates was always used.
- The display of the Caster Table entry for a given mountPt (a right-click menu item) now shows more clearly when the source entry has been modified for use in the Caster Table (for example when the send NMEA flag has been asserted).
- Several minor typographical errors were corrected.
- A server service to send rover AVL data to remote devices for display has been implemented is no now in limited testing. The existing map display can also be used within SNIP for this ability as well.
Like all Rev 2.x releases on the Windows platform, one-click and painless ! The built-in installer will inform you when a new release is issued. You can also check on this manually at any time.
When you upgrade (there is no reason not to) the installer will download the new image and install itself, leaving all of your current settings in place. The SNIP node is taken offline for about 90 seconds before service can then resume.
Please tell us how you use SNIP and how we can make it better. Feel free to use the free text areas in the survey below to tell us anything else you think we should know.
New to SNIP? Take a quick tour.
SNIP is an NTRIP Caster. You can also use SNIP as an NTRIP Server with your existing GNSS devices. Many deployments use a single paid copy of SNIP (Basic or Pro) in conjuration with multiple copies of SNIP Lite to set up their entire network. This configuration is very cost effective when the GNSS device vendor charges for providing an NTRIP Server option.
You can always obtain the most current release of SNIP here.