CALL:DCONnected

Function

Queries whether the test data connection ((SO32 (+F-SCH) or SO32 (+ SCH)) or the packet data connection (SO33 or SO33 (+F-SCH)) is in the connected state.

For test data connection (see Call Processing State Synchronization ).

• If the data connection is in the connected state (Connected +Data), the query immediately returns a 1.
• If the data connection is in any other stable state (Idle), the query immediately returns a 0.
• If the data change arm timer is armed (see CALL:DCONnected:ARM:STATe? ) and then this is queried, the query will hang until either the data change arm timer is disarmed or the data connection status changes.

For the packet data connection (for lab application only, see Packet Data Connection Processing States ).

• If the packet data connection is in the connected state (Connected +Data), the query immediately returns a 1.
• If the packet data connection is in any other stable state (Idle or Idle Dormant), the query immediately returns a 0.
• If the data change arm timer is armed (see CALL:DCONnected:ARM:STATe? ) and then this is queried, the query will hang until either the data change arm timer is disarmed or the data connection status changes.

Query

Range: 0|1

*RST Setting

0

Programming Example

 
OUTPUT 714;"CALL:DCONNECTED:STATE?" 
!Queries whether the data connection is in connected state.

Function

Sets (arms) the call-state-change detector. Arming this detector 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 data status change or the arm detector timer times out (determined by CALL:DCONnected:TIMeout ). It is not disarmed by any transitions from idle to idle or from connected to connected. See Call State Change Detector .

This is an overlapped command, and therefore has a Pending Operation Flag (POF) associated with it. See Call Processing Event Synchronization for more information about the behavior of overlapped commands.

Programming Example

 
OUTPUT 714;"CALL:DCONNECTED:ARM:IMMEDIATE" !Arms the call-state-change detector.

Function

Queries the arm state of the data-state-change detector. This command never hangs and immediately returns a one if the detector is armed, or a zero if the detector is not armed. See also CALL:DCONnected:ARM[:IMMediate] and CALL:DCONnected:TIMeout .

See Call State Change Detector for details.

Query

Range:   1|0

*RST Setting

0

Programming Example

 
OUTPUT 714;"CALL:DCONNECTED:ARM:STATE?" 
!Returns arm state of the call-state-change detector.

Function

Sets/queries the maximum time the test set will wait for a hanging query to complete (such as CALL:DCONnected[:STATe] or CALL:DORMant[:STATe]? ). Default setting units are seconds. To set timeout time in units other than seconds, include an optional unit specifier in the command string.

A timeout timer is started whenever the data-state-change detector becomes armed or gets rearmed when already armed. The duration of this timeout should be greater than the maximum amount of time the control program needs to wait between arming the data-state-change detector and the connect/disconnect operation starting. Once the process starts and the data channel's state has moved to one of the transitory states, the protocol timers take over and prevent the data channel's state from staying in a transitory state forever. See Call Processing State Synchronization .

Setting

Range: 0 to 100 seconds
Resolution: 0.1 seconds

Query

Range: 0 to 100 seconds
Resolution: 0.1 seconds

*RST Setting

10 seconds

Programming Example

 
OUTPUT 714;"CALL:DCONNECTED:TIMEOUT 3" 
!Sets the CALL:DCONnected:STATe? query timeout time to 3 seconds.

 
OUTPUT 714;"CALL:DCONNECTED:TIMEOUT 500 MS" 
!Sets the Sets the CALL:DCONnected:STATe? query timeout time to 500 milliseconds.