> 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/cg1018-relay-box-installation-manual/installation/config-file/practical_examples/standard_b2_or_rqs.md).

# B2/Coolguard

In this example we want to use the normal (single) URL used in both B2 and Coolguard (RQS), and we want it to behave like older versions of the Relay Box. That gives us the following scenario:

* CH1 shall control a sensor-alarm from server
* CH2 shall control a communication-alarm from server
* No Communication/Network failure signalling

## Operation mode

To achieve this the URL must be created in the server and the relevant alarm groups connected to it. 

Depending on the monitoring system type correct operation mode must be selected as described in [Operation modes](/cg1018-relay-box-installation-manual/installation/config-file/url__3_different_modes.md).

## Channels logic configuration

In the config file, only the URL has to be set to point to the server with the correct user ID.


---

# 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/cg1018-relay-box-installation-manual/installation/config-file/practical_examples/standard_b2_or_rqs.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.