{"id":7904,"date":"2021-09-13T19:51:47","date_gmt":"2021-09-13T19:51:47","guid":{"rendered":"https:\/\/www.use-snip.com\/kb\/?post_type=ht_kb&p=7904"},"modified":"2021-10-04T21:15:07","modified_gmt":"2021-10-04T21:15:07","slug":"ntrip-server-warnings","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/ntrip-server-warnings\/","title":{"rendered":"NTRIP Server Warnings"},"content":{"rendered":"

This article covers the NTRIP Server <\/strong><\/em>sections of the automatic error reporting in greater detail.\u00a0 Instructions regarding how to set the trigger thresholds for the needs for your own Caster are provided below.\u00a0\u00a0 The SNIP<\/span><\/strong> NTRIP Caster<\/a> provides a range of automatic error reporting mechanisms to alert the Caster Owner\/Operator when various detrimental operating conditions occur.\u00a0 A higher level overview of these functional sections is provided in this article<\/a>.<\/p>\n

Overview<\/h2>\n

The logic involved in this section deals primarily with detecting bad NTRIP Server<\/strong><\/a> connections<\/em> attempts (PUSH_in connections<\/a>) and reporting these (by eMail) to both the NTRIP operator.\u00a0 This complements other sections that deal with SNIP<\/strong><\/span> itself or NTRIP Client connections.\u00a0 In the case of closed Casters<\/a> using the Reservation system<\/a>, the email of the registration owner is used for sending reports as well.\u00a0 Informing the Base Station owner provides a means to alert the remote device operators with details of the problem at any hour of the day without operator intervention and at the moment the event occurs.<\/p>\n

This section of the dialog consists of the three related logic areas highlighted below.<\/p>\n

\"\"<\/a><\/p>\n

Each functional area can be enabled \/ disabled<\/em> by checking \/ un<\/strong>checking<\/em> the associated check box.\u00a0 Each SetUp<\/strong> button brings up a control dialog where the threshold behavior of that function can be set.\u00a0 For this group of functions the triggering moment is related to when the NTRIP Server<\/a> connection occurs.\u00a0 Every time an NTRIP Server connects to the Caster, the logs are checked for prior connections and any limits which have been exceeded.\u00a0 This may result in sending a warning eMail out.\u00a0 The Run button causes a summary report to be created. The Run Now<\/strong> button (at the bottom of the dialog) can be used to process all the active functions and send a report.<\/p>\n

Each functional area is discussed in turn.<\/p>\n

Base Station Off-Line Monitoring<\/h3>\n

This area deals with the detecting and reporting when a Base Station is offline.\u00a0 Only the Base Stations which are listed are tracked and reported on.\u00a0 If a listed Base Station has NEVER been present since SNIP<\/strong><\/span> started, it will not be tracked.\u00a0 Only listed station which have been active in the past (since the last restart) are tracked, this prevents false positive reports, in particular during the initial start up phase of operations.<\/p>\n

The Monitored Base Station<\/strong> dialog is similar but slightly more complex than many of the other error reporting threshold dialogs.<\/p>\n

\"\"<\/a><\/p>\n

Here you can create a list of all the Base Stations that are to be tracked and reported when offline.\u00a0\u00a0 Not every Base Station requires this, and it can be counter productive to add more than are wanted.<\/p>\n

The dialog also has the normal inputs to a)<\/strong> control how often the event must occur (in this case the time interval during which the Base must be offline, in seconds) and b)<\/strong> control if the operator is CCed in the eMail (applicable only to PUSH-In reservation<\/a> uses).<\/p>\n

The value selected for time offline before triggering<\/em> is a judgement call.\u00a0 A range from 15 to 7200 seconds (2 hours) is supported.\u00a0 In the above example, a time of 10 minutes (600 seconds) was used. Very short times (~15 seconds) reliably report what occurred, but often the NTRIP protocol itself has reconnected and resumed before the operator can react to such events.\u00a0 Very long times (>30 minutes to 2 hours) can be advantageous if the Base Stations have unreliable internet connections and the operator only wishes to be informed of more major events.\u00a0 The default time is 300 seconds (5 minutes).<\/p>\n

