Skip to content

Spiral Engineering — Firmware Upgrade

Overview

The Spiral Engineering app updates the firmware in Keilton+autani devices over the air (OTA), through Bluetooth. New firmware adds features or fixes. If your sensors are working properly, you do not need to install the latest firmware: new builds are rarely critical to daily operation unless we notify you.

There are two update methods:

  • Single-device OTA updates one device at a time, in about 90 seconds per device.
  • Mesh OTA updates every device of one firmware type in a single pass, in 20-30 minutes. Even a few devices take at least 20 minutes.

Choosing the right method saves the most time, so read Choose your method before you start.

Admin required · iOS only

Spiral Engineering runs on iPhone with iOS 12.0 or later, and it needs management privilege for the zone. See the Spiral Engineering — Overview for how to install the app and gain access.

Quick Reference

Item Value
Single-device OTA About 90 sec per device
Mesh OTA 20-30 min per pass, depending on device count
Rule of thumb Fewer than 20 devices of one firmware type: single-device OTA. 20 or more: Mesh OTA
One Mesh OTA pass covers One firmware type, in one mesh network
Signal booster coverage Stay within the 4-hop limit per booster area
Progress at 98% Normal. Wait at least 10 min before treating it as a stall

Before you start

  • Update the app. Install Spiral Engineering and update it to the latest version before each site visit.
  • Bring the right tools. Bring signal boosters, plus the RP0, RP1, and FL30. Bring a charged power bank for every booster, and keep booster antennas upright and unobstructed.
  • Practice first. Run a few updates in the office so you know what each screen and situation looks like before you work on a jobsite.

Firmware and tool compatibility

The RP1 works with devices on firmware build 230907 or later. The RP1 and FL30 together, with improved mesh performance, need build 250328 or later. Check each device's Current Build on the Light Upgrade screen.

The Light Upgrade screen

Open the app and tap Light Upgrade. Devices are grouped by firmware type; tap the arrow beside a firmware type to expand its device list. The screen has four parts:

Part What it shows
"Not Added" / "Added" tabs Not Added shows devices still in the factory-setting network. Added shows the network you are working in. Scan a network's QR code to switch networks.
Firmware type header Model is the firmware type (0xAA-BB). New Build is the latest firmware (YYMMDD). Total is the number of devices found; Upgraded is the number already current. The round blue button starts a Mesh OTA for this firmware type.
Device row The device Name (for example A1, A2), Current Build, New Build, and RSSI signal strength. Ignore Version, which is for internal use. The round orange button updates this one device; the checkbox adds it to a batch.
Bottom bar All selects every device whose Current Build does not match its New Build. Upgrade runs a single-device OTA on each selected device, one after another.

Choose your method

Estimated total time to update one firmware type:

Devices Single-device OTA Mesh OTA
1 90 sec 20-30 min
6 about 9 min 20-30 min
12 about 18 min 20-30 min
20 about 30 min 20-30 min
50 about 75 min 20-30 min

The faster method is in bold. Single-device time adds about 90 seconds for each device. Mesh OTA takes 20-30 minutes, depending on device count.

  • Choose single-device OTA when fewer than 20 devices of one firmware type need the update, or when several firmware types each have only a few devices pending.
  • Choose Mesh OTA when 20 or more devices of the same firmware type need the update.

Single-device OTA

The app connects directly to one device and updates it. Signal boosters are not needed.

  1. Stand near the device and keep the phone still.
  2. Tap the orange button on that device's row.
  3. Wait about 90 seconds until the update completes. The device reboots and the app reconnects to it.
  4. Check that the device's Current Build now matches its New Build.

If the app loses the connection, the update fails. Move closer to the device and start again.

Updating several devices

Check each device's box, or tap All, then tap Upgrade. The app updates the selected devices one after another automatically.

Mesh OTA

A Mesh OTA updates a whole group at once. The app updates one nearby device first, then that device broadcasts the firmware and the other devices relay it.

Every device in one pass must meet these conditions:

  • Same mesh network. All devices must be in the factory-setting network, or all in one commissioned zone.
  • Same firmware type. One pass covers one firmware type (0xAA-BB), not one model number. Products with the same model number can use different firmware types. Check under More → Nearby Lights. If a site has mixed firmware types, run a separate Mesh OTA for each type.
  • Boosters in the same network. Signal boosters help a Mesh OTA. Each booster must be in the same mesh network as the devices.

Plan for 20-30 minutes per pass. The time depends on the device count, distance, wireless conditions, and the firmware the devices start on.

