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
  • No no no, we don't understand each other;) These levels on oscilloscope are some wires so the question is how you generate that signal. Is it debug UART or just some GPIO high/low signalling? How you detect radio events and transfer it to these levels (interrupt, PPI, some mixed method e.g. with scheduler...)? That can make single digit up to several dozens of millisecond itself as systematic error. Yes, it doesn't explain full 200-300 delay but it's important to understand what are we looking at. Now if really GAP Central devices starts with Power On Reset event then obviously it needs to boot (so start-up itself and enabling of all modules including Soft Device costs you some time) and HF + LF clock start can take 200~300ms on nRF52 (read the spec!) but... (1/2)

Reply
  • No no no, we don't understand each other;) These levels on oscilloscope are some wires so the question is how you generate that signal. Is it debug UART or just some GPIO high/low signalling? How you detect radio events and transfer it to these levels (interrupt, PPI, some mixed method e.g. with scheduler...)? That can make single digit up to several dozens of millisecond itself as systematic error. Yes, it doesn't explain full 200-300 delay but it's important to understand what are we looking at. Now if really GAP Central devices starts with Power On Reset event then obviously it needs to boot (so start-up itself and enabling of all modules including Soft Device costs you some time) and HF + LF clock start can take 200~300ms on nRF52 (read the spec!) but... (1/2)

Children
No Data
Related