Often a end user needs to confirm that a Caster is up and operational, or that a given stream is present when the connection to it fails. This page describes several simple ways to get the real-time status of any NTRIP Caster.
The SNIP node on this site and the RTK2go web site (this page) are hosted on the same machine(s).
To determine if SNIP is up and operational, simply request the Caster table on the correct port with your browser tool (as in: http:// rtk2go.com:2101 ).
If you get a Caster table returned, then that copy of SNIP is on line.
On Casters designed by others, if you get a “invalid response” note and you are using Chrome, it most likely means that the Caster sent back a table according to the NTRIP protocol rules and Chrome is being picky. SNIP has an option to detect browsers requesting access and return well-formed html that overcomes this issue.
Hint: This method can be used for most NTRIP Casters anywhere in the world where a DNS name or a public IP has been used.
Or you can use one of our NTRIP monitoring services at: monitor.use-snip.com to test any Caster anywhere in the world and have the returned table decoded for easier human reading. This service is hosted on machines that span several dozen IP address sites so it very unlikely to ever be down. The returned Caster table is displayed in a more readable format, and any location data for Caster Table entries can be plotted and displayed with a simple map.
Or you can use the SNIP interactive protocol system on this node (or any other SNIP node where the operators has enabled it) to see basic operational status return to you as a web page. This is a paid feature unique to SNIP NTRIP Casters, and requires that the SNIP Caster operator decider to allow other parties access to selected system status and commands (because this additional information represent a security risk).
simple NTRIP + Interactive Protocol = SNIP®
If the device making the connection is also a SNIP machine, further explanatory messages are exchanged when a connection fails. This allows displaying useful details to inform the remote user what has occurred. The interactive protocol system is being developed for SNIP release 2.x but a basic status command is present on this node. Try this in your browser:
Or you are away from a PC, use your phone or tablet. Download a copy of this NTRIP Client and simply use that (along with the grossly inaccurate GNSS chip in you phone). You can still connect to the remote stream and see data moving across in this way, and you can obtain a current Caster table and check your spelling, Very handy when out in the field. Be sure your selected Caster allows multiple connection from the same user account at the same time, SNIP does. It is always interesting to come back to the office and see the Andriod phone track wandering around the precise RTK track in SNIP‘s map display view.
The RTK2go Caster may be periodically taken off-line for various of maintenance operations. This normally requires under 3 minutes to change out software and restart. On restart your PUSH-In stream connection (NTRIP Server) will be accepted again. Well behaved NTRIP Servers typically restart in under 15 seconds. On restart, NEAR streams require an additional 3 minutes to become fully operational.
Typically this this scheduled to occur just after UTC midnight.
The evolving web: Please Note that the latest release of Chrome (mid year 2017) will now claim that any returned text page from a “pure” NTRIP Caster table is a “invalid response” and the Caster Table is then not shown to the user.
Aside: SNIP has a setting to return web friendly Caster Table as pages, which we enable on this site. So when a device that is not a valid NTRIP Client tries to connect, SNIP returns well formatted html.