https://osmocom.org/https://osmocom.org/favicon.ico?16647414092016-06-13T12:58:10ZOpen Source Mobile CommunicationsOsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=15762016-06-13T12:58:10Zlaforge
<ul><li><strong>Assignee</strong> set to <i>msuraev</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=15792016-06-13T13:02:50Zlaforge
<ul><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' disabled> <i>set-up osmo-bts-trx locally for testing</i> added</li><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' disabled> <i>do some manual testing with different codecs and gprs</i> added</li><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' disabled> <i>verify multi-trx functionality (with two trx)</i> added</li></ul><p>please make sure that Lazlo joins you for setting up a network with osmo-bts-trx, so he can use this information to subsequently integrate osmo-bts-trx into the osmo-gsm-tester setup.</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=15952016-06-14T09:38:02Zlaforge
<ul><li><strong>Priority</strong> changed from <i>High</i> to <i>Urgent</i></li></ul> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=16232016-06-16T15:03:08Zmsuraev
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul><p>Waiting for suitable hw.</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=16292016-06-18T08:16:09Zlaforge
<ul></ul><p>msuraev wrote:</p>
<blockquote>
<p>Waiting for suitable hw.</p>
</blockquote>
<p>A B210 will be with you on monday.</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=16342016-06-22T11:00:17Zmsuraev
<ul></ul><p>The following issue was observed:<br />trx_if.c:380 transceiver (phy0.1) rejected TRX command with response: 'RSP SETTSC 1 7'</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=16352016-06-22T14:58:53Zmsuraev
<ul></ul><p>Disabling SETTSC command for all phy except 0 allows bts to start but calls do not go through.<br />Test commands:<br />sudo chrt 20 ./Transceiver52M/osmo-trx -c 2 <br />sudo chrt 15 ./src/osmo-bts-trx/osmo-bts-trx -t 2 -c ~/.config/osmocom/osmo-bts-mtrx.cfg -d DRTP:DCC:DRSL:DL1C<br />Tested on USRP B210.</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=16772016-06-24T07:49:13Zmsuraev
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-1 priority-lowest closed" href="/issues/1750">Bug #1750</a>: DTXu/DTXd support for osmo-bts-trx</i> added</li></ul> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=16802016-06-24T10:26:36Zmsuraev
<ul><li><strong>Related to</strong> deleted (<i><a class="issue tracker-1 status-3 priority-1 priority-lowest closed" href="/issues/1750">Bug #1750</a>: DTXu/DTXd support for osmo-bts-trx</i>)</li></ul> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=16812016-06-24T10:26:38Zmsuraev
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-1 status-3 priority-1 priority-lowest closed" href="/issues/1750">Bug #1750</a>: DTXu/DTXd support for osmo-bts-trx</i> added</li></ul> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=17972016-07-12T10:12:45Zmsuraev
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>New</i></li></ul> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=18282016-07-12T17:21:41Zlaforge
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Stalled</i></li></ul><p>waiting for a response from osmo-bts-trx maintainer</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=20472016-08-12T18:05:00Zmsuraev
<ul></ul><p>There are 2 ways to run multi-trx with osmo-trx:<br />1) use "-c 2" option (each arfcn get it's own channel)<br />2) use "-m" option (arfcns are multiplexed on same channel)</p>
<p>Unfortunately neither works for me. Also multiplexing (or maybe both) requires latest uhd master.<br />It's also unclear what kind of configuration changes are necessary for both modes both for osmo-bts and for openbsc. See on-going discussion in openbsc ML "multiple phy with osmo-trx".</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=20532016-08-13T10:44:37Zmsuraev
<ul><li><strong>File</strong> <a href="/attachments/2369">ggsn.conf</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2369/ggsn.conf">ggsn.conf</a> added</li><li><strong>File</strong> <a href="/attachments/2370">openbsc.cfg</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2370/openbsc.cfg">openbsc.cfg</a> added</li><li><strong>File</strong> <a href="/attachments/2371">openbsc-mc.cfg</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2371/openbsc-mc.cfg">openbsc-mc.cfg</a> added</li><li><strong>File</strong> <a href="/attachments/2372">osmo-bts.cfg</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2372/osmo-bts.cfg">osmo-bts.cfg</a> added</li><li><strong>File</strong> <a href="/attachments/2373">osmo-bts-mc.cfg</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2373/osmo-bts-mc.cfg">osmo-bts-mc.cfg</a> added</li><li><strong>File</strong> <a href="/attachments/2374">osmo-pcu.cfg</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2374/osmo-pcu.cfg">osmo-pcu.cfg</a> added</li><li><strong>File</strong> <a href="/attachments/2375">osmo-sgsn.cfg</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2375/osmo-sgsn.cfg">osmo-sgsn.cfg</a> added</li><li><strong>File</strong> <a href="/attachments/2376">README.txt</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2376/README.txt">README.txt</a> added</li></ul><p>Attaching sample configuration files and description provided by maintainer in ML.</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=22362016-10-13T13:52:47Zmsuraev
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/1775">Bug #1775</a>: LC15: No PDCH allocation across two TRX</i> added</li></ul> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=22382016-10-13T14:28:04Zmsuraev
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>10</i></li></ul><p>With recent UHD_003.010.000.000-release, mTRX is working using following commands:</p>
<p>./src/osmo-bts-trx/osmo-bts-trx -c ~/.config/osmocom/osmo-bts-mtrx.cfg -t 2</p>
<p>a) same-channel multiplex<br />./Transceiver52M/osmo-trx -m -c 2 -l INFO</p>
<p>1) voice is working on any of trx0, trx1 (tested by configuring TCH/F channels on single trx only)<br />2) gprs working (tested by configuring PDCH channels on single trx only)</p>
<p>b) separate channels<br />./Transceiver52M/osmo-trx -c 2 -l INFO</p>
<p>neither voice nor gprs are working - phone either fails to camp to network or loses connection after some time.</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=23672016-11-09T09:25:08Zlaforge
<ul><li><strong>Priority</strong> changed from <i>Urgent</i> to <i>High</i></li></ul> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=24762016-11-18T21:44:11Zlaforge
<ul><li><strong>Target version</strong> set to <i>osmo-bts-trx refresh</i></li></ul> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=27312017-01-05T16:20:07Zmsuraev
<ul><li><strong>% Done</strong> changed from <i>10</i> to <i>50</i></li></ul><p>With external 10MHz reference, using B210 and UHD_003.009.005-0-unknown on ubuntu 16.10 following was observed:<br />sudo ./Transceiver52M/osmo-trx -l INFO -x -c 2 <br />sudo ./src/osmo-bts-trx/osmo-bts-trx -c ~/.config/osmocom/osmo-bts-mtrx.cfg -t 2</p>
<p>1) both trx have PDCH and TCH/F timeslots: both test phones camp without problems, voice call is ok, voice slightly degraded.<br />2) TCH ts on trx0, PDCH on trx1 - iphone camps to network, acer fails to see it<br />3) TCH ts on trx1, PDCH on trx0 - both test phones camp to network, voice call goes through but quality is badly degraded: delays, skipped frames.</p>
<p>Following error was on OpenBSC side:<br /><0000> abis_rsl.c:1950 (bts=0,trx=1,ts=0,ss=0) ERROR INDICATION cause=SABM frame with information not allowed in this state in state=ACTIVE</p>
<p>On osmo-bts-trx:<br /><0006> scheduler.c:270 Prim for trx=1 ts=0 at fn=966278 is out of range, or channel already disabled. If this happens in conjunction with PCU, increase 'rts-advance' by 5. (current fn=966297)<br />was seen multiple times (no PCU were running)<br />also<br /><0006> scheduler_trx.c:477 TCH/F Transmitting 'bad FR frame' trx=1 ts=7 at fn=963274.<br /><0011> lapd_core.c:1511 N(S) sequence error: N(S)=6, V(R)=7<br /><0006> scheduler_trx.c:477 TCH/F Transmitting 'bad FR frame' trx=1 ts=7 at fn=963313.<br /><0011> lapd_core.c:1511 N(S) sequence error: N(S)=6, V(R)=7<br />were seen often.</p>
<p>On osmo-trx:<br />INFO 140188128442112 17:00:35.7 Transceiver.cpp:1021:driveTxFIFO: new latency: 0:8<br />INFO 140188126574336 17:00:35.8 Transceiver.cpp:1054:writeClockInterface: ClockInterface: sending IND CLOCK 940004<br />ERR 140188126574336 17:00:35.8 UHDDevice.cpp:1039:check_rx_md_err: An internal receive buffer has filled at 6.74236 sec.<br />ERR 140188126574336 17:00:35.8 UHDDevice.cpp:1039:check_rx_md_err: An internal receive buffer has filled at 6.74236 sec.<br />ERR 140188126574336 17:00:35.8 UHDDevice.cpp:1039:check_rx_md_err: An internal receive buffer has filled at 6.74991 sec.<br />ERR 140188126574336 17:00:35.8 UHDDevice.cpp:1039:check_rx_md_err: An internal receive buffer has filled at 6.74991 sec.<br />ERR 140188126574336 17:00:35.8 UHDDevice.cpp:1576:write: Skipping buffer data: timestamp=1833002 time_end=1827648<br />ERR 140188126574336 17:00:35.8 UHDDevice.cpp:1576:write: Skipping buffer data: timestamp=1833002 time_end=1827648<br />ERR 140188126574336 17:00:35.8 UHDDevice.cpp:1576:write: Skipping buffer data: timestamp=1833002 time_end=1827648<br />ERR 140188126574336 17:00:35.8 UHDDevice.cpp:1576:write: Skipping buffer data: timestamp=1833002 time_end=1827648<br />INFO 140188128442112 17:00:36.7 Transceiver.cpp:1031:driveTxFIFO: reduced latency: 7:7<br />INFO 140188126574336 17:00:36.7 Transceiver.cpp:1054:writeClockInterface: ClockInterface: sending IND CLOCK 940223<br />INFO 140188128442112 17:00:37.7 Transceiver.cpp:1031:driveTxFIFO: reduced latency: 6:7<br />INFO 140188126574336 17:00:37.7 Transceiver.cpp:1054:writeClockInterface: ClockInterface: sending IND CLOCK 940441<br />INFO 140188128442112 17:00:38.7 Transceiver.cpp:1031:driveTxFIFO: reduced latency: 5:7<br />INFO 140188126574336 17:00:38.7 Transceiver.cpp:1054:writeClockInterface: ClockInterface: sending IND CLOCK 940658<br />INFO 140188128442112 17:00:39.7 Transceiver.cpp:1031:driveTxFIFO: reduced latency: 4:7</p>
<p>Not sure if upgrading to newer UHD will help (there are no pre-build packages available for 16.10 ATM). Also it's unclear why swapping PDCH and TCH timeslots between TRXes affect network visibility for some phones.</p>
<p>In all tests ARFCN distance between TRX was 4.</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=27322017-01-05T16:50:32Zmsuraev
<ul></ul><p>Same configurations with GPRS and iphone:<br />1) works after some initial delay due to multitude of errors on OsmoPCU</p>
<p>20170105173301926 <0002> tbf.cpp:593 <abbr title="TFI=0 TLLI=0xa8d7baea DIR=DL STATE=ASSIGN">TBF</abbr> poll timeout for FN=1914254, TS=6 (curr FN 1914315)<br />20170105173301927 <0002> tbf.cpp:648 - Timeout for polling PACKET CONTROL ACK for PACKET DOWNLINK ASSIGNMENT.<br />20170105173301927 <0002> tbf.cpp:1008 - Assignment was on PACCH<br />20170105173301927 <0002> tbf.cpp:1016 - No downlink ACK received yet<br />20170105173302403 <0002> tbf.cpp:593 <abbr title="TFI=0 TLLI=0xa8d7baea DIR=DL STATE=ASSIGN">TBF</abbr> poll timeout for FN=1914358, TS=6 (curr FN 1914419)<br />20170105173302884 <0002> tbf.cpp:593 <abbr title="TFI=0 TLLI=0xa8d7baea DIR=DL STATE=ASSIGN">TBF</abbr> poll timeout for FN=1914462, TS=6 (curr FN 1914523)<br />20170105173303014 <0005> bts.cpp:1318 Got RACH from TLLI=0xa8d7baea while <abbr title="TFI=0 TLLI=0xa8d7baea DIR=DL STATE=ASSIGN">TBF</abbr> still exists. Release pending DL TBF <br />20170105173303014 <0002> tbf.cpp:447 <abbr title="TFI=0 TLLI=0xa8d7baea DIR=DL STATE=RELEASING">TBF</abbr> Software error: Pending downlink assignment. This may not happen, because the assignment message never gets transmitted. Please be sure not to free in this state. PLEASE FIX!<br />20170105173303014 <0002> bts.cpp:1347 MS supports EGPRS multislot class 10.<br />20170105173310078 <0002> bts.cpp:1347 MS supports EGPRS multislot class 10.<br />20170105173311345 <0002> tbf.cpp:593 <abbr title="TFI=0 TLLI=0xecc9d420 DIR=DL STATE=ASSIGN">TBF</abbr> poll timeout for FN=1916295, TS=6 (curr FN 1916356)<br />20170105173311345 <0002> tbf.cpp:648 - Timeout for polling PACKET CONTROL ACK for PACKET DOWNLINK ASSIGNMENT.<br />20170105173311345 <0002> tbf.cpp:1008 - Assignment was on PACCH<br />20170105173311345 <0002> tbf.cpp:1016 - No downlink ACK received yet<br />20170105173311826 <0002> tbf.cpp:593 <abbr title="TFI=0 TLLI=0xecc9d420 DIR=DL STATE=ASSIGN">TBF</abbr> poll timeout for FN=1916399, TS=6 (curr FN 1916460)<br />20170105173312303 <0002> tbf.cpp:593 <abbr title="TFI=0 TLLI=0xecc9d420 DIR=DL STATE=ASSIGN">TBF</abbr> poll timeout for FN=1916503, TS=6 (curr FN 1916564)<br />20170105173312783 <0002> tbf.cpp:593 <abbr title="TFI=0 TLLI=0xecc9d420 DIR=DL STATE=ASSIGN">TBF</abbr> poll timeout for FN=1916607, TS=6 (curr FN 1916668)<br />20170105173312846 <0002> tbf.cpp:947 <abbr title="TFI=0 TLLI=0xecc9d420 DIR=DL STATE=ASSIGN">TBF</abbr> releasing due to PACCH assignment timeout.<br />20170105173312846 <0002> tbf.cpp:447 <abbr title="TFI=0 TLLI=0xecc9d420 DIR=DL STATE=RELEASING">TBF</abbr> Software error: Pending downlink assignment. This may not happen, because the assignment message never gets transmitted. Please be sure not to free in this state. PLEASE FIX!<br />20170105173340681 <0002> bts.cpp:1347 MS supports EGPRS multislot class 10.</p>
<p>2) iphone indicates gprs connectivity but it doesn't work</p>
<p>3) works with errors on OsmoPCU</p>
<p>20170105174205658 <0002> bts.cpp:1347 MS supports EGPRS multislot class 10.<br />20170105174207477 <0002> bts.cpp:1392 RX: [PCU <- BTS] <abbr title="TFI=0 TLLI=0xce01da00 DIR=UL STATE=FLOW">TBF</abbr> FIXME: Packet resource request<br />20170105174211889 <0004> tbf_dl.cpp:423 - Restarting at BSN 83, because the window is stalled.<br />20170105174214633 <0004> tbf_dl.cpp:423 - Restarting at BSN 106, because the window is stalled.</p>
<p>acer phone fails in all configurations.</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=27422017-01-06T15:00:32Zmsuraev
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-3 priority-high3 closed" href="/issues/1553">Feature #1553</a>: Multi-TRX support of PCU</i> added</li></ul> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=28092017-01-12T20:19:50Zlaforge
<ul><li><strong>Priority</strong> changed from <i>High</i> to <i>Normal</i></li></ul> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=28562017-01-17T15:01:28Zmsuraev
<ul></ul><p>Checked with external bts tester: all tests pass except for leakage to neighbor frequencies which is expected and should not result in phones not seeing network. Btw, ports on olifantasia enclosure were printed incorrectly.</p>
<p>Notable thing is huge (40 db) difference between trx in transmission power - either smth is misconfigured by osmo-trx/osmo-bts-trx or hw failure (amplifier?). Not sure if it could be the reason for the effects described above.</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=28592017-01-17T16:34:11Zipse
<ul></ul><p>We've independently looked at issues with the 2nd channel in master version of osmo-bts-trx and found that "power" and "rxgain" commands are not sent to the 2nd channel (TRX1), because relevant VTY configuration commands and associated with a phy and not with an instance. Ivan is currently looking at this and some other issues with osmo-bts-trx VTY configuration like failure to set maxdly from a configuration file.</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=28602017-01-17T16:34:56Zipse
<ul></ul><p>And yes, this could leave to the effects you saw above.</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=28692017-01-18T07:15:08Zlaforge
<ul></ul><p>Hi Alexander,</p>
<p>On Tue, Jan 17, 2017 at 04:34:12PM +0000, ipse [REDMINE] wrote:</p>
<blockquote>
<p>We've independently looked at issues with the 2nd channel in master<br />version of osmo-bts-trx and found that "power" and "rxgain" commands<br />are not sent to the 2nd channel (TRX1), because relevant VTY<br />configuration commands and associated with a phy and not with an<br />instance. Ivan is currently looking at this and some other issues with<br />osmo-bts-trx VTY configuration like failure to set maxdly from a<br />configuration file.</p>
</blockquote>
<p>We are happy to work on the related code for integration with the<br />osmo-bts phy_link data model and vty, if you could document what kind of<br />setting osmo-trx needs in what sequence.</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=28722017-01-18T10:13:39Zkluchnikov
<ul></ul><p>Hi Harald,</p>
<p>Actually we have multiple related issues:</p>
<p><strong>1. osmo-bts doesn't set RXGAIN and POWER for second channel of osmo-trx (TRX1)</strong></p>
<p>We use the following osmo-bts config:<br /><pre>
phy 0
instance 0
osmotrx rx-gain 10
osmotrx tx-attenuation 10
instance 1
osmotrx rx-gain 2
osmotrx tx-attenuation 12
bts 0
band 900
ipa unit-id 1801 0
oml remote-ip 127.0.0.1
rtp jitter-buffer 0
paging lifetime 0
ms-power-loop -50
timing-advance-loop
settsc
gsmtap-sapi ccch
gsmtap-sapi pdtch
trx 0
phy 0 instance 0
trx 1
phy 0 instance 1
</pre></p>
<p>And if we start osmo-trx with INFO log level, we can see that osmo-bts sends RXGAIN and POWER commands only for the first channel, but these parameters should be set for second channel too, otherwise TRX1 is configured incorrectly and can't work properly:</p>
<p>2017-01-18_09:05:21.73985 INFO 139850878134016 09:05:21.6 Transceiver.cpp:740:driveControl: command is CMD POWEROFF<br />2017-01-18_09:05:21.73997 INFO 139850878134016 09:05:21.6 Transceiver.cpp:740:driveControl: command is CMD POWEROFF<br />2017-01-18_09:05:21.74007 INFO 139850878134016 09:05:21.6 Transceiver.cpp:740:driveControl: command is CMD RXTUNE 904800<br />2017-01-18_09:05:21.94325 INFO 139850878134016 09:05:21.7 Transceiver.cpp:740:driveControl: command is CMD TXTUNE 949800<br />2017-01-18_09:05:22.35494 INFO 139850878134016 09:05:21.9 Transceiver.cpp:740:driveControl: command is CMD SETTSC 7<br />2017-01-18_09:05:22.35508 INFO 139850878134016 09:05:21.9 Transceiver.cpp:740:driveControl: command is CMD POWERON<br />2017-01-18_09:05:22.35714 INFO 139850878134016 09:05:22.0 Transceiver.cpp:740:driveControl: command is CMD SETRXGAIN 2<br />2017-01-18_09:05:22.35724 INFO 139850878134016 09:05:22.0 Transceiver.cpp:740:driveControl: command is CMD SETPOWER 12<br />2017-01-18_09:05:22.35797 INFO 139850878134016 09:05:22.1 Transceiver.cpp:740:driveControl: command is CMD SETSLOT 0 5<br />2017-01-18_09:05:22.35807 INFO 139850878134016 09:05:22.1 Transceiver.cpp:740:driveControl: command is CMD SETSLOT 1 7<br />2017-01-18_09:05:22.35815 INFO 139850878134016 09:05:22.1 Transceiver.cpp:740:driveControl: command is CMD SETSLOT 2 7<br />2017-01-18_09:05:22.35923 INFO 139850878134016 09:05:22.1 Transceiver.cpp:740:driveControl: command is CMD SETSLOT 3 7<br />2017-01-18_09:05:22.35947 INFO 139850878134016 09:05:22.1 Transceiver.cpp:740:driveControl: command is CMD SETSLOT 4 7<br />2017-01-18_09:05:22.35955 INFO 139850878134016 09:05:22.1 Transceiver.cpp:740:driveControl: command is CMD SETSLOT 5 7<br />2017-01-18_09:05:22.35961 INFO 139850878134016 09:05:22.1 Transceiver.cpp:740:driveControl: command is CMD SETSLOT 6 7<br />2017-01-18_09:05:22.35969 INFO 139850878134016 09:05:22.1 Transceiver.cpp:740:driveControl: command is CMD SETSLOT 7 1<br />2017-01-18_09:05:22.35972 INFO 139850876937984 09:05:22.2 Transceiver.cpp:740:driveControl: command is CMD RXTUNE 910000<br />2017-01-18_09:05:38.09708 INFO 139850876937984 09:05:22.3 Transceiver.cpp:740:driveControl: command is CMD TXTUNE 955000<br />2017-01-18_09:05:38.09735 INFO 139850876937984 09:05:22.5 Transceiver.cpp:740:driveControl: command is CMD SETTSC 7<br />2017-01-18_09:05:38.09739 INFO 139850876937984 09:05:22.5 Transceiver.cpp:740:driveControl: command is CMD SETSLOT 0 1<br />2017-01-18_09:05:38.09742 INFO 139850876937984 09:05:22.5 Transceiver.cpp:740:driveControl: command is CMD SETSLOT 1 1<br />2017-01-18_09:05:38.09744 INFO 139850876937984 09:05:22.5 Transceiver.cpp:740:driveControl: command is CMD SETSLOT 2 1<br />2017-01-18_09:05:38.09746 INFO 139850876937984 09:05:22.5 Transceiver.cpp:740:driveControl: command is CMD SETSLOT 3 1<br />2017-01-18_09:05:38.09748 INFO 139850876937984 09:05:22.5 Transceiver.cpp:740:driveControl: command is CMD SETSLOT 4 1<br />2017-01-18_09:05:38.09750 INFO 139850876937984 09:05:22.5 Transceiver.cpp:740:driveControl: command is CMD SETSLOT 5 1<br />2017-01-18_09:05:38.09754 INFO 139850876937984 09:05:22.5 Transceiver.cpp:740:driveControl: command is CMD SETSLOT 6 1<br />2017-01-18_09:05:38.09757 INFO 139850876937984 09:05:22.5 Transceiver.cpp:740:driveControl: command is CMD SETSLOT 7 1</p>
<p><strong>2. Incorrect handling of osmo-trx configuration parameters on phy and instance levels</strong></p>
<p>As you can see above in osmo-bts config, we set "osmotrx rx-gain" and "osmotrx tx-attenuation" for each instance, because we should be able to set these parameters for each osmo-trx channel separatly. <br />But if we execute show running config command from vty, we can see:<br /><pre>
phy 0
osmotrx ip 127.0.0.1
osmotrx fn-advance 20
osmotrx rts-advance 5
osmotrx rx-gain 2
osmotrx tx-attenuation 12
instance 0
instance 1
bts 0
band GSM900
ipa unit-id 1801 0
oml remote-ip 127.0.0.1
rtp jitter-buffer 0
paging queue-size 200
paging lifetime 0
uplink-power-target -75
gsmtap-sapi ccch
gsmtap-sapi pdtch
min-qual-rach 50
min-qual-norm -5
ms-power-loop -50
timing-advance-loop
settsc
trx 0
power-ramp max-initial 23000 mdBm
power-ramp step-size 2000 mdB
power-ramp step-interval 1
ms-power-control dsp
phy 0 instance 0
trx 1
power-ramp max-initial 23000 mdBm
power-ramp step-size 2000 mdB
power-ramp step-interval 1
ms-power-control dsp
phy 0 instance 1
end
</pre></p>
<p>As you can see osmotrx rx-gain and osmotrx tx-attenuation parameters are on the phy level, but they should be moved to the instance level.<br />Actually I think that it could be the cause of the first issue too.</p>
<p><strong>3. Setting "osmotrx maxdly" and "osmotrx maxdlynb" parameters from config file doesn't work</strong></p>
<p>We get following error from osmo-bts:<br />2017-01-18_09:55:32.14230 There is no such command.<br />2017-01-18_09:55:32.14244 Error occurred during reading below line:<br />2017-01-18_09:55:32.14249 osmotrx maxdly 20</p>
<p>But we can set these parameters from vty, so it seems like configuration handling issue.</p>
<p>If you need more tests or feedback from our side, please let us know.</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=29672017-01-31T20:22:07Zipse
<ul></ul><p>Update: Ivan has developed patches to fix these issues. We will submit to Gerrit after a bit more testing and clean up.</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=30012017-02-06T09:45:44Zmsuraev
<ul></ul><p>Please add me as reviewer for those patches on gerrit once they are ready to speedup review process.</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=32032017-03-02T13:57:13Zmsuraev
<ul><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' checked disabled> <i>set-up osmo-bts-trx locally for testing</i> set to Done</li><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' checked disabled> <i>do some manual testing with different codecs and gprs</i> set to Done</li></ul> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=32112017-03-03T11:03:41Zmsuraev
<ul><li><strong>File</strong> <a href="/attachments/2554">open-bsc.cfg-mtrx1-f-gprs</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2554/open-bsc.cfg-mtrx1-f-gprs">open-bsc.cfg-mtrx1-f-gprs</a> added</li><li><strong>File</strong> <a href="/attachments/2555">open-bsc.cfg-mtrx0-f-gprs</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2555/open-bsc.cfg-mtrx0-f-gprs">open-bsc.cfg-mtrx0-f-gprs</a> added</li><li><strong>File</strong> <a href="/attachments/2556">osmo-pcu.cfg</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2556/osmo-pcu.cfg">osmo-pcu.cfg</a> added</li><li><strong>File</strong> <a href="/attachments/2557">osmo-bts.cfg-mtrx</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2557/osmo-bts.cfg-mtrx">osmo-bts.cfg-mtrx</a> added</li></ul><p>Re-testing after recent updates to osmo-trx and osmo-bts-trx:</p>
<pre>
sudo ./Transceiver52M/osmo-trx -l INFO -x -c 2 -m
linux; GNU C++ version 6.2.0 20161005; Boost_106100; UHD_003.009.006-release
...
-- Asking for clock rate 3.200000 MHz...
UHD Warning:
The requested master_clock_rate 3.200000 MHz exceeds bounds imposed by UHD.
The master_clock_rate has been forced to 5.000000 MHz.
-- Actually got clock rate 5.000000 MHz.
-- Performing timer loopback test... pass
-- Performing timer loopback test... pass
ALERT 139849313479552 11:54:38.8 UHDDevice.cpp:548:set_master_clk: Failed to set master clock rate
ALERT 139849313479552 11:54:38.8 UHDDevice.cpp:548:set_master_clk: Failed to set master clock rate
ALERT 139849313479552 11:54:38.8 UHDDevice.cpp:549:set_master_clk: Requested clock rate 3.2e+06
ALERT 139849313479552 11:54:38.8 UHDDevice.cpp:549:set_master_clk: Requested clock rate 3.2e+06
ALERT 139849313479552 11:54:38.8 UHDDevice.cpp:550:set_master_clk: Actual clock rate 5e+06
ALERT 139849313479552 11:54:38.8 UHDDevice.cpp:550:set_master_clk: Actual clock rate 5e+06
ALERT 139849313479552 11:54:38.8 osmo-trx.cpp:530:main: Failed to create radio device
</pre>
<p>Doesn't work at all, so we have to use<br /><pre>
sudo ./Transceiver52M/osmo-trx -l INFO -x -c 2
</pre></p>
<p>But in both cases I've tried (tch on on trx0, gprs on trx1 and vice versa) the phone fails to see the network:<br /><pre>
./openbsc/src/osmo-nitb/osmo-nitb -c ~/.config/osmocom/open-bsc.cfg-mtrx0-f-gprs -l ~/.config/osmocom/hlr.sqlite3 -P -d DGPRS:DGSUP:DSNDCP
sudo ./src/osmo-bts-trx/osmo-bts-trx -c ~/.config/osmocom/osmo-bts.cfg-mtrx -t 2 -r 99
sudo ./src/osmo-pcu -c ~/.config/osmocom/osmo-pcu.cfg -r 99
</pre></p>
<p>Am I missing smth?</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=32132017-03-03T12:13:01Zmsuraev
<ul><li><strong>Blocked by</strong> <i><a class="issue tracker-1 status-5 priority-2 priority-default closed" href="/issues/1963">Bug #1963</a>: multiplexing trx is not working</i> added</li></ul> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=34752017-03-31T06:50:26Zkeith
<ul></ul><p>Ivan, Does the resolution of <a class="issue tracker-1 status-5 priority-2 priority-default closed" title="Bug: multiplexing trx is not working (Closed)" href="https://osmocom.org/issues/1963">#1963</a> also resolve this?</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=42042017-05-31T10:56:34Zmsuraev
<ul><li><b>Checklist item</b> deleted (<strike><i>verify multi-trx functionality (with two trx)</i></strike>)</li><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' checked disabled> <i> verify multi-trx functionality with multiplexing (-m)</i> added</li><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' disabled> <i> verify multi-trx functionality without multiplexing</i> added</li></ul> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=42072017-05-31T11:20:37Zmsuraev
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-4 priority-2 priority-default" href="/issues/1524">Bug #1524</a>: PACCH on the wrong timeslot</i> added</li></ul> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=42092017-05-31T11:24:28Zmsuraev
<ul><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' checked disabled> <i> verify multi-trx functionality without multiplexing</i> set to Done</li></ul> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=42102017-05-31T11:28:28Zmsuraev
<ul><li><strong>Status</strong> changed from <i>Stalled</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>50</i> to <i>100</i></li></ul><p>Verified (using latest master) that both TRX work for gprs (with issues outlined in <a class="issue tracker-1 status-4 priority-2 priority-default" title="Bug: PACCH on the wrong timeslot (Feedback)" href="https://osmocom.org/issues/1524">#1524</a>) and voice, with and without multiplexing. To test this I've set all TS on one TRX to TCH/F on other to PDCH, than swapped this TS config between TRXs.</p>
<p>Dynamic TS configurations are tracked via separate issue <a class="issue tracker-1 status-3 priority-2 priority-default closed" title="Bug: validate dynamic TCH/PDCH support in osmo-bts-trx (Resolved)" href="https://osmocom.org/issues/1853">#1853</a>.</p> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=42112017-05-31T11:29:03Zmsuraev
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/1853">Bug #1853</a>: validate dynamic TCH/PDCH support in osmo-bts-trx</i> added</li></ul> OsmoBTS - Feature #1648: Verify Multi-TRX support for osmo-bts-trxhttps://osmocom.org/issues/1648?journal_id=48732017-08-08T19:06:34Zlaforge
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>