Regarding nrf5340 ISO interval

[Hejdern]

Maybe this is something I have overlooked, but I'm interested in running the nrf5340 audio dev with a different ISO interval than 10 ms. I'm looking into using 20 ms in order to support some other vendors BIG/BIS's. Is this possible? In that case how do you configure it?

Thanks,

[SwRa]

Hi Henrik,

Is the customer working on BIS headset.? In that case, they do not need to change the ISO interval to handle intervals other than 10ms in the latest v2.6.0 of the nRF Connect DK. On testing with a broadcaster from phone, which is using 30ms SO interval, our headset could handle it without making any changes.

Regards,

Swathy

[Hejdern]

Thanks for your reply!

The setup is that running nrf5340 2.6.0 as a broadcaster towards the other device will not work. Running it the opposite way, letting the other device be a broadcaster and the nrf5340 be a BIS headset then most often only the right channel can be received (I can supply logs later on). Anyway, using the iso_receive tool on the nrf5340 shows that the ISO interval on the other device is 40 ms:

BIG INFO[0]: [DEVICE]: 54:B7:E5:CD:35:4B (public), sid 0x08,

num_bis 2, 

nse 12, 

interval 0x0020 (40 ms), 

bn 4, 

pto 0, 

irc 3, 

max_pdu 120, 

sdu_interval 10000 us, 

max_sdu 120,

phy LE 2M, without framing, not encrypted

PER_ADV_SYNC[0]: [DEVICE]: 54:B7:E5:CD:35:4B (public), tx_power 127, RSSI -30, CTE 0, data length 42, data: 29165118000000010206000000000a020108020201030478000001060503010000000206050302000000

Therefore I would like to setup the nrf5340 to run with ISO interval 40ms (20 ms in the original question was wrong) as a test to see if this can make the other device receive correctly. An interesting observation is that nrf5450 running 2.4.2 works as a broadcaster towards the other device, but not 2.6.0. Can you point me in a direction of where to find the detailed changes between 2.4.2 and 2.6.0?

[SwRa]

Hi Henrik,

Sorry for the delay.

Hejdern said:

An interesting observation is that nrf5450 running 2.4.2 works as a broadcaster towards the other device, but not 2.6.0.

Could you share the log for these? Also, did you make any changes to the application.? We can try to replicate the issue here.  

The changes between different versions of the SDK's and the updates are documented in the release notes:https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.6.0/nrf/releases_and_maturity/release_notes.html 

Regards,

Swathy