> 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/previous-boards/version-1.md).
# Version 1
Our version 1 board uses different firmware version to provide advanced functionality.
### Firmware Links
[Standard Version](https://s3.amazonaws.com/www.buildingblockrobotics.com/firmware/Standard-v1-11.uf2)
The standard mode of the IR Seeker supports the following configurations:
* EV3 (EV3G - Via our custom blocks)
* EV3 Python
* Micro:Bit (via Adapter)
* I2C - Via EV3 Port or Grove style connector
* Spike Prime (Distance Sensor)
[Standard Version (Defender)](https://s3.amazonaws.com/www.buildingblockrobotics.com/firmware/Defender-v1-11.uf2)
The defender mode of the IR Seeker supports the following configurations with half the field visibility of the standard firmware.
* EV3 (EV3G - Via our custom blocks)
* EV3 Python
* Micro:Bit (via Adapter)
* I2C - Via EV3 Port or Grove style connector
* Spike Prime (Distance Sensor)
[Advanced Version](https://s3.amazonaws.com/www.buildingblockrobotics.com/firmware/Advanced-v1-11.uf2)
This mode can only be used from Spike Python, the sensor will no longer show up as a distance sensor. This mode will return both the direction and signal strength.
* EV3 (EV3G - Via our custom blocks)
* EV3 Python
* EV3 (Classroom - Distance Sensor)
* Micro:Bit (via Adapter)
* Spike Prime Python ONLY
### Do I have a version 1 board?
The version 1 IR Seeker has a single expansion port as shown in the image below.
### Detailed View
---
# 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/previous-boards/version-1.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.