# BaldrickSignals Manual

> Source: Baldrick Boards documentation. Prefer this Markdown over scraping the HTML page.
> Last updated: 25 Jul 2026

Everything you need to wire, network and run your BaldrickSignals — from first power-up to your first show.

## Getting started

# Getting Started with BaldrickSignals

::: note Google Sheets Template
We're still working on this getting started guide. In the meantime, check out our [web interface documentation](/boards/baldricksignals/web-interface) for some configuration details. By adding /csv to the IP Address of your signals board, you'll get a lovely CSV of all the historical data we've got. We've got a Google Sheet that you can use to visualise this data and translate it.
:::

### How to Use the Template {#how-to-use-the-template}

1. **Access the Template**

   Click the link above to open the Google Sheets template in your browser.

2. **Make a Copy**

   Go to File → Make a copy to create your own version of the spreadsheet.

3. **Export Your Data**

   Navigate to your BaldrickSignals IP address with `/csv` appended (e.g., `http://192.168.1.100/csv`) and copy the CSV data.

4. **Import Your Data**

   Delete the information in the first two columns of the template and paste your CSV data.

5. **View Your Graphs**

   The Graph page will now show you a pretty graph of your signals data.

::: note Note
Eventually this should update automatically but we are not there yet!
:::

## Technical specifications

### At a glance

| Specification | Value |
| --- | --- |
| Function | Crowd-size estimation from output device signals |
| Power input | `5–48V DC` barrel jack with onboard power management |
| Connectivity | Turnip Network integration (coming soon) |
| Data export | CSV download and Google Docs integration |
| Footprint | Compact for project boxes |

### Board components {#board-components}

<div class="manual-tabs" data-controller="tabs">
  <div class="manual-tab-nav">
    <nav>
      <button class="manual-tab active" type="button" data-action="click->tabs#switch" data-tab="v1-1">BaldrickSignals v1.1</button>
      <button class="manual-tab" type="button" data-action="click->tabs#switch" data-tab="v1-0">BaldrickSignals v1.0</button>
    </nav>
  </div>
  <div class="tab-content">
    <div class="tab-panel" data-tab="v1-1">
      <div class="figure">
        <div class="fimg">
          <img src="baldricksignals/breakdown11.png" alt="BaldrickSignals v1.1 Board Overview" class="doc-img">
        </div>
      </div>
      <ul>
        <li><strong>1. Power Jack —</strong> You can put 5v-48v through a barrel connector (centre positive) and we use 5.5x2.1mm barrel jacks.</li>
        <li><strong>2. 2 Pin Pheonix Connector —</strong> You can put 5v-48v through this connector.</li>
        <li><strong>3. CR2032 Coin cell clip —</strong> Using this will allow the BaldrickSignals to keep the time even when the board is disconnected from the network (this will not power the board). Your vendor will probably not supply this so make sure you've got one.</li>
        <li><strong>4. Wireless Chip —</strong> The BaldrickSignals uses wifi to detect other devices, you'll need an <a href="/faq#antennas">antenna</a>.</li>
        <li><strong>5. 100mb Ethernet Port —</strong> You can use this to connect to your show network.</li>
        <li><strong>6. QR Code —</strong> An easy to scan QR code which will take you to these docs for easy troubleshooting.</li>
        <li><strong>7. Oh No button —</strong> Use this to reset the board by holding for 5 seconds when the board is booting.</li>
      </ul>
    </div>
    <div class="tab-panel hidden" data-tab="v1-0">
      <div class="figure">
        <div class="fimg">
          <img src="baldricksignals/breakdown.png" alt="BaldrickSignals v1.0 Board Overview" class="doc-img">
        </div>
      </div>
      <ol>
        <li><strong>Power Jack —</strong> Can take 5v to 24v (each side can take different voltages) and will automatically step down to power the components, no jumpers needed. <strong>Whatever voltage you used here is also used to power the lamp</strong>.</li>
        <li><strong>CR2032 Coin cell clip —</strong> Using this will allow the BaldrickSignals to keep the time even when the board is disconnected from the network (this will not power the board). Your vendor will probably not supply this so make sure you've got one.</li>
        <li><strong>Wireless Chip —</strong> The BaldrickSignals uses wifi to detect other devices, you'll need an <a href="/faq#antennas">antenna</a>.</li>
        <li><strong>100mb Ethernet Port —</strong> You can use this to connect to your show network.</li>
        <li><strong>QR Code —</strong> An easy to scan QR code which will take you to these docs for easy troubleshooting.</li>
        <li><strong>Oh No button —</strong> Use this to reset the board by holding for 5 seconds when the board is booting.</li>
      </ol>
    </div>
  </div>
