gattc read in multi connect

RE: gattc read in multi connect

Sigurd — Thu, 09 Nov 2017 09:46:42 GMT

Ok. Glad to hear that you found the issue :)

RE: gattc read in multi connect

Siva Subrahmanyam — Thu, 09 Nov 2017 09:43:37 GMT

My Bad its a synchronization issue with my code, This was causing read requests going to other connected tags.

RE: gattc read in multi connect

Sigurd — Thu, 09 Nov 2017 08:43:34 GMT

How do you know that read request are going to other(wrong) tags ?

Are you sure it's not an issue with the ADC readings?

nRF51x22 Evaluation Kit(PCA10001) uses an nRF51 IC revision 1 or 2. This is an outdated chip revision, and not recommended for new products and design(nRF51 IC is now on revision 3). Also this old SDK could have some bugs. So it's not unthinkable that these factors could somehow be causing the issue. As mentioned in your other post, I would therefore recommend upgrading to a Development Kit. For new products I would recommend a nRF52832-DK, where you have support for the latest SDK versions and Bluetooth 5.

RE: gattc read in multi connect

Siva Subrahmanyam — Wed, 25 Oct 2017 11:47:44 GMT

Are you using the BLE battery service for this? Yes. So none of the tags really have 2 %, 8% battery level?
Yes, Verified with nrfconnect Mobile App & gatttool. As i said i got TagA read handle(0x09) and TagB read handle(0x12), with gatt tool i tried to do a char-read on TagA with 0x12 and TagB with 0x09 i am getting 2%,8% battery read values.

How are you measuring the battery level? Are you using the ADC for this? Yes.

When does this bug happen? Only when you are reading different tags at once?.

Yes, This bug will occur when i initiate connect to multiple tags at time. Yes i am doing a read on different tags. When i place One tag,/two Tags of each type this bug was not reproduced as my application will connect one tag will do a battery read disconnect and connect to other tag. If large number of tags are there (i.e 15/20/40) my application will try to connect to multiple tags and getting 2%,8% battery reads once in every 5 times.

RE: gattc read in multi connect

Sigurd — Mon, 23 Oct 2017 14:14:16 GMT

I am not getting garbage values, I am getting 2%,8% battery values. verified with nrf connect on each tag it was showing 91%.

Are you using the BLE battery service for this?
So none of the tags really have 2 %, 8% battery level?
How are you measuring the battery level? Are you using the ADC for this?
When does this bug happen? Only when you are reading different tags at once?

RE: gattc read in multi connect

Siva Subrahmanyam — Fri, 20 Oct 2017 07:13:20 GMT

I am not getting garbage values, I am getting 2%,8% battery values. verified with nrf connect on each tag it was showing 91%.

Yes, I am getting values from different type of tag. there is cross talk happening with multi connect.

I got two type tags TagA, TagB each 15 quantity. Tag A battery read handle 0x09,Tag B battery read handle 0x12. when read request are going to other tags i am getting 2%,8% battery reads.

RE: gattc read in multi connect

Sigurd — Wed, 18 Oct 2017 11:16:55 GMT

Ok, what do you mean by "I am getting invalid battery levels." ? Are you getting garbage values? or are you getting the value from a different board that you intended?

Is the values you get consistent? or do they change significantly from each read with sd_ble_gattc_read(...)?

RE: gattc read in multi connect

Siva Subrahmanyam — Fri, 13 Oct 2017 01:41:01 GMT

I am using nordic_sdk_7, with S120 Softdevice on PCA10001 board running ble_connectivity example program.

We are using appropriate reaad handle along with connection handle.

Here is the SetUp details: I am using beagle board as application board, PCA10001 as connectivity board. I had given a lot of debug prints to make sure that we are sending apropriate read handle.

RE: gattc read in multi connect

Sigurd — Thu, 12 Oct 2017 14:54:38 GMT

Hi,

What SDK version are you using? Make sure that sd_ble_gattc_read(...) uses both the correct connection handle and the correct attribute handle.