https://devzone.nordicsemi.com/f/nordic-q-a/66857/why-does-ncs-nrf-throughput-sample-not-allow-command-line-control-of-key-parametersThe nRF5 SDK&#39;s throughput sample (ble_app_throughput) provided very convenient shell commands to configure key parameters affecting throughput in a connection, such as ATT MTU size, Data Length, Connection Interval, and Preferred PHY (reference the SDKen-USTelligent Community 13Fri, 09 Oct 2020 06:38:33 GMThttps://devzone.nordicsemi.com/thread/273923?ContentTypeID=1Fri, 09 Oct 2020 06:38:33 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6f635636-b84d-4c9b-82be-8dd58e5094cbAmanda Hsieh<p>Hi Mike,</p> <ul> <li>Because several of these config&#39;s(PHY, DLE) cannnot be set at runtime / use an API at runtime. It is something that we will improve in the future.</li> <li>Since&nbsp;<span>nRF5340 runs the sample app on the application CPU, it requires consistent configuration settings as the network CPU. Please see the&nbsp;<a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/throughput/README.html?highlight=throughput#requirements">requirements</a>&nbsp;documentation.&nbsp;</span></li> </ul> <p><span>-Amanda H.</span></p><div style="clear:both;"></div>