> For the complete documentation index, see [llms.txt](https://irseeker.buildingblockrobotics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://irseeker.buildingblockrobotics.com/board-overview/board-feature-switches.md).

# Board Feature Switches

### Version 2:

The latest version update of the sensor uses the following switches:

#### Spike Mode: DIP Switch 1

DIP Switch 1 ON - This will allow the sensor to work with SPIKE Prime.

<div align="left"><img src="/files/HcfRUqdNldhf9QoO03JH" alt=""></div>

DIP Switch 1 OFF - This will allow the sensor to work with EV3 Labview, Arduino or other platforms.

<div align="left"><img src="/files/zOEAPButLZ2vG4WUJdis" alt=""></div>

#### Advanced Mode: DIP Switch 2

If DIP Switch 1 is enabled and DIP Switch 2, the sensor will appear as a Spike Colour Sensor where the reflected light can be used for the direction and the raw red value of the sensor can be used for the signal strength.

<div align="left"><img src="/files/WmG11dVORr84Hw6rJ5BG" alt=""></div>

If DIP Switch 1 is enabled and DIP Switch 2 is off, the sensor will appear as a Spike Distance Sensor where the distance value is used for the direction. No signal strength is available in this mode outside of the hardware setting (DIP 3).

<div align="left"><img src="/files/gqncwtSu1Ylw7pBL12y2" alt=""></div>

#### Hardware Signal Strength: DIP Switch 3

DIP Switch 3 used with DIP Switch 1 will only return a value to the Spike if the ball is within half a field distance. This can be used to build a defender style robot that only attacks when the ball is close to the robot.

<div align="left"><img src="/files/2XVwFnd3ujG8JMpwkRDH" alt=""></div>

{% hint style="info" %}
The following information relates to Version 1 of our IR seeker. If you are unsure which version you have please contact us at <info@buildingblockrobotics.com> and we can provide the correct firmware files.
{% endhint %}

### Version 1: Spike Prime Distance Sensor Mode

To use the IR Seeker as a Spike Prime distance sensor, move the switches to the following position:

1 - On, 2 - Off - 3 - Off

![](/files/IKO3vIXUg4CCbZPP0kxM)

### Advanced Mode - Including EV3 Labview

In order to receive both the ball direction and ball strength from the sensor, the switches should be moved to the following position:

1 - Off, 2 - On, 3 - Off

![](/files/cMNErknEN7wCL6kOZSZs)

This position should be used for Arduino development. More information can be found here

{% content-ref url="/pages/ZCRYs4Afuih1Wn1zVvt2" %}
[Advanced (Arduino)](/guides/advanced-arduino.md)
{% endcontent-ref %}

### Defender Mode

In order to use the Spike as a Distance sensor, but with reduced visibility we can move the switches to the following position:

1 - On, 2 - Off, 3 - On

![](/files/vEMvLEoMoRkV50BzRVW6)

This will operate the same as the standard mode, however the sensor will only report the direction when the ball is within roughly half a field radius (around 50cm).&#x20;


---

# 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://irseeker.buildingblockrobotics.com/board-overview/board-feature-switches.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.