Characteristic 5. Read more than 19 bytes.

Denis Katasonov

Hello everybody.

We tried to do, as is done here - http://e2e.ti.com/support/low_power_rf/f/538/p/254913/892847.aspx#892847

It's really works, we can read more than 19 bytes, number of recieved bytes is equal to SIMPLEPROFILE_CHAR5_LEN if we are using GATT_DiscCharsByUUID instead of GATT_ReadUsingCharUUID. But values of char5 in this case is garbage. What we are doing wrong?

Thanks!

Br. D.

over 12 years ago

0 Greenja over 12 years ago

Guru 22270 points

Hello Denis,

If you are using the example code for simplePeripheral, Characteristic 5 is encrypted.

Thanks,

0 Denis Katasonov over 12 years ago in reply to Greenja

Prodigy 200 points

Hello, greenja.

I know. But how does this relate to the volume of data transmitted?

Br.

0 Greenja over 12 years ago in reply to Denis Katasonov

Guru 22270 points

There are too few details to give any answer other than the obvious.

You stated that the post for transmitting 19+ bytes worked and that post is using a different characteristic. If you are using characteristic 5 and the data is garbage, then whatever you are reading the data from is not in a bonded connection if other characteristics provide valid data. As stated, there just wasn't enough information available to come come to any other conclusion.

Thanks,

0 Denis Katasonov over 12 years ago in reply to Greenja

Prodigy 200 points

Connection is bonded.

0 Greenja over 12 years ago in reply to Denis Katasonov

Guru 22270 points

I haven't tested out the code to see exactly what is going on. Quite possibly, the fact that you are GATT_ReadUsingCharUUID does not allow for description of data. Until I test it, this is just speculation. You could look up the parameters associated with GATT_ReadUsingCharUUID to see if in fact it can be used on encrypted data.

Thanks,

Bluetooth®︎

Bluetooth forum

Characteristic 5. Read more than 19 bytes.