Bluetooth GATT Characteristic Reference
PLX Features (0x2A60)
The PLX Features characteristic is used to describe the supported features of the Server. Included in the characteristic is a PLX Features field, and, depending on the contents of the PLX Features field, the Measurement Status Support field, and the Device and Sensor Status Support field.
Quick Summary
Payload length is 7 bytes. This page is generated from official GATT XML and presented as implementation-ready guidance.
At a Glance
Key reference details for BLE implementation, interoperability testing, and AI-assisted troubleshooting.
| Property | Value |
|---|---|
| Name | PLX Features |
| UUID | 0x2A60 |
| Type | org.bluetooth.characteristic.plx_features |
| XML Root | Characteristic |
| Source File | org.bluetooth.characteristic.plx_features.xml |
| Field Count | 3 |
Field Specification
Parsed field definitions from the source XML value structure.
| Field | Requirement | Format | Unit | Exponent | Notes |
|---|---|---|---|---|---|
| Supported Features | Mandatory | 16bit | - | - | - |
| Measurement Status Support | C1 | 16bit | - | - | - |
| Device and Sensor Status Support | C2 | 24bit | - | - | - |
Bit Map
Bit-level enumerations extracted from the XML BitField definition.
| Field | Bit | Size | Name | 0 Means | 1 Means |
|---|---|---|---|---|---|
| Supported Features | 0 | 1 | Measurement Status support is present | False | True |
| Supported Features | 1 | 1 | Device and Sensor Status support is present | False | True |
| Supported Features | 2 | 1 | Measurement Storage for Spot-check measurements is supported | False | True |
| Supported Features | 3 | 1 | Timestamp for Spot-check measurements is supported | False | True |
| Supported Features | 4 | 1 | SpO2PR-Fast metric is supported | False | True |
| Supported Features | 5 | 1 | SpO2PR-Slow metric is supported | False | True |
| Supported Features | 6 | 1 | Pulse Amplitude Index field is supported | False | True |
| Supported Features | 7 | 1 | Multiple Bonds Supported | False | True |
| Measurement Status Support | 5 | 1 | Measurement Ongoing bit supported | False | True |
| Measurement Status Support | 6 | 1 | Early Estimated Data bit supported | False | True |
| Measurement Status Support | 7 | 1 | Validated Data bit supported | False | True |
| Measurement Status Support | 8 | 1 | Fully Qualified Data bit supported | False | True |
| Measurement Status Support | 9 | 1 | Data from Measurement Storage bit supported | False | True |
| Measurement Status Support | 10 | 1 | Data for Demonstration bit supported | False | True |
| Measurement Status Support | 11 | 1 | Data for Testing bit supported | False | True |
| Measurement Status Support | 12 | 1 | Calibration Ongoing bit supported | False | True |
| Measurement Status Support | 13 | 1 | Measurement Unavailable bit supported | False | True |
| Measurement Status Support | 14 | 1 | Questionable Measurement Detected bit supported | False | True |
| Measurement Status Support | 15 | 1 | Invalid Measurement Detected bit supported | False | True |
| Device and Sensor Status Support | 0 | 1 | Extended Display Update Ongoing bit supported | False | True |
| Device and Sensor Status Support | 1 | 1 | Equipment Malfunction Detected bit supported | False | True |
| Device and Sensor Status Support | 2 | 1 | Signal Processing Irregularity Detected bit supported | False | True |
| Device and Sensor Status Support | 3 | 1 | Inadequite Signal Detected bit supported | False | True |
| Device and Sensor Status Support | 4 | 1 | Poor Signal Detected bit supported | False | True |
| Device and Sensor Status Support | 5 | 1 | Low Perfusion Detected bit supported | False | True |
| Device and Sensor Status Support | 6 | 1 | Erratic Signal Detected bit supported | False | True |
| Device and Sensor Status Support | 7 | 1 | Nonpulsatile Signal Detected bit supported | False | True |
| Device and Sensor Status Support | 8 | 1 | Questionable Pulse Detected bit supported | False | True |
| Device and Sensor Status Support | 9 | 1 | Signal Analysis Ongoing bit supported | False | True |
| Device and Sensor Status Support | 10 | 1 | Sensor Interface Detected bit supported | False | True |
| Device and Sensor Status Support | 11 | 1 | Sensor Unconnected to User bit supported | False | True |
| Device and Sensor Status Support | 12 | 1 | Unknown Sensor Connected bit supported | False | True |
| Device and Sensor Status Support | 13 | 1 | Sensor Displaced bit supported | False | True |
| Device and Sensor Status Support | 14 | 1 | Sensor Malfunctioning bit supported | False | True |
| Device and Sensor Status Support | 15 | 1 | Sensor Disconnected bit supported | False | True |
Byte Layout and Decode
Payload length is 7 bytes.
function decodePayload(dataView, offset = 0) {
// Parse supported_features (16bit) according to Bluetooth format rules.
// Parse measurement_status_support (16bit) according to Bluetooth format rules.
// Parse device_and_sensor_status_support (24bit) according to Bluetooth format rules.
return { supported_features, measurement_status_support, device_and_sensor_status_support };
}Use Cases and Integration Notes
BLE Telemetry
Map characteristic values into dashboards and alerts for device observability.
Firmware Regression
Compare decoded fields across builds to detect protocol or scaling changes.
App Integration
Build stable parsing paths that convert raw payloads into typed app models.
Implementation Checklist
- Validate payload length and mandatory fields before decode.
- Decode with Bluetooth-specified signedness, unit, and exponent handling.
- Convert units at presentation boundaries to avoid drift in business logic.
- Persist raw packets and decoded values for reproducible troubleshooting.
FAQ
What is PLX Features in Bluetooth GATT?
PLX Features is defined as a Bluetooth GATT characteristic entry with type org.bluetooth.characteristic.plx_features and UUID 0x2A60.
What UUID identifies PLX Features?
The UUID for PLX Features is 0x2A60.
How should I parse PLX Features?
Payload length is 7 bytes.
Where does this definition come from?
This page is generated from the Bluetooth SIG mirror XML in the oesmith/gatt-xml repository.
How does this page support BLE implementation?
The page combines structured tables, practical Q&A, and JSON-LD metadata to help teams validate integrations and troubleshoot consistently.