> 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.11/vehicle-spy-tutorials/tutorial-how-to-run-multiple-devices-in-one-vs3-file/part-2-adding-devices.md).

# Part 2 - Adding Devices

### 1. Select devices:

Once Selected Devices is checked, click on the "**Select Devices**" button.

### 2. Ascending serial numbers:

Inside of the Selected Hardware Setup popup, verify "**Select hardware using ascending serial numbers**"(Figure 1

:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smOne.gif)) is checked before the next step. The Ascending serial number option works best for this application and is a simple way to predict what device is being referenced. It also allows the ability to swap the hardware without changing the entire setup. As an example: A serial sumber starting with CY comes alphebetically before a serial number starting with GS, so a FIRE will always be before Gigastar.

### 3. Add names:

Type in a friendly name (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smTwo.gif)) for the device and then click **Add** (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smThree.gif)**)**. The name could be anything to help identify which device is being utilized in the setup. This can be done for however many devices are being worked with. Serial numbers do not need to be added to the entries. Once the devices have been added, click OK and then OK again to exit out of the options menu.

![Figure 1: Type a friendly name and then Add the device.](https://2673726158-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdYdvinhoJh0IN6rV8uo3%2Fuploads%2FhE1fP1iib1syJguIiVK4%2Fdevices.gif?alt=media\&token=8fec1e92-034e-44a6-9b7c-0f6fddf9d39c)


---

# 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.11/vehicle-spy-tutorials/tutorial-how-to-run-multiple-devices-in-one-vs3-file/part-2-adding-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.