{"id":1159,"date":"2016-04-11T14:56:09","date_gmt":"2016-04-11T14:56:09","guid":{"rendered":"\/?post_type=ht_kb&p=1159"},"modified":"2024-03-30T21:53:24","modified_gmt":"2024-03-30T21:53:24","slug":"stream-types","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/stream-types\/","title":{"rendered":"Stream Types."},"content":{"rendered":"

Unlike most Casters, SNIP<\/strong> <\/span>Supports four<\/span> basic types of data streams: PUSH-In<\/strong>, PUSH-Out<\/strong>, RELAY<\/strong>, and UART<\/strong>.\u00a0 These are used to gather and send your different corrections streams<\/strong> to your clients.\u00a0 Two additional data stream types are also supported; a NEARest mountPt<\/strong> functionality and support for older RAW TIP\/IP<\/strong> sockets are also provided\u00a0 Each of these six connection methods is grouped into a tab of its own in the SNIP<\/strong><\/span> GUI design.\u00a0\u00a0 SNIP<\/strong><\/span> also supports more than just RTCM rev3 message<\/a> content.\u00a0 You can send many other types of data (see the article on using SNIP as a bent pipe<\/a>).\u00a0 You can also gather these streams into NEAR<\/a> types.<\/p>\n

\"snipwstreamusers\"<\/a><\/p>\n

These features makes SNIP<\/strong> <\/span>unique and useful for any person who needs to assemble a network of RTCM corrections or other<\/span> data sources for their own purposes.\u00a0 To best use SNIP<\/strong><\/span>, it is important to understand how<\/strong> stream data is gathered into the caster itself.<\/p>\n

Stream Types<\/h3>\n
    \n
  1. PUSH-In<\/strong> Data, The traditional NTRIP flow of data sent to<\/strong> SNIP<\/strong><\/span> by a remote NTRIP Server device, used by large and small network operators.
    \n    See the PUSH-In Streams<\/strong><\/span> tab for further details.<\/a><\/li>\n
  2. PUSH-Out<\/strong> Data, In this model, data is sent by <\/strong>SNIP<\/strong><\/span> to another remote NTRIP Caster device,
    \nso that the Caster can serve your data to others. Combined with services like     RTK2go.com<\/a> this is an easy way to publish your corrections data.
    \n    See the PUSH-Out Streams<\/strong><\/span> tab for further details.<\/a><\/li>\n
  3. RELAY <\/strong>Data, which is NTRIP data gathered from another remote Caster, with SNIP<\/strong><\/span> connected as a Client to that Caster. Used to build up the network you require.
    \n    See the Relay Streams<\/strong><\/span> tab for further details.<\/a><\/li>\n
  4. UART<\/strong> Data, where a local serial or USB port is used to connect to a data sender
    \n(typically a GNSS reference station), and the need for an intermediate NTRIP Server
    \n(the name of the element that sends the data from the GNSS devices) is no longer needed.
    \n    See the Serial Stream<\/strong><\/span> tab for further details.<\/a><\/li>\n
  5. NEARest<\/strong> Data, where a set (or sub set) of the data streams on your SNIP node is used to create a special mountPt where NTRIP Client which provide their location will be automatically connected to the best Base Station.
    \n    See the Nearest<\/strong><\/span> tab for further details.<\/a><\/li>\n
  6. RAW TCP\/IP<\/strong> Data, Slots can be created for an an individual connection to an older GNSS device (one that does not support the NTRIP protocol) allowing them to connect similarly to an PUSH-In data connection.
    \n    See the RAW TCP\/IP<\/strong><\/span> tab for further details.<\/a><\/li>\n<\/ol>\n

    Items #3<\/strong> and #4<\/strong> of these bear additional mention.<\/p>\n

    The RELAY solution<\/em><\/strong>\u00a0 Unlike a more traditional Caster, SNIP<\/strong> <\/span>will reach out and connect to other remote Casters to create (we use the term federate<\/a>) a custom network from these heterogeneous sources.\u00a0 This allows building a network made up of the data streams you wish to use for consistent data logging and management.\u00a0 See the Relay Streams<\/a> tab for details.<\/p>\n

    The UART solution<\/strong><\/em> For many applications, the additional cost of having a GNSS reference station that also implements the NTRIP Server protocol (and therefore sends data to a predefined Caster) is cost prohibitive.\u00a0 Often such devices can also connect and send data with a serial port (also referred to as a UART port or a USB).\u00a0 SNIP<\/strong> <\/span>provides a ready means to connect one or more such devices directly, overcoming the need for a separate NTRIP Server element.\u00a0 See the Serial Streams<\/a> tabs for more details.<\/p>\n

    These different types<\/em> of data streams, along with the need to manage the clients and the status of the caster itself, have led to the tabbed display used in the SNIP<\/strong> <\/span>GUI.\u00a0 The connection details for each type of stream (called a slot) is handled in its own tab of the GUI, where all streams of that type are managed.<\/p>\n

    The licensing model used by SNIP<\/strong><\/span>\u00a0 keeps a running count of all the streams. A flexible licensing is used where each copy of SNIP<\/strong> <\/span>is allowed up to a selected number of simultaneous streams based on the model purchased.\u00a0 Keys for additional streams can be purchased when required.\u00a0 However, the free community Lite<\/strong> <\/em><\/span>model of SNIP<\/strong><\/span> does not allow purchasing such keys.\u00a0 The free community Lite<\/strong> <\/em><\/span>model is also not able to run a NEARest<\/a> style mountPt, use PFAT<\/strong><\/a>, or to accept RAW TCP\/IP<\/a> connections.<\/p>\n

    For an overview of how to filter the console display by stream types, try here<\/a>.<\/p>\n

    For a general overview of SNIP<\/strong>, <\/span>try here<\/a>.<\/p>\n

    Need to use SNIP<\/strong> <\/span>with Older Pre-NTRIP Base Stations…<\/h2>\n

    This is easily done.\u00a0 When using such streams, there is not a NTRIP layer, only a simple TCP\/IP connection.\u00a0 As a consequence you will need to provide a mountPt name for others to use for the stream in the setup process.<\/p>\n

    If the stream will be connecting to your Caster…<\/h3>\n

    Use the Raw Tab<\/strong> for this.\u00a0 See this article<\/a> for more details of how to setup.<\/p>\n

    If your Caster will connect to the Stream….<\/h3>\n

    Use the Remote-Relay Tab<\/strong> for this.\u00a0 SNIP<\/strong><\/span> will connect to the remote host machine expecting a proper NTRIP exchange.\u00a0 The remote host has no idea what that is and will just start sending data back into the open TCP\/IP connection.\u00a0 SNIP<\/strong><\/span> will detect what is occurring and simply deal with it; doing all the various stream establishment and auto-parse functions to set the rest of the needed details.<\/p>\n

     <\/p>\n","protected":false},"excerpt":{"rendered":"

    Unlike most Casters, SNIP Supports four basic types of data streams: PUSH-In, PUSH-Out, RELAY, and UART.\u00a0 These are used to gather and send your different corrections streams to your clients.\u00a0 Two additional data stream types are also supported; a NEARest mountPt functionality and support for older RAW TIP\/IP sockets are […]<\/p>\n","protected":false},"author":13,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"ht-kb-category":[112],"ht-kb-tag":[195,196,203,194,197,202,187],"class_list":["post-1159","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-general","ht_kb_tag-push","ht_kb_tag-relay","ht_kb_tag-remote","ht_kb_tag-slot","ht_kb_tag-stream","ht_kb_tag-stream-types","ht_kb_tag-uart"],"_links":{"self":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/1159","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/comments?post=1159"}],"version-history":[{"count":27,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/1159\/revisions"}],"predecessor-version":[{"id":9016,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/1159\/revisions\/9016"}],"wp:attachment":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/media?parent=1159"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb-category?post=1159"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb-tag?post=1159"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}