Crash of UmTRX transceiver with dual TRX

Thomas Tsou tom at
Mon Jul 8 14:34:31 UTC 2013

On Mon, Jul 8, 2013 at 3:27 PM, Andreas Eversberg <andreas at> wrote:
> Thomas Tsou wrote:
>> Should we now assume that each TRX is setup an independent manner?
> i see no problem with that reject. i think it makes sense to reject TSC,
> if it does not match the TSC of first TRX. since trx manager interface
> seems to be designed to handle each TRX individually (even might be
> possible to run on different transceivers for one BTS), i would think it
> is a good idea to set TSC for every TRX.

We can easily move to separate TSC settings be removing the static
identifier. The only issue then is that OpenBTS will no longer work.
Perhaps the larger limitation is that we can't set TSC dynamically
after POWERON. This is because the midamble correlation sequence is
regenerated and is not thread safe.

In summary, we can easily have separate TSC, but they need to be set
before the POWERON command is received.


More information about the UmTRX mailing list