Unable to Effectively Configure Procedure Parameters in Channel Sounding on nRF54L15 DK

Question

Hello, 
 I'm currently working with the channel_sounding_ras_initiator project on the nRF54L15 DK , using the nRF Connect SDK from the latest main branch on GitHub ( nrfconnect/sdk-nrf ). My main focus is on configuring the procedure parameters in Channel Sounding. However, I’ve noticed that the parameters I set do not take effect as expected. 
 I’m particularly interested in the following timing parameters: 
 
 max_procedure_len 
 min_procedure_interval 
 max_procedure_interval 
 min_subevent_len 
 max_subevent_len 
 
 Although I configured them as shown in the source code, the actual results do not match the configuration. For example, I set min_procedure_interval to 5, but the actual procedure_interval is 3. 
 
 In another case, I set the subevent length to 50000, but the actual configured value is different. I'm aware that the BLE 6.0 specification limits the number of steps in one event to 160, which would correspond to about 48000. However, this doesn’t seem to fully explain the discrepancy.

Additionally, in that case, the procedure_interval does match the configured min_procedure_interval , which makes the behavior inconsistent and unpredictable. 
 Overall, I find that the actual configured procedure parameters do not reliably match the values I set in the code , and I’ve spent a significant amount of time trying to tune them. This is especially problematic because my current task requires precise timing control . 
 I’ve tested this across multiple SDK versions, from v2.9.0 to the latest , over the past 2–3 months. Interestingly, the behavior and issues differ between SDK versions, which adds to the confusion. 
 Therefore, I would like to ask: 
 
 What are the internal rules or constraints that govern how these procedure parameters are applied? 
 Are there limitations or default overrides in the SDK that are not clearly documented in the BLE specification? 
 
 It’s currently very difficult to achieve the level of timing control that the Channel Sounding feature initially promised, due to these inconsistencies. 
 Thank you for taking the time to consider this issue!