Updating meshO firmware

Step by step, with meshO Manager: meshO Prime over USB, then every meshO Control over the air through Prime. Nothing to open up, and no cables to the Controls.

Download firmware 4.0.0

1. Before you start

You will need:

  • The computer that runs meshO Manager, on the latest version. Manager offers its own updates; there’s a download on the downloads page if you don’t have it.
  • meshO Prime and its USB cable. Prime is updated over USB, and it then sends the update to every Control.
  • The Controls, switched on and charged, near Prime. They update over the mesh, so they need to be on the network — a table or the charging case in the same room is ideal.
  • The firmware files for your units, from the downloads page. Section 2 says which.
  • No live event. The Devices page is only available while no event in Manager is live.

Allow a few minutes for Prime, and about four minutes per Control: the update goes to one Control at a time, and each one restarts and rejoins the network in about a minute afterwards. A case of 20 Controls is a job for an evening before the event, not the morning of it.

How the update gets to each unit

There are three steps, and the second one is done only once:

  1. Update Prime over USB, with the Prime file.
  2. Stage the Control file on Prime — load it onto Prime, once. Prime keeps it, even when it’s switched off.
  3. Send it to the Controls. Prime sends the staged file over the air, to one Control or to many in a batch. You can do some Controls today and the rest at a later session, without staging the file again.

meshO Manager

On your computer

meshO Prime

Staged
Control 4.0.0

Kept when switched off

  • Control 21Updated
  • Control 22Updated
  • Control 23Updating…
  • Control 24Next
  • More ControlsLater on
Prime is updated over USB. The Control file is staged on Prime once, and Prime then sends it to Controls one at a time — a few now, the rest at a later session — without staging it again.

Update Prime first, then the Controls. Controls on 4.0.0 send punches in a new format that an older Prime drops, so a Control should never be newer than the Prime it reports to. Updating Prime also clears any Control firmware already loaded onto it (section 7), so doing Prime first saves loading it twice.

2. Which file for which unit

meshO Prime has a single file. meshO Control has two, because there are two generations of Control circuit board: PCB v4 and PCB v6 (and later). A file only installs on the boards it was built for — a Control with the wrong file refuses it and keeps running what it had.

UnitBoardFile
meshO PrimeEvery PrimemeshO Prime v4.0.0 PCBv4.bin · 87 KB
meshO ControlPCB v6 and latermeshO Control v4.0.0 PCBv6+.bin · 110 KB
meshO ControlPCB v4meshO Control v4.0.0 PCBv4.bin · 111 KB

The Prime file is named PCBv4 because it runs on PCB v4 and every Prime board since. You don’t need to check which board a Prime has.

3. Finding a Control’s PCB version

There are three ways to tell. Whichever you use, write down the serial numbers of any PCB v4 Controls: the Firmware view in Manager lists Controls by serial number but doesn’t show their board, and you’ll need the list in section 10.

By how it switches on

  • PCB v4: switches on with a swipe of the magnet on the left-hand side.
  • PCB v6 or later: switches on when the magnet is held still on the right-hand side for 5 seconds.

On the circuit board

The version is printed on the board in white — v4 or v6 — beside the mounting screw next to the battery connector. The lid is clear, so you can read it through the lid without opening the Control.

Close-up photo inside a meshO Control: the green circuit board with v6 printed in white beside a mounting screw and a white two-pin connector, circled.
The version mark on a PCB v6 board (circled), beside the screw by the battery connector. Photographed with the lid off; it reads the same through the clear lid.

In meshO Manager

Only PCB v6 and later boards can be powered off remotely, so Manager offers Power off… only for those. Open the Devices page (section 4), stay on Manage, and click the ⋮ at the end of a Control’s row:

  • Power off… at the bottom of the menu: PCB v6 or later.
  • The menu ends at Deep sleep…: PCB v4.

A Control that hasn’t reported its board yet also has no Power off…, so if a Control you expected to be v6 shows none, give it a minute on the network and look again, or check the board through the lid.

