Bluetooth GATT Characteristic Reference
Cycling Power Feature (0x2A65)
The CP Feature characteristic is used to report a list of features supported by the device.
Quick Summary
Payload length is 4 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 | Cycling Power Feature |
| UUID | 0x2A65 |
| Type | org.bluetooth.characteristic.cycling_power_feature |
| XML Root | Characteristic |
| Source File | org.bluetooth.characteristic.cycling_power_feature.xml |
| Field Count | 1 |
Field Specification
Parsed field definitions from the source XML value structure.
| Field | Requirement | Format | Unit | Exponent | Notes |
|---|---|---|---|---|---|
| Cycling Power Feature | Mandatory | 32bit | - | - | - |
Bit Map
Bit-level enumerations extracted from the XML BitField definition.
| Field | Bit | Size | Name | 0 Means | 1 Means |
|---|---|---|---|---|---|
| Cycling Power Feature | 0 | 1 | Pedal Power Balance Supported | False | True |
| Cycling Power Feature | 1 | 1 | Accumulated Torque Supported | False | True |
| Cycling Power Feature | 2 | 1 | Wheel Revolution Data Supported | False | True |
| Cycling Power Feature | 3 | 1 | Crank Revolution Data Supported | False | True |
| Cycling Power Feature | 4 | 1 | Extreme Magnitudes Supported | False | True |
| Cycling Power Feature | 5 | 1 | Extreme Angles Supported | False | True |
| Cycling Power Feature | 6 | 1 | Top and Bottom Dead Spot Angles Supported | False | True |
| Cycling Power Feature | 7 | 1 | Accumulated Energy Supported | False | True |
| Cycling Power Feature | 8 | 1 | Offset Compensation Indicator Supported | False | True |
| Cycling Power Feature | 9 | 1 | Offset Compensation Supported | False | True |
| Cycling Power Feature | 10 | 1 | Cycling Power Measurement Characteristic Content Masking Supported | False | True |
| Cycling Power Feature | 11 | 1 | Multiple Sensor Locations Supported | False | True |
| Cycling Power Feature | 12 | 1 | Crank Length Adjustment Supported | False | True |
| Cycling Power Feature | 13 | 1 | Chain Length Adjustment Supported | False | True |
| Cycling Power Feature | 14 | 1 | Chain Weight Adjustment Supported | False | True |
| Cycling Power Feature | 15 | 1 | Span Length Adjustment Supported | False | True |
| Cycling Power Feature | 16 | 1 | Sensor Measurement Context | Force based | Torque based |
| Cycling Power Feature | 17 | 1 | Instantaneous Measurement Direction Supported | False | True |
| Cycling Power Feature | 18 | 1 | Factory Calibration Date Supported | False | True |
| Cycling Power Feature | 19 | 1 | Enhanced Offset Compensation Supported | False | True |
| Cycling Power Feature | 20 | 2 | Distribute System Support | Unspecified (legacy sensor) | Not for use in a distributed system |
Byte Layout and Decode
Payload length is 4 bytes.
function decodePayload(dataView, offset = 0) {
// Parse cycling_power_feature (32bit) according to Bluetooth format rules.
return { cycling_power_feature };
}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 Cycling Power Feature in Bluetooth GATT?
Cycling Power Feature is defined as a Bluetooth GATT characteristic entry with type org.bluetooth.characteristic.cycling_power_feature and UUID 0x2A65.
What UUID identifies Cycling Power Feature?
The UUID for Cycling Power Feature is 0x2A65.
How should I parse Cycling Power Feature?
Payload length is 4 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.