Battery Service Client Characteristic Configuration writeCB

Lewis Chen

Other Parts Discussed in Thread: CC2540

I am currently working with cc2540 chip BLE Stack 1.4.1

Right now, I am using Microsoft universal windows application to write a CCC descriptor with an arbitrary bit pattern for the Battery Service/Battery_level characteristic. I was hoping to intercept the 16 bit message before it was processed as I don't really have a need for the battery service and so I was hoping to utilize the write method a little differently.

However, when I check the value passed into the batterywriteCB, I get a constant value regardless of the descriptor value. The offset value is also the same as the message value.

Does anyone know what is causing this and/or is my fundamental thinking about what I can do with the CCC descriptor flawed?

Thanks

over 10 years ago

0 JXS over 10 years ago

TI__Guru** 105180 points

Hello,

Did you confirm with a sniffer to see if the value in your WriteCB matches what was sent by the Client?

Best wishes

0 Lewis Chen over 10 years ago in reply to JXS

Prodigy 100 points

Hi, after using the sniffer, the value being transmitted was a constant stream of 0s. I looked into it and windows 10 API does not allow you to send arbitrary bytes out, so I am only able to send Notify, Indications, or None out.

Thanks for the help.

Bluetooth®︎

Bluetooth forum

Battery Service Client Characteristic Configuration writeCB