The Manage view of the meshO devices page with the menu open on Control 21. The menu lists Identify, Pause listening to radio punches, TX power, Disable auto-standby, Start radio diagnostics, Stop radio diagnostics, Calibrate battery offset, Deep sleep and, in red at the bottom, Power off.
PCB v6: the menu for Control 21 ends with Power off….
The same Manage view with the menu open on Control 4. The menu ends at Deep sleep; there is no Power off item.
PCB v4: the menu for Control 4 ends at Deep sleep…, with no Power off….

Controls were only ever made on PCB v4 and on v6 and later. If a board says anything else, get in touch before updating it.

4. Open the Devices page

  1. Plug meshO Prime into the computer running Manager with its USB cable, and switch Prime on.
  2. Switch on the Controls you’re updating, close to Prime, and give them a minute to join the network.
  3. In Manager, go to the list of events. Make sure no event is live.
  4. Click the meshO Radios button at the top right.

If there’s no meshO Radios button, turn on Use meshO Prime for radio punches in Manager’s settings, or check that no event is live.

The top right of the meshO Manager events list: a row of icons, with the first one, a radio tower, highlighted and a tooltip under it reading meshO Radios.
The meshO Radios button on the events list.

The page opens as meshO devices. Until Prime is found it says Searching for meshO Prime; there’s no port to choose, so if it stays like this, check the cable and that Prime is switched on.

The meshO devices page with no Prime connected: a radio tower icon, Searching for meshO Prime, and Plug a meshO Prime into this computer over USB. A Searching chip is at the top right.
Waiting for Prime.

Once Prime is found the chip at the top right turns green and says Connected, and every unit on the network is listed: Prime first, then each Control as it reports in.

The Manage view of the meshO devices page, Connected. The table lists Prime serial 1 on firmware v3.2.0, Controls 4 and 7 on v3.3.3, and Controls 21 to 24 on v3.2.4, each with radio address, battery between 88 and 99 percent, Listening Active, TX power Full and Auto-standby On.
The Manage view: Prime and six Controls.

5. Check what each unit is running

Switch from Manage to Firmware at the top. The card at the top is Prime, with its firmware version; the table lists every Control with its version, and an Update Control… button that stays greyed out until there is Control firmware on Prime to send.

The Firmware view. The Prime card reads Serial 1, Firmware v3.2.0 (bank 0), with an Update Prime button; under Staged image it reads Nothing staged, with a Stage new image button. The table below lists Controls 4 and 7 on v3.3.3 (bank 0) and Controls 21 to 24 on v3.2.4 (bank 0), each with a greyed-out Update Control button.
Before the update: Prime on 3.2.0, Controls on 3.3.3 and 3.2.4.

The bank after each version is which of the unit’s two firmware slots it is running from. An update goes into the other slot and the unit switches over, so the bank number changes with each update. The previous firmware stays in the old slot: if the new one doesn’t start up properly, the unit goes back to it by itself.

6. Update meshO Prime

  1. On the Prime card, click Update Prime….
  2. Choose meshO Prime v4.0.0 PCBv4.bin.
  3. Leave Prime plugged in while the progress bar fills. The dialog can’t be closed during this part.
  4. Prime checks the file, restarts and reconnects by itself. When the dialog says Prime updated, click Done.
The Updating Prime dialog: meshO Prime v4.0.0 PCBv4.bin, 87.4 KB. Streaming firmware to Prime over USB. A progress bar at 241 of 597 chunks, 40 percent.
Sending the file to Prime over USB.
The Prime updated dialog: meshO Prime is now running the new firmware. New firmware: v4.0.0. A Done button.
Prime is done.

The Prime card should now show v4.0.0. Check it: the dialog reports success as soon as Prime reconnects, so this line is what confirms Prime is actually running the new version.

The Firmware view after the update. The Prime card reads Firmware v4.0.0 (bank 1). Nothing is staged, and the Controls are still on v3.3.3 and v3.2.4.
Prime on 4.0.0, now running from bank 1. The Controls are next.

