VelocAI logo Bluetooth Explorer Documentation

Bluetooth GATT Characteristic Reference

CGM Feature (0x2AA8)

org.bluetooth.characteristic.cgm_feature

CGM Feature is defined in the Bluetooth GATT XML specification with type org.bluetooth.characteristic.cgm_feature and UUID 0x2AA8.

Quick Summary

Payload length is profile-defined or variable based on field formats. 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.

PropertyValue
NameCGM Feature
UUID0x2AA8
Typeorg.bluetooth.characteristic.cgm_feature
XML RootCharacteristic
Source Fileorg.bluetooth.characteristic.cgm_feature.xml
Field Count4

Field Specification

Parsed field definitions from the source XML value structure.

Field Requirement Format Unit Exponent Notes
CGM FeatureMandatory24bit-0Byte Order - LSO...MSO
CGM TypeMandatory4bit--See Note number 2 below.
CGM Sample LocationMandatory4bit--See Note number 2 below.
E2E-CRCMandatoryuint16-0If the device supports E2E-safety (E2E-CRC Supported bit is set in CGM Feature), the feature are secured by a CRC calculated over all data. This field is mandatory in this characteristic. If the device doesn?t support E2E-safety the value of the field shall be set to 0xFFFF.

Bit Map

Bit-level enumerations extracted from the XML BitField definition.

Field Bit Size Name 0 Means 1 Means
CGM Feature01Calibration SupportedFalseTrue
CGM Feature11Patient High/Low Alerts supportedFalseTrue
CGM Feature21Hypo Alerts supportedFalseTrue
CGM Feature31Hyper Alerts supportedFalseTrue
CGM Feature41Rate of Increase/Decrease Alerts supportedFalseTrue
CGM Feature51Device Specific Alert supportedFalseTrue
CGM Feature61Sensor Malfunction Detection supportedFalseTrue
CGM Feature71Sensor Temperature High-Low Detection supportedFalseTrue
CGM Feature81Sensor Result High-Low Detection supportedFalseTrue
CGM Feature91Low Battery Detection supportedFalseTrue
CGM Feature101Sensor Type Error Detection supportedFalseTrue
CGM Feature111General Device Fault supportedFalseTrue
CGM Feature121E2E-CRC supportedFalseTrue
CGM Feature131Multiple Bond supportedFalseTrue
CGM Feature141Multiple Sessions supportedFalseTrue
CGM Feature151CGM Trend Information supportedFalseTrue
CGM Feature161CGM Quality supportedFalseTrue

Byte Layout and Decode

Payload length is profile-defined or variable based on field formats.

function decodePayload(dataView, offset = 0) {
  // Parse cgm_feature (24bit) according to Bluetooth format rules.
  // Parse cgm_type (4bit) according to Bluetooth format rules.
  // Parse cgm_sample_location (4bit) according to Bluetooth format rules.
  const e2e_crc = dataView.getUint16(offset + 0, true);
  return { cgm_feature, cgm_type, cgm_sample_location, e2e_crc };
}

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 CGM Feature in Bluetooth GATT?

CGM Feature is defined as a Bluetooth GATT characteristic entry with type org.bluetooth.characteristic.cgm_feature and UUID 0x2AA8.

What UUID identifies CGM Feature?

The UUID for CGM Feature is 0x2AA8.

How should I parse CGM Feature?

Payload length is profile-defined or variable based on field formats.

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.