we want to reduce power consumption in the connected state,
so we edit the function like that
void app_param_update_func(void)
{
struct gapc_param_update_cmd * req = KE_MSG_ALLOC(GAPC_PARAM_UPDATE_CMD, TASK_GAPC, TASK_APP, gapc_param_update_cmd);
// Fill in the parameter structure
req->operation = GAPC_UPDATE_PARAMS;
req->params.intv_min = 160; // N * 1.25ms
req->params.intv_max = 200; // N * 1.25ms
req->params.latency = 0; // Conn Events skipped
req->params.time_out = 800; // N * 10ms
ke_msg_send(req);
}
, and call the function one time in the connected state,
now the machine will disconnect with the phone at sometimes,
This situation is different from the phenomenon of different phones,
Some phones relatively long time to appear, and some appear very ordinary,
How can fix it,
Thankyou!!
Some phones a long time to appear, and some appear very frequently
Hi Dialog,
I also want to know if app_param_update_func() action affects the connection process. I set the latency to 4, will that take any compatibility problems in the connection process? Now we have some problems in reconnection, but not sure if that because of app_param_update_func().
Can anyone give me a clue? Thank u very much.
Best Regards
Angie
Hi angelforest,
As far as we know there is no effect from the update parameters procedure in the connection proccess, if the host accepts the parameter update will comply to the new information your peripheral requests, if not it will just reject it.
Thanks MT_dialog
Hi MT_dialog,
Thanks for your reply.
How about MTU exchange? To improve OTA rate, we increase MTU to 140+, may a failed MTU exchange block the connection process? Will increasing MTU reduce phone compatibility?
Thank u
BR
Angelforest
Hi angelforest,
When the MTU exchange is being perfomed the host might reject the request by your device but will not terminate the connection process it will just keep on working with the minimum agreed MTU and more packets. I dont think that will reduce compatibility.
Thanks MT_dialog