> 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/3.9.13/vehicle-spy-tutorials/tutorial-simple-standalone-logging/part-3-channels.md).

# Part 3 - Channels

### Channels Tab

The channels tab is where what to log is selected. The **Search** box (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smOne.gif)) gives a quick way to find the signals of interest. The information that is searched through comes from the applied platform and receive table. If the goal is to log everything, this step can be skipped.

Search results will be displayed in the **Results** box (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smTwo.gif)). Double clicking on a result will add it to the **Selected Channels for Test** list (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smThree.gif)). Remember that the channels can be normal bus traffic, diagnostic information, CCP/XCP, or data from receive messages defined in the receive table of the messages editor. Vehicle Spy will figure out how to get that data.

![Figure 1: Channel Selection tab](https://content.gitbook.com/content/jb1RvXgxzxcqgZdVpbGb/blobs/p2kTYiMy1z8s9JVqFEKm/tutorialss3.gif)

For this simple example, the channels tab will only be used to select the channels to capture. Channels tab is also used to configure how diagnostics are requested, polling rates, decimation, export order, and other parameters. For more information see the help topic for the [Channels table of VehicleScape DAQ](/vspy-3-documentation/3.9.13/vehicle-spy-main-menus/main-menu-measurement/vehiclescape-daq/vehiclescape-daq-channels-tab.md).


---

# 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.intrepidcs.com/vspy-3-documentation/3.9.13/vehicle-spy-tutorials/tutorial-simple-standalone-logging/part-3-channels.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.