2201R Mobile Tester SCPI Reference Guide
Chapter 6 Status commands
47090/323
Copyright © 2016 Aeroflex Limited. All rights reserved.
67
:STATus:OPERation:SIGNalling:GSM[:EVENt]?
Syntax
:STATus:OPERation:SIGNalling:GSM[:EVENt]?
Parameters
There are no parameters.
Description
Reads out the current contents of the signaling operation event register.
Note: Event-type registers are read-only and self-destructive. They are cleared after any query.
Query
There is only a query form of this command available. The query returns a string, containing one integer.
The value returned represents all signaling operation events that have occurred since the last query of this register.
As with any event-type register, the single bits remain set even when the reason for the bits to be set is no longer
valid. Please note that this is the main difference between event-type and condition-type registers. Condition-type
registers reflect the current state of the 2201R. Consequently, condition-type registers are updated continuously.
The bits of the signaling operation event register have the following meaning:
Bit 0 (decimal 1): The 2201R is in idle mode
Bit 1 (decimal 2): The 2201R is paging the mobile.
Bit 2 (decimal 4): A call has been established and is currently active.
Bit 3 (decimal 8): The BER loop has been closed.
Bit 4 (decimal 16): Async mode (e.g. Generator/Analyzer) active.
Bit 5 (decimal 32): The 2201R is calling the mobile under test. A BS call is in progress.
Bit 6 (decimal 64): Not used (reserved).
Bit 7 (decimal 128): Not used (reserved).
Bit 8 (decimal 256): Alerting.
Bits 9 through 15: Not used (reserved).
Note: In case a certain event is trapped in a loop within a program, always query the event-type register.
Example
:STATus:OPERation:SIGNalling:GSM:EVENt?
Value returned: "8".
This means that bit 3 of the signaling operation event register (stands for BER loop being closed) has been set.