CALL:CONNected

Last updated: 2014-11-28

For more information on the GPIB Command conventions, see GPIB Command conventions

CALL:CONNected:ARM[:IMMediate]

Function

Sets the call-state-change detector. It allows the control program to tell the test set that it is expecting a change in the state of a call, prior to initiating the state change.

Once armed, the detector remains armed until there is a call state change to "Idle" or "Connected" from other transition states.

Requirements

Test Application Revision: A.02.00 and above

Programming Example

"CALL:CONNECTED:ARM"

CALL:CONNected: ARM[:IMMediate]:DONE?

Function

 

Query

Range: 1|0

Requirements

Test Application Revision: A.02.00 and above

Programming Example

"CALL:CONNected:ARM:IMMediate:OPComplete?"

CALL:CONNected:ARM[:IMMediate]:OPComplete?

Function

Returns 1 in the test set's output queue when the call-state-change detector is armed, otherwise returns 0. Controlling program hangs on this query until the 1 is retrieved.

Query

Range: 1|0

Requirements

Test Application Revision: A.02.00 and above

Programming Example

"CALL:CONNected:ARM:IMMediate:OPComplete?"

CALL:CONNected:ARM[:IMMediate]:SEQuential

Function

Forces an overlapped command to execute in the call-state-change detector.

Requirements

Test Application Revision: A.02.00 and above

Programming Example

"CALL:CONNected:ARM:IMMediate:SEQuential"

CALL:CONNected:ARM[:IMMediate]:WAIT  

Function

Forces the test set to wait until the call-state-change detector is armed before executing any more commands.

Requirements

Test Application Revision: A.02.00 and above

Programming Example

"CALL:CONNected:ARM:IMMediate:WAIT"

CALL:CONNected:ARM:STATe?

Function

Queries the arm state of the call-state-change detector. This command never hangs and immediately returns 1if the detector is armed, or 0 if the detector is not armed.

Query

Range: 0|1

*RST Setting

0

Requirements

Test Application Revision: A.02.00 and above

Programming Example

"CALL:CONNected:ARM:STATe?"

CALL:CONNected:DROP:TIMer[:STATe][:SELected]

Function

Sets/queries the call drop timer timer for currently selected application, which indicates loss synchronization with uplink DPCH (ON).

Setting

Range: 1|ON|0|OFF

Query

Range: 1|0

*RST Setting

1(ON)

Requirements

Test Application Revision: A.02.00 and above

Programming Example

"CALL:CONNected:DROP:TIMer 1"

CALL:CONNected:DROP:TIMer[:STATe]:TDSCdma

Function

Sets/queries the call drop timer when using the TD-SCDMA application, which indicates loss synchronization with uplink DPCH (ON).

Setting

Range: 1|ON|0|OFF

Query

Range: 1|0

*RST Setting

1(ON)

Requirements

Test Application Revision: A.02.00 and above

Programming Example

"CALL:CONNected:DROP:TIMer:TDSCdma 1"

CALL:CONNected:LIMit[:STATe][:SELected]

Function

Sets/queries the call limit state for current selected format. When the call limit state is set to On, the test set does not respond to any UpPCH from the UE, which forces the UE to repeatedly send UpPCH.

Setting

Range: 1|ON|0|OFF

Query

Range: 1|0

*RST Setting

0(OFF)

Requirements

Test Application Revision: A.02.00 and above

Programming Example

"CALL:CONNected:LIMit 1"

CALL:CONNected:LIMit[:STATe]:TDSCdma

Function

Sets/queries the call limit state when using the TD-SCDMA application.

When the call limit state is set to On, the test set does not respond to any UpPCH from the UE, which forces the UE to repeatedly send UpPCH.

Setting

Range: 1|ON|0|OFF

Query

Range: 1|0

*RST Setting

0(OFF)

Requirements

Test Application Revision: A.02.00 and above

Programming Example

"CALL:CONNected:LIMit:TDSCdma 1"

CALL:CONNected[:STATe]?

Function

Queries the connected/disconnected state of the call. If the call status is "connected", 1 is returned;  else if the call status is in "idle",  0 is returned; else the call is in any other state , the query will hang until the call state transits to the connected or idle state.

Query

Range: 0|1

*RST Setting

0

Requirements

Test Application Revision: A.02.00 and above

Programming Example

"CALL:CONNECTED:STATE?"

CALL:CONNected:TIMeout

Function

Queries the arm state of the call-state-change detector. This command never hangs and immediately returns 1if the detector is armed, or 0 if the detector is not armed.

A timeout timer is started whenever the call-state-change detector becomes armed or gets rearmed. The timeout should be set greater than the maximum amount of time the control program needs to wait between arming the call-state-change detector and the connect/disconnect operation starting.

Setting

Range: 0 to 100 seconds

Query

Range: 0 to 100 seconds

*RST Setting

10 S

Requirements

Test Application Revision: A.02.00 and above

Programming Example

"CALL:CONNECTED:TIMEOUT 500 MS"