Our step-by-step guide to configure the beacons and sensors using Device Manager software.
Learn how we at reelyActive configure the rugged beacons for real-time sensing and location
ELA Innovation beacons, the Device Manager PC software, and a NFC reader.
Run Device Manager PC on the host PC with a NFC reader.
Install the Device Manager PC software using the Windows installer provided with the download.
An instructional video is available on the Device Manager Suite web page.
Connect the NFC reader to a free USB port on the host PC and validate that it is recognised by Windows.
ELA Innovation recommends the ACR1252U USB NFC reader.
Run the Device Manager PC software by double-clicking on the Desktop icon or selecting from the Windows Start menu, and observe the welcome screen.
Click the Play icon in the NFC Programmer box to open a dialog to select the connected NFC reader.
Click the ACS ACR1252 button* to select the connected NFC reader. The NFC reader panel should appear.
*If a different model of reader is connected, select that instead.
Click the Gear icon in the NFC reader panel to open the TAG Configuration panel.
It is now possible to configure beacons via NFC from the TAG Configuration panel, which is covered in Step 2.
Configure beacons one-at-a-time from the host PC via NFC.
Place the beacon on the NFC reader and click the Read icon in the TAG Configuration panel.
Information about the version, technology and firmware of the beacon should appear, as well as logical groupings of configurable parameters.
Edit the parameters in each logical grouping as required for the intended application.
The Advanced BLE grouping, when available, provides the option to advertise manufacturer data and battery level. The recommended settings are:
| Manufacturer Data Enable | True |
|---|---|
| Battery in Scan Response | True |
Using manufacturer data ensures that the beacon will be recognised as an ELA Innovation device by its Company ID, and that the sensor data will be processed accordingly.
For gateway infrastructure that is configured to actively scan devices, the battery option is an efficient way to relay the battery level in a scan response packet.
Manufacturer data must be enabled for accurate device classification in HPE Aruba IoT Operations.
Click the Write icon in the TAG Configuration panel to update the configuration of the beacon.
A popup should appear confirming the success of the write.
The beacon is now configured. Repeat Step 2 for each beacon. Observing the advertised data is covered in Step 3.
Optionally observe the transmitted data in your web browser.
Follow one of our tutorials to install Pareto Anywhere on your platform of choice:
Browse to the /context API of the Pareto Anywhere instance, specifying the beacon's identifier in the route as follows:
http://pareto.local/context/device/e467dd123456/2
Change pareto.local to the IP address and port (ex: 127.0.0.1:3001) as required, and the identifier of the device (ex: e467dd000000) to that of your beacon.* The /2 at the end specifies that the identifier is an EUI-48.
*alternatively, open the Devices Observer web app and select the beacon's identifier from the list of detected devices.
Our cheatsheet details the raddec and dynamb JSON output from the Pareto Anywhere open source middleware.
Tutorial prepared with ♥ by jeffyactive.
You can reelyActive's open source efforts directly by contributing code & docs, collectively by sharing across your network, and commercially through our packages.Continue exploring our open architecture and all its applications.