Sessions

Use Sessions to see what a base station sent to the caster, which rovers connected to it, and what happened during a connection. Start with the session list, then open a base session for live details or a review of a completed connection.

A base session is one source connection publishing corrections to the caster. A rover connection receives corrections from that source. Each base session has its own detail page; its rover connections appear inside that page. When a rover reconnects, it can appear as another connection even when it uses the same client credentials.

The illustrations below show the current interface with demonstration data. Select an illustration to open it at full size in a new tab.

Open Sessions

You can reach a session from several places:

• Account menu → Sessions opens the server session list.
• Dashboard → Sessions tile or View active sessions opens the list with the Active filter selected.
• Dashboard → base name opens that base's current session. Selecting a rover name opens the same page with that rover selected.
• Mount point → Session history opens the list filtered to that mount point. This action is available from both the account mount point page and the mount point page inside a caster.

On a session detail page, Sessions in the breadcrumb returns to the list. If you came from a filtered list, its status and mount point filters, along with the selected page, are preserved. History of this base opens the sessions for the same mount point when that mount point is available.

Find a base session

The list contains server sessions. Rover connections are available inside each session rather than as separate rows in this list.

Session history for a single mount point. Repeated names represent separate source connections.

Use Status to switch between All, Active, and Ended. A mount point filter is shown above the table when you arrive through a history link; Clear filters returns to the unfiltered list.

Each row shows the name, connection status, transferred bytes, start time, and end time. An ID is shown when a name is unavailable. Sessions are ordered by when their records were created, newest first. Use Previous page and Next page when more records are available.

Select the name to open the session. You can also open the link in a new browser tab. The list loads when you open it or change its filters; automatic live updates are available on the detail page.

Read the session summary

The detail page starts with the base name, its connection state, and the most recent page update. The summary shows:

• Started — when the session began.
• Duration — elapsed time, or the final duration for a completed session.
• Incoming data — total bytes received by the caster from this base during the session.
• Average rate (lifetime) — average bytes per second across the session's duration, not the current transfer rate.
• Rovers — active and ended rover connections associated with this session. These are connection counts, not necessarily unique devices.

The base summary and charts stay visible while you inspect a rover. In this example, Rover-02 is still marked Active, but its status report is stale.

Open Base connection details for the full session ID, source address, last status, and last observed transfer. A completed session can also show its end time and reported termination reason.

Previous session and Next session, when available, open adjacent retained sessions for the same mount point.

Read the charts

Data flow (base to caster) shows observed base throughput in bytes per second. Connected rovers shows the number of active rover connections over time. The period selector applies to both charts: Last hour, Last 6 hours, Last 24 hours, or Last 30 days.

Compare the charts when investigating an interruption. For example, a change in rover count near a drop in observed traffic gives you a time window to inspect in Events.

A gap means observations are missing. It does not prove that the base sent zero bytes during that interval. Historical charts are available only for periods when diagnostics were collected; older sessions may still have summary data without a traffic history.

Inspect a rover

Under Rovers, choose Active, Ended, or All, then select a client name. The inspector shows that specific connection's identity, state, received bytes, start time, duration, last status, and client IP. For a completed connection, it can also show the end time and reason.

The table identifies each connection separately, so two rows with the same client name can have different connection IDs and durations. If a selected rover disconnects, its inspector remains available even when it no longer matches the Active filter.

Latest position shows the most recently reported coordinates, their age, and a map when valid coordinates are available. It is a last reported location, not a continuous live track. If no position was reported, the page says so. A connection can transfer corrections without supplying a position.

The inspector also includes recent events for that rover. Use Copy connection link to share the exact selected connection with another person who has access to the account. Copy session link opens the base session without selecting a rover.

Review events

Select Events to see the base and rover connection events together, with the newest event times first. Entries can include Connected, Session started, Session ended, and Disconnected, with a reason when one was reported. Times in the detail page and charts are shown in UTC; the list uses your browser's local date and time format.

Use the event time and connection identity to narrow down an interruption. Select a rover connection in the timeline to inspect it.

Use Load more events if the page indicates that more entries are available. Event history begins when diagnostics collection starts; the absence of older entries does not establish that nothing happened.

Understand live updates and status

An open detail page normally checks for updates about every five seconds. Charts refresh about every fifteen seconds. Updates pause when the browser tab is hidden and resume when you return. After the base and its rover connections have finished and the remaining data has loaded, the page stops regular polling.

The update indicator tells you when the page last received data. The refresh button lets you request an update immediately. If a request fails, the page keeps the previously loaded data, displays an error, and retries with increasing delays. You can also select Try again.

Active means the connection has not been recorded as ended. It does not guarantee that corrections are flowing. Status stale means a recent status report is missing; with the current default, reports older than 20 seconds are stale. No status yet means no status report is available. Check the last reported time and traffic observations alongside the connection state.

Ended is a normal lifecycle state, not an error classification. Use the reported reason and surrounding events to understand how it ended. These diagnostics describe connections and data transfer; they do not establish a rover's RTK fix or positioning accuracy.

History retention

Completed sessions are retained for 30 days after their end time. Active sessions remain available even if they started more than 30 days ago. A base session may remain longer when an associated rover connection is still active or is still within its retention period.

Traffic observations use a rolling 30-day retention window. When a session is removed, its associated events and positions are removed too. Extending retention does not restore records that were already deleted.

Investigate a connection issue

1. Open the mount point's Session history and find the source connection covering the time you want to investigate.
2. Open the session and compare its connection state with the last status and observed traffic.
3. Select the affected rover. Check its connection ID, duration, received bytes, and position age if available.
4. Review Events around the interruption. Compare adjacent base sessions if the source reconnected.
5. Copy the session or connection link when asking a teammate to investigate the same record.

For a quick view of current connections, start with the Dashboard. For mount point and client configuration, see Casters.