If you choose a Control file here by mistake, Manager stops before anything is sent and Prime is left as it was:

The Updating Prime dialog with the file meshO Control v4.0.0 PCBv6+.bin and a red error: Firmware is for Control, but Prime firmware is required. A Close button.
The wrong file for Prime. Close it and choose the Prime file.

7. Load the Control firmware onto Prime

Controls are updated by Prime, so their firmware is loaded onto Prime first. Manager calls this staging. Prime holds one Control file at a time, so start with the file for most of your Controls — usually PCBv6+ — and do the other board type afterwards.

  1. Under Staged image, click Stage new image….
  2. Choose meshO Control v4.0.0 PCBv6+.bin (or meshO Control v4.0.0 PCBv4.bin if you’re doing your PCB v4 Controls).
  3. Wait for Image staged, then click Done.
The Staging firmware dialog: meshO Control v4.0.0 PCBv6+.bin, 110.3 KB. Streaming firmware image to Prime for staging. A progress bar at about 68 percent.
Loading the Control file onto Prime.
The Image staged dialog: Firmware successfully staged on meshO Prime. The firmware can now be deployed to devices on the network. New firmware: v4.0.0. A Done button.
The file is on Prime.

The Prime card now shows the staged file — Control, v4.0.0, its size and a green Valid — and every Update Control… button lights up.

The Firmware view with a staged image: a Control chip, v4.0.0, 110.3 KB, CRC 639F4D5B and a green Valid chip. The Update Control buttons on every row are now active.
Ready to send. The size tells the two Control files apart: 110 KB for PCBv6+, 111 KB for PCBv4.

Stage it once, use it as often as you like

You only stage a Control file once. It stays on Prime — when Prime is unplugged, switched off, or put away until next month — and every Update Control… from then on sends that same file. Update the Controls on the table now, and any that were flat or missing at your next session, straight from section 8.

Stage again only to change files (the other board type, section 10), or after updating Prime, which clears it. The Prime card always shows what’s staged.

8. Update one Control

With the file staged, check the Prime card shows it, then update Controls as often as you need — no need to stage it again. Try one Control on its own first. It shows the whole process, and confirms the Controls can hear Prime before you start on the rest.

  1. Click Update Control… on the row of a Control with the right board for the staged file.
  2. Check the version and the serial number, and click Start update.
  3. Prime sends the firmware over the mesh; the progress bar shows how far it has got.
  4. The Control checks the firmware, switches to it and restarts. It drops off the list for a moment and comes back about a minute later.
  5. When it reports the new version the dialog says Control … updated. Click Done.
The Update Control 21 dialog: Prime will push the staged firmware image (v4.0.0) to Control 21 over the mesh. A note: The push may take a few minutes. Once the new firmware is received, the Control will restart and take a short time to come back online. Cancel and Start update buttons.
Confirm the version and the serial.
The Updating Control 21 dialog: Pushing firmware to the Control over the mesh, with a progress bar.
Prime sending the firmware to Control 21.
The Updating Control 21 dialog with a spinner: Control received the image and is verifying, swapping banks, and rebooting. It will reappear on the mesh in about a minute. A Close button.
Control 21 restarting onto the new firmware. You can close this; the update carries on.
The Control 21 updated dialog: meshO Control 21 is now running the new firmware. New firmware: v4.0.0. A Done button.
Control 21 is back, on 4.0.0.

9. Update several Controls at once

  1. Tick the box at the start of each Control’s row — only Controls with the board the staged file is for.
  2. In the bar that appears, click Update firmware…, then Start updates.
  3. Prime updates them one after another. Leave Prime plugged in and the page open until the run finishes; Stop after current ends the run once the Control in progress is done.
  4. When it says Bulk firmware update complete, click Done.
