Ready mobile forms

Set up and document IoT devices with a mobile form

Use a mobile form near the equipment to identify an IoT device, connect over supported Bluetooth, read or set configured values, and submit a setup record for the office or manufacturer workflow.

Configure a supported device while standing near it

Bluetooth Low Energy (BLE) lets a supported phone or tablet communicate directly with a nearby IoT device. For the local exchange described by the source, the phone does not need an internet connection or a separate gateway.

The device user opens the available mobile form, enters or selects the settings, and sends supported values to the device. The same setup can read supported device data into the form.

  1. 01Manufacturer setupDefine forms, field data types, GATT links, device types, and user access.
  2. 02Nearby connectionOpen the mobile form and connect to the supported device over BLE.
  3. 03Read or set valuesUse the configured fields and commands supported by the device.
  4. 04Save a profileReuse supported settings across multiple matching devices.
  5. 05Submit the recordSend the configuration form or communication log when a connection is available.
Device definition → nearby phone setup → configured values → saved profile → office record.

Link each form field to the device data it uses

The source setup links a mobile-form field and its data type to a supported Bluetooth GATT service and GATT characteristic. GATT, or Generic Attribute Profile, is the structure BLE devices use to expose data that an application can read or write.

The exact device commands, field types, GATT links, read/write permissions, and Bluetooth behavior are configured per project. Existing firmware still needs to expose the communication required by the planned mobile form.

Save a configuration profile for matching devices

After a device user enters supported settings, the completed form can be saved as a configuration profile. That profile can be applied to multiple matching devices without entering the same values each time.

Staff can review available devices, profiles, and activity through the supported web interface described by the source. Confirm how device models and profiles should be matched before field rollout.

Separate the manufacturer setup from the device user's job

The manufacturer defines the mobile forms, GATT links, device types, users, and review process. The device user downloads the available form, connects near the equipment, applies or reads the supported values, and submits the completed setup record.

The source also describes a communication log with dates, employee names, and applied configuration parameters. When a phone is used to pass device data to the cloud, that handoff happens when the phone has the required connection.

Questions from the job

Frequently asked questions

Can a phone configure an IoT device without an internet connection?

Yes, when the supported device and mobile setup use direct Bluetooth communication. The phone can connect near the device, and an internet connection is not required for that local exchange.

How does a mobile-form field connect to an IoT device?

The source setup links each configured field and data type to the supported Bluetooth GATT service and characteristic used to read or send that value.

Can one saved configuration profile be applied to several devices?

Yes. A user can save supported settings as a configuration profile and apply that profile to multiple devices without entering the same values for each device.

Talk through the work

Talk with AHG about your IoT device setup

Tell us what your crew needs to capture. We will help map the current process and the next practical step.



Contact us to get a quote, discuss
your project and next steps:


Your name:

Your corporate e-mail:

What problems are you trying to solve by implementing QR Mobile Data:

What is your implementation timeframe:

Company:

Web site:



Submit