User Interface (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	Example
    http:// <test_set_ip_address> /uilogclear	http://111.222.333.444/uilogclear

  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 in the following table to the test set and the log is cleared.

  SYSTem:LOG:UI:CLEAR

  GPIB Command to Clear the UI Log

  Command	Example
  SYSTem:LOG:UI:CLEAR	SYST:LOG:UI:CLEAR

Step 2: Turn On UI Log GPIB State

• Send the GPIB command in the following table 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.

     

  NOTE

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

  ---

     

  SYSTem:LOG:UI:GPIB[:STATe]

  UI Log GPIB State Command

  Command	Example
  SYSTem:LOG:UI:GPIB[:STATe] ON|OFF	SYST:LOG:UI:GPIB:STAT ON

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.
     

  NOTE

  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	Example
  http:// <test_set_LAN_IP_Address> /uilog	http://111.222.333.444/uilog

  Display UI Log Data in Web Browser

  

     

  NOTE

  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 in the following table returns the number of lines in the log since the last time the log was cleared.

  SYSTem:LOG:UI:COUNt?

  Query the number of lines in the UI Log

  Command	Example
  SYSTem:LOG:UI:COUNt?	SYST:LOG:UI:COUN?

• Query the string at the specified line in the UI Log

  The GPIB query in the following table 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.

  SYSTem:LOG:UI:REPort?

  Query the string in the UI Log

  Command	Example
  SYSTem:LOG:UI:REPort? <sp><number value>	SYST:LOG:UI:REP? 11

Step 4: Save UI Log Data

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

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