Gatt table,Sensortile

[Hesan Rfai]

Posted on July 02, 2017 at 10:17

Hello

Just starting to interact with sensortile through Linux, would be very appreciated if any body could do me a favor

and let me have the gatt table, uuid,etc..

Regards

Hesan 

[Hesan Rfai]

Posted on July 24, 2017 at 14:38

Is there any one who could help? please

[Amir Ehsandar]

Posted on August 15, 2017 at 19:32

sensortile is a multi-sensor device, giving us many physical data such as acceleration, temprature, etc. you can find out more about sensortile on official website:

/external-link.jspa?url=http%3A%2F%2Fwww.st.com%2Fen%2Fevaluation-tools%2Fsteval-stlkt01v1.html

there is also an example application (android/ios) for recieving and monitoring sensortile data. the android SDK and example app source code are available on github:

/external-link.jspa?url=https%3A%2F%2Fgithub.com%2FSTMicroelectronics-CentralLabs%2FSTBlueMS_Android

while trying to use sensortile to catch some physical data (on a platform that's not android) i found out there is no datasheet or GATT table for using sensortile BLE; however there is some standard rules. i will attach a sample python script (uses bluepy) in a few days so you will see the raw data...

so here is the GATT table:

characteristics:

ProximityGesture::Motion Intensity:

handle: 0x000d, char properties: 0x12, char value handle: 0x000e, uuid: 00140000-0001-11e1-ac36-0002a5d5c51b

FeatureAcceleration::FeatureGyroscope::FeatureMagnetometer:

handle: 0x0010, char properties: 0x10, char value handle: 0x0011, uuid: 00e00000-0001-11e1-ac36-0002a5d5c51b

FeatureAccelerationEvent:

handle: 0x0013, char properties: 0x12, char value handle: 0x0014, uuid: 00000400-0001-11e1-ac36-0002a5d5c51b

FeatureMicLevel:

handle: 0x0016, char properties: 0x10, char value handle: 0x0017, uuid: 04000000-0001-11e1-ac36-0002a5d5c51b

FeatureMemsSensorFusionCompact:

handle: 0x0019, char properties: 0x10, char value handle: 0x001a, uuid: 00000100-0001-11e1-ac36-0002a5d5c51b

FeatureCompass:

handle: 0x001c, char properties: 0x10, char value handle: 0x001d, uuid: 00000040-0001-11e1-ac36-0002a5d5c51b

FeatureActivity:

handle: 0x001f, char properties: 0x12, char value handle: 0x0020, uuid: 00000010-0001-11e1-ac36-0002a5d5c51b

FeatureCarryPosition:

handle: 0x0022, char properties: 0x12, char value handle: 0x0023, uuid: 00000008-0001-11e1-ac36-0002a5d5c51b

FeatureMemsGesture:

handle: 0x0025, char properties: 0x12, char value handle: 0x0026, uuid: 00000002-0001-11e1-ac36-0002a5d5c51b

FeatureAudioADPCM:

handle: 0x0028, char properties: 0x10, char value handle: 0x0029, uuid: 08000000-0001-11e1-ac36-0002a5d5c51b

FeatureAudioADPCMSync:

handle: 0x002b, char properties: 0x10, char value handle: 0x002c, uuid: 40000000-0001-11e1-ac36-0002a5d5c51b

each characteristic contains 3 description. you must write value 0x0100 to first description of each char (this is an standard method). then sensortile will send you data continuously as notification. you could enable multiple notifications at the same time. notifications will arrive as characteristic value. so you can distinguish notifications.

note1:

for two first chars, data has following patern:

2byte<time stamp> 2byte<acc data x> 2byte<acc data y> ... 2byte<mag data pitch>

there is some more info about data structure and uuid prefixes at SDK git page:

https://github.com/STMicroelectronics-CentralLabs/BlueSTSDK_Android/tree/b490d4d382e6f8dddbf9ce6e02414a53d576cd58

note2:

each char data has a time stamp at two first bytes, except stream data (audio)

[Govarthanam Krishnasamy]

Posted on February 20, 2018 at 10:26

I tried to read the Sensor fusion values continuously but the values are not changing in correspondence to the sensor's orientation.

I am sure that the sensor is functioning properly as it is working perfectly with BlueMS app.

Can you please share the Python script which u have been mentioning in the previous post.