16 Sep
2022
16 Sep
'22
9:55 a.m.
Hi Osmocom Community,
May I ask your help on this. We have a test setup with UmTrx 2.3.2 SDR. We
are trying to set the tx-attenuation and measure the power output but it
seems it doesn't reflect based on the defined configurations. We tried to
set 0, 5, 10 as values and below are the results.
[image:
0-02-03-588e9973ceef2e018e29c0b2eb576f5b7d26972bbb779b44f79c97408d360299_1c6daee34bf8ee.jpg]
[image:
0-02-06-99d6d7ce8551b10be62ea130c638b19c5475b5b4140bf2843b92a5b55d36c67c_1c6daee34bfeec.jpg]
Please see attached files for osmo configurations and logs. Thanks!
Regards,
Justin
20 Sep
20 Sep
7:21 p.m.
Hi,
which versions of the osmocom CNI software are you using?
--
- Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
21 Sep
21 Sep
9:53 a.m.
Hi Pau,
We are using the split stack version. Most of the commits have a September
version.
Below are the commit IDs:
libosmocore - 812766e231a5dc509e5a96837dcc81d6b0ec37a5
libgtpnl - 6954da78fb08b7aa0b7f881444fd909fd2fcfdd3
libosmo-abis - 74c8eba5ada3483eb99201c1cdf63266a8bd2544
libosmo-dsp - 1dfd800e0c8f8aad04f814dfb1445d70ec0ae947
libosmo-netif - 98cc81bc98a894998a0bf606fb0f9a071b5a289b
libosmo-sccp - 71fc3224314dad9aa5d4c204c199e75f715f0801
libsmpp34 - d08cc74519c1d24726afa8dbea031165f53e204c
openbsc - 7baef66a612651cccc656810790e58678af70b3b
osmo-bsc - b2c7d0ab32ba31cc401daf53c2170e06574b929d
osmo-bts - 9b7a48421c84c3d055af8bd680ebbe24f87ee8b2
osmo-hlr - 78a9f92fda79bf8c21c1216363e724f17fdff4a9
osmo-mgw - e39ae87ea397cb2213520e184960feac0d696636
osmo-msc - be768ac302812426b148b48289cd4c39255ff270
osmo-sip-connector - 8120b11eaaddd99cee482448f35b917d607bd545
osmo-trx - 2f20c564bf6af5ae74f3669086797ab49bc8dbd0
UHD-Fairwaves - 20ab77fe91b11841ab176c3b12c4fe94ee789adf
uhd - aea0e2de34803d5ea8f25d7cf2fb08f4ab9d43f0
Regards,
Justin
On Wed, Sep 21, 2022, 3:21 AM Pau Espin Pedrol <pespin(a)sysmocom.de> wrote:
Hi,
which versions of the osmocom CNI software are you using?
--
- Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
10:26 a.m.
Hi,
attenuation is controlled in first place by osmo-bts, which gets
information about the nominal Tx power from the currently running device
from osmo-trx, by using TRXC protocol. BTS sends "NOMTXPOWER" command
and osmo-trx answers with "RSP NOMTXPOWER <dBm>".
Then osmo-bts tells osmo-trx which attenuation to apply based on the
nominal Tx power by means of using "SETPOWER" or "ADJPOWER" TRXC
commands.
I don't see any "NOMTXPOWER" "SETPOWER" or "ADJPOWER"
TRXC protocol
command in the logs of osmo-trx or osmo-bts, so I bet you don't have
osmo-bts properly configured to set the attenuation.
Maybe you didn't set enough verbosity for the TRXC category in logs,
debug would be great.
So have a look around those TRXC command strings in osmo-bts and
osmo-trx code, those are the ones in charge of setting attenutation.
In any case, the UmTRX is probably going to provide wrong information to
the BTS when it asks for the nominal Tx Power, since it is using the
B210 device values as fallback, as warned here:
<0005> UHDDevice.cpp:250 No Power parameters
exist for device UmTRX
4/1 Tx/Rx SPS on band GSM900, using B210 ones as fallback
To fix that, have a look in osmo-trx.git, grep for "struct
dev_band_desc", and add entries to the table called
"dev_band_nom_power_param_map" in UHDDevice.cpp (and submit a patch to
gerrit ;).
See also:
* osmo-bts User Manual "14.2.3 Configuring power ramping"
https://ftp.osmocom.org/docs/latest/osmobts-usermanual.pdf
* osmo-trx User Manual "19.2.1 Power Control"
https://ftp.osmocom.org/docs/latest/osmotrx-usermanual.pdf
10:30 a.m.
Hi,
btw you can find more information on the process of filling in the gain
tables for each device here:
https://osmocom.org/issues/4583
--
- Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
25 Oct
25 Oct
6:10 a.m.
Hi Pau,
We are now able to achieve the correct value when we are setting
tx-attenuation using B210. However, using UmTRX 2.3.1 SDR we are still
encountering this error
*<0005> UHDDevice.cpp:250 No Power parameters exist for device UmTRX4/1
Tx/Rx SPS on band GSM900, using B210 ones as fallback *even we already add
entries to "dev_band_nom_power_param_map" in UHDDevice.cpp.
[image: image.png]
[image: image.png]
Please see attached file for logs. Thank you.
Regards,
Justin
On Wed, Sep 21, 2022 at 6:30 PM Pau Espin Pedrol <pespin(a)sysmocom.de> wrote:
Hi,
btw you can find more information on the process of filling in the gain
tables for each device here:
https://osmocom.org/issues/4583
--
- Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
8:33 a.m.
Hi Justin,
You could start by sharing the patch with the modifications you mention,
in gerrit or here.
Quick look at the log I see:
"UHDDevice.cpp:250 No Power parameters exist for device UmTRX 4/1 Tx/Rx
SPS on band GSM900, using B210 ones as fallback"
hence line 250, which is the current line in master. So not sure if you
are really running the modified version, since I'd expect that line to
be higher if you added entries to the dev_band_nom_power_param_map table.
Regards,
Pau
--
- Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
11:45 a.m.
Hi Pau,
It seems that the said errors are now gone after rebuilding the osmo-trx.
But osmo-bts keeps on restarting. I've attached the logs and UHDDevice.cpp
file for your reference.
Regards,
Justin
On Tue, Oct 25, 2022 at 4:33 PM Pau Espin Pedrol <pespin(a)sysmocom.de> wrote:
Hi Justin,
You could start by sharing the patch with the modifications you mention,
in gerrit or here.
Quick look at the log I see:
"UHDDevice.cpp:250 No Power parameters exist for device UmTRX 4/1 Tx/Rx
SPS on band GSM900, using B210 ones as fallback"
hence line 250, which is the current line in master. So not sure if you
are really running the modified version, since I'd expect that line to
be higher if you added entries to the dev_band_nom_power_param_map table.
Regards,
Pau
--
- Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
1035
days inactive
1074
days old
7 comments
2 participants
participants (2)
-
Justin Mark Repollo -
Pau Espin Pedrol