Supplement to the NI-488M Software Reference Manual for AIX

Similar documents
Using NI-488.2M Software with 32-Bit Delphi Applications

NI-488.2M TM Software for Windows 95 Quick Reference Card

Model KPCI-488LPA GPIB Controller Interface Card and Model KUSB-488B USB to GPIB Converter

Quick Reference Card. NI-488.2M TM Software for Win32. Status Word Conditions (ibsta) Error Codes (iberr) NATIONAL INSTRUMENTS

ADL-GPIB. for PC Compatibles. Function Reference Manual

ESP-488 Software Reference Manual for LynxOS and the AT-GPIB

gpib-ctypes Documentation

NI-488 and NI Subroutines for FORTRAN. November 1993 Edition Part Number

Using Your NI Software with NEC Windows

NI-488 and NI Subroutines for NKR BASIC. August 1992 Edition Part Number

NI-488DDK Software Reference Manual

GPIB Library Software User's Guide

NI-488M. Software Reference Manual. National Instruments IEEE 488 Multitasking UNIX Device Driver. July 1994 Edition Part Number

Programming with NI Software

NI TM. Function Reference Manual for DOS/Windows. August 1996 Edition Part Number A-01

Using Measurement Studio GPIB to Accelerate Development with Visual Basic

ESP-488 Software Reference Manual for the GPIB-ENET

GPIB. NI-488DDK Software Reference Manual. January 2003 Edition Part Number B-01

NI-488.2TM. NI User Manual. NI User Manual. January N-01

NI-488.2TM. NI User Manual. NI User Manual. June W-01

PROLOGIX GPIB-ETHERNET CONTROLLER USER MANUAL VERSION September 14, 2009 PROLOGIX.BIZ

User s Manual. High Speed & Function IEEE I/F Board for PCI GP-IB(PCI)F. High Speed IEEE I/F Board for PCI GP-IB(PCI)FL

Installing Your PCI-GPIB, PXI-GPIB, or PMC-GPIB and NI for Solaris

The GPIB Interface. Last modified Week 4 - part 1. What we have here is a failure to communicate - Cool Hand Luke

Using Your NI-488 and NI Subroutines for Visual Basic for Windows

GP-IB(PCI) GP-IB(PCI)L

TABLE OF FIGURES... II A - DISCUSSION...1

NI NI User Manual for Windows

PC-HELPER. High Speed IEEE I/F Micro Converter for USB2.0 GP-IB(USB)FL. User s Manual CONTEC CO.,LTD.

Getting Started with Your GPIB-PCII/IIA and the NI Software for MS-DOS

GPIB Analyzer Help Contents Index Search

5 The GP Interface Bus

Error num: 1 Meaning: Not owner Error num: 2 Meaning: No such file or directory Error num: 3 Meaning: No such process Error num: 4 Meaning:

Orifice Flow Meter

Software Architecture Document: Addendum

VISA Events in NI-VISA

Dynamic Memory: Alignment and Fragmentation

NI NI User Manual. NI User Manual. March 2004 Edition Part Number B-01

How to communicate with instruments that support GPIB. Gianfranco Miele, Ph.D

DDA-RCM-E Rev D ISSUED: December 1999 $²

This resource describes how to program the myrio in C to perform timer interrupts.

Interface system Probus V

Using Measurement & Automation Explorer (MAX) with VXI

Using MATLAB with KEITHLEY Instrument Devices through GPIB Page 1 of 6

SERIES PS300 HIGH VOLTAGE POWER SUPPLIES MODEL PS310 MODEL PS325 MODEL PS350

4) In response to the the 8259A sets the highest priority ISR, bit and reset the corresponding IRR bit. The 8259A also places

Measure GPIB User Manual

MultiCom. for LabVIEW for Windows. Windows 95/98/NT Edition. Copyright , Viewpoint Software Solutions, Inc. All Rights Reserved

TPMC901-SW-95. QNX4 - Neutrino Device Driver. User Manual. The Embedded I/O Company. 6/4/2 Channel Extended CAN-Bus PMC

ines-ieee488.2 igpib Device Driver Software Manual 1998 ines GmbH

LabVIEW Real-Time Module for Mac OS X User Manual Addendum

National Instruments Model GPIB-MAC User Manual Part Number

TPMC860-SW-82. Linux Device Driver. 4 Channel Isolated Serial Interface RS232 Version 1.4.x. User Manual. Issue 1.4.

QC External Devices (EXD)

Assertions, pre/postconditions

