laforge has submitted this change. ( https://gerrit.osmocom.org/c/osmocom-bb/+/39606?usp=email )

Change subject: trx_toolkit: correct Tx burst advance value ......................................................................

trx_toolkit: correct Tx burst advance value

Change-Id: I559e86a15a3a8b4ec725f9d381e7d28628ea9155 --- M src/target/trx_toolkit/transceiver.py 1 file changed, 2 insertions(+), 2 deletions(-)

Approvals: Jenkins Builder: Verified laforge: Looks good to me, approved pespin: Looks good to me, but someone else must approve

diff --git a/src/target/trx_toolkit/transceiver.py b/src/target/trx_toolkit/transceiver.py index 7d08bb1..ce71bb1 100644 --- a/src/target/trx_toolkit/transceiver.py +++ b/src/target/trx_toolkit/transceiver.py @@ -122,8 +122,8 @@ are separate processes that are not perfectly synchronized in time. Moreover, the transceiver needs some time to prepare a burst for transmission. This is why the time difference between Uplink and - Downlink is actually much higher on practice (20 TDMA frame periods - by default, at the moment of writing this patch). + Downlink is actually much higher on practice (currently 2 TDMA + frame periods for both trxcon and osmo-bts-trx).

In order to reflect that delay in a virtual environment, this implementation, just like osmo-trx, queues all to be transmitted