User Interface (UI) Log

Last updated: 2014-11-28

Description

To help you troubleshoot or optimize your GPIB control programs, you can configure the test set to capture GPIB interface traffic and store it in the UI (User Interface) Log. To enable GPIB logging, see Step 2: Turn On UI Log GPIB State .

The UI log buffer can store up to 153600 bytes of information with 255 bytes displayed in a row. If the buffer is full, the oldest entry is removed from the top of the log and the newest entry is added to the end.

You can reset and access the UI Log through either the GPIB interface or a Web Browser.

The following procedures demonstrate how to reset and access the UI Log.

Step 1: Clear UI Log Data

Before capturing new GPIB traffic, you can clear the residual information in UI Log storage. Two methods are valid to clear UI Log data storage in the test set:

Clear the UI Log via Local Area Network (LAN)
Connect your computer to the test set via LAN or directly via a LAN crossover cable.
Go to the URL of the test set using a web browser such as Internet Explorer.

URL in Web Browser to Clear UI Log Data

Command: http:// <test_set_ip_address> /uilogclear

Example: http://111.222.333.444/uilogclear

Figure 1: Clear UI Log Data

Clear the UI log via GPIB
Connect your computer to the test set via a GPIB interface.
Send the GPIB command SYSTem:LOG:UI:CLEAR to the test set and the log is cleared.

Step 2: Turn On UI Log GPIB State

Send the GPIB command SYSTem:LOG:UI:GPIB[:STATe] to the test set before you run your test program or send it from the point in your program where it is desired to start GPIB logging.

The Log GPIB state is reset to OFF after cycling power. It is not reset by a full preset.

Step 3-1: Get UI Log Data

Go to the URL of the test set using your web browser to retrieve the GPIB log. The GPIB log is displayed in the browser window.

You must ensure the computer is connected to the test set either via Ethernet LAN or a direct connection using a LAN crossover cable.

URL in Web Browser to get the UI Log Data:

Command: http:// <test_set_LAN_IP_Address> /uilog

Example: http://111.222.333.444/uilog

Figure 2: Display UI Log Data in Web Browser

In addition to GPIB traffic information, the UI Log also includes data regarding the key presses, knob turns and error messages that occur as you operate your test set from the front panel. Only the lines with the prefix "rem:" indicate the GPIB commands.

The UI Log display is not real time, therefore the latest UI log does not display automatically in the web browser. To capture multiple logs, click Refresh in the View menu.

Step 3 - 2: Get Other UI Log Information (Optional)

You can get more information about UI log data by sending the GPIB queries.

Query the number of lines containing GPIB commands in the UI Log

The GPIB query SYSTem:LOG:UI:COUNt? returns the number of lines in the log since the last time the log was cleared.

Query the string at the specified line in the UI Log

The GPIB query SYSTem:LOG:UI:REPort? returns the string located at the line in the log that you specify. Note that issuing this command turns off GPIB logging. You must turn it back on using the SYSTem:LOG:UI:GPIB[:STATe] command to continue GPIB logging.

Step 4: Save UI Log Data

To save the log in the Web Browser to a file:

In the File menu, click Save As....
In the Save as type: box, select Text File (*.txt).
In the File name: box, type the file name.
Click the Save button.