> For the complete documentation index, see [llms.txt](https://docs.optitrack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.optitrack.com/motive-ui-panes/status-panel.md).

# Status Panel

The status panel lists the system parameters for monitoring the live status of system operations. Click on the displayed status at the bottom right corner of Motive, and the Status Panel pops up. You can drag and place the Status Panel anywhere.

## Status Panel

![Status Panel in Motive.](https://content.gitbook.com/content/WkNF2QVM5V7MzRdzoXmL/blobs/uL5CrHaszFvi9CQGUy95/image.png)

#### **Residual**

Average of [residual](/motive/reconstruction-and-2d-mode.md) values of all or selected live-reconstructed 3D points. This is available only in [Live mode](/motive/data-recording.md#live-mode-and-edit-mode) or in [2D Mode](/motive/reconstruction-and-2d-mode.md#2d-mode).

#### **Data**

Current incoming data transfer rate (KB/s) for all attached cameras.

#### **Point Cloud**

Measured latency of the point cloud reconstruction engine.

#### **Assets**

Measured latency of the Rigid Body solver and the Skeleton solver combined.

#### **Software**

Measured software latency. It represents the amount of time it takes Motive to process each frame of captured data. This includes the time taken for reconstructing the 2D data into 3D data, labeling and modeling the trackable assets, displaying in the viewport, and other processes configured in Motive.

#### **System**

**Available only on Ethernet Camera systems (Prime series and Slim 13E).** Measured total system latency. This is the time measured from the middle of the camera exposures to when Motive has fully solved all tracking data.

#### **Streaming**

The data rate at which the tracking data is streamed to connected client applications.

#### **Final Rate**

Final data acquisition rate of the system.

#### **Cameras**

**Available only on Ethernet Camera systems (Prime series or Slim 13E).** Average temperature, in Celsius, on the imager boards of the cameras in the system.

## Status Panel: Latency

When there is an [increased latency](https://docs.optitrack.com/developer-tools/natnet-sdk/latency-measurements#latency-details) on the processing pipeline that needs attention, it appearsa highlighted in purple. Increased processing latency can result in dropped frames when real-time processing the data in live-captures or in 2D Mode. Increased latency usually occurs because of the CPU not being fast enough to process the data in real time. If you perform post-processing reconstructions, you will be accessing the recorded 3D data or solved data (Rigid Bodies), and there will be no processing required for the corresponding pipeline, and the bodies will show as Inactive.

![Increased Point Cloud latency and skeleton solver latency. Increase in skeleton solve latency is due to the Point Cloud engine slowing down.](https://content.gitbook.com/content/WkNF2QVM5V7MzRdzoXmL/blobs/1xVUFnXTR4iGoQa6zN2W/image.png) ![Point cloud is inactive when accessing already reconstructed 3D data.](https://content.gitbook.com/content/WkNF2QVM5V7MzRdzoXmL/blobs/Fbp8NdmVKxxUqFc5kTJ4/image.png)

#### **Real-Time Point Cloud Latency**

With large camera systems, the Point Cloud engine can experience increased latency from the amount of data it needs to handle in real time. If the increased latency causes frame drops or affecting the tracking quality, you can exclude selected cameras from contributing to the real-time reconstruction. In the [Devices pane](/motive-ui-panes/devices-pane.md), reveal the Reconstruction setting from the header context menu, and disable this setting for the cameras that you wish to process later. 2D frames captured by these cameras will be recorded in the TAK, but they will not contribute to real-time reconstruction. This reduces the amount of data to be processed in real time, and you can still utilize the 2D frames using post-processing reconstruction pipeline.

![](https://content.gitbook.com/content/WkNF2QVM5V7MzRdzoXmL/blobs/4Yf6A1DvmRriu2opMOvN/image.png)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.optitrack.com/motive-ui-panes/status-panel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.