English dropdown-ico

Omega Engineering EN-EIC-325-PCI manual

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43

Go to page of

Similar user manuals

A good user manual

The rules should oblige the seller to give the purchaser an operating instrucion of Omega Engineering EN-EIC-325-PCI, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.

What is an instruction?

The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of Omega Engineering EN-EIC-325-PCI one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.

Unfortunately, only a few customers devote their time to read an instruction of Omega Engineering EN-EIC-325-PCI. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.

What should a perfect user manual contain?

First and foremost, an user manual of Omega Engineering EN-EIC-325-PCI should contain:
- informations concerning technical data of Omega Engineering EN-EIC-325-PCI
- name of the manufacturer and a year of construction of the Omega Engineering EN-EIC-325-PCI item
- rules of operation, control and maintenance of the Omega Engineering EN-EIC-325-PCI item
- safety signs and mark certificates which confirm compatibility with appropriate standards

Why don't we read the manuals?

Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of Omega Engineering EN-EIC-325-PCI alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of Omega Engineering EN-EIC-325-PCI, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the Omega Engineering service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of Omega Engineering EN-EIC-325-PCI.

Why one should read the manuals?

It is mostly in the manuals where we will find the details concerning construction and possibility of the Omega Engineering EN-EIC-325-PCI item, and its use of respective accessory, as well as information concerning all the functions and facilities.

After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.

