SimonMerrett

I have just 'upgraded' to 4dBm transmit power on the keyboard transmitters and set them to 200 retries instead of 100. There's still some potential to handle e.g. `nrf_gzll_device_tx_failed()` with...

> can you share you compiled hex for transmitters ? i will add them to my keyboard and test it out. > also it will be on keyboard or on...

In receiver `main.c` ``` // Define channel hoping parameters #define channel_table_size 6 #define timeslots_per_channel 2 #define GZLL_RX_PERIOD 1800 // supports 1Mbps static uint8_t channel_table[channel_table_size]={4, 25, 42, 63, 77, 33}; ```...

Not to worry, and from my testing so far, all it does is makes the channel hopping on par with the non-channel hopping version. I still get missed keypresses, sadly....

> it must be your adapted FW Brilliant, thanks for the confirmation - now I can go and feel like time spent addressing this is worth doing. As an update,...

> You've made the RX twice the TX haven't you ? Yes! it looks like I have. Will swap that round and try it out.

@LucidityCrash I think I got confused by [this ](https://developer.nordicsemi.com/nRF5_SDK/nRF51_SDK_v4.x.x/doc/html/group__gzll__02__user__guide.html) when you scroll to the bottom: ``` /* On Host and Device */ timeslots_per_channel = 2; channel_table_size = 3; nrf_gzll_set_timeslot_period(GZLL_RX_PERIOD /...

I think what I implemented was "correct" frequency hopping but for a single Tx/Rx pair, rather than a 2*Tx/Rx trio. If the boards are 1800 and Rx is 900, I...

> Either my keypresses are not recognized or they come in way after I press the key. Very similar to (one of) my issue(s): > Often I will have to...

As I'm part of the problem here I thought I'd change the timings and see what happens. Both halves of my keyboard are now ``` nrf_gzll_set_timeslot_period(GZLL_RX_PERIOD); ``` with the receiver...