# BBO setup

The following settings must be defined in all the BBO units connected to BBO Buffer.

1. DHCP must be enabled.
2. POST Client URL must be set.
3. NTP server address must be set.

Use BBO web interface to set the parameters.

## Enable DHCP <a href="#enable-dhcp" id="enable-dhcp"></a>

1. Go to “WEB Setup” and select “Enable DHCP”.
2. Click “Save”. The BBO will reboot. Please note it may have different IP after this step.

The BBO Buffer has DHCP server enabled that assigns IP addresses to devices on LAN ports (ports 2 to 5) in the range from 192.168.11.2 to 192.168.11.254. The BBO Buffer LAN IP is 192.168.11.1.

## BBO POST Client Configuration <a href="#bbo-post-client-configuration" id="bbo-post-client-configuration"></a>

All the BBOs working via a BBO Buffer must have the same URL set in their BBO POST Client Configuration.

1. Go to “POST Client Setup”.
2. Enter standard BBO login credentials – user: admin, password: icu.
3. For a default port of 54000 the URL shall be set to:\
   <http://192.168.11.1:54000/Receiver/BBO>\
   \
   If different port is defined in the config.txt file on BBO Buffer SD card, the URL to set is:\
   [http://192.168.11.1:*port*/Receiver/BBO](https://github.com/bask-icu/SG001-0003-BBOB/blob/master/quick_installation/http:/192.168.11.1:port/Receiver/BBO/README.md)
4. Click “Save”.

## BBO SNTP Configuration <a href="#bbo-sntp-configuration" id="bbo-sntp-configuration"></a>

All the BBOs working via a BBO Buffer must have the same SNTP Configuration with BBO Buffer selected as their SNTP server.

1. Go to System Configuration -> Network Time.
2. Enter 192.168.11.1 as a server and 0 (zero) as a time zone offset.

![](https://1482390586-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FegpnAPlZcRY7vPT5SNXz%2Fuploads%2Fgit-blob-37902a5bc71a37067a2d38088ac5f5ecb8a838ad%2Fimage4.png?alt=media)

3. Click “Save”.

## BBO versions support <a href="#bbo-versions-support" id="bbo-versions-support"></a>

### BBO below v.2.11 (no NTP) <a href="#bbo-below-v-2-11-no-ntp" id="bbo-below-v-2-11-no-ntp"></a>

The BBO Buffer shall not be used with old BBO models (firmware below v.2.11) which do not have real time clock which is synchronised from NTP server.

The GUI view for version below 2.11 (no NTP)

![](https://1482390586-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FegpnAPlZcRY7vPT5SNXz%2Fuploads%2Fgit-blob-438b0d9d521910fb9aeee238bfca7f2047a3197d%2Fimage5.png?alt=media)

These units send the readings with no time stamp (example below).

![](https://1482390586-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FegpnAPlZcRY7vPT5SNXz%2Fuploads%2Fgit-blob-33a5988632c0bae8f397e4f01177ac8ffe6ebc86%2Fimage6.png?alt=media)

If these frames are stored in BBOB when the B3 is not accessible, then later they are stored in B3 with the time stamp being the delivery time which can be almost the same for many frames and is different from the real measurement time.

### BBO v.2.11 and higher (with NTP) <a href="#bbo-v-2-11-and-higher-with-ntp" id="bbo-v-2-11-and-higher-with-ntp"></a>

![](https://1482390586-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FegpnAPlZcRY7vPT5SNXz%2Fuploads%2Fgit-blob-c72e33b5a75a25e4f9c63419d98bfb9d9a079ed9%2Fimage7.png?alt=media)

The frames sent by the BBO units with RTC contain the measurement time stamp (example below) which is then used by B3 as the measurement time, so the data are then stored and interpreted correctly.

![](https://1482390586-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FegpnAPlZcRY7vPT5SNXz%2Fuploads%2Fgit-blob-77661ead715520ce82135789bb4fca3884900a46%2Fimage8.png?alt=media)


---

# Agent Instructions: 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:

```
GET https://help.boomerang3.com/bbo-buffer-installation-manual/quick_installation/bbo_setup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
