# cPCI/PCI-8554/R®

# Multi-functions

# Counter / Timer Card

# User’s Guide

©Copyright 1998\~2002 ADLINK Technology Inc,

All Rights Reserved.

Manual Rev. 1.02: July 31, 2002

Part No: 50-11130-100

The information in this document is subject to change without prior notice in order to improve reliability, design and function and does not represent a commitment on the part of the manufacturer.

In no event will the manufacturer be liable for direct, indirect, special, incidental, or consequential damages arising out of the use or inability to use the product or documentation, even if advised of the possibility of such damages.

This document contains proprietary information protected by copyright. All rights are reserved. No part of this manual may be reproduced by any mechanical, electronic, or other means in any form without prior written permission of the manufacturer.

# Trademarks

NuDAQ, DAQBench are registered trademarks of ADLINK Inc.,

Other product names mentioned herein are used for identification purposes only and may be trademarks and/or registered trademarks of their respective companies.

# Getting service from ADLINK

Customer Satisfaction is the most important priority for ADLINK Tech Inc. If you need any help or service, please contact us.

<table><tr><td colspan="4">ADLINK Technology Inc.</td></tr><tr><td>Web Site</td><td colspan="3">http://www.adlinktech.com</td></tr><tr><td>Sales &amp; Service</td><td colspan="3">Service@adlinktech.com</td></tr><tr><td rowspan="4">Technical Support</td><td>NuDAQ + USBDAQ</td><td colspan="2">nudaq@adlinktech.com</td></tr><tr><td>Automation</td><td colspan="2">automation@adlinktech.com</td></tr><tr><td>NuIPC</td><td colspan="2">nuipc@adlinktech.com</td></tr><tr><td>NuPRO / EBC</td><td colspan="2">nupro@adlinktech.com</td></tr><tr><td>TEL</td><td>+886-2-82265877</td><td>FAX</td><td>+886-2-82265717</td></tr><tr><td>Address</td><td colspan="3">9F, No. 166, Jian Yi Road, Chungho City, Taipei, 235 Taiwan.</td></tr></table>

Please email or FAX us of your detailed information for a prompt, satisfactory and constant service.

<table><tr><td colspan="4">Detailed Company Information</td></tr><tr><td>Company/Organization</td><td colspan="3"></td></tr><tr><td>Contact Person</td><td colspan="3"></td></tr><tr><td>E-mail Address</td><td colspan="3"></td></tr><tr><td>Address</td><td colspan="3"></td></tr><tr><td>Country</td><td colspan="3"></td></tr><tr><td>TEL</td><td></td><td>FAX</td><td></td></tr><tr><td>Web Site</td><td colspan="3"></td></tr><tr><td colspan="4">Questions</td></tr><tr><td>Product Model</td><td colspan="3"></td></tr><tr><td>Environment to Use</td><td colspan="3">OS:Computer Brand:M/B: CPU:Chipset: BIOS:Video Card:Network Interface Card:Other:</td></tr><tr><td>Detail Description</td><td colspan="3"></td></tr><tr><td>Suggestions to ADLINK</td><td colspan="3"></td></tr></table>

# Table of Contents

# Tables............ iii

# Figures ....... . iv

# How to Use This Guide....... ... v

# Chapter 1 Introduction ......

1.1 Features . 2
1.2 Applications . 3
1.3 Specifications .. 3
1.4 Software Supporting .. 5

1.4.1 Programming Library . 5
1.4.2 PCIS-LVIEW: LabVIEW® Driver .... 6
1.4.3 PCIS-VEE: HP-VEE Driver .. 6
1.4.4 DAQBenchTM: ActiveX Controls.. 6

# Chapter 2 Getting Started ...... . 7

2.1 What You Have ..
2.2 Unpacking..
2.3 PCB Layout of cPCI/PCI-8554/R. .8
2.4 Default Jumper Setting . .9
2.5 cPCI/PCI-8554/R Installation. .11

2.5.1 Hardware configuration.. .11

2.6 Device Installation for Windows Systems .. .12
2.7 Pin Assignment of Connector . .13
2.8 Clock System... .15
2.9 Counters Architecture. . 15

2.9.1 Independent Counters (Counter 1\~10) . ..17
2.9.2 Cascaded Counters .. .17
2.9.3 User Configurable Cascaded Counters .. ..18

2.10 Clock Source Configurations.. .19
2.11 Gate Control Configurations.. ..20
2.12 Counter Outputs... .20
2.13 Debounce System.. .21
2.14 Interrupt System.. . 22
2.15 Digital Input and Output . .23
2.16 12V and 5V Power Supply . .. 24

# Chapter 3 Registers ....... ... 25

3.1 PCI PnP Registers... .25
3.2 I/O Address Map.. .. 26
3.3 Timer/Counter Registers . .27
3.4 Timer / Counter Clock Mode Control .. ..27
3.5 Digital Input Register . . 28
3.6 Digital Output Register . .29

# Chapter 4 Signal Connections & Applications.................... 30

4.1 Connectors Pin Assignment . .. 30
4.2 Digital I/O Connection.. ..30
4.3 Timer/Counter Connection.. .31
4.4 Frequency Generator . ..32

4.4.1 To generate a 250 KHz Square Wave. .. . 32

4.4.2 To generate a 1 pulse/1 hour signal . . 33

4.5 Pulse Width Measurement.. .34
4.6 Frequency Measurement.. .. 35
4.7 Event Counter... .37
4.8 Dual Interrupt System.. ..38

# Chapter 5 C/C++ Library .......... .. 39

5.1 Libraries Installation.. ..39
5.2 Programming Guide . .. 40

5.2.1 Naming Convention .. ..40
5.2.2 Data Types .. ..40
5.3 \_8554\_Initial .. ..41
5.4 \_8554\_Write\_Counter . .. 42
5.5 \_8554\_Read\_Counter .. .. 43
5.6 \_8554\_Stop\_Counter . .. 44
5.7 \_8554\_Read\_Status.. .. 45
5.8 \_8554\_DO ... .. 46
5.9 \_8554\_DI.. ..47
5.10 \_8554\_SET\_cntCLK . .. 48
5.11 \_8554\_SET\_CK1.. ..49
5.12 \_8554\_SET\_DBCLK . ..50
5.13 \_8554\_Set\_INT\_Control .. .. 51
5.14 \_8554\_Get\_IRQ\_Status. . 52
5.15 \_8554\_INT\_Enable . .53
5.16 \_8554\_INT\_Disable .. . 54
5.17 \_8554\_CLR\_IRQ1 . ..54
5.18 \_8554\_CLR\_IRQ2 . .. 55

# Warranty Policy .......... .... 56

# Tables

Table 1. Default Jumper Settings on PCI-8554 . .. 10

Table 2. Extra Default Jumper Setting on cPCI-8554/R... 10

Table 3. Counters label relationship . . 15

Table 4. I/O Address Map of cPCI/PCI-8554/R . . 26

Table 5. Timer/Counter Registers... . 27

Table 6. Timer/Counter Clock Mode Control Register ... . 28

Table 7. Digital Input Register .. . 28

Table 8. Digital Output Register... . 29

Table 9. Data types and their ranges. . 40

# Figures

Figure 1: Functional Block diagram.. 2
Figure 2: PCB Layout of PCI-8554.. 8
Figure 3: PCB Layout of cPCI-8554/R .. 9
Figure 4: Pin Assignment of PCI-8554 Connector CN1 . . 13
Figure 5: Pin Assignment of cPCI-8554/R Connector CN1.. . 14
Figure 6: Block Diagram of 8254 Counter.. . 16
Figure 7: Default Counters Architectural. . 16
Figure 8: Example of ‘independent counters’. . 17
Figure 9: JP14/JP15 (For cPCI-8554/R only).. . 17
Figure 10: Cascaded Counter Configuration.. . 18
Figure 11: User Programmable Cascaded Counters .. . 18
Figure 12: Clock Source of Counter n.. . 19
Figure 13: Clock Source of CK1 . 19
Figure 14: Gate source of counter 1 \~ 10 .. . 20
Figure 15: Structure of JP1 \~ JP11.. . 21
Figure 16: Clock Source of DB\_CLK . . 21
Figure 17: Basic Timing of the debounce system . . 22
Figure 18: Dual Interrupt System of cPCI/PCI-8554/R. . 22
Figure 19: Digital I/O Connection.. .. 30
Figure 20: Example of a frequency generator (1).. . 32
Figure 21: Example of frequency generator (2)... . 33
Figure 22: Example of pulse width measurement . . 34
Figure 23: Example of frequency measurement (1).. .. 36
Figure 24: Example of event counter .. . 37
Figure 25: Example of dual interrupt system.. . 38

# How to Use This Guide

This manual is designed to help you use the cPCI/PCI-8554/R. The manual describes how to modify various settings on the cPCI/PCI-8554/R card to meet your requirements. It is divided into 5 chapters:

Chapter 1, “Introduction,” gives an overview of the product features, applications, and specifications.

Chapter 2, “Installation & Configurations” describes the operation method and multi-functions of the cPCI/PCI-8554/R. Users should read through this chapter to understand the configurations of the cPCI/PCI-8554/R. The chapter will also outline how to install the cPCI/PCI-8554/R.

Chapter 3, “Registers,” describes the details of each register of the cPCI/PCI-8554/R; this information will assist programmers who want to control the hardware with low-level programming.

Chapter 4, “Signal Connection & Applications,” describes the connectors' pin assignment and how to connect the outside signal and devices to / from the cPCI/PCI-8554/R. Some applications also are introduced.

Chapter 5, “High-level Programming,” introduces the Clanguage library for operating the cPCI/PCI-8554/R. Some examples are shown too.

#

# Introduction

cPCI/PCI-8554/R is a general-purpose counter / timer and digital I/O card. The card is designed with four 8254, a programmable interval timer/counter chip, totally, providing twelve 16-bit down counter or frequency dividers. Three different types of interface are available: PCI (PCI-8554), CompactPCI (cPCI-8554), and CompactPCI with rear I/O connection (cPCI-8554R) for various platforms and applications.

The card has multi-configurations. Its counters can be set in an independent or cascaded configuration. The gate controls for the counter can come from either the internal default enable signal or from external sources. The clock source of the counters can be set from an internal or external clock source, when an external clock source is used, users can configure the jumper as to disable or enable the debounce function.

The card also provides digital input and output ports. There are 8 digital output and 8 digital input channels, which can be used to control or monitor external devices.

The cPCI/PCI-8554/R provides an interrupt signal, which is generated by the counter output. External interrupt signals can also be used. The interrupt can be used for watchdog timers or others applications. The maximum interrupt time interval can be 536 seconds.

The I/O signals are provided via the 100-pin SCSI-II connector. Figure 1 shows the functional block diagram of the cPCI/PCI-8554/R. The cPCI/PCI-8554/R uses ASIC PCI controller to interface the board to the PCI bus. The ASIC fully implements the PCI local bus specification Rev 2.1. The BIOS software automatically controls all bus relative configurations, such as base memory and interrupt assignment. This removes the burden of searching for a conflict, which can be very time consuming and difficult with some bus standards.

