Master Emulator incorrect connection interval

[Hugh]

Hi, I'm attempting to use API 2.1.3 and am experiencing some weird issues with transmission intervals. When I use UpdateConnectionParameters to set a connection interval of 250ms, I'm finding the messaging rate to be about 16Hz, and when I set a connection interval of 100ms I'm seeing around 40Hz. I tried lowering the rate to 1000ms, and am able to see 4 packets being sent within the first 50ms of the interval (I assume this is a single connection event), then around 950ms of inactivity before 4 packets being sent again. Is there some problem with the configuration? I noticed posts regarding multiple packets being sent per connection event, but none mention how to set this number, and it doesn't appear in the API documentation.

I'm not certain what type of trace will help, but I am having problems with our sniffer tool, so this is a timestamp output of SendData calls to the master emulator through our application with a connection interval of 1000ms:

19.719 Tx
19.734 Tx
19.750 Tx
19.750 Tx
20.717 Tx
20.733 Tx
20.748 Tx
20.764 Tx
21.716 Tx
21.731 Tx
21.747 Tx
21.762 Tx
22.730 Tx
22.745 Tx
22.745 Tx
22.761 Tx

Timestamps are in seconds. Any help would be appreciated.

[John]

I believe what you are describing is how Bluetooth low energy behaves. The peripheral device will attempt to send as many packets as it can as fast as it can when it gets the connection event from the central device. The central device controls how many packets the peripheral device is allowed to send per connection interval.

So, apparently your central device is limiting your peripheral to 4 packets per connection interval.

[Hugh]

If this is the case, I have a solution for it, I just didn't realize that's how it worked. Thanks!