John and others.?ÿ Just a quick correction / reply to the above - I saw that this older thread had produced a 'hit' on the SNIP knowledge base support web pages.?ÿ The SNIP NTRIP Caster will re-broadcast anything you send to it. So CMR (and its various flavors) all work as well as RTCM. It operates in a "bent pipe" mode for any data formats its does not understand.?ÿ For RTCM 3.x message SNIP fully decodes and understands the messages.?ÿ So it parses them out to provides some basic monitoring services, an auto setup of the Caster table entry, some plotting, a NEARest connection point, etc etc. In recent releases this is largely automatic, but you can set is as well. Several menu items allow you to look at any suspect data stream when there is a need
Basic to the original thread; many people use a copy of SNIP by the base to take the GNSS serial stream and forward it to another copy (in this case it is acting as an NTRIP Server) where they run the 'real' Caster.?ÿ That is a common configuration.?ÿ Other people are using our free RTK2go.com service to send their connections streams to the public Caster we run there.?ÿ I now see a number of RTK2go users who will setup and connect during a field campaign for several hours when they need arises. That seems to fill a need for folks that do not want a Caster of their own.