{"id":7145,"date":"2020-08-07T18:41:41","date_gmt":"2020-08-07T18:41:41","guid":{"rendered":"https:\/\/www.use-snip.com\/kb\/?post_type=ht_kb&p=7145"},"modified":"2021-03-10T00:12:33","modified_gmt":"2021-03-10T00:12:33","slug":"adding-mt1008-rtcm-messages","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/adding-mt1008-rtcm-messages\/","title":{"rendered":"Adding MT1008 RTCM Messages"},"content":{"rendered":"

In this article we review how to add the RTCM message\u00a0 Antenna Descriptor and Serial Number<\/a><\/strong>\u00a0 aka MT1008<\/strong> to any Base Station data stream when it is missing.\u00a0\u00a0\u00a0\u00a0 We use SNIP<\/strong><\/span>‘s proprietary PFAT<\/strong><\/span>\u00ae abilities<\/a> to add the missing messages by using the Station Translation<\/a> dialog.<\/p>\n

The Need & the Solution:<\/h3>\n

Some Trimble GNSS models require the presence of MT1008<\/strong> in order for them to utilize RTCM corrections\u00a0 originating from other brands.\u00a0 The actual content of this message is most often just the text “ADVNULLANTENNA” (indicating that any signal bias affects of the antenna have already been removed from the measurements, read more here<\/a>).\u00a0\u00a0 Other GNSS brands do not insist on seeing this message before using corrections.<\/p>\n

The message MT1008<\/strong> is needed in order to provide corrections for certain \"\" models when the data is originating from other GNSS Base Stations including:\r\n

\r\n\t\t
\r\n
\r\n\t
\r\n\t\t\t\"LeicaLogo\"\r\n\t\t<\/div>\r\n\r\n\t<\/div>\r\n
\r\n\t
\r\n\t\t\t\"Septentrio2\"\r\n\t\t<\/div>\r\n\r\n\t<\/div>\r\n
\r\n\t
\r\n\t\t\t\"stonexLogo\"\r\n\t\t<\/div>\r\n\r\n\t<\/div>\r\n
\r\n\t
\r\n\t\t\t\"topcon-logo2\"\r\n\t\t<\/div>\r\n\r\n\t<\/div>\r\n
\r\n\t
\r\n\t\t\t\"Hemisphere\"\r\n\t\t<\/div>\r\n\r\n\t<\/div>\r\n
\r\n\t
\r\n\t\t\t\"ublox-logo\"\r\n\t\t<\/div>\r\n\r\n\t<\/div>\r\n
\r\n\t
\r\n\t\t\t\"emlidLogo\"\r\n\t\t<\/div>\r\n\r\n\t<\/div>\r\n\t<\/div>\r\n<\/div><\/p>\n

With the improvements to the PFAT<\/strong><\/span>\u00ae Translation<\/a> of Station Details<\/a> dialog provided in this release, the SNIP<\/strong><\/span> operator can edit any of the station details, as before.\u00a0 But the operator can now also<\/em> make any text string “empty” (rather than only provide substitute text as before).<\/p>\n

And, of greater value here, you can now create and insert<\/strong> these messages when they do not exist in the original data stream. The messages are inserted into the data stream at the repetition rate you have selected after the Base Station location message (MT1005\/1006).\u00a0 With this simple change the problem Trimble devices are appeased and will operate in RTK fixed and float modes using corrections provided by non Trimble Base Stations.<\/strong><\/p>\n

In some use cases (typically where extreme mm level accuracy is needed) the presence of the “antenna description text” is not only needed, but must<\/em> adhere to certain naming and capitalization conventions, typically those developed by IGS<\/a>.\u00a0 These defined terms exist for antenna models where corresponding calibrations tables exist.<\/p>\n

Spelling and capitalization differences can cause problems in this field, so with this release of SNIP<\/strong><\/span> we have also added over 700<\/strong> new predefined antenna description strings in a selection box.\u00a0 Along with this is a pop-up with tool tips further describing the antenna make and models they refer to.\u00a0\u00a0 But for most user applications, a blank line of text, or the ADVNULLANTENNA choice (the default) is sufficient.<\/p>\n

A Step-by-step Example:<\/h3>\n

The Source Data<\/h4>\n

As an example, we will use a slightly older Hemisphere GNSS device that provides Legacy GPS and GLO content.\u00a0 It produces the common messages of:<\/p>\n