> 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-tutorials/tutorial-sort-messages-by-ecu.md).

# Tutorial: Sort Messages by ECU

### Overview

Vehicle networks are made up of many different ECUs. Sometimes, it is useful to record the data from a single ECU and then play it back through Vehicle Spy at a later time. This task can be accomplished by using function blocks and individual buffers for single or multiple ECUs.\
\
This tutorial will show how to record buffers from single modules and play them back in any combination.\
\
To achieve this goal, Tutorial 4 will guide you through the steps listed below.

1. Enter ECU message filters in Messages Editor
2. Create filtered Capture function blocks to sort incoming messages by ECU
3. Separate incoming messages by ECU
4. Setup trigger messages for Playback function blocks
5. Create Playback function blocks for each ECU
6. Create Script function blocks to trigger Playback blocks
7. Create a Graphical Panel
8. Run newly created application


---

# 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:

```
GET https://docs.intrepidcs.com/vspy-3-documentation/vehicle-spy-tutorials/tutorial-sort-messages-by-ecu.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
