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

BLE scanning in multiprotocol BLE/Thread solution

Hi, 

I have a multiprotocol application and I'd like to do BLE scanning for as long as it's possible. For now I made 30% to 70% BLE to Thread, and it's the most I can give to BLE without any errors. Is there a possibility to scan longer e.g. 50% of a time? Or is a 70% a limit that cannot be exceeded?

Thanks,

Marek

Parents
  • Hi Marmo,

    The answer is not straight forward. Thread nodes has I think around ~10 seconds polling interval so that the parent won't timeout and mark the child as lost. The safest for you is to give BLE more time when the node is SED (Sleepy End Device), The nice thing is that if SED should send Data Poll Request (to pull buffered frames from parent) while we are currently on BLE, we have in build mechanisms to postpone this operation after we will get timeslot 

    In general as long as you give Thread time to poll for its child + depending on the packets transmission, you can give BLE more than 50% of the time. But we cannot give you any conclusive benchmarking numbers as we  do not have those numbers yet. 

Reply
  • Hi Marmo,

    The answer is not straight forward. Thread nodes has I think around ~10 seconds polling interval so that the parent won't timeout and mark the child as lost. The safest for you is to give BLE more time when the node is SED (Sleepy End Device), The nice thing is that if SED should send Data Poll Request (to pull buffered frames from parent) while we are currently on BLE, we have in build mechanisms to postpone this operation after we will get timeslot 

    In general as long as you give Thread time to poll for its child + depending on the packets transmission, you can give BLE more than 50% of the time. But we cannot give you any conclusive benchmarking numbers as we  do not have those numbers yet. 

Children
No Data
Related