• State Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Subscribers 67 subscribers
  • Views 6178 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 125552
Options
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

nrf52832 scan channel switch time

loquat

I use nrf52832 + SoftDevices132_nrf52_3.1.0.

sd_ble_gap_scan_start() run with scan_interval=scan_window=5ms.

I look at scan-channel-switch time is about 1ms. (I analyze current consumption.) It's so many.

I want reduce switch time.

Add, I programed.

static const ble_gap_scan_params_t scan_params = { .active = 0, .use_whitelist = 0, .adv_dir_report = 0, .interval = 0x0008, /* 5ms / .window = 0x0008, / 5ms */ .timeout = 0, }; ... ... uint32_t err_code = sd_ble_gap_scan_start(&scan_params);

Parents
  • 0

    No, there are no signs that CSR chips would be superior to nRF52. I can only say that I've reached resolution of <2ms with nRF51 (meaning it registered >500 adv. packets per second) and I'm pretty sure that S132 stack on nRF52 should be in range of 500-1500 adv. events per second (at least). Note that during DTM chip is able to see one packet per 0.625ms without single failure. I'm afraid it's in your measurement set-up not in the chip (nor in the stack).

Reply
  • 0

    No, there are no signs that CSR chips would be superior to nRF52. I can only say that I've reached resolution of <2ms with nRF51 (meaning it registered >500 adv. packets per second) and I'm pretty sure that S132 stack on nRF52 should be in range of 500-1500 adv. events per second (at least). Note that during DTM chip is able to see one packet per 0.625ms without single failure. I'm afraid it's in your measurement set-up not in the chip (nor in the stack).

Children
No Data
Related