The Firmware view with Controls 22, 23 and 24 ticked. A bar above the table reads 3 devices selected, with Clear and Update firmware buttons. Control 21 now shows v4.0.0 (bank 1).
Three PCB v6 Controls selected. Controls 4 and 7 are PCB v4, so they’re left for the other file.
The Update firmware on 3 devices dialog: Prime will push the staged firmware image (v4.0.0) to each selected device over the mesh, one at a time. A note: The full run may take several minutes per device. Cancel and Start updates buttons.
Confirm the run.
The Updating firmware on 3 devices dialog: 1 of 3 done. Control 22 Pushed (v4.0.0), Control 23 at 60 percent, Control 24 Queued. A Stop after current button.
One at a time: Control 22 done, 23 in progress, 24 waiting.
The Bulk firmware update complete dialog: 3 pushed. Controls 22, 23 and 24 each Pushed (v4.0.0). A Done button.
All three sent.

Pushed means the Control received the firmware; it then restarts onto it. Give the last one a minute, then check that every Control shows v4.0.0 in the table. A Control that failed stays ticked when you click Done, so you can try just those again.

10. The second board type

If you have both kinds of Control, repeat sections 7 to 9 with the other file: stage meshO Control v4.0.0 PCBv4.bin, then update the PCB v4 Controls on the list you wrote down.

The Firmware view with the PCBv4 file staged: Control, v4.0.0, 111.3 KB, CRC 5CCB9D88, Valid. Controls 21 to 24 are on v4.0.0 (bank 1); Controls 4 and 7 are still on v3.3.3 (bank 0).
The PCBv4 file staged (111 KB). Controls 4 and 7 are the ones left.
The Firmware view with every Control, 4, 7 and 21 to 24, on v4.0.0 (bank 1), and Prime on v4.0.0 (bank 1).
Finished: Prime and every Control on 4.0.0.

Manager doesn’t know which board each Control has, so it will let you send a file to the wrong one. Nothing breaks if you do: the Control refuses a file that isn’t for its board before it changes anything, and keeps running its old firmware. In Manager it looks like an update that never finishes — after three minutes the dialog says the Control has not come back on the mesh with the new firmware, and its version in the table doesn’t change. Stage the other file and try that Control again.

11. If something goes wrong

The page says Searching for meshO Prime
Prime isn’t connected. Check the USB cable and that Prime is on; it’s found automatically.
A Control isn’t in the list
It isn’t on the network. Check it’s switched on and charged, and move it closer to Prime.
Update Control… stays greyed out
There’s no valid Control file staged on Prime, or another update is still running. Stage the file (section 7) and wait for any run in progress to finish.
“Firmware is for Control, but Prime firmware is required”
A Control file was chosen for Update Prime…. Choose meshO Prime v4.0.0 PCBv4.bin.
“This is a Prime firmware image. Use “Update Prime” instead.”
The Prime file was chosen for Stage new image…. Stage a Control file instead.
“Invalid firmware file.”
The file isn’t meshO firmware, or the download is incomplete. Download it again; the checksums are on the downloads page.
“PCB v… outside image range”
Prime’s board isn’t one this file is for. Nothing was changed; get in touch.
A Control “has not come back on the mesh with the new firmware”
If its version in the table hasn’t changed after a couple of minutes, it most likely has the other board type: stage the other file and try again. If it has dropped off the list, it may be slow to restart, out of range or flat.
Prime was unplugged or the computer slept during an update
Plug Prime back in, open the Devices page and check the version on the Prime card. If it shows the old version, update again. Prime keeps its previous firmware until the new one is safely in place.
A unit went back to its old version
If new firmware doesn’t start up properly, the unit returns to its previous firmware by itself, and the version and bank go back to what they were. Try the update once more; if it happens again, let us know the unit and serial number.
A PCB v4 Control on firmware older than 3.3.0
It can’t take the PCBv4 file over the air. Get in touch and we’ll sort it out.

For anything else, email sales@mesho.live with the unit’s serial number and what Manager showed. What’s new in 4.0.0 →