{"id":5002,"date":"2018-02-19T14:27:31","date_gmt":"2018-02-19T14:27:31","guid":{"rendered":"https:\/\/www.use-snip.com\/kb\/?post_type=ht_kb&p=5002"},"modified":"2024-12-09T22:53:06","modified_gmt":"2024-12-09T22:53:06","slug":"pfat-translate-settings-uses","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/pfat-translate-settings-uses\/","title":{"rendered":"PFAT: Translate Settings and Uses"},"content":{"rendered":"

The P.F.A.T.™<\/strong> control system provides several innovative ways to control the messages present in every data stream.\u00a0 The PFAT features<\/a> are available in the Pro<\/strong><\/em><\/span>, and Basic<\/strong><\/em><\/span>, editions of SNIP<\/strong><\/span>. Lite<\/strong><\/em> <\/span>copies of SNIP<\/strong> <\/span>share the same code base, but many of these innovative features are disabled in the freely available Lite<\/strong> <\/em><\/span>edition.<\/p>\n

Using the PFAT Translate <\/strong>Dialog Control<\/h3>\n

\"\"<\/p>\n

The PFAT<\/strong> Translate <\/em>control is used to modify and translate <\/strong>the selected RTCM3 message types<\/a> found in any Base Station data stream.\u00a0 Unlike the other PFAT<\/strong> controls, there are several translate commands that can be invoked for various needs.\u00a0 And many more are still in development.\u00a0 Each has its own dialog, making the translate controls easily the most complex interface found in SNIP<\/strong><\/span>.\u00a0 But this complexity enables a number of powerful features unique to SNIP<\/strong><\/span> and not found in other Casters.\u00a0 The results of the translation process are forwarded on to any NTRIP Clients<\/a> or to other users in SNIP<\/strong><\/span> (such as a PUSH_Out<\/a> stream) in the normal way.\u00a0 All the messages are still parsed and may be used in various navigation<\/a> and monitoring services.\u00a0 Whenever any PFAT<\/strong> Translate <\/em>action is active, the right-click menu<\/a> for the stream shows a check mark.\u00a0 Selecting the menu item displays the Add<\/em> dialog box.\u00a0 The message stream must be Parsed<\/a> in order to Filter the messages.\u00a0 A master on\/off switch for all translation steps is provided in this dialog as well.<\/p>\n

The individual controls of the master Translate <\/em>dialog are described in further detail here (link to be provided at release).\u00a0 The basic user interaction is to select one of the translate steps, then complete the setting in the presented dialog for that step.\u00a0 Multiple translate steps may be selected.\u00a0 [An example would be to offset the Base Station ECEF position, and to downgrade 1004 message types to be 1002 message types for an L1-only user community.] \u00a0 It is possible to create steps which conflict with each other, therefore some user forethought is presumed.\u00a0 Like all PFAT<\/strong> settings, the values selected are preserved and used each time the stream (or SNIP<\/strong><\/span>) is started.\u00a0 Hovering the mouse above a translation step will provide (in the tool-tip) a further description of its usage.<\/p>\n

The Master Translate Dialog<\/h3>\n

The Master Translate Dialog is show below.\u00a0 The translation steps that are disabled on your copy of SNIP<\/strong><\/span> are shown as grayed out (these are still in development).\u00a0\u00a0\u00a0 By clicking on the Setup<\/strong> button for a given step, the settings dialog for that step can be brought up.<\/p>\n

\"\"<\/p>\n

Current Translations Supported<\/h3>\n

At this time the following translation steps are shipped with all Basic<\/strong> <\/em><\/span>and Pro<\/strong> <\/em><\/span>models of SNIP<\/strong>\u00a0 <\/span>(and also with Evaluation<\/strong> <\/em><\/span>models).<\/p>\n

ECEF Adjustment<\/h4>\n

The ECEF Adjustment<\/em> translation is used to adjust the ECEF position of the Base Station in the RTCM3 messages.\u00a0 If the reported position from the data stream is incorrect, or in another reference frame, this translation is used to align it to the preferred datum.<\/p>\n

See this article<\/a> for further details, and this article<\/a> for an example of use.<\/p>\n

Station Details<\/h4>\n

The Base Station Details<\/em> translation is used to translate values about the base station in the messages.\u00a0 This includes the Antenna description (aka NULLADVANTENNA) and serial number as well various strings about the GNSS receiver device used.\u00a0 The message types MT1007, Mt1008, and MT1033 can also be inserted into message data streams when they are not present.<\/p>\n

See this article<\/a> for further details, and this article<\/a> for an example of use with MT1008.<\/p>\n

Last Observation Flag<\/h4>\n

The Last Observation Flag<\/em> translation is used to adjust a flag present in the RTCM3<\/a> messages used to indicate that the last set of observations at a given common time has been sent to the user.\u00a0 By convention, GPS observations are always sent first, followed by GLO observations, followed by other GNSS types.\u00a0 When a given message observation type has been filtered<\/a> out with other PFAT<\/strong> methods, it is required that the new ‘last observation’ now convey this flag.\u00a0 [Failure to do this leaves the rover device hanging and waiting for the final message for the common epoch time which never arrives.]\u00a0\u00a0 At this time the Last Observation Flag<\/em> translation operates on RTCM3 message types 1001~1004 (GPS) and 1009~1012 (GLONASS).<\/p>\n

See this article<\/a> for further details.<\/p>\n

L1\/L2 Translation to L1 Only Messages<\/h4>\n

The Remove L2 Content\u00a0 <\/em>translation is used remove L2 code and carrier content from RTCM3 Legacy message types 1003~1004 (GPS) and 1001~1012 (GLONASS) to produce (smaller) 1002 and 1010 messages.\u00a0\u00a0 This has value to network operators whose rover communities (NTRIP Clients<\/a>) are made up of L1-only<\/em> devices by allowing them to provide a wider set of Base Station streams without sending larger message payloads than required.<\/p>\n

See this article<\/a> for further details.<\/p>\n

Legacy to MSM Message Conversion<\/h4>\n

The Legacy to MSM Message Conversion <\/em>translation is used to create newer MSM style messages from Legacy RTCM3 message types 1001~1004 (GPS) and 1009~1012 (GLONASS).\u00a0 However, it\u00a0 will not add additional measurement information (more precision or Doppler data) which is not present in the original message.\u00a0 This has value to network operators operating with older pre-MSM Base Stations and whose rover communities (NTRIP Clients<\/a>) are made up of devices that use MSM messages, rather than more established classic messages.<\/p>\n

See this article<\/a> for further details.<\/p>\n

MSM to Legacy Message Conversion<\/h4>\n

The\u00a0MSM to Legacy Message Conversion <\/em>translation is the inverse of the\u00a0Legacy to MSM Message Conversion<\/em> translation.\u00a0 It is used to create RTCM3 Legacy message types 1002~1004 (GPS) and 1010~1012 (GLONASS) from MSM messages (types MSM4, 5, 6, and 7).\u00a0 Message content is truncated when required, and some data elements (Doppler) are not supported in the classical messages.\u00a0 This has value to network operators whose rover communities (NTRIP Clients<\/a>) are made up of older devices that cannot use MSM messages, but only the more established Legacy messages.<\/p>\n

See this article<\/a> for further details.<\/p>\n

See Also<\/h3>\n