•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 what Hardware EventFlags Output the card should supply.
•The card reflects in its Hardware General Outputs the status of its software INPUTS.
•Clicking "Write" writes into card's software inputs the desired status of card's Hardware General Outputs.
•The desired status of card's Hardware General Outputs may be set by clicking a specific output (1, 2 or 3). However, the output is NOT passed immediately to the card. Click "Write" to validate the new status, or "Undo" to leave out the last change(s).
3.1.3.VC
Select the ʻVCʼ folder that corresponds to your driver installation (section 3.1.1). This folder includes four elements:
•The file ReadMe.txt
•The file EncPciConst.h
•The file EncPciFunctions.h
•The subfolder EncPciBasicTest
The first item (ReadMe.txt) includes detailed instructions how to use the ActiveX control or the DLL in Visual C. In order to follow these instructions, you'll need the second and third items (EncPciConst.h and EncPciFunctions.h). The fourth (last) item (the subfolder EncPciBasicTest) includes a sample basic project that was created according to the instructions of ReadMe.txt.
3.1.4.CPP
Here you'll find the required files for the DOS C/C++ programmer.
The programmer should include EncPci.h in his source file, and EncPci.obj in his project.
A simple demo program is supplied. It reads continuously the four axes and displays their values.
3.1.5.More
This folder supplies more information for environments other than the above. The files EncPci.cpp and EncPci.h include the source code (in C++) of driver's functions in DOS. You may utilize this code in order to produce your own driver for your environment.
12
