VectorStar MS4640B Series VNA Programming Manual Anritsu Vector Star
Anritsu_VectorStar_Programming_Manual
Anritsu_VectorStar_Programming_Manual
User Manual:
Open the PDF directly: View PDF 
.
Page Count: 1122
| Download | |
| Open PDF In Browser | View PDF |
Programming Manual VectorStar™ MS464xB Series Microwave Vector Network Analyzer MS4642B VNA, 10 MHz to 20 GHz, K Connectors MS4644B VNA, 10 MHz to 40 GHz, K Connectors MS4645B VNA, 10 MHz to 50 GHz, K Connectors (No longer available) MS4647B VNA, 10 MHz to 70 GHz, V Connectors Anritsu Company 490 Jarvis Drive Morgan Hill, CA 95037-2809 USA http://www.anritsu.com Part Number: 10410-00322 Revision: U Published: October 2018 Copyright 2018 Anritsu Company Front-2 PN: 10410-00322 Rev. U MS464xB Series VNA PM Table of Contents Chapter 1—General Information 1-1 About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1-2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1-3 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Product Information, Compliance, and Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 1-4 Contacting Anritsu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 1-5 IEEE 488 GPIB Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 GPIB Network Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Functional Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Bus Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Data Bus Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Data Byte Transfer Control Bus Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 General Interface Management Bus Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Device Interface Function Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 Message Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Interface Function Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Device-Specific Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Data and Instrument Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Response to GPIB Interface Function Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 Configuring the Dedicated GPIB Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12 Configuring the IEEE 488.2 GPIB Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16 To change the VectorStar VNA GPIB address:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17 1-6 Resetting GPIB Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17 Returning the GPIB Addresses to Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17 1-7 Ethernet LAN TCP/IP and USB Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCP/IP General Requirements and Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default Plug-and-Play Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manually Configuring TCP/IP Ethernet LAN Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Configuring the Remote Language. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21 1-9 Minimum/Maximum Instrument Frequency and Related Parameters. . . . . . . . . . . . . . . . . . . Standalone VNAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standalone VNAs – Default Start, Default CW, and Default Stop Frequencies . . . . . . . . Standalone VNAs – Minimum Start, Minimum CW, and Maximum Start Frequencies . . . Standalone VNAs – Default Frequency Span and Maximum Frequency Span . . . . . . . . Standalone VNAs – Minimum Center and Maximum Center Frequencies . . . . . . . . . . . . Standalone VNAs – Default Center Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VNA Systems with ME7828A Configured as Broadband System . . . . . . . . . . . . . . . . . . . VNA Systems with ME7828A Configured as a Millimeter-Wave System . . . . . . . . . . . . . VNA Systems with ME7828A Using Multiple Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . VNA Systems with ME7838x Modular Broadband System . . . . . . . . . . . . . . . . . . . . . . . . VNA Systems with ME7838x Configured as a Millimeter-Wave System. . . . . . . . . . . . . . MS464xB Series VNA PM PN: 10410-00322 Rev. U 1-18 1-18 1-19 1-20 1-22 1-22 1-23 1-24 1-26 1-27 1-28 1-28 1-28 1-28 1-28 1-28 Contents-1 Table of Contents (Continued) Chapter 2—Programming the VectorStar Series VNA 2-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 2-2 Introduction to SCPI Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Command Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 2-3 IEEE 488.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 2-4 System Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 2-5 SCPI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Required SCPI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Native SCPI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 2-6 Anritsu Lightning VNA Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Using Anritsu Lightning VNA Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 VectorStar VNA Language Set to Lightning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 2-7 HP8510 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 2-8 Command Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Query Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hierarchical Command Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 2-4 2-4 2-4 2-5 2-9 Notational Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameter Notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notational Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Band Equation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 2-6 2-7 2-8 2-8 2-10 Numeric Data Suffix Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 2-11 Data Transmission Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . or . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . or . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MPND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MPNF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MPNI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Formatting Data Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ASCII or Binary Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 2-10 2-10 2-10 2-10 2-11 2-11 2-11 2-13 2-13 2-13 2-13 2-13 2-14 2-12 Calculating the Byte Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Numbers Output-per-Data Point (NODP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bytes Output-per-Number (BOPN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Size of Data Block (SODB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Number of Bytes Output (NBO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17 2-17 2-17 2-18 2-18 2-13 GPIB Input Buffer Size and NRFD Holdoff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18 Contents-2 PN: 10410-00322 Rev. U MS464xB Series VNA PM Table of Contents (Continued) 2-14 Synchronization of GPIB Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 2-15 Forcing the Parser to Stop Waiting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 2-16 How Can I Abort an RF or Hardware Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 2-17 GPIB Time-Out Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 2-18 Trace Type Parameters and Coefficients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21 2-19 Input/Output Data Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25 2-20 Status System Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28 Status Group Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28 Status Group Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28 2-21 Trigger System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34 Trigger Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34 Trigger Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36 2-22 Calibration Component Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loads and Through Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other Connector Coefficients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W1 Calibration Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sliding Load Cutoff Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microstrip Kit Common Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37 2-37 2-38 2-39 2-40 2-41 2-23 Notes on Calibration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up a 2-Port Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up a 4-Port Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Calibration Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing the Calibration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AutoCal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LRL Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43 2-43 2-44 2-47 2-51 2-53 2-57 2-24 Command Script Example – Limit Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Limit Lines for Single Rectilinar Trace Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DUT Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel and Trace Display Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VNA General Setup and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency and Sweep Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Limit Lines Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clear Previous Limit Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create and Configure Limit Line Segment 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create and Configure Limit Line Segment 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create and Configure Limit Line Segment 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create and Configure Limit Line Segment 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure AutoCal Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ready for Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60 2-60 2-61 2-61 2-61 2-61 2-62 2-63 2-63 2-64 2-64 2-64 2-65 2-65 2-66 2-66 Chapter 3—IEEE Commands 3-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 3-2 Command Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 MS464xB Series VNA PM PN: 10410-00322 Rev. U Contents-3 Table of Contents (Continued) 3-3 Numeric Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 3-4 IEEE 488.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Chapter 4—System and Troubleshooting Commands 4-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 4-2 Parameters and Notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 4-3 Numeric Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 4-4 System Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Chapter 5—SCPI Commands 5-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 5-2 Minimum/Maximum Frequency Limits and Related Parameters . . . . . . . . . . . . . . . . . . . . . . . 5-1 5-3 Command Level Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Descriptions and Notation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Numeric Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notational Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 General Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 5-5 :CALCulate{1-16}:AFCW Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 5-6 :CALCulate{1-16}:ALL:ALTernate:TRACe Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13 5-7 :CALCulate{1-16}:APPLication:MEASurement Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 5-8 :CALCulate{1-16}:CORRection Subsystem - Adapters/Merge Calibration . . . . . . . . . . . . . . . 5-15 Calibration Option Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15 5-9 :CALCulate{1-16}:DISPlay:MARKer Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18 Marker Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18 5-2 5-2 5-2 5-3 5-10 :CALCulate{1-16}:DNFigure Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19 DNFigure Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19 5-11 :CALCulate{1-16}:EOOE: Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EOOE Commands – General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EO4 Measurement Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EO Measurement Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34 5-34 5-35 5-39 5-12 :CALCulate{1-16}:EXTRaction Subsystem - Network Extraction . . . . . . . . . . . . . . . . . . . . . . 5-52 Calibration Option Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52 General Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52 5-13 :CALCulate{1-16}:FCW Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65 5-14 :CALCulate{1-16}:FORMat Subsystem - SnP Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70 I/O Configuration and File Operation Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70 5-15 :CALCulate{1-16}:FSIMulator:NETWork Subsystem - Simulation . . . . . . . . . . . . . . . . . . . . . 5-72 Calibration Simulation Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72 5-16 :CALCulate{1-16}:FSIMulator:NETWork {1-50} Subsystem - Simulation . . . . . . . . . . . . . . . . 5-84 Calibration Simulation Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-84 5-17 :CALCulate{1-16}:IMPedance:TRANsformation Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . 5-95 Calibration Setup Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-95 5-18 :CALCulate{1-16}:MARKer Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-97 Marker Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-97 Contents-4 PN: 10410-00322 Rev. U MS464xB Series VNA PM Table of Contents (Continued) 5-19 :CALCulate{1-16}:MXP Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-98 Measurement and Mixed Mode Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-98 General Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-98 5-20 :CALCulate{1-16}:NFIGure Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-103 5-21 :CALCulate{1-16}:NXN Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-108 Calibration Option Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-108 I/O Configuration and File Operation Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-108 5-22 :CALCulate{1-16}:OPTical Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-113 O/O Measurement Commands – 2-Port Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-136 5-23 :CALCulate{1-16}:PARameter and :PARameter{1-16} Subsystem . . . . . . . . . . . . . . . . . . . 5-152 Trace Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-152 5-24 :CALCulate{1-16}:PARameter{1-16}:REFerence Subsystem. . . . . . . . . . . . . . . . . . . . . . . . 5-161 5-25 :CALCulate{1-16}:PARameter{1-16}:FSIMulator Subsystem . . . . . . . . . . . . . . . . . . . . . . . . 5-165 Measurement and Mixed Mode Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-165 5-26 :CALCulate{1-16}:PARameter{1-16}:MARKer Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . 5-171 Marker Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-171 5-27 :CALCulate{1-16}:PARameter{1-16}:MSTatistics Subsystem . . . . . . . . . . . . . . . . . . . . . . . 5-174 Marker Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-174 5-28 :CALCulate{1-16}:PARameter{1-16}:SELect Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-176 Trace Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-176 5-29 :CALCulate{1-16}:PARameter{1-16}:COUPling Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . 5-177 Trace Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-177 5-30 :CALCulate{1-16}:POLar Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-178 Trace Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-178 5-31 :CALCulate{1-16}:PROCessing:ORDer Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-180 Time Domain, Group Delay, and Reference Plane Subsystems. . . . . . . . . . . . . . . . . . . 5-180 5-32 :CALCulate{1-16}:PULSe Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-181 Pulse Configuration and Setup Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-181 5-33 :CALCulate{1-16}:REFerence Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-192 Calibration Setup Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-192 Time Domain, Group Delay, and Reference Plane Subsystems. . . . . . . . . . . . . . . . . . . 5-192 5-34 :CALCulate{1-16}[:SELected]:ALTernate Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-201 5-35 :CALCulate{1-16}[:SELected]:CONVersion Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-202 Trace Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-202 5-36 :CALCulate{1-16}[:SELected]:DATA Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-204 I/O Configuration and File Operation Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-204 Trace Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-204 5-37 :CALCulate{1-16}[:SELected]:EYE Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-206 Eye-diagram Configuration and Setup Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-206 5-38 :CALCulate{1-16}[:SELected]:FORmat Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-219 Trace Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-219 5-39 :CALCulate{1-16}[:SELected]:GCOMpression Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . 5-221 Time Domain, Group Delay, and Reference Plane Subsystems. . . . . . . . . . . . . . . . . . . 5-221 MS464xB Series VNA PM PN: 10410-00322 Rev. U Contents-5 Table of Contents (Continued) 5-40 :CALCulate{1-16}[:SELected]:GDELay Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-224 Time Domain, Group Delay, and Reference Plane Subsystems. . . . . . . . . . . . . . . . . . . 5-224 5-41 :CALCulate{1-16}[:SELected]:LIMit Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-225 Limit Line and Segment Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-225 Trace Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-225 5-42 :CALCulate{1-16}[:SELected]:MARKer Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-238 Marker Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-238 5-43 :CALCulate{1-16}[:SELected]:MARKer{1-13} Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . 5-253 Marker Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-253 Trace Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-253 5-44 :CALCulate{1-16}[:SELected]:MATH Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-256 Trace Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-256 5-45 :CALCulate{1-16}[:SELected]:MDATA Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-263 Trace Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-263 5-46 :CALCulate{1-16}[:SELected]:MSTatistics Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-265 5-47 :CALCulate{1-16}[:SELected]:SMITh Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-284 Trace Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-284 5-48 :CALCulate{1-16}[:SELected]:SMOothing Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-286 Trace Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-286 5-49 :CALCulate{1-16}[:SELected]:TDATA Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-287 Trace Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-287 I/O Configuration and File Operation Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-287 5-50 :CALCulate{1-16}[:SELected]:TRANsform:TIME Subsystem . . . . . . . . . . . . . . . . . . . . . . . . 5-289 Time Domain, Group Delay, and Reference Plane Subsystems. . . . . . . . . . . . . . . . . . . 5-289 Trace Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-289 5-51 :CALCulate{1-16}:SNPSetup Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-305 5-52 :CALCulate{1-16}:TMS Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-307 5-53 :CALCulate{1-16}:UFEXtraction:GENB Subsystem - Network Extraction . . . . . . . . . . . . . . 5-310 Calibration Option Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-310 5-54 :CALCulate{1-16}:UFEXtraction:MSTD Subsystem - Network Extraction . . . . . . . . . . . . . . 5-316 Calibration Option Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-316 5-55 :CALCulate{1-16}:UFEXtraction:PLOCalized Subsystem - Network Extraction . . . . . . . . . . 5-326 Calibration Option Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-326 5-56 :CALCulate{1-16}:UFEXtraction:SEQuential Subsystem - Network Extraction . . . . . . . . . . 5-337 Calibration Option Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-337 5-57 :CONTrol:AUXio Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-342 Rear Panel Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-342 5-58 :CONTrol{1-16}:AOUT Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rear Panel Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I/O Configuration and File Operation Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Rear Panel Output Mode as Horizontal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Rear Panel Output Mode as Driven Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Rear Panel Output Mode as TTL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents-6 PN: 10410-00322 Rev. U 5-343 5-343 5-343 5-343 5-344 5-344 MS464xB Series VNA PM Table of Contents (Continued) 5-59 :DISPlay Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Marker Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Limit Line Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-351 5-351 5-351 5-351 5-60 :FORMat Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-373 I/O Configuration and File Operation Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-373 5-61 :HCOPy Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-376 I/O Configuration and File Operation Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-376 5-62 :MMEMory Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-382 I/O Configuration and File Operation Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-382 5-63 :SENSe:BANDwidth Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-392 IF Configuration Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-392 5-64 :SENSe:HOLD Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-393 Trigger, Hold, and External Source Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-393 5-65 :SENSe{1-16}:ABORtcal Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-396 Calibration Subsystems with Actual Calibrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-396 5-66 :SENSe{1-16}:AVERage Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-397 Channel and Sweep Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-397 5-67 :SENSe{1-16}:BANDwidth Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-399 IF Configuration Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-399 5-68 :SENSe{1-16}:BWIDth Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-400 IF Configuration Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-400 5-69 :SENSe{1-16}:CORRection:COEFficient:PORT Subsystem - Simulation . . . . . . . . . . . . . . Calibration Simulation Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibration Type Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-401 5-401 5-401 5-401 5-70 :SENSe{1-16}:CORRection:COEFficient Subsystem - Simulation . . . . . . . . . . . . . . . . . . . . 5-406 Calibration Simulation Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-406 Calibration Type Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-406 5-71 :SENSe{1-16}:CORRection:COLLect:BBCal Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-411 Calibration Subsystems with Actual Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-411 5-72 :SENSe{1-16}:CORRection:COLLect:CALB Subsystem - 4-Port VNAs. . . . . . . . . . . . . . . . Calibration Subsystems with Actual Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibration Type Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-412 5-412 5-412 5-412 5-73 :SENSe{1-16}:CORRection:COLLect:ECAL Subsystem - 4-Port VNAs. . . . . . . . . . . . . . . . 5-414 5-74 :SENSe{1-16}:CORRection:COLLect:DISPlay Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . 5-421 5-75 :SENSe{1-16}:CORRection:COLLect:FLEXible Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . 5-422 Calibration Option Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-422 5-76 :SENSe{1-16}:CORRection:COLLect:FULL4 Subsystem - 4-Port VNAs . . . . . . . . . . . . . . . 5-423 Calibration Subsystems with Actual Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-423 MS464xB Series VNA PM PN: 10410-00322 Rev. U Contents-7 Table of Contents (Continued) 5-77 :SENSe{1-16}:CORRection:COLLect:HYBRid Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . 5-424 Calibration Option Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-424 Calibration Type Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-424 5-78 :SENSe{1-16}:CORRection:COLLect:LRL:BAND{1-5} Subsystem . . . . . . . . . . . . . . . . . . . 5-430 LRL Calibration Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-430 5-79 :SENSe{1-16}:CORRection:COLLect:LRL:CALB Subsystem . . . . . . . . . . . . . . . . . . . . . . . 5-432 LRL Calibration Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-432 5-80 :SENSe{1-16}:CORRection:COLLect:LRL:DEVice{1-10} Subsystem . . . . . . . . . . . . . . . . . 5-447 LRL Calibration Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-447 5-81 :SENSe{1-16}:CORRection:COLLect:LRL:PORT Subsystem - 4-Port VNAs. . . . . . . . . . . . 5-452 LRL Calibration Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-452 5-82 :SENSe{1-16}:CORRection:COLLect:LRL:SINGleton Subsystem - 4-Port VNAs . . . . . . . . 5-454 LRL Calibration Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-454 5-83 :SENSe{1-16}:CORRection:COLLect:LRL:WAVeguide Subsystem. . . . . . . . . . . . . . . . . . . 5-459 LRL Calibration Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-459 5-84 :SENSe{1-16}:CORRection:COLLect:LRL[:CALa] Subsystem. . . . . . . . . . . . . . . . . . . . . . . 5-460 LRL Calibration Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-460 5-85 :SENSe{1-16}:CORRection:COLLect:METHod Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . 5-475 Calibration Setup Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-475 5-86 :SENSe{1-16}:CORRection:COLLect:MICrostrip Subsystem. . . . . . . . . . . . . . . . . . . . . . . . 5-476 Calibration Setup Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-476 5-87 :SENSe{1-16}:CORRection:COLLect:MULTiple Subsystem . . . . . . . . . . . . . . . . . . . . . . . . 5-481 Calibration Setup Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-481 5-88 :SENSe{1-16}:CORRection:COLLect:PORT Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-482 Calibration Subsystems with Actual Calibrations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-482 Calibration Type Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-482 5-89 :SENSe{1-16}:CORRection:COLLect Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-525 Calibration Setup Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-525 5-90 :SENSe{1-16}:CORRection:COLLect:WAVeguide Subsystem . . . . . . . . . . . . . . . . . . . . . . 5-527 Calibration Setup Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-527 5-91 :SENSe{1-16}:CORRection:COLLect[:CALa]:PORT Subsystem . . . . . . . . . . . . . . . . . . . . . 5-534 Calibration Subsystems with Actual Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-534 Calibration Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-534 5-92 :SENSe{1-16}:CORRection:COLLect Subsystem - 2-Port/4-Port VNA . . . . . . . . . . . . . . . . Calibration Setup Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Command Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibration Method Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-536 5-536 5-536 5-536 5-93 :SENSe{1-16}:CORRection:DISPlay Subsystem - 2-Port VNA . . . . . . . . . . . . . . . . . . . . . . 5-550 5-94 :SENSe{1-16}:CORRection:EXTension Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-551 Time Domain, Group Delay, and Reference Plane Subsystems. . . . . . . . . . . . . . . . . . . 5-551 5-95 :SENSe{1-16}:CORRection:INTerpolation Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-552 Calibration Setup Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-552 Contents-8 PN: 10410-00322 Rev. U MS464xB Series VNA PM Table of Contents (Continued) 5-96 :SENSe{1-16}:CORRection:ISOLation Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-553 Calibration Setup Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-553 5-97 :SENSe{1-16}:CORRection:STATe Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-554 Calibration Setup Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-554 5-98 :SENSe{1-16}:DNFigure Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-555 DNFigure Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-555 5-99 :SENSe{1-16}:FREQuency Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-558 Channel and Sweep Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-558 Frequency Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-558 5-100 :SENSe{1-16}:FSEGMent Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-561 Limit Line and Segment Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-561 5-101 :SENSe{1-16}:FSEGMent{1-50} Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-572 Limit Line and Segment Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-572 5-102 :SENSe{1-16}:GRANging Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-578 5-103 :SENSe{1-16}:HOLD Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-579 Trigger, Hold, and External Source Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-579 5-104 :SENSe{1-16}:IMD Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-580 IMD Configuration and Setup Validation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-580 5-105 :SENSe{1-16}:ISEGMent Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-597 Limit Line and Segment Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-597 5-106 :SENSe{1-16}:ISEGMent{1-50} Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-607 Limit Line and Segment Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-607 5-107 :SENSe{1-16}:NFIGure Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-613 5-108 :SENSe{1-16}:OFFSet and :OFFset{1-50} Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-615 Trigger, Hold, and External Source Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-615 General Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-615 5-109 :SENSe{1-16}:RECEiver Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-650 5-110 :SENSe{1-16}:SEGMent Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-652 Limit Line and Segment Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-652 5-111 :SENSe{1-16}:SOURce{1-4} Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-653 Trigger, Hold, and External Source Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-653 5-112 :SENSe{1-16}:SPUR Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-654 Channel and Sweep Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-654 5-113 :SENSe{1-16}:SWEep Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-655 Channel and Sweep Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-655 5-114 :SENSe{1-16}:TS3738 Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-659 5-115 :SENSe{1-16}:TS3739 Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-666 5-116 :SOURce:ALL:EXTernal Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-673 Trigger, Hold, and External Source Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-673 5-117 :SOURce{1-16}:EFFective Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-674 Power Configuration Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-674 5-118 :SOURce{1-16}:MODBB Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-675 Power Configuration Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-675 MS464xB Series VNA PM PN: 10410-00322 Rev. U Contents-9 Table of Contents (Continued) 5-119 :SOURce{1-16}:POWer Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-676 Power Configuration Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-676 5-120 :SOURce{1-16}:TS3739 Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-696 Related Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-696 5-121 :SOURce{1-4}:EXTernal Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-699 Trigger, Hold, and External Source Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-699 5-122 :STATus:OPERation Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-701 5-123 :STATus:QUEStionable Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-703 5-124 :SYSTem Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-706 5-125 :TRIGger[:SEQuence] Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-723 Trigger, Hold, and External Source Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-723 Appendix A—Programming with LabVIEW A-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 A-2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 Programming Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 GPIB Mnemonics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 What is VISA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 Programming Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 A-3 Installing the MS464X LabVIEW Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 Set up VectorStar Remote Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5 A-4 A Quick Start with the Windows GPIB Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8 A-5 Programming Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9 A-6 Example 1 ─ Open a Session to get some Instrument Information . . . . . . . . . . . . . . . . . . . . A-16 A-7 Example 2 ─ Sending the *IDN? Command – Display Results . . . . . . . . . . . . . . . . . . . . . . . A-19 A-8 Example 3 ─ Error Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21 A-9 Example 4 ─ LIST Command – Send to a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-22 A-10 Example 5 ─ Acquiring Trace Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-25 A-11 Example 6 – Smith Chart Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-27 A-12 Example 7 – Output S2P File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-30 A-13 Example 8 – Output BMP File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-31 Appendix B—Programming with LabWindows/CVI B-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 B-2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 Programming Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 GPIB Mnemonics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 What is VISA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 Programming Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2 B-3 Installing the Anritsu au464x LabWindows/CVI Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3 Setup VectorStar for Native Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6 Contents-10 PN: 10410-00322 Rev. U MS464xB Series VNA PM Table of Contents (Continued) B-4 Quick Start with the Windows GPIB Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8 B-5 Programming Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9 Setting up the Driver to Load every time CVI starts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-16 B-6 Example 1 – Open a Session to Obtain Instrument Information. . . . . . . . . . . . . . . . . . . . . . . B-21 B-7 Example 2 – Sending the *IDN? Command and Displaying results . . . . . . . . . . . . . . . . . . . . B-24 B-8 Example 3 – Error Checking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-28 B-9 Example 4 ─ LIST Command – Send to a File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-33 B-10 Example 5 ─ Acquiring Trace Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-38 B-11 Example 6 and 6a– Smith Chart Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-43 Example 6 – Acquire Smith Chart Trace Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-43 Example 6a – Smith Chart Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-47 B-12 Example 7 – Output S2P File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-50 B-13 Example 8 – Output BMP File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-54 Appendix C—Programming with VISA/C# C-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1 C-2 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1 Programming Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1 What is VISA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2 Programming Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4 GPIB Mnemonics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4 C-3 A Quick Start with the Windows GPIB Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5 C-4 Programming Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8 C-5 Example 1 ─ Open Session and *IDN? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11 Example 1 – Code Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11 Example 1 – Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13 C-6 Example 2 ─ Session Parameters and Status Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-16 Example 2 – Code Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-16 Example 2 – Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20 C-7 Example 3 ─ LIST Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-22 Example 3 – Code Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-22 Example 3 – Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-25 C-8 Example 4 ─ Acquiring ASCII Data, Arbitrary Block. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-27 Example 4 – Code Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-27 Example 4 – Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-31 C-9 Example 5 – Acquiring Binary Data, Arbitrary Block. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-32 Example 5 – Code Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-32 Example 5 – Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-36 C-10 Example 6 – Output S2P File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-37 Example 6 – Code Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-37 Example 6 – Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-41 MS464xB Series VNA PM PN: 10410-00322 Rev. U Contents-11 Table of Contents (Continued) C-11 Example 7 – Output a Bitmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-42 Example 7 – Code Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-42 Example 7 – Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-46 Appendix D—Programming Basics with Legacy Software D-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1 D-2 Programming Basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1 VISA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1 Programming Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3 GPIB Mnemonics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3 D-3 Installing the LabVIEW Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4 D-4 Installing the LabWindows/CVI Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7 D-5 Anritsu GPIB, USB, VXI-11, and TCP/IP Exerciser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-10 D-6 VISA and C# Programming Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-12 Create a New Console Application Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-12 Build the Solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-13 Run the Code (Start Debugging). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-13 Example 1 – Opening a Session and Sending the *IDN? Command . . . . . . . . . . . . . . . . D-14 Example 1 Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-15 Example 2 – Session Parameters and Status Checking . . . . . . . . . . . . . . . . . . . . . . . . . . D-17 Example 2 Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-19 Example 3 – Sending Data to a File with the LIST Command. . . . . . . . . . . . . . . . . . . . . . D-21 Example 3 Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-23 Example 4 – Acquiring ASCII Data, Arbitrary Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-25 Example 4 Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-27 Example 5 – Acquiring Binary Data, Arbitrary Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-28 Example 5 Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-30 Example 6 – Output S2P File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-31 Example 6 Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-33 Example 7 – Output a Bitmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-34 Example 7 Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-36 D-7 LabView Programming Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-37 Setup Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-37 Example 1 – Opening a Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-42 Example 2 – Sending the *IDN? Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-44 Example 2 – Error Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-45 Example 3 – Sending Data to a File with the LIST Command. . . . . . . . . . . . . . . . . . . . . . D-46 Example 4 – Acquiring Trace Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-48 Example 5 – Smith Chart Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-48 Example 6 – Output S2P File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-50 Example 7 – Output BMP File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-52 Contents-12 PN: 10410-00322 Rev. U MS464xB Series VNA PM Table of Contents (Continued) D-8 LabWindows/CVI Programming Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-54 Example 0 – Opening a Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-62 Example 1 – Sending the *IDN? Command and Displaying Results. . . . . . . . . . . . . . . . . D-63 Example 2 – Error Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-65 Example 3 – Sending Data to a File with the LIST Command . . . . . . . . . . . . . . . . . . . . . D-67 Example 4 – Acquiring Trace Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-69 Example 5 – Smith Chart Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-72 Example 6 – Output S2P File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-75 Example 7 – Output BMP File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-77 Appendix E—Alphabetical Command Index E-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1 Sorting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1 System Suffix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1 E-2 Alphabetical Command Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1 MS464xB Series VNA PM PN: 10410-00322 Rev. U Contents-13 Contents-14 PN: 10410-00322 Rev. U MS464xB Series VNA PM Chapter 1 — General Information 1-1 About this Manual This manual provides information for remote operation of the VectorStar MS464xB Series VNAs using commands sent from an external controller via the IEEE 488 General Purpose Interface Bus (GPIB), USB, and Ethernet. It includes the following: • A general description of the GPIB and the bus data transfer and control functions • A listing of the IEEE 488 Interface Function Messages recognized by the VNA • A brief description of the Ethernet and USB program interface to the VNA • A complete listing and description of all the Standard Commands for Programmable Instruments (SCPI) commands that can be used to control VNA operation with examples of command usage • See the companion document, Programming Manual Supplement – 10410-00323 for a complete listing of all Anritsu legacy Lightning (37xxxD/E) commands and all Agilent/HP legacy 8510 commands that can be used to control MS464xB Series VNAs. • This manual is intended to be used in conjunction with the VectorStar MS464xB Series Microwave VNA Operation Manual – 10410-00317. Refer to that manual for general information about the VectorStar Series VNAs including equipment set up and front panel (manual mode) operating instructions. Note Many of the images in this document are used as typical representations of the product or of the product features. Your instrument and instrument displays may vary slightly from these images. This manual covers the IEEE 488.2, System and Troubleshooting, and SCPI commands. See the Programming Manual - Supplement, 10410-00323 for descriptions of the Anritsu 37xxxx and HP8510 commands. 1-2 Introduction This chapter provides a general description of the GPIB and the bus data transfer and control functions. It also contains a listing of the MS464xB GPIB interface function subset capability and response to IEEE 488 interface function messages. The GPIB information presented in this chapter is general in nature. For complete and specific information, refer to the following documents, available from the Institute of Electrical and Electronics Engineers: • ANSI/IEEE Standard 488.1-1987 IEEE Standard Digital Interface for Programmable Instrumentation • ANSI/IEEE Standard 488.2-1987 IEEE Standard Codes, Formats, Protocols, and Common Commands These documents precisely define the total specification of the mechanical and electrical interface, and of the data transfer and control protocols. The final section in this chapter, “Minimum/Maximum Instrument Frequency and Related Parameters” on page 1-22, provides a listing of the VNA instrument minimum and maximum frequency settings and related parameters such as default frequency span. These values are provided for standalone VectorStar VNAs as well as for VNAs configured with ME7828A or MS7838A Broadband/Millimeter-Wave/Multiple Source Test Sets. Note When operating the VectorStar VNA through remote programming, the front panel user interface and controls are disabled. To return to local front panel control, press the front panel Clear/Tab key [Clr -->|], keyboard Esc key, or send the RTL command. For general information about GPIB, refer to Section 1-5 “IEEE 488 GPIB Description”. MS464xB Series VNA PM PN: 10410-00322 Rev. U 1-1 1-3 Related Documentation 1-3 General Information Related Documentation The latest product information and documentation can be found on the VectorStar product web page: http://www.anritsu.com/en-us/test-measurement/products/ms4640b-series On this web page, you can select various tabs for more information about your instrument. Included is a “Library” tab which contains links to all the latest technical documentation related to this instrument. Product Information, Compliance, and Safety Refer to the VectorStar Product Information, Compliance, and Safety (PICS) – 10100-00063 for applicable product information, compliance statements, and safety information, including links to applicable product web pages. 1-4 Contacting Anritsu To contact Anritsu, please visit: https://www.anritsu.com/en-US/contact-us From here, you can select the latest sales, service and support contact information in your country or region, provide online feedback, complete a "Talk to Anritsu" form to get your questions answered, or obtain other services offered by Anritsu. 1-2 PN: 10410-00322 Rev. U MS464xB Series VNA PM General Information 1-5 1-5 IEEE 488 GPIB Description IEEE 488 GPIB Description The IEEE 488 General Purpose Interface Bus (GPIB) is an international instrumentation interface standard for integrating instruments, computers, printers, plotters, and other measurement devices into systems. IEEE stands for the Institute of Electrical and Electronics Engineers and is currently the world’s largest technical professional society. Refer to http://www.ieee.org for more information about the society and its standards. The interface between the VectorStar VNA and other devices on the GPIB is via a standard 24-wire GPIB interface cable. This cable uses a double-sided connector where one connector face is a plug and the other a receptacle. These double-function connectors allow parallel connection of two or more cables to a single instrument connector. Caution When two or more cables are connected in parallel, be careful not to bend the attached connectors and damage the rear panel GPIB Port connector. MS464xB Series VNA PM PN: 10410-00322 Rev. U 1-3 1-5 IEEE 488 GPIB Description General Information GPIB Network Restrictions To achieve design performance on the GPIB network bus, the proper timing and voltage level relationships must be maintained. If either the cable length between separate instruments or the accumulated cable length between all instruments is too long, the data and control lines cannot be driven properly and the system may fail to perform. • Network Topology GPIB network topologies can be in any combination of star and/or serial (“daisy-chain”) network topology subject to the limitations below. Looped topologies are prohibited. If a star topology is used, care must be observed when stacking two or more GPIB connectors. • Number of Units The maximum number of physical GPIB devices must be less than or equal to 15 including the controller. • Addresses The default address for a GPIB Controller Device must be 0 (zero). The address for a GPIB-controlled device can be from 1 (one) to 30. Each device address in a GPIB network must be unique. • Total Network Length The network length is measured in meters. The total network length of all cables less than two times the number of instruments, and always less than 20 meters. For example, the maximum length of a 2 instrument network is 4 meters; a 6 instrument network is limited to 12 meters; and networks of 10 or more instruments are limited to 20 meters. • Maximum Network Leg Length The recommended length of any network leg is less than or equal to 4 meters. In all cases, minimize cable lengths to achieve maximum data transfer rates. • Power State Two-thirds of the network devices must be powered on before signaling is started. No devices should be powered up while bus signaling is in operation where devices are actively sending or receiving messages or data. Note For low EMI applications, the GPIB cable should be a fully shielded type with well-grounded metal-shell connectors. Use Anritsu Model 2100-series cables. The devices on the GPIB are connected in parallel, as shown in Figure 1-1. The interface consists of 16 signal lines and 8 ground lines in a shielded cable. Eight of the signal lines are the data lines, DIO 1 through DIO 8. These data lines carry messages (data and commands), one byte at a time, among the GPIB devices. Three of the remaining lines are the handshake lines that control the transfer of message bytes between devices. The five remaining signal lines are referred to as interface management lines. The following paragraphs provide an overview of the GPIB including descriptions of: • “Functional Elements” • “Bus Structure” • “Data Bus Description” • “Data Byte Transfer Control Bus Description” • “General Interface Management Bus Description” • “Device Interface Function Capability” • “Message Types” • “Response to GPIB Interface Function Messages” • “Configuring the Dedicated GPIB Port” • “Configuring the IEEE 488.2 GPIB Port” 1-4 PN: 10410-00322 Rev. U MS464xB Series VNA PM General Information Figure 1-1. 1-5 IEEE 488 GPIB Description GPIB Interface Connection and Bus Structure MS464xB Series VNA PM PN: 10410-00322 Rev. U 1-5 1-5 IEEE 488 GPIB Description General Information Functional Elements Effective communications between devices on the GPIB requires three functional elements; a talker, a listener, and a controller. Each device on the GPIB is categorized as one of these elements depending on its current interface function and capabilities. • Talker A talker is a device capable of sending device-dependent data to another device on the bus when addressed to talk. Only one GPIB device at a time can be an active talker. • Listener A listener is a device capable of receiving device-dependent data from another device on the bus when addressed to listen. Any number of GPIB devices can be listeners simultaneously. • Controller A controller is a device, usually a computer, capable of managing the operation of the GPIB. Only one GPIB device at a time can be an active controller. The active controller manages the transfer of device-dependent data between GPIB devices by designating who will talk and who will listen. • System Controller The system controller is the device that always retains ultimate control of the GPIB. When the system is first powered-up, the system controller is the active controller and manages the GPIB. The system controller can pass control to a device, making it the new active controller. The new active controller, in turn, may pass control on to yet another device. Even if it is not the active controller, the system controller maintains control of the Interface Clear (IFC) and Remote Enable (REN) interface management lines and can thus take control of the GPIB at anytime. 1-6 PN: 10410-00322 Rev. U MS464xB Series VNA PM General Information 1-5 IEEE 488 GPIB Description Bus Structure The GPIB uses 16 signal lines to carry data and commands between the devices connected to the bus. The interface signal lines are organized into three functional groups. • Data Bus (8 lines) • Data Byte Transfer Control Bus (3 lines) • General Interface Management Bus (5 lines) The signal lines in each of the three groups are designated according to function. Table 1-1 lists these designations. Table 1-1. Interface Bus Signal Line Designations Bus Type Signal Line Name Function Data Bus DIO1–DIO8 Data Input/Output, 1 through 8 Data Byte Transfer Control Bus DAV NRFD NDAC Data Available Not Ready For Data Not Data Accepted General Interface Management Bus ATN IFC SRQ REN EOI Attention Interface Clear Service Request Remote Enable End Or Identify Data Bus Description The data bus is the conduit for the transfer of data and commands between the devices on the GPIB. It contains eight bidirectional, active-low signal lines —DIO 1 through DIO 8. Data and commands are transferred over the data bus in byte-serial, bit-parallel form. This means that one byte of data (eight bits) is transferred over the bus at a time. DIO 1 represents the least-significant bit (LSB) in this byte and DIO 8 represents the most-significant bit (MSB). Bytes of data are normally formatted in seven-bit ASCII (American Standard Code for Information Interchange) code. The eighth (parity) bit is not used. Each byte placed on the data bus represents either a command or a data byte. If the Attention (ATN) interface management line is TRUE while the data is transferred, then the data bus is carrying a bus command which is to be received by every GPIB device. If ATN is FALSE, then a data byte is being transferred and only the active listeners will receive that byte. Figure 1-2. Typical GPIB Handshake Operation MS464xB Series VNA PM PN: 10410-00322 Rev. U 1-7 1-5 IEEE 488 GPIB Description General Information Data Byte Transfer Control Bus Description Control of the transfer of each byte of data on the data bus is accomplished by a technique called the “three-wire handshake”, which involves the three signal lines of the Data Byte Transfer Control Bus. This technique forces data transfers at the speed of the slowest listener, which ensures data integrity in multiple listener transfers. One line (DAV) is controlled by the talker, while the other two (NRFD and NDAC) are wired-OR lines shared by all active listeners. The handshake lines, like the other GPIB lines, are active low. The technique is described briefly in the following paragraphs and is depicted in Figure 1-2. For further information, refer to the ANSI/IEEE Standard 488.1 specification. General Interface Management Bus Description The general interface management bus is a group of five signal lines used to manage the flow of information across the GPIB. A description of the function of each of the individual control lines is provided below. • ATN (Attention) The active controller uses the ATN line to define whether the information on the data bus is a command or is data. When ATN is TRUE (low), the bus is in the command mode and the data lines carry bus commands. When ATN is FALSE (high), the bus is in the data mode and the data lines carry device-dependent instructions or data. • EOI (End or Identify) The EOI line is used to indicate the last byte of a multi byte data transfer. The talker sets the EOI line TRUE during the last data byte. The active controller also uses the EOI line in conjunction with the ATN line to initiate a parallel poll sequence. • IFC (Interface Clear) Only the system controller uses this line. When IFC is TRUE (low), all devices on the bus are placed in a known, quiescent state (unaddressed to talk, unaddressed to listen, and service request idle). • REN (Remote Enable) Only the system controller uses this line. When REN is set TRUE (low), the bus is in the remote mode and devices are addressed either to listen or to talk. When the bus is in remote and a device is addressed, it receives instructions from the GPIB rather than from its front panel. When REN is set FALSE (high), the bus and all devices return to local operation. • SRQ (Service Request) The SRQ line is set TRUE (low) by any device requesting service by the active controller. 1-8 PN: 10410-00322 Rev. U MS464xB Series VNA PM General Information 1-5 IEEE 488 GPIB Description Device Interface Function Capability An interface function is the GPIB system element which provides the basic operational facility through which a device can receive, process, and send messages. Each specific interface function may only send or receive a limited set of messages within particular classes of messages. As a result, a set of interface functions is necessary to achieve complete communications among devices on the GPIB. The ANSI/IEEE Standard 488.1 specification defines each of the interface functions along with its specific protocol. The ANSI/IEEE Standard 488.2 specification specifies the minimum set of IEEE 488.1 interface capabilities that each GPIB device must have. This minimum set of interface functions assures that the device is able to send and receive data, request service, and respond to a device clear message. Table 1-2 lists the interface function capability of the VectorStar Series VNA. Table 1-2. VectorStar VNA Interface Function Capability Function Identifier Function VectorStar VNA Capability AH1 Acceptor Handshake Complete Capability SH1 Source Handshake Complete Capability T6 Talker No Talk Only (TON) L4 Listener No Listen Only (LON) SR1 Service Request Complete Capability RL1 Remote/Local Complete Capability PP1 Parallel Poll Complete Capability DC1 Device Clear Complete Capability DT1 Device Trigger Complete Capability C0 C1 C2 C3 C28 Controller Capability Options C0, No Capability C1, System Controller C2, Send IFC and Take Charge C3, Send REN C28, Send IF Messages E2 Tri-State Drivers Three-state bus drivers MS464xB Series VNA PM PN: 10410-00322 Rev. U 1-9 1-5 IEEE 488 GPIB Description General Information Message Types There are three types of information transmitted over the GPIB: • interface function messages • device-specific commands, and • data and instrument status messages. Interface Function Messages The controller manages the flow of information on the GPIB using interface function messages, usually called commands or command messages. Interface function messages perform such functions as initializing the bus, addressing and unaddressing devices, and setting device modes for remote or local operation. There are two types of commands: multiline and uniline. Multiline commands are bytes sent by the active controller over the data bus (DIO1-DIO8) with ATN set TRUE. Uniline commands are signals carried by the individual interface management lines. The user generally has control over these commands; however, the extent of user control depends on the implementation and varies with the specific GPIB interface hardware and software used with the external controller. Device-Specific Commands These commands are keywords or mnemonic codes sent by the external controller to control the setup and operation of the addressed device or instrument. The commands are normally unique to a particular instrument or class of instruments and are described in its documentation. Device-specific commands are transmitted over the data bus of the GPIB to the device in the form of ASCII strings containing one or more keywords or codes. They are decoded by the device’s internal controller and cause the various instrument functions to be performed. Data and Instrument Status Messages These messages are sent by the device to the external controller via the GPIB. They contain measurement results, instrument status, or data files that the device transmits over the data bus in response to specific requests from the external controller. The contents of these messages are instrument specific and may be in the form of ASCII strings or binary data. In some cases data messages will be transmitted from the external controller to the device. For example, messages to load calibration data. An SRQ (service request) is an interface function message sent from the device to the external controller to request service from the controller, usually due to some predetermined status condition or error. To send this message, the device sets the SRQ line of the General Interface Management Bus true, then sends a status byte on the data bus lines. An SRQ interface function message is also sent by the device in response to a serial poll message from the controller, or upon receiving an Output Status Byte(s) command from the controller. The protocols associated with the SRQ functions are defined in the ANSI/IEEE Std 488.2 document. The manner in which interface function messages and device-specific commands are invoked in programs is implementation specific for the GPIB interface used with the external controller. Even though both message types are represented by mnemonics, they are implemented and used in different ways. Normally, the interface function messages are sent automatically by the GPIB driver software in response to invocation of a software function. For example, to send the IFC (Interface Clear) interface function message, one would call the ibsic function of the National Instruments software driver. On the other hand, the command *RST (Reset) is sent in a command string to the addressed device. In the case of the National Instruments example, this would be done by using the ibwrt function call. 1-10 PN: 10410-00322 Rev. U MS464xB Series VNA PM General Information 1-5 IEEE 488 GPIB Description Response to GPIB Interface Function Messages Table 1-3 lists the GPIB interface function messages that the MS464xB will recognize and respond to. With the exception of the Device Clear and Selected Device Clear messages, these messages affect only the operation of the VectorStar VNA GPIB interface. The VNA response for each message is indicated below. Interface function messages are transmitted on the GPIB data lines and interface management lines as either unaddressed or addressed to receive the commands. The manner in which these messages are invoked in programs is implementation dependent. For more programming information, refer to the documentation included with the GPIB interface used for the external controller and to the IEEE 488.1 specification. Table 1-3. VectorStar VNA Response to GPIB Interface Function Messages Interface Function Message Addressed Command VectorStar VNA Response Device Clear (DCL) Selected Device Clear (SDC) No Yes Clears the input and output buffers and resets the parser. Go To Local (GTL) Yes Returns the VNA to local front panel control. Group Execute Trigger (GET) Yes In step sweep, single trigger: triggers a sweep. In list sweep, manual trigger: triggers step to next index within start/stop index boundaries. In list sweep, single trigger: triggers a sweep. Interface Clear (IFC) No Stops the VNA GPIB interface from listening or talking. (The front panel controls are not cleared.) Local Lockout (LLO) No Disables the front panel menu RETURN TO LOCAL soft-key. Remote Enable (REN) No Places the VNA under remote (GPIB) control when it has been addressed to listen. Serial-Poll Enable (SPE) No Outputs the serial-poll status byte. Serial-Poll Disable (SPD) No Disables the serial-poll function. Parallel-Poll Configure (PPC) Yes The VectorStar VNA does not respond to Parallel-Poll messages. Parallel-Poll Unconfigure No The VectorStar VNA does not respond to Parallel-Poll messages. MS464xB Series VNA PM PN: 10410-00322 Rev. U 1-11 1-5 IEEE 488 GPIB Description General Information Configuring the Dedicated GPIB Port Use this procedure to setup the dedicated GPIB port to control other GPIB devices such as Power Meters or Signal Generators by using the VNA rear panel Dedicated GPIB Port. An example of a complex GPIB configuration with the VNA as the GPIB controller is shown in Figure 1-3. GPIB 10 MHz Input 10 MHz Output to BNC T-Connector Synthesizer #1 2 GPIB 10 MHz Input Dedicated GPIB IFs External I/O Synthesizer #2 Control Input IFs 3739x Test Set VectorStar VNA 3 4 1 mm-Wave Module 1 mm-Wave Module 2 5 6 1. VectorStar VNA 4. 3739x Broadband Test Set 2. Synthesizer #1 5. Millimeter-Wave (mm-Wave) Module #1 3. Synthesizer #2 6. mm-Wave Module #2 Figure 1-3. 1-12 VNA as a Remote GPIB Controller for Synthesizers PN: 10410-00322 Rev. U MS464xB Series VNA PM General Information 1. 1-5 IEEE 488 GPIB Description Connect GPIB devices to the VNA rear panel Dedicated GPIB Port using the appropriate length GPIB cable. 1. GPIB Port: Rear panel Dedicated GPIB Port D-24 (f) 2. GPIB Cable and Connector: GPIB cable and connector. double-sided connector. Cable routes to any controlled GPIB devices. Figure 1-4. VNA Dedicated GPIB Port and GPIB Cable Connection 2. Power-up the VectorStar VNA and any attached GPIB devices, and allow the system to warm up. 3. Navigate to the Remote Inter. menu as follows: MAIN | System > | SYSTEM | Remote Interface > | REMOTE INTER/ MS464xB Series VNA PM PN: 10410-00322 Rev. U 1-13 1-5 IEEE 488 GPIB Description General Information . Figure 1-5. 1-14 REMOTE INTERFACE (REMOTE INTER) Menu PN: 10410-00322 Rev. U MS464xB Series VNA PM General Information 1-5 IEEE 488 GPIB Description The GPIB address for any controlled device can be kept at the factory default values or changed as required. The default GPIB addresses are: • VectorStar MS464xB Series VNA = 6 • VectorStar MN469xC Series Test Set = 16 • External Source 1 = 4 • External Source 2 = 5 • External Source 3 = 2 • External Source 4 = 3 • Power Meter = 13 • Frequency Counter = 7 • W-Band Power Meter = 15 The GPIB addresses for the External Sources can be changed from the Ext Src Addr sub-menu available at: • MAIN | System | SYSTEM | Remote Interface | REMOTE INTER | Ext Sources | EXT SRC ADDR. Figure 1-6. EXT SRC ADDR (EXTERNAL SOURCE ADDRESS) Menu 4. If a change of GPIB address is required, click the device button, and the device field toolbar appears as shown below: 5. Use the front panel keys, a keyboard, or mouse to set the required GPIB address. 6. Click the Enter button to set the new GPIB address. MS464xB Series VNA PM PN: 10410-00322 Rev. U 1-15 1-5 IEEE 488 GPIB Description General Information Configuring the IEEE 488.2 GPIB Port Use this procedure to set up the talker/listener port to control the VNA remotely over an IEEE 488.2 GPIB bus network. In this configuration, an external computer/controller is physically connected to the VNA rear panel IEEE 488.2 GPIB Port with a standard GPIB cable. Most of the VectorStar VNA functions (except power on/off and initialization of the hard disk) can be controlled remotely by an external computer/controller via the IEEE-488.2 GPIB bus network. 1. Connect the VNA to the GPIB Controller using the rear panel IEEE 488.2 GPIB Port DB-24 (f) connector and a standard GPIB cable. 1. IEEE 488.2 Talker/Listener Port: Rear panel IEEE 488.2 Talker/Listener GPIB Port D-24 (f) connector. Figure 1-7. 2. 2. GPIB Cable and Connector: GPIB cable and double-sided connector. Cable routes to the GPIB Controller computer. IEEE 488.2 GPIB Talker/Listener Port and GPIB Cable Connection Apply power to the VectorStar VNA and allow the system to warm up. Once the software has finished loading and start-up testing is complete, the instrument is ready to be remotely controlled via the GPIB. The instrument will not respond to GPIB commands until the instrument’s software has been loaded. Note 1-16 The factory default GPIB address for the instrument is six (6). PN: 10410-00322 Rev. U MS464xB Series VNA PM General Information 1-6 Resetting GPIB Addresses To change the VectorStar VNA GPIB address: 1. Navigate to the REMOTE INTER menu: MAIN | System | SYSTEM | Remote Interface | REMOTE INTER 2. On the Remote Inter. menu, click the IEEE 488.2 GPIB button. The IEEE 488.2 GPIB toolbar appears below the icon toolbar near the top of the display. 3. Use the front panel keys, a keyboard, or a mouse to set the required GPIB address. 4. Click the Enter button to set the new GPIB address. 1-6 Resetting GPIB Addresses The VectorStar VNA Reset commands received over the GPIB do not reset GPIB addresses. Below is a list of the Reset commands which are recognized by the VectorStar VNA. • IEEE488 Commands • *RST - Instrument reset • Lightning Commands • RST - Instrument reset • RST0 - Instrument reset • RST1 - Instrument reset • HP8510 Commands • FACTPRES - Perform a factory preset • PRES - Instrument reset • Native SCPI Commands • :SYSTem:PRESet - Performs Preset • :SYSTem:PRESet:ZERo - Performs a Reset Zero Background ATE programs use a Reset command to return the VNA to a known state. Most large ATE programs which do multiple operations use a Reset command at the start of each operation. However, allowing a Reset command to alter GPIB addresses could unexpectedly cause loss of communication with the External Controller and/or the External Instruments on the VNA Dedicated Bus. Therefore the reset commands listed above DO NOT alter GPIB addresses. Returning the GPIB Addresses to Default If it is necessary to return the GPIB addresses associated with the VectorStar VNA to their normal default values, use the following procedure. 1. Exit the VectorStar VNA application by selecting MENU BAR | File | Exit at the top of the Display. This will return execution to the PC desktop. 2. Start the VectorStar Reset Application by double clicking its Icon (Yellow Starburst) on the Desktop. 3. When the VectorStar Reset Application starts up, click the Reset VectorStar button. This will sequentially reset the VectorStar application and the VectorStar 100K application. 4. When done, exit the application. 5. VectorStar VNA operation can be resumed by double clicking the Blue VectorStar Icon on the Desktop. MS464xB Series VNA PM PN: 10410-00322 Rev. U 1-17 1-7 Ethernet LAN TCP/IP and USB Description 1-7 General Information Ethernet LAN TCP/IP and USB Description The VectorStar VNA supports Ethernet 10/100 BASE-T. The instrument is connected directly to the LAN via the rear panel RJ-45 Ethernet Port using a standard CAT-5 Ethernet cable. The MS464xB Series VNAs can also be controlled remotely across a Universal Serial Bus (USB) Type 2 network by a PC equipped with a USB control application using the rear panel USB Control Port. The general requirements for manual Ethernet LAN configuration are discussed in the sections below. Note This section is provided for general information about manually configuring an Ethernet connection and does not apply to USB networking. Consult your local network administrator for the exact requirements and settings that are required for your network installation. TCP/IP General Requirements and Settings Transmission Control Protocol/Internet Protocol (TCP/IP) is a network protocol. In the Windows operating system, TCP/IP is automatically installed and in most cases, installation, configuration, and communication are transparent to the user. In a TCP/IP network, you must provide IP addresses and other information to clients. Clients may also require a naming service or a method for name resolution. The TCP/IP protocol setup requires the following information: • IP Address Every device in a TCP/IP network requires an IP address that consists of four numbers, each between 0 and 255, separated by periods. For example: 128.111.122.42 is a valid IP address. • Subnet Mask The subnet mask distinguishes the portion of the IP address that is the network identification (ID) address from the portion that is the station ID address. When the subnet mask 255.255.0.0 is applied to the IP address above, it would identify the network ID address as 128.111 and the station ID address as 122.42. All stations in the same Local Area Network (LAN) should have the same network ID, but different station IDs. • Default Gateway A TCP/IP network can have a gateway to communicate beyond the LAN identified by the network ID. A gateway is a computer or electronic device that is connected to two different networks and can move TCP/IP data from one network to the other. A single LAN that is not connected to other LANs requires a default gateway setting of 0.0.0.0. The default gateway setting for the VectorStar MS4640B Series VNA is 0.0.0.0. If your network has a gateway, then the default gateway would be set to the appropriate value of your gateway. • Hardware Address (MAC Address) An Ethernet address is a unique 48-bit value that identifies a network interface card internal to the VNA to the rest of the network. Every network card has a unique Ethernet address permanently stored into its memory. • TCP/IP Port Number Reports the currently used TCP/IP port number with Port #5001 set as the default. In general, it should not be changed. If the port number is changed, do not change it to 5000 as that port is used by VXI-11. Ports below #5000 are generally reserved for other services and devices. Custom settings generally should use settings of #5001 and higher. • Network Interface Setup TCP/IP connectivity requires setting up the parameters described at the beginning of this section. You may need to contact your network administrator or refer to your network documentation for further assistance. The following procedure is a general overview of how to set up a general LAN connection on both the VNA and the remote machine. The actual menus and sequence may vary. 1-18 PN: 10410-00322 Rev. U MS464xB Series VNA PM General Information 1-7 Ethernet LAN TCP/IP and USB Description Default Plug-and-Play Configuration The VectorStar VNA and its Windows operating system comes pre-configured and ready to plug into and connect with an existing Ethernet network. The Ethernet network must provide DNS/DHCP and be configured with a gateway. Connection can also be made to a USB network. USB networks are typically auto-detecting without the need for configuration; however, a special USB network cable (described below) is required. The required PC-to-Instrument USB 2.0 networking cable (also called a USB-USB cable, USB networking cable, or USB bridge cable) has a small electronic circuit module in the middle of the cable that allows the PC and the VectorStar VNA to talk to each other at 480 Mbps. The PC-to-Instrument USB cable is user-provided and does not come with the VectorStar VNA. Warning Using the wrong type of USB-USB cable can result in damage to the PC and/or VectorStar USB ports and/or power supplies. Do NOT use a so-called “USB A/A” cable that is similar to a serial port cross-over null-modem cable. For Ethernet connection, connect the VectorStar VNA to the network with an Ethernet cable between the VNA rear panel RJ-45 Ethernet Port and your local network port. For USB networks, use the USB network cable defined above between the VNA rear panel USB Type 2 Port and your local network hub. 1. Ethernet Port – Rear panel Ethernet RJ45 (f) port or USB Type 2 connection Figure 1-8. 2. Ethernet CAT-5 RJ-45 or USB cable from LAN (Local Area Network). VectorStar VNA Network Connection Windows will automatically detect the network settings and configure the network connection. MS464xB Series VNA PM PN: 10410-00322 Rev. U 1-19 1-7 Ethernet LAN TCP/IP and USB Description General Information Manually Configuring TCP/IP Ethernet LAN Settings To see the current network settings for your VectorStar VNA, with the VectorStar Application Software running, navigate to the Network Interface (Network Interf.) menu as follows: • MAIN | System | SYSTEM | Ntwk Interface | NETWORK INTERF. Figure 1-9. NETWORK INTERFACE (NETWORK INTERF) Menu The top eight (8) display buttons provide information for the current network settings. Changes to these settings must be made through the Microsoft Windows configuration utilities by clicking Network Connections. The Network Connections dialog box shows the current available local networks. Note 1-20 You may need to consult your network documentation or network administrator for assistance in manually configuring your network setup. The Windows network connections Help may provide information related to computer networking. PN: 10410-00322 Rev. U MS464xB Series VNA PM General Information 1-8 1-8 Configuring the Remote Language Configuring the Remote Language The VectorStar VNA command parser responds to Native SCPI commands, legacy Anritsu Lightning commands, or to HP8510 commands. When the programming language is set to Native: • The VectorStar VNA responds to Lightning commands on a secondary basis. • Does not respond to HP8510 commands. When the programming language is set to Lightning: • The VectorStar VNA responds to SCPI commands on a secondary basis. • Does not respond to HP8510 commands. When the language is set to HP8510: • The VectorStar VNA responds to SCPI commands on a secondary basis. • And responds to Lightning commands on a tertiary basis. Processing and response times are improved if the Remote Language setting matches the majority of the sent commands. Scripts written in older versions of the Lightning command set or in the HP/Agilent 8510 command set may need editing to be fully compatible with the VNA. Not all Lightning and HP/Agilent commands are supported. Procedure If necessary, you can change the VNA default GPIB language from Native to Lightning or HP8510 as follows: 1. Navigate to the Remote Lang. menu: MAIN | System | SYSTEM | Remote Interface | REMOTE INTER | Language Selection | REMOTE LANG Figure 1-10. REMOTE LANGUAGE (REMOTE LANG) Menu 2. Select the interface language being used. 3. Click Back at the bottom of the menu to return to the REMOTE INTER menu. MS464xB Series VNA PM PN: 10410-00322 Rev. U 1-21 1-9 Minimum/Maximum Instrument Frequency and Related Parameters 1-9 General Information Minimum/Maximum Instrument Frequency and Related Parameters The minimum and maximum instrument frequencies depend on the instrument model and the installed options. The general frequency limits for the :SENSe{1-16}:FREQuency subsystem and related commands are defined below in Table 1-4, Table 1-5, Table 1-6, Table 1-7, and Table 1-8. In general, the frequency default values and limits are affected by three factors: • Instrument model number, which defines the VNA standalone instrument high-side frequency limit • Installed options (Option 70), if equipped, which define the VNA instrument low-side limit. On MS464xB Series VNAs, Option 70 provides a lower limit specified to 70 kHz, but which is allowed to go to 40 kHz. • Attached broadband, millimeter-wave, and/or multiple source equipment (if equipped) that defines the VNA system high-side frequency limit. Standalone VNAs For the base VNA, the frequency range is established by the models (for the high end) and options (for the low end). For the higher frequency systems, the limits are dependent on the exact hardware being used and the instrument mode. The tables below provide standalone VNA frequency limits: • Table 1-4, “Standalone VNAs – Default Start, Default CW, and Default Stop Frequencies” on page 1-23 • Table 1-5, “Standalone VNAs – Minimum Start, Minimum CW, and Maximum Start Frequencies” on page 1-24 • Table 1-6, “Standalone VNAs – Minimum Stop, Maximum Stop, and Maximum CW Frequencies” on page 1-25 • Table 1-7, “Standalone VNAs – Default Frequency Span and Maximum Frequency Span” on page 1-26 • Table 1-8, “Standalone VNAs – Minimum Center Frequency and Maximum Center Frequency” on page 1-27 • Table 1-9, “Standalone VNAs – Default Center Frequencies” on page 1-28 1-22 PN: 10410-00322 Rev. U MS464xB Series VNA PM General Information 1-9 Minimum/Maximum Instrument Frequency and Related Parameters Standalone VNAs – Default Start, Default CW, and Default Stop Frequencies The instrument start frequency depends if the Option 70 – 70 kHz Low End Frequency Extension is installed. Table 1-4. Model MS4642B MS4644B MS4645B MS4647B Standalone VNAs – Default Start, Default CW, and Default Stop Frequencies Default Start Frequency or Default CW Frequency without Option 70 Default Start Frequency or Default CW Frequency with Option 70 Default Stop Frequency 1.0000000000E+007 7.0000000000E+004 2.0000000000E+010 10 MHz 70 kHz 20 GHz 1.0000000000E+007 7.0000000000E+004 4.0000000000E+010 10 MHz 70 kHz 40 GHz 1.0000000000E+007 7.0000000000E+004 5.0000000000E+010 10 MHz 70 kHz 50 GHz 1.0000000000E+007 7.0000000000E+004 7.0000000000E+010 10 MHz 70 kHz 70 GHz MS464xB Series VNA PM PN: 10410-00322 Rev. U 1-23 1-9 Minimum/Maximum Instrument Frequency and Related Parameters General Information Standalone VNAs – Minimum Start, Minimum CW, and Maximum Start Frequencies The highest possible setting for the Start Frequency is the Stop Frequency minus 2 Hz. This yields a sweep with three data points. Table 1-5. Model MS4642B MS4644B MS4645B MS4647B 1-24 Standalone VNAs – Minimum Start, Minimum CW, and Maximum Start Frequencies Minimum Start Frequency or Minimum CW Frequency without Option 70 Minimum Start Frequency or Minimum CW Frequency with Option 70 Maximum Start Frequency (Start Frequency – 2 Hz) 1.0000000000E+007 7.0000000000E+004 1.9999999998E+010 10 MHz 70 kHz 20 GHz – 2 Hz 1.0000000000E+007 7.0000000000E+004 3.9999999998E+010 10 MHz 70 kHz 40 GHz – 2 Hz 1.0000000000E+007 7.0000000000E+004 4.9999999998E+010 10 MHz 70 kHz 50 GHz – 2 Hz 1.0000000000E+007 7.0000000000E+004 6.9999999998E+010 10 MHz 70 kHz 70 GHz – 2 Hz PN: 10410-00322 Rev. U MS464xB Series VNA PM General Information 1-9 Minimum/Maximum Instrument Frequency and Related Parameters Standalone VNAs – Minimum Stop and Maximum Stop Frequencies The lowest possible setting for the stop frequency is the start frequency plus 2 Hz which yields as sweep of three (3) data points. Table 1-6. Model MS4642B MS4644B MS4645B MS4647B Standalone VNAs – Minimum Stop, Maximum Stop, and Maximum CW Frequencies Minimum Stop Frequency without Option 70 Minimum Stop Frequency with Option 70 Stop Min = Start + 2 Hz = 3 data points Stop Min = Start + 2 Hz = 3 data points Maximum Stop Frequency or Maximum CW Frequency Stop Max = Instrument Max) 1.0000002000E+007 7.0002000000E+004 2.0000000000E+010 10 MHz + 2 Hz 70 kHz + 2 Hz 20 GHz 1.0000002000E+007 7.0002000000E+004 4.0000000000E+010 10 MHz + 2 Hz 70 kHz + 2 Hz 40 GHz 1.0000002000E+007 7.0002000000E+004 5.0000000000E+010 10 MHz + 2 Hz 70 kHz + 2 Hz 50 GHz 1.0000002000E+007 7.0002000000E+004 7.0000000000E+010 10 MHz + 2 Hz 70 kHz + 2 Hz 70 GHz MS464xB Series VNA PM PN: 10410-00322 Rev. U 1-25 1-9 Minimum/Maximum Instrument Frequency and Related Parameters General Information Standalone VNAs – Default Frequency Span and Maximum Frequency Span The frequency span equals the stop frequency minus the start frequency. The minimum possible frequency span is frequency is 2 Hz. Table 1-7. Standalone VNAs – Default Frequency Span and Maximum Frequency Span Minimum Frequency Span All Models Default Frequency Span or Maximum Frequency Span without Option 70 Default Frequency Span or Maximum Frequency Span with Option 70 Span Min = 2 Hz Span Max = Stop – Start Span Max = Stop – Start Model MS4642B MS4644B MS4645B MS4647B 1-26 2 Hz 2 Hz 2 Hz 2 Hz 1.9990000000E+010 1.9999930000E+010 20 GHz – 10 MHz 20 GHz – 70 kHz 3.9990000000E+010 3.9999930000E+010 40 GHz – 10 MHz 40 GHz – 70 kHz 4.9990000000E+010 4.9999930000E+010 50 GHz – 10 MHz 50 GHz – 70 kHz 6.9990000000E+010 6.9999930000E+010 70 GHz – 10 MHz 70 GHz – 70 kHz PN: 10410-00322 Rev. U MS464xB Series VNA PM General Information 1-9 Minimum/Maximum Instrument Frequency and Related Parameters Standalone VNAs – Minimum Center and Maximum Center Frequencies The minimum possible center frequency is the minimum start frequency plus 1 Hz. The maximum possible center frequency is the maximum stop frequency minus 1 Hz. Table 1-8. Model MS4642B MS4644B MS4645B MS4647B Standalone VNAs – Minimum Center Frequency and Maximum Center Frequency Minimum Center Frequency without Option 70 Minimum Center Frequency with Option 070 Maximum Center Frequency All Models Center Min = Start + 1 Hz Center Min = Start + 1 Hz Center Max = Stop – 1 Hz 1.0000001000E+007 7.0001000000E+004 1.9999999999E+010 10 MHz + 1 Hz 70 kHz + 1 Hz 20 GHz – 1 Hz 1.0000001000E+007 7.0001000000E+004 3.9999999999E+010 10 MHz + 1 Hz 70 kHz + 1 Hz 40 GHz – 1 Hz 1.0000001000E+007 7.0001000000E+004 4.9999999999E+010 10 MHz + 1 Hz 70 kHz + 1 Hz 50 GHz – 1 Hz 1.0000001000E+007 7.0001000000E+004 6.9999999999E+010 10 MHz + 1 Hz 70 kHz + 1 Hz 70 GHz – 1 Hz MS464xB Series VNA PM PN: 10410-00322 Rev. U 1-27 1-9 Minimum/Maximum Instrument Frequency and Related Parameters General Information Standalone VNAs – Default Center Frequencies The center frequency is equal to Start Frequency plus the Stop Frequency divided by two (2). The minimum possible frequency span is 2 Hz. Table 1-9. Standalone VNAs – Default Center Frequencies Default Center Frequency without Option 70 Default Center Frequency with Option 70 Center Default = (Start + Stop)/2 Center Default = (Start + Stop)/2 Model Center Minimum Frequency Span = 2 Hz Minimum Frequency Span = 2 Hz MS4642B 1.0005000000E+010 1.0000035000E+010 MS4644B 2.0005000000E+010 2.0000035000E+010 MS4645B 2.5005000000E+010 2.5000035000E+010 MS4647B 3.5005000000E+010 3.5000035000E+010 VNA Systems with ME7828A Configured as Broadband System For VNAs with ME7828A configured as a broadband system (mode selection and hardware selection): • The VNA upper limit is 110 GHz • The VNA lower limit is determined by the VNA installed option: • With Option 70, the lower limit is specified to 70 kHz, but is allowed to go to 40 kHz. • Without Option 70, the lower limit is 10 MHz. VNA Systems with ME7828A Configured as a Millimeter-Wave System For VNAs with ME7828A configured as a millimeter-wave system, the frequency range is established by the selected waveguide band. For example, 325 GHz to 500 GHz for WR-2.2. VNA Systems with ME7828A Using Multiple Source For VNAs with ME7828A configured using multiple sources, the frequency range is defined by the band equations and the installed hardware. The VNA system has no knowledge of the exact frequency range so it will report that of the base VNA. VNA Systems with ME7838x Modular Broadband System For VNAs equipped with the ME7838x modular broadband/millimeter-wave system in Modular BB mode: • For ME7838A, The VNA acquires a broadband personality with an upper frequency limit of 125 GHz. • For ME7838D, The VNA acquires a broadband personality with an upper frequency limit of 145 GHz. • For ME7838E, The VNA acquires a broadband personality with an upper frequency limit of 110 GHz. • The VNA lower limit is determined by the VNA installed option: • With Option 70, the lower limit is specified to 70 kHz, but is allowed to go to 40 kHz. • Without Option 70, the lower limit is 10 MHz. VNA Systems with ME7838x Configured as a Millimeter-Wave System For VNAs with ME7838x configured as a millimeter-wave system, the frequency range is established by the selected waveguide band. For example, 325 GHz to 500 GHz for WR-2.2. 1-28 PN: 10410-00322 Rev. U MS464xB Series VNA PM Chapter 2 — Programming the VectorStar Series VNA 2-1 Introduction This chapter provides an introduction to programming the VectorStar VNA with the SCPI programming language. It also includes descriptions of the command types that the MS4640B accepts, program command structures, data parameters and input/output specifications, and notational conventions. Information on the MS4640B status system and trigger system programming is also provided. Note When operating the VectorStar VNA through remote programming, the front panel user interface and controls are disabled. To return to local front panel control, press the front panel Clear/Tab key [Clr -->|], keyboard Esc key, or send the RTL command. For general information about GPIB, refer to Section 1-5 “IEEE 488 GPIB Description”. 2-2 Introduction to SCPI Programming The Standard Commands for Programmable Instruments (SCPI) defines a set of standard programming commands for use by all SCPI compatible instruments. SCPI is intended to give the ATE user a consistent environment for program development. It does so by defining controller messages, instrument responses, and message formats for all SCPI compatible instruments. The IEEE 488 (GPIB) interface for the MS4640B is designed to conform to the requirements of SCPI 1999.0. The set of SCPI commands implemented by the MS4640B GPIB interface provides a comprehensive set of programming functions covering all of the major functions of the MS4640B. Command Types SCPI commands, which are also referred to as SCPI instructions, are messages to the instrument to perform specific tasks. The MS4640B command set, introduced in this chapter, includes these command types: • “IEEE 488.2 Commands” • “System Commands” • “SCPI Commands” • “Native SCPI Commands” • “Anritsu Lightning VNA Commands” • “HP8510 Commands” MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-1 2-3 IEEE 488.2 Commands 2-3 Programming the VectorStar Series VNA IEEE 488.2 Commands The IEEE-488.2 commands are defined in the IEEE-488.2 standard and must be implemented by all SCPI compatible instruments. The mandated commands listed in Table 2-1 are identified by the asterisk (*) at the beginning of the command keyword. These commands are used to control instrument status registers, status reporting, synchronization, and other common functions. The IEEE 488.2 required common commands are described in detail in the first half of Chapter 3, “IEEE Commands” starting with “IEEE 488.2 Commands” on page 3-2. Table 2-1. 2-4 IEEE 488.2 Mandated Commands *CLS *ESE *IDN? *OPT? *STB? *DDT *ESE? *OPC *RST *TRG *DDT? *ESR? *OPC? *SRE *TST? *SRE? *WAI System Commands The set of system commands are primarily used to control the state of the MS4640B for system diagnostics, hardware calibration, and troubleshooting. 2-5 SCPI Commands There are two general classifications of SCPI commands described in the two sections below. They are: • Required (or mandated) SCPI Commands • Native SCPI Commands Note that the Required SCPI Commands are a subset of the Native SCPI commands. Required SCPI Commands The required SCPI commands are listed in the table below Table 2-2. SCPI Required or Mandated Commands :SYSTem :STATus :ERRor :OPERation [:NEXT]? [:EVENt]? :CONDition? :ENABle :QUEStionable [:EVENt]? :CONDition? :ENABle The SCPI Required Commands are described in detail in Chapter 5, “SCPI Commands” in the following sections: • “:STATus:OPERation Subsystem” on page 5-701 • “:STATus:QUEStionable Subsystem” on page 5-703 • “:SYSTem Subsystem” on page 5-706 2-2 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-6 Anritsu Lightning VNA Commands Native SCPI Commands The majority of the commands are native SCPI commands and are also described in detail in Chapter 5, “SCPI Commands”. The commands are organized into subsystems, starting with the “:CALCulate{1-16}:APPLication:MEASurement Subsystem” on page 5-14 and ending with the “:TRIGger[:SEQuence] Subsystem” on page 5-723. Depending on the number of keywords in the command, the subsystems are grouped by either the first two keywords (such as :CALCulate:MARKer Subsystem) or the first three keywords (such as :CALCulate{1-16}[:SELected]:CONVersion Subsystem) The commands are listed in strict ASCII sort sequence. See the sections below starting with “Command Requirements” on page 2-4 for definitions of parameters and other notations. 2-6 Anritsu Lightning VNA Commands Many (but not all) commands used on the Anritsu Lightning 37xxxD/E VNAs are supported on the MS4640B Series VNA. The supported and non-supported commands are described in the companion manual, VectorStar MS464xB Series VNA Programming Manual Supplement – 10410-00323. For additional detailed information on Lightning 37xxxx VNA commands and programming the Anritsu Lightning 37xxxD/E VNAs, refer to either of the following manuals available on the Anritsu web site: • Lightning 37xxxD Programming Manual – 10410-00262 • Lightning 37xxxE Programming Manual – 10410-00301 Using Anritsu Lightning VNA Commands All Anritsu Lightning VNA commands operate on the VectorStar MS4640B VNA Active Channel, and there are no Lightning commands which can change the VectorStar VNA active channel to another one. If the VectorStar VNA is configured with multiple channels, the Lightning commands will then only operate on the currently active VectorStar channel. No error will be generated. Other Lightning command limitations are noted in the command listing in the Programming Manual Supplement – 10410-00323. See the sections below for definitions of parameters and other notations. VectorStar VNA Language Set to Lightning When using Anritsu Lightning commands, note that: 1. Recognition of the Lightning command set is provided for compatibility with existing Lightning ATE programs, and the use of the Lightning command set is not recommended for new development. 2. Some of the Lightning commands may not work as expected if the programming Language is not set to Lightning via the LANG command (or LANG LIGHT). • For example, markers in the Native language are trace based. This means that each trace has its own set of markers, independent of the other traces. • In Lightning there are only 6 markers. If you move Marker1 on Trace1 to 3 GHz, Marker1 on the other 3 traces will also go to 3 GHz. If you want the Lightning behavior on the markers, you need to set the Language to Lightning. 2-7 HP8510 Commands Many commands used on the HP8510 VNA are also supported on the MS464xB Series VNA. The supported commands are described in detail in the aforementioned Programming Manual Supplement – 10410-00323. See the sections below for definitions of parameters and other notations. MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-3 2-8 Command Requirements 2-8 Programming the VectorStar Series VNA Command Requirements Query Commands All commands, unless specifically noted in the commands syntax descriptions, have a query form. Exceptions are noted as: • Commands without a query form have a query status of “No Query”. • Queries without a command form have a query status of “Query Only”. As defined in IEEE-488.2, a query is a command with a question mark symbol appended (examples are *ESR? and *TST?). When a query form of a command is received, the current setting associated with the command is placed in the output buffer. Query commands always return the short form of the parameter. For example, NORMal or INVerted is returned as NORM or INV. Boolean values are returned as 1 or 0, even when they can be set as ON or OFF. Command Names Typical SCPI commands consist of one or more keywords, parameters, and punctuation. SCPI command keywords can be a mixture of upper and lower case characters. Except for common commands, each keyword has a long and a short form. In this manual, the long form is presented with the short form in upper case and the remainder in lower case. For example, the long form of the command keyword to control the instrument display is :DISPlay. The short form keyword is usually the first four characters of the long form (example: DISP for DISPlay). The exception to this is when the long form is longer than four characters and the fourth character is a vowel. In such cases, the vowel is dropped and the short form becomes the first three characters of the long form. Example: the short form of the keyword :POWer is :POW. Some command keywords may have a numeric suffix to differentiate between multiple instrument features such as multiple pulse widths. For example, keywords :WIDTh2 (or :WIDT2). As with any programming language, the exact command keywords and command syntax must be used. The syntax of the individual commands is described in detail in Chapter 5, “SCPI Commands”. Unrecognized versions of long form or short form commands, or improper syntax, will generate an error. Hierarchical Command Structure All SCPI commands, except the common commands, are organized in a hierarchical structure similar to the inverted tree file structure used in most computers. The SCPI standard refers to this structure as “the Command Tree.” The command keywords that correspond to the major instrument control functions are located at the top of the command tree. The command keywords for the MS4640B SCPI command set are shown in the diagram below. Figure 2-1. 2-4 MS4640B Partial SCPI Command Tree PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-8 Command Requirements All MS4640B SCPI commands have one or more subcommands (keywords) associated with them to further define the instrument function to be controlled. The subcommand keywords may also have one or more associated subcommands (keywords). Each subcommand level adds another layer to the command tree. The command keyword and its associated subcommand keywords form a portion of the command tree called a command subsystem. The :FORMat command subsystem is shown below. Figure 2-2. SCPI :FORMat Subsystem Data Parameters Data parameters, referred to simply as “parameters,” are the quantitative values used as arguments for the command keywords. The parameter type associated with a particular SCPI command is determined by the type of information required to control the particular instrument function. For example, Boolean (ON | OFF) type parameters are used with commands that control switch functions. The command descriptions in Chapter 5, “SCPI Commands” specify the type of data parameter to be used with each command. The most commonly used parameter types are numeric, extended numeric, discrete, and Boolean. • Numeric Numeric parameters comprise integer numbers or any number in decimal or scientific notation, and may include polarity signs. This includes , , and numeric data as defined in “Parameter Notations” on page 2-7. This type of numeric element is abbreviated as throughout this document. • Extended Numeric Extended numeric parameters include values such as MAXimum and MINimum. Extended numerics are not supported in the current MS4640B SCPI implementation. • Discrete Discrete parameters, such as INTernal and EXTernal, are used to control program settings to a predetermined finite value or condition. • Boolean Boolean parameters represent binary conditions and may be expressed as ON, OFF or 1, 0. Note The VectorStar command parser will generally accept all numerical values within the parameter ranges specified. In cases where a command parameter value is outside of the indicated range or resolution of the instrument, the nearest appropriate value will be entered. MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-5 2-9 Notational Conventions 2-9 Programming the VectorStar Series VNA Notational Conventions The SCPI interface standardizes command syntax and style that simplifies the task of programming across a wide range of instrumentation. As with any programming language, the exact command keywords and command syntax must be used. Unrecognized commands or improper syntax will not function. General Notations The syntax conventions that are used for all SCPI command keywords and data parameter descriptions in this manual are described below: Table 2-3. General Notations : A colon links command keywords together to form commands. The colon is not an actual part of the keyword, but is a signal to the SCPI interface parser. A colon must precede a root keyword immediately following a semicolon (see “Notational Examples” on page 2-8). ; A semicolon separates commands if multiple commands are placed on a single program line (see “Notational Examples” on page 2-8). [] Square brackets enclose one or more optional keywords. {} Braces enclose one or more keyword parameters that may be included one or more times. | A vertical bar (also called a “pipe”) indicates “or” and is used to separate alternative parameter options. For Example: ON | OFF is the same as ON or OFF. <> Angle brackets enclose parameter descriptions. ::= Means “is defined as” For example: ::= indicates that can replace . For further information about SCPI command syntax and style, refer to the Standard Commands for Programmable Instruments (SCPI) 1999.0 document. 2-6 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-9 Notational Conventions Parameter Notations The following syntax conventions are used for all data parameter descriptions in this manual: Table 2-4. Parameter Notations Parameter Definition A non-delimited 7-bit ASCII text. The end of the text must be terminated with the 0A character (decimal 10) and concurrent setting (^) of the GPIB End of Transmission State (EOI). (also called ) text is transmitted only at the end of a program or response message. IEEE-488.2 block data format. Can be in ASCII, XML, or other format. Boolean values in format; numeric 1 or 0 ON | OFF. Can also be represented as 1 or 0, where 1 means ON and 0 means OFF Boolean parameters are always returned as 1 or 0 in format by query commands Examples: CW, FIXed, UP, and DOWN Positive Infinity. Positive infinity is represented as 9.9E37. The numeric value for positive infinity fits into a 32-bit IEEE 754 floating point number. An unsigned integer without a decimal point (implied radix point) Not Applicable Not A Number. Not a number is represented as 9.91E37 and is defined in IEEE 754. Typically used where applications are dividing zero by zero or subtracting infinity from infinity. NAN is also used to represent missing data such as a trace that has not been yet acquired. Negative Infinity. Negative infinity is represented as -9.9E37. The numeric value for negative infinity fits into a 32-bit IEEE 754 floating point number. A signed integer without a decimal point (implied radix point) A signed number with an explicit radix point A scaled explicit decimal point numeric value with an exponent (e.g., floating point number) Values in NR1, NR2, or NR3 formats are accepted. Logically, | | Also or SCPI numeric value as: | MINimum | MAXimum | DEFault | UP | DOWN | NAN or NotANumber | INF or INFinity | NINF or NegativeINFinity or other types or SCPI numeric value as: | MINimum | MAXimum | DEFault | UP | DOWN | NAN or NotANumber | INF or INFinity | NINF or NegativeINFinity or other types ASCII characters surrounded by double quotes For example: “C:\Anritsu\VectorStar\filename.s2p” MPND Numeric Limit. Maximum Positive/Negative Double Precision Number. ± 1.792 693 134 860 E+308 MPNF Numeric Limit. Maximum Positive/Negative Float Number ± 3.402 819 E+38 MPNI Numeric Limit. Maximum Positive/Negative Integer - 2 147 483 648 to +2 147 483 647 Refer to “Data Transmission Methods” on page 2-10 for detailed information about parameter input/output and transferring data to/from the instrument. MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-7 2-9 Notational Conventions Programming the VectorStar Series VNA Notational Examples The following is an example showing command syntax: :SENSe1:FREQuency:STARt 2.0E9 Command statements read from left to right and from top to bottom. In the command statement above, the :FREQuency keyword immediately follows the :SENSe1 keyword with no separating space. A space is required between the command string and its argument. Note that the first keyword in the command string does not require a leading colon; however, it is good practice to always use a leading colon for all keywords. The following is an example of a multiple command statement that uses two separate commands in a single statement: :SENSe1:FREQuency:STARt 2.0E9;:SENSe1:FREQuency:STOP 20.0E9 Using the command keyword short form, the command string above would be: :SENS1:FREQ:STAR 2.0E9;:SENS1:FREQ:STOP 20.0E9 Note the semicolon used to join the commands. Also note the leading colon used immediately after the semicolon. Band Equation MPNI, Limited by the band equation. The band equation depends whether or not CW is set. If CW is off, the band equation equals: Source = (Multiplier/Divisor) x (Frequency plus Offset Frequency) If CW is on, the band equation equals: Source = (Multiplier/Divisor) + Offset Frequency 2-8 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-10 2-10 Numeric Data Suffix Reference Numeric Data Suffix Reference Unit suffixes are not required for data parameters, provided the values are scaled for the global default units. The MS4640B SCPI default units are: • Hz (hertz) for frequency-related parameters • s (second) for time-related parameters • m (meter) for distance-related parameters • ohm for impedance-related parameters • dB for power-related parameters • Henry and Farad for reactance-related parameters For example, the commands below set the MS4640B marker 1 frequency to 3 GHz. :CALCulate1:MARKer1:X 3000000000 :CALCulate1:MARKer1:X 3.0E9 The following table provides a reference to the I/O parameter types (and the appropriate multiplier) used with the MS4640B VNA. Table 2-5. Numeric Data Suffix Code Parameter Type Multiplier DB, DBL, DBM Power 1.0 DEG Phase 1.0 RAD Phase 180/(180/Pi) HZ Frequency (Hertz) 1.0 KHZ Frequency (Kilohertz) 1.0E3 MHZ Frequency (Megahertz) 1.0E6 GHZ Frequency (Gigahertz) 1.0E9 REU Real 1.0 IMU Imaginary 1.0 S Time 1.0 MS Time (Millisecond) 1.0E-3 US, USC Time (Microsecond) 1.0E-6 NS, NSC Time (Nanosecond) 1.0E-9 PS, PSC Time (Picosecond) 1.0E-12 M, MTR Distance (Meter) 1.0 CM, CMT Distance (Centimeter) 1.0E-2 MM, MMT Distance (Millimeter) 1.0E-3 OHM Impedance 1.0 V, VLT Voltage 1.0 MV Voltage (Millivolt) 1.0E-3 XM3 Unitless 1.0E-3 XX1 Unitless 1.0 XX3 Unitless 1.0E3 MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-9 2-11 Data Transmission Methods 2-11 Programming the VectorStar Series VNA Data Transmission Methods Data transmissions to and from the MS4640B conform to the protocols specified by the IEEE 488.2 GPIB Standard. The 488.2 Standard specifies how any data, such as ASCII numbers, strings, or blocks of data bytes, will be transmitted over the GPIB. This section describes the various transmission methods in use by the MS4640B. The transmission method names described below (also called notations) will be used throughout the Programming Manual when describing specific MS4640B data transfer commands. Data transmission notations are easily distinguished in text as they are always shown surrounded by the “less than” and the “greater than” characters (< >). The transmission type notations used in describing various MS4640B VNA data transmissions are: • For ASCII numbers, the notations are: , , , or • For ASCII strings (printable characters and print formatting codes), the notation is: • For generic (7-bit) ASCII characters, the notation is: • For generic binary bytes, (7-bit ASCII or binary), the notation is: This notation represents ASCII integer values. A comma (,) is used to separate multiple values sent in a single command's input or output string. Examples of values that can be represented by notation: 10 -29,179 This notation represents ASCII floating point values in decimal point format. A comma (,) is used to separate multiple values sent in a single command's input or output string. Examples of values that can be represented by notation: 1.0 -0.00015 12.743,-180.07 This notation represents ASCII floating point values in exponential format (scientific notation). A comma (,) is used to separate multiple values sent in a single command's input or output string. Examples of values that can be represented by notation: 1.0E9 -7.056E3 9.0E-2,3.42E2 This notation is used to signify that data can be in either , , or format as described above. Examples of values that can be represented by notation: 1.0E-9 10.005 -83,4.5E2,-234.9901 2-10 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-11 Data Transmission Methods This notation represents a string of ASCII characters (including non-printable characters) that is delimited (surrounded) with either single quotes (' ') or double quotes (" "). The string can include text formatting characters such as line feed, space, carriage return, or printer control characters. Note that if a double quote character must be sent as part of the string, then it must be followed by an additional double quote. Alternatively, the string can be sent using single quotes (See "cal_file" example below). Examples of data represented by notation: "1/15/98" "Save ""cal_file"" now" 'Save "cal_file" now' or This notation represents undelimited 7-bit ASCII text. The end of the text must be terminated with the 0A character (decimal 10) and concurrent setting (^) of the GPIB End of Transmission State (EOI). This requirement makes it necessary for text to be transmitted only at the end of a program or response message, i.e., at the end of a multiple input or output statement. Example of data represented by notation: ANRITSU,MS4642B,123456,1.0<0A^EOI> The example shows a sample response from the *IDN?, 488.2 common query. In the example, the instrument identifies itself as an ANRITSU MS4642B, with serial number 123456, and software version 1.0 installed. Note Note that decimal 10 (0A character) must be sent with the EOI to signal the end of transmission. or This notation represents data that is transmitted as 8-bit data bytes (00–FF hex, 0–255 decimal, notation is ). This is useful for transmitting large blocks of: • Formatted ASCII data • Formatted XML data • Formatted binary data • Unformatted binary data The data stream is immediately preceded by a variable length ASCII header that is encoded with the number of data bytes to be sent. The header always starts with the pound (#) character. The header and the transmitted data messages are described as follows: #nm1..mn ... Where: # = The pound sign character. Required for binary data transfer. n = Number of digits to follow (m1..mn) that make up the number m. m1..mn = Taken together, this makes up the number m which is the number of data bytes to follow that constitute the requested data. = An 8 bit binary data byte. This is the data (or information) being sent. Note If n = 0, then m is omitted, and transmission end is signaled by sending the line feed character (0A, or decimal 10) and concurrent setting (^) of the GPIB End Of Transmission State (EOI) immediately following the last . MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-11 2-11 Data Transmission Methods Programming the VectorStar Series VNA Example 1: #3204 ... Example 1 shows how 204 8-bit bytes are transmitted using the proper header. The header in this example is comprised of 5 characters (#3204). It begins with the pound character (#). The next character (3) indicates there are 3 digits to follow that indicate the number of bytes being transmitted (204). The next three characters (204) indicate the number of data bytes being transmitted immediately after the header. Next comes the actual data bytes, or information, being transmitted ( ... ). Example 2: #512808 ... Example 2 shows how 12808 bytes are transmitted using the proper header. The header in this example is comprised of 7 characters (#512808). It begins with the pound character (#). The next character (5) indicates there are 5 digits to follow that indicate the number of bytes being transmitted (12808). The next five characters (12808) indicate the number of data bytes being transmitted immediately after the header. Next comes the actual data bytes, or information, being transmitted ( ... ). Note Examples 1 and 2 above demonstrate the form referred to as . It is so called because the number of data bytes being transmitted is known from the encoded header. Example 3: #0 ... <0A^EOI> Example 3 shows how an unknown number of bytes are transmitted using the proper header. The header in this example is comprised of 2 characters (#0). As usual, the header begins with the pound character (#). The next character (0) indicates there is an unknown number of data bytes being transmitted immediately after the header. Next comes the actual data bytes being transmitted ( ... ). The end of the data stream is signaled by sending the line feed character (0A, or decimal 10) and concurrent setting (^) of the GPIB End of Transmission State (EOI). Note 2-12 Example 3, above, demonstrates a special form of data referred to as the . It is so called because the number of data bytes being transmitted is unknown, and therefore cannot be encoded in the header. Instead, the header always consists of the pound and zero characters (#0) and end of the data stream is always signaled by sending the line feed character (0A, or decimal 10) and concurrent setting (^) of the GPIB End of Transmission State (EOI). This requirement makes it necessary for text to be transmitted only at the end of a program or response message (at the end of a multiple input or output statement). PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-11 Data Transmission Methods Character program data such as CW, FIXed, UP, and DOWN. A single instance in a command or query is . If multiple instances are required, each is identified such as or and the individual elements are separated by commas: • , • , , • , , , MPND The instrument numeric limit as the Maximum Positive/Negative Double Precision Number or: +/– 1.792 639 134 86 E+308 MPNF The instrument numeric limit as the Maximum Positive/Negative Float Number or: +/- 3.402 819 E+38 MPNI The instrument numeric limit as the Maximum Positive/Negative Integer or: - 2 147 483 648 to +2 147 483 647 Formatting Data Output Three commands are provided to alter the way the arbitrary block header for output data is formed. • FDH0 Specifies that the length of the arbitrary block header will be minimized; that is, the byte count section will not contain leading zeros, thus its length is indeterminate. This means that a program must decode the header in order to skip over it. FDH0 is the default mode when the programming language is selected as Lightning (see “Configuring the Remote Language” on page 1-21). • FDH1 Specifies that the length of the arbitrary block header will be fixed at 11 characters. This is accomplished by forcing leading zeros as required in the byte count section. This means that a program can skip over the arbitrary block header by skipping 11 characters. FDH1 is the default mode when the programming language is selected as Native (see “Configuring the Remote Language” on page 1-21). • FDH2 Specifies that no arbitrary block header will be sent with the next transmission. This mode is not in compliance with IEEE 488.2 specifications and will persist for all subsequent program messages. • FDHX? FDH mode query yields the following results: • 0: FDH0 • 1: FDH1 • 2: FDH2 MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-13 2-11 Data Transmission Methods Programming the VectorStar Series VNA ASCII or Binary Data Format The following sections discuss the various data output formats: Non-Array Data The formats used for data transfers not involving numerical data arrays are preset. They always occur in either binary format or ASCII format, depending on the data. These data transfers include a variety of information. Examples include: • Instrument setup strings • Marker data, queries • Disk directory listings Numerical Data Arrays Numerical data array transfers are used to transfer the following types of data: • Measurement data • Calibration data • Sweep frequency, time, or distance values Each of these data transfer types are individually explained below. You can select either binary or ASCII format for data transfers involving numerical data arrays. The commands described below select and keep the format for all subsequent data transfers. • ASCII Format - FMA ASCII formatted values represented in , , , or formats. The MS4640B VNA accepts any of the above formats as input. It will always output values using exponential format with each value represented using 18 characters plus a comma to separate multiple values. • Binary Formats • FMB Each eight consecutive data bytes represent one floating point value in IEEE 754 64-bit format (double precision, 8 byte, floating point value). • FMC Each four consecutive data bytes represent one floating point value in IEEE 754 32-bit format (single precision, 4 byte, floating point value). • FMX? FMA, FMB, FMC format selection query • Byte Ordering • MSB Byte ordering is most significant byte first. For use only with FMB and FMC. This is the optional byte mode for the MS4640B. • LSB Byte ordering is least significant byte first. For use with FMB and FMC. This is required for transferring data to/from Intel/IBM based computers. LSB is the default mode. • XSB? MSB, LSB format selection query. • FMT0 Turn ASCII enhancement off (normal default mode). • FMT1 Turn ASCII enhancement on. • FMTX? 2-14 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-11 Data Transmission Methods ASCII enhancement ON/OFF status query. The following SCPI commands select either ASCII or Binary format as described above: :FORMat:DATA Where the arguments of ASC or ASCII ::= FMA, REAL ::= FMB, REAL32 ::= FMC :FORMat:DATA? is the ASC or ASCII, REAL, or REAL32 format selection query. :FORMat:BORDer Where the arguments of NORMAL ::= MSB, SWAPPED ::= LSB :FORMat:BORDer? is the MSB | LSB format selection query. MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-15 2-11 Data Transmission Methods Programming the VectorStar Series VNA Enhanced ASCII Formatting Enhanced ASCII formatting can be applied to both non-array ASCII data and numerical data arrays in the FMA format when this data is output within an format. The format selectively replaces comma data element separators with a line feeds (ASCII 10) in order to enhance the visual effect. The following provides two examples of this enhanced structure: • An unenhanced directory listing #9000000392Directory of C:\ 1-30-96 13:03,UTIL 1-25-96 12:58,PLOT BMB 38462 1-22-96 14:41,PLOT BMC 307446 1-22-96 14:41,TTT CAL 44174 1-22-96 17:02,TTT2 CAL 44174 1-22-96 17:16,PLOT1 DAT 10323 1-22-96 14:03,PLOT1 HGL 19899 1-22-96 14:02,PLOT2 HGL 38462 1-25-96 13:16,8 Files 502940 Bytes • An enhanced directory listing #9000000392 Directory of C:\ 1-30-96 13:03 UTIL 1-25-96 12:58 PLOT BMB 38462 1-22-96 14:41 PLOT BMC 307446 1-22-96 14:41 TTT CAL 44174 1-22-96 17:02 TTT2 CAL 44174 1-22-96 17:16 PLOT1 DAT 10323 1-22-96 14:03 PLOT1 HGL 19899 1-22-96 14:02 PLOT2 HGL 38462 1-25-96 13:16 8 Files 502940 Bytes • An unenhanced response to OCD #9000000189-9.99750733376E-01, 3.21409821510E-01, 3.60706359148E-01, 9.82860028744E-01, 7.76742696762E-01,-5.06587028503E-01,-5.07535457611E-01, -8.45697641373E-01,-6.10321164131E-01,6.05827927589E-01 • An enhanced response to OCD #9000000189 -9.99750733376E-01, 3.21409821510E-01 3.60706359148E-01, 9.82860028744E-01 7.76742696762E-01,-5.06587028503E-01 -5.07535457611E-01,-8.45697641373E-01 -6.10321164131E-01, 6.05827927589E-01 2-16 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-12 2-12 Calculating the Byte Size Calculating the Byte Size This section describes the factors for calculating the byte size of responses to selected remote-only queries. The byte size of the resultant data from several of the remote only queries depends on several factors: • Parameters per Output • Numbers Output per Data Point • Bytes Output per Number • Size of Block Data • Number of Bytes Output Numbers Output-per-Data Point (NODP) The data for each data point is a complex number (A + jB) where A and B are floating point numbers. This data is saved internally for use and possible future output. Additionally, if an RF correction is active, the RF correction is applied to the RAW measurement and the result is saved internally for use and possible future output. Either the RAW or CORRECTED data are taken and converted into the data format for the display type selected. This data is saved internally in the FORMATTED (final) measurement form for use and possible future output. When this conversion takes place, the data will, in most cases, still be two orthogonal numbers. However, several of the displays types throw away a portion of the data and the result will be one number only. The display types that produce only one number are: • Group Delay • Imaginary • Linear Magnitude • Log Magnitude • Phase • Power Out • Real • SWR To summarize, the RAW, CORRECTED, and FORMATTED data output will be two numbers-per-point, unless the display type is one of those mentioned above. Bytes Output-per-Number (BOPN) The number of bytes output per number is shown below: Table 2-6. Bytes Output per Number Number Output Format Output-per-Number (ASCII) 14 plus comma (short form data) 19 plus comma (long form data) FMB (double precision binary) 8 FMC (single precision binary) 4 FMA MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-17 2-13 GPIB Input Buffer Size and NRFD Holdoff Programming the VectorStar Series VNA Size of Data Block (SODB) In the case where there is only one parameter to output, the formula is: SODB = NODP * BOPN * Number of points in the sweep If the command is O4SC, O4FD, or O4SR, the formula is: SODB = 8 * BOPN * Number of points in the sweep Number of Bytes Output (NBO) The number of bytes output is the number of bytes transmitted over the GPIB. In most cases, the data block is proceeded by an arbitrary block header followed by an end character (line feed), as shown below: • Response Message = [Arbitrary Block Header] + [Data Block] + [End Character] The size of the end character is one byte. The size of the arbitrary block header is variable between 2 and 11. If we always assume an arbitrary block header size of 11, then: NBO = 12 + SODB. For example: • The VNA is set up for a one channel, four-trace display with a 1601 point sweep. • Trace 1 is displaying S11 in LogMag and Phase format • Trace 2 is displaying S12 in LogMag format • Trace 3 is displaying S21 in Phase format • Trace 4 is displaying S22 in Smith Chart format • The output formatting commands CH2, FMC, and LSB are received The number of output bytes for the O4FD query command is: NBO = 12 + 8 * 4 * 1601 = 51244 bytes The number of output bytes for the ORD query command is: NBO = 12 + 2 * 4 * 1601 = 12820 bytes The number of output bytes for the OFD3 query command is: NBO = 12 + 1 * 4 * 1601 = 6416 bytes The number of output bytes for the FMA or O4SR query command is: NBO = 12 + 8 * 19 * 1601 = 243364 bytes 2-13 GPIB Input Buffer Size and NRFD Holdoff VectorStar VNAs provide a very large input buffer that can hold up to 100 commands. Each command plus any associated data can be as large as the amount of memory available in the VNA at the time. If a programmer attempts to exceed 100 commands, the GPIB bus will go into Not Ready For Data (NRFD) Holdoff. This Holdoff condition will hold onto the controller PC until a command is executed which frees up room for another command. Then the new command will be read in. Some controller PCs can detect this Holdoff condition and programmers interpret this condition as an Error. It is not an Error. Rather, it is a function provided by any listener device to guarantee that commands and data are not lost. It might be an ATE program error, but not a VNA error. 2-18 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-14 2-14 Synchronization of GPIB Commands Synchronization of GPIB Commands The VectorStar VNA provides synchronization of the GPIB by executing commands in a serial fashion. Subsequent commands will not be parsed and executed until the current GPIB command is parsed and completely executed. Indeed, as far as VNA operations are concerned, if this serial execution method is not incorporated, the VNA, the GPIB bus, and the controller PC will be in chaos. Avoiding this chaos condition is so important that the IEEE488.2 standard mandated 3 commands to be provided: *OPC, *OPC?, and *WAI. Note For more information, see the descriptions of the *OPC, *OPC?, and *WAI commands in Chapter 3, “IEEE Commands”. This synchronization is accomplished by the GPIB parser which waits for a Completed signal from the internal interface after starting execution of the command. While the parser is waiting, it is not parsing newer commands. Subsequent commands are put into the input buffer, awaiting their turn to be parsed and executed. 2-15 Forcing the Parser to Stop Waiting The parser will wait forever for the Completed signal as discussed above in “Synchronization of GPIB Commands”. Therefore there is no GPIB command (which would itself require parsing) that can stop the parser from waiting. The controller PC will have to send a GPIB bus command called Device Clear (DCL) or Selected Device Clear (SDC). SDC is directed at a particular device address. DCL will perform the same action on all devices on the Bus. Among the required things DCL and SDC do is reset the Parser. This causes the parser to stop waiting for the ‘Completed’ signal and get ready to execute a command. In the IEEE488.2 Specification, see IEEE488.2 Section 5.8 and IEEE488.1 Section 4.10 for a discussion of DCL and SDC. 2-16 How Can I Abort an RF or Hardware Calibration Flat Test Port Power Calibration and Linearity Calibrations are also Hardware Calibrations. From the front panel, an operator can start and abort these calibrations with ease. Usually there is a STOP or ABORT button. One can also send the GPIB command ‘ABORT’ to abort these manually initiated calibrations. However, when a calibration is initiated from the GPIB, the parser is busy waiting for the ‘Completed’ message from the internal interface and is not available to parse the ‘ABORT’ command to abort the calibration. Refer to the two sections above ‘Synchronization of GPIB commands’ and ‘Forcing the Parser to stop waiting’ to see how that is done. Once the parser is ready for a new command, send the ‘ABORT’ command. 2-17 GPIB Time-Out Settings VectorStar and Lightning VNAs provide synchronization with the GPIB by executing commands in a serial fashion. A new command will not be parsed and executed until the previous command has finished processing. Therefore, the synchronization commands stipulated in IEEE 488.2 (*OPC?, *OPC, and *WAI) execute with ease. Lightning VNAs provide a very large input buffer that permits storing many commands until they can be executed. The VectorStar VNAs can store very large command strings (a series of characters terminated with a line feed), but only two strings at most. This creates a situation where the GPIB bus can go into Not Ready for Data (NRFD) hold off if the controller sends more than two command strings at a time. NRFD hold off will hold onto the controller until it can store the data byte that is currently being transferred. This hold off merely guarantees that no data byte will be lost from a message. Although some controllers can detect this hold off, it's occurrence is of no consequence and it is how instruments are kept communicating at the same rate on the GPIB. MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-19 2-17 GPIB Time-Out Settings Programming the VectorStar Series VNA Some commands may take a very long time to execute, such as waiting for the end of a sweep when the IF bandwidth is very low (1 Hz to 100 Hz). In spite of the long sweep time, the controller should avoid timing out because it creates a situation where synchronization and data can be lost. A controller time-out also leaves the GPIB and the VNA in an unknown I/O state. This unknown I/O state may not be responsive because the proper data handshake has been interrupted, thus creating a hung bus. In many cases, the GPIB parser will also be busy participating in a long event, such as when the commands TRS;WFS are sent. The parser will not be available until the sweep is finished. The only way to get the parser to stop its current task and start processing new commands is to assert the Interface Clear Line (IFC) and issue a GPIB bus command called Device Clear (DCL). These two commands together brings the parser back to the Ready for Data (RFD) state. The commands also reset the input and output buffers, which results in both input and output data being lost. Below is a sequence that shows how to apply a time-out properly: SETTIMEOUT(40000); // Sets a longer time-out for the controller. OUTPUT ; RST // RST (reset) is a command that can take 30 seconds or longer. ENTER ; ONP // Outputs the number of points. The actual wait occurs here. SETTIMEOUT(20000); // Sets the time-out back to its normal value. Setting the proper time-out on the controller is very important to guarantee that the GPIB will be synchronized and data will not be lost. One should choose a time-out that allows most operations to finish without problems and set the time-out to different values on those commands that require a longer time to execute. If time-outs do occur in program execution, the time-out settings for the particular commands in question should be increased. If a time-out is due to an application error, such as sending a syntax error preceding a query or an impossible state is set up such as being in HOLD and waiting for the end of the sweep, the coding error should be fixed and the time-out setting left as it is. Timing out also leaves the bus in an unknown I/O state, so a DCL should be sent to synchronize handshaking. USB or VXI-11 do not provide an IFC, but they do provide a DCL. 2-20 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-18 2-18 Trace Type Parameters and Coefficients Trace Type Parameters and Coefficients The following table provides a reference for the various graph types and related data types used in the VectorStar Series VNA. Table 2-7. Trace Parameters and Coefficients (1 of 4) Trace Name SCPI Keyword Display Trace Abbreviation Group Delay GDELay Trace Graph Format Default Reference Level Reference Level Range Single Rectilinear Graph 0 Single Rectilinear Graph 0 Resolution Range Scale Default Reference Position Scale Num of VertIcal Div. Default Resolution Parameter / Division ±9.9999E2 1 microsecond 1E-13 to 1E9 5 4 to 30 ±9.9999E2 1 Unit (U) 1E-5 to 1E6 5 4 to 30 Top = 0 ±9.9999E2 Bottom = 0 Top = 10 U -NA- Top = 5 Top = 4 to 30 GDEL Imaginary IMAGinary IMAG Linear Mag and Phase LINPHase Double Rectilinear Graphs LINPH Log Mag and Phase LOGPHase Double Rectilinear Graphs Top = 0 ±9.9999E2 Bottom = 0 MLINear Top = 10 dB Bottom = 45 degrees LOGPH Linear Mag Bottom = 5 Bottom = 45 degrees Bottom = 4 to 30 Top = 1E-3 to 1E3 Top = 5 Top = 4 to 30 Bottom = 5 Bottom = 1E-2 to 1E6 Bottom = 4 to 30 Single Rectilinear Graph 0 ±9.9999E2 10 U 1E-5 to 1E6 5 4 to 30 Single Rectilinear Graph 0 ±9.9999E2 10 dB 1E-3 to 1E3 5 4 to 30 Single Rectilinear Graph 0 ±9.9999E2 45 degrees 1E-2 to 1E6 5 4 to 30 Polar Graph 5 1E-8 to 9.9999E2 1U 2E-9 to 1E6 -NA- -NA- MLIN Log Mag MLOGarithmic MLOG Phase PHASe PHAS Linear Polar Lin/Phase PLINear PLIN MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-21 2-18 Trace Type Parameters and Coefficients Table 2-7. Programming the VectorStar Series VNA Trace Parameters and Coefficients (2 of 4) Trace Name SCPI Keyword Display Trace Abbreviation Linear Polar Real/Imag Resolution Range Default Resolution Parameter / Division Scale Default Reference Position 1E-8 to 9.9999E2 1U 2E-9 to 1E6 -NA- -NA- 0 ±9.9999E2 10 dB 1E-5 to 1E6 -NA- -NA- Polar Graph 0 ±9.9999E2 10 dB 1E-5 to 1E6 -NA- -NA- Single Rectilinear Graph 0 dBm ±9.9999E2 10 dB 1E-3 to 1E3 -NA- -NA- Single Rectilinear Graph 0 dBm ±9.9999E2 10 dB 1E-3 to 1E3 5 4 to 30 Single Rectilinear Graph 0 ±9.9999E2 1U 1E-5 to 1E6 5 4 to 30 Double Rectilinear Graphs TOP = 0 ±9.9999E2 Top = 1 U Top = 1E-5 to 1E6 Top = 5 Top = 4 to 30 Trace Graph Format Default Reference Level Reference Level Range Polar Graph 5 Polar Graph Scale Num of VertIcal Div. PLINCOMPlex PLIN Log Polar Log/Phase PLOGarithmic PLOG Log Polar Real/Imag PLOGCOMPlex PLOGCOMP Power In PWRIn PWRI Power Out PWROut PWRO Real REAL REAL Real and Imaginary REIMaginary Bottom = 0 SADCOMPlex Bottom = 40 to 30 Bottom = 1E-5 to 1E6 REIM Smith (G + jB) Real/Imag Bottom = 5 Bottom = 1 U Smith Chart - Admittance (Complex) -NA- ±9.9999E2 1U 1E-5 to 1E6 -NA- -NA- Smith Chart - Admittance (Linear) -NA- ±9.9999E2 10 U 1E-5 to 1E6 -NA- -NA- SADCOMP Smith (G + jB) Lin/Phase SADLINear SADLIN 2-22 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA Table 2-7. 2-18 Trace Type Parameters and Coefficients Trace Parameters and Coefficients (3 of 4) Trace Name SCPI Keyword Display Trace Abbreviation Smith (G + jB) Log/Phase SADLOGarith mic Resolution Range Parameter / Division Scale Default Reference Position Scale Num of VertIcal Div. 10 U 1E-5 to 1E6 -NA- -NA- ±9.9999E2 10 U 1E-5 to 1E6 -NA- -NA- -NA- ±9.9999E2 10 U 1E-5 to 1E6 -NA- -NA- Smith Chart - Impedance (Linear) -NA- ±9.9999E2 10 U 1E-5 to 1E6 -NA- -NA- Smith Chart - Impedance (Log) -NA- ±9.9999E2 10 U 1E-5 to 1E6 -NA- -NA- Smith Chart - Impedance (Impedance) -NA- ±9.9999E2 10 U 1E-5 to 1E6 -NA- -NA- Single Rectilinear Graph 0 ±9.9999E2 10 U 1E-5 to 1E6 5 4 to 30 Single Rectilinear Graph 0 Ohms ±9.9999E2 10 Ohms 1E-5 to 1E6 5 4 to 30 Single Rectilinear Graph 0 Ohms ±9.9999E2 10 Ohms 1E-5 to 1E6 5 4 to 30 Trace Graph Format Default Reference Level Reference Level Range Default Resolution Smith Chart - Admittance (Log) -NA- ±9.9999E2 Smith Chart - Admittance (Admittance) -NA- Smith Chart - Impedance (Complex) SADLOG Smith (G + jB) Admittance SADMittance SADM Smith (R + jX) Real/Imag SCOMPlex SCOMP Smith (R + jX) Lin/Phase SLINear SLIN Smith (R + jX) Log/Phase SLOGarithmic SLOG Smith (R + jX) Impedance SMITh SMIT SWR SWR SWR Impedance Real ZREAL ZREAL Impedance Imaginary ZIMAGinary ZIMAG MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-23 2-18 Trace Type Parameters and Coefficients Table 2-7. Programming the VectorStar Series VNA Trace Parameters and Coefficients (4 of 4) Trace Name SCPI Keyword Display Trace Abbreviation Impedance Magnitude ZMAGNitude Resolution Range Parameter / Division Scale Default Reference Position Scale Num of VertIcal Div. 10 Ohms 1E-5 to 1E6 5 4 to 30 Top = 10 Ohms Top = 1E-5 to 1E6 Top = 5 Top = 4 to 30 Bottom = 10 Ohms Bottom = 1E-5 to 1E6 Trace Graph Format Default Reference Level Reference Level Range Default Resolution Single Rectilinear Graph 0 Ohms ±9.9999E2 Double Rectilinear Graphs Top = 0 Ohms ±9.9999E2 ZMAGN Impedance Real & Imaginary ZCOMPlex Bottom = 0 Ohms ZCOMP Impedance Inductance ZINDuctance Bottom = 5 Bottom = 4 to 30 Single Rectilinear Graph 0 nH ±1E6 1.000 nH 1E-15 to 1E9 5 4 to 30 Single Rectilinear Graph 0 pF ±1E6 1.000 pF 1E-15 to 1E9 5 4 to 30 ZIND Impedance Capacitance ZCAPacitance ZCAP 2-24 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-19 2-19 Input/Output Data Files Input/Output Data Files The following is a list of file types that are supported by the VectorStar MS4640B. For more detailed definitions and applicability of each file type, refer to the UIRM, Appendix A — File Specifications. Table 2-8. Supported File Types (1 of 3) File Extension Description Command Compatibility ACD AutoCal Characterization file. :MMEMory:LOAD | :MMEMory:STORe AHC All hardware calibration file. On a per system basis, the file contains all hardware calibration data. :MMEMory:LOAD | :MMEMory:STORe AIC Analog in calibration file. Per-system. :MMEMory:LOAD | :MMEMory:STORe ALC ALC calibration file. Saves all available ALC calibration for all ports. Per-system. :MMEMory:LOAD | :MMEMory:STORe BMP Bitmap image file of data display area. :MMEMory:STORe | :MMEMory:STORe:IMAGe CCF Calibration kit coefficients file. :MMEMory:LOAD:CKIT CHA Setup and Calibration file for all channels. :MMEMory:LOAD | :MMEMory:STORe CHC Active Channel Setup and Calibration File with Calibration Kit information. :MMEMory:LOAD | :MMEMory:STORe CHX Active Channel Setup and Calibration File :MMEMory:LOAD | :MMEMory:STORe CSV Comma separated text data file. :MMEMory:STORe EDL Embedding/De-embedding array file. :MMEMory:LOAD | :MMEMory:STORe EQN Equation file FPC Flat test port power calibration file :MMEMory:LOAD | :MMEMory:LOAD:FLAT :MMEMory:STORe:FLAT{1-7} JPG JPEG image file of data display area. :MMEMory:STORe :MMEMory:STORe:IMAGe KIT_INFO. “Extension” The Anritsu Lightning Calibration kit files are supported by the VectorStar MS4640B VNA. The files are usually bundled together on a floppy disk. To use the files, transfer from the floppy disk to a USB memory device. When plugged into an MS4640B Series VNA, the USB drive is identified as drive E:\. Files can be manually loaded by navigating to drive E:\ and selecting the files. The MS4640B VNA Series VNA then loads all of files. Lightning command: LKT Alternatively, use the Lightning LKT command to load all of the calibration kit files. The Lightning calibration kit files all have a base name of “KIT_INFO.Extension” where the extension identifies the connector geometry and gender. LMT :MMEMory:STORe:LIMit | :MMEMory:LOAD:LIMit Set up for limit lines. MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-25 2-19 Input/Output Data Files Table 2-8. Supported File Types (2 of 3) File Extension Description Command Compatibility LOG A list of all entries in the VectorStar event log. :MMEMory:STORe LST List of component file names for s1p characterized calibration kits. :MMEMory:LOAD:CKIT MNP Active Channel Mixed mode parameter file MWZD 2-26 Programming the VectorStar Series VNA Mixer Wizard Setup file PPC Power sweep power calibration file. :MMEMory:LOAD:LINearity | :MMEMory:STORe:LINearity{1-2} PNG PNG image of data display area. :MMEMory:STORe | :MMEMory:STORe:IMAGe PTC Pretune calibration file. RCVR Receiver calibration file. :MMEMory:LOAD | :MMEMory:STORe S1P Data file in S1P format (see S2P below). :MMEMory:STORe S2P Data file in S2P standard microwave simulator text format. Includes a controlled header and only one or four S-parameters are saved. If an S2P file is requested, but not all of the S-parameters are currently being measured, a value of 0 (zero) is entered for missing parameters. If a full two-port calibration is applied, all of the S-parameters are measured, even if they do not need to be displayed. The resultant S2P file is complete with all S-parameter information. S2P files can be recalled and displayed as trace memory when they are loaded into the active channel. :MMEMory:STORe S3P Data file in S3P format (see S2P above). :MMEMory:STORe S4P Data file in S4P format (see S2P above). :MMEMory:STORe SGS Setup file for segmented traces. :MMEMory:LOAD:FSEGMent | :MMEMory:LOAD:ISEGMent SLC Source Local Oscillator (Src LO) calibration file. Per-system. :MMEMory:LOAD | :MMEMory:STORe SQM Source Quadrupler hardware calibration file :MMEMory:LOAD | :MMEMory:STORe STA Setup file for all channels. :MMEMory:LOAD | :MMEMory:STORe STC Setup and calibration kit information file for a single channel. :MMEMory:LOAD | :MMEMory:STORe STX Setup file for a single channel. :MMEMory:LOAD | :MMEMory:STORe TDF Active trace data memory formatted file. :MMEMory:LOAD:MDATA TDU Active trace data memory unformatted file. :MMEMory:LOAD:MDATA PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA Table 2-8. 2-19 Input/Output Data Files Supported File Types (3 of 3) File Extension Description Command Compatibility TMZ Ten (10) MHz calibration file. Per-system. :MMEMory:LOAD | :MMEMory:STORe TXT Active channel trace data text file. Similar to the .csv format described above. A tab-delimited format with an optional descriptive heading in which the data for every trace is saved to a defined location folder. The data for each trace is saved as an X and a Y column to accommodate multiple parameters such as mixed frequency and time domain. Subsequent traces are added as additional columns.The .txt file cannot be recalled into the VNA memory. :MMEMory:STORe MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-27 2-20 Status System Reporting 2-20 Programming the VectorStar Series VNA Status System Reporting The MS4640B status system consists of the following SCPI-defined status-reporting structures: • The Instrument Summary Status Byte Group • The Standard Event Status Group • The Operation Status Group • The Questionable Status Group The following paragraphs describe the registers that make up a status group and explain the status information that each status group provides. Note Parallel Polling is not supported in the MS4640B VNA. Status Group Registers In general, a status group consists of a condition register, a transition filter, an event register, and an enable register. Each component is briefly described in the following paragraphs. Condition Register The condition register is continuously updated to reflect the current status of the MS4640B. There is no latching or buffering for this register, it is updated in real time. Reading the contents of a condition register does not change its contents. Transition Filter The transition filter is a special register that specifies which types of bit state changes in the condition register will set corresponding bits in the event register. • Negative transition filters (NTR) are used to detect condition changes from True (1) to False (0). • Positive transition filters (PTR) are used to detect condition changes from False (0) to True (1). • Setting both positive and negative filters True allows an event to be reported anytime the condition changes. • Transition filters are read-write. • Transition filters are unaffected by queries or *CLS (clear status) and *RST commands. Event Register The event register latches transition events from the condition register as specified by the transition filter. Bits in the event register are latched, and once set they remain set until cleared by a query or a *CLS command Event registers are read only. Enable Register The enable register specifies the bits in the event register that can produce a summary bit. The MS4640B logically ANDs corresponding bits in the event and enable registers, and ORs all the resulting bits to obtain a summary bit. Summary bits are recorded in the Summary Status Byte. Enable registers are read-write. Querying an enable register does not affect it. Status Group Reporting The state of certain MS4640B hardware and operational events and conditions can be determined by programming the status system. Three lower status groups provide status information to the Summary Status Byte group. The Summary Status Byte group is used to determine the general nature of an event or condition and the other status groups are used to determine the specific nature of the event or condition. The following paragraphs explain the information that is provided by each status group. Programming commands for the status system, including examples of command usage, can be found in Chapter 5, “SCPI Commands”. Summary Status Byte Group 2-28 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-20 Status System Reporting The Summary Status Byte group, consisting of the Summary Status Byte Enable register and the Summary Status Byte, is used to determine the general nature of a MS4640B event or condition. The bits in the Summary Status Byte provide the following: Table 2-9. Status Byte Group Bit # Bit Name Description 0,1 Not Used These bits are always set to 0. Error Queue (ERRQ) Set to indicate the Error Queue contains data. The Error Query command can then be used to read the error message(s) from the queue. Questionable Event (QUEST) Set to indicate the Questionable Status summary bit has been set. The Questionable Status Event register can then be read to determine the specific condition that caused the bit to be set. Message Available (MAV) Set to indicate that the MS4640B has data ready in its output queue. Standard Event (STD) Set to indicate that the Standard Event Status summary bit has been set. The Standard Event Status register can then be read to determine the specific event that caused the bit to be set. Master Summary Status (MSS/RQS) Set to indicate that the MS4640B has at least one reason to require service. This bit is also called the Master Summary Status Bit (MSS). The individual bits in the Status Byte are ANDed with their corresponding Service Request Enable Register bits, then each bit value is ORed and input to this bit. Operation Event (OPER) Set to indicate that the Operation Status summary bit has been set. The Operation Status Event register can then be read to determine the specific condition that caused the bit to be set. 2 3 4 5 6 7 Standard Event Status Group The Standard Event Status group, consisting of the Standard Event Status register (an Event register) and the Standard Event Status Enable register, is used to determine the specific event that set bit 5 of the Summary Status Byte. The bits in the Standard Event Status register provide the following: Table 2-10. Standard Event Status Group Bit # 0 Bit Name Description Operation Complete (OP) Set to indicate that all pending MS4640B operations were completed following execution of the “*OPC” command. For more information, see the descriptions of the *OPC, *OPC?, and *WAI commands in Chapter 3, “IEEE Commands”. 1 Not Used The bit is always set to 0. 2 Query Error Set to indicate that a query error has occurred. 3 Device Dependent Error Set to indicate that a device-dependent error has occurred. 4 Execution Error Set to indicate that an execution error has occurred. 5 Command Error Set to indicate that a command error (usually a syntax error) has occurred. 6 Not Used This bit should be set to 0 (zero). 7 Power ON Set to indicate that the MS4640B is powered ON and in operation. Operation Status Group MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-29 2-20 Status System Reporting Programming the VectorStar Series VNA The Operation Status group, consisting of the Operation Condition register, the Operation Positive Transition register, the Operation Negative Transition register, the Operation Event register, and the Operation Event Enable register, is used to determine the specific condition that set bit 7 in the Summary Status Byte. The bits in the Operation Event register provide the following: Table 2-11. Operation Status Group Bit # 0 Bit Name Description Calibration Complete Set to indicate that a calibration is complete. Sweep Complete Set to indicate that a sweep is complete. Note that the Sweep Complete Bit will not be set unless the sweep was started by an appropriate trigger commands. 1 2-3 4 6-15 2-30 For examples of use, see the “TRS” command in the Lightning 37xxxx Command chapter in the Programming Manual Supplement. Also see “:TRIGger[:SEQuence] Subsystem” on page 5-723 in Chapter 5, “SCPI Commands”. Not Used These bits should be set to 0 (zero). Waiting for Trigger Set to indicate that the MS4640B is in an armed “wait for trigger” state. Not Used These bits should be set to 0 (zero). PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-20 Status System Reporting Questionable Status Register The Questionable Status Register consists of the Questionable Condition register, the Questionable Positive Transition register, the Questionable Negative Transition register, the Questionable Event register, and the Questionable Event Enable register. The Questionable Status Register is used to determine the specific condition that set bit 3 in the Summary Status Byte. The bits in the Questionable Event register provide the following: Table 2-12. Questionable Status Register Bit # Bit Name Description 0 New Service Log Entry Set to indicate that a new entry has been made to the Windows service log. 1 Limit Failure Set to indicate that trace data is outside a limit line boundary. 2 RF Unleveled Set to indicate that an RF unleveled condition exists. 3 Unlocked Set to indicate that an internal PLL unlocked condition exists. 4-15 Not Used These bits should be set to 0 (zero). MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-31 2-20 Status System Reporting Programming the VectorStar Series VNA Questionable Limits Status Register The Questionable Limits Status Register (QLSR) consists of the Questionable Limits Condition register, the Questionable Limits Event register, the Positive and Negative Transition Filters, and the Questionable Limits Event Enable register. The QLSR is used to determine the channels that continuous limits testing failures and set Bit B1 of the Questionable Status Register. The bits in the QLSR provide the information described in the table below. Table 2-13. Questionable Limits Status Register (QLSR) Bit # Bit Name Description 0 Channel1Fail Limits testing on Channel 1 detected a failure 1 Channel2Fail Limits testing on Channel 2 detected a failure 2 Channel3Fail Limits testing on Channel 3 detected a failure 3 Channel4Fail Limits testing on Channel 4 detected a failure 4 Channel5Fail Limits testing on Channel 5 detected a failure 5 Channel6Fail Limits testing on Channel 6 detected a failure 6 Channel7Fail Limits testing on Channel 7 detected a failure 7 Channel8Fail Limits testing on Channel 8 detected a failure 8 Channel9Fail Limits testing on Channel 9 detected a failure 9 Channel10Fail Limits testing on Channel 10 detected a failure 10 Channel11Fail Limits testing on Channel 11 detected a failure 11 Channel12Fail Limits testing on Channel 12 detected a failure 12 Channel13Fail Limits testing on Channel 13 detected a failure 13 Channel14Fail Limits testing on Channel 14 detected a failure 14 Channel15Fail Limits testing on Channel 15 detected a failure 15 Channel16Fail Limits testing on Channel 16 detected a failure 2-32 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-20 Status System Reporting Service Request Status Register Error Queue *CLS *STB? SPOLL *SRE n *SRE? Status Byte b0 b1 b2 b3 b4 b5 b6 b7 Error Code/ Error Description Not Used Not Used (not empty) Error Queue (ERRQ) Questionable Event (QUEST) Message Available (MAV) Standard Event (STD) Master Summary Status (MSS/RQS) Operation Event (OPER) Standard Event Status Register ENABle & *ESE n *ESR? *ESR? b0 b1 b2 b3 b4 b5 b6 b7 Operation Complete (OP) Not Used Query Error Device Dependent Error Execution Error Command Error Not Used Power ON EVENt b0 b1 b2 b3 b4 b5 b6 b7 & ENABle b0 b1 b2 b3 b4 b5 b6 b7 *CLS *CLS Operation Status Register Questionable Status Register :STAT:OPER:ENAB? :STAT:OPER:EVEN? :STAT:OPER:NTR :STAT:OPER:PTR :STAT:OPER:COND? CONDition PTR NTR EVENt Calibration Complete b0 b0 b0 b0 Sweep Complete b1 b1 b1 b1 Not Used b2 b2 b2 b2 Not Used b3 b3 b3 b3 Waiting for Trigger b4 b4 b4 b4 Not Used b5 b5 b5 b5 Not Used b6 b6 b6 b6 Not Used b7 b7 b7 b7 & Not Used b8 b8 b8 b8 Not Used b9 b9 b9 b9 Not Used b10 b10 b10 b10 Not Used b11 b11 b11 b11 Not Used b12 b12 b12 b12 Not Used b13 b13 b13 b13 Not Used b14 b14 b14 b14 Not Used (=0) b15 b15 b15 b15 ENABle b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 b10 b11 b12 b13 b14 b15 :STAT:QUES:ENAB? :STAT:QUES:EVEN? :STAT:QUES:NTR :STAT:QUES:PTR :STAT:QUES:COND? CONDition PTR NTR EVENt New Service Log Entry b0 b0 b0 b0 Limit Failure b1 b1 b1 b1 RF Unleveled b2 b2 b2 b2 Unlocked b3 b3 b3 b3 Not Used b4 b4 b4 b4 Not Used b5 b5 b5 b5 Not Used b6 b6 b6 b6 Not Used b7 b7 b7 b7 & Not Used b8 b8 b8 b8 Not Used b9 b9 b9 b9 Not Used b10 b10 b10 b10 Not Used b11 b11 b11 b11 Not Used b12 b12 b12 b12 Not Used b13 b13 b13 b13 Not Used b14 b14 b14 b14 Not Used (=0) b15 b15 b15 b15 ENABle b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 b10 b11 b12 b13 b14 b15 *CLS *CLS Questionable Limit Status Register Bit Weight b0 b1 b2 b3 b4 b5 b6 b7 1 2 4 8 16 32 64 128 b8 b9 b10 b11 b12 b13 b14 b15 256 512 1024 2048 4096 8192 16384 32768 Note: Not Used bits are always cleared to 0. :STAT:QUES:LIM:ENAB? :STAT:QUES:LIM:EVEN? :STAT:QUES:LIM:NTR :STAT:QUES:LIM:PTR :STAT:QUES:LIM:COND? CONDition PTR NTR EVENt CH1 Limit Fail b0 b0 b0 b0 CH2 Limit Fail b1 b1 b1 b1 CH3 Limit Fail b2 b2 b2 b2 CH4 Limit Fail b3 b3 b3 b3 CH5 Limit Fail b4 b4 b4 b4 CH6 Limit Fail b5 b5 b5 b5 CH7 Limit Fail b6 b6 b6 b6 CH8 Limit Fail b7 b7 b7 b7 & CH9 Limit Fail b8 b8 b8 b8 CH10 Limit Fail b9 b9 b9 b9 CH11 Limit Fail b10 b10 b10 b10 CH12 Limit Fail b11 b11 b11 b11 CH13 Limit Fail b12 b12 b12 b12 CH14 Limit Fail b13 b13 b13 b13 CH15 Limit Fail b14 b14 b14 b14 CH16 Limit Fail b15 b15 b15 b15 ENABle b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 b10 b11 b12 b13 b14 b15 *CLS Figure 2-3. Status Register Structure MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-33 2-21 Trigger System 2-21 Programming the VectorStar Series VNA Trigger System The MS4640B trigger system is used to synchronize analyzer actions with software trigger commands. The VNA follows the layered trigger model used in SCPI instruments. The following paragraphs describe the operation of the analyzer’s trigger system. A sample logic flowchart of the trigger model is shown in Figure 2-4. A sample timing reference of the trigger model is shown in Figure 2-5. Trigger Modes The trigger system supports four different trigger modes: • Internal Trigger Mode This is an automatic triggered point-by-point measurement that is internally controlled by the DSP software. • Manual Trigger Mode Manual mode is triggered by the user from the front panel to start a measurement based on a per point, a per sweep (or a per port), or a per channel (or all channels) trigger mode. • GPIB Trigger Mode GPIB mode is triggered by a GPIB trigger command to start a measurement based on a point-per-point, a sweep-per-sweep (or a port-per-port), or a channel-per-channel (or all channels). • External Trigger Mode • External mode is triggered through the rear panel input of the instrument to start a measurement based on a point-per-point, a sweep-per-sweep (or a port-per-port), or a channel-per-channel (or all channels) trigger mode. • The external trigger system allows the user to select a positive or negative edge trigger to start the measurement. • A trigger delay can also be applied to a measurement right after an external trigger is received by the instrument and just before the measurement begins. • The external trigger has an additional feature to handle trigger handshaking, which uses the “Ready for Trigger” and “Trigger Output” output signals through the rear panel of the instrument. • The Ready for Trigger signal is sent from the instrument to the rear panel output when the system is ready to accept an external trigger. • The Trigger Output pulse signal is sent to the rear panel when the system has completed a measurement. 2-34 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-21 Trigger System The following diagram is a flowchart of the triggering logic: Figure 2-4. Triggering Logic Flowchart MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-35 2-21 Trigger System Programming the VectorStar Series VNA Trigger Timing The timing diagram below illustrates the general measurement sequence of per-point triggering using a positive trigger edge. Trigger Delay, Ready for Trigger, and Trigger Output are only used by an external trigger. Figure 2-5. Sample Trigger Model The trigger sequence with trigger handshake turned on is as follows (Trigger Handshake enables “Ready for Trigger” and “Trigger Output”: 1. A trigger measurement is received from the State machine. 2. Ready for Trigger (rear panel BNC output) is set to low to indicate that the instrument is ready for trigger. 3. External trigger (rear panel BNC input) is received. 4. After the external trigger is received, the Ready for Trigger (rear panel BNC output) is set to high to indicate that the system is not ready for trigger and the trigger delay is added. 5. The data measurement is started. 6. At the completion of the data measurement, the Trigger Output (rear panel BNC output) is pulsed to indicate that the measurement is completed. 7. The Level Dip and/or the LLoad pulse are executed. 8. The next frequency is preloaded and the State machine is triggered. Trigger handshaking is enabled with: Note :TRIGger[:SEQuence]:EXTernal:HANDshake[:STATe] If handshaking is not in use, steps 2, 4, and 6 are deleted, but the trigger delay is still present. 2-36 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-22 2-22 Calibration Component Parameters Calibration Component Parameters The calibration component parameter values depend on the calibration kit used and the reset status of the instrument. The tables below, starting with Table 2-14, “Loads and Through-Line Values” on page 2-37 and ending with Table 2-21 on page 2-42 summarize parameters related to calibration components and list the factory default values for the various connector coefficients and lengths. These values may change if calibration kits are loaded that overwrite them. A Factory Default using the :SYStem:PRESet:ZERo command restores all connector values to those in the tables below. After the restoration, a Factory Default also performs a Default Default. A Default Default (System Default not set to USER) changes the connector type to the appropriate connector type based on the model number. The following general calibration component parameters should also be noted: • A Default Default (System Default not set to USER) will change the Microstrip Kit to 10 Mil. • A Default Default (System Default not set to USER) will change the Waveguide Kit to WR10. Loads and Through Lines The standard values for Loads and Through Lines are listed in the table below. Table 2-14. Loads and Through-Line Values Type Loads Through Lines MS464xB Series VNA PM Parameter Value Units Impedance 50 Ohms Resistance 50 Ohms Impedance 50 Ohms Length 0 Meters Loss 0 dB Frequency 0 Hz PN: 10410-00322 Rev. U 2-37 2-22 Calibration Component Parameters Programming the VectorStar Series VNA Other Connector Coefficients The default connector coefficients apply if not overwritten by the connector values loaded from a calibration kit. Table 2-15. Default Connector Coefficients (1 of 2) Type (gender) Type (gender) Type (gender) Type (gender) Type (gender) Type (gender) SMA (male) SMA (female) K (male) K (female) N (male) N (female) OpenC0 23E–15 26E–15 –1.5E–15 –1.0E–15 125.0E–15 65.0E–15 OpenC1 –550E–27 –550E–27 720E–27 650E–27 0.0E–27 0.0E–27 OpenC2 10.0E–36 10.0E–36 –23.0E–36 –23.0E–36 0.0E–36 0.0E–36 OpenC3 0.7E–45 0.5E–45 0.35E–45 0.35E–45 10.0E–45 6.0E–45 5.0E–3 5.0E–3 5.0E–3 5.0E–3 M DUT = 0.0E–3 F Test Port = 20.3E–3 M Test Port = 8.97E–3 F DUT = 0.0E–1 Value Type (gender) OpenOffsetLength ShortL0 0 0 0 0 0 0 ShortL1 0 0 0 0 0 0 ShortL2 0 0 0 0 0 0 ShortL3 0 0 0 0 0 0 ShortOffsetLength 5.0E–3 5.0E–3 5.0E–3 5.0E–3 20.37E–3 8.97E–3 GPC3.5 (male) GPC3.5 (female) GPC7 (none) V (male) V (female) TNC (male) OpenC0 24E–15 24E–15 91E–15 –1.0E–15 0.0E–15 79.0E–15 OpenC1 –425.0E–27 –250.0E–27 –220.0E–27 –275.0E–27 –200.0E–27 0.0E–27 OpenC2 10.0E–36 10.0E–36 75.0E–36 6.25E–36 5.0E–36 40.0E–36 OpenC3 0.6E–45 0.5E–45 1.3E–45 0.0E–45 0.0E–45 0.0E–45 OpenOffsetLength 5.0E–3 5.0E–3 0.0E–3 4.75E–3 4.75E–3 18.05E–3 ShortL0 0 0 0 0 0 0 ShortL1 0 0 0 0 0 0 ShortL2 0 0 0 0 0 0 ShortL3 0 0 0 0 0 0 ShortOffsetLength 5.0E–3 5.0E–3 0.0E–3 5.10E–3 5.10E–3 18.05E–3 Type (gender) 2-38 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-22 Calibration Component Parameters Table 2-15. Default Connector Coefficients (2 of 2) Type (gender) Type (gender) Type (gender) Type (gender) Type (gender) Type (gender) TNC (female) N75 (male) N75 (female) 7/16 (male) 7/16 (female) – OpenC0 79E–15 55.0E–15 23.0E–15 32.0E–15 32.0E–15 – OpenC1 0.0E–27 0.0E–27 0.0E–27 100.0E–27 100.0E–27 – OpenC2 40.0E–36 0.0E–36 0.0E–36 –50.0E–36 –50.0E–36 – OpenC3 0.0E–45 0.0E–45 0.0E–45 100.0E–45 100.0E–45 – OpenOffsetLength 25.27E–3 0.0E–3 0.0E–3 20.0E–3 20.0E–3 – ShortL0 0 0 0 0 0 – ShortL1 0 0 0 0 0 – ShortL2 0 0 0 0 0 – ShortL3 0 0 0 0 0 – ShortOffsetLength 25.27E–3 0.0E–3 0.0E–3 20.0E–3 20.0E–3 – Value Type (gender) W1 Calibration Kit A W1 Calibration Kit is slightly different because it has to cover such a wide frequency range. It has a selection of components to use in a SOLT Calibration that covers the 70 kHz to 70 GHz range. A Male and Female Open and a Male and Female Short with a set of coefficients characterize them over that range. It has a selection of components to use in an SSST Calibration which covers the 70 kHz to 70 GHz range. Three Male and Female Shorts with a set of coefficients characterize them over that range. Physically, there are only 3 shorts: ShortX, ShortY, and ShortZ. ShortX has two different sets of coefficients (the offset lengths are the same). The first set of coefficients are good over the 70 kHz to 70 GHz range and the second set of coefficients (referred to as OffsetShort) are good over the 70 GHz to 110 GHz range. Table 2-16. W1 Calibration Kit Connector Parameters (1 of 2) Geometry W1 Male W1 Female OpenC0 9.63E–15 4.43E–15 OpenC1 374.73E–27 –1.109E–27 OpenC2 –4.96E–36 14.65E–36 OpenC3 0.0154E–45 –0.1768E–45 OpenOffsetLength 1.510E–3 1.930E–3 ShortL0 0.98E–12 0.98E–12 ShortL1 2.48E–24 2.48E–24 ShortL2 –1.02E–33 –1.05E–33 ShortL3 0.0164E–42 0.0164E–42 ShortOffsetLength 2.020E–3 2.020E–3 MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-39 2-22 Calibration Component Parameters Programming the VectorStar Series VNA Table 2-16. W1 Calibration Kit Connector Parameters (2 of 2) Geometry W1 Male W1 Female OffsetShort1L0 –4.1930E–12 3.13E–12 OffsetShort1L1 1308.5E–24 –971.86E–24 OffsetShort1L2 –25.1370E–33 25.010E–33 OffsetShort1L3 0.1282E–42 –0.1464E–42 OffsetShort1OffsetLength 2.020E–3 2.020E–3 OffsetShort2L0 0.9450E–12 –2.13E–12 OffsetShort2L1 544.52E–24 1117.4E–24 OffsetShort2L2 –12.32E–33 –20.4450E–33 OffsetShort2L3 0.0724E–42 0.0968E–42 OffsetShort2OffsetLength 2.650E–3 2.650E–3 OffsetShort3L0 3.0800E–12 –0.0018E–12 OffsetShort3L1 –106.12E–24 –150.2460E–24 OffsetShort3L2 3.50E–33 3.1380E–33 OffsetShort3L3 –0.0218E–42 –0.0107E–42 OffsetShort3OffsetLength 3.180E–3 3.180E–3 Sliding Load Cutoff Frequency The general sliding load frequency parameters are: • The V, 2.4mm and W1 connector sliding load cutoff frequency is 4.0E9 Hz. • Any other connector sliding load cutoff frequency is 2.0E9 Hz. Table 2-17. Sliding Load Cutoff Frequency 2-40 Connector Sliding Load Cutoff Frequency – – V 4.0E9 Hz – – 2.4mm 4.0E9 Hz – – W1 4.0E9 Hz – – Other Connectors 2.0E9 Hz – – PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-22 Calibration Component Parameters Microstrip Kit Common Values The following microstrip kit values are set. Table 2-18. MIcrostrip Calibration Kit Common Values Parameter Value – – Microstrip Default Impedance 50 Ohms – – Microstrip Substrate Dielectric 9.96 – – Microstrip Effective Dielectric 6.69 – – Parameter 10 Mil 15 Mil 25 Mil Microstrip Thickness 0.254E–3 0.381E–3 0.635E–3 Microstrip Width 0.23876E–3 0.35814E–3 0.5969E–3 Table 2-19. Microstrip Kit Dimensions Table 2-20. Waveguide Frequencies and Lengths Parameter WR10 WR12 WR15 Cutoff Frequency 59.0143E9 48.3723E9 39.8766E9 SHORT1 Offset Length 2.537E–3 2.654E–03 2.793E–03 SHORT2 Offset Length 3.612E–3 3.963E–3 4.380E–3 SHORT3 Offset Length 0 0 0 * The WR10, WR12 and WR15 values are valid for the SSLT calibration method only. All values are zero for the SSST calibration method. MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-41 2-22 Calibration Component Parameters Programming the VectorStar Series VNA Table 2-21. SOLX, SSLT, Microstrip, and Waveguide Kit Names and Connectors Kit Name Defined Connectors User-Defined Connectors SOLX Kit 2.4 mm GPC-3.5 K-Conn N-Conn SMA TNC V-Conn W1-Conn 7/16 GPC-7 N-Conn(75) User-Defined1 User-Defined2 User-Defined3 User-Defined4 User-Defined5 User-Defined6 User-Defined7 User-Defined8 SSLT Kit W1-Conn User-Defined1 User-Defined2 User-Defined3 User-Defined4 User-Defined5 User-Defined6 User-Defined7 User-Defined8 Microstrip Kit 10-Mil-Kit 15-Mil-Kit 25-Mil-Kit User-Defined1 User-Defined2 User-Defined3 User-Defined4 User-Defined5 User-Defined6 User-Defined7 User-Defined8 Waveguide Kit WR10 WR12 WR15 User-Defined1 User-Defined2 User-Defined3 User-Defined4 User-Defined5 User-Defined6 User-Defined7 User-Defined8 2-42 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-23 2-23 Notes on Calibration Commands Notes on Calibration Commands This section provides an overview of the calibration commands and when they should be used. Setting Up a 2-Port Calibration The commands listed in this section work on the first two ports of the instrument on either 2-port or 4-port configurations. The FULL1 calibration is set up with the following calibration commands: 1. Calibration method :SENSe{1-16}:CORRection:COLLect:METHod Available calibration methods: AUTOcal | LRL | LRM | SOLR | SOLT | SSLT | SSST | BBCal 2. Calibration type :SENSe{1-16}:CORRection:COLLect:1P2PF :SENSe{1-16}:CORRection:COLLect:1P2PR :SENSe{1-16}:CORRection:COLLect:FULL1 :SENSe{1-16}:CORRection:COLLect:FULL2 :SENSe{1-16}:CORRection:COLLect:FULLB :SENSe{1-16}:CORRection:COLLect:RESP1 :SENSe{1-16}:CORRection:COLLect:RESPB :SENSe{1-16}:CORRection:COLLect:TFRB :SENSe{1-16}:CORRection:COLLect:TFRF :SENSe{1-16}:CORRection:COLLect:TFRR :SENSe{1-16}:CORRection:COLLect:TYPe? 3. Line type :SENSe{1-16}:CORRection:COLLect:LINE Available line types: COAXial | MICROstrip | NONDISpersive | WAVEguide 4. Load type :SENSe{1-16}:CORRection:COLLect:LOAD Available load types: FIXED | SLIDING :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD:SELect Available loads: LOAD1 | LOAD2 5. Calibration port :SENSe{1-16}:CORRection:COLLect:PORT Available calibration ports: PORT1 | PORT2 | PORTP12 MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-43 2-23 Notes on Calibration Commands Programming the VectorStar Series VNA Setting Up a 4-Port Calibration 4-port calibrations are more complex and are hence divided into six broad categories: • “Reflection Response Calibration” • “Full 1-Port Calibration” • “Transmission Response Calibration” • “Full 2-Port Calibration” • “Full 3-Port Calibration” • “Full 4-Port Calibration” Reflection Response Calibration Under the reflection response calibration type, one can specify up to four individual 1-port response calibrations to be performed using the following command: :SENSe{1-16}:CORRection:COLLect:PORT {1 | 2 | 3 | 4 | 12 | 13 | 14 | 23 | 24 | 34 | 123 | 124 | 134 | 234 | 1234}:RESP1 For instance, to perform a reflection response calibration on ports 2, 3, and 4, the command is: :SENS1:CORR:COLL:PORT234:RESP1 The following command is used to define the components used in the reflection calibration: :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:REFLection:COMPonent Available reflection components are: NONE | OPEN | SHORt | OFSH1 | OFSH2 | OFSH3 Full 1-Port Calibration With a full 1-port calibration type, one can specify up to four individual 1-port calibrations to be performed using the following command: :SENSe{1-16}:CORRection:COLLect:PORT {1 | 2 | 3 | 4 | 12 | 13 | 14 | 23 | 24 | 34 | 123 | 124 | 134 | 234 | 1234}:FULL1 For instance, to perform a full 1-port calibration on ports 2, 3, and 4, the command is: :SENS1:CORR:COLL:PORT234:FULL1 2-44 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-23 Notes on Calibration Commands Transmission Response Calibration Under the transmission response calibration type, one can specify up to six, 2-port combinations: 12 | 13 | 14 | 23 | 24 | 34 using three response methods that are stored in a list: TFRF: transmission frequency response, forward TFRR: transmission frequency response, reverse TFRB: transmission frequency response, both. First, clear the list using: :SENSe{1-16}:CORRection:COLLect:TFR:CLEar Next, use a combination of the following three commands: :SENSe{1-16}:CORRection:COLLect:PORT{12 | 13 | 14 | 23 | 24 | 34}:TFRB :SENSe{1-16}:CORRection:COLLect:PORT{12 | 13 | 14 | 23 | 24 | 34}:TFRF :SENSe{1-16}:CORRection:COLLect:PORT{12 | 13 | 14 | 23 | 24 | 34}:TFRR For instance, to specify a forward response calibration on port12, a reverse response calibration on port13, and both forward and reverse calibrations on port14, the commands are: :SENS1:CORR:COLL:TFR:CLE :SENS1:CORR:COLL:PORT12:TFRF :SENS1:CORR:COLL:PORT13:TFRR :SENS1:CORR:COLL:PORT14:TFRB Full 2-Port Calibration With a full 2-port calibration type, one can specify two, 2-port calibrations to be performed with six, 2-port combinations: 12 | 13 | 14 | 23 | 24 | 34 The port pairs selected must be port exclusive. For instance, if the first calibration is on port23, then the second, if specified, must be on port14. There are 3 calibration types that can be specified: FULL2 | 1P2PF | 1P2PR This is accomplished using one of the commands below for the first calibration: :SENSe{1-16}:CORRection:COLLect[:CALa]:PORT{12 | 13 | 14 | 23 | 24 | 34}:1P2PF :SENSe{1-16}:CORRection:COLLect[:CALa]:PORT{12 | 13 | 14 | 23 | 24 | 34}:1P2PR :SENSe{1-16}:CORRection:COLLect[:CALa]:PORT{12 | 13 | 14 | 23 | 24 | 34}:FULL2 And one of the following commands below for the second calibration: :SENSe{1-16}:CORRection:COLLect:CALB:1P2PF :SENSe{1-16}:CORRection:COLLect:CALB:1P2PR :SENSe{1-16}:CORRection:COLLect:CALB:FULL2 For instance, the commands below specify a full, 2-port calibration on port12 and use a one path, 2-port forward calibration as the second calibration: :SENS1:CORR:COLL:PORT12:FULL2 :SENS1:CORR:COLL:CALB:1P2PF Full 3-Port Calibration With a full 3-port calibration type, one can specify a 3-port calibration to be performed on the indicated ports with the following command: :SENSe{1-16}:CORRection:COLLect:PORT{123 | 124 | 134 | 234}:FULL3 MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-45 2-23 Notes on Calibration Commands Programming the VectorStar Series VNA In addition to selecting the ports above, two or three thru lines must be measured using the commands below: :SENSe{1-16}:CORRection:COLLect:THRu:CLEar :SENSe{1-16}:CORRection:COLLect:THRu:ADD The arguments of the above command are: THRu12 | THRu13 | THRu14 | THRu23 | THRu24 | THRu34 For example, to perform a full, 3-port calibration on ports 1, 3, and 4 with thru lines on port pairs 13, 14, and 34, send the following commands: :SENS1:CORR:COLL:PORT134:FULL3 :SENS1:CORR:COLL:THR:CLE :SENS1:CORR:COLL:THR:ADD THR13 :SENS1:CORR:COLL:THR:ADD THR14 :SENS1:CORR:COLL:THR:ADD THR34 Full 4-Port Calibration With a full 4-port calibration type, one can specify a 4-port calibration to be performed on all four ports with the following command: :SENSe{1-16}:CORRection:COLLect:FULL4 In addition, three to six thru lines must be measured using the commands below: :SENSe{1-16}:CORRection:COLLect:THRu:CLEar :SENSe{1-16}:CORRection:COLLect:THRu:ADD Available throughs are: THRu12 | THRu13 | THRu14 | THRu23 | THRu24 | THRu34 For example, to perform a full, 4-port calibration with thru lines on port pairs 12, 13, 14, and 24, send the following commands: :SENS1:CORR:COLL:FULL4 :SENS1:CORR:COLL:THR:CLE :SENS1:CORR:COLL:THR:ADD THR12 :SENS1:CORR:COLL:THR:ADD THR13 :SENS1:CORR:COLL:THR:ADD THR14 :SENS1:CORR:COLL:THR:ADD THR24 2-46 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-23 Notes on Calibration Commands Defining the Calibration Standards The following command sets the connector type: :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:CONNector The connector types are as follows (the second letter is the gender: F for female, M for male, N for no gender): Table 2-22. Connector Type Abbreviations and Descriptions Connector Type Connector Description CF2, CM2 2.4 mm Female, 2.4 mm Male CF3, CM3 3.5 mm CFK, CMK K CFN, CMN N CFS, CMS SMA CFC, CMC TNC (predefined types) CFV, CMV V CF1, CM1 W1 CF716, CM716 7/16 CFN75, CMN75 N (75 ohm) CF-2V, CM-2V Anritsu 2.4 mm Female, 2.4 mm Male CNG GPC7 genderless CFU1, CMU1 to CFU32, CMU32 User Defined 1 to User Defined 32 Use the following command to load a calibration kit file with its path and name as string data: :MMEMory:LOAD:CKIT The many calibration standard types are divided into four categories of OPEN, SHORT, LOAD, and THRU (or THROUGH) as described in the following sections. MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-47 2-23 Notes on Calibration Commands Programming the VectorStar Series VNA OPEN An OPEN standard has the following parameters that define its electrical behavior: • C0, C1, C2 and C3 are power series coefficients used to calculate capacitance as follows: C = C0 + C1*f + C2*f^2 + C3*f^3 These coefficients are often displayed in scientific notation as shown below: C0 C1 C2 C3 = = = = number number number number x x x x 10E-15 10E-27 10E-36 10E-45 If one enters a number for Cx whose magnitude is > 10E-5, then it is assumed that the number must be multiplied by the appropriate power of 10 shown above to determine the coefficient. Otherwise, the coefficient value is taken as is. • OFFSET is the offset length of the load expressed in meters The parameters of the predefined types cannot be changed. Only the parameters of the User Defined types can be changed. Note The following commands are used to change the OPEN standard parameters: :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:OPEN:C0 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:OPEN:C1 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:OPEN:C2 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:OPEN:C3 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:OPEN:LABEL :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:OPEN:OFFS :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:OPEN:SERIAL SHORT A SHORT standard has the following parameters that define its electrical behavior: L0, L1, L2 and L3 are power series coefficients used to calculate inductance as follows: L = L0 + L1*f + L2*f^2 + L3*f^3 These coefficients are often displayed in scientific notation as shown below: L0 L1 L2 L3 = = = = number number number number x x x x 10E-12 10E-24 10E-33 10E-42 If one enters a number for Lx whose magnitude is > 10E-5, then it is assumed that the number must be multiplied by the appropriate power of 10 shown above to determine the coefficient. Otherwise, the coefficient value is taken as is. • OFFSET is the offset length of the load expressed in meters There are actually four SHORTS that one may encounter; however, one may be working with more than one at a time so numerics are used to differentiate them as follows: SHORT SHORT1 SHORT2 SHORT3 2-48 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-23 Notes on Calibration Commands The following commands are used to change the SHORT standard parameters: :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT:L0 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT:L1 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT:L2 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT:L3 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT:LABEL :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT:OFFS :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT:SERIAL :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT1:L0 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT1:L1 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT1:L2 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT1:L3 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT1:LABEL :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT1:OFFS :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT1:SERIAL :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT2:L0 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT2:L1 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT2:L2 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT2:L3 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT2:LABEL :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT2:OFFS :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT2:SERIAL :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT3:L0 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT3:L1 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT3:L2 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT3:L3 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT3:LABEL :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT3:OFFS :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT3:SERIAL MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-49 2-23 Notes on Calibration Commands Programming the VectorStar Series VNA LOAD A LOAD standard has the following parameters that define its electrical behavior: • C0 is a capacitance term • LO, L1, L2, L3 are power series coefficients used to calculate inductance as follows: L = L0 + L1*f + L2*f^2 + L3*f^3 • R is the resistance of the load • Z0 is the characteristic impedance • OFFSET is the offset length of the load expressed in meters Most calibration kits have two loads; therefore, they are differentiated by naming them LOAD1 and LOAD2. Use the following commands to modify the LOAD parameters: :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD1:C0 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD1:L0 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD1:L1 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD1:L2 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD1:L3 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD1:OFFS :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD1:R :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD1:Z0 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD1:LABEL :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD1:SERIAL :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD2:C0 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD2:L0 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD2:L1 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD2:L2 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD2:L3 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD2:OFFS :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD2:R :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD2:Z0 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD2:LABEL :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD2:SERIAL 2-50 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-23 Notes on Calibration Commands THRU (or THROUGH) A THRU (technically a “through”) standard has the following parameters that define its electrical behavior: • LENGTH is the length of the line • LOSS is the loss of the line • FREQUENCY is the frequency at which the loss was measured • Z0 is the Characteristic impedance • USERECIPROCAL is not actually an electrical parameter. It is merely a flag to notify the calibrator that it should use a reciprocal type of calculation. Use the following commands to modify the THRU parameters: :SENSe{1-16}:CORRection:COLLect:PORT{12 | 13 | 14 | 23 | 24 | 34}:THRU:FREQuency :SENSe{1-16}:CORRection:COLLect:PORT{12 | 13 | 14 | 23 | 24 | 34}:THRU:LENGth :SENSe{1-16}:CORRection:COLLect:PORT{12 | 13 | 14 | 23 | 24 | 34}:THRU:LOSS :SENSe{1-16}:CORRection:COLLect:PORT{12 | 13 | 14 | 23 | 24 | 34}:THRU:Z0 :SENSe{1-16}:CORRection:COLLect:PORT{12 | 13 | 14 | 23 | 24 | 34}:THRU:RECIProcal :SENSe{1-16}:CORRection:COLLect:PORT{12 | 13 | 14 | 23 | 24 | 34}:THRU:LABEL :SENSe{1-16}:CORRection:COLLect:PORT{12 | 13 | 14 | 23 | 24 | 34}:THRU:SERIAL Performing the Calibration Once all of the calibration setup parameters described above have been complete, the actual measurements for the calibration type and methods can be performed. Each calibration type and method requires measuring the appropriate standards using the commands listed below: :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:LOAD :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:OPEN :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT1 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT2 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SHORT3 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SLOAD1 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SLOAD2 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SLOAD3 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SLOAD4 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SLOAD5 :SENSe{1-16}:CORRection:COLLect:PORT{1-4}:SLOAD6 2- and 4-Port Isolation and Thru: :SENSe{1-16}:CORRection:COLLect:PORT{12 | 13 | 14 | 23 | 24 | 34}:ISOL :SENSe{1-16}:CORRection:COLLect:PORT{12 | 13 | 14 | 23 | 24 | 34}:THRU 2- and 4-Port Thru Update: :SENSe{1-16}:CORRection:COLLect:PORT{12 | 13 | 14 | 23 | 24 | 34}:THRu:UPDate MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-51 2-23 Notes on Calibration Commands Programming the VectorStar Series VNA Once the measurements are complete, the correction coefficients must be calculated and the calibration corrections must be applied (turned on): :SENSe{1-16}:CORRection:COLLect:SAVE :SENSe{1-16}:CORRection:ISOLation:STATe :SENSe{1-16}:CORRection:STATe To simulate a calibration, use one of the commands below to specify the calibration type: :SENSe{1-16}:CORRection:COEFFicient:1P2PF :SENSe{1-16}:CORRection:COEFFicient:1P2PR :SENSe{1-16}:CORRection:COEFFicient:FULL1 :SENSe{1-16}:CORRection:COEFFicient:FULL2 :SENSe{1-16}:CORRection:COEFFicient:FULLB :SENSe{1-16}:CORRection:COEFFicient:RESP1 :SENSe{1-16}:CORRection:COEFFicient:RESPB :SENSe{1-16}:CORRection:COEFFicient:TFRB :SENSe{1-16}:CORRection:COEFFicient:TFRF :SENSe{1-16}:CORRection:COEFFicient:TFRR The commands below are for simulations with a 4-port test set attached to the VNA: :SENSe{1-16}:CORRection:COEFficient:PORT{1-4}:1P2PF :SENSe{1-16}:CORRection:COEFficient:PORT{12 | 13 | 14 | 23 | 24 | 34}:1P2PR :SENSe{1-16}:CORRection:COEFficient:PORT{1-4}:FULL1 :SENSe{1-16}:CORRection:COEFficient:PORT{12 | 13 | 14 | 23 | 24 | 34}:FULL2 :SENSe{1-16}:CORRection:COEFficient:PORT{12 | 13 | 14 | 23 | 24 | 34}:FULLB :SENSe{1-16}:CORRection:COEFficient:PORT{1-4}:RESP1 :SENSe{1-16}:CORRection:COEFficient:PORT{12 | 13 | 14 | 23 | 24 | 34}:RESPB :SENSe{1-16}:CORRection:COEFficient:PORT{12 | 13 | 14 | 23 | 24 | 34}:TFRB :SENSe{1-16}:CORRection:COEFficient:PORT{12 | 13 | 14 | 23 | 24 | 34}:TFRF :SENSe{1-16}:CORRection:COEFficient:PORT{12 | 13 | 14 | 23 | 24 | 34}:TFRR :SENSe{1-16}:CORRection:COEFficient:PORT{PORT,123 | 124 | 134 | 234}:FULL3 :SENSe{1-16}:CORRection:COEFficient:FULL4 The following command inputs and outputs the specified correction coefficients: :SENSe{1-16}:CORRection:COEFficient The correction coefficients must be specified using one of the character data arguments below: • 2-Port: ED1 | EP1S | ET11 | ET21 | EP2L | EX21 | ED2 | EP2S | ET22 | ET12 | EP1L | EX12 • 4-Port only: ED3 | ET31 | ET32 | ET13 | ET23 | ET33 | EP3L | EP3S | EX31 | EX32 | EX13 | EX23 | ED4 | ET14 | ET41 | ET24 | ET42 | ET34 | ET43 | ET44 | EP4L | EP4S | EX14 | EX24 | EX34 | EX41 | EX42 | EX43 2-52 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-23 Notes on Calibration Commands AutoCal The AutoCal calibration method (calibration using a compatible Precision Automatic Calibrator module) must first be specified using the command below: :SENSe{1-16}:CORRection:COLLect AUTO Then the calibration type is selected using the commands described above in “Setting Up a 2-Port Calibration” on page 2-43 or “Setting Up a 4-Port Calibration” on page 2-44. Without a 4-port test set, the calibration types supported are FULL1 and FULL2. With a 4-port test set, the calibration types supported are FULL1, FULL2, and FULL4. Note Multiple calibrations are not supported with AutoCal. With the exception of the FULL4 calibration, use the commands described above to set the desired calibration type. For a FULL4 calibration, use the calibration type command: :SENSe{1-16}:CORRection:COLLect:ECAL:PORT{12 | 13 | 14 | 23 | 24 | 34}:FULL4 The FULL4 calibration is achieved by performing two FULL2 calibrations on independent port pairs. One to four thru lines must also be measured using the commands listed above in “Full 3-Port Calibration” on page 2-45. The following command sets the autocal box orientation manually: :SENSe{1-16}:CORRection:COLLect:ECAL:ORIentation This command inputs a list of up to four comma-separated items: L1 | L2 | L3 | L4 | R1 | R2 | R3 | R4 | L1R2 | L1R3 | L1R4 | L2R3 | L2R4 | L3R4 | R1L2 | R1L3 | R1L4 | R2L3 | R2L4 | R3L4 | R2L1 | R3L1 | R4L1 | R3L2 | R4L2 | R4L3 | L2R1 | L3R1 | L4R1 | L3R2 | L4R2 | L4R3 The following command specifies substituting a true thru line instead of using the thru provided in the autocal box. :SENSe{1-16}:CORRection:COLLect:ECAL:TRUEthru The command’s input argument list consists of comma separated data with alternating port selections and on/off flags. For instance, if AutoCals are being performed on Ports 1 and 3 and Ports 2 and 4 with true thrus on the Ports 2 and 4 calibration, then the command is: :SENS1:CORR:COLL:ECAL:TRUE PORT13,OFF,PORT24,ON Automatic detection of the Autocal module orientation is available with the following command only with 2-port configurations, but is not offered when a 4-port test set is connected: :SENSe{1-16}:CORRection:COLLect:ECAL:AUTOmatic:ORIentation[:STATe] Once the AutoCal setup is complete, the following command starts the calibration: :SENSe{1-16}:CORRection:COLLect:ECAL:BEGin? The AutoCal calibration may require interaction with a user to perform some mechanical setup steps such as reversing the autocal box, connecting the autocal box to different port(s), or connecting external thru lines. As each step is completed, send the following command to instruct the VNA to continue with the measurements: :SENSe{1-16}:CORRection:COLLect:ECAL:CONTinue? MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-53 2-23 Notes on Calibration Commands Programming the VectorStar Series VNA The following command outputs a copy of the Autocal messages list: :SENSe{1-16}:CORRection:COLLect:ECAL:MSGS:LIST? This command outputs a list of up to four comma-separated items from the following list: 0 - AssurancePassed 19 - CharacBad 1 - Update 20 - DisplayMessage 2 - TrueThru 21 - ConnectToPort1 3 - Adapter 22 - ConnectToPort2 4 - NoModule 23 - ConnectToPort3 5 - NoOrient 24 - ConnectToPort4 6 - NoFile 25 - ConnectToPorts12 7 - NoMatch 26 - ConnectToPorts13 8 - No12T 27 - ConnectToPorts14 9 - NotAllowed 28 - ConnectToPorts23 10 - OutOfRange 29 - ConnectToPorts24 11 - AssuranceFailed 30 - ConnectToPorts34 12 - Aborted 31 - ConnectThrubwPorts12 13 - AbortOK 32 - ConnectThrubwPorts13 14 - AbortNotOK 33 - ConnectThrubwPorts14 15 - ACError 34 - ConnectThrubwPorts23 16 - ACFatalError 35 - ConnectThrubwPorts24 17 - DoneCalculateCoeff 36 - ConnectThrubwPorts34 18 - ACConnectCalB 37 - SequentialBegins 2-54 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-23 Notes on Calibration Commands The following is a list of AutoCal return codes: Table 2-23. AutoCal Module Return Code Definitions (1 of 2) Return Code Code Description 0 Assurance: Assurance passed for AutoCal Modules that have an assurance step. AutoCal complete for AutoCal Modules that have no assurance step. 1 Update: AutoCal complete for AutoCal Modules that have no assurance step. 2 True Thru: Connect through line. 3 Adapter: Reverse AutoCal module connection for Adapter Removal 4 NoModule: AutoCal module not found. 5 NoOrient: AutoCal module orientation not detected. 6 NoFile: AutoCal Characterization file not found. 7 NoMatch: AutoCal Characterization file and module mismatch. Check AutoCal serial number match to AutoCal Characterization file name. 8 No12T: Characterization function needs Full 2-Port (12-Term) calibration. Full 2-Port calibration not found. 9 NotAllowed: AutoCal automatic orientation not available on Lightning modules. Orientation must be manually specified. 10 OutOfRange: Frequencies are out of AutoCal module range. 11 AssuranceFailed: Assurance failed for AutoCal modules that have an assurance step. Not applicable for AutoCal Modules that do not have an assurance step 12 Aborted: AutoCal calibration or Characterization aborted, typically by user. 13 AbortOK: Abort operation concluded successfully. 14 AbortNotOK: Abort operation not concluded successfully. 15 ACError: AutoCal unspecified error. 16 ACFatalError: AutoCal unspecified fatal error. 17 DoneCalculateCoeff: AutoCal module has completed calculating required coefficients. 18 ACConnectCalB 19 CharacBad: Characterization is bad. 20 DisplayMessage 21 ConnectToPort1: Connect AutoCal module to Port 1. 22 ConnectToPort2: Connect AutoCal module to Port 2. 23 ConnectToPort3: Connect AutoCal module to Port 3. Requires 4-port VNA. 24 ConnectToPort4: Connect AutoCal module to Port 4. Requires 4-port VNA. 25 ConnectToPorts12: Connect AutoCal module to Ports 1 and 2. 26 ConnectToPorts13: Connect AutoCal module to Ports 1 and 3. Requires a 4-port VNA. 27 ConnectToPorts14: Connect AutoCal module to Ports 1 and 4. Requires a 4-port VNA. 28 ConnectToPorts23: Connect AutoCal module to Ports 2 and 3. Requires a 4-port VNA. 29 ConnectToPorts24: Connect AutoCal box to Ports 2 and 4. Requires a 4-port VNA. 30 ConnectToPorts34: Connect AutoCal module to Ports 3 and 4. Requires a 4-port VNA. 31 ConnectThrubwPorts12: Connect Thru line to Ports 1 and 2. 32 ConnectThrubwPorts13: Connect Thru line to Ports 1 and 3. Requires a 4-port VNA. 33 ConnectThrubwPorts14: Connect Thru line to Ports 1 and 4. Requires a 4-port VNA. MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-55 2-23 Notes on Calibration Commands Programming the VectorStar Series VNA Table 2-23. AutoCal Module Return Code Definitions (2 of 2) Return Code Code Description 34 ConnectThrubwPorts23: Connect Thru line to Ports 2 and 3. Requires a 4-port VNA. 35 ConnectThrubwPorts24: Connect Thru line to Ports 2 and 4. Requires a 4-port VNA. 36 ConnectThrubwPorts34: Connect Thru line to Ports 3 and 4. Requires a 4-port VNA. All VectorStar AutoCal modules support an assurance step. Some Lightning AutoCal modules do not support an assurance step. 2-56 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-23 Notes on Calibration Commands LRL Calibration The LRL calibration method must first be specified using the command below: :SENSe{1-16}:CORRection:COLLect LRL FULL3 LRL Calibration The FULL3 LRL calibration is accomplished by performing two, FULL2 calibrations having a common port. The following command sets the calibration type to a full 3-port LRL calibration for the indicated channel: :SENSe{1-16}:CORRection:COLLect:LRL:PORT{13 | 14 | 23 | 24}:FULL3 The port selection for the CALA calibration is limited to the ports shown below. The command’s argument must complement that of the port selection for the CALB calibration. The port selections available for the CALB calibration are limited based on the port selection made in the CALA calibration as follows: CALA Port Selection Caution CALB Port Choices PORT13 or PORT24 <--------> PORT14 or PORT23 PORT14 or PORT23 <--------> PORT13 or PORT24 If the rules above for the CALB calibration port pair is violated, the FULL3 command will fail. FULL4 LRL Calibration The FULL4 LRL calibration is accomplished by performing two, FULL2 calibrations on independent port pairs. The following command sets the calibration type to a full 4-port LRL calibration for the indicated channel: :SENSe{1-16}:CORRection:COLLect:LRL:PORT{12 | 13 | 14 | 23 | 24 | 34}:FULL4 In addition, one to four thru lines must be measured using the commands listed below: :SENSe{1-16}:CORRection:COLLect:THRu:CLEar :SENSe{1-16}:CORRection:COLLect:THRu:ADD Available throughs are: THRu12 | THRu13 | THRu14 | THRu23 | THRu24 | THRu34 MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-57 2-23 Notes on Calibration Commands Programming the VectorStar Series VNA Setting Up the Device Parameters The following commands are then used to set up the device parameters: The following three commands provide backward compatibility with legacy VectorStar software and are used to set up the frequency, line length, and loss values: :SENSe{1-16}:CORRection:COLLect:LRL:DEVice{1-10}:PORT12:LINE:FREQuency :SENSe{1-16}:CORRection:COLLect:LRL:DEVice{1-10}:PORT12:LINE:LENGth :SENSe{1-16}:CORRection:COLLect:LRL:DEVice{1-10}:PORT12:LINE:LOSS The following three commands provide support for newer VectorStar software and are used to set up the frequency, line length, and loss values: :SENSe{1-16}:CORRection:COLLect:LRL[:CALa]:DEVice{1-10}:LINE:FREQuency :SENSe{1-16}:CORRection:COLLect:LRL[:CALa]:DEVice{1-10}:LINE:LENGth :SENSe{1-16}:CORRection:COLLect:LRL[:CALa]:DEVice{1-10}:LINE:LOSS The following commands provide support for newer VectorStar software and for the 4-port test set. Omitting the optional [:CALa] keyword in these commands provide support for legacy 2-port instruments: :SENSe{1-16}:CORRection:COLLect:LRL[:CALa]:BAND1:REFLection:TYPe :SENSe{1-16}:CORRection:COLLect:LRL[:CALa]:BAND2:REFLection:TYPe :SENSe{1-16}:CORRection:COLLect:LRL[:CALa]:BANDs:COUNt :SENSe{1-16}:CORRection:COLLect:LRL[:CALa]:DEVice{1-10}:PORT{1-4}:MATCH:C0 :SENSe{1-16}:CORRection:COLLect:LRL[:CALa]:DEVice{1-10}:PORT{1-4}:MATCH:L0 :SENSe{1-16}:CORRection:COLLect:LRL[:CALa]:DEVice{1-10}:PORT{1-4}:MATCH:OFFS :SENSe{1-16}:CORRection:COLLect:LRL[:CALa]:DEVice{1-10}:PORT{1-4}:MATCH:R :SENSe{1-16}:CORRection:COLLect:LRL[:CALa]:DEVice{1-10}:PORT{1-4}:MATCH:Z0 :SENSe{1-16}:CORRection:COLLect:LRL[:CALa]:DEVice{1-10}:TYPe :SENSe{1-16}:CORRection:COLLect:LRL[:CALa]:FREQuency:BREakpoint :SENSe{1-16}:CORRection:COLLect:LRL[:CALa]:OPEN:OFFS :SENSe{1-16}:CORRection:COLLect:LRL[:CALa]:REFPlane :SENSe{1-16}:CORRection:COLLect:LRL[:CALa]:SHORT:OFFS 2-58 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-23 Notes on Calibration Commands The following commands are used for the corresponding CALB parameters: :SENSe{1-16}:CORRection:COLLect:LRL:CALB{1-5}:REFLection:TYPe :SENSe{1-16}:CORRection:COLLect:LRL:CALB:BANDs:COUNt :SENSe{1-16}:CORRection:COLLect:LRL:CALB:DEVice{1-10}:LINE:FREQuency :SENSe{1-16}:CORRection:COLLect:LRL:CALB:DEVice{1-10}:LINE:LENGth :SENSe{1-16}:CORRection:COLLect:LRL:CALB:DEVice{1-10}:LINE:LOSS :SENSe{1-16}:CORRection:COLLect:LRL:CALB:DEVice{1-10}:PORT{1-4}:MATCH:C0 :SENSe{1-16}:CORRection:COLLect:LRL:CALB:DEVice{1-10}:PORT{1-4}:MATCH:L0 :SENSe{1-16}:CORRection:COLLect:LRL:CALB:DEVice{1-10}:PORT{1-4}:MATCH:OFFS :SENSe{1-16}:CORRection:COLLect:LRL:CALB:DEVice{1-10}:PORT{1-4}:MATCH:R :SENSe{1-16}:CORRection:COLLect:LRL:CALB:DEVice{1-10}:PORT{1-4}:MATCH:Z0 :SENSe{1-16}:CORRection:COLLect:LRL:CALB:DEVice{1-10}:TYPe :SENSe{1-16}:CORRection:COLLect:LRL:CALB:FREQuency:BREakpoint :SENSe{1-16}:CORRection:COLLect:LRL:CALB:OPEN:OFFS :SENSe{1-16}:CORRection:COLLect:LRL:CALB:REFPlane :SENSe{1-16}:CORRection:COLLect:LRL:CALB:SHORT:OFFS The following command defines which match corresponds to which port: :SENSe{1-16}:CORRection:COLLect:LRL:DEVice{1-10}:MATCH:PORT The following commands collect LRL calibration data: :SENSe{1-16}:CORRection:COLLect:LRL:DEVice{1-10}:PORT{1-4}:MATCH :SENSe{1-16}:CORRection:COLLect:LRL:DEVice{1-10}:PORT{12 | 13 | 14 | 23 | 24 | 34}:LINE MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-59 2-24 Command Script Example – Limit Lines 2-24 Programming the VectorStar Series VNA Command Script Example – Limit Lines This script example provides the basic procedure for establishing upper and lower limit lines for a trace. Limit Lines for Single Rectilinar Trace Display The requirements for this limit line example are shown in the figure below where one lower limit has been established with three upper limits. Tr1 S12 Trans LogM Reflvl: 4 dB Res 2 dB/Div 14 12 Limit Segment 3 10 5 Limit Segment 4 8 6 4 Limit Segment 2 6 4 2 7 2 0 3 Limit Segment 1 -2 -4 -6 1 1.0 GHz 10.0 GHz 15.0 GHz 20.0 GHz 1. Representative trace display for frequency from 1 GHz to 20 GHz, and levels from –6 to +14 dB. 4. Limit Segment 2 – An upper limit line from 1 GHz at 4 dB to 10 GHz at 10 dB. 2. Log Magnitude trace display measuring S12, with: • Resolution set at 2 dB per division. • Reference value set at 2 dB. • Reference position set at 5. 5. Limit Segment 3 – An upper limit line from 10 GHz at 10 dB to 15 GHz at 10 dB. 3. Limit Segment 1 – A lower limit line from 1 GHz at –2 dB to 20 GHz at 0 dB. 7. Typical signal trace for this DUT. Figure 2-6. 2-60 6. Limit Segment 4 – An upper limit line from 15 GHz at 10 dB to 20 GHz at 0 dB. Limit Line Concept and Example PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-24 Command Script Example – Limit Lines Required Equipment • VectorStar MS4644B VNA, K Connectors, 10 MHz to 40 GHz • Anritsu 36585K-2MF Precision Automatic Calibrator (AutoCal) Module Calibration Kit, K (male) to K (female) Prerequisites • The VNA has warmed up for at least 90 minutes. • The AutoCal Module characterization file has been installed on the VNA. DUT Requirements The DUT measurements require the following parameters: • S-Parameter Required: S12 • Frequency Range: 1 GHz to 20 GHz • Segment 1: Lower Limit, -2 dB at 1 GHz to 0 dB at 20 GHz • Segment 2: First Upper Limit, 4 dB at 1 GHz to 10 dB at 10 GHz • Segment 3: Second Upper Limit, 10 dB at 10 GHz to 10 dB at 15 GHz • Segment 4: Third Upper Limit, 10 dB at 15 GHz to 4 dB at 20 GHz Channel and Trace Display Requirements The following VNA setup parameters are required: • Channels: 1 • Traces: 1 • Trace Display Type: Log Magnitude • Trace Scale Resolution: 2 dB/Division • Trace Scale Reference Value: 4 dB • Trace Scale Reference Position: 5 (Positions the reference value above at the fifth gridline from the display counting from the display bottom. MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-61 2-24 Command Script Example – Limit Lines Programming the VectorStar Series VNA VNA General Setup and Configuration Throughout the script examples, long form commands are used for clarity. The command explanation follows the command. In this section, the VNA is cleared and per-instrument settings established. Optional commands or queries are noted and are presented for clarity. :SYSTem:ERRor:CLEar Clears the system error queue. :SYSTem:POINt:MAXimum 25000 Set number of measurement points to 25,000 points. The instrument will reboot if the instrument was in 100,000 point mode. If already in 25,000 point mode, no instrument change and no reboot. :DISPlay:COLor:RESet Resets all colors to normal factory default value. This returns the channel, channel background, trace, limit line, and graticule colors to their default values. :DISPlay:COUNt 1 Sets one (1) channel. • When in 25,000 point mode, this can be set to 1 (one), 2, 3, 4, 6, 8, 9, 10, 12, or 16 channels. • If the channel display is set to a non-listed number (5, 7, 11, 13, 14, 15), the instrument is set to the next higher channel number. :CALCulate1:PARameter:COUNt 1 The command sets the number of traces as 1 on Channel 1. :DISPlay:SPLit R1C1 Sets the channel display layout in a Row-by-Column format where channel window display is set to one channel on one row and one column. This is the same as maxmizing a multi-channel display. :DISPlay:WINDow1:ACTivate 1 The command sets the active channel to the indicated channel number. :DISPlay:SIZe MAXimum Sets the maximum size of the graphic display. Not really needed here for a one channel display, but shown for a multi-channel and/or multi-trace display. :CALCulate1:PARameter1:DEFine S12 The command sets the measurement parameter as S12 for Trace 1. :CALCulate1:PARameter1:FORMat MLOGarithmic The command selects the display format as Log Magnitude (MLOGarithmic) for Trace 1 on Channel 1. 2-62 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-24 Command Script Example – Limit Lines Frequency and Sweep Settings In this section, the required frequency and sweep settings are established. :SENSe1:FREQuency:STARt 1.0E9 Sets start frequency to 1 GHz. :SENSe1:FREQuency:STOP 20.0E9 Sets the stop frequency to 20 GHz. :SENSe1:FREQuency:SPAN? Optional query. Span is automatically calculated as Stop Frequency minus Start Frequency. The query returns the resulting span in Hertz. 19.0E9 Frequency span is 19 GHz. :SENSe1:FREQuency:CENTer? Optional query. Center frequency is automatically calculated using Stop Frequency and Start Frequency as: Fc = ((Fstop - Fstart)/2) + Fstart 10.5E9 Center frequency is 10.5 GHz :SENSe1:SWEep:TYPe LINear The command sets the sweep for Channel 1 as Frequency-Based Linear. :SENSe1:SWEep:POINt 401 Sets the number of measurement points for Channel 1 to 401 points. • The minimum number of points is 2. • The maximum number of points is limited to the total point instrument mode as 25,000 or 100,000. Limit Lines Setup There are several ways to programmatically add limit lines to a trace display. The technique below uses the :CALCulate{1-16}:SELected:LIMit command subsystem in the following general procedure: 1. Create an empty limit line segment by using the :ADD command to create a blank limit. • Note that each :ADD command must be followed by the :TYPE and :X1, :X2, :Y1, and :Y2 commands. • The first :ADD command creates a limit line that uses the entire frequency range of the instrument. • If the :TYPE and :X1, :X2, :Y1, and :Y2 values are not changed, no further limit line segments can be added. 2. Use the :TYPE command to define the segment as a lower or upper limit. 3. Use the :X1 and :X2 commands to configure the horizontal X-Axis start and stop points for each limit segment. In this example, the start and stop values are frequency in GHz. 4. Use the :Y1 and :Y2 commands to configure the vertical Y-Axis start and stop points for each limit segment. In this example, the start and stop values are in dB. 5. The :TYPE and :X1, :X2, :Y1, and :Y2 commands can be issued in any sequence for the segment being defined. MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-63 2-24 Command Script Example – Limit Lines Programming the VectorStar Series VNA Clear Previous Limit Lines Best practices recommend clearing all previous segments. :CALCulate1:SELected:LIMit:SEGMent:CLEar The command clears all the limit segment definitions on the active trace of the indicated channel. Create and Configure Limit Line Segment 1 In this section, the first limit line is added, and then configured as to limit line type, start and stop frequencies, and start and stop Y-axis parameters. :CALCulate1:SELected:LIMit:SEGMent:ADD On Channel 1, the command adds a limit line segment. This limit line segment will be identified as Segment 1 and set as the lower limit line across the entire frequency range of interest. :CALCulate1:SELected:LIMit:SEGMent1:TYPe LOWer Sets the Channel 1 Segment 1 limit line type as a lower limit line. :CALCulate1:SELected:LIMit:SEGMent1:X1 1.0E9 Sets the Channel 1 Segment 1 lower limit line start frequency value at 1 GHz. :CALCulate1:SELected:LIMit:SEGMent1:X2 20.0E9 Sets the Channel 1 Segment 1 lower limit line stop frequency value at 20 GHz. :CALCulate1:SELected:LIMit:SEGMent1:Y1 -2.0 Sets the Channel 1 Segment 1 lower limit start Y1 value at –2.0 dB. :CALCulate1:SELected:LIMit:SEGMent1:Y2 0.0 Sets the Channel 1 Segment 1 lower limit stop Y2 value at 0.0 dB. Create and Configure Limit Line Segment 2 In this section, the second limit line is added, and then configured as to limit line type, start and stop frequencies, and start and stop Y-axis parameters. :CALCulate1:SELected:LIMit:SEGMent:ADD On Channel 1, command adds a blank limit line segment. This limit line segment will be later identified as Segment 2 and set as the first upper limit line segment. :CALCulate1:SELected:LIMit:SEGMent2:TYPe UPPer Sets the Channel 1 Segment 2 limit line type as an upper limit line. :CALCulate1:SELected:LIMit:SEGMent2:X1 1.0E9 Sets the Channel 1 Segment 2 upper limit start frequency value at 1 GHz. :CALCulate1:SELected:LIMit:SEGMent2:X2 10.0E9 Sets the Channel 1 Segment 2 upper limit line stop frequency value at 10 GHz. :CALCulate1:SELected:LIMit:SEGMent2:Y1 4.0 Sets the Channel 1 Segment 2 upper limit start Y1 value at 4.0 dB. :CALCulate1:SELected:LIMit:SEGMent2:Y2 10.0 Sets the Channel 1 Segment 2 upper limit stop Y2 value at 10.0 dB. 2-64 PN: 10410-00322 Rev. U MS464xB Series VNA PM Programming the VectorStar Series VNA 2-24 Command Script Example – Limit Lines Create and Configure Limit Line Segment 3 In this section, the third limit line is added, and then configured as to limit line type, start and stop frequencies, and start and stop Y-axis parameters. :CALCulate1:SELected:LIMit:SEGMent:ADD On Channel 1, the command adds a blank limit line segment. This limit line segment will be later identified as Segment 3 and set as the second upper limit line segment. :CALCulate1:SELected:LIMit:SEGMent3:TYPe UPPer Sets the Channel 1 Segment 3 limit line type as an upper limit line. :CALCulate1:SELected:LIMit:SEGMent3:X1 10.0E9 Sets the Channel 1 Segment 3 upper limit start frequency value at 10 GHz. :CALCulate1:SELected:LIMit:SEGMent3:X2 15.0E9 Sets the Channel 1 Segment 3 upper limit line stop frequency value at 15 GHz. :CALCulate1:SELected:LIMit:SEGMent3:Y1 10.0 Sets the Channel 1 Segment 3 upper limit start Y1 value at 10.0 dB. :CALCulate1:SELected:LIMit:SEGMent3:Y2 10.0 Sets the Channel 1 Segment 3 upper limit stop Y2 value at 10.0 dB. Create and Configure Limit Line Segment 4 In this section, the third limit line is added, and then configured as to limit line type, start and stop frequencies, and start and stop Y-axis parameters. :CALCulate1:SELected:LIMit:SEGMent:ADD On Channel 1, command adds a blank limit line segment. This limit line segment will be later identified as Segment 4 and set as the third and final upper limit line segment. :CALCulate1:SELected:LIMit:SEGMent4:TYPe UPPer Sets the Channel 1 Segment 4 limit line type as an upper limit line. :CALCulate1:SELected:LIMit:SEGMent4:X1 15.0E9 Sets the Channel 1 Segment 4 upper limit start frequency value as 15 GHz. :CALCulate1:SELected:LIMit:SEGMent4:X2 20.0E9 Sets the Channel 1 Segment 4 upper limit line stop frequency value at 20 GHz. :CALCulate1:SELected:LIMit:SEGMent4:Y1 10.0 Sets the Channel 1 Segment 4 upper limit start Y1 value at 10.0 dB. :CALCulate1:SELected:LIMit:SEGMent4:Y2 4.0 Sets the Channel 1 Segment 4 upper limit stop Y2 value at 4.0 dB. MS464xB Series VNA PM PN: 10410-00322 Rev. U 2-65 2-24 Command Script Example – Limit Lines Programming the VectorStar Series VNA Configure AutoCal Calibration For this example, the Anritsu 36585K Precision Automatic Calibrator (AutoCal) Calibration Module will be used to perform the calibration. If the characterization file for the AutoCal module has not been loaded, best practices recommand using the User Interface menus to load the characterization file. :SENSe1:CORRection:COLLect:ECAL:AUTOmatic:ORIentation:STATe OFF Turn the AutoCal module automatic orientation detection off for Channel 1. :SENSe1:CORRection:COLLect:ECAL:ORIentation L1R2 Set the AutoCal module orientation detection off and sets the port-to-port orientation manually for Channel 1 so that Port 1 is on the leftt and Port 2 is on the right. :SENSe1:CORRection:COLLect:ECAL:TRUEthru OFF The command turns off the use of the AutoCal True Thru feature, where a cable through is used during the AutoCal calibration for Channel 1. By setting this to OFF, the AutoCal module will use its Internal Thru capability to complete the calibration. Ready for Measurements The VNA is ready for measurements. 2-66 PN: 10410-00322 Rev. U MS464xB Series VNA PM Chapter 3 — IEEE Commands 3-1 Introduction This chapter contains all of the IEEE commands that are implemented in the instrument. Note When operating the VectorStar VNA through remote programming, the front panel user interface and controls are disabled. To return to local front panel control, press the front panel Clear/Tab key [Clr -->|], keyboard Esc key, or send the RTL command. For general information about GPIB, refer to Section 1-5 “IEEE 488 GPIB Description”. 3-2 Command Descriptions IEEE commands are used to control instrument status registers, status reporting, synchronization, data storage, and other common functions. All IEEE 488.2 commands are identified by the leading asterisk in the command word and are fully defined in IEEE 488.2. Each IEEE command is followed a complete descriptive listing of the command description, parameters, and output. If applicable, an example for each command, the default value, and the range information is written out at the end of the individual description. • See Chapter 2, “Programming the VectorStar Series VNA”, “Notational Conventions” on page 2-6 for definitions of parameters and notations. • Detailed descriptions of parameter types is available in “Data Transmission Methods” on page 2-10and through the links below. • • • • • • or • or • • , • , , • , , , • MPND • MPNF • MPNI MS464xB Series VNA PM PN: 10410-00322 Rev. U 3-1 3-3 Numeric Limits 3-3 IEEE Commands Numeric Limits The following numeric limits are abbreviated in the IEEE command descriptions: • MPND – Maximum Positive/Negative Double Precision Number • +/– 1.792 693 134 86 E+308 • MPNI – Maximum Positive/Negative Integer • – 2 147 483 648 to +2 147 483 647 • +/– 2 E31 • MPNF – Maximum Positive/Negative Float Number • +/– 3.402 819 E+38 3-4 IEEE 488.2 Commands *CLS Description: Clear Status Command. Clears the Status Byte, the Data Questionable Event Register, the Standard Event Status Register, the Standard Operation Status Register, the error queue, the OPC pending flag, and any other registers that are summarized in the Status Byte. No Query Cmd Parameters: NA Query Parameters: NA Query Output: NA Syntax Example: *CLS *DDT | *DDT? Description: Define Device Trigger. The command enters the 488.2 Define Device Trigger command with an input of arbitrary block or string. The query returns the 488.2 Define Device Trigger command as an arbitrary block output string. Note that the IEEE488.2 Standard specifies the input type to only be . In addition, VectorStar VNAs will also accept a . Cmd Parameters: | Query Parameters: NA Query Output: Range: NA Default: NA Syntax Example: *DDT *DDT? 3-2 PN: 10410-00322 Rev. U MS464xB Series VNA PM IEEE Commands 3-4 IEEE 488.2 Commands *ESE *ESE? Description: Standard Event Status Enable and Query. The command sets the Standard Event Status Enable Register bits. The binary weighted data parameter used with this command must have a value between 0 to 255. The query returns the value of the Standard Event Status Enable Register in format. Refer to “Status System Reporting” on page 2-28. Cmd Parameters: Query Parameters: NA Range: 0 to 255 Query Output: Syntax Example: *ESE *ESE? *ESR? Description: Standard Event Status Register Query. Query only. Returns the value of the Standard Event Status Register in format. This command clears the Standard Event Status Register. Refer to “Status System Reporting” on page 2-28. Cmd Parameters: NA Query Parameters: NA Query Output: Range: NA Default: NA Syntax Example: *ESR? *IDN? Description: Identification Query. Query only. This query returns an instrument identification string in IEEE-488.2 specified format consisting of four fields separated by commas. The fields are: , , , where the actual model number, serial number, and firmware version of the MS464xB Series VNA queried will be passed. The character output is of indeterminate length and must be the last statement issued if multiple commands and/or queries are issued at the same time. See Chapter 2 for definition of . Cmd Parameters: NA Query Parameters: NA Query Output: Range: NA Default: NA Syntax Example: *IDN? *IST? Description: Individual Status Query. Output the value of the IST message. This command is not supported by VectorStar VNA hardware. MS464xB Series VNA PM PN: 10410-00322 Rev. U 3-3 3-4 IEEE 488.2 Commands IEEE Commands *OPC Description: Operation Complete Command. When the *OPC command is encountered, it does nothing. Program flow is allowed to proceed to the next command in the input buffer. No query. Note that *OPC and *OPC? are not a command/query pair although they appear to be. When the *OPC command is encountered, it immediately sets the Operational Complete bit in the Standard Events Status Register. The *OPC command is a control command for overlapped commands in systems that support command overlapping. The VectorStar does not support overlapped commands, and as a result, no pause function is provided. Overlapped Command Background Some non-VectorStar GPIB implementations allow commands to execute simultaneously which is called an Overlapped Command. For example, a calibration step which takes many minutes could be set into operation and then allow other GPIB communication and control commands to proceed while the calibration step continues to take place. At some point in these non-VectorStar GPIB implementations, the separate Overlapped Operational Streams need to be brought back together and placed under programmatic control in a process called Regaining Synchronization between the controller PC and the instrument. The commands *OPC, *OPC?, and *WAI are designed to regain synchronization control and three different synchronization methods. IEEE 488.2 Overlapped Command Definitions The *OPC, *OPC?, and *WAI commands provide coverage for command completion before the next command is parsed and executed and comprise a class of commands termed Overlapped Commands. For instruments that support overlapped commands, each command works differently. Per the IEEE 488.2 specification: • “IEEE 488.2 defines a distinction between overlapped and sequential commands. • As defined in IEEE 488.2, a sequential command is one which finishes executing before the next command starts executing. An overlapped command is one which does not finish executing before the next command starts executing. • These types of commands are described in IEEE 488.2, section 12. Examples are given in IEEE 488.2, Appendix B. • IEEE 488.2 defines three common commands (*OPC, *OPC?, *WAI) which a device controller can use to synchronize its operation to the execution of overlapped commands. • Each overlapped command has associated with it a Pending Operation flag. • The device sets this flag TRUE when it passes the corresponding command from the Execution Control block to the Device Action block. • The device sets the flag false when the device operation is finished, or has been aborted.” *OPC Synchronization The *OPC Operation Complete command is defined in IEEE 488.2-1992, Section 10.18. *OPC works only if one or more preceeding commands are overlapped command. In systems that support overlapped commands, when this command is encountered, it waits until all overlapped commands have completed. Once all prior overlapped commands are complete, it instructs the parser to execute the next following command. A typical use would be to issue a *OPC before issuing a command for a long duration measurement sweep. *OPC causes the instrument to continuously sense the No Operation Pending flag. When the No Operation Pending (NOP) flag becomes TRUE, the OPC event bit in the Standard Event Status Register is set to “1” to indicate that the state of all pending operations have been completed. If this bit had been previously programmed to send a Service Request, then the controller would be aware that all is synchronized. 3-4 PN: 10410-00322 Rev. U MS464xB Series VNA PM IEEE Commands 3-4 IEEE 488.2 Commands • For example, OV1 through OV3 are overlapped commands where the command series is OV1, OV2, OV3, *OPC, XXX. • Commands OV1, OV2, OV3 start running. The NOP is set to FALSE. • Parser execution stops at *OPC and the parser waits while the NOP is FALSE. • Commands OV1, OV2, and OV3 continue to run in overlapped mode. • Commands OV1, OV2, and OV3 are finally complete. • The NOP flag is set to TRUE and *OPC sets the status bit to 1. • Parser execution resumes. • Command XXX starts running. *OPC? Synchronization In systems that support overlapped commands, the *OPC? Operation Complete Query command waits until all overlapped commands have been completed. When that synchronizing moment arrives, the ASCII character “1” is placed in the output buffer. This sets the MAV bit in the Status byte to TRUE which indicates there is data in the output buffer. If the controller had been attempting to read data, the moment the “1” appears in the output buffer, it is read by the controller making it aware that all is synchronized. When that synchronizing moment arrives, the next command in the input buffer is executed and the command execution is synchronized. • For example, OV1 through OV3 are overlapped commands where the command series is OV1, OV2, OV3, *OPC?, XXX. • Commands OV1, OV2, OV3 start running. The NOP is set to FALSE. • Parser execution stops at *OPC? and the parser waits while the NOP is FALSE. • Commands OV1, OV2, and OV3 continue to run in overlapped mode. • Commands OV1, OV2, and OV3 are finally complete. • The NOP flag is set to TRUE and *OPC? puts a one (“1”) in the output buffer. • Parser execution resumes. • Command XXX starts running. *WAI Synchronization In systems that support overlapped commands, the *WAI Wait-to-Continue Command causes the parser to wait until all overlapped commands have been completed. When that synchronizing moment arrives, the next command in the input buffer is executed and command execution is synchronized. • For example, OV1 through OV3 are overlapped commands where the command series is OV1, OV2, OV3, *WAI, XXX. • Commands OV1, OV2, OV3 start running. The NOP is set to FALSE. • Parser execution stops at *WAI and the parser waits while the NOP is FALSE. • Commands OV1, OV2, and OV3 continue to run in overlapped mode. • Commands OV1, OV2, and OV3 are finally complete. • The NOP flag is set to TRUE. • Parser execution resumes. • Command XXX starts running. VectorStar and Overlapped Commands In VectorStar VNAs, and in Anritsu’s earlier 360 and Lightning VNAs, there are no Overlapped Commands. Everything works synchronously and no command is executed until the command which preceded it has finished. Because of this, the commands *OPC, *OPC? and *WAI work slightly differently than the IEEE 488.2 specification. MS464xB Series VNA PM PN: 10410-00322 Rev. U 3-5 3-4 IEEE 488.2 Commands IEEE Commands Related Commands: *OPC, *OPC?, and *WAI commands. Cmd Parameters: NA Query Parameters: NA Query Output: Range: NA Default: NA Syntax Example: *OPC *OPC? Description: Operation Complete Query. Query only. Not a command/query pair with *OPC. When the *OPC? command is encountered, it does nothing. Program flow is allowed to proceed to the next command in the input buffer. Per IEEE 488.2, *OPC? is an Overlapped Command which VectorStar VNAs do not support. When the *OPC? command is encountered, it immediately puts the character “1” (one) in the Output Queue buffer, and parser execution continues. It sets the MAV bit true when all pending operations are complete. The *OPC, *OPC?, and *WAI Overlapped Commands are related. Because VectorStar does not support overlapped commands, they do not function exactly as specified in IEEE 488.2. See the description of Overlapped Commands in the *OPC command description above. Related commands: *OPC, *OPC?, and *WAI commands. Cmd Parameters: NA Query Parameters: NA Query Output: Range: NA Default: NA Syntax Example: *OPC? *OPT? Description: Operation Query. Query only. The query reads out the identification number of an option installed in the MS4640B. See Chapter 2 for definition of . Cmd Parameters: NA Query Parameters: NA Range: NA Default: NA Query Output: Syntax Example: *OPT? *PRE *PRE? Description: The command enters the 488.2 Parallel Poll Register Enable mask. The query outputs the 488.2 Parallel Poll Register Enable mask. This command/query is not supported by VectorStar VNA hardware. 3-6 PN: 10410-00322 Rev. U MS464xB Series VNA PM IEEE Commands 3-4 IEEE 488.2 Commands *RST Description: Reset Command. The *RST command performs a device reset of the MS4640B VNA to a pre-defined condition or to a user-defined condition. No query. The user-defined condition of *RST resets all user programmable parameters to those defined by the user in a saved configuration file. The pre-defined condition of the *RST command sets the defaults described below. For additional information on default parameter values, see each SCPI command in this manual. *RST Does Reset the Following Parameters Except as explicitly excluded in the next section, the *RST command does the following: • Sets the device-specific functions to a known state that is independent of the past-use history of the device; • Device specific commands may be provided to program a different reset state than the original factory-supplied one; • Sets the macro defined by *DDT to a device-defined state; • Disables macros; • Forces the device into the OCIS state (Operation Complete Command Idle State); • Forces the device into the OQIS state (Operation Complete Query Idle State). *RST Does Not Reset the Following Parameters The *RST command does not change the parameters listed below: • Does not change the state of the IEEE 488.1 interface; • Does not change the selected IEEE 488.1 address of the device; • Does not change the GPIB address of the device; • Does not change the Output Queue; • Does not change any Event Enable Register settings including the Standard Event Status Enable Register; • Does not change any Event Register setting including the Standard Event Status Register settings; • Does not change the power-on-status-clear flag setting; • Does not change the Service Request Enable Register; • Does not change the maximum number of instrument points to 25,000 if it is set to 100,000 nor change them to 100,000 if it is set to 25,000. Cmd Parameters: NA Query Parameters: NA Query Output: NA Range: NA Default: NA Syntax Example: *RST MS464xB Series VNA PM PN: 10410-00322 Rev. U 3-7 3-4 IEEE 488.2 Commands IEEE Commands *SRE *SRE? Description: Service Request Enable. The command sets the Service Request Enable Register bits. A zero value in the command resets the register. The query returns the value of the Service Request Enable Register in format. Bit 6 is always zero. The integer data parameter used with this query have a value between 0 to 255. Cmd Parameters: Query Parameters: NA Query Output: Range: 0 to 255; 0 performs a register reset. Default: NA Syntax Example: *SRE *SRE? *STB? Description: Read Status Byte Query. Query only. Returns the content of the Status Byte Register (bits 0 through 5 and 7). Bit 6 is the Master Summary Status bit value. This command does not reset the status byte values. Query Parameters: NA Query Output: Range: NA Default: NA Syntax Example: *STB? 3-8 PN: 10410-00322 Rev. U MS464xB Series VNA PM IEEE Commands 3-4 IEEE 488.2 Commands *TRG Description: Trigger Command. Triggers the instrument if :TRIGger:SOURce command data parameter is set to REMOTE. Performs the same function as the Group Execute Trigger ( ) bus command as defined in IEEE 488.2. *TRG or the can trigger a measurement. No query. The *TRG and commands are handled differently by the parser. The *TRG command: • The *TRG command can be mixed with other GPIB commands in a command string which goes through the parser. • The *TRG command can only trigger a single measurement event on only one device in the GPIB network. The command: • The gets turned into the command *TRG and goes through the parser by itself. • A can trigger single measurement events on any or all instruments in the GPIB network. What is measured depends on the setting of the *DDT and :TRIGger[:SEQuence]:EXTernal:TYPe commands. • If a *DDT command has been issued previously, the *TRG or will execute what is defined in the *DDT instead. • If a *DDT has not been issued, the *TRG triggers a measurement based on the :TRIG:EXT:TYP command which can be measurement of a point, a single sweep, a single channel, or all channels. • If a sweep is selected, on 2-port VNAs, it can be either a either a forward or reverse sweep. On 4-port VNAs, the sweep can be between any two ports. Cmd Parameters: NA Query Parameters: NA Query Output: NA Range: NA Output: NA-port Syntax Example: *TRG *TST? Description: Self Test Query. Query only. Performs a self test and outputs the self test status in format with the following values: • 0 indicates that self test passed • Any number greater than 0 indicates the number of the self test that failed • 144 indicates that the self test was aborted. Cmd Parameters: NA Query Parameters: NA Query Output: Range: NA Default: NA Syntax Example: *TST? MS464xB Series VNA PM PN: 10410-00322 Rev. U 3-9 3-4 IEEE 488.2 Commands IEEE Commands *WAI Description: Wait-to-Continue Command. When the *WAI command is encountered, it does nothing. Program flow is allowed to proceed to the next command in the input buffer. No query. The *WAI command is an Overlapped Command that provides coverage for command completion when the device supports overlapped command execution. The VectorStar does not support overlapped commands, and as a result, the *WAI does not function exactly as specified in IEEE 488.2. See the description of Overlapped Commands in the *OPC command description above. Related commands: *OPC, *OPC?, and *WAI. Cmd Parameters: NA Query Parameters: NA Query Output: NA Syntax Example: *WAI 3-10 PN: 10410-00322 Rev. U MS464xB Series VNA PM Chapter 4 — System and Troubleshooting Commands 4-1 Introduction This chapter provides a listing and description of general system-related commands used for configuration, diagnostics, internal calibration, and troubleshooting. Complete details of each command is given in the listing following each command SCPI subsystem. If applicable, an example for each command, the default value, and the SCPI information is written out at the end of the individual description. When operating the VectorStar VNA through remote programming, the front panel user interface and controls are disabled. To return to local front panel control, press the front panel Clear/Tab key [Clr -->|], keyboard Esc key, or send the RTL command. Note For general information about GPIB, refer to “IEEE 488 GPIB Description” on page 1-3. 4-2 Parameters and Notations See Chapter 2, “Notational Conventions” on page 2-6 for definitions of parameters and notations. A notation summary table is available in Table 2-4, “Parameter Notations” on page 2-7. Detailed descriptions are available in “Data Transmission Methods” on page 2-10 and through the links below. • • • • • • or • or •