• State Not Answered
  • Replies 8 replies
  • Subscribers 62 subscribers
  • Views 2491 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 110934
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Problem receiving many data from two different characteristics

jpo38

We have a home made BLE device based on nrfR1822. This one has two embedded sensors sampling data at a frequency of 25Hz.

In regular mode, the device sends every second or so some markers extracted from 25Hz raw data (local embedded data processing) through 2 characteristic notifications.

In debug mode, the device sends the whole signals (at 25Hz, so one frame per 40ms) through 2 different characteristic notifications.

When I connect the device from and Android phone, I can receive the 25Hz signals in parallel (and even more).

When I connect the device from PC using a s130 dongle, only one characteristic data can be received:

  • If I toggle CCCD On for characteristic #1, I receive data for #1 at a 25Hz frequency
  • If I toggle CCCD On for characteristic #2, I don't receive any data for #2 (still receiving data for #1)
  • If I toggle CCCD Off for characteristic #1, I then receive data at a 25Hz frequency for #2
  • If I toggle CCCD On for characteristic #1, I don't receive any data for #1 (still receiving data for #2)

Looks like s130 dongle is unable to receive a huge amount from two different characteristics.

Note that, in the mean time, CCCD is On for battery level characteristic and I receive this one correctly in any configuration (a battery level is sent every few seconds, so frequency is very low).

Is this a bug? A known issue? A bad configuration I'm using (as it works on Android, I know the problem does not come from my BLE device)...

Parents
  • 0

    I'll have to ask the team who designed the firmware to be able to answer your question. Anyway, even if we handle error codes here, it won't fix the s130 limitation.... By the way, my connection interval is 6ms and I'm receiving values from each caharacteristic at 250Hz (so every 40ms). So it should work better (having 6 connection interval between two samples), shouldn't it? But the two values are notified synchonously (sent at the same time every 40ms, this may be the problem). Is there any chance to have s130 be able to work as Android phone works in the near future?

Reply
  • 0

    I'll have to ask the team who designed the firmware to be able to answer your question. Anyway, even if we handle error codes here, it won't fix the s130 limitation.... By the way, my connection interval is 6ms and I'm receiving values from each caharacteristic at 250Hz (so every 40ms). So it should work better (having 6 connection interval between two samples), shouldn't it? But the two values are notified synchonously (sent at the same time every 40ms, this may be the problem). Is there any chance to have s130 be able to work as Android phone works in the near future?

Children
No Data
Related