![**Labeled Blocks:**\n*   PCI Bus\n*   PCI Controle\n*   Interrupt system\n*   clock system\n*   8 bits input/output\n*   8254 chip #1\n*   8254 chip #2\n*   8254 chip #3\n*   8254 chip #4\n*   Debounce system\n*   100 pin SCSI -\n\n**Connections:**\n*   **PCI Bus** and **PCI Controle**: Connected via 'data bus' (bidirectional), 'Address bus' (PCI Bus to PCI Controle), and 'Interru' (PCI Controle to PCI Bus).\n*   **PCI Controle** and **Interrupt system**: Connected via a bidirectional arrow.\n*   **PCI Controle** and **8 bits input/output**: Connected via a bidirectional arrow.\n*   **PCI Controle** and **8254 chip #1**: Connected via a bidirectional arrow.\n*   **PCI Controle** and **8254 chip #2**: Connected via a bidirectional arrow.\n*   **PCI Controle** and **8254 chip #3**: Connected via a bidirectional arrow.\n*   **PCI Controle** and **8254 chip #4**: Connected via a bidirectional arrow.\n*   **8 bits input/output** and **100 pin SCSI -**: Connected via bidirectional arrows labeled '8' and '8/'.\n*   **8254 chip #1** and **100 pin SCSI -**: Connected via unidirectional arrows labeled 'COUT1 ~ COUT3' and 'GATE1 ~ GATE3'.\n*   **8254 chip #2** and **100 pin SCSI -**: Connected via unidirectional arrows labeled 'COUT4 ~ COUT6' and 'GATE4 ~ GATE6'.\n*   **8254 chip #3** and **100 pin SCSI -**: Connected via unidirectional arrows labeled 'COUT7 ~ COUT9' and 'GATE7 ~ GATE9'.\n*   **8254 chip #4** and **100 pin SCSI -**: Connected via unidirectional arrows labeled 'COUT10 ~ COUT12' and 'GATE10 ~'.\n*   **Debounce system** and **100 pin SCSI -**: Connected via unidirectional arrows labeled 'ECLK1 ~ ECLK10' and 'E_INT'.\n*   **clock system** and **Interrupt system**: Connected via a unidirectional arrow.\n*   **Debounce system** and **Interrupt system**: Connected via a unidirectional arrow.\n*   **8254 chip #4** (left side) and **Interrupt system**: Connected via a unidirectional arrow labeled 'COUT12'.](.pci-8554-manual-4/cc27c76327dde70b654c5ef55400c6eaf6cf73e2c038c88e9736ca432e1f0dac.jpg)

Figure 1: Functional Block diagram

# 1.1 Features

The cPCI/PCI-8554/R Counter / Timer and digital I/O Card provides the following advanced features:

• Four 8254 chips provide twelve 16 bits down counters
Multi-configurations of counters / timers:
Flexible setting for each independent counter, the clock source could be external, internal or cascaded. The gate signal is external controlled or internal enabled.
Provide debounce function with flexible setting to prevent from bounce phenomenon when using external clocks.
• 8 digital output channels
• 8 digital input channels
Dual interrupt sources
3 From output of counter #12, or
3 From external source.
100-pin SCSI-II female connector.
• PCI-Bus

# 1.2 Applications

• Event counter
Frequency generator
Frequency synthesizer
Pulse width measurement
• Low level pulse generator
Time delay
Industry automation
Watchdog timer

# 1.3 Specifications

# Programmable Counter / Timer

Device: 82C54x4
Number of Counters/timers:
3 10 independent timers / counters
3 2 cascaded timers / counters
3 Cascaded 32-bit counters with fixed 8MHz internal clock

• Counter mode: 16-bit down counter

Maximum input frequency: 8 MHz

Clock sources of independent counters:

3 External clock
3 Prior counter output
3 Clock #10 output
3 CK1 (Programmable)

CK1 clock sources: (Programmable)

3 8MHz internal base clock
3 Programmable counter 11 output

Gate control: default enable or external control

# Digital Filter Circuits

Device: MC14490
De-bounce clock: (Programmable)
3 8MHz internal base clock
3 Programmable counter 11 output

# Digital I/O (DIO)

• No. of input channels : 8 channels
No. of output channels : 8 channels (dedicated output)
Characteristics: TTL compatible signal

# General Specifications

Connector: 100-pin SCSI-II female connector
Operating Temperature: 0°C \~ 60°C
Storage Temperature: -20°C \~ 80°C
• Humidity: 5 \~ 95%, non-condensing
• Power Consumption: +5 V @ 350 mA typical
Dimension: 134mm(L) X 107mm(W)

# 1.4 Software Supporting

ADLINK provides versatile software drivers and packages for users’ different approach to building a system. ADLINK not only provides programming libraries such as DLL for most Windows based systems, but also provide drivers for many other software packages such as LabVIEW®, HP VEETM, DASYLabTM, InTouchTM, InControlTM, ISaGRAFTM, and so on.

All software options are included in the ADLINK CD. Non-free software drivers are protected with licensing codes. Without the software code, you can install and run the demo version for two hours for trial/demonstration purposes. Please contact ADLINK dealers to purchase the formal license.

# 1.4.1 Programming Library

For customers who are writing their own programs, we provide function libraries for many different operating systems, including:

DOS Library: Borland C/C++ and Microsoft C++, the functional descriptions are included in this user’s guide.

Windows 95 DLL: For VB, VC++, Delphi, BC5, the functional descriptions are included in this user’s guide.

PCIS-DASK: Include device drivers and DLL for Windows 98, Windows NT and Windows 2000. DLL is binary compatible across Windows 98, Windows NT and Windows 2000. This means all applications developed with PCIS-DASK are compatible with Windows 98, Windows NT and Windows 2000. The developing environment can be VB, VC++, Delphi, BC5, or any Windows programming language that allows calls to a DLL. The user’s guide and function reference manual of PCIS-DASK are included in the CD. Please refer to the PDF files under \\Manual\_PDF\Software\PCIS-DASK

PCIS-DASK/X: Include device drivers and shared library for Linux. The developing environment can be Gnu C/C++ or any programming language that allows linking to a shared library. The user's guide and function reference manual of D2K-DASK/X are included in the CD. (\Manual\_PDF\Software\D2K-DASK-X.)

The above software drivers are shipped with the board. Please refer to the “Software Installation Guide” for installation procedures.

# 1.4.2 PCIS-LVIEW: LabVIEW® Driver

PCIS-LVIEW contains the VIs, which is used to interface with the NI LabVIEW® software package. The PCIS-LVIEW supports Windows 95/98/NT/2000. The LabVIEW® drivers are shipped free with the board. For more information about PCIS-LVIEW, please refer to the user’s guide in the CD. (\\Manual\_PDF\Software\PCIS-LVIEW)

# 1.4.3 PCIS-VEE: HP-VEE Driver

The PCIS-VEE includes user objects, which are used to interface with the HP VEE software package. PCIS-VEE supports Windows 95/98/NT. The HP-VEE drivers are shipped free with the board. For more information about PCIS-VEE, please refer to the user’s guide in the CD. (\\Manual\_PDF\Software\PCIS-VEE)

# 1.4.4 DAQBenchTM: ActiveX Controls

We suggest customers who are familiar with ActiveX controls and VB/VC++ programming use the DAQBenchTM ActiveX Control components library for developing applications. The DAQBenchTM is designed under Windows NT/98. For more information about DAQBench, please refer to the user’s guide in the CD. (\\Manual\_PDF\Software\DAQBench\DAQBench Manual.PDF)

# 2

# Getting Started

This chapter discusses how to setup the cPCI/PCI-8554R and configure the card to meet the requirements of your application. The contents of the package and unpacking information that you should be aware off are outlined first.

# 2.1 What You Have

In addition to this User's Manual, the package should includes the following items:

cPCI/PCI-8554/R Enhanced Multi-function Counter / Timer Card
ADLINK CD
Software Installation Guide

If any of these items are missing or damaged, contact the dealer from whom you purchased the product. Save the shipping materials and carton in case you want to ship or store the product in the future.

# 2.2 Unpacking

Your cPCI/PCI-8554/R card contains electro-static sensitive components that can be easily be damaged by static electricity.

Therefore, the card should be handled on a grounded anti-static mat. The operator should be wearing an anti-static wristband, grounded at the same point as the anti-static mat.

Inspect the card module carton for obvious damages. Shipping and handling may cause damage to your module. Be sure there are no shipping and handling damages on the modules carton before continuing.

After opening the card module carton, extract the system module and place it only on a grounded anti-static surface with component side up.

Again, inspect the module for damages. Press down on all the socketed $| \check { \mathbf { C } ^ { \prime } } \mathsf { s }$ to make sure that they are properly seated. Do this only with the module placed on a firm flat surface.

Note: DO NOT APPLY POWER TO THE CARD IF IT HAS BEEN DAMAGED.

You are now ready to install your cPCI/PCI-8554/R.

# 2.3 PCB Layout of cPCI/PCI-8554/R

![PCI-B554 REV.A2\n8254\n8254\n8254\n8254\n74LS273\n74LS273\n74LS273\n74LS244\n74LS273\n74LS273\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8256\n8256\n8256\n8256\n8256\n8256\n8256\n8256\n8256\n8256\n8256\n8256\n8256\n8256\n8256\n8256\n8256\n8256\n8256\n8256\n8250\n8250\n8250\n8250\n8250\n8250\n8250\n8250\n8250\n8250\n8250\n8250\n8250\n8250\n8250\n8250\n8250\n8250\n8250\n8250\n8251\n8251\n8251\n8251\n8251\n8251\n8251\n8251\n8251\n8251\n8251\n8251\n8251\n8251\n8251\n8251\n8251\n8251\n8251\n8251\n8253\n8253\n8253\n8253\n8253\n8253\n8253\n8253\n8253\n8253\n8253\n8253\n8253\n8253\n8253\n8253\n8253\n8253\n8253\n8253\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8254\n8260\nR1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1](.pci-8554-manual-4/a49d04d8e738a1139de783b206e8b3b05db74858dc624d943ea49bd501b08b26.jpg)

Figure 2: PCB Layout of PCI-8554

![Circuit board layout diagram with labeled components and connections](.pci-8554-manual-4/77cd7c62e07f53f313d896bbcd48d01d55dc758cad43ba17c78a0d937e65deb6.jpg)

Figure 3: PCB Layout of cPCI-8554/R

# 2.4 Default Jumper Setting

To operate the cPCI/PCI-8554/R correctly, users need to understand the structure of cPCI/PCI-8554/R and details of the possible configurations. The functional block diagram of the cPCI/PCI-8554/R is shown in figure 1 of chapter 1. The following section lists the default jumper setting on the cPCI/PCI-8554/R.

<table><tr><td>Items</td><td>Default Configuration</td><td>Set by</td></tr><tr><td>ECLK1</td><td>No Debounce function</td><td>JP1</td></tr><tr><td>ECLK2</td><td>No Debounce function</td><td>JP2</td></tr><tr><td>ECLK3</td><td>No Debounce function</td><td>JP3</td></tr><tr><td>ECLK4</td><td>No Debounce function</td><td>JP4</td></tr><tr><td>ECLK5</td><td>No Debounce function</td><td>JP5</td></tr><tr><td>ECLK6</td><td>No Debounce function</td><td>JP6</td></tr><tr><td>ECLK7</td><td>No Debounce function</td><td>JP7</td></tr><tr><td>ECLK8</td><td>No Debounce function</td><td>JP8</td></tr><tr><td>ECLK9</td><td>No Debounce function</td><td>JP9</td></tr><tr><td>ECLK10</td><td>No Debounce function</td><td>JP10</td></tr><tr><td>E_INT</td><td>No Debounce function</td><td>JP11</td></tr><tr><td>ECLK11</td><td>Internal 8MHz Clock</td><td>JP12</td></tr><tr><td>ECLK12</td><td>Output of CLK11</td><td>JP13</td></tr></table>

Table 1. Default Jumper Settings on PCI-8554

<table><tr><td>Items</td><td>Default Configuration</td><td>Set by</td></tr><tr><td>GATE11</td><td>Vcc</td><td>JP14</td></tr><tr><td>GATE12</td><td>Vcc</td><td>JP15</td></tr></table>

Table 2. Extra Default Jumper Setting on cPCI-8554/R

There are 13 jumpers available on the PCI-8554, and 15 jumpers on the cPCI-8554/R, the first 11 jumpers are used to select the debounce function. JP12 and JP13 are used for selecting the clock source for Counter No. 11 and 12. The default setting for counter No. 11 and 12 are cascaded for frequency division. Refer to section 2.9 for more details. JP14 and JP15 are used for selecting the gate voltages of counter No. 11 and 12 (only for cPCI-8554/R). Users can change the cPCI/PCI-8554/R's default configuration by setting jumpers on the card to suit the application. The card's jumpers are preset at the factory.

Before changing the default configuration, users must fully understand the operation of the debounce function. The setting and the basic operation theory are not discussed in this chapter. Refer to section 2.12 for details of the operation theory and than refer to chapter 4 for application notes.

# 2.5 cPCI/PCI-8554/R Installation

# 2.5.1 Hardware configuration

The PCI cards (or CompactPCI cards) is equipped with the plug and play PCI controller, it has the ability to request base addresses and interrupts according to the PCI standard. The systems BIOS will install the system resources based on the PCI cards’ configuration registers and system parameters (which are set by system BIOS). Interrupt assignments and memory usage (I/O port locations) of the PCI cards are also assigned by system BIOS. This system resource assignment is done on a board-byboard basis. It is not suggested to assign system resources by any other methods.

The PCI card can be inserted into any PCI slot without the need for any system resource configuration.

# 2.5.1.1 Installation Procedures

1. Turn off your computer
2. Turn off all accessories (printer, modem, monitor, etc.) connected to your computer.
3. Remove the cover from your computer.
4. Setup jumpers on the PCI or CompactPCI card.
5. Select a 32-bit PCI slot. PCI slot are shorter than ISA or EISA slots, and are usually white or ivory in color.
6. Before handling the PCI cards, discharge any static buildup on your body by touching the metal case of the computer. Hold the edge and do not touch the components.
7. Position the board into the PCI slot you selected.
8. Secure the card in place at the rear panel of the system.

# 2.6 Device Installation for Windows Systems

Once Windows 95/98/2000 has started, the Plug and Play function of the Windows OS will find the new NuDAQ/NuIPC cards. If this is the first time a NuDAQ/NuIPC cards is installed into the computer system. The Windows operating system will inform you to input the device information source. Please refer to the “Software Installation Guide” for installation procedures.

# 2.7 Pin Assignment of Connector

![(1)\n(2)\n(3)\n(51)\n(52)\n(53)\n(48)\n(49)\n(50)\n(98)\n(99)\n(100)](.pci-8554-manual-4/c529f9fd2f0bc51b08889fda14af472351f8f7bad57c85bd95561e95675dc4ec.jpg)

<table><tr><td>(1) +12V</td><td>(26) GND</td><td>(51) GND</td><td>(76) ECLK9</td></tr><tr><td>(2) +12V</td><td>(27) GND</td><td>(52) GOUT2</td><td>(77) COUT8</td></tr><tr><td>(3) +12V</td><td>(28) GND</td><td>(53) GIN2</td><td>(78) GATE8</td></tr><tr><td>(4) Vcc</td><td>(29) GND</td><td>(54) GND</td><td>(79) ECLK8</td></tr><tr><td>(5) Vcc</td><td>(30) GND</td><td>(55) GOUT1</td><td>(80) COUT7</td></tr><tr><td>(6) Vcc</td><td>(31) GND</td><td>(56) GIN1</td><td>(81) GATE7</td></tr><tr><td>(7) NC</td><td>(32) GND</td><td>(57) E_INT</td><td>(82) ECLK7</td></tr><tr><td>(8) DI_6</td><td>(33) GND</td><td>(58) DI7</td><td>(83) COUT6</td></tr><tr><td>(9) DI_4</td><td>(34) GND</td><td>(59) DI5</td><td>(84) GATE6</td></tr><tr><td>(10) DI_2</td><td>(35) GND</td><td>(60) DI3</td><td>(85) ECLK6</td></tr><tr><td>(11) DI_0</td><td>(36) GND</td><td>(61) DI1</td><td>(86) COUT5</td></tr><tr><td>(12) DO_6</td><td>(37) GND</td><td>(62) DO7</td><td>(87) GATE5</td></tr><tr><td>(13) DO_4</td><td>(38) GND</td><td>(63) DO5</td><td>(88) ECLK5</td></tr><tr><td>(14) DO_2</td><td>(39) GND</td><td>(64) DO3</td><td>(89) COUT4</td></tr><tr><td>(15) DO_0</td><td>(40) GND</td><td>(65) DO1</td><td>(90) GATE4</td></tr><tr><td>(16) NC</td><td>(41) GND</td><td>(66) ECLK12</td><td>(91) ECLK4</td></tr><tr><td>(17) GND</td><td>(42) GND</td><td>(67) COUT12</td><td>(92) COUT3</td></tr><tr><td>(18) GND</td><td>(43) GND</td><td>(68) ECLK11</td><td>(93) GATE3</td></tr><tr><td>(19) GND</td><td>(44) GND</td><td>(69) COUT11</td><td>(94) ECLK3</td></tr><tr><td>(20) GND</td><td>(45) GND</td><td>(70) GND</td><td>(95) COUT2</td></tr><tr><td>(21) GND</td><td>(46) GND</td><td>(71) COUT10</td><td>(96) GATE2</td></tr><tr><td>(22) GND</td><td>(47) GND</td><td>(72) GATE10</td><td>(97) ECLK2</td></tr><tr><td>(23) GND</td><td>(48) GND</td><td>(73) ECLK10</td><td>(98) COUT1</td></tr><tr><td>(24) GND</td><td>(49) GND</td><td>(74) COUT9</td><td>(99) GATE1</td></tr><tr><td>(25) GND</td><td>(50) GND</td><td>(75) GATE9</td><td>(100) ECLK1</td></tr></table>

Figure 4: Pin Assignment of PCI-8554 Connector CN1

Legend:

<table><tr><td>ECLK n:</td><td>External clock source for counter #n</td></tr><tr><td>ExtG n:</td><td>External gate signal for counter #n</td></tr><tr><td>COUT n:</td><td>Counter / Timer output of counter #n</td></tr><tr><td>DO_m:</td><td>Digital output port channel #m</td></tr><tr><td>DI_m:</td><td>Digital input port channel #m</td></tr><tr><td>E_int:</td><td>External interrupt signal input</td></tr><tr><td>GOUT1:</td><td>Inverse TTL signal of GIN1</td></tr><tr><td>GOUT2:</td><td>Inverse TTL signal of GIN2</td></tr><tr><td>NC:</td><td>No Connection</td></tr></table>

![The image displays the text '(1)' on the left side and '(51)' on the right side. Between these numbers, a large, thin black line arches upwards, resembling a brace. Underneath this arch are two small, gray squares positioned side-by-side.](.pci-8554-manual-4/31e83179279f9e327f0548452575a6b0d821cafc94d18e9db1032db9c7205cf6.jpg)

(1) +12V

(26) GND

(51) GND

(76) ECLK9

<table><tr><td>(2) +12V</td><td>(27) GND</td><td>(52) GOUT2</td><td>(77) COUT8</td></tr><tr><td>(3) +12V</td><td>(28) GND</td><td>(53) GIN2</td><td>(78) GATE8</td></tr><tr><td>(4) Vcc</td><td>(29) GND</td><td>(54) GND</td><td>(79) ECLK8</td></tr><tr><td>(5) Vcc</td><td>(30) GND</td><td>(55) GOUT1</td><td>(80) COUT7</td></tr><tr><td>(6) Vcc</td><td>(31) GND</td><td>(56) GIN1</td><td>(81) GATE7</td></tr><tr><td>(7) GATE12</td><td>(32) GND</td><td>(57) E_INT</td><td>(82) ECLK7</td></tr><tr><td>(8) DI_6</td><td>(33) GND</td><td>(58) DI7</td><td>(83) COUT6</td></tr><tr><td>(9) DI_4</td><td>(34) GND</td><td>(59) DI5</td><td>(84) GATE6</td></tr><tr><td>(10) DI_2</td><td>(35) GND</td><td>(60) DI3</td><td>(85) ECLK6</td></tr><tr><td>(11) DI_0</td><td>(36) GND</td><td>(61) DI1</td><td>(86) COUT5</td></tr><tr><td>(12) DO_6</td><td>(37) GND</td><td>(62) DO7</td><td>(87) GATE5</td></tr><tr><td>(13) DO_4</td><td>(38) GND</td><td>(63) DO5</td><td>(88) ECLK5</td></tr><tr><td>(14) DO_2</td><td>(39) GND</td><td>(64) DO3</td><td>(89) COUT4</td></tr><tr><td>(15) DO_0</td><td>(40) GND</td><td>(65) DO1</td><td>(90) GATE4</td></tr><tr><td>(16) GATE11</td><td>(41) GND</td><td>(66) ECLK12</td><td>(91) ECLK4</td></tr><tr><td>(17) GND</td><td>(42) GND</td><td>(67) COUT12</td><td>(92) COUT3</td></tr><tr><td>(18) GND</td><td>(43) GND</td><td>(68) ECLK11</td><td>(93) GATE3</td></tr><tr><td>(19) GND</td><td>(44) GND</td><td>(69) COUT11</td><td>(94) ECLK3</td></tr><tr><td>(20) GND</td><td>(45) GND</td><td>(70) GND</td><td>(95) COUT2</td></tr><tr><td>(21) GND</td><td>(46) GND</td><td>(71) COUT10</td><td>(96) GATE2</td></tr><tr><td>(22) GND</td><td>(47) GND</td><td>(72) GATE10</td><td>(97) ECLK2</td></tr><tr><td>(23) GND</td><td>(48) GND</td><td>(73) ECLK10</td><td>(98) COUT1</td></tr><tr><td>(24) GND</td><td>(49)GND</td><td>(74) COUT9</td><td>(99) GATE1</td></tr><tr><td>(25) GND</td><td>(50) GND</td><td>(75) GATE9</td><td>(100) ECLK1</td></tr></table>

Figure 5: Pin Assignment of cPCI-8554/R Connector CN1

# Legend:

ECLK n: External clock source for counter #n

ExtG n: External gate signal for counter #n

COUT n: Counter / Timer output of counter #n

DO\_m: Digital output port channel #m

DI\_ m: Digital input port channel #m

$E _ { - } i n t { : }$ External interrupt signal input

GOUT1: Inverse TTL signal of GIN1

GOUT2: Inverse TTL signal of GIN2

Note: pin-7and pin-16 is different from the definition in PCI-8554.

# 2.8 Clock System

The clock system of the cPCI/PCI-8554/R provides the internal clock source for the 8254 chips. The clock for counter/timer 1 \~ 10 can be one of 4 sources; an external clock source, a cascaded source from the ‘last’ channel, CK1 or COUT10. The next section will outline details on setting the clock for each counter/timer and CK1. The clock of counter/timer 11 is fixed at 8Mhz, and the clock of counter/timer 12 is connected to COUT11

# 2.9 Counters Architecture

There are four 8254 programmable timer/counter chips on the cPCI/PCI-8554/R card. Each 8254 chip contains 3 counter/timer and are labeled from 1 to 12. Counters 11 and 12 are default cascaded counters, but can be set for independent operation through jumpers JP12 & JP13. Counters 1 \~ 10 can also be set as an independent or cascaded counters. Table 3 illustrates the relationship between the reference 8254-chip label and the counter labels.

<table><tr><td>8254 Chip Label</td><td>Reference Number</td><td>Counter Label</td><td>Type of Counter</td></tr><tr><td rowspan="3">Chip 1</td><td rowspan="3">U3</td><td>Counter 1</td><td>Independent or Cascaded</td></tr><tr><td>Counter 2</td><td>Independent or Cascaded</td></tr><tr><td>Counter 3</td><td>Independent or Cascaded</td></tr><tr><td rowspan="3">Chip 2</td><td rowspan="3">U4</td><td>Counter 4</td><td>Independent or Cascaded</td></tr><tr><td>Counter 5</td><td>Independent or Cascaded</td></tr><tr><td>Counter 6</td><td>Independent or Cascaded</td></tr><tr><td rowspan="3">Chip 3</td><td rowspan="3">U5</td><td>Counter 7</td><td>Independent or Cascaded</td></tr><tr><td>Counter 8</td><td>Independent or Cascaded</td></tr><tr><td>Counter 9</td><td>Independent or Cascaded</td></tr><tr><td rowspan="3">Chip 4</td><td rowspan="3">U6</td><td>Counter 10</td><td>Independent or Cascaded</td></tr><tr><td>Counter 11</td><td>Independent or Cascaded</td></tr><tr><td>Counter 12</td><td>Independent or Cascaded</td></tr></table>

Table 3. Counters label relationship

There are three signals (2 input and 1 output) for each counter, a clock input signal, a gate control signal, and an output signal. Figure 6 illustrates the block diagram of the 8254 counter. CLK1 \~ CLK12 are clock sources, GATE1 \~ GATE12 are gate control signals and COUT1 \~ COUT12 are outputs of the counters. Figure 7 shows the inter-connection of the 8254 counters and the labels associated to each counter.

![The diagram depicts a block labeled **8254 Chip** at the top. Inside the block, the word **Counter** is centered.\n\n**Inputs (Left Side):**\n*   **Clock Source Input**: An arrow points from this text to the letter **C** inside the block.\n*   **Gate Control Input**: An arrow points from this text to the letter **G** inside the block.\n\n**Output (Right Side):**\n*   An arrow originates from the letter **O** inside the block and points to the text **Counter / Timer Output**.](.pci-8554-manual-4/e11bd3c0f24759c753b097d3f801d3a82feda79b1e6c701259cc01c1c5d6cd93.jpg)

Figure 6: Block Diagram of 8254 Counter

![The diagram displays a block labeled **8254 Chip #2** which contains three internal counters: **Counter #4**, **Counter #5**, and **Counter #6**.\n\n**Connections:**\n*   **Inputs (Left Side):**\n    *   **CLK4** connects to the top input of **Counter #4** (labeled **C**).\n    *   **GATE4** connects to the bottom input of **Counter #4** (labeled **G**).\n    *   **CLK5** connects to the top input of **Counter #5**.\n    *   **GATE5** connects to the bottom input of **Counter #5** (labeled **G**).\n    *   **CLK6** connects to the top input of **Counter #6**.\n    *   **GATE6** connects to the bottom input of **Counter #6** (labeled **G**).\n*   **Outputs (Right Side):**\n    *   **COUT4** exits **Counter #4**.\n    *   **COUT5** exits **Counter #5**.\n    *   **COUT6** exits **Counter #6**.](.pci-8554-manual-4/f1d5c3e69b61e933f77b4710caf87104466aebabe9518e5cde3f31e00f141104.jpg)

![The diagram depicts a block labeled **8254 Chip #1** which contains three vertically stacked internal blocks: **Counter #1**, **Counter #2**, and **Counter #3**.\n\n**Connections and Labels:**\n\n*   **Counter #1:**\n    *   Input **CLK1** connects to port **C**.\n    *   Input **GATE1** connects to port **G**.\n    *   An output line labeled **COUT1** exits to the right.\n\n*   **Counter #2:**\n    *   Input **CLK2** connects to port **C**.\n    *   Input **GATE2** connects to port **G**.\n    *   An output line labeled **COUT2** exits to the right.\n\n*   **Counter #3:**\n    *   Input **CLK3** connects to port **C**.\n    *   Input **GATE3** connects to port **G**.\n    *   An output line labeled **COUT3** exits to the right.](.pci-8554-manual-4/ee9521d168cbee3df63664e9172d59090c3260ee64d61fb52471b341e34e0a23.jpg)

![The diagram depicts a block labeled **8254 Chip #4** containing three distinct counters stacked vertically.\n\n**Labeled Blocks:**\n*   **Counter #10** (Top section)\n*   **Counter #11** (Middle section)\n*   **Counter #12** (Bottom section)\n\n**Connections:**\n*   **CLK10** connects to the **C** input of **Counter #10**.\n*   **GATE10** connects to the **G** input of **Counter #10**.\n*   **8M Hz** connects to the **C** input of **Counter #11**.\n*   **VCC** connects to the **G** input of **Counter #11** and loops downward to connect to the **G** input of **Counter #12**.\n*   The output labeled **COUT11** connects to the **C** input of **Counter #12**.\n\n**Outputs:**\n*   **COUT10** exits from **Counter #10**.\n*   **COUT11** exits from **Counter #11**.\n*   **COUT12** exits from **Counter #12**.](.pci-8554-manual-4/d6a7eb7ea6f4c96023c4191f270b177d6cd47369fd44b86bc7f943a4570f9b02.jpg)

![This block diagram depicts a component labeled **8254 Chip #3** which houses three vertically stacked counters: **Counter #7**, **Counter #8**, and **Counter #9**.\n\nEach counter section follows a consistent input/output pattern:\n\n*   **Counter #7**: Receives inputs via arrows labeled **CLK7** and **GATE7** connecting to terminals labeled **C** and **G** respectively. It produces an output arrow labeled **COUT7**.\n*   **Counter #8**: Receives inputs via arrows labeled **CLK8** and **GATE8** connecting to terminals labeled **C** and **G** respectively. It produces an output arrow labeled **COUT8**.\n*   **Counter #9**: Receives inputs via arrows labeled **CLK9** and **GATE9** connecting to terminals labeled **C** and **G** respectively. It produces an output arrow labeled **COUT9**.](.pci-8554-manual-4/8ddaa70e88b5d68192e0742a5064e603d87ec99d1d0591353d8a7658a1a513ce.jpg)

Figure 7: Default Counters Architectural

# 2.9.1 Independent Counters (Counter 1\~10)

Counters 1 to 10 are independent counters because the clock source and gate control of those counters can be set independently (Thus named Independent Counter).

![The diagram depicts a single rectangular block labeled **8254 Chip #1** at the top and **Counter #1** in the center.\n\n**Connections:**\n*   An input line labeled **CLK1** points to the input pin labeled **C** on the left side of the block.\n*   An input line labeled **GATE1** points to the input pin labeled **G** below **C** on the left side.\n*   An output line originates from the output pin labeled **O** on the right side and is labeled **COUT1**.](.pci-8554-manual-4/f01feaab6e998f0704172177345318dc7819c2cfc262371ed6c1df43d0d90b48.jpg)

Figure 8: Example of ‘independent counters’

# 2.9.2 Cascaded Counters

The connection of Counter 11 and 12 are different from the independent counters. These two counters are cascaded counters by default settings. The clock source of counter 11 is set to the internal 8 MHz clock by JP12, while JP13 connects its output to counter 12. In fact, counter 11and 12 are designed for frequency division by using the 8254's square wave generator mode. The gates of these counters are by default tied to logic high (‘H’) to enable these counters at all times. Users can change JP14 and JP15 to tie the signal to the GATE pins.

![JP14 / JP15\nVcc\nGATE11/12\nGate of Counter\n#11 / #12](.pci-8554-manual-4/397a393da9f3f49c623bc9c6b0d6df66fbc2ac4dd1a63dc54028d9245eaf6165.jpg)

Figure 9: JP14/JP15 (For cPCI-8554/R only)

COUT12 can precisely generate frequencies up to 2MHz and as low as 0.00186 Hz. Note that the COUT12 signal can also be used as an interrupt source. See ‘Interrupt Sources’ section for details. Figure 10 illustrates the cascaded counters - counters 11 and 12. Sometimes, you may require all 12 counters to operate independently. For such a case, you can break the default connection by reconfiguring jumpers J12 and J13. Note that both counters 11 and 12 only have 2 selectable clock sources. It can be either the 8 MHz internal clock source or an external clock source.

![8MHz\nJP12\nECLK11\nJP13\nECLK12\n8254 Chip #4\nCounter 11 O\nCounter 12 O](.pci-8554-manual-4/d44399c6d3e76a1799de614929ecc4b53bddeceebbae8942cc3aae984f1d160f.jpg)

Figure 10: Cascaded Counter Configuration

# 2.9.3 User Configurable Cascaded Counters

Although by default there is only one cascaded counter, users can configure the independent counters to be in a cascaded arrangement by using the \_SET\_cntCLK\_ function. . Figure 11 illustrates the user programmable-cascaded counter. Refer to the next section for details of the clock source options.

![The diagram depicts a block labeled '8254 Chip #1' containing two sub-blocks: 'Counter #1' and 'Counter #2'.\n\n**Inputs:**\n*   **Counter #1:** Receives 'CLK1' connected to pin 'C', 'GATE1' connected to pin 'G', and 'VCC' connected to pin 'G'.\n*   **Counter #2:** Receives 'CLK2' connected to pin 'C', 'GATE2' connected to pin 'G', and 'VCC' connected to pin 'G'.\n\n**Outputs and Connections:**\n*   **Counter #1** has an output labeled 'COUT1'.\n*   **Counter #2** has an output labeled 'COUT2'.\n*   The output 'COUT1' connects via a switch to the input 'CLK2' (pin 'C' of Counter #2). The switch is indicated by two circles and labeled below with 'selectable by function '_SET_cntCLK_ ''.\n*   The output 'COUT2' is labeled 'Cascaded Counters Output'.](.pci-8554-manual-4/4d09f71be71f6e534102c579132627432421baf189bbc91ac9c16f764797f49b.jpg)

Figure 11: User Programmable Cascaded Counters

# 2.10 Clock Source Configurations

For each independent counter, one of four different clock sources maybe selected using the software. The clock source of counter n can be either an external clock source (ECLK n), a cascaded counter output (COUTn-1), CK1 or COUT10.

# Note:

1. The clock source of cascaded counter 11 is set at C8M (8MHz) and counter 12 is set to COUT11.
2. The external clock source labelled ECK n comes from JP1 \~ JP10, see section 2.12 for details

![This diagram depicts a 4-to-1 multiplexer (switch) with the following connections:\n\n*   **Inputs:** Four lines on the left connect via arrows to the four input terminals of the switch. From top to bottom, they are labeled:\n    *   'ECK n'\n    *   'COUT n-1'\n    *   'CK1'\n    *   'COUT10'\n*   **Control:** An arrow points upward into the center of the switch from text labels reading:\n    *   'select by function'\n    *   '_8554_SET_cntCLK'\n*   **Output:** A line exits the right side of the switch with an arrow pointing outward, labeled 'CLK n'.\n*   **Parameter:** The text 'n=1~9' appears at the top right of the diagram.](.pci-8554-manual-4/e738fdbd4e11eda7bf212dc185d7f83f8ea3af5020e323bbaf3cdf69165f5081.jpg)

![The diagram depicts a multiplexer logic block with the following labeled components and connections:\n\n*   **Inputs:** Four signals enter from the left side: **ECK10**, **COUT9**, **CK1**, and **C8M**. These inputs feed into four triangular buffer symbols.\n*   **Select Control:** An arrow points upward into the group of buffers, labeled with the text: **select by function '_8554_SET_cntCLK'**. This indicates the selection logic determines which input is active.\n*   **Output:** The active input signal passes through a connection node (small circle) and exits to the right, labeled **CLK10**.](.pci-8554-manual-4/7844f90d5a34019b49d68af9a9cf4c3003ec2653a2eded960d6c510e03ac8b03.jpg)

Figure 12: Clock Source of Counter n

![The diagram illustrates a logic switching mechanism (resembling a multiplexer) with the following labeled blocks and connections:\n\n**Labeled Blocks:**\n*   **C8M**\n*   **COUT11**\n*   **CK1**\n*   **select by function**\n*   **'_8554_SET_CK1''** (Note: This text appears on a second line below the previous label).\n\n**Connections:**\n*   An arrow from **C8M** points to a triangular buffer symbol.\n*   An arrow from **COUT11** points to a triangular buffer symbol.\n*   The outputs of these two buffer symbols feed into a switching point.\n*   An arrow from the text **select by function** and **'_8554_SET_CK1''** points upward to the center of the switching mechanism.\n*   An arrow from the right side of the switch points to the label **CK1**.](.pci-8554-manual-4/f5e70dc15373172131811ccb9339aad61707b9a13eafa22a2a6671f043e3e7e7.jpg)

Figure 13: Clock Source of CK1

The internal clock sources of CK1 can be either C8M or COUT11, and is selected by using the “\_8554\_SET\_CK1” function. If the counters are set in a cascaded configuration, then the clock source will be from the output of the previous counter (Counter n-1). For example, COUT1 is cascaded to CLK2; COUT3 is cascaded to CLK4 and so on. (Note: If counter 1 is set in cascaded mode, CLK1 is connected to GND because COUT0 doesn’t exist).

# 2.11 Gate Control Configurations

The gate control signals of each independent counter is internally pulled high hence they are Enabled by default if no external gate is used. When an external gate signal is used, the counters can be used for pulse width measurements. Therefore, the period of the gate signal can be precisely controlled and frequency measurement is possible. Figure 14 shows the settings for the gate signals of counters 1\~ 10. (Note: The gate signals of counter 11 and 12 are always pulled high)

![VCC\nGATE n( From 100 pin\nSCSI-II Connector )\n→ GATE n( To 8254 )](.pci-8554-manual-4/9cdf7d458d8cf4b212aa37ea8608570d6f8a034b2bbab3fc2113d68700692279.jpg)

Figure 14: Gate source of counter 1 \~ 10

# 2.12 Counter Outputs

The clock source, gate signal and software programming controls the timer/counter output signal “COUT n”. All outputs from the 12 counters are routed to the 100-pin connector. Refer to the figure 4 and 5 for the corresponding signal pin number.

In addition, the output signal may be used as a clock source for cascaded configuration, see the above sections for details. It is possible to cascade all ten counters using the software settings, see 2.8 for reference. The output COUT12 can also be used as an internal interrupt source (refers to 'Interrupt System' for details).

# 2.13 Debounce System

The debounce system is used to eliminate the affects of bounce phenomenons. If an external clock is used, user can set JP1 \~ JP11 to select, whether or not to used the debounce system. If the debounce system is used, the debounce output signal will be in the same state as the input only if the input signal maintains the same state for four DB\_CLK cycles, otherwise the input signal will be treated as a glitch and the debounce output signal will maintain its present state, figure 15 illustrates how to set these jumpers, figure 16 illustrates how to select the DB\_CLK. Figure 17 illustrates the basic timing of the debounce system. (Note: DB\_CLK can’t be higher than 2MHz).

![The diagram depicts a circuit block diagram with the following labeled blocks and connections:\n\n*   **debounce system**: A rectangular block on the left.\n    *   **DB_CLK**: An arrow points downward from this label into the top of the **debounce system** block.\n    *   An arrow extends from the right side of the **debounce system** block, pointing towards the right assembly.\n\n*   **JP n**: A vertical assembly on the right, labeled **JP n** (with the text **n=1~10** to its right). This assembly visually consists of a rectangular box containing two grey circles stacked vertically, and a switch symbol below it.\n    *   The arrow from the **debounce system** connects to the top grey circle within the **JP n** box.\n    *   **ECLK n**: An arrow points upward from this label into the bottom terminal (open circle) of the switch symbol.\n    *   **ECK n**: An arrow points to the right from the bottom terminal of the switch symbol.](.pci-8554-manual-4/b1ad27366e4ff14741273aae91e86616c472f263a81e1372ec195a002cf84f17.jpg)

![Based on the provided image, here is an accurate and concise description of the flowchart/block diagram:\n\n**Labeled Blocks:**\n*   **debounce system**: A rectangular block.\n*   **JP11**: A rectangular block containing two circular terminals (pins).\n\n**Connections and Text:**\n*   **DB_CLK**: An arrow points downwards from the label 'DB_CLK' into the 'debounce system' block.\n*   **debounce system to JP11**: Lines connect the right side of the 'debounce system' block to the top terminal of the 'JP11' block.\n*   **JP11 to debounce system (E INT)**: A line originates from the bottom terminal of the 'JP11' block, extends to the left, and has an arrow pointing upwards into the 'debounce system' block. The text 'E INT' is labeled next to this connection.\n*   **JP11 Output (EXTINT)**: An arrow points to the right from the bottom area of the 'JP11' block, labeled 'EXTINT'.](.pci-8554-manual-4/b4052c85986834979fd637dbacd1d1f214d3bda0157b010f54170d9e73554ca7.jpg)

Figure 15: Structure of JP1 \~ JP11
![This diagram depicts a signal selection mechanism (essentially a multiplexer or switch).\n\n**Labeled Blocks/Text:**\n*   **COUT11** (Top input)\n*   **2MHz** (Bottom input)\n*   **DB_CLK** (Output)\n*   **select by function '_8554_SET_DBCLK'** (Control label)\n\n**Connections:**\n*   **COUT11** and **2MHz** are inputs on the left side, each with an arrow pointing toward a terminal of a switch symbol.\n*   The switch symbol connects one of these inputs to the output labeled **DB_CLK**.\n*   A vertical arrow points upward from the text **select by function '_8554_SET_DBCLK'** to the switch, indicating that this function controls which input is routed to the **DB_CLK** output.](.pci-8554-manual-4/2403457af1bcaa15ed834de95a7d5d59ccf39c6250a214c0508cd5f5f00c18a4.jpg)

Figure 16: Clock Source of DB\_CLK

![DB_CLK\ninput\nsignal\noutput\nsignal\nglitch is\neliminated](.pci-8554-manual-4/4e8709b22ed0efb8883cd9e45a9ced1d00986157863e0a09d00cd295636bac95.jpg)

Figure 17: Basic Timing of the debounce system

# 2.14 Interrupt System

The cPCI/PCI-8554/R‘s interrupt system is a powerful and flexible system, which is suitable for many applications. The system is a Dual Interrupt System. Dual Interrupt means the hardware can generate two interrupt request signals simultaneously and the software is able to respond and invoke the ISR. Note that dual interrupt do not mean the card will occupy two IRQ levels. These two interrupt request signals INT1 and INT2 are generated by the external interrupt signal EXTINT and the timer/counter 12 output. Figure 18 shows the structure of interrupt system.

![Based on the provided block diagram, here is the accurate and concise description:\n\n**Labeled Blocks:**\n*   8254 Chip #4 Counter #11\n*   8254 Chip #4 Counter #12\n*   IRQ Flip-Flops (appears twice)\n*   debounce system\n*   JP11\n*   PCI Controller\n\n**Connections:**\n*   **8MHz** and **'H'** connect to **8254 Chip #4 Counter #11**.\n*   The output of **8254 Chip #4 Counter #11** (labeled **'H'**) connects to **8254 Chip #4 Counter #12**.\n*   **COUT12** connects **8254 Chip #4 Counter #12** to the upper **IRQ Flip-Flops**.\n*   **Clear by '8554_CLR_IRQ1'** connects to the upper **IRQ Flip-Flops**.\n*   **INT1** connects the upper **IRQ Flip-Flops** to the **PCI Controller**.\n*   **DB_CLK** connects to the **debounce system**.\n*   **E_INT** connects to the bottom pin of **JP11**.\n*   The **debounce system** connects to the top pin of **JP11**.\n*   The middle and bottom pins of **JP11** are connected.\n*   **EXTINT** connects **JP11** to the lower **IRQ Flip-Flops**.\n*   **Clear by '8554_CLR_IRQ2'** connects to the lower **IRQ Flip-Flops**.\n*   **INT2** connects the lower **IRQ Flip-Flops** to the **PCI Controller**.\n*   **INT #A** is the output from the **PCI Controller**.](.pci-8554-manual-4/0a7f1f6a3348705db8bd315fa42bbdf3aa18fd3fbd03542592aa66b06127ce83.jpg)

Figure 18: Dual Interrupt System of cPCI/PCI-8554/R

Even though it is a dual interrupt system, only one interrupt level is ever used. The card uses the INT #A interrupt request signal on the PCI bus. The motherboards circuits will then transfer INT #A to one of the AT bus IRQ levels. The IRQ level is set by the PCI plug and play BIOS and is saved in the PCI controller. It is not necessary for users to set the IRQ level. Users can however read back the IRQ level setting by using the software library. Refer to the section 5.4.

The PCI controller of cPCI/PCI-8554/R can receive two hardware IRQ sources. However, a PCI controller can generate only one IRQ to the PCI bus, the two IRQ sources are distinguished by the ISR software. If both IRQ are in use, the application software will invoke the “\_8554\_GET\_IRQ\_Status” function to distinguish which interrupt is inserted and servicing that IRQ. Users must then clear the current IRQ to allow the next IRQ be processed.

If the application needs only one IRQ, the other IRQ source can be disabled by software. If your application does not require any IRQ sources, you can disable both interrupts. However, the PCI BIOS will still assign an IRQ level to the PCI card and hence will still occupy the PC’s resources if you only disable the IRQ sources without changing the initial conditions of the PCI controller. It is however, not recommended that the user re-design the initial condition of the PCI card with the users’ own application software. If users want to disable the IRQ level, user can use the ADLINK utility ‘INIT8554.EXE’ to change the interrupt settings.

# 2.15 Digital Input and Output

To program the digital I/O operation is fairly straightforward. The digital input operation is used for reading data from its corresponding registers, and the digital output operation is used for writing data to its corresponding registers. The digital I/O registers‘ are discussed in section 3.4 and 3.5.

# 2.16 12V and 5V Power Supply

The 100-pin SCSI-II connector provides +12 and +5 volt power sources. To avoid shorts or overloads of the power sources, thermistors are added to all power supply rails. The current rating of the +5 volt supply thermistor is 500 mA. If the load current is larger than 500mA, the resistance of the thermistors will increase due to the temperature rise. The rising resistance drops the supply voltage and hence reduces the current. If the overload or short condition is cleared, the thermistor will return to normal operation. The +12V supply thermistor also has the same current rating characteristics as the +5V supply.

# 3

# Registers

Detailed descriptions of the registers are specified in this chapter. This information is useful for programmers who wish to handle the card with low-level programming. However, we suggest users to an understanding of the PCI interface before starting any low-level programming. In addition, the contents of this chapter will also help users understand how to use the software drivers to configure this card.

# 3.1 PCI PnP Registers

This PCI card functions as a 32-bit PCI target device to any master on the PCI bus. There are three types of registers: PCI Configuration Registers (PCR), Local Configuration Registers (LCR) and cPCI/PCI-8554/R registers.

The PCR, which is PCI-bus specifications compliant, is initialized and controlled by the plug & play (PnP) PCI BIOS. Users may obtain more information on the PCI BIOS specification to better understand the operation of the PCR. Please contact PCISIG to acquire the specifications of the PCI interface.

The PCI bus controller PCI-9030/9050 is provided by PLX technology Inc. (www.plxtech.com). For more information about the LCR, please visit PLX technology’s web site to download relative information. It is not necessary for users to fully understand the details of the LCR if the software library provided is used. The PCI PnP BIOS assigns the base address of the LCR. The assigned address is located at an offset of 14h from the PCR.

The cPCI/PCI-8554/R registers are discussed in the next section. The base address, which is also assigned by the PCI PnP BIOS, is located at an offset of 18h from the PCR. Therefore, users can read the address 18h from the PCR to obtain its base address by using the BIOS function call. Do not attempt to modify the base address and interrupt that have been assigned by the PCI PnP BIOS, it may cause resource conflicts with your system.

# 3.2 I/O Address Map

All cPCI/PCI-8554/R registers are 8 bits long. Users can access these registers using 8-bit I/O instructions. The following table shows the registers address map, including descriptions and their offset addresses relative to the base address.

<table><tr><td>I/O Address</td><td>Write</td><td>Read</td></tr><tr><td>Base + 0x00 ~ 0x03</td><td>Counter 1~3 &amp; Mode Control</td><td>Counter 1 ~ 3</td></tr><tr><td>Base + 0x04 ~ 0x07</td><td>Counter 4~6 &amp; Mode Control</td><td>Counter 4 ~ 6</td></tr><tr><td>Base + 0x08 ~ 0x0B</td><td>Counter 7~9 &amp; Mode Control</td><td>Counter 7 ~ 9</td></tr><tr><td>Base + 0x0C ~0x0F</td><td>Counter 10~12 &amp; Mode Control</td><td>Counter 10 ~ 12</td></tr><tr><td>Base + 0x10 ~ 0x12</td><td>Clock Mode Control</td><td>--</td></tr><tr><td>Base + 0x18</td><td>Digital Output</td><td>Digital Input</td></tr></table>

Table 4. I/O Address Map of cPCI/PCI-8554/R

# 3.3 Timer/Counter Registers

The 8254-chips occupies 4 I/O address locations on the cPCI/PCI-8554/R as shown below. Users can refer to Tundra's or Intel's data sheet for a full description of the 8254 features available at the following websites: “http://support.intel.com/support/controllers/peripheral/231164.htm” or http://www.tundra.com (for Tundra’s 82C54 datasheet.)

Address: BASE + 0x00 \~ BASE + 0x0F

Attribute: read / write

Data Format:

<table><tr><td>Base + 0</td><td>Counter 1 Register (R/W)</td></tr><tr><td>Base + 1</td><td>Counter 2 Register (R/W)</td></tr><tr><td>Base + 2</td><td>Counter 3 Register (R/W)</td></tr><tr><td>Base + 3</td><td>8254 Mode Control Register (W)8254 Read Back Register (R)</td></tr><tr><td>Base + 4</td><td>Counter 4 Register (R/W)</td></tr><tr><td>Base + 5</td><td>Counter 5 Register (R/W)</td></tr><tr><td>Base + 6</td><td>Counter 6 Register (R/W)</td></tr><tr><td>Base + 7</td><td>8254 Mode Control Register (W)8254 Read Back Register (R)</td></tr><tr><td>Base + 8</td><td>Counter 7 Register (R/W)</td></tr><tr><td>Base + 9</td><td>Counter 8 Register (R/W)</td></tr><tr><td>Base + A</td><td>Counter 9 Register (R/W)</td></tr><tr><td>Base + B</td><td>8254 Mode Control Register (W)8254 Read Back Register (R)</td></tr><tr><td>Base + C</td><td>Counter 10 Register (R/W)</td></tr><tr><td>Base + D</td><td>Counter 11 Register (R/W)</td></tr><tr><td>Base + E</td><td>Counter 12 Register (R/W)</td></tr><tr><td>Base + F</td><td>8254 Mode Control Register (W)8254 Read Back Register (R)</td></tr></table>

Table 5. Timer/Counter Registers

# 3.4 Timer / Counter Clock Mode Control

There are a total of twenty-two bits on the cPCI/PCI-8554/R used for selecting clock sources for Timer/Counter 1 \~ 10, CK1 and the debounce system.

Address: BASE + 0x10 \~ 0x12

Attribute: write only

Data Format:

<table><tr><td>Bit</td><td>7</td><td>6</td><td>5</td><td>4</td><td>3</td><td>2</td><td>1</td><td>0</td></tr><tr><td>Base+0x10</td><td>C4N2</td><td>C4N1</td><td>C3N2</td><td>C3N1</td><td>C2N2</td><td>C2N1</td><td>C1N2</td><td>C1N1</td></tr><tr><td>Base+0x11</td><td>C8N2</td><td>C8N1</td><td>C7N2</td><td>C7N1</td><td>C6N2</td><td>C6N1</td><td>C5N2</td><td>C5N1</td></tr><tr><td>Base+0x12</td><td>-</td><td>DBCSEL</td><td>-</td><td>CK1SEL</td><td>C10N2</td><td>C10N1</td><td>C9N2</td><td>C9N1</td></tr></table>

Table 6. Timer/Counter Clock Mode Control Register

CnN1and CnN2: These two bits are used to control clock source of Timer/Counter n, n = 1 \~ 10

CK1SEL: select source of CK1

DBCSEL: select debounce clock

# 3.5 Digital Input Register

There are 8 digital input channels on the cPCI/PCI-8554/R.

Address: BASE + 0x18

Attribute: read only

Data Format:

<table><tr><td>Bit</td><td>7</td><td>6</td><td>5</td><td>4</td><td>3</td><td>2</td><td>1</td><td>0</td></tr><tr><td>Base+0x18</td><td>DI7</td><td>DI6</td><td>DI5</td><td>DI4</td><td>DI3</td><td>DI2</td><td>DI1</td><td>DI0</td></tr></table>

Table 7. Digital Input Register

# 3.6 Digital Output Register

This register is a general-purpose 8 bits digital output port. These signals can be used to control external devices.

Address: BASE + 0x18

Attribute: write only

Data Format:

<table><tr><td>Bit</td><td>7</td><td>6</td><td>5</td><td>4</td><td>3</td><td>2</td><td>1</td><td>0</td></tr><tr><td>Base+0x18</td><td>DO7</td><td>DO6</td><td>DO5</td><td>DO4</td><td>DO3</td><td>DO2</td><td>DO1</td><td>DO0</td></tr></table>

Table 8. Digital Output Register

# 4

# Signal Connections & Applications

This chapter describes the connectors and applications of the cPCI/PCI-8554/R including signal connections between the cPCI/PCI-8554/R and external devices.

# 4.1 Connectors Pin Assignment

The cPCI/PCI-8554/R comes equipped with a 100-pin SCSI-II female connector (CN1). CN1 is located at the rear plate. The pin assignment of the connector is illustrated in the Figure 4 and 5 of section 2.1.

# 4.2 Digital I/O Connection

The cPCI/PCI-8554/R provides 8 digital input and 8 digital output channels through CN1. The digital I/O signals are fully TTL compatible.

![Digital Input(DI)\nFrom TTL Devices\nDigital Output (DO)\nTo TTL Devices\nGND\nCPCI/PCI-8554/R\nOutside Device](.pci-8554-manual-4/c496f57fb2b96d91c7920915b3027345028d39fa3893741b9ca394853bd522a3.jpg)

Figure 19: Digital I/O Connection

# 4.3 Timer/Counter Connection

The cPCI/PCI-8554/R has four 8254 chips on board. It can offer 10 independent 16-bit programmable down counters with the option of cascading the counters. To implement your application, the following procedures should be followed.

1. Does the application require a fixed frequency, if answer is ‘No’, an external clock source must be used. Go to step 3.
2. Calculate the frequency of the clock according to your application requirements, then decide which clock source to use (internal, external, or cascaded), and then decide which counters to use.
3. If an external clock source is chosen, generate a clock signal external to the cPCI/PCI-8554/R card and measure its frequency. Determine whether the debounce function should be enabled or disabled, and then set JP1 \~ JP10. If reserved counters 11 and 12 are required, set JP12 and JP13 to pin 2-3.
4. Decide the gate control source: always enable or external controls, if gate control is necessary, connect the gate signal.

Note: Gate control of counter 11 and 12 are always enabled (tied to logic high) and there are no gate control pins for counters 11 and 12 on CN1.

5. Program the counter/timer using the desired mode.

# 4.4 Frequency Generator

# 4.4.1 To generate a 250 KHz Square Wave.

Step 1: Use a fixed clock source because the output is a fixed frequency.

Step 2: The internal 8MHz clock is capable of generating the 250KHz frequency. Use Counter 1 for this application.

$$
\therefore 2 5 0 \mathrm{kHz} = 8 \mathrm{MHz} / 3 2
$$

Step 3: The gate source should be set to “enable” always and therefore GATE1 is let open (pin 99 of CN1).

Step 4: Connect the counter output to an external device and write the control program. Refer to ‘DEMO1.C’ source code.

![This block diagram illustrates a clock signal routing path leading to a counter.\n\n**Labeled Blocks and Connections:**\n\n*   **First Switch (Multiplexer):**\n    *   **Control:** Labeled `set by function '_8554_SET_CK1'` with an arrow pointing to the switch mechanism.\n    *   **Inputs:**\n        *   Left side: `8MHz`, `COUT11`, and an empty terminal.\n        *   Right side: `ECK1`, `GND`, `CK1`, `COUT10` (indicated by arrows pointing into terminals).\n    *   **Output:** A line connects the output of this switch to the input of the second switch.\n\n*   **Second Switch (Multiplexer):**\n    *   **Control:** Labeled `set by function '8554_SET_cntCLK'` with an arrow pointing to the switch mechanism.\n    *   **Inputs:**\n        *   Top input: Connected to the output of the first switch.\n        *   Bottom input: Connected to the signal labeled `CK1` (indicated by an arrow).\n    *   **Output:** A line connects the output of this switch to the 'C' input of the counter block.\n\n*   **Counter Block:**\n    *   **Label:** A rectangular block labeled `Counter #1` inside a box labeled `8254 Chip #1`.\n    *   **Input 'C':** Connected to the output of the second switch.\n    *   **Input 'G':** Connected to the signal labeled `'H'`.\n    *   **Output 'O':** Connected to the output signal `COUT1` (indicated by a thick arrow pointing right).](.pci-8554-manual-4/b56ce8c0fb9491427264ee499f7db6e33bbab9a998f2c2226a188cf848c6a76b.jpg)

Figure 20: Example of a frequency generator (1)

# 4.4.2 To generate a 1 pulse/1 hour signal

Step 1: Use a fixed clock source because the output is a fixed frequency.

Step 2: As the desired frequency is too slow, one counter will be unable to produce the desired frequency (1/3600sec=0.000278Hz. Therefore to reach this low frequency, cascade the independent counters 1, 2 and 3. Set the clock source of counter 1 to the internal 8MHz. Connect COUT1 to clock source of counter 2, and connect COUT2 to clock source of counter 3.

Step 3: Using the counter divider function, set counter 1 to 4000, counter 2 to 2000, and counter 3 to 3600.

$$
\therefore 8 \mathrm{MHz} / 4 0 0 0 / 2 0 0 0 / 3 6 0 0 = 1 / 3 6 0 0,
$$

Hence COUT3 will generate a pulse every hour.

Step 4: The gate sources to enable always, hence GATE1, GATE2, and GATE3 are open.

Step 5: Write and verify the control program. Refer to ‘DEMO2.C’ source code.

![This diagram depicts a cascaded system of three counters (Counter #1, Counter #2, and Counter #3) on a single 8254 Chip. Each counter has two stages of switching before its clock input.\n\n**Top Section (Counter #1)**\n*   **Inputs:** The signals `8MHz` and `COUT11` feed into a small circular node. This node connects to a switch. Other inputs to this same switch node are `ECK1`, `GND`, `CK1`, and `COUT10`.\n*   **First Switch:** This switch is controlled by `set by function '_8554_SET_Ck1'`.\n*   **Second Switch:** The output of the first switch feeds a second switch node. This switch is controlled by `set by function '8554_SET_cntCLK'` and selects between `'H'` and `X`.\n*   **Block:** The output goes to a block labeled `8254 Chip #1` and `Counter #1`.\n*   **Output:** The block outputs `COUT1`.\n\n**Middle Section (Counter #2)**\n*   **Inputs:** The `COUT1` signal from Counter #1 loops back to a switch node. Other inputs to this node are `ECK2`, `COUT1`, `CK1`, and `COUT10`.\n*   **Second Switch:** The output of this switch feeds a second switch node. This switch is controlled by `set by function '8554_SET_cntCLK'` and selects between `'H'` and `X`.\n*   **Block:** The output goes to a block labeled `8254 Chip #1` and `Counter #2`.\n*   **Output:** The block outputs `COUT2`.\n\n**Bottom Section (Counter #3)**\n*   **Inputs:** The `COUT2` signal from Counter #2 loops back to a switch node. Other inputs to this node are `ECK3`, `COUT2`, `CK1`, and `COUT10`.\n*   **Second Switch:** The output of this switch feeds a second switch node. This switch is controlled by `set by function '8554_SET_cntCLK'` and selects between `'H'` and `X`.\n*   **Block:** The output goes to a block labeled `8254 Chip #1` and `Counter #3`.\n*   **Output:** The block outputs `COUT3`.](.pci-8554-manual-4/81ea1f538f8de4d3f414fae0c878e5a8e0327b1dc21c8a3b63fd64edf18fba88.jpg)

Figure 21: Example of frequency generator (2)

# 4.5 Pulse Width Measurement

Step 1: Use a fixed clock source as base time interval (or base frequency).

Step 2: Assuming an internal 2MHz clock is used. The time base is:

$$
\Delta t = 1 / 2 \mathrm{M} = 5 \times 1 0 \mathrm{e} - 7 \sec
$$

The count range for measuring the pulse width is:

$$
\Delta t &lt;   \text { pulse   width } &lt;   \Delta t * 6 5 5 3 5 (= 3 2. 7 6 8 \mathrm{msec})
$$

If the specification of the pulse width to be measured is within the range, the 2MHz can be used. Otherwise change the base frequency of the counter, for example, you can set counter 2 to cascaded mode, and use counter 2 to measure the pulse width. The count range will increase but the resolution will decrease. Counter 1, 2, and 3 are used in this example.

Step 3: Connect GATE1 to the signal to be measured.

Step 4: Write and verify the control program. Refer to ‘DEMO3.C’ source code.

![The diagram illustrates a signal measurement and clock selection circuit involving a counter and debounce system.\n\n**Labeled Blocks:**\n*   **debounce system**: A rectangular block processing clock signals.\n*   **JP1**: A connector block with four pins.\n*   **8254 Chip #1**: A rectangular block labeled internally as 'Counter #1'. It has inputs labeled 'c' and 'G', and an output labeled 'o'.\n*   **Two Switches**: Represented by circular symbols with lever arms. One is located between JP1 and the counter, and the other is located between signal sources and the debounce system.\n\n**Connections and Text:**\n*   **Clock Selection (Top Right):**\n    *   **JP1** provides four signals to a switch: **ECLK1**, **GND**, **CK1**, and **COUT10**.\n    *   The output of this switch connects to the **'c'** input of the **8254 Chip #1**.\n    *   A label pointing to this switch reads: `set by function '_8554_SET_cntCLK'`.\n*   **Debounce System (Top Left):**\n    *   **ECLK1** enters from the top into the **debounce system**.\n    *   The **debounce system** outputs a signal labeled **DB_CLK** (arrow pointing up) which feeds into the bottom switch. Wait, looking closer at the diagram, the **DB_CLK** label is on a line going UP to the switch connected to JP1? No, the line labeled **DB_CLK** goes from the bottom switch UP to the **debounce system**.\n    *   Actually, tracing the lines:\n        *   The **debounce system** receives **ECLK1** (from top) and **DB_CLK** (from bottom).\n        *   The **debounce system** has an output that goes to the switch connected to **JP1**. Wait, let's re-trace.\n        *   The line from the **debounce system** goes to the switch connected to **JP1**.\n        *   The switch connected to **JP1** selects between **ECLK1**, **GND**, **CK1**, **COUT10** (from JP1) and the output of the debounce system? No, the switch has 4 inputs from JP1.\n        *   Let's look at the bottom left switch.\n        *   **Bottom Left Switch:**\n            *   Inputs: **2MHz** and **COUT11**.\n            *   Output: **DB_CLK**.\n            *   Label: `selectable by function '_8554_SET_DBCLK'`.\n            *   The **DB_CLK** output goes UP into the **debounce system**.\n*   **Counter Input (Gate):**\n    *   The **'G'** input of the **8254 Chip #1** is connected to a line labeled **Signal to be measured**.\n    *   Below this line is a pulse diagram showing a pulse.\n    *   An arrow points to the end of the pulse with the label: `Polling D/I for c end of a pulse`.\n    *   Double arrows below the pulse indicate **Pulse Width**.\n*   **Counter Output:**\n    *   The **'o'** output of the **8254 Chip #1** is labeled **COUT1**.](.pci-8554-manual-4/2141faf8e48c61530dd94ba0f7ad7c80c95c9232400b9c1b915fb73f63973ea7.jpg)

Figure 22: Example of pulse width measurement

# 4.6 Frequency Measurement

To measure a frequency around 1\~100 KHz the following steps can be followed.

Step 1: This application requires two counters. One counter is used to generate a pulse with a precise time interval. The pulse is then used to enable the second counter (Counting counter). In this example the gate control is from COUT3 and cascaded counters configuration is used. The pulse generator is set to counter 3 (clock from COUT2) and counter 1 is used to measure the frequency.
Step 2: The maximum value of the counting counter is 65535. To measure a 100 KHz signal, the time interval must be within 1/100 KHz x 65535 = 0.655 seconds. If the time interval is wider, then the measurement resolution is better, however, the counting value will overflow if the time interval is too large. This means the low pulse width for counter 3 output should be shorter than 0.655 sec.
Step 3: Connect the signal to be measured to ECLK1 and adjust JP1 to allow the debounce function.
Step 4: Connect GATE1 to /COUT3.
Step 5: The following block diagram illustrates the application. Write and verify the control program. The frequency of the signal is:
Frequency = Counting value of counter 1/precise time interval
Refer to ‘DEMO4.C’ source code.

![This block diagram illustrates a digital circuit using two instances of an 8254 Chip, labeled as counters, along with clock selection logic and a debounce system.\n\n**Labeled Blocks:**\n*   **8254 Chip #1** (containing **Counter #2**) - Located at the top right.\n*   **8254 Chip #1** (containing **Counter #1**) - Located at the middle right.\n*   **debounce system** - Located at the middle left.\n*   **JP1** - A connector header located near the input pins.\n\n**Connections and Signals:**\n\n**Top Section (Counter #2):**\n*   **Inputs:** The block has inputs labeled **C** (clock) and **G** (gate), and an output labeled **o**.\n*   **Clock Path (C):**\n    *   A signal path originates from **8MHz** and **COUT11**, passing through a switch controlled by 'set by function '_8554_SET_CK1''.\n    *   This signal enters a switch controlled by 'set by function '_8554_SET_cntCLK''.\n    *   This switch also has inputs labeled **ECLK2**, **COUT1**, **CK1**, and **COUT10**.\n    *   The output of this switch goes through a buffer (inverter symbol) to the **C** input of **Counter #2**.\n*   **Gate Path (G):** Connected to a switch labeled **'H'**.\n*   **Output:** The output **COUT2** is labeled with '**Precis Time Interv**'.\n\n**Bottom Section (Counter #1):**\n*   **Inputs:** The block has inputs labeled **C**, **G**, and an output labeled **o**.\n*   **Clock Path (C):**\n    *   A signal path originates from the debounce logic. **ECLK1** (labeled 'frequency to be measured') goes into the **debounce system**, which outputs **DB_CLK**.\n    *   **DB_CLK** connects to a switch controlled by 'selectable by function '_8554_SET_DBCLK''.\n    *   Inputs to this switch include **2MHz** and **COUT11** (passing through a switch).\n    *   This signal enters a switch controlled by 'set by function '_8554_SET_cntCLK''.\n    *   This switch also has inputs labeled **ECLK1**, **GND**, **CK1**, and **COUT10**.\n    *   The output goes through a buffer to the **C** input of **Counter #1**.\n*   **Gate Path (G):** Connected to an inverter. The inverter input comes from a dashed box labeled **/COUT2** (derived from **COUT2**). A label '**'H' enable counter #1**' is near this connection.\n*   **Output:** Labeled **COUT1**.\n\n**Other Labels:**\n*   **connect by** - Located at the bottom right.](.pci-8554-manual-4/d1fd8ab2f3007b08e96fde7d9eac47f8209ffba2025f86601671a7e4df3d8e86.jpg)

Figure 23: Example of frequency measurement (1)

# 4.7 Event Counter

This example counts how many external events in 1 second

Step 1: This application requires one counter to generate a time base of 1 second and the second counter to count the event. Cascaded counters 11and 12 are used as a watchdog timer. Counter 1 is used in this example to count the external events. The clock source of counter 1 is the event signal so the frequency is not fixed.

Step 2: Connect ECLK1 to the signal to be measured and adjust JP1 to enable the debounce function.

Step 4: The gate source of counter 1 is always enabled, so the external gate is open.

Step 5: Write the control program. Refer to‘DEMO5.C’ source code.

![The diagram illustrates signal routing and counting logic with the following blocks and connections:\n\n**Top Section:**\n*   **Input:** 'ECLK1 ( Event Signal )' feeds into the **debounce system**.\n*   **Switch (Bottom Left):** A switch labeled **'selectable by function '_8554_SET_DBCLK''** selects between inputs **'2MHz'** and **'COUT11'**. The output is labeled **'DB_CLK'** and feeds into the **debounce system**.\n*   **Connector:** The **debounce system** connects to a 2-pin header labeled **JP1**.\n\n**Middle Section:**\n*   **Switch:** A switch labeled **'selectable by function'** selects one of four inputs: **'ECK1'**, **'GND'**, **'CK1'**, or **'COUT10'**.\n*   **Counter #1:** The selected signal from the switch connects to the **'c'** input of the block labeled **'8254 Chip #1'** (containing **'Counter #1'**). The **'G'** input is connected to **''H''. The output is labeled **'COUT1'**.\n\n**Bottom Section:**\n*   **Counter #11:** The block labeled **'8254 Chip #4'** contains **'Counter #11'**. It receives **'8MHz'** at the **'c'** input and **''H''** at the **'G'** input. Its output connects to the next counter.\n*   **Counter #12:** The block labeled **'8254 Chip #4'** contains **'Counter #12'**. It receives the output from Counter #11 at the **'c'** input and **''H''** at the **'G'** input. The final output is labeled **'COUT12'**.](.pci-8554-manual-4/58ab1bd602cf43d491346c0fa16bfce75bf21bad8f5096e0a71acb7807671ac6.jpg)

Figure 24: Example of event counter

# 4.8 Dual Interrupt System

The cPCI/PCI-8554/R provides a dual interrupt source (one internal plus one external), which can be very useful in some applications. For example, most applications require a watchdog timer to monitor the system periodically; hence, an IRQ channel is used. An emergency control may also be necessary; therefore the external IRQ channel will come in handy.

![Based on the provided flowchart, here is the accurate description of the labeled blocks and their connections:\n\n**Labeled Blocks:**\n*   **8254 Chip #4** (containing **Counter #11** and **Counter #12**)\n*   **IRQ Flip-Flops** (appears twice, once at the top and once in the middle-bottom)\n*   **debounce system**\n*   **JP11**\n*   **PCI Controller**\n\n**Connections and Signal Flow:**\n\n**Top Section (Counter Chain):**\n*   **'8MHz'** and **''H''** inputs enter **Counter #11** at pins labeled **C** and **G**, respectively.\n*   The **0** output of **Counter #11** connects to the **C** input of **Counter #12**.\n*   **''H'**' enters the **G** input of **Counter #12**.\n*   The **COUT12** output of **Counter #12** connects to the top **IRQ Flip-Flops**.\n*   A dotted arrow labeled **Clear by '8554_CLR_IRQ'** points to the top **IRQ Flip-Flops**.\n*   The output from the top **IRQ Flip-Flops** connects to the **INT1** input of the **PCI Controller**.\n\n**Bottom Section (Debounce Chain):**\n*   **E_INT** and **DB_CLK** inputs enter the **debounce system**.\n*   The **debounce system** connects to **JP11** (specifically to the top and bottom pins of the connector).\n*   **JP11** outputs a signal labeled **EXTINT** to the middle-bottom **IRQ Flip-Flops**.\n*   A dotted arrow labeled **Clear by '8554_CLR_IRQ2'** points to the middle-bottom **IRQ Flip-Flops**.\n*   The **INT2** output of the middle-bottom **IRQ Flip-Flops** connects to the **INT2** input of the **PCI Controller**.](.pci-8554-manual-4/e653a5cf8a63da082781865377c1625cf9d248d05f74a1456078443047db82aa.jpg)

Figure 25: Example of dual interrupt system

# 5

# C/C++ Library

This chapter describes the software libraries for operating this card. Only the functions in the DOS library and Windows 95 DLL are described. Refer to the PCIS-DASK function reference manual, which is included in the ADLINK CD, for descriptions of Windows 98/NT/2000 DLL functions.

The function prototypes and useful constants are defined in the header files located in the LIB directory (DOS) and INCLUDE directory (Windows 95). For Windows 95 DLL, the developing environment can be Visual Basic 4.0 or above, Visual C/C++ 4.0 or above, Borland C++ 5.0 or above, Borland Delphi 2.x (32-bit) or above, or any Windows programming language that allows calls to a DLL.

# 5.1 Libraries Installation

Refer to the “Software Installation Guide” for information regarding software installation of libraries for DOS, Windows 95 DLL, or PCIS-DASK for Windows 98/NT/2000.

The device drivers and DLL functions for Windows 98/NT/2000 are included in the PCIS-DASK. Refer to the PCIS-DASK user’s guide and function reference, which is included in the ADLINK CD, for programming information.

# 5.2 Programming Guide

# 5.2.1 Naming Convention

The functions of the NuDAQ PCI or NuIPC CompactPCI card software drivers uses full-names to represent the functions' real meaning. The naming convention rules are:

# In DOS Environment:

$\mathtt { \_ { ( h a r d w a r e \_ m o d e l ) \_ ( a c t i o n \_ n a m e ) . e . g . \_ 8 5 5 4 \_ l n i t i a l ( \lambda ) . } }$

In order to recognize the difference between the DOS library and Windows 95 library, a capital "W" is placed at the start of each function name for Windows 95 DLL drivers. e.g. W\_8554\_Initial().

# 5.2.2 Data Types

We have defined some data types in the Pci\_8554.h (DOS) and Acl\_pci.h (Windows 95) header files. These data types are used by the NuDAQ Cards’ library. We recommend you use these data types in your application programs. The following table shows the data type names and their range.

&lt;table&gt;<tr><td>Type Name</td><td>Description</td><td>Range</td></tr><tr><td>U8</td><td>8-bit ASCII character</td><td>0 to 255</td></tr><tr><td>I16</td><td>16-bit signed integer</td><td>-32768 to 32767</td></tr><tr><td>U16</td><td>16-bit unsigned integer</td><td>0 to 65535</td></tr><tr><td>I32</td><td>32-bit signed integer</td><td>-2147483648 to 2147483647</td></tr><tr><td>U32</td><td>32-bit single-precision floating-point</td><td>0 to 4294967295</td></tr><tr><td>F32</td><td>32-bit single-precision floating-point</td><td>-3.402823E38 to 3.402823E38</td></tr><tr><td>F64</td><td>64-bit double-precision floating-point</td><td>-1.797683134862315E308 to 1.797683134862315E309</td></tr><tr><td>Boolean</td><td>Boolean logic value</td><td>TRUE, FALSE</td></tr></table>

Table 9. Data types and their ranges

# 5.3 \_8554\_Initial

# @ Description

The cPCI/PCI-8554/R cards are initialized by this function. The software library could be used to control multiple cPCI/PCI-8554/R cards. Because the cPCI/PCI-8554/R is designed with the PCI bus architecture and meets the plug and play specifications, the IRQ and I/O address are assigned by system BIOS directly.

# @ Syntax

C/C++ (DOS)

U16 \_8554\_Initial (U16 \*existCards, PCI\_INFO \*pciinfo)

C/C++ (Windows 95)

U16 W\_8554\_Initial (U16 \*existCards, PCI\_INFO \*pciinfo)

# Visual Basic (Windows 95)

W\_8554\_Initial (existCards As Integer, pciInfo As PCI\_INFO) As Integer

# @ Arguments

existCards:

The numbers of installed cPCI/PCI-8554/R cards. The returned value shows how many cPCI/PCI-8554/R cards are installed in the system.

pciinfo:

This structure stores the PCI bus plug and play initialization information, which is determined by PnP BIOS. The PCI\_INFO structure is defined in the PCI\_8554.H header file. The base I/O address and the interrupt channel number is stored in pciinfo for reference.

# @ Return Value

ERR\_NoError, ERR\_PCIBiosNotExist

# 5.4 \_8554\_Write\_Counter

# @ Description

User can directly write commands to counters 1\~12 using this function. Using this function, user can also re-assign the counter numbers 1\~12 in any order

# @ Syntax

C/C++ (DOS)

U16 \_8554\_Write\_Counter (U16 cardNo, U16 cntNo, U16 mode, U16 cntrVal)

C/C++ (Windows 95)

U16 W\_8554\_Write\_Counter (U16 cardNo, U16 cntNo, U16 mode, U16 cntrVal)

# Visual Basic (Windows 95)

W\_8554\_Write\_Counter (ByVal cardNo As Integer, ByVal cntNo As Integer, ByVal mode As Integer, ByVal cntrVal As Integer) As Integer

# @ Arguments

cardNo: card number to be selected

cntNo: Counter/Timer number. This value must be between 1 and 12.

mode: Counter operation mode. This value must be between 0 and 5.

cntrVal: The counter value to be written to the counter.

# @ Return Value

ERR\_NoError

ERR\_BoardNoInit

ERR\_InvalidCounterNo: cntNo is out of range.

ERR\_TimerMode: mode is out of range

# 5.5 \_8554\_Read\_Counter

@ Description

User can directly read counter information with this function.

@ Syntax

```txt
C/C++ (DOS)
```

```csv
U16 _8554_Read_Counter (U16 cardNo, U16 cntNo, U16 *mode, U16 *cntrVal)
```

```txt
C/C++ (Windows 95)
```

```txt
U16 W_8554_Read_Counter (U16 cardNo, U16 cntNo, U16 *mode, U16 *cntrVal)
```

# Visual Basic (Windows 95)

W\_8554\_Read\_Counter (ByVal cardNo As Integer, ByVal cntNo As Integer, mode As Integer, cntrVal As Integer) As Integer

@ Arguments

cardNo: card number to be selected

cntNo: Counter/Timer number. This value must be between 1 and 12.

mode: Counter operation mode.

cntrVal: Counter value read back from counter

@ Return Value

ERR\_NoError, ERR\_BoardNoInit

ERR\_InvalidCounterNo: cntNo is out of range.

# 5.6 \_8554\_Stop\_Counter

# @ Description

User can directly stop the counter with this function. This function will stop the counter by setting the counter to mode 5.

# @ Syntax

```txt
C/C++ (DOS)
```

U16 \_8554\_Stop\_Counter (U16 cardNo,U16 cntNo,U16 \*cntrVal)

```txt
C/C++ (Windows 95)
```

U16 W\_8554\_Stop\_Counter (U16 cardNo,U16 cntNo,U16 \*cntrVal)

# Visual Basic (Windows 95)

W\_8554\_Stop\_Counter (ByVal cardNo As Integer, ByVal cntNo As Integer, cntrVal As Integer) As Integer

# @ Arguments

cardNo: card number to be selected

cntNo: Counter/Timer number. This value must be between 1 and 12.

cntrVal: Counter value read back from counter

# @ Return Value

ERR\_NoError , ERR\_BoardNoInit

ERR\_InvalidCounterNo: if cntNo is not in the range of 1 \~ 12

# 5.7 \_8554\_Read\_Status

@ Description

User can directly read current counter status with this function.

@ Syntax

C/C++ (DOS)

U16 \_8554\_Read\_Status (U16 cardNo, U16 cntNo, U16 \* cntrVal, U16 \*status)

C/C++ (Windows 95)

U16 W\_8554\_ Read\_Status (U16 cardNo, U16 cntNo, U16 \* cntrVal, U16 \*status)

Visual Basic (Windows 95)

W\_8554\_Read\_Status (ByVal cardNo As Integer, ByVal cntNo As Integer, cntrVal As Integer, status As Integer) As Integer

@ Arguments

cardNo: card number to be selected

cntNo: Counter/Timer number. This value must be between 1 and 12.

cntrVal: Counter value read back from counter

status: current status read back from counter, refer to 8254’s datasheet for more information

@ Return Value

ERR\_NoError, ERR\_BoardNoInit

ERR\_InvalidCounterNo: if cntNo is not in the range of 1 \~ 12

# 5.8 \_8554\_DO

@ Description

Write an 8-bit data to the digital output port.

@ Syntax

C/C++ (DOS)

U16 \_8554\_DO (U16 cardNo, U16 doData)

C/C++ (Windows 95)

U16 W\_8554\_DO (U16 cardNo, U16 doData)

Visual Basic (Windows 95)

W\_8554\_DO (ByVal cardNo As Integer, ByVal doData As Integer) As Integer

@ Arguments

cardNo: card number to be selected

doData: the value to be written to digital output port

@ Return Value

ERR\_NoError

ERR\_PCIBiosNotExist

# 5.9 \_8554\_DI

@ Description

Read an 8-bit data from the digital input port.

@ Syntax

C/C++ (DOS)

U16 \_8554\_DI (U16 cardNo, U16 \*diData)

C/C++ (Windows 95)

U16 W\_8554\_DI (U16 cardNo, U16 \*diData)

Visual Basic (Windows 95)

W\_8554\_DI (ByVal cardNo As Integer, diData As Integer) As Integer

@ Arguments

cardNo: card number to be selected

doData: the value read from the digital input port

@ Return Value

ERR\_NoError, ERR\_BoardNoInit

# 5.10 \_8554\_SET\_cntCLK

# @ Description

This function is used to select the clock source for counters 1\~10 (Clock source for counter 11 is 8MHz and clock source of counter 12 is from COUT11, both clock sources are fixed).

# @ Syntax

C/C++ (DOS)

U16 \_8554\_DI (U16 cardNo, U16 cntNo, U16 clkMODE)

C/C++ (Windows 95)

U16 W\_8554\_DI (U16 cardNo, U16 cntNo, U16 clkMODE)

# Visual Basic (Windows 95)

W\_8554\_SET\_cntCLK (ByVal cardNo As Integer, ByVal cntNo As Integer, ByVal clkMODE As Integer) As Integer

# @ Arguments

cardNo: card number to be selected

cntNo: Counter/Timer number. This value must be between 1 and 10.

clkMODE: Select clock sources:

$$
" 0" = \text { ECLKn }.
$$

$$
" 1" = \text { COUTn - 1 }.
$$

$$
" 2" = \mathrm{CK1}.
$$

$$
" 3" = \text { COUT10 }.
$$

# @ Return Value

ERR\_NoError

ERR\_BoardNoInit

ERR\_InvalidCounterNo: cntNo is not in the range of 1 \~ 12

ERR\_InvalidMode: clkMODE is not in the range of 0 \~ 3

# 5.11 \_8554\_SET\_CK1

@ Description

Select source for CK1.

@ Syntax

C/C++ (DOS)

U16 \_8554\_SET\_CK1 (U16 cardNo, U16 selCK1)

C/C++ (Windows 95)

U16 W\_8554\_SET\_CK1 (U16 cardNo, U16 selCK1)

Visual Basic (Windows 95)

W\_8554\_SET\_CK1 (ByVal cardNo As Integer, ByVal selCK1 As Integer) As Integer

@ Arguments

cardNo: card number to be selected

selCK1: if selCK1 is set to “0” then CK1 = C8M, and if set to “1” then CK1 = COUT11

@ Return Value

ERR\_NoError

ERR\_BoardNoInit

ERR\_InvalidMode: selCK1 is out of range

# 5.12 \_8554\_SET\_DBCLK

@ Description

Select debounce clock.

@ Syntax

C/C++ (DOS)

U16 \_8554\_SET\_DBCLK (U16 cardNo, U16 DBCLK)

C/C++ (Windows 95)

U16 W\_8554\_SET\_DBCLK (U16 cardNo, U16 DBCLK)

Visual Basic (Windows 95)

W\_8554\_SET\_DBCLK (ByVal cardNo As Integer, ByVal DBCLK As Integer) As Integer

@ Arguments

cardNo: card number to be selected

DBCLK: if dbclk is set to “0” then DB\_CLK = COUT11, and if set to “1” then DB\_CLK = 2MHz

@ Return Value

ERR\_NoErro, ERR\_BoardNoInit

ERR\_InvalidMode: DBCLK is out of range

# 5.13 \_8554\_Set\_INT\_Control

# @ Description

The cPCI/PCI-8554/R has a dual interrupts system. Two interrupt sources can be generated and be checked by the software. This function is used to select and control the cPCI/PCI-8554/R interrupt sources. The interrupt source can either come from counter 12’s output, COUT12 (INT1) or from an external interrupt signal EXTINT (INT2).

# @ Syntax

C/C++ (DOS)

U16 \_8554\_Set\_INT\_Control (U16 cardNo, U16 int1Flag, U16 int2Flag)

C/C++ (Windows 95)

U16 W\_8554\_Set\_INT\_Control (U16 cardNo, U16 int1Flag, U16 int2Flag)

# Visual Basic (Windows 95)

W\_8554\_Set\_INT\_Control (ByVal cardNo As Integer, ByVal int1Falg As Integer, ByVal int2Falg As Integer)

# @ Arguments

cardNo: card number to be selected

int1Flag: INT1 setting; 0: disable, 1: enable

int2Flag: INT2 setting; 0: disable, 1: enable

# 5.14 \_8554\_Get\_IRQ\_Status

# @ Description

The cPCI/PCI-8554/R has dual interrupts system. Two interrupt sources can be generated and be checked by the software. This function is used to distinguish which interrupt has been inserted if both INT1 and INT2 interrupts are used.

# @ Syntax

```txt
C/C++ (DOS)
```

U16 \_8554\_Get\_IRQ\_Status (U16 cardNo, U16 \*ch1, U16 \*ch2)

```txt
C/C++ (Windows 95)
```

U16 W\_8554\_Get\_IRQ\_Status (U16 cardNo, U16 \*ch1, U16 \*ch2)

# Visual Basic (Windows 95)

W\_8554\_Get\_IRQ\_Status (ByVal cardNo As Integer, ch1 As Integer, ch2 As Integer)

# @ Arguments

cardNo: card number to be selected

ch1: INT1 status; 0: interrupt is not from INT1, 1: interrupt is from INT1

ch2: INT2 status; 0: interrupt is not from INT2, 1: interrupt is from INT2

# 5.15 \_8554\_INT\_Enable

# @ Description

This function is only available to the Windows 95 driver. It is used to activate the interrupt controller. After calling this function, every time an interrupt request signal is generated, a software event is signaled.

# @ Syntax

C/C++ (Windows 95)

U16 W\_8554\_INT\_Enable (U16 cardNo, HANDLE \*hEvent)

# Visual Basic (Windows 95)

W\_8554\_INT\_Enable (ByVal cardNo As Integer, hEvent As Long) As Integer

# @ Arguments

cardNo: card number to be selected

hEvent: the address of an array for two handles. HEvent[0] and hEvent[1] are the events for interrupt signals INT1 and INT2 respectively.

# @ Return Value

ERR\_NoError

ERR\_BoardNoInit

# 5.16 \_8554\_INT\_Disable

@ Description

This function is only available to the Windows 95 driver. It is used to disable the generation of an interrupt signal.

@ Syntax

C/C++ (Windows 95)

U16 W\_8554\_INT\_Disable (U16 cardNo)

Visual Basic (Windows 95)

W\_8554\_INT\_Disable (ByVal cardNo As Integer) As Integer

@ Arguments

cardNo: card number to be selected

@ Return Value

ERR\_NoError, ERR\_BoardNoInit

# 5.17 \_8554\_CLR\_IRQ1

@ Description

This function is only available to the DOS driver. It is used to clear the interrupt request, which is generated by INT1. You should use this function to clear the interrupt request status; otherwise the new incoming interrupt will not be generated.

@ Syntax

C/C++ (Windows 95)

U16 \_8554\_CLR\_IRQ1 (U16 cardNo)

@ Arguments

cardNo: card number to be selected

# 5.18 \_8554\_CLR\_IRQ2

# @ Description

This function is only available to the DOS driver. It is used to clear the interrupt request, which is generated by INT2. You should use this function to clear the interrupt request status; otherwise the new incoming interrupt will not be generated.

# @ Syntax

C/C++ (Windows 95)

U16 \_8554\_CLR\_IRQ2 (U16 cardNo)

# @ Arguments

cardNo: card number to be selected

# Warranty Policy

Thank you for choosing ADLINK. To understand your rights and enjoy all the after-sales services we offer, please read the following carefully.

1. Before using ADLINK’s products please read the user manual and follow the instructions exactly. When sending in damaged products for repair, please attach an RMA application form which can be downloaded from: http://rma.adlinktech.com/policy/.
2. All ADLINK products come with a limited two-year warranty, one year for products bought in China.

The warranty period starts on the day the product is shipped from ADLINK’s factory.
Peripherals and third-party products not manufactured by ADLINK will be covered by the original manufacturers' warranty.
For products containing storage devices (hard drives, flash cards, etc.), please back up your data before sending them for repair. ADLINK is not responsible for any loss of data.
Please ensure the use of properly licensed software with our systems. ADLINK does not condone the use of pirated software and will not service systems using such software. ADLINK will not be held legally responsible for products shipped with unlicensed software installed by the user.
For general repairs, please do not include peripheral accessories. If peripherals need to be included, be certain to specify which items you sent on the RMA Request & Confirmation Form. ADLINK is not responsible for items not listed on the RMA Request & Confirmation Form.

3. Our repair service is not covered by ADLINK's guarantee in the following situations:

Damage caused by not following instructions in the User's Manual.
Damage caused by carelessness on the user's part during product transportation.
Damage caused by fire, earthquakes, floods, lightening, pollution, other acts of God, and/or incorrect usage of voltage transformers.

Damage caused by inappropriate storage environments such as with high temperatures, high humidity, or volatile chemicals.
Damage caused by leakage of battery fluid during or after change of batteries by customer/user.
Damage from improper repair by unauthorized ADLINK technicians.
Products with altered and/or damaged serial numbers are not entitled to our service.
This warranty is not transferable or extendible.
Other categories not protected under our warranty.

4. Customers are responsible for all fees necessary to transport damaged products to ADLINK.

For further questions, please e-mail our FAE staff: service@adlinktech.com
[🔗 Link to the original document](.pci-8554-manual-4/pci-8554-manual-4.pdf)