Bluetooth® Tag Analog Mapping
How to 'marry' a BLE sensor to a BLE Gateway
Table of Contents
What Does Analog Mapping Mean?
Bluetooth® analog mapping refers to a BLE gateway device (e.g. Oyster3 4G Bluetooth®) treating sensor readings from a BLE tag as if they came from its own analog inputs. This means that a temperature reading from a BLE tag would not exist within the Tag List as an attribute against that specific tag, but would instead appear within a heartbeat or dynamic trip log event as an analog value.
When Should Analog Mapping Be Used?
- The BLE tag and the BLE gateway are attached to the same asset and will never change their association with one another.
- Your integration method can already handle analog values on a message payload and there would be a large amount of technical work required to interpret sensor readings from BLE Tag List data reliably.
When Should Analog Mapping Not Be Used?
- The BLE gateway device needs to detect the sensor values from more than three tags
- The BLE gateway device has no enduring relationship with the tags that it needs readings from, and the associations change frequently.
How to Create an Analog Mapping for a BLE Gateway Device
The process of creating analog mappings within Device Manager has evolved with our hardware, and will depend on your device. Please find your device below.
Device Types | Analog Mapping Method |
---|---|
G70 Bluetooth®, Dart3 Bluetooth® | Generic Protocol Tag Analog Mapping |
Oyster3 Bluetooth® | Generic Protocol Tag Analog Mapping, Proprietary Tag Analog Mapping |
Oyster Edge | Generic Protocol Tag Analog Mapping, Proprietary Tag Analog Mapping |
Remora3 | Proprietary Tag Analog Mapping |
Remora2 | Proprietary Tag Analog Mapping |
Eagle | Proprietary Tag Analog Mapping |