What is new in the Alpha 0_8_8 release    [May 16, 2016]

• SNIP underwent an extensive rework of the console logging functions in this release. More robust filtering abilities  have been added to allow a finer control of what information is displayed. At the same time, an array of prior log entries allows using these filters to redisplay the log in various ways to show or hide types of data on command. In a SNIP NTRIP Caster with dozens of active connections and many clients, these new abilities are useful to filter the displayed console information to only the context of current interest.  Using the filters is covered further in this knowledge base article.

• The SNIP filter controls can be accessed from two areas in the program:  the menu system or the pop-up controls located just above the console log area.  Both provide the same menus and functionality.
• The types of information filters include displaying or suppressing the various types of streams (remote, UART, and pushed), the progress of NTRIP Client connections, and various system level messages. This is described further in a KB article.
• Besides the basic stream types, Information about each individual data stream (mount point) that your caster provides can be filtered on or off to allow focusing visual attention only on the streams of interest. This is described further in a KB article.  The image above shows a list of streams active on that Caster.
• A general Log Threshold filter level provides the primary means to control overall verbosity by selecting more or fewer details about the displayed events, and is described further in this KB article.
• The Filter Log check box provides a means to quickly enable or disable a complex filter setup, while a Reset All menu item allows easily reverting to a more normal display state.

• SNIP now has a simple wizard to assist in setting up new Relayed Stream connections. This provides a focused multiple step process to enter all the required connection details, rather than the more complex Add New Caster Stream dialog which advanced users may prefer.

The wizard uses the same underlying technology found in other parts of SNIP to assist the user by populating fields including user account name, password, and port numbers based on the user’s prior connections to each host.  At this time, a similar wizard tool is also being developed for use with the serial stream connections tab.  A step by step KB article can be found here.

Other improvements in this release include:

• Adding a test button to allow the user to quickly confirm that the user’s remote FTP setting allows actual connection to the remote host (Located in the FTP Dialog which is part of the Log Setting Dialog under the Data File Setting menu item).
• Logic was added to ensure that the minor “Hint” console entries are not repeated to reduce overall console log clutter. This, along with the recent filter logic described above, allows a much cleaner log display.
• Further changes to SNIP‘s core server code were made to resolve naming conflicts and accommodate using RTKLIB libraries as a navigation quality checking tool when in Unix builds.
• Initial Linux installation scripts for SNIP  have been built and are undergoing testing. The diversity of possible folder locations for installing over different builds remains the primary problem to overcome at this point.
• Further logic changes to support the one hour time limit for the evaluation of SNIP in pro and basic modes were made. The Server and stream shutdown process is now cleaner and some explanatory notes are presented to the user urging them to register SNIP.
• A button has been added to allow forcing an immediate reconnect for any caster stream that had timed out and is awaiting a reconnect. This has value when a remote caster has gone offline for a considerable period of time and the user wants to reconnect to it immediately rather than waiting for the next timed interval.
• In release 0.8.6 the allowed port number for remote connections was limited to the range 0~10000, this limit was removed, as some casters use higher port numbers.  As an example, the Michigan State network uses values starting at 10001 and above, while Alabama starts some of their network at 15000 and above.
• The log entries can now be displayed in a variety of tagged and nontagged formats to quickly see what slot or stream caused an entry. A menu item under Display By Types allows selecting this.
• The web site Knowledge Base (KB) for SNIP has continued to grow with more new articles since the last alpha release in mid-April.
• We expect to move to a Beta release level at the end of May.  At that time we will open the door for wider testing to the general public and allow purchasing of SNIP to begin. To our valued Alpha testers, please continue to provide us with your feedback.

The Next Release

New to SNIP ?  Take a quick tour.

SNIP is an NTRIP Caster, if you are seeking for an NTRIP Client, try the products mentioned here or here.