This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Connection problem

Currently using nordic52832 to develop products that use batteries.

We found that the problem is that when the BLE module is connected successfully, it takes 200ms to send the message.

How can I improve this problem?

We need a very short grip time and turn off the power.

Parents
  • OK so this makes it even more confusing;) What is exact configuration of your test system and sequence of steps? Can you take RF trace by some BLE sniffer? Then you can clearly say what part is spent before even GAP Peripheral starts advertising, then how long it takes to GAP Central to pick-up the advertisement and issue CONNECT_REQ and finally how long the LL and GATT procedures take before any meaningful exchange happen on APP layer. Without this you can hardly debug and optimize your set-up. There can be many easy/stupid mistakes or misunderstandings like nRF5x starting with LF crystal takes 200-400ms just there so you need o use internal RC or synth from HF if you require start in <100ms range etc.

Reply
  • OK so this makes it even more confusing;) What is exact configuration of your test system and sequence of steps? Can you take RF trace by some BLE sniffer? Then you can clearly say what part is spent before even GAP Peripheral starts advertising, then how long it takes to GAP Central to pick-up the advertisement and issue CONNECT_REQ and finally how long the LL and GATT procedures take before any meaningful exchange happen on APP layer. Without this you can hardly debug and optimize your set-up. There can be many easy/stupid mistakes or misunderstandings like nRF5x starting with LF crystal takes 200-400ms just there so you need o use internal RC or synth from HF if you require start in <100ms range etc.

Children
No Data
Related