Connection failure

The nRF52832 devices have been produced in hundreds of units. Currently, it has been found that individual central devices are problematic – connecting to peripherals often takes a very long time, whereas switching to another central device usually results in quick connections. There is a noticeable difference when testing with these two central devices. What could be the possible reasons for this? As shown in the sniffer log, the faulty central device sends multiple CONNECT_IND packets before finally establishing a connection, whereas other central devices often succeed on the very first CONNECT_IND attempt.

Parents
  • Hello,

    Do you know if the peripheral in question get any connection event for these packets, or does it simply advertise as normal during this period since the connection request packet was not received? Is it possible the peripheral here have whitelist enabled (thereby preventing other/new central devices to connect)?

    Finally, have you performed any radio test or direct test mode on the board to ensure the design is operating within specifications?

    Also, which SDK and SDK version are you using here?

    Kenneth

Reply
  • Hello,

    Do you know if the peripheral in question get any connection event for these packets, or does it simply advertise as normal during this period since the connection request packet was not received? Is it possible the peripheral here have whitelist enabled (thereby preventing other/new central devices to connect)?

    Finally, have you performed any radio test or direct test mode on the board to ensure the design is operating within specifications?

    Also, which SDK and SDK version are you using here?

    Kenneth

Children
No Data
Related