1. OptoControlSDKR40.exe Driver
2. ReadMe.TXT File Contents

ReadMe.TXT Driver File Contents (OptoControlSDKR40.exe)

ReadMe.TXT for the OptoControl SDK
12-19-2001

What is the OptoControl SDK?
----------------------------
The OptoControl SDK is a set of documentation and samples that 
demonstrate how to write programs to talk to Opto 22's 
controllers on Win32. Please see the Opto 22 web site:
http://www.opto22.com
for examples on other operating systems.

The SDK has the necessary header files and LIB files to provide 
access to functions in the Opto DLLs and drivers. 

All necessary DLLs and drivers are included in Factory Floor.
All Opto DLLs have a file name of the form "Opto*.DLL".


SPECIAL NOTE for OptoControl 4.0 and up:
----------------------------------------
Visual C/C++ users may notice some instances of 
#ifdef OK50 
in the code. These should be ignored. Do not define OK50 
as it will cause your code to behave unpredictably.


Quick Start:
------------
* see "SDK Quickstart.htm" for a quick overview.
* see "1151_Opto_Controller_Comm_Overview.pdf" for an overview of 
communications to the controller.
* Configure a controller using OptoControl or OptoTerm. 
* Run OptoTerm to test communications with the controller.
* In OptoTerm, experiment with commands such as PTIME.
* see the HostWords document, HWOCtrl.DOC, for a comprehensive list of 
commands HostWords commands (most commonly used with 3rd party HMI
packages).
* see the examples included in the OptoCom subdirectory, 
in particular, the 'terminal' examples such as VcTerm
which is a trivial terminal application for Visual C++.


OptoCom.DLL is the DLL that handles communications with Opto 
controllers. There are three main APIs: one to open a handle to a 
controller, one to send a command and get the corresponding response, 
and one to close the handle to a controller. See "SDK Quickstart.htm" 
for more details.

The type of connection to the controller (serial, Arcnet, Ethernet 
etc) is transparent at this level and is determined by configuring the 
controller using OptoControl or OptoTerm. This means that a program 
written to communicate to a controller using OptoCom.Dll will work 
over serial, Arcnet, Ethernet or through the OptoCds server accross a 
network.

For users migrating from 16 bit MwDriver.DLL to 32 bit:
Many users/programmers in Win16 use MwDriver.DLL to communicate to 
Opto controllers from Visual Basic and other languages. In Win32, use 
OptoCom.DLL instead of the 16 bit MwDriver.DLL to talk to controllers.


Contents:
----------
"SDK Quickstart.htm" 
  - quick overview of what's included.
"1151_Opto_Controller_Comm_Overview.pdf" 
  - overview of communications to the controller.
HostWords directory 
  - Info about the commands that controllers using HostWords.
OptoCom             
  - examples to talk to controllers
OptoCdb             
  - examples to access tag database
OptoErr             
  - examples to translate Opto error codes into text
OptoSnif            
  - examples to use diagnostic logging or 'sniffing' utility
WinSock Term        
  - how to access an Opto Controller via Ethernet using Socket


(end of ReadMe.TXT)