hi,
we have a issue with updates software by using a SUOTA application.
first we scanning all a BLE devices, when devices with DA14581 wad founded than we choose a one of them at mobile application, once we choose a some device (that include DA14581) then connection started between the a mobile device ( with installed SUOTA application) and the device that include DA14851. The problem is at power consumptio while connectiot started before process of update SW.
I mean , that I cah choose by mobile application one scanned device, then connectivity session started and it last up I will click on SW update.
maybe there is some way for start connectivity betwee the application and the device only when I click on SW update instead start connectivity while I choose the device?
thanks
Hi sergey_kolen,
Correct me if i got this wrong, but as far as i understand, you mention that when you are connected to the SUOTA application you see the device drawing more power, i trust that this is due to the fact that your advertising interval is larger than the connection interval chosen between the host and the peripheral when connected (which is the default that the android uses, about 48ms if i remember correctly). Its not the SUOTA application or the SUOTA profile that consumes power, once connected, the device has to communicate with the central with steady connection intervals an i suppose that this is what you see. The device when the update starts it uses a smaller connection interval in order to perform the update. You can indicate with a connection parameter update request that a larger connection interval is required in order to cosnume less power while you are just connected, once the update starts the phone application will change the connection interval in order to allow a faster update.
Thanks MT_dialog
right.
“你可以印度语的ate with a connection parameter update request that a larger connection interval is required in order to cosnume less power while you are just connected"
how I can do it?
Hi sergey_kolen,
You will have to use the app_easy_gap_param_update_start() API. Upon connection start a timer about 10 seconds (this is what the time that the SDK uses in order not to send the update parameter during the discovery of services). When the time elapses invoke the function. You can see an implementation like the one descibed above in most of the examples in the SDK, like the ble_app_peripheral.
Thanks MT_dialog