A Device Port Pair (also referred to as a DevPair) pairs the device name to the ports being used and contains the following information:

The format of a device port pair is:

name:inPort,outPort  for example DCM_1:2,3

  • name is the calibration device name.
  • inPort is the input port of the device that is connected to the PNA.
  • outPort is the output port of the device.

The outPort is optional, it is used to determine the characterization file to be used when extending the reference plane from the inPort to the outPort.

For special cases such as TransmissionResponse calibrations, in devices that have multiple ports it specifies the thru switch state when the device is put into a thru state.

Device port pairs are always the name of the calibration device and the input port of the device separated by a colon. Optionally an output port can be added separated by a comma. Some devices only have one output port (such as the FCM) and therefore do not need to specify the output port. Other devices such as the DCM can have various through paths and therefore should specify the output port to identify the characterization file to be used when the cal type is "ExtendWithFcmFile" or "TransmissionResponse".

When a Path component refers to a calibration device it must also specify the ports on that device that are being used. This is accomplished using a Device Port Pair.

For Example:

Port1DevPair = DCMX:2,1


Some examples:

"MyFCM:1"    (specifies the FCM with the name "MyFCM" using FCM input port 1)

"SCM_A:0,2"    (specifies the SCM with the name "SCM_A" using SCM input port 0 and SCM output port 2)

"DCMx:1,3"    (specifies the DCM with the name "DCMx" using DCM input port 1 and DCM output port 3 for the thru path.)

"DCM:3"    (specifies the DCM with the name "DCM" using DCM input port 3, and the output port is not utilized)

Device Port Pairs are used in the following configurations: