the conflict of timer gazell wait for ack and the soft timer

[pipixia_8_8]

hi

im add the gzll funcation of project:

nRF5_SDK_16.0.0_98a08e2\examples\proprietary_rf\gzll\gzp_dynamic_pairing\device

to the project :

nRF5_SDK_16.0.0_98a08e2\examples\ble_peripheral\ble_app_hids_keyboard

and it can run well ,and the host can recive the data of device,but when i modify the timer interval of battery timer,when the value less 80ms，the gzll cant work ,and i find the reson is the 

funcation of gzp_delay_rx_periods and gzp_tick_sleep_rx_periods .and i browser the page of gzll,

the timeslot is 504us in the project ,but the delay of gzp_delay_rx_periods   up than 200 000 us ,i cant understand why the timer  is so long？

 i want to know  if the conflict between the  gzll delay time for ack and the 5ms soft timer can be solve？and how?

[Kenneth]

Hi,

I believe that during gazell pairing that the gzp_delay_rx_periods() delays on the device side is to allow the host to generate the various keys, this take some time for hosts that are using the 8051MCU (e.g. a delay of 200ms is required on the device).

During gazell pairing other tasks (e.g. battery timer) can be stopped or run with lower interval on the device.

Best regards,
Kenneth