> 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/url__3_different_modes/single-b2-and-coolguard.md).

# Single (B2 and Coolguard)

To set the CG1018 to operate with B2 or Coolguard (RQS) server in SINGLE mode define:

**URL\_MAC=0** and **URL\_DUAL=0**

The settings shown below set **SINGLE** mode and define server at IP address equal to **81.91.10.237**.&#x20;

The alarms signaled by the unit are selected basing on the ID at the end of SERVICE\_URL line which is ICU\_MANKAN\_INTERNAL\_TEST\_CGNS\_GW in the example.&#x20;

{% code overflow="wrap" %}

```sh
# B2 or RQS (only reads temperature-alarms of two URL's)
#URL_DUAL=0 -> Uses the SERVICE_URL to get status from server (older behaviour of Blixtljus where a single URL controls both relays)
#URL_DUAL=1 -> Uses the two URL's SERVICE_URL_CH1 and SERVICE_URL_CH2 to control the two relay outputs individually, only temperature-alarms (ie. 1x) from URL will control the outputs (server's communication alarm status is ignored).
URL_DUAL=0
SERVICE_URL_CH1="http://81.91.10.237/strobelight.aspx?User=HUS_CH1"
SERVICE_URL_CH2="http://81.91.10.237/strobelight.aspx?User=HUS_CH2"


# B2 or RQS (old standard URL)
#Use either URL_MAC or URL_DUAL solution (above), OR, SERVICE_URL (don't try to use both)
#SERVICE_URL="http://81.91.10.237/strobelight.aspx?User=HUS_CH1"
#SERVICE_URL="http://192.168.61.156/rasp.html"
SERVICE_URL="http://www.rqs.se/bl/?id=ICU_MANKAN_INTERNAL_TEST_CGNS_GW"
```

{% endcode %}

Sensor alarms control CH1, and communication alarms control CH2.

The URL for Coolguard (RQS) in the example looks like this:

```sh
SERVICE_URL="http://www.rqs.se/bl/?id=ICU_MANKAN_INTERNAL_TEST_CGNS_GW"
```


---

# 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/url__3_different_modes/single-b2-and-coolguard.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.