How a Mesh OTA works, step by step
  1. The app connects to one device and updates it to the latest firmware.
  2. The app sends the Mesh OTA start command to that device.
  3. The device broadcasts the firmware, and the other devices relay it (15 min or more).
  4. The device reports progress to the app.
  5. The device resends lost packets as needed (5 min or more).
  6. The device tells the app that all packets are sent.
  7. The app confirms that the Mesh OTA is complete.
  8. The device sends the complete command to all devices.
  9. The devices install the firmware and reboot.

A Mesh OTA can fail for two reasons. Distance: on large sites, far devices receive only part of the firmware and cannot finish. Traffic storms: too many devices relaying at once blocks transmission. Booster placement, and working area by area, solve both.

Scenario 1: a commissioned zone

A commissioned zone holds no more than 100 devices, usually close together, so a Mesh OTA is straightforward. A signal booster helps.

  1. In the Keilton+autani app, open the zone.
  2. Add a signal booster to the zone. Reset the booster to factory settings first if needed (see PPA109S Emergency Lighting & Additional Bridges).
  3. In the Spiral Engineering app, scan the zone's QR code, or switch to the zone if you already have access.
  4. Keep the booster powered on, near the phone, with its antenna upright. For a large zone, add more boosters, each within range of the next.
  5. Choose the firmware type and tap its blue button to start the Mesh OTA. Do not move the phone or the boosters until it finishes.
  6. Check the results when the app reports completion.
  7. Repeat for any other firmware types in the zone.
  8. In the Keilton+autani app, delete the boosters from the zone and reset them to factory settings.

Scenario 2: a large factory-setting site

A site can have thousands of factory-setting devices, which makes distance and wireless traffic harder. The RP1, RP0, and FL30 help. Follow four placement rules:

  • Place boosters for coverage. Cover as much area as possible, with overlapping coverage, within the 4-hop limit.
  • Keep the phone near a booster. The app should always be close to one booster.
  • Do not move anything. Keep the phone and the boosters in place for the whole Mesh OTA.
  • Work area by area. On a large site, move the phone and the boosters to the next area and repeat.

Steps 1-3 prepare the site, steps 4-7 run the update, and steps 8-10 verify it.

  1. Prepare: use the RP1 to turn off BLE on all factory-setting devices.
  2. Turn BLE back on for a few nearby devices. Set the signal strength of BLE module 3 on the RP1, or use the FL30 on one device (its firmware must support FlashNet).
  3. Power on the boosters (in factory settings) and place them, antennas upright and unobstructed.
  4. Run: in the Spiral Engineering app, find a few devices and start the Mesh OTA.
  5. Keep the phone still until the process finishes.
  6. At 98%, wait at least 10 minutes while the app confirms.
  7. If the app loses the connection, stay in the app and follow the on-screen prompts to reconnect and resume.
  8. Verify: on a large site, move to the next area and repeat steps 2-7.
  9. Use the RP1 to turn BLE back on for all devices, then check the results.
  10. For devices that did not update: run a Mesh OTA again if many are close together, or update them one by one if only a few remain.

If a Mesh OTA stalls

If the progress bar stops moving, the devices are usually still updating; only the status report to the app has paused. Do not tap "Restart". Recover without starting over:

  1. Force-quit the Spiral Engineering app completely.
  2. Reopen it and go back to the Mesh OTA screen for this firmware type.
  3. The app finds the update already in progress and continues from the devices' real progress. Wait for it to finish.

Normal, not a stall

Progress can sit at 98% for several minutes while the app confirms. Wait at least 10 minutes before you treat it as a stall.

Troubleshooting

What you see What to do
Update takes far longer than expected Check the method. A few devices take about 90 sec each with single-device OTA; a Mesh OTA takes 20-30 min, even for a few devices.
Single-device update fails partway The phone lost its connection. Move closer to the device, keep still, and start again.
Progress sits at 98% Normal. The app is confirming. Wait at least 10 min.
Progress bar stops moving Do not tap Restart. Force-quit the app, reopen it, and return to the Mesh OTA screen.
App reports a lost connection Stay in the app and follow the on-screen prompts to reconnect and resume.
Far devices did not update Add or move boosters within the 4-hop limit, or work in smaller areas.
A few devices failed after a Mesh OTA Update them one by one. If many are close together, run a Mesh OTA again.
Mesh OTA will not include some devices Check that they share the same mesh network and firmware type (0xAA-BB).

Need help planning a site update or working through a stalled one? See Support & Contact.