> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/s2-radio-system-manual/s2-system-description/s2-pt100-pt1000-interface/connectors.md).
# Connectors
The interface is mounted inside an enclosure identical with S2 node enclosure.
There is a sensor port RJ45 socket on one side of the box. Connect the interface with S2 node with PT100 firmware using S2 - PT100 cable P/N RD003 connected to the S2 node sensor socket. The cable provides both the data connection and supply from the S2 node.
A round opening with a rubber grommet on the other side of the box is used to insert sensor cables into the enclosure.
S2 node with PT100 interface
S2 node with PT100 interface in DBU002/2 holder
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.boomerang3.com/s2-radio-system-manual/s2-system-description/s2-pt100-pt1000-interface/connectors.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
