BLE Gatt Descriptors 0x2904, 0x2905

hansonite
Posts: 4
Joined: Mon Mar 30, 2020 12:17 pm

BLE Gatt Descriptors 0x2904, 0x2905

Postby hansonite » Wed Apr 15, 2020 11:56 am

<r>Hi,<br/>
<br/>
currently, I'm wondering if anybody ever has implemented the following GATT Descriptors ?<br/>
<br/>
• Characteristic Presentation Format - 0x2904<br/>
<br/>
The Characteristic Presentation Format descriptor defines the format of the Characteristic Value.<br/>
<br/>
<URL url="https://www.bluetooth.com/wp-content/up ... <LINK_TEXT text="https://www.bluetooth.com/wp-content/up ... format.xml">https://www.bluetooth.com/wp-content/up ... </URL><br/>
<br/>
<br/>
z.B: IPv4, IPv6, Bluetooth Address<br/>
<br/>
<Enumerations><br/>
<Enumeration key="0" value="Reserved For Future Use"/><br/>
<Enumeration key="1" value="Boolean"/><br/>
<Enumeration key="2" value="unsigned 2-bit integer"/><br/>
<Enumeration key="3" value="unsigned 4-bit integer"/><br/>
<Enumeration key="4" value="unsigned 8-bit integer"/><br/>
<Enumeration key="5" value="unsigned 12-bit integer"/><br/>
<Enumeration key="6" value="unsigned 16-bit integer"/><br/>
<Enumeration key="7" value="unsigned 24-bit integer"/><br/>
<Enumeration key="8" value="unsigned 32-bit integer"/><br/>
<Enumeration key="9" value="unsigned 48-bit integer"/><br/>
<Enumeration key="10" value="unsigned 64-bit integer"/><br/>
<Enumeration key="11" value="unsigned 128-bit integer"/><br/>
<Enumeration key="12" value="signed 8-bit integer"/><br/>
<Enumeration key="13" value="signed 12-bit integer"/><br/>
<Enumeration key="14" value="signed 16-bit integer"/><br/>
<Enumeration key="15" value="signed 24-bit integer"/><br/>
<Enumeration key="16" value="signed 32-bit integer"/><br/>
<Enumeration key="17" value="signed 48-bit integer"/><br/>
<Enumeration key="18" value="signed 64-bit integer"/><br/>
<Enumeration key="19" value="signed 128-bit integer"/><br/>
<Enumeration key="20" value="IEEE-754 32-bit floating point"/><br/>
<Enumeration key="21" value="IEEE-754 64-bit floating point"/><br/>
<Enumeration key="22" value="IEEE-11073 16-bit SFLOAT"/><br/>
<Enumeration key="23" value="IEEE-11073 32-bit FLOAT"/><br/>
<Enumeration key="24" value="IEEE-20601 format"/><br/>
<Enumeration key="25" value="UTF-8 string"/><br/>
<Enumeration key="26" value="UTF-16 string"/><br/>
<Enumeration key="27" value="Opaque Structure"/><br/>
<Reserved start="28" end="255"/><br/>
</Enumerations><br/>
<br/>
<br/>
• Characteristic Aggregate Format - 0x2905<br/>
<br/>
The Characteristic Aggregate Format descriptor defines the format of an aggregated Characteristic Value.<br/>
<br/>
<URL url="https://www.bluetooth.com/wp-content/up ... <LINK_TEXT text="https://www.bluetooth.com/wp-content/up ... format.xml">https://www.bluetooth.com/wp-content/up ... </URL><br/>
<br/>
<Summary><br/>
Only one Characteristic Aggregate Format descriptor exists in a characteristic definition. This descriptor consists of a list of Attribute Handles pointing to Characteristic Presentation Format declarations. This descriptor is read only and does not require authentication or authorization. The list of Attribute Handles is the concatenation of multiple 16-bit Attribute Handle values into a single Attribute Value. If more than one Characteristic Presentation Format declarations exist, then there is one Characteristic Aggregate Format declaration. However, a Characteristic Aggregate Format descriptor can be present even if there aren't any Presentation Format descriptors in the characteristic definition. The order of the Attribute Handles in the list is significant.<br/>
</Summary><br/>
<Example><br/>
If 3 Characteristic Presentation Format declarations exist at Attribute Handles 0x40, 0x50 and 0x60, the Characteris Aggregate Format Value is 0x405060.<br/>
</Example></r>

Who is online

Users browsing this forum: No registered users and 110 guests