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

Mix BLE audio and custom BLE Characteristic

bojan

Hello, everyone!

I'm interested to know about the possibility of mixing BLE audio and custom BLE Characteristic in one single nRF5340 application.

For example, we would like to mix:

  1. A True Wireless Earbud (TWS) BLE audio topology with mono output and microphone input for two-way audio communication and
  2. Custom BLE Characteristic that will be used for transferring data collected from various sensors

If there is no possibility to mix BLE audio with the Custom BLE Characteristic for data transfer, would it be possible to have run-time reconfiguration and change the desired BLE profile during run time?

I know that we must have LE Audio Controller for nRF53 app binary implemented in the network core of nRF5340 for BLE audio profile. Is this any blocker for using custom BLE characteristic for data transfer?

Thanks in advance for your time and efforts.

Sincerely,
Bojan.

  • 0

    Hi Bojan,

    Yes, it is possible to setup a custom GATT Characteristic when you are using the BLE Audio feature together with the LE Audio Controller.

    Could you please give a little more details on which devices have to connect to which for the sensor data in your example? There is a limit on the number of concurrent connections a device with the LE Audio Controller can maintain.

    Hieu

    Due to Christmas & New Year Holidays, our team is currently understaffed and will take longer than usual for responses and follow-ups. Our apologies for the inconvenience.

  • 0 in reply to Hieu

    Hello,  

    Sorry for the late reply.

    We would basically have one single BLE Central device (e.g the smartphone) that will be used to establish a connection with nRF53.

    We would need to:

    1. Establish two-way audio communication (TWS topology) between nRF53 and BLE Central
    2. Collect the data from various sensors and transfer them to the BLE Central device using a custom-defined BLE Service with multiple custom BLE Characteristics.

    Those two should exist in parallel (ideally) or it would be nice if we could reconfigure the BLE part during run-time to run either in TWS BLE audio mode or in data collection mode.

    I hope it's now clear what we want to achieve.

    Sincerely,
    Bojan.

  • 0 in reply to bojan

    Hi Bojan,

    Thank you for the information. I am out of office for the rest of the week so I will answer you latest by the end of next Tuesday, Jan 10. If you need support more urgently, please let me know and I will arrange some alternatives.

    Best regards,

    Hieu

  • 0 in reply to Hieu

    No worries, , it's not urgent. We are in the research and development phase.

    Thanks for your readiness to help, though!

    Looking forward to hearing from you.

    Sincerely,
    Bojan.

  • 0 in reply to bojan

    Hi Bojan,

    Thank you for your patience.

    I understand that, both your two-way audio communication (ISO Link) and the sensor data communications (ACL Link) are between the same nRF53 device and the same BLE Central, is this right?

    If so, this is doable. The two "links" can run at the same time, and you should not have to reconfigure them during run time.

    Are you going to send sensor data often, or will the data be large? Currently, the LE Audio Controller has some difficulties running both an ISO Link and a high throughput ACL Link at the same time. It is being improved, but that is the current state.

    Best regards,

    Hieu

Related