aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVadim Yanitskiy <vyanitskiy@sysmocom.de>2022-04-08 01:52:13 +0300
committerfixeria <vyanitskiy@sysmocom.de>2022-04-11 12:04:21 +0000
commit93ad8143f18f2ea8a8b9d0e05faa682be10119ac (patch)
treeb8345c5f92454f2df3cd443746b3cca6ccd4de55
parent9c8c458fe879541ea1004bbb426b0858a5581071 (diff)
BTS_Tests: tune waiting timeout in TC_rsl_ms_pwr_dyn_up
Since recenly, osmo-bts is using P_CON_INTERVAL=2 by default. This means that the MS power loop gets triggered every 4th SACCH block (1.92s), so we need more time to reach the maximim Tx power. Change-Id: I9266f7284fcdb0afa3473f575640689e334e89a8 Related: osmo-bts.git I91c505447f68714239a4f033d4f06e91893df201 Related: OS#5517
-rw-r--r--bts/BTS_Tests.ttcn6
1 files changed, 4 insertions, 2 deletions
diff --git a/bts/BTS_Tests.ttcn b/bts/BTS_Tests.ttcn
index 3a3d7cc3..06fe43b5 100644
--- a/bts/BTS_Tests.ttcn
+++ b/bts/BTS_Tests.ttcn
@@ -3042,8 +3042,10 @@ private function f_TC_rsl_ms_pwr_dyn_up(charstring id) runs on ConnHdlr {
48.058 The maximum power to be used is indicated in the BS and MS Power elements respectively. */
RSL.send(ts_RSL_MS_PWR_CTRL_with_pp(g_chan_nr, pwr_max_var));
- /* wait, then check that our power level was reduced */
- timer T1 := 10.0;
+ /* By default, the MS power loop gets triggered every 4th SACCH block (1.92s).
+ * We need 9 * 4 dB steps to get from 0 dBm to 33 dBm, so 9 * 1.92s total.
+ * Add an extra offset to avoid race conditions: +1.92s. */
+ timer T1 := 9.0 * 1.92 + 1.92;
T1.start;
alt {
[] as_l1_sacch_l1h(l1h) { repeat; }