This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

About the obstacle which is at the time of Gzll communication.

Hi, I suffer from the phenomenon which can't sometimes maintain communication between the 32.8ms at Gazell communication at present. When not writing in SoftDevice, this phenomenon doesn't occur.

The condition that I confirmed the upper problem and the parameter are as follows. Module:nRF51822. SoftDevice:s110_nrf51822_7.1.0. SDK:nRF51_SDK_7.2.0. Sample Project:gzll_device_ack_payload_pca10028.uvprojx and gzll_host_ack_payload_pca10028.uvprojx. lib File:gzll_sd_resources_arm.lib.

Change parameter: maximum number of TX attempts is 100. Device channel selection policy is CURRENT. Set the radio datarate is NRF_GZLL_DATARATE_1MBIT. Set the timeslot period is 900us. Send Data Payload is 32.

Time is usually every 1.8 ms and communication is done, but the section which can't sometimes do communication between the 32.8ms can be done. When SoftDevice isn't written in, the section which can't communicate doesn't occur.

Thank you.

  • can you please explain clearer, I am unable to understand your description.

  • I'd like to communicate using Gazell. The parameter was changed because I'd like to send and receive with speed as early as possible. It could be sent and received now by the early speed by changing the parameter. But SoftDevice has been just written in, the problem that the one which could be sent and received can't communicate during 32.8ms by some reasons generated data periodically.

    I'd like to settle this problem. Is that possible? Or is it impossible?

  • I am not sure if this is possible, but the expert in this is in vacation and we have kept this case open quite long. I have to close this is no response. Open a new one if you need.

Related