Source:Bb:Nr5G:Ubwp:User:Cell:Downlink:Bwp:Rmc:Id#
SCPI Commands
- [SOURce<HW>]:BB:NR5G:UBWP:USER<US(CH0)>:CELL<CC(ST0)>:DL:BWP<BWP(DIR0)>:RMC:ID
Direct SCPI Members
- RmcIdAllEnum Get ( )#
- RmcIdAllEnum Get ( UserNullRepCap userNull, CellNullRepCap cellNull, BwPartNullRepCap bwPartNull )
// SCPI: [SOURce<HW>]:BB:NR5G:UBWP:USER<US(CH0)>:CELL<CC(ST0)>:DL:BWP<BWP(DIR0)>:RMC:ID RmcIdAllEnum value = driver.Source.Bb.Nr5G.Ubwp.User.Cell.Downlink.Bwp.Rmc.Id.Get(); RmcIdAllEnum value = driver.Source.Bb.Nr5G.Ubwp.User.Cell.Downlink.Bwp.Rmc.Id.Get(UserNullRepCap.Default, CellNullRepCap.Default, BwPartNullRepCap.Default);This command selects a reference measurement channel. The availability of RMCs depends on the subcarrier spacing of the bandwidth part you are configuring.
rmcId: The logic of the labels is as follows: No prefix = 38.521 FR1 RMCs Prefix FR2 = 38.521 FR2 RMCs F / T = duplexing (FDD or TDD) Q / 6 / 2 = modulation (QPSK, 64QAM or 256 QAM) 15 / 30 / 60 = subcarrier spacing (15, 30 or 60 kHz) For example “T615” corresponds to FR1 RMC with the name “TS 38.521: A.3.3.3-1 (15 kHz) “. The RMCs from 38.176 are basically a shortened form of the names of the RMCs. For example “TS38176_FR1A352” corresponds to RMC with the name “TS 38.176: M-FR1-A3_5_2”.
userNullRepeated capability selectorcellNullRepeated capability selectorbwPartNullRepeated capability selectorWhen you do not use any explicit repeated capability selector, the value is taken from its parent group.