{"id":3079,"date":"2017-01-28T20:08:05","date_gmt":"2017-01-28T20:08:05","guid":{"rendered":"\/kb\/?post_type=ht_kb&p=3079"},"modified":"2017-07-17T19:35:22","modified_gmt":"2017-07-17T19:35:22","slug":"viewing-rtcm-1019-1020-messages","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/viewing-rtcm-1019-1020-messages\/","title":{"rendered":"Viewing RTCM 1019, 1020 messages"},"content":{"rendered":"

Instructions for displaying the contents of RTCM ephemeris <\/em>(orbital) data message types 1019 and 1020.<\/p>\n

When something is not working in a GNSS navigation filter, it is often helpful to look at the\u00a0ephemeris data that is input to the filter.\u00a0\u00a0 This orbital data is needed in order to make any type of navigation filter work.\u00a0 In some systems each rover device obtains this locally (by decoding the SVs in view to at it’s location), while in other systems an NTRIP Caster<\/a> such as SNIP<\/strong><\/span> provides it. There are advantages to both, and the best designs often use a hybrid approach.\u00a0 When the ephemeris data comes from a stream on a SNIP<\/strong><\/span> Caster, then the RTCM Content Viewer<\/a> dialog can be used to look at the message contents.<\/p>\n

Hint<\/strong><\/span>: The SNIP<\/strong><\/span> open caster<\/a> found at ntrip.use-snip.com:2101<\/a> provides a complete set of world wide broadcast ephemeris data which you are welcome to connect to and use in your own system.\u00a0 There are several public services which provide similar data streams, and well as services which provide more precise orbital and clock correction information.<\/p>\n

How To…<\/h4>\n

To enable RTCM3 decoding the selected stream must be parsed. And of course it must contain messages in an RTCM3 form (other content can also be present but will be ignored).<\/p>\n

    \n
  1. On any stream’s display (for any stream type<\/a> in a tab display)
    \nright-click and be sure the Parse<\/strong> <\/em>check box is active.<\/li>\n
  2. Select the Show in RTCM3 Viewer<\/em><\/strong> menu item to start the RTCM3 decoder dialog,
    \nthe dialog will appear with the selected stream in its own tab.<\/li>\n
  3. Click on the small arrows on the right side on any message type,
    \nthe view will be expanded to show the detailed contents of that message.<\/li>\n
  4. Resize the display window as needed when many items are expanded.<\/li>\n<\/ol>\n

    In order to see the last (most current) message of a given type, switch to the “View Messages sorted by Message Type<\/span>” mode. The dialog display starts in this mode, but may be in the “View Messages by Stream<\/span>” mode if it was used before.\u00a0 As new messages arrive, the data shown in each tab will be updated.\u00a0 You can also stop the display from updating with the Pause<\/strong><\/em> button at the bottom of the dialog.<\/p>\n

    If the menu item Show in RTCM3 Viewer<\/em><\/strong> menu item is greyed out, re-confirm that the Parse menu item is checked.\u00a0 If the dialog appears but no data is shown, then no RTCM3 message content has been found in the stream to decode.<\/p>\n

    Hint<\/strong><\/span>:\u00a0 Rather than invoke this dialog with its more detailed decoding, if you are simply interested to learn if<\/span> a message type exists in the data stream; just use the Show Message Types<\/strong><\/em> menu item.\u00a0 If the stream is being parsed, a precise listing of the messages that are decoded will be sent to the console as they occur.\u00a0 If the stream is not parsed, then SNIP<\/strong><\/span>‘s universal decoder<\/a> will provide a rough summary of the data contents it can decode. Be sure to uncheck this menu item when done, as it causes a considerable amount of console log clutter.<\/p>\n

    This is quick way to discover if a Base Station is sending in proprietary messages, rather then the RTCM3 you thought. It is also useful to discover that a station is sending in unwanted NMEA-183 message content\u00a0 (which would be corrected not in SNIP<\/strong><\/span> but by proper setup of the Base Station).\u00a0 [When SNIP<\/strong><\/span> is Parsing a stream for RTCM3 content, such extraneous content is filtered out and is not sent to the NTRIP Clients.]<\/p>\n

    Often Base Stations are set up not to send ephemeris messages at all.\u00a0 The general point of view is that this is wasteful of precious bandwidth to the NTRIP Clients, who can normally obtain the same information (perhaps after a ~25 second start-up delay).<\/p>\n

    Typical Data Content<\/h4>\n

    Here is a typical display for a stream called “RTCM3EMP”\u00a0 which is sending ephemeris for the GPS, GLONASS, Galileo, and Compass GNSS systems.\u00a0 Basically this represents a single stream containing all<\/span> the current broadcast orbits for all<\/span> the SVs in the world.<\/p>\n

    \"SNIP_Orbits_decode\"<\/p>\n

    The two arrows along the left side indicate that message types 1019 and 1020 are fully decoded and can be expanded (the the other message types are not).\u00a0 Expanding either of these creates a display with the most current key orbital details.\u00a0 Click on the images below to see each group decoded and shown at full scale.<\/p>\n

    \"SNIP_1019_decode\"<\/a>\u00a0\u00a0\u00a0 \"SNIP_1020_decode\"<\/a><\/p>\n

    In reviewing the above data, recall that the GPS ephemeris is expressed using Kepler equations, while the GLONASS system uses an XYZ dot product format.\u00a0 Unlike observational data that changes with every update (typically every second), the precise message content for ephemeris information only changes when a new orbit is issued by the GNSS ground control segment for that system.<\/p>\n

     <\/p>\n

    \n

    See Also<\/h4>\n

    These articles contain similar information about decoding other common RTCM message types<\/p>\n

    Viewing RTCM 1004 and 1012 messages<\/a><\/p>\n

    Using the RTCM3 Decoder Dialog<\/a><\/p>\n

    RTCM Message Cheat Sheet <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

    Instructions for displaying the contents of RTCM ephemeris (orbital) data message types 1019 and 1020. When something is not working in a GNSS navigation filter, it is often helpful to look at the\u00a0ephemeris data that is input to the filter.\u00a0\u00a0 This orbital data is needed in order to make any […]<\/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":[341],"ht-kb-tag":[295,204,297],"class_list":["post-3079","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-message-decoding","ht_kb_tag-decoder","ht_kb_tag-rtcm3","ht_kb_tag-type-1019"],"_links":{"self":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/3079","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=3079"}],"version-history":[{"count":11,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/3079\/revisions"}],"predecessor-version":[{"id":3244,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/3079\/revisions\/3244"}],"wp:attachment":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/media?parent=3079"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb-category?post=3079"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb-tag?post=3079"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}