• There are no items in your cart

IEEE DRAFT 1226.4 : D2.0 DEC 95

Withdrawn

Withdrawn

A Withdrawn Standard is one, which is removed from sale, and its unique number can no longer be used. The Standard can be withdrawn and not replaced, or it can be withdrawn and replaced by a Standard with a different number.

A BROAD BASED ENVIRONMENT FOR TEST (ABBET) SOFTWARE INTERFACE FOR INSTRUMENT DRIVERS

Withdrawn date

07-23-2013

Published date

01-12-2013

1 Overview
    1.1 Scope
    1.2 Purpose
    1.3 Application
2 References
3 Definitions of Terms
4 Description
    4.1 Objectives
    4.2 Overview
         4.2.1 Instrument Driver Requirements
             4.2.1.1 Full-Feature Control
             4.2.1.2 Modularity and Hierarchy
             4.2.1.3 Consistency in Design and
                      Implementation
         4.2.2 Instrument Driver Architecture
             4.2.2.1 Instrument Driver External
                      Interface Model
             4.2.2.2 Functional Body
             4.2.2.3 Input/Output (I/O) Interface
             4.2.2.4 Subroutine Interface
             4.2.2.5 Programmatic Developer Interface
             4.2.2.6 Interactive Developer Interface
             4.2.2.7 Instrument Driver Internal Design
                      Model
    4.3 Relationship to ABBET Architecture
         4.3.1 Architecture Levels
         4.3.2 Application
         4.3.3 Extension Framework
         4.3.4 Foundation Framework
         4.3.5 Test resource Foundation Class
    4.4 Relationship to Reference Documents
5 Conformance
    5.1 Minimum Capabilities
    5.2 Subsets
    5.3 Extensions
    5.4 Approach for Implementation of Extensions
6 Specification
    6.1 Conventions
         6.1.1 Functional Body
         6.1.2 Error Handling
    6.2 Component Functions
         6.2.1 State Model
         6.2.2 Data Type Notation
         6.2.3 Completion Warning and Error Codes
         6.2.4 Initialize Function
         6.2.5 Configuration Functions
         6.2.6 Action/Status Functions
         6.2.7 Data Functions
         6.2.8 Utility Functions
         6.2.9 Close Function
         6.2.10 Application Functions
    6.3 Interactive Developer Interface
         6.3.1 Function Panel Layout
         6.3.2 Function Panel Help Information
                6.3.2.1 Instrument Driver Help
                6.3.2.2 Function Panel Help
                6.3.2.3 Control Help
                6.3.2.4 Return Help
Annex
A Instrument Driver Programmer Interface for Windows
    (informative)
    A.1 Introduction
    A.2 Compatible Application Development Environments
    A.3 Instrument Driver Function Prototypes
    A.4 Naming Conventions
    A.5 Data Types
    A.6 Parameter Conventions
    A.7 Language-specific Capabilities
    A.8 Header Files
    A.9 Bindings for the Required Functions
    B The Vpptype.h Header for the WIN Framework
         (informative)
    C The Vpptupe.bas Header File for the WIN
         Framework (informative)
    D Example Instrument Driver Header File
         (informative)
    E Example Visual BASIC Header File (informative)
    F IDL Bindings (Normative)
    G Bibliography (Informative)
    H Additional Definitions (informative)


Applies to the software interface for control of test resources in an ABBET system.

DocumentType
Draft
PublisherName
Institute of Electrical & Electronics Engineers
Status
Withdrawn

IEEE DRAFT 1226.3 : 1997 A BROAD BASED ENVIRONMENT FOR TEST (ABBET) SOFTWARE INTERFACE FOR RESOURCES MANAGEMENT

IEEE 488.1 : 2003 STANDARD FOR HIGHER PERFORMANCE PROTOCOL FOR THE STANDARD DIGITAL INTERFACE FOR PROGRAMMABLE INSTRUMENTATION
IEEE 488.2 : 1992 STANDARD CODES, FORMATS, PROTOCOLS, AND COMMON COMMANDS FOR USE WITH IEEE 488.1-1987, IEEE STANDARD DIGITAL INTERFACE FOR PROGRAMMABLE INSTRUMENTATION
ANSI INCITS 159 : 1989 "C" PROGRAMMING LANGUAGE

View more information
Sorry this product is not available in your region.

Access your standards online with a subscription

Features

  • Simple online access to standards, technical information and regulations.

  • Critical updates of standards and customisable alerts and notifications.

  • Multi-user online standards collection: secure, flexible and cost effective.