GPIB Device Returns Error ENEB, EBUS with Interactive Control Hardware: GPIB
Problem: I am unable to query my GPIB device without getting an interactive control error ENEB or EBUS? Solution: If you are receiving the ENEB error:The ENEB error means that the board index entered does not exist. Each GPIB board in your system is assigned an index usually starting with the number 0. For example, the first board in a system is usually referenced as GPIB0, the second is called GPIB1, and so on. See Measurement & Automation Explorer in Windows, Interactive Control on Mac and Linux, or Digital Unix on older Unix drivers to find out what GPIB boards are installed, and what their assigned board indexes are. ud0: ibdevNote: Make sure this matches up with your device that you are trying to query. If there is no device listed there then you will get a ENEB error shown as shown below:[8000] (err)If you are receiving the EBUS error:The EBUS error indicates that no devices are handshaking GPIB command signals. Most commonly, this is due to no cable being connected to the GPIB board, a bad cable, or devices not being powered up on the bus. Verify that GPIB target is powered on and connected. If it appears to be, power cycle the device and try to query it again.ud0: ibwrt "*IDN?"[8100] (err cmpl)Related Links: GPIB Support: GPIB Installation/Configuration Troubleshooter Product Manuals: NI-488.2 User Manual Attachments:
Report Date: 04/14/2005 Last Updated: 03/03/2008 Document ID: 3KDHENY3 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
