|author||Pau Espin Pedrol <firstname.lastname@example.org>||2019-12-20 23:31:05 +0100|
|committer||Pau Espin Pedrol <email@example.com>||2020-01-07 16:04:04 +0100|
doc: clarify number of channels on B210 with multi-arfcn enabled
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/manuals/chapters/configuration.adoc b/doc/manuals/chapters/configuration.adoc
index 2f4986f..a194537 100644
@@ -46,15 +46,16 @@ Multi-ARFCN support is available since osmo-trx release `0.2.0`, and it was
added specifically in commit `76764278169d252980853251daeb9f1ba0c246e1`.
This feature is useful for instance if you want to run more than 1 TRX with an
-Ettus B200 device, or 2 TRX with an Ettus B210 device, since they support only 1
-and 2 physical RF channels respectively. No device from other providers or even
-other devices than B200 and B210 from Ettus are known to support this feature.
+Ettus B200 device, or more than 2 TRXs with an Ettus B210 device, since they
+support only 1 and 2 physical RF channels respectively. No device from other
+providers or even other devices than B200 and B210 from Ettus are known to
+support this feature.
With multi-ARFCN enabled, ARFCN spacing is fixed at 800 kHz or 4 GSM channels.
So if TRX-0 is set to ARFCN 51, TRX-1 _must_ be set to 55, and so on. Up to
three ARFCN's is supported for multi-TRX.
-From BTS and BSC point of view, supporting multiple TRX through multi-ARFCN
+From BTS and BSC point of view, supporting multiple TRXs through multi-ARFCN
feature in OsmoTRX doesn't make any difference from a regular multi-TRX setup,
leaving apart of course the mentioned ARFCN limitations explained above and as a
consequence physical installation and operational differences.