# BactoBox® software changelog

We continuously improve the software for your BactoBox®.

{% content-ref url="/pages/ju8GX0Rmv7wK1yVatiFr" %}
[Update BactoBox® software](/protocols/best-practices/update-bactobox-r-software.md)
{% endcontent-ref %}

See what changed in each software version in the [list below](#changes).

## Legend

Some changelog entries have icons. The table below describes what each icon means.

<table><thead><tr><th width="100">Icon</th><th>Description</th></tr></thead><tbody><tr><td>💻</td><td><a href="/pages/WLqOGbtauoHPqvximyYA">Access</a> user interface</td></tr><tr><td>📟</td><td><a href="/pages/teQIZyIIfT8ZyHW8IdpA">Dash</a> user interface</td></tr><tr><td>🧰</td><td>Workshop mode only<br><mark style="color:$info;">Intended for internal use during operations and development within SBT.</mark></td></tr><tr><td>⚗️</td><td><a href="/pages/XsZORjBfNNbuImdEvEy5">Experimental</a><br><mark style="color:$info;">We may change or remove this feature at any point in time.</mark></td></tr></tbody></table>

## Changes

{% updates format="full" %}
{% update date="2026-04-15" %}

## v2026.02a

**Changed**

* Allow HTTP API connections from any origin via CORS. In practice, this allows all third party connections to BactoBox®.

**Fixed**

* Fix a very rare data corruption bug. We tracked this bug internally as wal-db-corruption.
  {% endupdate %}

{% update date="2026-03-09" %}

## v2026.02

**Added**

* 💻⚗️ Add experimental "growth-curve" measurement group. This includes richer growth analytics, CIZE views, and computed HPI metadata in tables and plots.
* 💻 Add more column filters for the measurement and measurement group tables.
* 💻🧰 Add workshop-only "shipping-qc" measurement group.
* Store additional program settings in the PEDB. This makes it easier to troubleshoot when a program misbehaves.

**Changed**

* 💻 Rework the "Support" page entirely. The overall workflow is the same but the implementation behind it is now consistent with the other pages.

**Fixed**

* Fix "Database is locked" when connecting to BactoBox via USB while a program runs. Behind the scenes, the PEDB now uses a WAL.
  {% endupdate %}

{% update date="2026-01-14" %}

## v2026.01

**Added**

* 💻 Add automatic clock synchronization when connected to Access.
* 💻 Add "Measurements" page to Access. Allows you to view and annotate measurements.
* 💻 Add "Measurement group" page to Access. Allows you to create measurement groups and add/remove measurements to them. It also features a plots of the growth curve and CFU correlation.
* 💻 Add MSEC buttons to Access (Measure, Stop, Empty, Clean). Allows you to start/stop programs directly through Access.
* 💻 Add progress bar to Access that shows the outline/outcome of the current program (if any).
* 💻🧰⚗️ Add experimental "SBT Lab" page to Access with live stream of the demodulated signal (from the lock-in amplifier).
* 💻 Add "System info" overview to the top right of Access.
* 💻 Add link to help center for error codes that we show in Access' bottom bar.
* Add PEDB file to the DDB. Makes it easier to troubleshoot (especially now that we have data annotations).

**Changed**

* Change "ml" (millilitre) to "mL" throughout.
* 💻 Rename "Measurements" to "Summary" in Access
* 💻 Rename "Summary" to "Download summary" in Access
* 💻 Hide scroll bars when they are unnecessary in Access

**Fixed**

* 📟 Fix dash entering in a pending state when start execution fails
* Fix snapshot creating a corrupted zip file when biome does not respond.
* Fix issue where fields such as "Software version" were missing data (inside the PEDB's outcome column).
* 💻 Fix overflow/wrap in Access for low screen sizes
  {% endupdate %}

{% update date="2025-11-17" %}

## v2025.10b

**Changed**

* 📟 Replace "blank diluent" for "Dilution vial" in QC test.

**Fixed**

* Fix "Execution error: \[Errno 111] Connection refused" when the end user presses Measure. This was due to an issue with corrupt/missing starred.json file.
* Always persist changes to .crs.json files and starred.json files when the user presses *Save*. This avoids an issue where the user presses *Save*, flips the rocker switch shortly after, and ends up with a corrupt/missing starred.json file.
  {% endupdate %}

{% update date="2025-10-15" %}

## v2025.10

**Added**

* Deep clean program has two options: 15 minutes and 10 hours.
* 📟 Add 2 steps to the QC test guide screen: 'Clean' and 'Measure on blank diluent'
* 📟 Add 'Set target concentration' screen right before entering in the QC test guide screen.
* Add 50XX error codes related to the blank liquid validation.
* Add liquid info to the extended troubleshooting bundle.

**Changed**

* Replace 'See troubleshooting guide' text in error messages to 'Further instructions: help.sbtinstruments.com'.
* 📟 Disable empty program by default. It is only enabled when the 'There is liquid in the system modal' appears.
* 📟 Change confusing text in the 'Ready' home screen. Now it just displays Ready.
* Remove flush program
* Replace the flush modal for the deep clean modal. It is triggered by 1 week since the last deep clean of any length.
* Merge the 40XX errors to the new error system implemented in bebop
* Replace Clean the system/flow system for Clean the setup to keep it consistent with the help center.
* Change rinse duration in deep clean from 20 to 25 seconds and reduce the soak duration from 20 to 15 seconds.
* Change the QC test durability cost to 0. This includes the Measure on blank diluent step.
* Replace system for setup in all the different flow directives.
  {% endupdate %}

{% update date="2025-09-17" %}

## v2025.09a

{% endupdate %}
{% endupdates %}


---

# 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.sbtinstruments.com/encyclopedia/software/bactobox-r-software-changelog.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.
