Connecting nRF5340 LE Audio to other LE Audio equipment

Hi,

I'm trying to connect the nRF5340 LE Audio example to another LE Audio equipment: VOCE by Nexum (https://www.nexum-design.com/

I asked Nexum if this was possible and got this reply:

Hi, This is totally ok if you set VOCE as Auracast TX mode. but please note, the standard sample rate of Auracast is 24K sample rate. And VOCE now is set by 48Kh. We will upgrade our VOCE to support 16 / 24Khz by next upgrade. now, you need to make sure nRF5340 as Auracast RX device can also support 16bit/48K sample rate. BR, NEXUM

I also opened a ticket on DevZone earlier but thought this got a little off topic, 

 Building nRF5340_audio example for nRF5340-DK (not NRF5340-AUDIO-DK) 

I was able to build the example and connect two nRF5340-Audio-DK kits. 

Do you have any advice for how to attack this?

I'm currently trying out different config parameters in addition to adding LOG_INF(...) to see if nRF5340 sees the VOCE device. But i have't got any closer..

Thanks in advance for any reply on this,

Best,

Håkon 

Parents
  • Hi Dejan,
    thanks for your reply,

    I would like VOCE to be connected to a microphone and transmit on a broadcast stream, and then setting up multiple nRF5340 as receivers and connect them to speakers.

    Initially I want to connect the two devices in any way so I can see that they are compatible, then I can use that as a baseline for further development. So if you think switching roles would be easier I can try that first.  

    BR,
    Håkon

  • Hi Håkon,

    Our nRF5340 audio in BIS mode supports 16 KHz/24 KHz/48 KHz and it is currently set in compile time. You could consider even replacing VOCE with nRF5340 audio device. This can be done since nRF5340 audio can be set as BIS gateway using microphone as audio source.

    Best regards,
    Dejan

  • Hi Dejan,

    Is it possible to modify nRF5340 Audio to support ISO intervals sendt from VOCE?

    Best regards,
    Håkon

  • Hi Håkon,

    As a workaround, it should be possible to disable presentation and drift compensation, but this may cause stability issues and potentially other issues as well. Therefore, I would recommend that you wait for the official support of the current VOCE ISO interval (of 20 ms) from our side.

    Best regards,
    Dejan

  • Hello,

    I'm piggy backing on this topic.

    I'm trying to do exactly the same thing:

    being able to send or receive audio data to a VOCE device.

    using latest sdk 1.3 (controller version 3330), I am able to sync with the VOCE stream.

    I've added some log to deciupher the PA data

    it uses the following BASE info:

    bt_hci_core: bt_data_parse_log(): Len: 41, Type: x16 (BT_DATA_SVC_DATA16)
    bt_hci_core: bt_data_parse_log(): svc: x1851
    bt_hci_core: bt_data_parse_log(): Data: Basic Announcement (BASE)
    bt_hci_core: base_log(): Basic Announcement (0x1851)
    bt_hci_core: base_log(): BASE, presentation Delay: 0
    bt_hci_core: base_log(): BASE, nb_subgroup: 1
    bt_hci_core: base_log(): BASE, nb_bis: 2
    bt_hci_core: base_log(): BASE, sub1, Codec: 6
    bt_hci_core: base_log(): BASE, sub1, Codec cid: 0
    bt_hci_core: base_log(): BASE, sub1, Codec vid: 0
    bt_hci_core: base_log(): BASE, sub1, Codec params size: 10
    bt_hci_core: log_codec_param(): Len: 2, Type: x1 (BT_CODEC_CONFIG_LC3_FREQ)
    bt_hci_core: log_codec_param(): Freq: x8
    bt_hci_core: log_codec_param(): Len: 2, Type: x2 (BT_CODEC_CONFIG_LC3_DURATION)
    bt_hci_core: log_codec_param(): Duration: x1
    bt_hci_core: log_codec_param(): Len: 3, Type: x4 (BT_CODEC_CONFIG_LC3_FRAME_LEN)
    bt_hci_core: log_codec_param(): Frame Len: x0064
    bt_hci_core: base_log(): BASE, sub1, Codec Meta size: 0
    bt_hci_core: base_log(): BASE, sub1, bis index: 1
    bt_hci_core: base_log(): BASE, sub1, bis data length: 6
    bt_hci_core: log_bis_data(): Len: 5, Type: x3
    bt_hci_core: log_bis_data(): unknow type: data x1
    bt_hci_core: log_bis_data(): unknow type: data x0
    bt_hci_core: log_bis_data(): unknow type: data x0
    bt_hci_core: log_bis_data(): unknow type: data x0
    bt_hci_core: base_log(): BASE, sub1, bis index: 2
    bt_hci_core: base_log(): BASE, sub1, bis data length: 6
    bt_hci_core: log_bis_data(): Len: 5, Type: x3
    bt_hci_core: log_bis_data(): unknow type: data x2
    bt_hci_core: log_bis_data(): unknow type: data x0
    bt_hci_core: log_bis_data(): unknow type: data x0
    bt_hci_core: log_bis_data(): unknow type: data x0

    Raw Data of the BASE:
    bt_hci_core: bt_data_parse_log(): Data[000..015]: x51 x18 x00 x00 x00 x01 x02 x06 x00 x00 x00 x00 x0a x02 x01 x08
    bt_hci_core: bt_data_parse_log(): Data[016..271]: x02 x02 x01 x03 x04 x64 x00 x00 x01 x06 x05 x03 x01 x00 x00 x00
    bt_hci_core: bt_data_parse_log(): Data[032..040]: x02 x06 x05 x03 x02 x00 x00 x00
    bt_audio_broadcast_sink: PD received null, force it to 10ms

    And the following Big Info:

    bt_audio_broadcast_sink: biginfo_recv(), Big Info Received, enc: 0, nb_bis: 2, iso interval:16
    bt_audio_broadcast_sink: biginfo_recv(), Big Info, sid: 8, sub_evt_count: 8, burst_number:2, offset: 0, rep_count: 4
    bt_audio_broadcast_sink: biginfo_recv(), Big Info, sdu_interval: 10000, max_sdu: 100, phy:2, framing: 0

    I can join am Ellysis sniffer trace if needed.

    While I can sync with the VOCE broadcast, I cannot receive audio properly.

    I think the reason is that nRF53 controller doe snot Manage a BN value of 2 in combination with an iso interval of 20ms.

    Since SDU interval is 10ms, it should receive 2 SDU frame every 20ms.

    However the controller is only sending one SDU frame every 20ms. so half the audio is missing.

    I have try to reproduce the same behavior with a nRF broadacster, using the BT_HCI_OP_LE_CREATE_BIG_TEST command (instead of BT_HCI_OP_LE_CREATE_BIG).

    I am able to reproduce the same (bad) behavior as soon as I set the BN value to 2 and iso interval to 20ms.

    Can you confirm this is an issue? or that it is actually a working configuration and I have done something wrong in my setup?

    At this time, I can't receive or send data to VOCE successfully by the way. still working on that. might contact them.

    If you have a new controller version that fixes this issue I will be happy to test it :)

  • Hi,

    Please find the answer in your newly opened ticket.

    Best regards,
    Dejan

  • Hej Håkon! Did you have any progress on this, I have the same kind of problems when trying to connect nrf5340 to a MoerLab Duo transmitter?

    Regards,

    Henrik

Reply Children
Related