Connection current queries

Hi karanshah28,

Can you please indicate the procedure you are following for the current consumption measurements? I assume that you are getting an average current consumption. The system goes into sleep mode between advertising or connection intervals. So, having bigger connection or advertising intervals means that the system is in sleep mode more time and as a result the power consumption will be lower.

The amount of data that the device sends during a connection interval depends on the packets that the central allows to a peripheral to send. The payload for each packet with the standard MTU selection is 20 bytes. So each data that you send can carry up to 20 bytes. You can't control the how many packets the BLE will send during a connection interval because is up to the master of the connection, if he doesn't want to accept the data he just won’t accept it even if you indicate that you have more data to send. In addition, there are is not a fixed connection interval regarding your application.

Let me quickly describe you the Connection Parameters Update procedure:

外围设备,这是广告,assumes the role of a slave device, while the scanner device, which is searching for a device to connect to, assumes the role of a master device upon a connection process. The latter, is responsible for performing various mandatory actions including which channel to transmit and what event interval to use. However, following a successful connection, the slave device can propose its own preferred parameters (connection interval, supervision time-out etc) via an update connection parameter request. After that, the master responds to the slave if its demands has been approved. To do so, the peripheral device sends connection parameter update request, the negotiation procedure will happen over the air, if the commend is approved, a connection parameter updated event will take place. Please refer to Bluetooth LE specifications for getting more information regarding Update Connection Parameters.

user_gapm_conf结构保持用户的配置igurations and the device upon connection will have the connection interval from this structure. The user_connection_param_conf keeps the connection parameter update configuration. The connection intervals are defined by the central, so what you can do, is to issue a connection update request and the central will decide if it will accept the connection parameters that you have requested. If the current parameters don’t match will send a request to the central in order to update the connection parameters (the request is sent 10 seconds after the connection is established), so if the central accepts the parameters the connection will change to the specified values in the user_connection_param_conf structure.

Regarding the 1 connection event, how you are measuring it? You should measure it like the attached imaged. This is 1 connection event. I power analyzer for this measurement.

Thanks, PM_Dialog

Hi Karan,

Which is the central device you are connecting to?

BR, Paolo

Hi,

I saw in the previous thread you talked about a range extender, are you using it also here?

Are you using a custom PCB or one of our Pro starter kit + our Daugther Board?

At which distance is the Android phone from the board?

BR, Paolo

Hi Karanshah28,

0x13 means timeout disconnection.

Here are all the possible causes i could think of：

1. The app ( central device ) is killed by mobile phone system.

2. In the firmware, the ble event can not be handled timely. That means, there is a long time process in you firmware, which blocks your main process.

3. The RF perfomance is not good. For example, the power of RF TX is weak, or the frequency offset is large etc.

4. There is a compatibility probem between your mobile phone and your device. Try another mobile phone for testing in this case.

Br

Yibin

Hi karanshah28,

There are various reasons that can broken a connection down, such as moving the peer device out of the range, power failure conditions, several interferences etc. According to Bluetooth LE specifications, since the aforementioned reasons may happen without any prior warning, it is important for both the

master and the slave to monitor the status of the connection. To do so, both Central and Peripheral shall use a Link Layer connection supervision timer, in order to detect a link loss. Refer to Bluetooth core specifications for getting more information on this topic. In user_connection_param_conf configuration structure of the SDK, there is a parameter named. time_out. This is the Connection supervision timeout which defined the maximum time between two received Data Packet PDUs before the

connection is considered lost. According to the core specifications, the Connection supervision timeout shall be a multiple of 10 ms in the range of 100 ms to 32.0 sec and it shall be larger than

(1 + connection_latency) * connection_interval * 2. What is the supervision timeout that you have set to the device? If you set a longer timeout, the device will take more time to disconnect or is cannot disconnect? The CO_ERROR_CON_TIMEOUT = 0x08 error is the Connection Timeout error code indicates that the link supervision timeout has expired for a given connection.

Thanks, PM_Dialog

Hi karanshah28,

Can you please check if the code Is running after the disconnection or is gets somewhere stuck? For example, after the disconnection, what is the application doing? Does the device start advertising again after the disconnection? Are you able to detect it in the air after the disconnection and without resetting the board? Is it possible for you to use a BLE sniffer in order to check the packets that are transmitted over the air?

Which is the disconnection reason code? You can print it out in the disconnect event callback function ( user_app_on_disconnect() ) as it is already mentioned in the post.

I read again your post, and I found that the disconnection reason is 0x13. Can you please make sure for that?

“And both the time the disconnection reason was 0x13 in disconnect callback.”

The 0x13 ( CO_ERROR_REMOTE_USER_TERM_CON ) error code, named REMOTE USER TERMINATED CONNECTION and indicates that the user on the remote device terminated the connection. Do you have a custom mobile application?

“We flashed our firmware in our board and observed disconnection within 2Hours of time and sometimes within 15 minutes also. Our firmware is ble_all_in_one + Range extender driver + Some product regarding change.”

Do you have the Range extender reference design in order to try to replicate this issue? Have you done any modifications in the ble_all_in_one?

“Then to find the issue of disconnection, we flashed ble_all_in_one firware binary into DA14586 EVM board and did not observed disconnection for 10 hours. “

Can you please clarify the board? Do you mean Pro DK or the 585 Range Extender?

Then, we flashed ble_all_in_one firware binary into our board, and observed same result, i.e. did not observed disconnection for 10 hours.

The same result as below? Disconnection not happened.? Also, with or without the SkY66111?

“Then we removed Range extender driver support from our firmware code i.e our firmware code will be ble_all_in_one + Some product regarding changes.

In this case also we did not observed disconnection with mobile phone for more than 9 hours. “

你能分享更多的澄清有关吗the driver that you mentioned?

It would be better to create a new forum post in order to best track the issue of the disconnection, as the initial post was related to the connection current consumption. But it is up to you.

Thanks, PM_Dialog