Contents. Error Message Descriptions... 7

Fred Meyer EDI997 data samples

VARIABLES AND CONSTANTS

Instruction Set Architecture of MIPS Processor

Outline. Overview. Linux-specific, since kernel 2.6.0

The Data timeout plugin PRINTED MANUAL

Asynchronous Events on Linux

NI-CAN 2.6 Error/Warning Codes

IMAQ Vision Deployment Engine Note to Users

K2289: Using advanced tcpdump filters

CMSC 313 COMPUTER ORGANIZATION & ASSEMBLY LANGUAGE PROGRAMMING LECTURE 09, SPRING 2013

Lesson 6 Instrument Control You Will Learn:

Lesson 5 More on Instrument Control You Will Review: Instrument Control Overview. GPIB Communication. GPIB Hardware Specifications

PCI Advance Technologies; Automate the World. IEEE488 GPIB Interface Card User s Manual. Manual Rev Revision Date: April 14, 2005

11/3/71 SYS BREAK (II)

CARRIER-SW-82. Linux Device Driver. IPAC Carrier Version 2.2.x. User Manual. Issue November 2017

Up to three (3) RIO-RS232 modules may be attached to one RIO-PBA Profibus adapter.

Foundation Fieldbus Hardware and NI-FBUS Software for Windows 2000/XP

GPIB ASIC Reference Manual Errata

CIS 110 Introduction to Computer Programming. February 29, 2012 Midterm

Remote Control Manual

ICS ICS ELECTRONICS division of Systems West Inc.

BOONTON ELECTRONICS A subsidiary of Noise/Com a Wireless Telecom Group Company

System Software Assignment 1 Runtime Support for Procedures

CS159. Nathan Sprague

User Manual for Application Software Type 7300

The TCP redirecting plugin PRINTED MANUAL

Overview. Exercise 0: Implementing a Client. Setup and Preparation

Parsing Instrument Data in Visual Basic

TPMC821-SW-42. VxWorks Device Driver. User Manual. The Embedded I/O Company. INTERBUS Master G4 PMC. Version 1.4. Issue 1.

X ITRON T ECHNOLOGIES 6010 O PERATING I NSTRUCTIONS

TIP675-SW-82. Linux Device Driver. 48 TTL I/O Lines with Interrupts Version 1.2.x. User Manual. Issue November 2013

MultiCom. for LabVIEW for Windows. Windows 95/Windows NT Edition. Copyright , Viewpoint Software Solutions, Inc. All Rights Reserved

System II Device Driver & Controller

Alstom Redundant Ethernet Driver Help Kepware Technologies

APPLICATION BULLETIN ICS ICS. ELECTRONICS division of Systems West Inc. VXI-11 TUTORIAL and RPC Programming Guide AB80-11 INTRODUCTION

Sequential Search (Searching Supplement: 1-2)

CSE410 Operating Systems Spring 2018 Project 1: Introduction to Unix/Linux Signals

Windows architecture. user. mode. Env. subsystems. Executive. Device drivers Kernel. kernel. mode HAL. Hardware. Process B. Process C.

VXI-11 and HP E2050A

Programming with MPI

APPENDIX A ACL ELITE/ELITE PRO. Host Communication Protocol

Modbus ASCII Serial Device Driver Help 2009 Kepware Technologies

PROGRAMMABLE AC POWER SOURCE

EM210 COMMUNICATION PROTOCOL. Version 3 Revision 1

Transcription:

Supplement to the NI-488M Software Reference Manual for AIX This supplement contains a discussion of the NI-488 function ibdev and the AIX-specific functions ibhwdiag and ibpost that are not documented in the standard NI-488M Software Reference Manual. The purpose, syntax, and C language programming examples for each function are given. The functions ibdev and ibpost are part of the standard AIX GPIB language interface. The ibhwdiag function is available as a separate linkable object file, which is not included with the AIX driver software. For descriptions of all other NI-488 functions, please refer to the NI-488M Software Reference Manual. NI-488 and NI-488M are trademarks of National Instruments Corporation. Product and company names are trademarks or trade names of their respective companies. 321319A-01 Copyright 1996 National Instruments Corp. All rights reserved. June 1996

