Page 3
Limited Warranty The GPIB-1014P is warranted against defects in materials and workmanship for a period of two years from the date of shipment, as evidenced by receipts or other documentation. National Instruments will, at its option, repair or replace equipment that proves to be defective during the warranty period. This warranty includes parts and labor.
Page 4
FCC/DOC Radio Frequency Interference Compliance This equipment generates and uses radio frequency energy and, if not installed and used in strict accordance with the instructions in this manual, may cause interference to radio and television reception. This equipment has been tested and found to comply with the following two regulatory agencies: Federal Communications Commission This device complies with Part 15 of the Federal Communications Commission (FCC) Rules for a Class A digital...
Page 5
Preface The GPIB-1014P is a single-height circuit board which interfaces the VMEbus to the IEEE-488 General Purpose Interface Bus (GPIB). The GPIB-1014P provides a means to implement VMEbus test and measurement systems with standard interconnecting cables. Organization of the Manual This manual describes the mechanical and electrical aspects of the GPIB-1014P and contains information concerning its operation and programming.
VMEbus Slave-Data ..................2-3 Interrupter ......................2-4 VMEbus Modules Not Provided ............... 2-5 Diagnostic Aids ....................2-5 Data Transfer Features ....................2-5 GPIB-1014P Functional Description ................2-5 Section Three Configuration and Installation ..................3-1 Configuration ........................ 3-1 Access Mode ..................... 3-3 VMEbus Base Address ..................
Page 9
Going from Standby to Active Controller ............5-4 Going from Active to Idle Controller ............... 5-4 The GPIB-1014P as GPIB Talker and Listener ............5-5 Programmed Implementation of Talker and Listener ........5-5 Addressed Implementation of the Talker and Listener ........5-5 Address Mode 1 ..................
Page 10
Timing Control Logic ....................6-3 Interrupter Logic ......................6-3 GPIB Interface ......................6-4 Test and Troubleshooting ....................6-5 Section Seven GPIB-1014P Diagnostic and Troubleshooting Test Procedures ..... 7-1 Interpreting Test Procedures ..................7-1 GPIB-1014P Hardware Installation Tests ..............7-2 Appendix A Specifications ........................
Section One General Information The GPIB-1014P is an IEEE-488 interface for the VMEbus. This interface permits IEEE-488 compatible engineering, scientific, or medical instruments to be controlled from a VMEbus-based computer. The GPIB-1014P has the following features: Complete IEEE-488 Talker/Listener/Controller (TLC) capability using the NEC µPD7210 •...
Unpacking Follow these steps when unpacking your GPIB-1014P: 1. Your GPIB-1014P board is shipped packaged in an antistatic plastic bag to prevent electrostatic damage to the board. Several components on the board can be damaged by electrostatic discharge. To avoid such damage in handling the board, touch the plastic bag to a metal part of your VMEbus computer chassis before removing the board from the bag.
The GPIB-1014P measures 160 by 100 mm and is supplied with a standard 24-pin GPIB connector mounted on the front panel. The card is available with both single- and double-height metal front panels (.8 in. width). A DIN 41612 96-pin connector connects the GPIB-1014P to the VMEbus backplane.
Table 2-3 later in this section summarizes the capabilities of these modules. VMEbus Slave-Addressing The GPIB-1014P occupies 16 bytes of consecutive memory addresses located in the A16 (short) Input/Output (I/O) space. These addresses are used to access the GPIB Talker/Listener/Controller (TLC).
8 bits VMEbus Slave-Data As discussed previously, the GPIB-1014P can function as a VMEbus slave, decoding memory addresses and commands from a VMEbus master. It is designed to accommodate address pipelining as well as Address Only (ADO) cycles. All data is transferred to and from the VMEbus with lines D00 through D07.
Upon seeing DS0* high, the interrupter releases the data bus and the interrupt request line. This implies that the GPIB-1014P interrupter is a Release On Acknowledge (ROAK) interrupter. Note: Even though the interrupt request line is no longer driven, the TLC Interrupt (INT) line remains asserted until it is cleared in the interrupt service routine by reading the appropriate status register (ISR1 or ISR2).
Section Two General Description VMEbus Modules Not Provided Because the GPIB-1014P is not designed to be VMEbus System Controller, it does not have the following modules: • Master • Bus Timer • Arbiter • Interrupt Handler • IACK Daisy Chain Driver •...
General Description Section Two Figure 2-1 and Figure 2-2 show typical applications for the GPIB-1014P. In Figure 2-2, the GPIB-1014P is used to interface an assortment of test instruments to a VMEbus computer system, which then functions as an intelligent System Controller. This is the traditional role of the GPIB.
Page 22
AM5-AM0 A15-A01 A03-A01 Bus Address LWORD* Decoding DSO* AS*, IACK* 75160A Transceiver WRITE* Timing and DI08*- µPD7210 Data DI01* DTACK* Direction 75162A DS1* Control Transceiver SRQ*, ATN* IACKIN* EOI*, DAV* Interrupt IACKOUT* NRFD*, NDAC* Logic IFC*, REN* IRQ1*- IRQ7* System Data Bus Controller Transceivers...
Page 23
Monitors the VMEbus utility signals to generate the 8 MHz clock used by the TLC and to detect System Reset. • Timing State Machine Controls the timing of accesses to the GPIB-1014P from the VMEbus. • Interrupter Implements the correct VMEbus priority interrupt protocol, allowing the GPIB-1014P to request and respond to an interrupt acknowledge cycle.
General Description Section Two Table 2-3 lists the capabilities of the GPIB-1014P in terms of the IEEE-488 standard codes. Table 2-3. GPIB-1014P IEEE-488 Interface Capabilities Capability Code Description Complete Source Handshake capability Complete Acceptor Handshake capability DAC and RFD Holdoff on certain events...
Page 25
Listener or Extended Listener. It can be placed in a Listen Only mode, and it is unaddressed to listen when it receives its talk address. The GPIB-1014P has full capabilities for requesting service from another Controller. It can be placed in local mode, but the interpretation of remote versus local mode is software-dependent.
Page 26
General Description Section Two capability, but the interpretation is software dependent. All Controller functions as specified by the IEEE-488 standard are included in the GPIB-1014P. These include the capability to: • Be System Controller • Initialize the interface • Send Remote Enable •...
This section describes the configuration and installation of the GPIB-1014P. Configuration Before installing the GPIB-1014P in the VMEbus backplane, the following options must be configured with hardware jumpers or switches that are located on the GPIB-1014P interface board: • Access Mode (W2) •...
3-2a. To configure the board for non-privileged access, place the jumper on the side labeled NP as shown in Figure 3-2b. The default setting for the GPIB-1014P is for non-privileged access. In the Supervisor (privileged) mode, the GPIB-1014P only responds to Address Modifier (AM) code 2D.
Configuration and Installation VMEbus Interrupt Configuration The GPIB-1014P contains circuitry that permits it to request service by driving one of the VMEbus interrupt request lines. The GPIB-1014P responds to an interrupt acknowledge cycle of correct priority by providing an 8-bit vector (status byte) that is used to locate the appropriate interrupt service routine.
Place the jumper on the side labeled ISO to leave the GPIB cable shield isolated. Select one configuration depending on whether or not the GPIB-1014P is the GPIB System Controller and whether or not the GPIB cable shield is grounded elsewhere. Figure 3-7 shows the two possible configurations.
Configuration and Installation Installation The GPIB-1014P is a single-height board that interfaces to the VMEbus P1 and is available with either a single- or double-height metal front cover plate. The following paragraphs describe the GPIB-1014P interface to the VMEbus backplane and to the IEEE-488 bus.
Optional cables are available to connect the GPIB-1014P to other GPIB devices. Connect the cable to the GPIB-1014P at the standard GPIB connector labeled J1 at the top of the interface board. (The GPIB connector protrudes through the metal front cover plate.)
Register Map The register map for the GPIB-1014P is shown in Table 4-1. This table gives the register name, the register address, the type of the register, and the size of the register in bits. Table 4-1. GPIB-1014P Register Map...
All program registers on the GPIB-1014P are 8-bit registers. Register Description Format The remainder of this section discusses each of the GPIB-1014P registers in the order shown in Table 4-1. Each register group is introduced, followed by a detailed bit description of each register.
All are located within the NEC µPD7210 Talker/Listener/Controller (TLC) integrated circuit. Each of the 16 interface registers is addressed relative to the GPIB-1014P VMEbus base address which is set with DIP switches (refer to Base Address in Section Three).
Page 69
Holdoff on RFD or DAC. 0 0 1 0 0 Trigger Note: Trigger cannot be used with the GPIB-1014P. The Trigger command generates a high pulse on the TRIG pin (T/R3 pin when TRM1=0) of the TLC. The Trigger command performs the same function as if the DET (Device Trigger) bit (ISR1[5]r) were set.
Page 72
These commands generate the local message request system control (rsc) and set Interface Clear (IFC) to the value of COM3. These commands should only be issued if the GPIB-1014P is the System Controller (SC). In order to meet the IEEE-488 requirements, you must not issue for at least 100 µsec.
Page 75
Unconfigures PPR 0 1 1 0 0 0 0 0 0 0 0 0 0 is written to the PPR. GPIB-1014P participates in a Parallel Poll, asserting the DIO1 line if ist is 0. Otherwise, the GPIB-1014P does not participate.
The INV bit affects the polarity of the TLC INT pin. Setting INV causes the polarity of the Interrupt (INT) pin on the TLC to be active low. As implemented on the GPIB-1014P, configuring the INT pin to active low results in interrupt request errors. Consequently, INV should always be clear and should never be set.
Programming Considerations This section explains important considerations for programming the GPIB-1014P. Initialization On power-up (pon), the VMEbus system typically issues a system reset (SYSRESET*) that drives the GPIB-1014P RESET* signal active and initializes the following circuitry: • Timing State Machine •...
8.Execute the desired TLC auxiliary commands. The GPIB-1014P as GPIB Controller The GPIB-1014P Controller function is generally in one of two modes: idle or in charge. When in charge, the Controller function is either active (asserting ATN) or standby (not asserting ATN). The following paragraphs discuss the various transitions between these two modes.
Section Five Programming Considerations Another Active Controller passes control to the GPIB-1014P by sending the TLC GPIB talk address (MTA) followed by the GPIB Take Control (TCT) message. The TLC, upon receiving these two messages (MTA and TCT), automatically becomes CIC when ATN is dropped. The exact sequence of events is as follows: 1.
In Cases 2 and 3, the END IE bit in IMR1 can also be set to indicate to the program that the TLC (functioning as a GPIB Listener) has received its last byte. In all cases, a CO status indicates that the GPIB-1014P is now Active Controller. GPIB-1014P User Manual...
3. As soon as the TCT command message is accepted by all devices on the GPIB, the TLC automatically unasserts ATN and the new Controller asserts ATN. The GPIB-1014P as GPIB Talker and Listener The TLC can be either GPIB Talker or Listener, but not both simultaneously. Either function is deactivated automatically if the other is activated.
To send data, wait until the GPIB-1014P has been programmed or addressed to talk and the CDOR is empty. When this occurs, the DO bit in the ISR1 is set, indicating that it is safe to write a byte to the CDOR.
Interrupts The interrupt circuitry of the GPIB-1014P allows the board to interrupt the CPU to request service. Prior to use, the following three characteristics of the interrupter must be set (see Interrupt Request Line Selection in Section Three for details): •...
Responding To a Parallel Poll Before the GPIB-1014P can be polled by the CIC, the TLC must be configured either locally by your program at initialization time or remotely by the CIC. Configuration involves the following: •...
During interrupter Status/ID cycles or read cycles to the GPIB-1014P, the F245 is directed to allow the GPIB-1014P to drive the data bus. During write cycles, the direction of the F245 is reversed to allow the Talker, Listener, Controller (TLC) registers to receive data from the VME data bus. The F245 transceiver is enabled when either the EV or the STB signal is high.
The clocked output signal is labeled MCYC. If MCYC is false, the GPIB-1014P is prevented from taking any action until a new address cycle begins. If MCYC is true, the GPIB-1014P is able to respond if DS0* goes low. DS1* is not monitored for the purpose of distinguishing 16-bit transfers from 8-bit transfers, so the GPIB-1014P responds to BYTE (0-1) or BYTE (2-3) accesses.
GPIB-1014P), the GPIB-1014P waits for DTACK* to be released and for DS0* to be asserted. The GPIB-1014P then asserts STRT after delaying a minimum of 85 nsec in order to meet the TLC address set-up time.
(DEN*=1), IDTACK* is high, and DS1* is released. If the address lines A01 through A03 do not match the indicated priority of the GPIB-1014P, the Q* output of the flip-flop is latched high, indicating that IACKOUT* is to be asserted. After IACKIN and the delayed AS are received high, the VMEbus signal IACKOUT* is driven low.
Page 100
T/R3 is high when the three-state driver mode is active and low when the open collector mode is active. When the GPIB-1014P is parallel polled, the transceiver switches to open collector mode. SC is set whenever the System Controller Select logic senses that the TLC has received the Set IFC auxiliary command;...
Section Six Test and Troubleshooting The GPIB-1014P is designed to aid acceptance testing and troubleshooting of either hardware failures or software bugs. The hardware provides several features that enable stand-alone testing. The NDAC* and DIO1* bits can be used to determine if the output signals of the TLC, the 75160A, and the 75162A are functioning properly.
The tests should be performed without connecting the GPIB-1014P to another GPIB device. All GPIB cables should be removed. If the GPIB-1014P does not perform as described in the test procedures, users are advised to carefully perform the following steps.
• Pass GPIB control to another device (PASSC). Assumptions regarding the state of the GPIB-1014P appear at the beginning of each routine and must be adhered to for proper, error-free operation. The following characteristics of the code must be considered: •...
Page 118
CSEND (Command Send) (Write Commands) PASSC (Pass Control) ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; 68000 Code BASE 0xFF1000 | Base address of GPIB-1014P interface BASE + 0x1 | Data In Register (read) CDOR BASE + 0x1 | Control/Data Out Register (write) ISR1 BASE + 0x3...
Page 123
| * * * * * * * * * * * * * * * * * * * * * * | Summary: - Initialize the interface function of other GPIB devices | Assumptions on entry: - GPIB-1014P has been initialized | Actions: - Assert GPIB IFC - Wait at least 100 microseconds - Unassert IFC...
Page 124
- Set or clear GPIB Remote Enable signal | Assumptions on entry: - User specified sre is non-zero if REN is to be asserted and is zero if REN is to be unasserted - GPIB-1014P is System Controller and Active Controller | Actions: - Check sre flag.
Page 125
| * RECEIVE - RCV* | * * * * * * * * * * * * * * * | Summary: - Called by READ to receive data if GPIB-1014P is Controller-In-Charge - Called directly from main program to receive data if...
Page 126
| Save d2 movb #FH,AUXMR.L | Release any handshake holdoff in progress b cic.L | Is GPIB-1014P Controller-In-Charge? RCV1 movb #AUXRA+0202,AUXMR.L | Yes--Set HLDE and BIN in AUXRA RCV2 RCV1: movb #AUXRA,AUXMR.L | No--Clear any HLDE or HLDA in effect...
Page 127
| Summary: - Called to read device-dependent (data) messages when the GPIB-1014P is Controller-In-Charge (RCV is called when the GPIB-1014P is Idle Controller) | Assumptions on entry: - GPIB-1014P is Controller-In-Charge - The Talker address is placed in first location of...
Page 128
#UNL,cmdbuf.L+1 addw #2,cmdct.L | Command routine will address the Talker movb #LTN,AUXMR.L | Program GPIB-1014P to be a Listener movb #GTS,AUXMR.L | so it can take control synchronously | later; then go to standby and drop ATN movw #datct,d0...
Page 129
| - The GPIB-1014P is Standby or Idle Controller | - GPIB-1014P is or will be addressed to talk | - If the GPIB-1014P is Idle Controller, the current CIC will go to standby - The d0 register contains the byte count...
Page 131
| Actions: - Set up cmdbuf and cmdct and call CMD to address the GPIB-1014P as Talker, to address the Listener, and to unaddress all other devices - Go to standby and unassert ATN - Transfer the contents of datct to the d0 register...
Page 133
| Summary: - Called by CMD to send interface command messages | Assumptions on entry: - The GPIB-1014P is Active Controller - The d0 register contains the number of bytes to send - The a0 register contains the address oc cmdbuf...
Page 134
| Summary: - Send GPIB interface or command messages | Assumptions on entry: - The GPIB-1014P is Controller-In-Charge - The commands to be sent are in cmdbuf - The variable cmdct contains the number of commands to be sent, which must be less than 256...
Page 135
- The primary GPIB address of the new controller is placed in tctadr | Actions: - Send TCA command to take control in case the GPIB-1014P is at standby - Set up the command buffer and command count - Call CMD to send the command bytes...
Page 155
Technical Support Form ___________________________________________________ Photocopy this form and update it each time you make changes to your software or hardware, and use the completed copy of this form as a reference for your current configuration. Completing this form accurately before contacting National Instruments for technical support helps our applications engineers answer your questions more efficiently.
Page 156
GPIB-1014P Hardware and Software Configuration Form Record the settings and revisions of your hardware and software on the line to the right of each item. Update this form each time you revise your software or hardware configuration, and use this form as a reference for your current configuration.
Page 157
• Type of other boards installed and their respective hardware settings: Base I/O Interrupt Board Type Address Level Channel...
Documentation Comment Form National Instruments encourages you to comment on the documentation supplied with our products. This information helps us provide quality products to meet your needs. Title: GPIB-1014P User Manual Edition Date: June 1994 Part Number: 370944A-01 Please comment on the completeness, clarity, and organization of the manual.
Page 160
BIN (Binary Bit), 4-38 bus signals. See VMEbus. cable shield grounding, GPIB, 3-8 cabling, 3-10 to 3-11 capability codes for GPIB-1014P, 2-10 to 2-12 CDO[7-0] (Command/Data Out Bits 7 through 0), 4-7 CDOR. See Command/Data Out Register (CDOR). Chip Reset command...
Page 170
7-2 to 7-3 interpreting test procedures, 7-1 overview, 6-5, 7-1 verification of GPIB-1014P before installation, 3-10 U (Parallel Poll Unconfigure Bit), 4-36 UNL (Unlisten) command, 4-26 unpacking the GPIB-1014P, 1-3 to 1-4 UNT (Untalk) command, 4-26...