ROUTe:CHANnel:VERify[:ENABle]

34980A

ROUTe:CHANnel:VERify[:ENABle]

Syntax

ROUTe:CHANnel:VERify[:ENABle] <mode>, (@<ch_list>)

ROUTe:CHANnel:VERify[:ENABle]? (@<ch_list>)

Description

This command enables or disables verification, which senses the actual hardware state of the specified channels following a ROUTe:CLOSe or ROUTe:OPEN operation (and reset operations). By default, verification is disabled because not all external microwave devices have verify lines and verification will slow switching performance.

Used With:

  • 34945A Microwave Switch/Attenuator Driver

  • 34946A Dual 1x2 SPDT Terminated Microwave Switch

  • 34947A Triple 1x2 SPDT Unterminated Microwave Switch

Parameters

Name

Type

Range of Values

Default Value

<mode>

Boolean

{OFF|0|ON|1}

OFF (verification disabled)

<ch_list>

34945A

Numeric

One or more channels in the form (@srcc).
 

Bank 1:

sr01 through sr08
sr
11 through sr18

Bank 2:

sr21 through sr28
sr
31 through sr38

Bank 3:

sr41 through sr48
sr
51 through sr58

Bank 4:

sr61 through sr68
sr
71 through sr78
 

s: Mainframe slot number (1 through 8)
r
: 34945EXT remote module (1 through 8) 

This is a required parameter

<ch_list>

34946A/47A

Numeric

One or more channels in the form (@sccc).

34946A: s101, s102, s201, s202
34947A: s101, s102, s201, s202, s301, s302

This is a required parameter

Remarks

  • When verification is enabled, the actual hardware state of each relay is sensed for the correct state. If a switch operation appears to have failed, an error will be generated at the time the ROUTe:CLOSe or ROUTe:OPEN command is executed. If you send a ROUTe:CLOSe or ROUTe:OPEN command with a channel list (i.e., multiple channels), the verification is performed after all open/close operations have been completed. An error will be generated for each channel operation that did not properly verify.

  • On the 34945EXT remote modules, if verification is enabled on one or more channels, the entire verified state of the associated channels is refreshed following any switch operations on the module. This is done to ensure that the module state displayed on the 34980A front panel (and Web Interface) is accurate.

  • The verification process will affect the operation of the ROUTe:CLOSe? and ROUTe:OPEN? commands. If verification is enabled, these commands will check the actual hardware state of the specified channels, rather than just reporting the presumed state.

  • Verification will slow switching performance. Specifically, if you have enabled the command overlap function (see ROUTe:OPERation:OVERlap[:ENABle] command), the verification will be performed at the end of each close/open operation, before processing the next command.

  • When verification is enabled on the 34945A, the channels are verified following a reset/boot. Errors are limited to a single message for each slot containing a 34945A. Each consolidated error message indicates the first channel on which a verification error was found, and gives an indication of whether more verification errors exist.

  • The ROUTe:CHANnel:DRIVe:TIME:SETTle command (34945A only) configures a settling time for switching operations after which the verification operation is complete. The specified settling time is acknowledged, regardless of whether verification is enabled or disabled.

  • For paired operations on the 34945A (see ROUTe:CHANnel:DRIVe:PAIRed[:MODE] command), when you enable verification on either paired channel, verification will be enabled on both channels. In addition, the module checks for complementary position indicators on the lower and upper channels of the pair (i.e., the position indicators should indicate opposite states). If the state of the lower and upper position indicators are found to be in the same state (due to a hardware issue), an error is generated and the state of the lower channel is assumed.

  • When the paired mode is disabled on a 34945A channel with the pulsed mode enabled (see ROUTe:CHANnel:DRIVe:PULSe[:MODE] command), you cannot query the open/closed state of that channel unless verification is enabled (see ROUTe:CHANnel:VERify[:ENABle] command).

  • If you enable verification on a non-paired (one coil), non-pulsed channel on the 34945A, the ROUTe:CLOSe? and ROUTe:OPEN? commands return the state of the verified device, rather than the drive state of the specified channel. You can use the ROUTe:CHANnel:VERify:POSition:STATe? command to determine exactly which channels are currently being driven.

  • The SYSTem:RMODule:RESet command (34945A only) will restore the default verification state (OFF) on all channels.

  • On the 34946A/47A, when you enable verification on either channel in a bank, verification will be enabled on both channels.

  • The verification setting for each channel is stored in non-volatile memory. On the 34945A, the state is stored on the 34945EXT remote module.

Return Format

The query command returns "0" (OFF) or "1" (ON) for each channel specified. Multiple responses are separated by commas.

Examples

The following command enables verification on channels 101 and 201 on the module in slot 2 (assumes 34946/47A).

ROUT:CHAN:VER ON,(@2101,2201)

The following command enables verification on channels 01 and 02 on Bank 2 on 34945EXT remote module #2 (slot 3).  

ROUT:CHAN:VER ON,(@3201,3202)

The following query returns whether verification is enabled on channels 101 and 201 on the module in slot 2 (assumes 34946/47A).

ROUT:CHAN:VER? (@2101,2201)

Typical Response:  1,1

See Also

ROUTe:CHANnel:DRIVe:TIME:SETTle   (34945A only)

ROUTe:CHANnel:VERify:POLarity   (34945A only)

ROUTe:CHANnel:VERify:POSition:STATe?   (34945A only)

ROUTe:CLOSe

ROUTe:OPEN

ROUTe:OPERation:OVERlap[:ENABle]