> 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-network-interface-hardware/vehicle-network-interface-hardware-rad-a2b.md).

# Vehicle Network Interface Hardware: RAD-A2B

#### Automotive Audio Bus and Network Monitoring Solution

Intrepid has partnered with Analog Devices to create a state-of-the art A2B (Automotive Audio Bus®) testing tool. A2B technology allows a two-Wire interface to transmit audio and control data using a multi-source audio system. This technology enables low cost transmission of audio, active noise cancellation and in-vehicle voice recognition from any part of the vehicle.

RAD-A2B combines Analog Devices’ A2B technology with two CAN/CAN-FD transceivers and one LIN channel to allow mixed network messages in one time stamped log. The RAD-A2B tool includes one channel for A2B receive-only monitoring and one channel that can act as an emulator node.

The A2B tool works in harmony with the Intrepid Controls world renowned Vehicle Spy application. In Vehicle Spy, you can view A2B live data, control frames, I²C data, real-time audio meters for visual reference, and the ability to capture streams. When used as an emulator node, full A2B node simulation including downstream flashing is allowed (available with future update).

<figure><img src="/files/X5tae37XlvOtJQDw0tKN" alt=""><figcaption><p>RAD-A2B device</p></figcaption></figure>

User Guide for RAD-A2B - <https://cdn.intrepidcs.net/guides/RAD-A2B/>


---

# 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-network-interface-hardware/vehicle-network-interface-hardware-rad-a2b.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.
