{"id":9070,"date":"2024-04-27T00:29:00","date_gmt":"2024-04-27T00:29:00","guid":{"rendered":"https:\/\/www.use-snip.com\/kb\/?post_type=ht_kb&p=9070"},"modified":"2024-07-19T15:33:50","modified_gmt":"2024-07-19T15:33:50","slug":"trimble-base-station-connections","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/trimble-base-station-connections\/","title":{"rendered":"Trimble Base Station Connections"},"content":{"rendered":"

Theis article provides step-by-step<\/em> instructions to connect any modern Trimble base station to an SNIP<\/strong><\/span> NTRIP Caster such as RTK2go.com<\/a>.\u00a0 While this article used a Trimble Net R9 GNSS device and was written to support RTK2go.com users with Push-In reservations<\/a>, the general information and process is applicable to many other Trimble models, and any NTRIP Caster.<\/p>\n

Logging In <\/strong><\/h2>\n

Below is the initial log in screen you will see for the GNSS base station. \u00a0You need to have an account on the GNSS device itself to do this and must be able to reach it\u2019s IP from the browser that you use.<\/p>\n

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

After a successful log in the page will briefly say \u201cOK\u201d and then move to a page that summarizes the current satellite (often called SV, for space vehicle) tracking activity on the GNSS unit<\/p>\n

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

Aside:<\/strong><\/span> If this device already had an active NTRIP connection to a Caster, you would also see a line (typically with the text: \u201cOutput : IBSS\/NTRIP Server – RTCM_V3\u201d) present in the Input\/Output: section above.<\/p>\n

We are interested in setting up an \u201cNTRIP Server<\/a>\u201d connection, which Trimble has placed under the \u201cI\/O Configuration<\/strong>\u201d tab along the left side.\u00a0 Press that and you will be taken to another page similar to the below<\/p>\n

\"\"<\/a>The device supports up to 19 different output streams in various common formats. Each has its own setup page with appropriate options.\u00a0 Most of the streams allow selecting one of several standardized output formats (this is where you will tell it to send RTCM messages).\u00a0 On this page the color red<\/strong> <\/span>means \u201coff<\/strong>\u201d (or no-used if you prefer), green<\/strong> <\/span>means a stream is on<\/strong> and active<\/strong>, and\u00a0 yellow<\/strong> <\/span>means some problem has occurred or the stream is in a transitory condition (such as retrying).<\/p>\n

In the image above you can see that port 5017 is setup to send RT27 (a Trimble proprietary message format) over TCP\/IP but the stream is not active at this time (indicated by red).\u00a0 The other choices are all off as well.<\/p>\n

We are interested in the three lines called \u201cIBSS\/NTRIP Server1<\/strong>\u201d (and 2 and 3).\u00a0 These are the connections used to Push-Out data from the GNSS base into the NTRIP Caster you designate. \u00a0[Aside: IBSS<\/em> is a Trimble invented term we can ignore]<\/p>\n

Aside<\/strong><\/span>: Note that this device can in fact be a \u201cbaby Caster\u201d serving just its own base station to up to ten NTRIP Clients<\/a>. However a publicly accessible (typical static) IP is required for this. Your motivation to use RTK2go<\/a> may be simply to forward the base station to a publicly available Caster so others can access it.<\/p>\n

Please press the line (it is in fact an html button) marked IBSS\/NTRIP Server1<\/strong> and you will be taken to the I\/O setup page, shown below.\u00a0 If stream #1 is already in use (perhaps this base is sending to data to another NTRIP Caster as well), simply select one of the other two lines and use that.<\/p>\n

Side note<\/strong><\/span>: Observe that each page starts with a combo drop-down
\nwhere you can easily move to another stream if desired.<\/p>\n

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

This is the critical page where you will enter two key things:<\/p>\n

    \n
  1. The reservation details you have received from the RTK2go registration<\/a> process or from the Caster operator if you are connecting to another Caster.<\/li>\n
  2. What sort of data will be sent over that connection to the remote caster. Typically this will be RTCM3 messages (or perhaps the older CMR+ format used by Trimble).<\/li>\n<\/ol>\n

    The rest of this page is not of any interest to us today and can be ignored.\u00a0 This includes the sections marked RT27<\/strong>, OmniStar<\/strong>, and BINEX <\/strong>and CMR<\/strong> (unless you plan to send that).<\/p>\n

    Taking each of the two sections in turn…<\/p>\n

    Caster Setup<\/strong><\/h2>\n

    We now setup the connection to the RTK2go Caster.\u00a0 Look at the registration confirmation email you received and find the section similar to the below. You will of course enter you own details rather than this example.<\/p>\n

    Sir or Madam: The requested mountPt has been added to the
    \nSNIP<\/strong><\/span> NTRIP Caster operating at rtk2go.com:2101<\/strong> and may now be used.<\/p>\n

    The mountPt name is: aTrimbTest<\/strong> – (this is case sensitive and must match to be used)
    \nWith the user account: itsmeAgain<\/strong> – (also case sensitive)
    \nWith the password: iforgotit<\/strong> – (also case sensitive)
    \nOther details [City: Glendora, CA<\/strong>, Country: United States of America<\/strong> Code: USA<\/strong>]<\/p>\n

    This connection is expected to use the NTRIP Rev2<\/strong> format (contact us if Rev1<\/strong> is preferred)<\/p>\n

    The key section of the unused dialog appears below.\u00a0 Note that this device defaults to using NTRIP Rev2 (rather than Rev1 which many inexpensive and\/or open source based devices use).\u00a0 If you requested a Rev1 reservation, no problem, you can set it up that way as well.\u00a0 But, for a base station, you MUST<\/strong> use the reservation format you were assigned.\u00a0 Note that the line for \u201cStatus\u201d is \u201cInit\u201d at this point.\u00a0 If there are errors in the setup or connection, they will be summarized (rather poorly) on that line.<\/p>\n

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

    Enter the above registration data so the dialog now looks like the below.\u00a0 Use the City name as the \u201cIdentifier\u201d or leave it blank (Trimble will default to using a product name and serial number here). You can enter the 3-digit country code or leave it blank, but the SNIP<\/strong><\/span> Caster will fill it in for you based on the IP which the base connects from.\u00a0 You can leave the \u201cNetwork\u201d blank as well, the SNIP<\/strong><\/span> Caster will fill it in as well.<\/p>\n

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

    Be sure to check<\/strong> the \u201cEnable\u201d button.\u00a0 Do not check<\/strong> the \u201cIBSS\u201d mode button. Do not check<\/strong> the SSL\/TLS button.<\/p>\n

    If you requested a Rev1 reservation by mistake:\u00a0 Chose \u201cNTRIP v1.0\u201d in the combo drop-down for NTRIP Version.\u00a0 All other values remain the same, and the SSL option is hidden.\u00a0 There is no user name in a Rev1 style connection, although this field remains visible in the dialog,\u00a0 just leave it blank.<\/p>\n

    We have to save these changes (the OK<\/strong> button at the bottom of the page), but first we need to set the message contents to be sent.<\/p>\n

    Setup Details for using your own copy of SNIP<\/span><\/strong><\/p>\n

    This article was written for those sending data directly to www.RTK2go.com<\/a> from the Trimble base. Typically this is so that your rover devices can then access it in the field from a public IP rather then the private office network your Trimble device is at.\u00a0 Here are two further variations:\u00a0 If you are sending the data to your own copy of SNIP<\/strong><\/span> somewhere else (such as a VM you leased from Amazon Web Services<\/a>), replaces the line “rtk2go.com:2101” with your own IP and port.\u00a0 If you have the Trimble base connected to a local copy of SNIP<\/strong><\/span> running in your office (and can not open local firewalls to allow others to get to it), use the Push-Out tab<\/strong><\/a> to forward the data to RTK2go using the same reservation credentials.<\/p>\n

    Message Setup<\/strong><\/h2>\n

    For the most users, you will send only RTCM3 messages. You will want to send either older legacy<\/em> messages or the newer \u201cMSM\u201d messages.\u00a0 You set that in the below section (which happens to default to the even older RTCM 2.2 message format when it is first displayed). \u00a0All other message types shown on this page should be set of off or disabled.<\/strong>\u00a0 Technically speaking, more than one message type can be sent over the same stream in NTRIP but as the rover devices cannot then decode and extract the individual messages they need, this has no practical use.<\/p>\n

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

    First, in the Version<\/strong> combo box\u2026\u00a0\u00a0 Select the RTCM3 message (rather than RTCM2.x messages) and the display will change to be one of the two formats shown below.<\/p>\n