> 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/vehiclescape-daq/vehiclescape-daq-pc-logging-tab.md).

# VehicleScape DAQ: PC Logging Tab

PC Logging in [VehicleScape DAQ](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/vehiclescape-daq.md) is very similar to the [Logging](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/logging.md) feature for collecting signals while connected to ICS hardware. One difference is that PC Logging provides control over the signal polling rates by using the [Channels Tab](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/vehiclescape-daq/vehiclescape-daq-channels-tab.md) or [Online Tab](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/vehiclescape-daq/vehiclescape-daq-online-tab.md). Another is that PC Logging can be controlled with a [Function Block](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-scripting-and-automation/function-blocks.md) script.

The PC Logging Tab (Figure 1) determines log file parameters, when to start and stop logging, and how to handle invalid signals. The interface is almost identical to that of the [Logging](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/logging.md) view, with a couple of exceptions:

* **Single shot diagnostics:** When enabled (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smOne.gif)), the DAQ will use GMLAN one shot (mode $AA/01) DPID requests instead of periodic (mode $AA/02-04).
* **Start Manually:** When selected, the DAQ must be started manually or by using a function block script [DAQ Action](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-scripting-and-automation/function-blocks/function-blocks-types/script-type-function-block-commands/script-type-function-block-command-daq-action.md) command.

![Figure 1: The VehicleScape DAQ PC Logging tab..](/files/xjxiKQSj0FRJIAe8Y978)


---

# 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/vehicle-spy-main-menus/main-menu-measurement/vehiclescape-daq/vehiclescape-daq-pc-logging-tab.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.