> For the complete documentation index, see [llms.txt](https://help.sbtinstruments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sbtinstruments.com/technical-documentation/hardware/bactobox-r-configuration.md).

# BactoBox® configuration

BactoBox® comes with a factory-defined *configuration*. A configuration is a set of default settings. It covers [About gating](/technical-documentation/gating/about-gating.md) and result presentation.

Configuration is independent of the [hardware version](/technical-documentation/hardware/bactobox-r-hardware-changelog.md) and [software version](/software/bactobox-r-software-changelog.md).

## Current configurations

Nowadays, there is a single BactoBox® configuration: BB14 (aka "Customizable"). We recommend BB14 for all new users.

{% hint style="info" %}
The configuration name matches the item number used to purchase BactoBox®.
{% endhint %}

## Legacy configurations

<table><thead><tr><th width="181">Configuration</th><th width="165">Also known as</th><th>Notes</th></tr></thead><tbody><tr><td>BB12</td><td>EasyCount</td><td><strong>No longer available.</strong></td></tr><tr><td>BB05</td><td>Original</td><td><strong>No longer available.</strong><br>For adopters of an early version of BactoBox®.</td></tr></tbody></table>

## Configuration-defined defaults

These are *defaults*. You can sometimes override them.

Example: you can select a different [CRS file](/software/file-formats/crs-file.md).

<table><thead><tr><th width="142">Configuration</th><th width="186">Gating (CRS file)</th><th width="161">Limit of detection</th><th>Presentation</th></tr></thead><tbody><tr><td>BB14<br><mark style="color:$info;">Customizable</mark></td><td><a href="/technical-documentation/gating/bactotal-10.md"><em>BacTotal_v2024-<strong>10</strong></em></a><br><mark style="color:$info;">You can change this.</mark></td><td>core2b-latest<br><mark style="color:$info;">30 000–5 000 000/mL</mark><br></td><td>sbt2_v2025-01<br><mark style="color:$info;">Example: "total/mL"</mark></td></tr><tr><td>BB12<br><mark style="color:$info;">EasyCount</mark><br><strong>No longer available</strong></td><td><a href="/technical-documentation/gating/bactotal-10.md"><em>BacTotal_v2024-<strong>10</strong></em></a><br><mark style="color:$info;">You cannot change this.</mark></td><td>core2b-latest<br><mark style="color:$info;">30 000–5 000 000/mL</mark></td><td>sbt2_v2025-01<br><mark style="color:$info;">Example: "total/mL"</mark></td></tr><tr><td>BB05<br><mark style="color:$info;">Original</mark><br><strong>No longer available</strong></td><td><em>BacTotal_v2024-<strong>02</strong></em><br><mark style="color:$info;">You can change this.</mark></td><td>sbt1-latest<br><mark style="color:$info;">5 000–5 000 000/mL</mark></td><td>sbt1_v2022-03<br><mark style="color:$info;">Example: "total particles/mL"</mark></td></tr></tbody></table>


---

# 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.sbtinstruments.com/technical-documentation/hardware/bactobox-r-configuration.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.