Caster Management (located under the Caster and Clients tab on the right side) is used to control the internet IP address at which your SNIP Caster will provide services.
Setting the values involves only a few steps:
- Enter the Caster IP to use.
- Enter the Port number to use
(2101 is the default for NTRIP)
And then press the Connect button. The label will toggle between Connect and Disconnect based on the current Caster state. The data entry controls are greyed out when the Caster is connected.
If you wish to have the process automatically repeated each time SNIP starts, check the Auto Start box. SNIP will save this and many other settings, restoring your settings when the application next runs.
You can also see a quick list of all the current mount points which SNIP is serving by pressing the List MountPts button.
You enter the IP you with to use. When SNIP starts it will list the current IP addresses which it finds, choose of one these, preferably an IP which you user community can access. This need not be static if you are operating in a smaller closed network. If you wish other parties on the internet to access your SNIP node, you will need either a static IP or can use one the many dynamic DNS solutions to publish your dynamic IP assignment to others.
If you are behind a firewall you may have to employ a method of port forwarding to expose the SNIP port to others.
The Disconnect button enables / disables the Caster. When disabled no clients can connect and receive data.
The Auto Start check box is used to control if SNIP will automatically startup in an active mode, it is usually checked.
The Table button sends the current Caster Table to the console for viewing.
The MountPt button provides a summary to the console for every mountPt and data stream type you have created.
Some people prefer to use another SNIP node located at a static public IP, and use a copy of SNIP to PUSH-Out data to it for public use. It is fairly common for a network to run multiple copies of SNIP, using multiple free Lite copies to send data from remote GNSS sites to a “main” SNIP node with a suitably sized license.
Other deployments use our free RTK2go.com service to publish their data to others.