Troubleshooting

If you are able to connect to the SCPI interface, but a command does not seem to be working as expected, query the SCPI system error queue by issuing the :SYSTem:ERRor? SCPI query and read back the result, which may provide additional information regarding syntax errors or invalid configurations. See Error Codes for more information on possible errors.

Translator Framework

The Keysight Translator Framework process hosts the VSA SCPI interface layer that interacts with the native VSA .NET Remoting API.  The Translator Framework provides a control panel that can be used as a diagnostic tool to monitor SCPI commands sent to the VSA.  This control panel can be opened by double-clicking the Translator Framework icon in the system tray show as follows:

The Translator Framework control panel will display any errors that are encountered related to I/O connection failures or other communication problems.  Also, setting the log level to Verbose (see below) will list of all the SCPI writes and reads.  This log can be saved to disk for diagnostic purposes.

When the Agilent.Translator.exe process is not running, the SCPI interface will not be available.  Ensure that the steps in the Configuring SCPI section have been followed.  If after following these steps, the Translator Framework process is still not running, open the Programs and Features (Add/Remove programs in Windows XP) Windows Control Panel to ensure that the Keysight Translator Framework is installed. 

The Translator Framework is automatically installed when the 89600 VSA software is installed, but if the Translator has since been removed, the Translator can be reinstalled from the 89600 installation disk by running the installer file located at [89600 VSA DVD]\SCPI\AgilentTranslatorFramework.msi

Known Issues

The following are some known issues with the VSA SCPI interface: