CC2650STK Service UUID's

Hi Jeff,

Which iOS app & version are you using to connect to the SensorTag 2.0?

Best wishes

Also, please post CC2650STK related questions in the BLE E2E forum: e2e.ti.com/support/wireless_connectivity/f/538.aspx

Best wishes

Hi JXS -

I believe this is the correct forum, unless I am missing something.

With regard to the iOS app. I am using the TI SensorTag app v4.0 (updated February 24, 2015), so I think that is the latest. I am see the same thing on the Service Explorer that is shown on the 3rd screenshot on the appstore. I am not able to determine the UUID for the gyroscope, the accelerometer, or the microphone. I would assume there would be some documentation on the UUID's and the data formats - I figured out the light sensor just by trial and error.

Also, the accelerometer and gyroscope seemed inconsistent at best even with the app store app.

Thanks,

Jeff.

Hi Jeff,

My apologies - you are in the correct forum!

We'll look into it and get back to you.

Best wishes

Hi Jeff,

I'm suffering the lack of documentation with this new module. I've used the iOS app to know the UUIDs associated to each sensor, and then tried to use gatttool in Linux. I can access "movement" data from the MPU, but I don't know how to extract only the accelerometer data, any idea?

Thanks,

Diego

The only characteristics user description is for the key press state, and knowing if a button is pressed isn't the most exciting thing ever. Everything else is "unknown".

TI went all out for the Sensortag 1.0 User's Guide. An epic wiki isn't really essential, but we would appreciate a list of all the characteristics. It can be a simple pdf or csv file for all I care. If someone had the free time to read through the source code am host the info somewhere that'd be great...

Exciting button press notifications with gatttool

PS can we also get support for embedded vines on E2E?

Hi JXS -

Thanks for digging this up, but the CSV still has a bunch of unknown services.  I didn't realize this was not launched yet, so I can wait for the collateral with the launch - I have pieced enough of this together to get some movement and gyroscope data.

BTW - it is amazing how much more reliable and consistent the device works with a fresh 2032 battery in it.  The symptoms I saw were crazy meter readings and lockups of the movement sensor after a few responses until reconnecting the device.  Seemed to impact the movement sensors the most.

Thanks again for the help,

Jeff.

Hi Diego -

From what I can tell, the accelerometer is controlled by using the last 3 bits of the movement service ('f000aa80-0451-4000-b000-000000000000'). So, to get the x,y,z axes, send a 7 to the config service.

Jeff.

JXS,

In the CVS file, many of the UUID descriptions are "uknown". Could you tell me where you got the descriptions from? Are the UUIDs listed somewhere or does the BTTool "know"?

Jeff,

The movement service that you hypothesized sends me 18 bytes of data. How is this data structured?

Hi Diego -

I got this from the Evothings app:

var ax = evothings.util.littleEndianToInt16(data, 0) / 16.0
var ay = evothings.util.littleEndianToInt16(data, 2) / 16.0
var az = evothings.util.littleEndianToInt16(data, 4) / 16.0 * -1.0

This is the accelerometer.  Gyroscope is 6,8,10.  Hope it helps.

Jeff.

Jeff Durnwald said:

I would assume there would be some documentation on the UUID's and the data formats - I figured out the light sensor just by trial and error.

Hi,

Which characteristic UUID on the CC2650STK did you figure out was the light sensor?

So far, I've only been able to test the button from my iOS test app.

Thanks,

Ron

The light sensor is 'f000aa70-0451-4000-b000-000000000000'. You can see that from the iOS app by going to the Service Explorer. You should also check out the Evothings app to get help on some of the other sensors until they get the documentation completed. I did notice that the gyroscope and the accelerometer were flipped on the Evothings app. See forum.evothings.com/viewtopic.php;t=1390

Jeff.