GPIB Analyzer User Manual
GPIB Analyzer User Manual
2
TM
Worldwide Offices
Australia 61 2 9672 8846, Austria 43 0 662 45 79 90 0, Belgium 32 0 2 757 00 20, Brazil 55 11 3262 3599,
Canada (Calgary) 403 274 9391, Canada (Montreal) 514 288 5722, Canada (Ottawa) 613 233 5949,
Canada (Québec) 514 694 8521, Canada (Toronto) 905 785 0085, Canada (Vancouver) 514 685 7530,
China 86 21 6555 7838, Czech Republic 42 02 2423 5774, Denmark 45 45 76 26 00,
Finland 385 0 9 725 725 11, France 33 0 1 48 14 24 24, Germany 49 0 89 741 31 30, Greece 30 2 10 42 96 427,
Hong Kong 2645 3186, India 91 80 4190000, Israel 972 0 3 6393737, Italy 39 02 413091,
Japan 81 3 5472 2970, Korea 82 02 3451 3400, Malaysia 603 9059 6711, Mexico 001 800 010 0793,
Netherlands 31 0 348 433 466, New Zealand 64 09 914 0488, Norway 47 0 32 27 73 00,
Poland 48 0 22 3390 150, Portugal 351 210 311 210, Russia 7 095 238 7139, Singapore 65 6 226 5886,
Slovenia 386 3 425 4200, South Africa 27 0 11 805 8197, Spain 34 91 640 0085, Sweden 46 0 8 587 895 00,
Switzerland 41 56 200 51 51, Taiwan 886 2 2528 7227, United Kingdom 44 0 1635 523545
For further support information, refer to the Technical Support and Professional Services appendix. To comment
on the documentation, send email to techpubs@ni.com.
Warranty
The media on which you receive National Instruments software are warranted not to fail to execute programming instructions, due to defects
in materials and workmanship, for a period of 90 days from date of shipment, as evidenced by receipts or other documentation. National
Instruments will, at its option, repair or replace software media that do not execute programming instructions if National Instruments receives
notice of such defects during the warranty period. National Instruments does not warrant that the operation of the software shall be
uninterrupted or error free.
A Return Material Authorization (RMA) number must be obtained from the factory and clearly marked on the outside of the package before
any equipment will be accepted for warranty work. National Instruments will pay the shipping costs of returning to the owner parts which are
covered by warranty.
National Instruments believes that the information in this document is accurate. The document has been carefully reviewed for technical
accuracy. In the event that technical or typographical errors exist, National Instruments reserves the right to make changes to subsequent
editions of this document without prior notice to holders of this edition. The reader should consult National Instruments if errors are suspected.
In no event shall National Instruments be liable for any damages arising out of or related to this document or the information contained in it.
EXCEPT AS SPECIFIED HEREIN, NATIONAL INSTRUMENTS MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AND SPECIFICALLY DISCLAIMS ANY WARRANTY OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. CUSTOMER’S RIGHT TO RECOVER DAMAGES CAUSED BY FAULT OR NEGLIGENCE ON THE PART OF
NATIONAL INSTRUMENTS SHALL BE LIMITED TO THE AMOUNT THERETOFORE PAID BY THE CUSTOMER. NATIONAL INSTRUMENTS WILL NOT BE LIABLE FOR
DAMAGES RESULTING FROM LOSS OF DATA, PROFITS, USE OF PRODUCTS, OR INCIDENTAL OR CONSEQUENTIAL DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY
THEREOF. This limitation of the liability of National Instruments will apply regardless of the form of action, whether in contract or tort, including
negligence. Any action against National Instruments must be brought within one year after the cause of action accrues. National Instruments
shall not be liable for any delay in performance due to causes beyond its reasonable control. The warranty provided herein does not cover
damages, defects, malfunctions, or service failures caused by owner’s failure to follow the National Instruments installation, operation, or
maintenance instructions; owner’s modification of the product; owner’s abuse, misuse, or negligent acts; and power failure or surges, fire,
flood, accident, actions of third parties, or other events outside reasonable control.
Copyright
Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical, including photocopying,
recording, storing in an information retrieval system, or translating, in whole or in part, without the prior written consent of National
Instruments Corporation.
Trademarks
CVI™, HS488™, National Instruments™, NI™, NI-488.2™, and ni.com™ are trademarks of National Instruments Corporation.
Product and company names mentioned herein are trademarks or trade names of their respective companies.
Patents
For patents covering National Instruments products, refer to the appropriate location: Help»Patents in your software, the patents.txt file
on your CD, or ni.com/patents.
» The » symbol leads you through nested menu items and dialog box options
to a final action. The sequence File»Page Setup»Options directs you to
pull down the File menu, select the Page Setup item, and select Options
from the last dialog box.
bold Bold text denotes items that you must select or click in the software, such
as menu items and dialog box options. Bold text also denotes parameter
names.
monospace Text in this font denotes text or characters that you should enter from the
keyboard, sections of code, programming examples, and syntax examples.
This font is also used for the proper names of disk drives, paths, directories,
programs, subprograms, subroutines, device names, functions, operations,
variables, filenames and extensions, and code excerpts.
monospace bold Bold text in this font denotes the messages and responses that the computer
automatically prints to the screen. This font also emphasizes lines of code
that are different from the other examples.
Contents
Chapter 1
GPIB Analyzer Overview
About This Manual ........................................................................................................1-1
GPIB Analyzer Overview ..............................................................................................1-1
Online Help....................................................................................................................1-1
Features of the GPIB Analyzer ......................................................................................1-1
Capturing Data with the GPIB Analyzer .......................................................................1-2
Analyzing Captured Data with the GPIB Analyzer.......................................................1-2
Starting the GPIB Analyzer ...........................................................................................1-3
Chapter 2
GPIB Analyzer Features
Main GPIB Analyzer Window ......................................................................................2-2
File»New Capture Display ..............................................................................2-2
File»Open Capture Display .............................................................................2-2
File»Exit ..........................................................................................................2-3
Settings»Change Settings ................................................................................2-3
Settings»Load Settings ....................................................................................2-3
Settings»Save Settings As ...............................................................................2-3
Windows Menu ...............................................................................................2-3
Help Menu .......................................................................................................2-3
Settings Configuration ...................................................................................................2-4
Capture Stimulus Configuration......................................................................2-5
Trigger Condition Configuration.....................................................................2-6
Configuration of Other Trigger Settings .........................................................2-6
Exiting the Settings Dialog Box ......................................................................2-7
Action Window..............................................................................................................2-7
Bus Monitor Window ....................................................................................................2-8
Capture Display Window...............................................................................................2-9
Menu Choices from a Capture Display ...........................................................2-10
Capture Settings in a Capture Display.............................................................2-11
Markers & Statistics in an Inactive Capture Display ......................................2-11
Controls in a Capture Display .........................................................................2-11
Capture Data in a Capture Display Window ...................................................2-12
Search Capability ...........................................................................................................2-12
Chapter 3
How To…
Install the GPIB Analyzer ............................................................................................. 3-1
Start the GPIB Analyzer................................................................................................ 3-1
Exit the GPIB Analyzer................................................................................................. 3-1
Start and Stop Capture of Data...................................................................................... 3-1
Monitor or Participate in GPIB Activity ....................................................................... 3-2
View/Change the State of GPIB Data and Control Lines ............................... 3-2
Accept a Single Byte....................................................................................... 3-3
View Previously Captured Data .................................................................................... 3-3
Configure the Settings ................................................................................................... 3-3
Configure Capture Settings ............................................................................. 3-3
Configure Trigger Settings.............................................................................. 3-4
Timestamp Capture Events ............................................................................. 3-4
Do a Nonintrusive Capture ............................................................................. 3-4
Avoid Overflow Errors ................................................................................... 3-4
Save and Reload Capture/Trigger Settings.................................................................... 3-6
Analyze Captured Data.................................................................................................. 3-6
View the Captured Data .................................................................................. 3-6
Read the Timestamp Column ........................................................... 3-7
Read the Mnemonics Column .......................................................... 3-8
Search for a Capture Event ............................................................................. 3-8
Mark Capture Events to Show Statistics......................................................... 3-9
Print and Save Captured Data........................................................................................ 3-9
Chapter 4
Tutorial
Part 1. Capture and View New Data ............................................................................. 4-1
Part 2. Capture and View New Data with a Trigger Condition..................................... 4-4
Part 3. Search for Data in a Capture Display................................................................. 4-7
Part 4. Show Statistics for Captured Data ..................................................................... 4-10
Part 5. Print and Export a Capture File.......................................................................... 4-12
Chapter 5
Examples
Example 1. Slow Communication................................................................................. 5-1
Description of Problem ................................................................................... 5-1
Setting up the GPIB Analyzer......................................................................... 5-1
Reading the Capture Display .......................................................................... 5-3
Example 2. A Service Request Problem........................................................................ 5-4
Description of Problem ................................................................................... 5-4
Appendix A
Common Questions
Appendix B
Capture Display Mnemonics
Appendix C
Technical Support and Professional Services
Glossary
Index
Online Help
The GPIB analyzer application includes an online help system, which you
can access while running the analyzer by pressing <F1> or using the Help
menu. The online help contains the same information as this user manual.
You might want to capture and display data based on a specific bus event
without knowing when the event might occur. In this case, you can specify
a trigger condition and capture any number of events before and after the
trigger condition occurs. The capture operation proceeds according to the
settings configuration.
The analyzer can perform the acceptor handshake while capturing, and it
can timestamp captured events. The number of recorded capture events can
be configured to be between 10 and 99999999 and is limited by the memory
available on your computer.
You can reload previously saved capture events for later review and
analysis. You can even have multiple capture displays open so that you can
analyze current bus activity in one display and previously captured data in
another display.
Figure 2-1 shows the main GPIB analyzer window. The Action and
Bus Monitor windows are always open.
display. Filenames for GPIB analyzer capture files typically use the .CAP
extension.
File»Exit
Choosing Exit from the File menu in the main window closes the GPIB
analyzer application. The analyzer prompts you to save any capture display
that contains unsaved GPIB events. The current settings for capturing and
triggering are saved automatically, and they are automatically loaded the
next time you start the GPIB analyzer.
Settings»Change Settings
Choosing Change Settings from the Settings menu in the main window
opens the Settings configuration dialog box so that you can change the
settings used for capturing GPIB events and triggering on specific GPIB
events. Refer to the Settings Configuration section for more information.
Settings»Load Settings
Choosing Load Settings from the Settings menu in the main window
opens a file of previously saved settings to be used for capturing GPIB
events and triggering on specific GPIB events. Filenames for GPIB
analyzer settings typically use the .SET extension.
Settings»Save Settings As
Choosing Save Settings As from the Settings menu in the main window
allows you to save the current settings used for capturing GPIB events and
triggering. Whenever possible, use the .SET extension for GPIB analyzer
settings filenames.
Windows Menu
The Windows menu in the main window lists all currently open GPIB
analyzer windows. When you select a window from this menu, it moves to
the front.
Help Menu
The Help menu in the main window accesses the online help for the GPIB
analyzer. It also accesses information about the analyzer software, such as
version number and hardware configuration.
Settings Configuration
To configure capture and trigger settings, select Change Settings from the
Settings menu in the main window. Figure 2-2 shows the Settings
configuration dialog box.
The configured settings apply only to active capture displays. Notice that
the settings in this window cannot be changed unless capturing and
triggering are turned off. (Use the Action window to turn off capturing and
triggering.)
The Retain up to _____ capture events edit control specifies the number
of captured GPIB events that can be kept in the internal capture memory
buffer. When the buffer becomes full, the oldest GPIB events are discarded
to make space for new GPIB events.
The Handshake rate list box selects the rate at which the GPIB analyzer
accepts data and command bytes. It is disabled unless Participate in
Acceptor Handshake is checked. The Maximum option allows the
analyzer to accept bytes at the fastest rate possible without causing
overflow errors. The other options slow down all GPIB transfers to a rate
no greater than that specified.
The Data Transfers checkbox enables the capture of GPIB data bytes.
Both IEEE 488 and HS488 data bytes are captured.
The Control Line Transitions checkbox enables the capture of EOI, ATN,
SRQ, REN, and IFC GPIB control line transitions. These lines manage the
GPIB interface system.
For more information about setting the capture stimulus, refer to the
Configure the Settings section of Chapter 3, How To….
You can enter the GPIB data lines trigger condition as an ASCII value in
the ASCII edit control, a hexadecimal value in the Hex edit control, or a
binary value in the D8 to D1 spin controls. Notice that the GPIB data trigger
condition is replicated in all three representations: ASCII, hexadecimal,
and binary. Also notice that the D8 to D1 spin controls have the added
feature of letting you select x (don’t care) values for particular GPIB data
lines whose states are not relevant to the GPIB data trigger condition. For
example, if you want to configure the GPIB data trigger so that any
non-ASCII GPIB data causes a trigger, set D8 to 1 and set D7, D6, D5, D4,
D3, D2, and D1 to x.
You can enter the GPIB control lines trigger condition for each of the GPIB
control lines using the spin controls for EOI, ATN, SRQ, REN, IFC,
NRFD, NDAC, and DAV. Notice that the x value (don’t care) can be
chosen for GPIB control lines whose state is not relevant to the trigger
condition.
The spin control on the left configures how to capture data around the first
trigger point. The choices are Capture around first trigger point and
Capture indefinitely after trigger point. If you select Capture around
first trigger point, capture is stopped at a specified point after the first
trigger is noticed, and the three controls below that spin control are enabled.
These controls are the Thumb denotes first trigger point slider control,
the events before trigger edit control, and the events after trigger edit
control. These three additional controls specify the exact location in the
capture buffer for the first trigger point. If you select Capture indefinitely
after trigger point, these three controls are disabled and capture continues,
even after the trigger condition is noticed.
The two spin controls on the right side below the Trigger Condition group
box configure the number of triggers that get recorded and whether beep
sounds occur when the trigger condition is noticed. If you select Trigger
on first occurrence of condition, a single trigger is recorded in the capture
buffer. If you select Trigger on all occurrences of condition, every
instance of the trigger condition is recorded in the capture buffer. To
configure beeping that you want to accompany trigger conditions, select
Do not sound a beep on any trigger, Sound a beep on first trigger point,
or Sound a beep on all trigger points.
For more information about selecting the trigger settings, refer to the
Configure Trigger Settings section of Chapter 3, How To….
Clicking the Cancel button cancels the changes made to the settings and
closes the window.
Clicking the Default button restores the settings to match the default
values, without closing the window.
Action Window
The Action window contains controls you can use to turn capturing and/or
triggering on and off. The Action window, shown in Figure 2-3, is always
open. If the window is hidden, select Windows»Action Window to bring
it to the front.
When the GPIB analyzer application is started, capture and trigger are
both off.
Clicking the Capture button causes the analyzer to begin capturing GPIB
events into the active capture display. Data is captured according to the
current capture configuration settings. Triggering is not enabled.
Clicking the Capture & Trigger button causes the analyzer to begin
capturing GPIB events into the active capture display and monitoring for
trigger conditions. Data is captured according to the current capture
configuration settings, and triggers are monitored according to the current
trigger configuration. The capture and trigger configuration can be
modified using the settings configuration described in the Settings
Configuration section.
Clicking the Off button causes the analyzer to stop capturing GPIB events
and stop monitoring for trigger conditions.
The state of the GPIB data and control lines is displayed on the row of
LEDs and the upper ASCII and Hex edit controls. You can alter the value
of the GPIB data and control lines using the row of binary switches and the
lower ASCII and Hex edit controls.
You can enter the GPIB data value as an ASCII value in the ASCII edit
control, a hexadecimal value in the Hex edit control, or a binary value in
the 8 to 1 binary switches. Notice that the GPIB data value is replicated in
all three representations: ASCII, hexadecimal, and binary.
You can enter the GPIB control value using the EOI, ATN, SRQ, REN,
IFC, NRFD, NDAC, and DAV binary switches. The up position
corresponds to the assertion of the line.
Clicking the Unassert Lines button moves all of the binary switches to the
down (unasserted) position and disables the Accept Byte button.
Clicking the Enable Accept Byte button prepares the analyzer to accept
either GPIB data or command bytes, one byte at a time, and changes the
button title to Disable Accept Byte. The analyzer unasserts NRFD and
asserts NDAC. When another GPIB device on the bus asserts the DAV
signal, indicating that data is available, clicking the Accept Byte button
accepts the byte and prepares for the next byte. Enabling this feature
disables the manual binary switches for the NRFD and NDAC control lines.
When you are finished accepting data, clicking the Disable Accept Byte
button releases control of the handshaking lines.
The Accept Byte button causes the analyzer to examine the state of the
DAV line to determine whether another GPIB device is trying to send a
byte. If DAV is unasserted, clicking Accept Byte has no effect because no
data is available to be accepted. If DAV is asserted, clicking Accept Byte
accepts a single byte of GPIB data by automatically toggling NRFD and
NDAC in the proper sequence. Before you can use this button, you must
click the Enable Accept Byte button in the Bus Monitor window.
Choosing Print from the File menu prints the contents of an inactive
capture display to a selected printer.
Choosing Export from the File menu saves the GPIB events in an inactive
capture display to an ASCII text file, which can be imported into other
applications such as word processors. You cannot import the ASCII file
back into the GPIB analyzer.
Choosing Close from the File menu closes the Capture Display window.
The analyzer program prompts you to save any unsaved GPIB events.
The Help menu accesses the online help for the GPIB analyzer.
The From box is used to select the beginning marker used to calculate the
capture statistics.
The To box is used to select the ending marker used to calculate the capture
statistics.
Click the Find button to open the Find dialog box, which you can use to
specify search criteria for finding a particular GPIB event in an inactive
Capture Display window.
Click the Find Next button to search for the next occurrence of your search
criteria in the inactive capture display. This button is disabled if you have
not yet entered your search criteria in the Find dialog box.
The Display mode spin control chooses the display mode used for the
captured GPIB events. In Detailed display mode, captured GPIB events are
shown one per line. In Summarized display mode, multiple events can be
shown on each line. Line transitions are displayed on separate lines, but
data and command transfers are grouped on the same line. In both display
modes, data transfers are shown in blue, command transfers are shown in
green, and control line transitions, handshake line transitions, and parallel
poll responses are all shown in black.
For specific information about how to interpret the capture display, refer
to the Analyze Captured Data section of Chapter 3, How To…, or to
Appendix B, Capture Display Mnemonics.
Search Capability
The Find and Find Next buttons in the capture display allow you to search
for specific GPIB data and control line patterns, data strings, or trigger
points in an inactive capture display.
To find a trigger point in the Capture Display window, check the Find
Trigger checkbox, and then click the Find button.
To find a particular data and control line pattern, set the pattern of the data
lines using either the ASCII or Hex edit controls or the D8 to D1 spin
controls (for binary values), and set the pattern of the control lines using the
EOI, ATN, SRQ, REN, IFC, NRFD, NDAC, and DAV spin controls.
Notice that the spin controls allow you to select 0 (unasserted), 1 (asserted),
or x (don’t care) for each data and control line. When the data and control
lines have been selected, click the Find button.
To find a series of GPIB data and control line patterns, use the Insert
Above, Insert Below, and Delete buttons to add and remove entries from
the Find String list box until it contains the desired series of GPIB data and
control line patterns. Click the Find button to conduct the search.
Use the Search Direction switch to specify the direction to search from the
current cursor position in the capture display.
Click the Cancel button to cancel the search and close the Find dialog box.
To stop capturing new data, click the Off button in the Action window.
The state of the GPIB data and control lines is displayed on the row of
LEDs and the upper ASCII and Hex edit controls. You can alter the value
of the GPIB data and control lines using the row of binary switches and the
lower ASCII and Hex edit controls.
You can enter the GPIB data value as an ASCII value in the ASCII edit
control, a hexadecimal value in the Hex edit control, or a binary value in
the 8 to 1 binary switches. Notice that the GPIB data value is replicated in
all three representations: ASCII, hexadecimal, and binary.
You can enter the GPIB control value using the EOI, ATN, SRQ, REN,
IFC, NRFD, NDAC, and DAV binary switches. The up position
corresponds to the assertion of the line.
To accept a byte of data on the bus, use the NRFD and NDAC binary
switches to simulate the IEEE 488 handshake, or use the Accept Byte
button, which automatically toggles NRFD and NDAC in the correct
sequence. The Accept Byte button is enabled by clicking the Enable
Accept Byte button.
If you are using the Bus Monitor to assert GPIB lines, do not use the
NI-488.2 ibfind or ibdev functions. These functions unassert the lines
on the bus, even though the switches in the Bus Monitor window show that
the lines are asserted. If you encounter this problem, click the Unassert
Lines button and avoid using the ibfind or ibdev functions.
If you try to accept a byte when no GPIB device is currently trying to source
a byte (DAV unasserted), toggling the handshake lines or clicking on
Accept Byte has no effect.
To use the configured trigger settings, start capture using the Capture &
Trigger button in the Action window, instead of the Capture button.
Do a Nonintrusive Capture
To prevent the GPIB analyzer from participating in acceptor handshaking,
uncheck the Participate in Acceptor Handshake checkbox in the
Settings dialog box. If this checkbox is checked, the analyzer participates
in all handshaking on the GPIB. You might want to select this checkbox to
slow down the GPIB transfers or to avoid overflow errors.
If an overflow error occurs, one or more GPIB events have been lost. You
can usually avoid overflow errors by making one of the following changes:
• Check the Participate in Acceptor Handshake checkbox in the
Settings dialog box, and set the Handshaking rate to Maximum.
This configuration causes the analyzer to hold off when the FIFO is
almost full. It prevents high speed GPIB data transfers when the FIFO
is almost full, which can be a common cause of overflow errors.
• Uncheck the Handshake Line Transitions checkbox in the Settings
dialog box. If this option is selected, you might capture up to six times
as many GPIB events as when choosing to capture only data and
command transfers. The reason for this is that when you enable the
capture of handshake line transitions, you start getting GPIB events
such as NDAC↑ and NRFD↓, which reflect the multiple changes that
occur to the states of the GPIB handshake lines for each byte
transferred on the GPIB. This high volume of events is likely to cause
overflow errors.
In summarized mode, where more than one event can be present on a line,
the timestamp value represents the time elapsed between the first event on
that line and the first event on the previous line.
After you have placed your markers, you can use the From and To controls
in the Markers & Statistics group box to examine statistics about the
captured data.
If you are using summarized display mode, you might have more than
one marker for each line. In this case, the letter M appears in the marker
column. You can click the M several times to see each marker for that line.
Both inactive and active (if capturing is turned off) capture displays can be
saved to a file. To save the data in a Capture Display window, use
File»Save As. Whenever possible, use the .CAP extension for saving
capture display files. Captured data is saved in an analyzer-specific format
and can be reopened as an inactive capture display.
You also can export an inactive capture display as an ASCII text file to
another application, such as a word processor. Use File»Export to export
the captured data. You can export captured data as text in both detailed and
summarized formats. You cannot import the ASCII text file back into the
GPIB analyzer.
The Settings dialog box should now look like Figure 4-1.
in this script file write data on the GPIB, and the analyzer portion of
the GPIB hardware captures the data.
11. At the : prompt, type quit and press <Enter> to exit the Interactive
Control utility.
12. Switch back to the GPIB analyzer, and click Off in the Action window
to stop the capture.
13. In the active Capture Display window, use the scroll bar to go to the
beginning of the capture file.
The Capture Display window should look like Figure 4-2.
mode is often easier to read if you do not need to see one event per line,
but it displays less information.
9. Click in the spin control with the words Trigger on first occurrence
of condition to see your choices. Select Trigger on all occurrences of
condition. This option captures and displays all occurrences of the
trigger condition.
10. Click in the spin control with the words Do not sound a beep on any
trigger to see your choices, then select Sound a beep on first
trigger point.
The Settings dialog box should look like Figure 4-3.
14. Open the Interactive Control utility from MAX, which is started by
selecting Start»Programs»National Instruments»NI-488.2»
Explore GPIB. To start Interactive Control, select Tools» NI-488.2»
Interactive Control.
15. At the prompt, enter $ "c:\Program Files\National
Instruments\NI-488.2\Analyzer\Tutorial.txt" to run the
tutorial script again. (The path to the file might be different if you did
not use the default installation directory when you installed the GPIB
analyzer software.)
16. Switch back to the analyzer program and click Off in the Action
window to stop the capture.
17. In the active Capture Display window, click Switch to Inactive
Display.
18. If necessary, switch to detailed display mode. Scroll to the top of the
capture display.
The Capture Display window should look something like Figure 4-4.
The trigger points are enclosed in dotted boxes and the display shows
five events before the first trigger point.
14. Choose Insert Below again, but this time enter 7. These characters
form a string (“567”) that the analyzer searches for in the capture file.
The Find dialog box should look like Figure 4-6.
16. The first character of the matched search string, “5,” will be
highlighted as shown in Figure 4-7.
17. Click the Find Next button to continue your search. The next
successful search result will be highlighted.
The capture display statistics show the total number of captured events
from marker M0 to marker M1. The Time elapsed statistic shows you
the total time to transfer this block of data. The Capture events per
second box shows system performance during this period of time.
5. Choose M0 in the Go To list box to highlight the line with the letter
“A” again.
The technician clicks OK to close the Settings dialog box and clicks
Capture in the Action window to start capture, then runs his application.
After the application executes, he switches back to the analyzer and clicks
Off in the Action window to stop capture.
In the Settings dialog box of the GPIB analyzer, the engineer chooses the
following settings:
• Capture data transfers, command transfers, and control line transitions
• Capture 500 events after the trigger point
• Trigger condition set to SRQ asserted (SRQ = 1) and all other lines
equal to “x”
• Timestamping feature enabled
• Capture around the first trigger point
The engineer chooses Capture & Trigger in the Action window and runs
his application program.
Device 1
Response Time
Device 2
Response Time
The marker M0 appears on the first line, which shows the assertion of the
SRQ line. The engineer places a marker M1 where the Controller starts the
serial poll by sending the Unlisten command (UNL). By choosing M0 in
the From list box and M1 in the To list box to calculate the Time elapsed
statistic, he sees that the Controller takes 953 ms, 52 µs, and 400 ns to
respond to the service request.
The Controller sends its listener address (LA0 in this case) and the serial
poll enable (SPE) command. The Controller sends TA1 so that the first
device can talk, then unasserts ATN and reads the status byte (0x00) from
the device. By reading the timestamp information on the line where the first
device sends 0x00, the engineer knows that the device takes 3 ms and
465 µs to send its status byte.
Because the first device is not the one requesting service (because its status
byte does not have bit 6 set), the Controller addresses the second device to
talk. The Controller then reads the device’s status byte (0x40), which
indicates that it is requesting service. By reading the timestamp information
on the line where the second device sends 0x40, the engineer sees that the
device takes only 4 µs and 850 ns to send its status byte.
Because the response time of the second device polled is shorter than the
first device, the engineer changes his application so that the Controller
always polls the faster device first. If the faster device is the one requesting
service, the Controller will not need to poll the slower device.
The programmer chooses Capture in the Action window and captures the
sequence of events on the GPIB. She then clicks Off in the Action window
of the analyzer.
In this example, the Controller does not seem to be sending any data bytes.
In her application, the programmer set up the device to have primary
address 3 and secondary address 0. She notices, however, that at the line
containing the marker M0, the Controller configures the device to be a
Listener at primary address 3 with no secondary address. The device is
not responding because the Controller is not addressing it correctly.
The programmer corrects her application and runs the capture again. The
Controller can now write to the device, and the capture display looks like
Figure 5-7.
The programmer chooses Capture in the Action window and captures the
sequence of events as the device sends data on the bus. He then clicks Off
in the Action window of the analyzer.
This capture display shows that the device asserts EOI with the last byte.
The programmer remembers that he set up his application to expect an
End-of-String character to terminate the data transfer from the device. He
changes the program so that it expects the assertion of EOI to terminate the
data transfer. The application then runs without an error.
This state of the handshake lines is necessary to guarantee that valid data is
present on the data lines.
What do the rows of lights and switches in the Bus Monitor window
represent?
The LEDs represent the state of the bus lines at all times. The toggle
switches represent the assertion of lines from within the Bus Monitor
window of the analyzer. If the LED for a particular line is on, and the switch
for that line is off (down position), the line is asserted, but not by the Bus
Monitor.
In summarized display mode, where more than one event can be present on
a line, the timestamp value represents the time elapsed between the first
event on that line and the first event on the previous line.
GTL Go to local
1 If SC appears after a talk or listen address, it is a secondary address. If it appears after a parallel poll configure, it is either a
parallel poll enable (PPE) or a parallel poll disable (PPD) command. If it appears after configuration enable (CFE), it is the
cable length for HS488.
UNL Unlisten
UNT Untalk
GPIB parallel poll responses captured using the parallel poll response
capture stimulus:
If you searched ni.com and could not find the answers you need, contact
your local office or NI corporate headquarters. Phone numbers for our
worldwide offices are listed at the front of this manual. You also can visit
the Worldwide Offices section of ni.com/niglobal to access the branch
office Web sites, which provide up-to-date contact information, support
phone numbers, email addresses, and current events.
A
ANSI American National Standards Institute
B
B bytes
D
DIO digital input/output
E
EOI end or identify
EOS End-of-String
F
FCC Federal Communications Commission
FIFO first-in-first-out
G
GPIB General Purpose Interface Bus
H
hex hexadecimal
Hz hertz
I
I/O input/output
in. inches
K
Kbytes kilobytes
L
LED light-emitting diode
legacy board ISA board whose system resources are chosen by changing physical
switches or jumpers on the board
M
m meters
MB megabytes of memory
P
PC personal computer
R
RAM random-access memory
S
s seconds
V
VCCI Voluntary Control Council for Interference
I P
installing the GPIB analyzer, 3-1 participating in GPIB activity, 3-2
instrument drivers, C-1 phone technical support, C-1
printing captured data, 3-9
professional services, C-1
K programming examples, C-1
KnowledgeBase, C-1
R
L reloading capture/trigger settings, 3-6
Load Settings, 2-3
S
M Save Settings As, 2-3
main window, 2-2 saving capture/trigger settings, 3-6
Markers & Statistics, 2-11 saving captured data, 3-9
mnemonics, B-1 search capability, 2-13
mnemonics column service request problem example, 5-4
reading, 3-8 settings configuration, 2-4
monitoring GPIB activity, 3-2 Settings dialog box, exiting, 2-7
settings, configuring, 3-3
slow communication example, 5-1
N software drivers, C-1
National Instruments starting data capture, 3-1
customer education, C-1 starting the GPIB analyzer, 3-1
professional services, C-1 stopping data capture, 3-1
system integration services, C-1 support
technical support, C-1 technical, C-1
worldwide offices, C-1 system integration services, C-1
New Capture Display, 2-2
new data, capturing and viewing, 4-1
with a trigger condition, 4-4 T
nonintrusive capture, 3-4 technical support, C-1
telephone technical support, C-1
timeout error during a read example, 5-10
O timestamp column
online help, 1-1 reading, 3-7
online technical support, C-1 training
Open Capture Display, 2-2 customer, C-1
overflow errors, avoiding, 3-4 Trigger Condition configuration, 2-6
trigger settings W
configuring, 2-6, 3-4
Web
saving and reloading, 3-6
professional services, C-1
troubleshooting resources, C-1
technical support, C-1
tutorial
Windows menu, 2-3
capturing and viewing new data, 4-1
worldwide technical support, C-1
capturing and viewing new data with a
trigger condition, 4-4
printing and exporting a capture file, 4-12
searching for data in a capture display, 4-7
showing statistics for captured data, 4-10
V
viewing new data, 4-1
with a trigger condition, 4-4
viewing previously captured data, 3-3