TxRank2 Check AMOS Command

4G LTE
, , ,
1

E// Exports, I want to know which amos command gives the same results as below:

image
image836Ă—302 33.7 KB

2

Look for something like this in amos console:
momp . RANK

3

Using the above command momp.rank it

not yield above o/p

4

That output is a health-check script parsing PM counters from ROP files — so the AMOS equivalent is the ROP-reading command family, not a live MO read. The direct match:

lt all
pmx EUtranCellFDD=JK4G18_441PC371E_14 pmRadioTxRankDistr -m 0.5

Or for all cells on the node in one shot:

pmx EUtranCellFDD= pmRadioTxRankDistr -m 0.5

Why this is the equivalent:

  • pmx reads historical counter values directly from the ROP files stored on the node — the screenshot’s header (“Report from 06:00 to 06:29 UTC, 2 ropfiles”) is exactly a 2Ă—15-min ROP window, which is what -m 0.5 (last half hour) reproduces. Use -m 1, -m 24 etc. for longer windows.

  • pmRadioTxRankDistr is the PDF (bin-vector) counter holding the transmission-rank sample distribution per cell. The script’s TM03_RANK2 / TM04_RANK2 columns are computed percentages: rank-2 samples Ă· total samples within each transmission-mode bin group. The “NA” under TM03 simply means those cells logged no TM3 samples (running TM4), so the denominator is zero.

  • pmx gives you the raw bin values — the script does the division and the 20% threshold comparison on top. If you want the ready-made percentage without manual math, check pmr (moshell’s report menu); recent moshell versions include a MIMO/rank distribution report that presents rank-2 share per cell directly. The menu numbering varies by moshell version, so run pmr and pick the rank/MIMO report from the list it prints.

Two related commands worth knowing for the same investigation: pget EUtranCellFDD= pmRadioTxRankDistr reads the live accumulating value of the current ROP (not yet closed), and pmxh works like pmx but prints per-hour aggregation, useful when you widen the window to spot the time-of-day pattern behind low rank-2.

One verification note, in keeping with how you work: the exact bin-to-TM/rank mapping of pmRadioTxRankDistr changed across L-releases — confirm the bin layout in the ALEX/CPI counter description for the node’s release before you hard-code the percentage formula into any check of your own. If you tell me the release, I’ll walk the computation with you.

5

is this AI or not ?

6

Try and let me know.

7

Not same result

8

I will need the corresponding libraries and logs to perform an extraction correlation and pinpoint the issue