Bluetooth GATT Characteristic Reference
Step Climber Data (0x2ACF)
The Step Climber Data characteristic is used to send training-related data to the Client from a step climber (Server).
Quick Summary
Payload length is 23 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 | Step Climber Data |
| UUID | 0x2ACF |
| Type | org.bluetooth.characteristic.step_climber_data |
| XML Root | Characteristic |
| Source File | org.bluetooth.characteristic.step_climber_data.xml |
| Field Count | 13 |
Field Specification
Parsed field definitions from the source XML value structure.
| Field | Requirement | Format | Unit | Exponent | Notes |
|---|---|---|---|---|---|
| Flags | Mandatory | 16bit | - | - | - |
| Floors | C1 | uint16 | org.bluetooth.unit.unitless | - | Unitless with a resolution of 1 |
| Step Count | C1 | uint16 | org.bluetooth.unit.unitless | - | Unitless with a resolution of 1 |
| Step Per Minute | C2 | uint16 | org.bluetooth.unit.step_per_minute | - | Step/minute with a resolution of 1 |
| Average Step Rate | C3 | uint16 | org.bluetooth.unit.step_per_minute | - | Step/minute with a resolution of 1 |
| Positive Elevation Gain | C4 | uint16 | org.bluetooth.unit.length.metre | - | Meters with a resolution of 1 |
| Total Energy | C5 | uint16 | org.bluetooth.unit.energy.kilogram_calorie | - | Kilo Calorie with a resolution of 1 |
| Energy Per Hour | C5 | uint16 | org.bluetooth.unit.energy.kilogram_calorie | - | Kilo Calorie with a resolution of 1 |
| Energy Per Minute | C5 | uint8 | org.bluetooth.unit.energy.kilogram_calorie | - | Kilo Calorie with a resolution of 1 |
| Heart Rate | C6 | uint8 | org.bluetooth.unit.period.beats_per_minute | - | Beats per minute with a resolution of 1 |
| Metabolic Equivalent | C7 | uint8 | org.bluetooth.unit.metabolic_equivalent | -1 | Metabolic Equivalent with a resolution of 0.1 |
| Elapsed Time | C8 | uint16 | org.bluetooth.unit.time.second | - | Second with a resolution of 1 |
| Remaining Time | C9 | uint16 | org.bluetooth.unit.time.second | - | Second with a resolution of 1 |
Bit Map
Bit-level enumerations extracted from the XML BitField definition.
| Field | Bit | Size | Name | 0 Means | 1 Means |
|---|---|---|---|---|---|
| Flags | 0 | 1 | More Data | False | True |
| Flags | 1 | 1 | Step per Minute present | False | True |
| Flags | 2 | 1 | Average Step Rate Present | False | True |
| Flags | 3 | 1 | Positive Elevation Gain present | False | True |
| Flags | 4 | 1 | Expended Energy present | False | True |
| Flags | 5 | 1 | Heart Rate present | False | True |
| Flags | 6 | 1 | Metabolic Equivalent present | False | True |
| Flags | 7 | 1 | Elapsed Time present | False | True |
| Flags | 8 | 1 | Remaining Time present | False | True |
Byte Layout and Decode
Payload length is 23 bytes.
function decodePayload(dataView, offset = 0) {
// Parse flags (16bit) according to Bluetooth format rules.
const floors = dataView.getUint16(offset + 0, true);
const step_count = dataView.getUint16(offset + 2, true);
const step_per_minute = dataView.getUint16(offset + 4, true);
const average_step_rate = dataView.getUint16(offset + 6, true);
const positive_elevation_gain = dataView.getUint16(offset + 8, true);
const total_energy = dataView.getUint16(offset + 10, true);
const energy_per_hour = dataView.getUint16(offset + 12, true);
const energy_per_minute = dataView.getUint8(offset + 14);
const heart_rate = dataView.getUint8(offset + 15);
return { flags, floors, step_count, step_per_minute, average_step_rate, positive_elevation_gain };
}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 Step Climber Data in Bluetooth GATT?
Step Climber Data is defined as a Bluetooth GATT characteristic entry with type org.bluetooth.characteristic.step_climber_data and UUID 0x2ACF.
What UUID identifies Step Climber Data?
The UUID for Step Climber Data is 0x2ACF.
How should I parse Step Climber Data?
Payload length is 23 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.