A drop-down combo box provides a list of all active MountPts from which the operator can select which is to be added.\u00a0 The usual hints showing additional content details about that mountPt are provided for the entries.\u00a0 The MountPts to be tracked are added by selecting them from the list.\u00a0 Once added, they are shown in the dialog.\u00a0 If over 50 mountPts have been selected, the visual list is truncated (you can use the Print command to see the members).<\/p>\n

In addition, the following additional controls provide the ability to create and manage the list of Base Stations (mountPts) which is to be tracked.<\/p>\n

Clear All<\/h4>\n

Pressing this button removes all the list members, producing an empty list.\u00a0 This has the same effect as unchecking the check box for this function on the main dialog.<\/p>\n

Add All<\/h4>\n

Pressing this button adds every member of the combo box to the list.<\/p>\n

Unless all of your Base Stations connections are unusually reliable, or you have set the off-line period to be large (>1hr), or you are simply monitoring things for debug, such a list is often not suitable.\u00a0 This can result in many eMails being sent if the off-line trigger time is set to be short.<\/p>\n

Print<\/h4>\n

Pressing this button lists every mountPt that is to be tracked to the console list for further review.<\/p>\n

Load All Push-In Reservations<\/h4>\n

This checkbox controls how the combo list is loaded.\u00a0 When un<\/strong>checked only the active mountPt are loaded (regardless of the type of connection<\/a> they come from).\u00a0 When checked, all active mountPts are loaded as well as all mountPts in the PUSH_In reservations<\/a> list.\u00a0 This allows selecting Base Stations which connect by way of a PUSH_In (NTRIP Server) connection when they are not present at that moment in time.<\/p>\n

Recall that before any tracked mountPts is reported as offline it must first be present for a short period of time.\u00a0 This prevents false triggering on any tracked mountPts that have never connected to your SNIP<\/strong><\/span> Caster.<\/p>\n

eMail on data Resume<\/h4>\n

This checkbox controls the sending of an eMail when the data has resumed.\u00a0 When un<\/strong>checked no eMail is sent, when checked an eMail is sent when the tracked Base Station data stream resumes and has been declared stable again.<\/p>\n

 <\/p>\n

Push_In Connection Issues<\/h3>\n

This area deals with the most common NTRIP Server connection problems (PUSH_In connections).\u00a0 Issues such as using the wrong password, capitalization problems, NTRIP Revision (Rev1 vs Rev2<\/a>), missing or incorrect mountPts, and violating various User Account restrictions<\/a> are all handled here.\u00a0 Ill-formed connections attempts are also reported if they use the POST or SOURCE keywords defined in NTRIP.<\/p>\n

The setup dialog allows you to set the number of bad connections which must occur before eMail is sent (in the spin box).\u00a0 You can also set how often another email wold be sent to any connection which continues to make this error (in the combo drop down).\u00a0 You can also CC the operator (or not) on these emails.<\/p>\n

\"\"<\/a><\/p>\n

Base Station IP Blocked Events<\/h3>\n

This area deals with sending an eMail when the offending IP has just been blocked.\u00a0 The actual thresholds for blocking are set in the IP blocking<\/a> dialog.\u00a0 Note the NTRIP Server multiplier control on the IP blocking dialog as well.<\/p>\n

The setup dialog does not allow you to set the number of bad connections which must occur before eMail is sent.\u00a0 This value is set in the IP blocking<\/a> dialog.\u00a0\u00a0 The only option provided is that you can CC the operator (or not) on these emails.<\/p>\n

\"\"<\/a><\/p>\n

Typical Examples of use<\/h2>\n

Here we provide two common NTRIP Client connection problems as examples of use.
\n<\/strong><\/p>\n