{"id":538,"date":"2016-03-04T23:42:59","date_gmt":"2016-03-04T23:42:59","guid":{"rendered":"\/?post_type=ht_kb&p=538"},"modified":"2020-08-09T19:41:55","modified_gmt":"2020-08-09T19:41:55","slug":"console-logging","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/console-logging\/","title":{"rendered":"Console Logging"},"content":{"rendered":"

Along the lower half of the application window, below the set of control tabs, is a scrolling textual display called the console log. Several controls provide the means to control what level of detail is shown.\u00a0 Below that, at the bottom of the application window, is a status display line.<\/p>\n

<\/p>\n

The above image shows a typical fragment of a report from the console. The user has just pressed the List Mount Point button and a report of the active mountPts from all stream types has been appended to the log.\u00a0 If any of the remote relay caster connections were down, this would also be shown.<\/p>\n

Small Icons<\/a><\/h3>\n

The console log employs a set of small icons with each entry to quickly show the type of connection the entry pertains to.\u00a0\u00a0 This is helpful to disambiguate the entries when the same MountPt name is used in different contexts.\u00a0 Consider a base station called “xxx” which arrives to the Caster with a PUSH_In<\/strong> connection, is sent out of the Caster to another Caster with a PUSH_Out<\/strong> connection, and is then connected to be one or more NTRIP Client<\/strong> devices.\u00a0 Without these symbols it is harder to discern which connection is being described.\u00a0 This symbol is added when the console is reporting details about the stream or its connection. The symbol is not used when reporting about a connected user (rover or NTRIP Client) and that stream.<\/p>\n

These six small symbols are used:
\n\u00a0\u2191<\/big><\/span>\u00a0<\/strong> The Data is from Remote-Relay<\/a> connection
\n\u2190<\/big><\/strong><\/span>\u00a0 The Data is from PUSH-In<\/a> connection
\n\u00a0<\/strong>\u2192<\/big><\/strong><\/span>\u00a0 The Data is from PUSH-Out<\/a> connection
\n\u21d0<\/strong><\/span>\u00a0 The Data is from RAW TCP\/IP<\/a> connection
\n\u2193<\/big><\/span><\/strong>\u00a0 The Data is from Serial UART<\/a> connection
\n\u21d2<\/big><\/strong><\/span>\u00a0 The Data is from a NEAR<\/a> pool<\/p>\n

The symbol is not used when reporting about a connected user (a rover or NTRIP Client) for each stream. Here is an typical example where three Remote-Relay connection events are being described.<\/p>\n

[SCSC\u2191<\/span>]: \u00a0Stream analysis completed... Parsing is Enabled<\/strong> for one format. \u00a0\u00a0[Detected RTCM3<\/strong>, Decoded: RTCM3<\/strong>]\r\n[Demo1\u2191<\/span>]: Stream analysis completed... Parsing is Enabled<\/strong> for one format. \u00a0\u00a0[Detected RTCM3<\/strong>, Decoded: RTCM3<\/strong>]\r\n[Demo2\u2191<\/span>]: Stream analysis completed... Parsing is Enabled<\/strong> for one format. \u00a0\u00a0[Detected RTCM3<\/strong>, Decoded: RTCM3<\/strong>]<\/pre>\n
 <\/p>\n
Labeling Style<\/a><\/h3>\n
The console supports a number of different labeling styles.\u00a0 These can be quickly selected from the button Types<\/strong> and the menu Toggle the Label Style Used.<\/em>\u00a0 Each time the menu is selected the style changes.\u00a0 There is a rotation of several styles to select from.\u00a0 The different items in the list below are enabled and disabled to create the final label heading to be used.<\/p>\n