First connection: reach your SB1000 and choose its operating mode

Before you connect

Record the SB1000 serial number and firmware version, the field-device models, and the system they will connect to. Have the field-device wiring and register documentation available. Arrange any interruption to an existing bus before changing modes or starting a scan.

1. Establish local access

  1. Connect the specified power supply and check that the device starts. SB1000 accepts 9–24 V AC/DC; follow its product label and the installation's wiring requirements.
  2. Prefer Ethernet for the first connection when it is available. Check the physical link, then obtain the actual IP configuration from the device or the installation records. Do not assume a DHCP address or copy an example IP from a guide.
  3. Put the computer on a network that can reach that address. Check subnet, routing, and duplicate static addresses. Open the device's configured HTTP or HTTPS address and port.
  4. If the device cannot be reached over the network, the Varibits app can read supported settings over NFC on compatible hardware when the device's NFC policy permits it. Use the current snapshot to check the network configuration.
  5. If using the commissioning hotspot, join the network shown by the device's instructions. A phone's “no internet” warning does not itself mean local access failed. Use the local address supplied for that hotspot if the captive page does not open.

Wi-Fi uses 2.4 GHz. A metal cabinet can substantially reduce reception. Ethernet access is a useful comparison when diagnosing a radio problem.

The Wi-Fi password, web login, MQTT credentials, and NFC write permission serve different purposes. Changing one does not change the others.

2. Choose who starts the communication

  • A BMS/PLC sends Modbus TCP requests to RTU equipment: select TCP → RTU for the connected serial port. The default gateway ports are 4001 for Port 1 and 4002 for Port 2.
  • An existing RTU controller sends requests to a TCP server: select RTU → TCP and configure the remote server and its listening port. This is the opposite request direction.
  • SB1000 reads field points and publishes MQTT messages: select the MQTT mapping mode and configure the broker, devices, and points.
  • A BACnet/IP system needs objects representing Modbus points: select the BACnet mapping mode and configure the BACnet identity and point definitions.
  • A serial application expects a virtual COM port: use the matching RFC2217 client and mode.
  • Equipment needs unmodified serial frames over a TCP connection: use the raw bridge mode and its client/server and frame-timing settings.
  • A serial controller must communicate across two serial segments: use the supported RTU bridge arrangement and define the controller and device sides.

Selecting a protocol mode does not configure the external system's point definitions. A Modbus TCP client still needs the field device's register map. A raw TCP bridge or virtual COM port is not a Modbus TCP server.

The optional management interface on default TCP port 502 exposes SB1000 settings. It is separate from the serial gateway ports. Use the actual saved ports, not just these defaults.

3. Verify one result

  1. Save the selected mode and matching serial settings. Note any service restart or reconnect.
  2. If you used commissioning, finish the tests and exit commissioning so normal port operation resumes.
  3. Choose one documented read-only point. Verify its raw response and engineering value in the destination system before adding a larger point list.
  4. Record the working IP, port, bus, Unit ID, protocol, and versions.

When settings change access

Before changing an IP address, Wi-Fi network, web port, or HTTPS setting, record how you will reconnect. Reopen the new address after the change and any restart. A disappearing page can be an expected result of changing the connection you are using.

Keep a recoverable configuration before major changes. The native app's reusable template contains only supported settings and is different from a device configuration backup.

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 phone cannot read SB1000 over NFC

Check the NFC connection

  1. Confirm the phone/tablet has a compatible NFC reader. App installation alone does not mean the hardware can scan; tablets without NFC can still show offline help and templates.
  2. Start scanning inside the Varibits app. On Android, check that NFC is enabled where a system switch is available.
  3. Locate the phone's NFC antenna and hold it at the SB1000 NFC area until the scan finishes. Reposition slowly and try without a thick or metallic case.
  4. Read the actual message: no tag detected, locked reading, unsupported content, and an interrupted scan require different actions.
  5. If the device's NFC interface or reads are disabled, use the permitted web/local configuration route to inspect that policy.
  6. If a snapshot is readable but writing fails, follow the save-verification article rather than repeating reader-position tests.

Expected result

The app reads the correct SB1000 identity and supported settings. If it does not, record phone model, operating system, app/firmware versions, exact message, and whether another compatible phone can read the same device.

The app says saved, but the SB1000 setting did not change

Check the result on the affected device

  1. Confirm you wrote to the intended SB1000 and note any restart notice. Keep the phone correctly positioned until the NFC operation finishes.
  2. Allow the device to apply the change and perform the app's optional verification rescan. A completed NFC write can be shown as saved before a matching apply receipt has been read.
  3. If verification reports a stale revision, read a fresh snapshot, review the proposed changes again, and reapply only the intended edits. Another interface may have changed the configuration since the previous read.
  4. If writes are disabled/locked, check the device's NFC settings and the installation's permitted configuration route. If the response is unsupported, check app/firmware compatibility. Do not repeatedly resend the same rejected payload.
  5. If the setting changed but its effect is not visible, check restart requirements, the selected operating mode, and any changed network address. Verify through the applicable device interface.
  6. If an error persists, record the app/platform version, SB1000 firmware, setting name, and apply status. A storage error or repeated invalid-payload result needs support evidence rather than repeated retries.

Passwords are intentionally not read back. A blank password field does not prove that the saved password is empty. Reusable templates also omit secret values or request them at application time.

The native app provides NFC configuration and offline help. Live RS485 scans and self-tests require the affected SB1000's web interface.

Expected result

A fresh read confirms the intended readable setting and, where supported, a matching successful apply receipt. Retain the status and transaction evidence if it does not.