Last updated: September 2, 2009
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.
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)
Clear the UI log via GPIB
Command | Example |
---|---|
SYSTem:LOG:UI:CLEAR | SYST:LOG:UI:CLEAR |
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 |
Command | Example |
---|---|
NOTE |
Command | Example |
---|---|
http:// <test_set_LAN_IP_Address> /uilog | http://111.222.333.444/uilog |
NOTE |
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.
You can get more information about UI log data by sending the GPIB queries.
The GPIB query in the following table returns the number of lines in the log since the last time the log was cleared.
Command | Example |
---|---|
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.
Command | Example |
---|---|