{"id":6687,"date":"2019-10-21T18:16:06","date_gmt":"2019-10-21T18:16:06","guid":{"rendered":"https:\/\/www.use-snip.com\/kb\/?post_type=ht_kb&p=6687"},"modified":"2020-08-28T14:32:03","modified_gmt":"2020-08-28T14:32:03","slug":"pfat-legacy-to-msm-messages","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/pfat-legacy-to-msm-messages\/","title":{"rendered":"PFAT: Legacy to MSM messages"},"content":{"rendered":"

The Legacy to MSM<\/em> translation is used to translate older Legacy messages to newer MSM style message types (msm = multiple signals messages<\/em>).\u00a0 This has value to network operators with an installed base of older Base Station GNSS devices which cannot produce MSM messages directly.\u00a0 Caster streams can be developed that overcome these limits.\u00a0 And these streams may be used with other GNSS Base Station sending MSM content in NEAR<\/a> pools.\u00a0 RTCM SC-104 recommends that MSM and Legacy observations should not be combined in the same stream, and it is wasteful of wireless bandwidth.<\/p>\n

In more detail:\u00a0 messages MT1002~1004 (for GPS) and MT1010~1012 (for GLO) are converted to the equivalent MSM message types selected during setup.\u00a0 That is, messages MT1074~1077 (GPS)\u00a0 and MT1084~1087 (GLO).\u00a0 Only GPS and GLO GNSS types are supported, as the other GNSS types do not have legacy equivalents.\u00a0 In general, only the MSM4 message would be used because the source Legacy messages lack extended precision of any Doppler information which is found in MSM5, 6, or 7.<\/p>\n

Use<\/h3>\n

This translation consists of an on\/off checkbox (“Enable Translation”) and a set of radio buttons to select which of four possible MSM style message types is to be output.\u00a0 The default message choice of “MSM4” should be used unless it is desired to create MSM5, 6, or 7 messages with empty data content where the Legacy source cannot provide it (such as Doppler data).<\/p>\n

\"\"<\/p>\n

If the subject stream does not contain messages with suitable Legacy content, some informative warnings are presented and the checkbox is disabled.<\/p>\n

A note about Loss of Lock<\/em> Times<\/strong>.\u00a0 The loss of lock count is used in RTCM observation messages to convey the minimum interval of time since the last detected carrier loss occurred on a given signal. It is generally used by the rover device as a quality indication and when loss of lock occurs on a given signal the carrier wavelength ambiguity process must be repeated.\u00a0\u00a0 In the MSM messages there are two definitions for loss of lock time, and in the Legacy message definitions there is a third.\u00a0 These three definitions vary in range and precision and were selected to conserve bit sizes in the messages. When translating from one message to another, mild truncation between these intervals occurs.<\/p>\n

Example<\/h3>\n

Simply enable the translation on any Base Station stream sending GPS and\/or GLO Legacy message content.\u00a0 You can see the resulting translation using stream tool tips or with\u00a0 the RTCM message viewer<\/a>.<\/p>\n

\"\"<\/p>\n

Note the tool tip showing that the GPS MT1004 has been translated to GPS MT1074.\u00a0 The green highlight color in the message numbering cells also serves to indicate that the message has had PFAT<\/strong> operations performed\u00a0 on it.<\/p>\n

Hint<\/span>:<\/strong> If both a Legacy and MSM stream will be provided from a Base Station, you may want to append the text “-MSM”<\/strong> to new MSM streams to help users identify the stream.<\/p>\n

The reverse of this operation is provided by the translation called MSM to Legacy<\/em> and is described in this article<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

The Legacy to MSM translation is used to translate older Legacy messages to newer MSM style message types (msm = multiple signals messages).\u00a0 This has value to network operators with an installed base of older Base Station GNSS devices which cannot produce MSM messages directly.\u00a0 Caster streams can be developed […]<\/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":[334],"ht-kb-tag":[453,452,381,367],"class_list":["post-6687","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-advanced-topics","ht_kb_tag-legacy","ht_kb_tag-msm","ht_kb_tag-pfat","ht_kb_tag-translate"],"_links":{"self":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/6687","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=6687"}],"version-history":[{"count":9,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/6687\/revisions"}],"predecessor-version":[{"id":6808,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/6687\/revisions\/6808"}],"wp:attachment":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/media?parent=6687"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb-category?post=6687"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb-tag?post=6687"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}