Table of contents for the manual

  • Page 1

    omega.com e-mail: info@omega.com For latest product manuals: omegamanual.info EN-EIC-325-PCI Four Axis PCI Encoder Inter face Card Shop online at U ser ’ s Guide[...]

  • Page 2

    Servicing Nor th America: U.S.A.: One Omega Drive, P.O. Box 4047 ISO 9001 Certified Stamford, CT 06907-0047 TEL: (203) 359-1660 FAX: (203) 359-7700 e-mail: info@omega.com Canada: 976 Bergar Laval (Quebec) H7L 5A1, Canada TEL: (514) 856-6928 FAX: (514) 856-6886 e-mail: info@omega.ca For immediate technical or application assistance: U.S.A. and Canad[...]

  • Page 3

    1 FOUR AXIS ENCODER INTERFACE CARD M M M O O O D D D E E E L L L Version 2.01, Oct. 2003[...]

  • Page 4

    2 TABLE of CONTENTS Section Page 1 GENERAL DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 ENCODER INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1.1 IPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1.2 SOFTWARE OUTPUTS . . . . . . . . . . . . . . . [...]

  • Page 5

    3 1. GENERAL DESCRIPTION • The EN-EIC-325-PCI handles four axes of user's encoders. Each user's encoder is directly attached to the Encoder Interface on the card. • The EN-EIC-325-PCI includes eleven logical inputs, and three general outputs. • The EN-EIC-325-PCI is I/O mapped. 1.1. ENCODER INTERFACE Note: Each of the registers IPC,[...]

  • Page 6

    4 1.1.3. SOFTWARE INPUTS a. Data Request to request an XPC update. For example, upon Data Request on the A axis, the following operation is done: XPC A ⇐ IPC A Notes: 1. Data Request may be applied on a single axis, or (all at once) on: axes pair (A+B or C+D), or all four axes. 2. Besides this software Data Request , there is also a hardware (rea[...]

  • Page 7

    5 2.2. PIN LAY-OUT The drawings of the input/output connections are in Appendix B. Encoder Inputs Function D-Type 44 pin No. Vcc 31 Index+ 17 GND 2 Index– 32 Sine– / Phase A– 18 Sine+ / Phase A+ 3 Cosine+ / Phase B+ 33 Encoder A Cosine– / Phase B– 4 GND 20 Vcc 5 Index+ 35 Sine+ / Phase A+ 21 Index– 6 Sine– / Phase A– 36 Cosine– / [...]

  • Page 8

    6 Logical Inputs Function D-Type 44 pin No. Input #2 16 Input #1 1 Input #3 19 Input #4 34 Input #5 37 Input #11 8 Input #7 26 Input #6 11 Input #8 29 Input #9 44 Input #10 15 GND 30 ENCODERS' EVENT SIGNALS AND GENERAL OUTPUTS Function D-Type 9 pin No. VExt+ 1 Encoder A 6 Encoder B 2 Encoder C 7 Event Signal Encoder D 3 Output #1 8 Output #2 4[...]

  • Page 9

    7 3. SOFTWARE INTERFACE WITH THE CARD 3.1. INSTALLATION The main files and folders of the software package are as follows: Win95_98 Install.exe WRTdevN.VxD (Ten files: N=0,...,9) ImsEncPci.ocx VB VC WinNT WinRT.sys ImsEic325-PCINT4.reg Win2K EIC325_P.sys ImsEic325-PCIWDM.inf WinXP EIC325_P.sys ImsEic325-PCIWDM.inf OCX for WinNT/2K/XP ImsEncPci.ocx [...]

  • Page 10

    8 The VB folders The VB folders include an illustration program, which is essential for any user, not only the VB programmer. For any environment you are using – refer to the relevant VB folder. Note: If Visual Basic is NOT installed on your computer, then before running the (VB produced) program EncPciTest.exe (recommended), please verify that: [...]

  • Page 11

    9 3.1.1. Windows The various Windows folders supply the files required for the driver installation. The Win95/98 driver includes an ActiveX control. The WinNT/2K/XP drivers include two options: an ActiveX control and a DLL. The DLL uses the popular ‘stdcall’ calling convention recognizable by VB, VC, Delphi etc. The ActiveX control and the DLL [...]

  • Page 12

    10 WinNT/2K/XP • ActiveX Control Copy the .ocx file from your ‘OCX for WinNT_2K_XP’ folder to your WinSysPath folder and register it by Start, Run, 'regsvr32 WinSysPath ImsEncPci.ocx'. • DLL Copy the .dll file from your ‘DLL for WinNT_2K_XP’ folder to your WinSysPath folder. WinSysPath is:[...]

  • Page 13

    11 3.1.2. VB Select the ‘VB’ folder that corresponds to your driver installation (section 3.1.1). You'll find here a full illustration in VB 5.0 (named "EncPciTest") that demonstrates how to use the various functions to communicate with the card. There are two versions: one using the ActiveX control, the other using the DLL. The [...]

  • Page 14

    12 • The display of the Hardware EventFlags Output reflects what SHOULD be in these outputs analyzing the Software EventFlags Outputs as well as user's operations that may affect the Hardware EventFlags Output, as described in section 3.5.4, functions #22 and #24. Actually, the EncPciTest program simulates card's response and concludes [...]

  • Page 15

    13 3.2. INTRODUCTION TO THE FUNCTIONS Each encoders pair is handled by a "chip": Chip #1 includes Encoder Interfaces A and B. Chip #2 includes Encoder Interfaces C and D. The following functions serve the DOS C/C++ programmer as well as the Windows programmer. • The DOS C/C++ programmer should include EncPci.h in his source file, and En[...]

  • Page 16

    14 3.3. CARD LEVEL FUNCTIONS # Brief Description Name Arguments (in C Syntax) Full Description 1 Supply a ‘Card Handle’ to the n-th EN- EIC-325-PCI card (if exists). (First n is 0.) GetCardHandle (long* CardHandle , short CardIndex ) Call this function in loop in your initialization. Start with CardIndex=0 and increment it each iteration. Stop [...]

  • Page 17

    15 # Brief Description Name Arguments (in C Syntax) Full Description 5 Set Active Chip SetActiveChip (long CardHandle , short ChipNumber ) Makes the specified chip active. All the following functions refer to that active chip. 6 Get Active Chip GetActiveChip (long CardHandle , short* ChipNumber ) Gets the current active chip (Chip1 or Chip2). 7 Tes[...]

  • Page 18

    16 3.4.2. I/O # Brief Description Name Arguments (in C Syntax) Full Description 8 Read the inputs of a chip, the EventFlags of its two encoders, and the Voltage Failure. ReadInputs (long CardHandle , short* Inputs , short* EncoderEventFlags ) Reads 5 or 6 chip's logical inputs, the two flags of its EncoderEvents, and, in case of Chip #1, the V[...]

  • Page 19

    17 3.5. ENCODER LEVEL FUNCTIONS 3.5.1. RESOLUTION # Brief Description Name Arguments (in C Syntax) Full Description 10 Set Encoder Resolution SetEncoderResolution (long CardHandle , short EncoderNumber , short ClocksPerCycle ) Selects the appropriate resolution that fits user's encoder. 11 Get Encoder Resolution GetEncoderResolution (long Card[...]

  • Page 20

    18 3.5.2. INDEX # Brief Description Name Arguments (in C Syntax) Full Description 12 Set Index Pulse Polarity SetIndexPulsePolarity (long CardHandle , short EncoderNumber , short Polarity ) Selects the polarity of the index (marker) pulse coming from user's encoder. 13 Get Index Pulse Polarity GetIndexPulsePolarity (long CardHandle , short Enc[...]

  • Page 21

    19 3.5.3. SETPOINT # Brief Description Name Arguments (in C Syntax) Full Description 16 Set Set Point SetSetPoint (long CardHandle , short EncoderNumber , long SetPoint ) Defines the Set Point Register (SPR). Reaching the SPR (i.e., meeting the condition IPC = SPR) may become the trigger of the Event Signal. SetPoint : The desirable SPR. Should con[...]

  • Page 22

    20 3.5.4. EVENT SIGNAL # Brief Description Name Arguments (in C Syntax) Full Description 18 Set Source of Encoder's EventFlag SetEncoderEventFlag Source (long CardHandle , short EncoderNumber , short EventFlagSource ) Selects a condition that becomes the trigger of the Event Signal. Upon meeting this condition, an Event Signal is supplied, bot[...]

  • Page 23

    21 22 Set Hold Mode of Hardware Encoder's EventFlag SetHoldEncoderEvent Flag (long CardHandle , short EncoderNumber , short OnOffMode ) Determines the "hold" characteristic of the hardware Event Signal: OnOffMode : Off: Hardware signal remains "as is" – no holding mechanism. On: Hardware signal is held until running an ex[...]

  • Page 24

    22 3.5.5. POSITION COUNTER # Brief Description Name Arguments (in C Syntax) Full Description 25 Reset (=clear) Position Counter ResetPositionCounter (long CardHandle , short EncoderNumber , short OutputsMirror ) Clears the Internal Position Counter (IPC) of one or two axes. OutputsMirror : This argument is described within the function WriteOutputs[...]

  • Page 25

    23 3.6. ARGUMENTS The constants of the arguments are available as follows: * In VB they are included in the example source file. * In VC they are in the EncPciConst.h file in the VC folder; refer to the ReadMe.txt file. * For DOS C/C++, the arguments, along with the headers of the functions, are in the file CPPEncPci.h. * For other environments, r[...]

  • Page 26

    24 #define TurnOn 1 #define TurnOff 0 // EnabledDisabledMode : #define SetEnabled 1 #define SetDisabled 0 // Polarity: #define ActiveOnHigh 1 #define ActiveOnLow 0[...]

  • Page 27

    25 APPENDIX A: SPECIFICATION Introduction A half-size PC card. Supports four optical encoders with either Square-wave or Sine output, both linear and rotary types. Directly connected to the encoders and also provides the excitation. Single / Multiple encoder pulses: Interpolation = 1, 2 or 4 (software selectable). Independent operation mode for eac[...]

  • Page 28

    26 I/O Index input per each axis (indicating Marker/Home/Zero). The user may instruct the card to reset its counter and/or generate an "Event Signal" output upon recognizing the index input. 11 Logical Inputs. The inputs are TTL/CMOS compatible Schmidt trigger single ended. Ten of them are general inputs and one is being used for requesti[...]

  • Page 29

    27 Software Method of communication with PCI bus: I/O ports. Software included: An ActiveX control to communicate with the card in Win95/98/NT/2K/XP. For WinNT/2K/XP thereʼs also a DLL option instead of the ActiveX control. A basic example in Visual C and a detailed example in VB. Example and source code on how to communicate with the board under [...]

  • Page 30

    28 APPENDIX B: DRAWINGS Connector Wiring for the Inputs[...]

  • Page 31

    29 Connector Wiring for the Outputs[...]

  • Page 32

    30 APPENDIX C: CARD INSTALLATION ? ? Install your card only after driver installation (section 3.1.1). Win95/98 1. Shut down your PC (i.e., power off). 2. Insert the new card into a free PCI slot. 3. Turn on your PC. 4. During the Windows 95/98 startup, the following window will appear: Add New Hardware Wizard This wizard searches for new drivers f[...]

  • Page 33

    31 9. Click: Next 10. Wizard displays: Unsupported Device. Windows has not installed a driver for this device. This is normal either. Click: Finish WinNT 1. Shut down your PC (i.e., power off). 2. Insert the new card into a free PCI slot. 3. Turn on your PC. ? ? For Win2K/XP instructions please refer to the following pages.[...]

  • Page 34

    32[...]

  • Page 35

    33[...]

  • Page 36

    34[...]

  • Page 37

    35[...]

  • Page 38

    36[...]

  • Page 39

    37[...]

  • Page 40

    38[...]

  • Page 41

    39 APPENDIX D: PRODUCT DEVELOPMENT Main Milestones in Product Development: • Dec. ʼ01: V1.00: Product launching. • Apr. ʼ02: V1.02: Support under WinNT/2K/XP (refer to section 3.1.1 & appendix C). • May ʼ02: V1.03: In addition to the OCX, a DLL is supplied too (WinNT/2K/XP only). • May ʼ03: V2.00: New feature: Option to request a sn[...]

  • Page 42

    W ARRANTY / DISCLAIMER OMEGA ENGINEERING, INC. warrants this unit to be free of defects in materials and workmanship for a period of 13 months from date of purchase. OMEGA ’ s W ARRANTY adds an additional one (1) month grace period to the normal one (1) year product warranty to cover handling and shipping time. This ensures that OMEGA ’ s custo[...]

  • Page 43

    M4272/0106 Where Do I Find Ever ything I Need for Pr ocess Measurement and Contr ol? OM EGA…Of Course! Shop online at omega.com TEMPERA TURE 䡺 ⻬ Thermocouple, RTD & Thermistor Probes, Connectors, Panels & Assemblies 䡺 ⻬ Wire: Thermocouple, RTD & Thermistor 䡺 ⻬ Calibrators & Ice Point References 䡺 ⻬ Recorders, Contr[...]