Brewblox release 2020/12/02

Announcements Releases
1

Relevant links:

Brewblox release 2020/12/02

firmware release date: 2020/11/02

We added three new widgets this release, and changed the default settings of the kettle PID in some wizards.

Wrong Td value generated by wizards
The HERMS wizard, RIMS wizard, and Brew Kettle wizard set Td to 5 minutes, which is a value that does not work well. It was a mistake in the software. For PIDs that control a heating element in a kettle, 10s is a better value for Td. Please check your settings to see if you have the incorrect value.

The Web Frame widget is a wrapper around the HTML iframe element.

The Quick Values widget lets you set multiple buttons and sliders for a single field to easily toggle between multiple settings without having to enter a new value.

The Spark Sim Display is built for simulation services. It will render the Spark LCD screen on your dashboard. For technical reasons, this widget is only available for simulation services.

For more information (and screenshots), see the Widgets page.

We updated the default settings for some PIDs in HERMS, RIMS, and Brew Kettle wizards.
If you’re still using the default settings after running one of these wizards, you may want to apply the new settings manually:

  • Brew Kettle
    • Kettle PID
      • Ti: 10m
      • Td: 10s
  • HERMS
    • HLT PID
      • Td: 10s
    • BK PID
      • Ti: 10m
      • Td: 10s
  • RIMS:
    • Kettle PID
      • Td: 10s

Windows recently released Terminal. This comes with a built-in ssh command, which functions like ssh on Linux/Mac. To keep instructions consistent, we now recommend Terminal in our install guide, but PuTTY/Git Bash still work just fine.

Changes

  • (feature) Added Web Frame widget.
  • (feature) Added Quick Values widget.
  • (feature) Added Spark Sim Display widget.
  • (feature) Added brewblox-ctl add-node-red command.
  • (docs) The startup guide now recommends Windows Terminal.
  • (improve) Block changes are now published immediately to other clients.
  • (improve) The Quick Actions editor now shows a warning if Block was not found.
  • (improve) Updated PID default settings for PIDs in HERMS, RIMS, and Brew Kettle wizards.
  • (fix) Increased Spark command timeout to handle wifi channel switches.
  • (fix) Datastore writes no longer fail if the eventbus is not connected.
  • (fix) The Spark Device Info widget is now visible again on the service page.
  • (fix) Widgets no longer respond to arrow keys when dashboard is not editable.
  • (fix) Dashboards no longer show a scroll bar if the contents fit on screen.
  • (fix) Added help text for brewblox-ctl add-plaato command.
3 Likes
2

Hi Bob,

what are the default settings for the HERM-MT PID:
now I have: Ti: 5m and Td: 10m

Is this correct?

cheers,
Douwe

3

Yes, these are the default settings.

For reference, default settings for various PIDs now are:

(If not specified, Kp is based on calculations in the wizard)

Brew Kettle

  • Ti: 10m
  • Td: 10s

Ferment

  • Beer cool
    • Kp: -50 1/degC
    • Ti: 6h
    • Td: 30m
  • Fridge cool
    • Kp: -20 1/degC
    • Ti: 2h
    • Td: 10m
  • Beer heat
    • Kp: 100 1/degC
    • Ti: 6h
    • Td: 30m
  • Fridge heat
    • Kp: 20 1/degC
    • Ti: 2h
    • Td: 10m

Glycol

  • Cool
    • Kp: -20 1/degC
    • Ti: 2h
    • Td: 10m
  • Heat
    • Kp: 100 1/degC
    • Ti: 2h
    • Td: 10m
  • Glycol control (optional)
    • Kp: -20 1/degC
    • Ti: 2h
    • Td: 5m

HERMS

  • HLT
    • Ti: 10m
    • Td: 10s
  • MT
    • Ti: 5m
    • Td: 10m
  • BK
    • Ti: 10m
    • Td: 10s

RIMS

  • Kettle:
    • Kp: 10 1/degC
    • Ti: 5m
    • Td: 10s
  • Tube:
    • Kp: 30 1/degC
    • Ti: 2m
    • Td: 10s
1 Like
4

Love the Web Frame widget. Could we get a setting to scale the content? Looks like this can be done with CSS:

2020-12-03_10-58-38

    <!DOCTYPE html>

<html lang="en" xmlns="http://www.w3.org/1999/xhtml">
<head>
    <meta charset="utf-8" />
    <title></title>
</head>
<style>
    .wrap {
    width: 400px;
    height: 205px;
    padding: 0;
    overflow: hidden;
}
.frameScaled {
    --scale: 0.5;
    width: 800px;  /* wdith =  wrap width / scale   */
    height: 410px;  /* height =  wrap height / scale   */
    border: 0;
    -ms-transform: scale(var(--scale));
    -moz-transform: scale(var(--scale));
    -o-transform: scale(var(--scale));
    -webkit-transform: scale(var(--scale));
    transform: scale(var(--scale));
    
    -ms-transform-origin: 0 0;
    -moz-transform-origin: 0 0;
    -o-transform-origin: 0 0;
    -webkit-transform-origin: 0 0;
    transform-origin: 0 0;
}
.frame {
    width: 400px;
    height: 205px;
    border: 0;
}

</style>
<body>
    <div>Scaled</div>
    <div class="wrap">
        <iframe class="frameScaled" src="http://tiltpi:1880/ui/"></iframe>
    </div>
    <div>Unscaled</div>
    <div class="wrap">
        <iframe class="frame" src="http://tiltpi:1880/ui/"></iframe>
    </div>

</body>
</html>
5

Scaling is on the backlog. Auto-resizing the frame to match parent took priority for a first implementation.

1 Like
6

Yeah, that’s a pain and obviously I didn’t attempt to mess with it in my example.

7

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.