> 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/bbo-gateway-installation-manual/introduction/example-of-infrastructure.md).

# Example of infrastructure

A BBO is a 1-Wire to Ethernet bridge.

An example infrastructure using BBO units may look as shown below:

![](https://1398263718-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe49zOmJ9qgXRcOoMVIir%2Fuploads%2FRk9NavfCJZ2iFXsto7AE%2F0.png?alt=media)

The measurements are read using the 1-Wire connections with the sensors and/or interfaces.

Then they are sent in XML format via a POST at port 80. The server needs to acknowledge the received POST by sending a POSTBack reply confirming the reception. The server can also send commands to the gateway, such as to change the transmission intervals for sensors.

Note that the server can only do this immediately after the gateway has sent its POST to the server, so changing a parameter may take some time before it is implemented on the gateway side.

ICU Scandinavia offers the BBO family elements described in detail in [BBO gateways](/bbo-gateway-installation-manual/bbo-gateways.md).


---

# 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/bbo-gateway-installation-manual/introduction/example-of-infrastructure.md?ask=<question>&goal=<user_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.