IBDEV (3) device only IBDEV (3) ibdev - open and initialize an unused device when the device name is unknown #include <sys/ugpib.h> ud = int ibdev (int boardindex, int pad, int sad, int tmo, int eot, int eos) boardindex is an index from 0 to [(number of boards) - 1] of the access board that the device descriptor must be associated with. The arguments pad, sad, tmo, eot, and eos dynamically set the software configuration for the NI-488 I/O functions. These arguments configure the primary address, secondary address, I/O timeout, asserting EOI on last byte of data sourced, and the End-Of-String mode and byte, respectively. (Refer to the ibpad, ibsad, ibtmo, ibeot, and ibeos function descriptions for more information on each argument.) The device descriptor is returned in the variable ud. The ibdev command selects an unopened device, opens it, and initializes it. You can use this function in place of ibfind. ibdev returns a device descriptor of the first unopened user-configurable device that it finds. For this reason, it is very important to use ibdev only after all of your ibfind calls have been made. This is the only way to ensure that ibdev does not use a device that you plan to use via an ibfind call. The ibdev function performs the equivalent of the ibonl function to open the device. Note: The device descriptor of the NI-488M driver can remain open across invocations of an application, so be sure to return the device descriptor to the pool of available devices by calling ibonl with v=0 when you are finished using the device. If you do not, that device will not be available for the next ibdev call. 2

If the ibdev call fails, a negative number is returned in place of the device descriptor. There are two distinct errors that can occur with the ibdev call: If no device is available or the specified board index refers to a non-existent board, it returns the EDVR or ENEB error. If one of the last five parameters is an illegal value, it returns with a good board descriptor and the EARG error. Example ibdev opens an available device and assigns it to access gpib0 (board = 0) with a primary address of 6 (pad = 6), a secondary address of 0x67 (sad = 0x67), a timeout of 10 ms (tmo = 7), the END message enabled (eot = 1) and the EOS mode disabled (eos = 0). if ((ud = ibdev(0,6,0x67,7,1,0)) < 0) { /* Handle GPIB error here */ if (iberr == EDVR) { /* bad boardindex or no devices * available. */ } else if (iberr == EARG) { /* The call succeeded, but at least one * of pad, sad, tmo, eos, eot is incorrect. */ } ibfind (3), ibpad (3), ibsad (3), ibtmo (3), ibeot (3), and ibeos (3) in the NI-488M Software Reference Manual 3

IBHWDIAG (3) board only IBHWDIAG (3) ibhwdiag - perform hardware diagnostic tests on the specified board ibhwdiag(int boardnum, int cable) boardnum is an index from 0 to [(number of boards) - 1]. cable should be set to zero if no cable is attached and all tests can be performed, or 1 if a cable is attached. If a cable is attached, only the tests that can work with a cable attached to the MC- GPIB are performed. ibhwdiag performs a series of tests on the GPIB hardware, where each test is uniquely identified by a number. The ibhwdiag function performs these hardware tests by accessing the GPIB driver. The ibhwdiag function returns -1 if there is a communication problem with the GPIB driver, and -2 if the board is not installed. ibhwdiag returns 0 if all the tests completed successfully. If one of the hardware tests failed, the function returns a value greater than 0 with the return value corresponding to the test number that failed. Examples 1. Run hardware diagnostics on gpib0 with cable attached. ibhwdiag(0,1); 2. Run hardware diagnostics on gpib2 with no cables attached. ibhwdiag(2,0); The ibdiag section in the Getting Started manual 4

IBPOST (3) board only IBPOST (3) ibpost - request notification of the occurrence of an SRQ event #include <sys/ugpib.h> int ibpost(int ud, int eventmask) ud designates a board descriptor, and eventmask specifies a mask bit you want to associate with an SRQ event. There is no defined mask value to represent the GPIB SRQ event. In applications that use ibpost, you must define your own mask value to represent an SRQ event. However, you need to make sure that the value you define does not coincide with the predefined mask values the system reserves to represent certain general events. Please refer to the system file sleep.h for a list of the mask values defined for general events. Like the NI-488 function ibsgnl, ibpost returns immediately, freeing the application program to perform other tasks. When an SRQ interrupt occurs, the driver issues an e_post with the SRQ eventmask as one of its parameters. This causes the kernel to set the SRQ mask bit. The only way the application can examine and clear this bit is with the e_wait kernel function. Therefore, when the process needs to check or wait for an occurrence of the SRQ interrupt, it has to execute an e_wait on the SRQ mask bit. Note: To use this function you must have access rights to use the kernel extensions from your application. Example Call ibpost with the SRQ event bit defined to be 0x2000000. ibpost(brd0, 0x2000000); The e_post and e_wait kernel function descriptions on the man pages 5