Systems Requirements

SNIP is designed to run on a wide range of different PC configurations.  The minimum system requirement to run SNIP are:

Operating System:  Windows 7 SP1 or all later versions of Windows (including all server models) with the newest updates.  Both 32 and 64 bit modes are supported.

Processor:  1GHz or faster processor

Memory:  1GB or more

Hard disk space:  200MB or more on a partition, much more if you will be data logging

Internet Connection:  Ability to originate both http and https  (SSL) connections

As a general rule, a desktop class machine can support several dozen data streams at once and hundreds of users before noticeable processor load occurs.  For bandwidth estimates, each NTRIP client will need about ~300 bytes per second.

KEY:
Your firewall must also allow others to connect to SNIP on the port you have selected (typically 2101), and your user community must be able to find your through a host address (either an IP address or a host name and DNS).

While a static IP is not required, it is useful if your users are beyond your local internet network.  You can also use one of the many dynamic DNS (DDNS) services like opendns,  DynUp, or EasyDNS for this.  If you need a fixed static IP but do not have one, consider using our RTK2go.com caster service.

All versions of SNIP use a secure socket layer (SSL or https) to provide Base Map services, validate product licenses, and to connect to various 3rd party services.   SNIP uses the FTP protocol (on various ports) to transfer your data log files to the remote storage location (NAS or other format) which you have selected.

The Enterprise versions of SNIP use a build-in SMTP email service (on various ports) to to send outbound email to your registered NTRIP Clients and to the operator.  This may be relayed to your corporate server or to SCSC operated mail servers depending on the your configuration setup.

 


 

Ubuntu

Running SNIP on a Ubuntu machine has the same requirements.  There is not a noticeable change in platform performance between Windows and Ubuntu in this regard. Some users prefer to use Kubuntu but we are unable to support all the various GUI flavors that exist.  Because SNIP is built using Qt, the GUI will largely adapt to the user preference settings when possible.  By design, SNIP is a GUI intensive tool, it is not a command line application.

Use on Window XP

While not officially supported, some users operate SNIP on older Windows XP nodes as well.  With release 1.12 and Rev 2.x onward, this is no longer possible.  The underlying DLLs no longer will run on this older system and require Win7 or better.  If you have an XP node you are using as an NTRIP Server to feed another SNIP node, this page may be of value to you.

Use on maxOs and/or with WINE

While not officially supported, some users operate SNIP on WINE.  The most common issues reported are that the font families used by SNIP (various common true type fonts) are not found in the WINE environment, producing charts and images with no labels.  Various level in emulation in the serial port process may cause unneeded latency in corrections data, but this remains unproven.

Running as a Service

By default SNIP runs as a process with access to the windowing GUI system (interact with the desktop in Microsoft terminology).  You can also set SNIP to run as a service, but it must be granted access to the windowing GUI system.  Some users prefer this mode for unattended 24/7 operation.

Was this article helpful?

Related Articles

Leave A Comment?

You must be logged in to post a comment.