• State Not Answered
  • Replies 5 replies
  • Subscribers 69 subscribers
  • Views 123 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 336402
Options

Channel Sounding - Speed and Multiple Devices

MatthewP

Hi,

We are evaluating BLE Channel Sounding for indoor localization of small mobile robots. We need 2D localization within the room, so we would need to measure the distance to multiple anchors.

We have some basic questions about this:

  • How fast can a single distance measurement be performed? I've seen numbers in the range of 100ms?
  • Is it possible to be paired with multiple anchors and perform BLE CS sequentially without having to establish a new connection each time?
  • When can we expect an update of the SDK with CS support?

Thank you very much for your response.

BR, Matthew

Parents
  • 0

    Hi Matthew

    I got a reply from the devs now, and I'm still waiting on a specific answer on question 1, but here are some preliminary responses.

    1. This is very situational, but it's worth noting that CS can be started by setting the max_procedure_count=0, that means that CS procedures will continue to run on the ACL indefinitely or until explicitly disabled. In principle you could start a new CS procedure every ACL interval (minimum 7.5ms). 7.5ms is most likely not getting enough CS measurements in that time to do any accurate distance estimatio., but you can configure it so that a new procedure starts once you have collected enough CS measurements in the current CS procedure, to continuously get new measurements.

    2. Having multiple peripherals connected at the same time to do sequential CS should be possible in the current NCS 2.8.0 implementation, although we haven't done any testing on this. Note that the central device would be using a lot of memory to store CS measurements from each peripheral device it is connected to and performing CS with. The ACL interval also needs to be noticably higher for the conncetions in order to not get scheduling conflicts between different links.

    Best regards,

    Simon

Reply
  • 0

    Hi Matthew

    I got a reply from the devs now, and I'm still waiting on a specific answer on question 1, but here are some preliminary responses.

    1. This is very situational, but it's worth noting that CS can be started by setting the max_procedure_count=0, that means that CS procedures will continue to run on the ACL indefinitely or until explicitly disabled. In principle you could start a new CS procedure every ACL interval (minimum 7.5ms). 7.5ms is most likely not getting enough CS measurements in that time to do any accurate distance estimatio., but you can configure it so that a new procedure starts once you have collected enough CS measurements in the current CS procedure, to continuously get new measurements.

    2. Having multiple peripherals connected at the same time to do sequential CS should be possible in the current NCS 2.8.0 implementation, although we haven't done any testing on this. Note that the central device would be using a lot of memory to store CS measurements from each peripheral device it is connected to and performing CS with. The ACL interval also needs to be noticably higher for the conncetions in order to not get scheduling conflicts between different links.

    Best regards,

    Simon

Children
No Data
Related