> 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-online-tab.md). # VehicleScape DAQ: Online Tab The Online tab is where all of the configuration work and settings in [VehicleScape DAQ](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/vehiclescape-daq/vehiclescape-daq-online-tab.md) come together for [PC Logging](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/vehiclescape-daq/vehiclescape-daq-pc-logging-tab.md). Switching from other VehicleScape DAQ tabs to this one will automatically take Vehicle Spy [online](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-run.md). Depending on the selected settings, logging may or may not automatically commence as well. A sample of the Online tab with logging active can be seen in Figure 1. The interface is mostly divided into a left half for signals and a right half for diagnostics. Main logging control is provided through a button at the top left, with additional controls found near the bottom right of the tab. ![Figure 1: The VehicleScape DAQ Online Tab.](/files/NTz9HcTEMTnGYPRbm2MZ) ### Log / Stop Logging The button at the top left of the screen (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smOne.gif)) allows logging to be turned on or off, changing from **Log** (with a green start icon) to **Stop Logging** (with a red stop sign) depending on current logging status. Logging can also be toggled on or off by pressing the **F2** key. The time that logging begins depends on the setting of the **Start Logging** parameter under [PC Logging](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/vehiclescape-daq/vehiclescape-daq-pc-logging-tab.md). If it is set to **Start Automatically**, then logging will begin as soon as Vehicle Spy goes online (including when the Online Tab is clicked.) If the setting is **Start Manually**, logging must be initiated using the **Log** button; for **Start on Equation**, logging will begin when the equation evaluates to **True**. ### Signals List The left half of the screen (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smTwo.gif)) shows a real-time display of signals that were selected for the DAQ project under the [Channels Tab](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/vehiclescape-daq/vehiclescape-daq-channels-tab.md). This area continues to update even while logging is disabled, making it similar to the [Signal List](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/signal-views/signal-list.md) view. PID and MEP [A2L file data item](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/mep-xcp-ccp-memory-edit-protocol/mep-setup.md#a2l-file-data-item-tree-refer-to-figure-1) priorities can be changed to **High**, **Medium** or **Low** simply by double-clicking on them. The [right-click menu used in the Channels Tab](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/vehiclescape-daq/vehiclescape-daq-channels-tab.md) is accessible here as well, providing a number of convenient options. ### Diagnostic Tweaker This side of the screen (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smThree.gif)) shows diagnostic information that VehicleScape DAQ is automatically requesting for you. The Diagnostic Tweaker window shows the diagnostic setup and results of diagnostic requests to the specific ECUs for VehicleScapeDAQ. The Tweaker is defaulted to enabled. The Tweaker window can be disabled by right clicking in the Tweaker window and unchecking the selection. To re-enable it, right click in the Tweaker window and re-check the Diagnostic Tweaker option. ### Additional Controls Below the Diagnostic Tweaker are a few additional controls: * **(Re)start Button:** Manually starts or restarts the entire DAQ job, including logging (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFour.gif)). * **Stop Button:** Manually stops the DAQ job, including logging (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFive.gif)). * **DTC Code Request Rate:** Specifies how often fault code requests are sent (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smSix.gif)). * **Mask... Button:** Use this button (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smSeven.gif)) to open a dialog box that will allow you to view and change DTC status mask bits (Figure 2). ![Figure 2: DTC Status Mask dialog box.](/files/fT2twZvHqMYMIiAmc5Lp) --- # 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-online-tab.md?ask=&goal= ``` `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.