Table of Contents

Embedded NTRIP Caster

Current

This web page gives access to two different tabs:

   Sources tab: This tab lists the mount points currently seen by the NTRIP caster. For each mount point, the table provides the mount point name, the time when the data source started to be available through that mount point, and the IP address of that source. The Status column (second column) indicates the following:

 

Status

Meaning

Green light

Mount point declared in the NTRIP caster source table and data are currently available through this mount point.

Red light

Mount point declared in the NTRIP caster source table but no data are currently available through this mount point.

Orange light

Mount point not declared in the NTRIP caster source table. Data currently available from this mount point. A receiver alarm is also triggered in that case.

 

   Clients tab: This tab lists all the users currently connected to the NTRIP caster. For each user, the table provides the user name, the mount point to which the user is connected, the time when the connection to the mount point started and the user IP address.

 

History

The History web page is an interpretation of the log file presented below. This page gives access to two different tabs:

   Sources tab: This tab lists all the available sources of corrections since the log file was started. For each source, the table provides the mount point name, the current status of the source (green: available; red: unavailable), the times when the source started and stopped to be available, as well as its IP address.

   Clients tab: This tab lists all the users that have been or were connected to the NTRIP caster since the log file was created. For each user, the table provides the user name, the mount point to which the user is, or was connected, the times when the connection to the mount point started and stopped, as well as the user IP address.

 

Log

This web page provides a view of the log file, which is a viewable text file listing all the events detected since the log file was created.

 

When the log file reaches 1Mbyte in size, it is closed and saved, becoming the “old” log file. A new log file is then created.

Later when the new log file reaches 1 Mbyte in size, it is closed and saved, becoming in turn the “old” log file. Data logging is then resumed in the first log file, etc.