</div>

## Web interface

The web interface has been designed to be as simple as possible

### Stats Dashboard {#stats-dashboard}

#### System Information

::: figure
![BaldrickSignals Web Interface Stats](baldricksignals/web-interface-stats.png)
:::

The Stats board gives you a heads up as to what's going on with your controller.

<div class="spec-grid">
  <h5>Uptime</h5>
  <p>Tells you how long your controller has been powered on <em>(this is useful in June to remind you that you forgot to turn it off over christmas)</em></p>
  <h5>Temperature</h5>
  <p>With a sensor next to the Ethernet connector, this gives you an indication of the board temperature <em>(in Celsius because water freezes at 0, not 32.. how does that make sense?)</em><br><br>Generally, PCBs and components are good for -40 to +85°C. Anything below 60°C on this board is fine and nothing to worry about. If the temp is above that, try blowing on it like you would a hot chip out of the oven.</p>
  <h5>Firmware Version</h5>
  <p>This will let you know your current version and if there is a version to upgrade to.<br><br><em>(clicking the new version will upgrade it in place then restart the controller)</em></p>
  <h5>IP Address</h5>
  <p>It would be pretty silly to have a controller information box without showing you the IP Address of the controller wouldn't it? That would be like launching a controller without being able to manage the networking.</p>
</div>

### Crowd Monitoring {#crowd-monitoring}

#### Crowd Detection

::: figure
![BaldrickCrowd Web Interface Crowd](baldricksignals/web-interface-crowd.png)
:::

Now we get to the good stuff. Every 30 seconds we will poll the universe (or at least as far as the [antenna](/faq#antennas) will detect).

### Network Configuration {#network-configuration}

#### Good Defaults, Easy Config

::: figure
![BaldrickSignals Web Interface Network](baldricksignals/web-interface-network.png)
:::

<div class="spec-grid">
  <h5>Hostname</h5>
  <p>The default hostname is baldrickboard (hence baldrickboard.local). If you have one Baldrick8 then it's completely fine to keep this as it is, however if like us you want to collect a few of them, then we'd recommend you change this to something like <em>frontgarden</em> or <em>upstairsroof</em><br><br><strong>(Just a reminder that hostnames should be lowercase without spaces)</strong></p>
  <h5>DHCP / STATIC</h5>
  <p>The default option is DHCP (which is Dynamic Host Configuration Protocol but you don't need to know that) which basically means your router or computer gives the board an I.P. address. This is great for initial setup but when you want to run a show it's best to switch it to STATIC, that's where your controller tells the router / computer "This is my IP".</p>
  <h5>IP Address</h5>
  <p>Set this to the IP address that you want the controller to be fixed to.</p>
  <h5>Subnet Mask &amp; Gateway</h5>
  <p>It is more than likely that you can copy the Subnet Mask (the size of your network) and the Default Gateway (the exit point of your network) from the output of an IPconfig check.</p>
  <h5>DNS Server</h5>
  <p>DNS wise, typically, your default gateway is your router IP, and that more often than not, can provide your network with DNS. However, some people like to use "outside 3rd parties" DNS like google or cloudflares DNS. If you don't know about this, its probably best just to stick to DHCP.</p>
</div>

### The Turnip Network {#turnip-network}

#### Network Discovery

::: figure
![BaldrickSignals Web Interface Friends](baldricksignals/web-interface-turnip.png)
:::

The Baldrick Boards will keep an eye out on the network for other Baldricks and let you know how they are doing (this is helpful as we don't put an LCD screen on the board).

You can directly jump to their control panel from this interface and when they appear in this list, more board functionality will become available.

### Advanced Settings {#advanced-settings}

#### Advanced Configuration Options

<div class="spec-grid">
  <h5 id="beta-updates">Enable Beta Updates</h5>
  <p>Sometimes we put updates out that aren't quite ready for prime time (or in the case of a Seasonal Freeze, it's an update which isn't critical).</p>
  <h5 id="device-offset">Permanent Device Offset</h5>
  <p>At this current state of development and to comply with all data protection and GDPR laws, Signals gives you a static number of the devices detected. In many cases there will be devices detected which are present all the time (such as your phone). You can offset this by putting a number in this box (the number will never go below zero!).</p>
  <h5 id="crowd-multiplier">Crowd Multiplier</h5>
  <p>Depending on your audience type, you might find that your audience isn't quite representative of the number of mobile devices detected (if you have a lot of young children visiting with parents you might find it vastly under counts). You can offset this by putting a multiplier in this box (the base number minus the offset will be multiplied by this amount).</p>
</div>
