https://osmocom.org/https://osmocom.org/favicon.ico?16647414092020-07-24T15:57:54ZOpen Source Mobile CommunicationsOsmoTRX - Bug #4679: osmo-trx: Add rate-ctr for clipping https://osmocom.org/issues/4679?journal_id=191892020-07-24T15:57:54Zipse
<ul></ul><p>Good idea about adding stats for this.</p>
<p>But please do not remove this log output - it's useful when debugging. Just move it to DEBUG level.</p> OsmoTRX - Bug #4679: osmo-trx: Add rate-ctr for clipping https://osmocom.org/issues/4679?journal_id=191942020-07-25T20:52:38Zlaforge
<ul></ul>I think it's not just clipping. There are many situations (also seen in SYS#5014) which<br />are potentially happening at every burst:
<ul>
<li>empty burst (no energy in the channel)</li>
<li>clipping detected</li>
<li>no RACH or NB detected</li>
</ul>
<p>We should have counter for (at least) all of these.</p>
<p>Given that we may have different radio carrier (ARFCN) and TS, the counters should<br />exist at least on a per-carrier basis, if not even on a per-TS basis.</p> OsmoTRX - Bug #4679: osmo-trx: Add rate-ctr for clipping https://osmocom.org/issues/4679?journal_id=192082020-07-27T09:55:51Zpespin
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>90</i></li></ul><p>Available here: <a class="external" href="https://gerrit.osmocom.org/c/osmo-trx/+/19403">https://gerrit.osmocom.org/c/osmo-trx/+/19403</a> Transceiver: Add several rate_ctr for rx error conditions</p>
<p>Once merged the ticket can be closed.</p> OsmoTRX - Bug #4679: osmo-trx: Add rate-ctr for clipping https://osmocom.org/issues/4679?journal_id=193932020-08-17T17:02:28Zpespin
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>90</i> to <i>100</i></li></ul><p>Merged, closing.</p>