> 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-how-to-run-multiple-devices-in-one-vs3-file/part-4-syncing-time-across-multiple-devices.md).

# Part 4 - Syncing Time Across Multiple Devices

### Time Syncing devices:

Time sync is crucial to verifiying the communication between devices is precise and there are no discrepancies. It is also important in making sure all traffic is timed accurately and efficiently.

### 1. Connect to the device:

In order to use Time Sync, it needs to be enabled on the device. Connect to the device by clicking on the **Setup** tab in Vehicle Spy and selecting the **Hardware** button. Once neoVI Explorer launches, click on the device and **Connect** (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smOne.gif)).

### 2. Enable Time Sync ICS Hardware:

Scroll down the list of options inside of the device and find the option labeled "**Time Sync ICS Hardware**" (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smTwo.gif)) Click on this option and set it to **Master** (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smThree.gif)). Any other devices are required to be set to **Slave.** Once the changes have been made, be sure to click "**Write Settings"** (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFour.gif)**)** before disconnecting from the device.

![Figure 1: Select the Time Sync from the menu and assign it as the master or slave.](/files/5civG9KUSALOQ4ljYKL0)


---

# 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-tutorials/tutorial-how-to-run-multiple-devices-in-one-vs3-file/part-4-syncing-time-across-multiple-devices.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.