Configure SB1000 with the iOS or Android app

What the app provides

The Varibits app reads and changes supported SB1000 settings over NFC and stores product information and help for offline use. A compatible NFC reader is needed for device scans; an app installed on a tablet without NFC can still provide help and templates.

Live RS485 scans, register scans, point editors, and the loopback self-test run in the affected SB1000's web interface. New firmware settings may be web-only until the app's NFC schema supports them.

1. Read the intended device

  1. Open the app and start its scan action. On Android, enable NFC if the device provides that switch.
  2. Place the phone's NFC antenna at the SB1000 NFC area and hold it steady until the read finishes. Antenna position varies by phone; a thick or metallic case can interfere.
  3. Confirm product identity and firmware version in the returned snapshot before editing.
  4. If reading is disabled by the device's NFC policy, use the installation's permitted configuration interface. Do not interpret a locked response as a wiring problem.

2. Review and write the changes

Edit the required settings and review the difference from the snapshot. The app sends changed settings, so leaving an unrelated setting untouched is different from explicitly clearing it.

Record a reconnect plan before changing network settings. Observe any restart indication. Keep the phone in place until the NFC write completes.

The app can show the write as saved before it has read a device apply receipt. An optional verification rescan checks the transaction result. To establish that the device applied the intended change, rescan and inspect the readable setting and successful receipt where supported.

3. Handle a rejected or uncertain result

  • Stale revision: read a fresh snapshot, compare again, and reapply only the intended changes. Another interface may have changed the device.
  • Writes disabled or locked: check the NFC write policy through an authorized configuration route.
  • Unsupported: check the device/app/protocol compatibility rather than repeatedly retrying the same setting.
  • Invalid payload or storage error: record the exact status, app and firmware versions, and setting name for support.
  • Interrupted scan/write: obtain a fresh snapshot before deciding whether another write is necessary.

Passwords are write-only. A blank password display after a read is not evidence that the password was erased. Enter a new secret only when you intend to change it.

4. Reuse a template

Create a reusable template from the scanned device's supported settings and give it a descriptive name. Device-specific values should be requested when applying it rather than copied blindly to every unit.

Portable templates use the .varibitsconfig format. Import a file through the app's document/share workflow, then review it against a freshly scanned target before writing. The app checks product, schema, protocol, field definitions, and value limits.

Templates omit secret values or ask for them at application time. They are not complete backups of point maps, certificates, firmware, and every device setting. An incompatible/newer template must not be made to “fit” by editing its format identifiers.

Completion check

Rescan the correct device when verification is required, confirm the intended readable settings, and test the affected function. Keep templates and support evidence free of passwords. Note the app/platform and firmware versions if behavior differs between devices.

The help library is bundled with the app. Updating an article on the website does not update an already-installed app until a release includes the newer content.

Back up, update, restore, and hand over SB1000

Before a change

Record the current firmware, serial number, network access method, port modes, and one known-good integration test. Arrange a maintenance window for changes that restart services or the unit. Keep a copy of the point definitions and installation wiring/address list.

1. Save the appropriate configuration

Use “Back up configuration” in the SB1000 web interface's Device Settings. Complete any authentication/unlock step and confirm that the .sbb file was downloaded. Label it with the installation, serial number, firmware, and date.

Store a configuration backup as sensitive installation data: it can contain network and credential settings. Do not attach it to a public issue or send it as an ordinary unreviewed diagnostic export.

An NFC .varibitsconfig template is a reusable selection of supported settings. It omits secrets or asks for them and does not replace the device's configuration backup.

2. Update firmware

  1. Use the update workflow offered by the device and the firmware intended for SB1000. Check the target version and release notes.
  2. Maintain reliable power and a stable local connection during upload. Close unnecessary sessions and avoid simultaneous configuration changes.
  3. Start the update and allow the device to complete it and restart. A temporary disconnected page can be expected during reboot.
  4. Reconnect using the configured address and verify the running firmware version before retrying an upload that appeared to lose its connection.
  5. Recheck the intended operating modes and the known-good integration test.

Do not assume an upload failure message proves the old firmware is still running. If the unit remains unreachable, first check power/link, the current address, and any reported update result. Use the documented recovery procedure for that release or contact support instead of improvising a factory reset.

3. Restore deliberately

Restoring a .sbb configuration replaces current settings and point/device maps and then reboots the unit. The web interface describes the scope before confirming. Factory-locked identity values such as the serial number are preserved; copied network or integration settings can still be inappropriate for the destination installation.

  1. Confirm the backup belongs to the intended product and installation and is compatible with the target firmware.
  2. Save the current configuration first if you may need to return to it.
  3. Check the IP address and network details that will take effect, including duplicate-address risks when restoring to a replacement unit.
  4. Choose the restore file, review the warning, and restore only the intended configuration.
  5. Reconnect after reboot and verify both identity and integration behavior.

A restore is not a merge of just the settings you were viewing. A failed restore must be investigated from its reported error; do not repeatedly try unrelated backups.

4. Verify and hand over

Check one correct point in each active integration, source quality/freshness, the intended polling/cache settings, and required write/release behavior. Confirm commissioning has ended and test overrides have been removed.

Record firmware/app/client versions, actual IP/service ports, bus settings and Unit IDs, point-map revision, and the location of protected backups. Provide the operator with a clear way to regain local access.

When contacting support

Include the serial number, running/target firmware versions, exact error, time of the change, access method, and what still works. Share redacted screenshots and a minimal failed transaction first. Send a backup containing secrets only through an explicitly agreed support route.

The network link is on, but I cannot open SB1000

Check from the computer you are using

  1. Obtain the device's current IP address and whether it uses static addressing or DHCP. Use installation records, the network's lease information, or a permitted NFC read; do not assume a factory or example address.
  2. Check subnet/routing and duplicate IP addresses. A phone on another Wi-Fi network may have a different route from the BMS computer.
  3. Use the configured HTTP or HTTPS scheme and web port. A changed web port is unrelated to the Modbus gateway port.
  4. If access disappeared after a settings change, allow any expected restart and reconnect at the new address. Check whether the commissioning hotspot has closed.
  5. If the page opens but live data does not, record the connection message. Close unused sessions and retry one browser session; proxies/firewalls can affect live connections differently from ordinary page requests.

A failed ping alone does not prove the web service is unavailable. A successful Ethernet link alone does not prove IP or web configuration is correct.

Expected result

The correct unit opens from the intended network and live status updates. If it does not, record the exact URL without credentials, network/interface, IP settings, firmware, and browser error. Resolve access before trying the device's RS485 self-test.