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.