> For the complete documentation index, see [llms.txt](https://docs.intrepidcs.com/vspy-3-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intrepidcs.com/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/graphical-panels/graphical-panels-tools/graphical-panel-controls-message-history.md).

# Graphical Panel Controls: Message History

This control allows you to review the messages received by Vehicle Spy, essentially embedding a [Messages View](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/messages-view.md) window within a graphical panel. Message filters can be applied within the control so that only messages of interest are shown.

![Figure 1: An example Message History control.](https://3170208387-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL6lcovCpkhoS9uTOFtEp%2Fuploads%2FVzcR0RTQ4Q8IT8Iz20yq%2FgpctrlMessageHistory.gif?alt=media\&token=106c5b65-b89b-4d15-a9c0-1b6c1a395f9a)

Table 1 lists the properties specific to the Message History control. A list of common properties can be found under [Common Control Properties](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/graphical-panels/graphical-panels-tools/graphical-panel-controls-common-control-properties.md).

**Table 1: Message History Control Properties**

| Property     | Function and Options                                                                                                                                                                                                                                          |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| UpdateRate   | Specifies how often to update the message display, in milliseconds (default is 100 ms).                                                                                                                                                                       |
| Scrolling    | <p>Determines whether or not messages are shown in scroll mode:</p><ul><li><strong>0-No:</strong> Messages are displayed in static mode.</li><li><strong>1-Yes:</strong> Messages are displayed in scroll mode.</li></ul>                                     |
| MonitorSetup | Launches the [Setup Filter](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/messages-view/messages-view-filter-bar/messages-view-custom-filters.md) dialog box, where you can enter a filter to manage what is displayed in this control. |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.intrepidcs.com/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/graphical-panels/graphical-panels-tools/graphical-panel-controls-message-history.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.