• State Not Answered
  • Replies 5 replies
  • Subscribers 65 subscribers
  • Views 251 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 327957
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs

Data Loss Issue with nRF52832 and nRF52833 Gateways [nRF52 SDK]

Gavin

Hi team,

I'm currently facing an issue with the nRF52832 and nRF52833 gateways in our setup. Here are the details:

Current Configuration:
- Scan Interval: 100ms
- Scan Window: 75ms

With these parameters, we're experiencing a regular interval of 3 minutes where data reception drops.

Temporary Solution:
- I've tried adjusting the parameters to:
- Scan Interval: 50ms
- Scan Window: 50ms
- This has improved the situation but still, there are instances where data is not received for up to 30 seconds.

Testing:
- I've simulated device broadcasts using the DK development board, and the same phenomenon occurs.

I'm not clear on the root cause of this issue and have only been able to mitigate it by tweaking the parameters.

Questions:
1. Has anyone else encountered a similar problem?
2. Do you have any suggestions or insights that might help resolve this issue?

Environment:
- SDK: nRF5_SDK_17.1.0_ddde560
- Chips: nRF52832, nRF52833

Any help or guidance would be greatly appreciated. Thank you in advance for your time and expertise.

  • 0

    Hello,

    Are you doing anything else at the time when you are seeing the dropouts? Advertising? In a BLE connection? Any other protocol running at the same time? 

    And do you see any logs from your gateway? Any errors being printed? And have you tested having two gateways in the same area? When one drops out, does the other still see advertisements? Or can you use nRF Connect for Mobile/iOS/Android to check if there are actually advertisements around at the time?

    Best regards,

    Edvin

  • 0 in reply to Edvin

    Hi Edvin,

    Sorry, I did't explain it well.

    Edvin said:
    Are you doing anything else at the time when you are seeing the dropouts? Advertising? In a BLE connection? Any other protocol running at the same time? 

    Just BLE advertising, no connections, no other protocol running, only a gateway scanning and multiple tags broadcasting

    Edvin said:
    And do you see any logs from your gateway? Any errors being printed? And have you tested having two gateways in the same area? When one drops out, does the other still see advertisements? Or can you use nRF Connect for Mobile/iOS/Android to check if there are actually advertisements around at the time?

    Right now, I'm just testing with one gateway, so it's a one-to-many deal, not using multiple gateways to scan the same tags at the same time. I'll check that out later.

    But when this happens, I can still get data with nRF Connect, which should mean the tags are broadcasting fine, right?

    The gateway isn't showing any other errors.

    I haven't tried using the DK board to scan and check the data yet, but I can keep testing.

    Also, on the chip, when there's a problem, the 'ble_evt_handler' callback function doesn't get any advertising events back

  • 0 in reply to Gavin
    Gavin said:
    Just BLE advertising, no connections, no other protocol running, only a gateway scanning and multiple tags broadcasting

    So that means that you are advertising and scanning? Or only scanning? If you are advertising at the same time, what is your advertising interval?

    Gavin said:
    But when this happens, I can still get data with nRF Connect, which should mean the tags are broadcasting fine, right?

    Yes. If you see that the RSSI on nRF Connect is changing, it means that you are receiving advertisements live. Also, if you have multiple tags advertising, they probably don't all fail at the same time. 

    Gavin said:
    Also, on the chip, when there's a problem, the 'ble_evt_handler' callback function doesn't get any advertising events back

    Do you see any other events during the problem? How about right before or right after? Any particular events? (try printing out the default event IDs, in case there is an event that you do not check for in the event handler. 

    Are you able to replicate this on a DK as well? Or only on the custom HW?

    Best regards,

    Edvin

  • 0 in reply to Edvin

    Hi Edvin,

    Edvin said:
    So that means that you are advertising and scanning? Or only scanning? If you are advertising at the same time, what is your advertising interval?

    scanning only

    Edvin said:
    Do you see any other events during the problem? How about right before or right after? Any particular events? (try printing out the default event IDs, in case there is an event that you do not check for in the event handler. 

    I'll test it and let you know ASAP. Thanks

  • 0 in reply to Gavin

    Just on the off-chance, peripherals might have this ..

    #define APP_ADV_DURATION 18000 /**< The advertising duration (180 seconds) in units of 10 milliseconds. */

Related