Table of contents
-
NI-488.2 Help
- Related Documentation
- Using Help
- Getting Started with GPIB
- Learning More about GPIB
- NI-488.2 Utilities
-
Application Development with NI-488.2
- Choosing a Development Environment
- Language-Specific Programming Instructions
-
General Programming Considerations
- Communicating with Your Instrument
-
Using the NI-488.2 API
- Choosing a Method to Access the NI-488.2 Driver
- Differences Between the GPIB32 API and NI4882 API
- Choosing How to Use the NI-488.2 API
- Communicating with a Single GPIB Instrument
- Communicating with Multiple Instruments and/or Multiple Interfaces
- Header Files
- Examples
- Programming Model for Applications that Communicate with a Single GPIB Instrument
- Programming Model for Applications that Communicate with Multiple Instruments and/or Multiple Interfaces
- Checking Global Status After Each NI-488.2 Call
- Advanced Programming Techniques
- Tools for Developing Your Application
-
Troubleshooting Problems
- Troubleshooting Tools
-
Troubleshooting EDVR Error Conditions
- Ibcnt() Set to 0xE014002C (-535560148)
- Ibcnt() Set to 0xE0140025 (-535560155)
- Ibcnt() Set to 0xE0140035 (-535560139)
- Ibcnt() Set to 0xE1080080 (-519569280) or 0xE1080081 (-519569279)
- Ibcnt() Set to 0xE00A0047 (-536215481)
- Ibcnt() Set to 0xE1030043 (-519897021)
- Ibcnt() Set to 0xE1060075 (-519700363)
- Ibcnt() Set to 0xE1060078 (-519700360)
- Why Can't I Communicate with My GPIB Instrument?
- Why Can't I Find My GPIB-ENET/100?
-
Debugging an NI-488.2 Application
- Determine Whether an NI-488.2 Call Failed
-
Checking Global Status Functions to Debug Your Application
- Checking Global Status After Each NI-488.2 Call
-
Ibsta() or ibsta Status Bit Values
- ATN Status Condition
- CIC Status Condition
- CMPL Status Condition
- DCAS Status Condition
- DTAS Status Condition
- END Status Condition
- ERR Status Condition
- LACS Status Condition
- LOK Status Condition
- REM Status Condition
- RQS Status Condition
- SRQI Status Condition
- TACS Status Condition
- TIMO Status Condition
- Debugging Existing Applications
- Solving Errors
-
How to
- Add a New GPIB Interface
- Remove a GPIB Interface
- Scan for GPIB Instruments
- View GPIB Instrument Information
- Communicate with a GPIB Instrument
- Set Network Settings for the GPIB-ENET/100
- Use Static IP Address Settings Suggested for the GPIB-ENET/100
- View NI-488.2 Software Version
- Enable/Disable NI-488.2 DOS Support
- Require Administrator Privileges
- Access Additional Help and Resources for GPIB
-
Frequently Asked Questions
- How do I get error information about failed NI-488 calls?
- How do I communicate with my instrument?
- How do I change a GPIB device template?
- How can I NULL terminate an ASCII response from my instrument?
- Are interrupts required for the NI-488.2 software?
- Is DMA required for the NI-488.2 software?
- Is my instrument 488.1 or 488.2 compliant?
- How can I determine which type of GPIB hardware I have installed?
- How do I use an NI-488.2 application interface?
-
Function Reference
-
Traditional NI-488.2 Calls
- Board-Level
- Device-Level
- IBASK
- IBCAC
- IBCLR
- IBCMD
- IBCMDA
- IBCONFIG
- IBDEV
- IBDMA
- IBEOS
- IBEOT
- IBFIND
- IBGTS
- IBIST
- IBLCK
- IBLINES
- IBLN
- IBLOC
- IBNOTIFY
- IBONL
- IBPAD
- IBPCT
- IBPPC
- IBRD
- IBRDA
- IBRDF
- IBRPP
- IBRSC
- IBRSP
- IBRSV
- IBSAD
- IBSIC
- IBSRE
- IBSTOP
- IBTMO
- IBTRG
- IBWAIT
- IBWRT
- IBWRTA
- IBWRTF
- Multi-Device NI-488.2 Calls
- Supplemental Calls for Multithreaded NI-488.2 Applications
-
Traditional NI-488.2 Calls
- IEEE 488 Command Messages
- Glossary
- Important Information
- Technical Support and Professional Services