> 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.17/vehicle-spy-main-menus/main-menu-embedded-tools/bitsmash.md).

# BitSmash

The [Embedded Tools](/vspy-3-documentation/3.9.17/vehicle-spy-main-menus/main-menu-embedded-tools.md) -> BitSmash is a hardware mode that can "smash" or corrupt received CAN frames. This feature can be useful for testing how an ECU or network reacts to specific bad CAN frames due to precise control down to the bit level.\
\
In general, hardware is setup with BitSmash to wait for a period of time for a certain CAN frame and then smash bits in that frame after it is received.\
\
BitSmash requires Intrepid hardware with CAN/CAN FD support. Please note that this feature is currently not supported on neoVI FIRE 3 and neoVI RED2; however, a future update will include support for these devices. The CAN controller of the hardware is disabled while in BitSmash mode. As a result, the hardware can only smash received frames; it can not smash one of its own transmit frames. This also means either a second device or a special CAN bridging cable is needed if you want to monitor the CAN bus during the smash event.\
\
Setting up BitSmash requires going online with hardware that supports it then using the dialog shown in Figure 1.

![Figure 1: Use the BitSmash dialog after taking Vehicle Spy online with ICS hardware.](/files/wz6LFPA7ghtgk2QgQu6m)

**Select Device**\
Selects a connected device to run in BitSmash mode.\
\
**Number of bits to wait** (1-157)\
Selects the first bit to "smash" starting after the ArbID of the RAW CAN frame.\
\
**Number of bits to drive** (1-157)\
Selects the total number of bits to "smash".\
\
**Number of CAN frames** (1-254)\
Sets the total number of CAN frames to "smash".\
\
**Timeout (ms)**\
Number of milliseconds to wait to receive the specified CAN frame. Normal hardware operation resumes after this timeout expires.\
\
**ArbId**\
The arbitration identifier of the CAN frame to "smash".\
\
**Network**\
Selects the CAN network on the hardware that will get the BitSmash.\
\
**Extended 29 bit**\
Sets the ArbID as 29 bit when checked or 11 bit if unchecked.\
\
**Remote**\
When checked, remote frames are targeted.\
\
**Send BitSmash button**\
This button does NOT transmit a smashed CAN frame! Clicking this button just sends the BitSmash setup up to the selected device. The device will stay in BitSmash mode until the correct CAN ArbID is received and smashed or until the timeout expires.


---

# 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:

```
GET https://docs.intrepidcs.com/vspy-3-documentation/3.9.17/vehicle-spy-main-menus/main-menu-embedded-tools/bitsmash.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.