VelocAI logo Bluetooth Explorer Documentation

Bluetooth GATT Characteristic Reference

Record Access Control Point (0x2A52)

org.bluetooth.characteristic.record_access_control_point

This control point is used with a service to provide basic management functionality for the Glucose Sensor patient record database. This enables functions including counting records, transmitting records and clearing records based on filter criterion. The filter criterion in the Operand field is defined by the service that references this characteristic as is the format of a record (which may be comprised of one or more characteristics) and the sequence of transferred records.

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
NameRecord Access Control Point
UUID0x2A52
Typeorg.bluetooth.characteristic.record_access_control_point
XML RootCharacteristic
Source Fileorg.bluetooth.characteristic.record_access_control_point.xml
Field Count3

Field Specification

Parsed field definitions from the source XML value structure.

Field Requirement Format Unit Exponent Notes
Op CodeMandatoryuint8---
OperatorMandatoryuint8---
OperandMandatoryvariable--The operands correspond to the Op Code values (Keys 0 to 255) defined in the Op Code Field above

Byte Layout and Decode

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

function decodePayload(dataView, offset = 0) {
  const op_code = dataView.getUint8(offset + 0);
  const operator = dataView.getUint8(offset + 1);
  // Parse operand (variable) according to Bluetooth format rules.
  return { op_code, operator, operand };
}

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 Record Access Control Point in Bluetooth GATT?

Record Access Control Point is defined as a Bluetooth GATT characteristic entry with type org.bluetooth.characteristic.record_access_control_point and UUID 0x2A52.

What UUID identifies Record Access Control Point?

The UUID for Record Access Control Point is 0x2A52.

How should I parse Record Access Control Point?

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.