Hi Dialog.
不同的SDK5。x和SDK3。x, I found "APP_PARAM_UPDATE_REQUEST_TO"
I think this value is timer for connection parameter update request.
My question is why this value is 10sec? It so to late..
Is this minimum value?
In my case, I use SDK3.0.10.x and I was maked same timer for connection parameter update request.
and vlaue is about 200ms
Which value is correct?
Thanks
Device:
Hi build77,
Yes it is the timer that after the connection proccess issues an UPDATE_REQUEST to the host. This isn't the minimum allowed value, in general the value of the parameter update request depends on the OS of the host. You should issue your UPDATE_REQUEST after the host has finished sending his parameters, so in order to be on the safe side we are waiting for a long period in order to be certain that the host has finished sending.
Thanks MT_dialog
Thanks for reply.
In document "RW-BLE-GAP-IS" 5.5.1 GAPC_PARAM_UPDATE_CMD
"Note: If slave of connection request update of connection parameters, a 30s timer will be started in order to
let master to reply. If timer ends without response from master, link is automatically disconnected."
How can I block disconnection of 30s timer?
Instead of 30s timer, When master send refuse, I want to re-request update params to master.
Thanks.
Hi build77,
You can't change the 30s timer, what you can do is, when you take the response from the master you can catch in the gapc_cmp_evt_handler the GAPC_UPDATE_PARAMS case and define the behaviour of your application in case of rejected parameters to the master. You can have a look at the DSPS project and see how it handles the rejected parameter case.
Thanks MT_dialog
Hi build77,
You can't change the 30s timer, what you can do is, when you take the response from the master you can catch in the gapc_cmp_evt_handler the GAPC_UPDATE_PARAMS case and define the behaviour of your application in case of rejected parameters to the master. You can have a look at the DSPS project and see how it handles the rejected parameter case.
Thanks MT_dialog