Prefer to have your mountPt string and settings reserved? The reservation feature of SNIP allows this.
Drop us a note at our support email, support [at] use-snip.com and we can set that up for you in RTK2go. We need to know the following information from you:
We will send you a reply (typically within 24 hours) with a unique password for your use.
When your reservation is activated, no one will be allowed to log on to it except with the unique password and with the IP selected above (if selected).
Aside: Until the reservation is activated you can send in the same data without a reservation like everyone else. So if it was working a short time ago and just stopped, it’s a clear sign your reservation was just activated. Use the assigned password from that point onward.
If you can spare a moment more, a short note about how you are using RTK2go is always appreciated.
There is no cost for this service. We are now running the RTK2go Caster to default any PUSH-In new connection as “unparsed” in order to support our CMR/CMR+ user community. But a reservation with parsing enabled is also the best way to send SNIP RTCM 3 messages and have it parse over them and set up the Caster Table Entry automatically for you.
NOTE: A note to “emlid” or “Reach” users: Please consider getting a reservation set up with us. If you are sending RTCM3 data to this node, and if creating the Caster Table entry is too complex, then let SNIP automatically do it for us. As per the above, drop us a short email and get a reservation for the mountPt name you want.
NOTE: A note to RTKLIB users: Please consider getting a reservation setup with us. You can then leave the Caster string detail blank in any other RTKLIB tools (e.g. RTKNAVI or STRSVR) and SNIP will automatically complete the correct entry for you, if parsing is enabled. As per the above, drop us a short email and get a reservation for the mountPt name you want.