> 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-introduction/vehicle-spy-overview.md). # Vehicle Spy Overview ### The Automotive Electronics Engineering Tool for Networked Vehicles. Vehicle Spy is a world class engineering tool for designing, testing, and analyzing networked vehicles of today and tomorrow. Electronics in the Vehicle has grown to an unprecedented level of complexity, from a handful of computers just a decade ago to literally dozens of computers situated in an in-vehicle computer network. Further increasing complexity is the inclusion of multiple networks including main networks, sub-networks, and multimedia networks with gateways in between them. This newfound complexity makes development and verification of vehicle electronics systems a difficult challenge. Vehicle Spy tackles this challenge head on with a focus on ease-of-use and user productivity. Vehicle Spy software contains many tools to help users access information quickly. ### Examples of Ways to Use Vehicle Spy * **Bus Analyzer** - simultaneously monitor all network message transmissions. * **Flight Recorder** - automatically capture bus events and store buffer files. * **Node Simulator** - simulate missing nodes, gateways, or entire vehicles. * **Flash/Diagnostics Tool** - flash ECU software, read/write memory locations, or read trouble codes. ### Simultaneous, Multi-Protocol Support CAN (dual and single wire), Ford SCP, Ford UBP, GM CGI, GME CIM SCL K-line, GMLAN, ISO9141, J1708, J1850 PWM, J1850 VPW (GM Class 2 & Chrysler 1 byte header), J1857, J1939, Keyword 2000, LIN, LSFT CAN, and UART. [**Introduction**](/vspy-3-documentation/vehicle-spy-introduction.md) **- Overview -** [**Applications Tour**](/vspy-3-documentation/vehicle-spy-introduction/vehicle-spy-overview/vehicle-spy-tour/vehicle-spy-tour-1-bus-monitor.md) **-** [**Users**](/vspy-3-documentation/vehicle-spy-introduction/other-vehicle-spy-users.md) **-** [**Specification**](/vspy-3-documentation/vehicle-spy-introduction/vehicle-spy-specifications.md)**-**[**Required Hardware**](/vspy-3-documentation/vehicle-spy-introduction/vehicle-spy-required-hardware-pc-system-requirements.md) **-** [**Website**](https://intrepidcs.com/products/software/vehicle-spy/) --- # 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-introduction/vehicle-spy-overview.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.