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, two or more cores.
Memory: 1GB or more, 4+GB preferred
Display: Able to run basic OpenGL graphics (both HW and SW GPU modes supported)
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 many dozens of data streams at once and hundreds of users before noticeable processor load occurs. For bandwidth estimates, each connected NTRIP client will need about ~300 bytes per second.
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, DDNS.net, DynUp, or EasyDNS for this. If you need a fixed static IP but do not have one, consider using our RTK2go.com caster service. SNIP also supports port mapping and forwarding setups within your firewall.
All versions of SNIP use a secure socket layer (TSL/SSL also called https) to provide Base Map services, validate product licenses, and to connect to various 3rd party services. SNIP also uses the FTP protocol (on various outbound 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 the SCSC operated mail servers depending on the your configuration setup.
VM Use of SNIP
SNIP runs well on suitably configured VM machines, both locally based and cloud based. Two cautionary notes on “small” virtual windows machines running on the cloud must be given.
- Some deployments have tried to install SNIP on very low cost machines running in time-sliced modes with required periodic sleep periods. Because the NTRIP connections are intended to be provided in real time with a low latency for message delivery this is not advised.
- Some of these smaller machines also do no have suitable graphics display abilities and therefore cannot display document reports or maps. In such cases the display window is not able to create OpenGL calls and the content shows as blank. While SNIP runs on such machines, the lack of reports is a major hindrance and this is not advised. This knowledge base note on remotely connecting to the machine running SNIP may also be of value.
At the least a 2-core machine is highly recommended. SNIP places the GUI update tasks in a separate core when possible, to allow faster services of data into and out of the Caster.
When in doubt regarding a given configuration; simply try it and see. If the evaluation copy of SNIP runs on the machine you intend to use, all production copies (Lite, Basic, Pro, and Enterprise) will also run on that machine.
Most VM solutions offering a Windows OS provide only Windows Servers OS choices. Any of these will serve as well as using Window 7 when available. The core “server” parts of SNIP are built in and do not depend on the operating system used. A SQL solution on the VM is not required.
Running SNIP on a Ubuntu machine has the same requirements. There is not any 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. At this time SNIP is not longer being offered for Ubuntu machines.
Use on Window XP
While never 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. This mode of operation also requires that suitable true type fonts be installed and available.
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 also be granted access to the windowing GUI system. Some users prefer this mode for unattended 24/7 operation.