snap ethernet-based i/o units protocols and programming guide

More documents

Recommendations

Info

CHAPTER 3: USING THE SNAP ETHERNET I/O DRIVER TOOLKIT other specific brain models. See page 6 for features that apply to each model. For example, SNAP Simple I/O does not do high-speed digital counting. Methods such as GetStreamReadArea normally read and write data on active counters; you can still use these methods for SNAP Simple I/O, but disregard any data in the areas that don’t apply. A Note on Multithreading The components and classes in this toolkit do not have internal synchronization. If you wish to access a single instance of an object from multiple threads, you must provide your own external synchronization. Installing the Driver Toolkit The SNAP Ethernet I/O Driver Toolkit consists of examples and all source code. It is included on the CD that came with the brain and is also available from our Web site at www.opto22.com. Two installations are available: For Windows, use SnapENETDTK_R20a.exe. It will copy all files and register the ActiveX components. If you have difficulty using the toolkit, make sure you have installed OptoEnetUtilities.exe, which updates certain system files. For Linux, use snapenetdtk_R20a.tar. It contains just the files needed for a Linux system. Overview of the ActiveX Components You can use the OptoSnapIoMemMapX and OptoSnapIoStreamX ActiveX components from Windows programming environments that support ActiveX components, such as Borland Delphi, Microsoft Visual Basic®, Visual Basic for Applications, VBScript, and Visual C++. See “Important ActiveX Client Issues” on page 47 for more details on suitable clients. ActiveX is an umbrella term for many technologies based on COM (Component Object Model, a Microsoft technology allowing binary code reuse). Different programming environments use different terminology; in this chapter, we use terms as follows: An interface is a set of related functions (not a user interface). A component is an implementation of one or more interfaces. A control is a component that also has user interface elements. An object is an instance of a component. A type library is a description of a library’s exposed classes, interfaces, methods, and properties. In this toolkit, the type library is contained in the OptoSnapIoMemMapX.dll file. 46 SNAP Ethernet-Based I/O Units Protocols and Programming Guide
CHAPTER 3: USING THE SNAP ETHERNET I/O DRIVER TOOLKIT A UUID (Universally Unique Identifier, also called a GUID) is a a 128-bit value that uniquely identifies something. ActiveX Names and IDs NOTE: Different programming environments may require different information. File Name: OptoSnapIoMemMapX.dll Type Library UUID: 54D2FA40-E34F-11D2-9707-080009ABC65D Type Library Name: OptoSnapIoMemMapXLib MemMap ProgID: OptoSnapIoMemMapX.O22SnapIoMemMapX.1 MemMap Class UUID: 54D2FA50-E34F-11D2-9707-080009ABC65D MemMap Class Name: OptoSnapIoMemMapX MemMap Interface UUID: 54D2FA4F-E34F-11D2-9707-080009ABC65D MemMap Interface Name: IO22SnapIoMemMapX Streaming ProgID: OptoSnapIoMemMapX.OptoSnapIoStreamX.1 Streaming Class UUID: 54D2F150-E34F-11D2-9707-080009ABC65D Streaming Class Name: OptoSnapIoStreamX Streaming Interface UUID: 54D2F14F-E34F-11D2-9707-080009ABC65D Streaming Interface Name: IO22SnapIoStreamX Streaming Event Interface UUID: 54D2F148-E34F-11D2-9707-080009ABC65D Streaming Event Interface Name: _IOptoSnapIoStreamXEvents Important ActiveX Client Issues Before deciding to use these components in a particular language or tool, please keep the following in mind. Some types of ActiveX clients are better suited for use with these components than others. The components are designed to be used in procedural languages, such as Visual Basic and C++. They are not recommended for use in other types of languages, such as graphical or dataflow languages (for exmaple, LabVIEW). Opto 22 recommends Visual Basic 6.0 and Visual Basic for Applications as the best environments for using these components. Opto 22 is able to support the use of the ActiveX components only in the environments for which examples are provided: Access 2000, Word 2000, Visual Basic 6.0, Internet Explorer 6.0, Visual C++ 6.0, and Borland Delphi 5. See page 52 for more information on these examples. SNAP Ethernet-Based I/O Units Protocols and Programming Guide 47
Page 1 and 2:
SNAP ETHERNET-BASED I/O UNITS PROTO
Page 3 and 4:
Table of Contents Chapter 1: Introd
Page 5 and 6: Non-velocity Algorithms............
Page 7 and 8: Disconnecting......................
Page 9 and 10: Data Logging Configuration—Read/W
Page 11 and 12: Chapter 1 Introduction CHAPTER 1 We
Page 13 and 14: About this Guide CHAPTER 1: INTRODU
Page 15 and 16: For Help CHAPTER 1: INTRODUCTION If
Page 17 and 18: FEATURE CHAPTER 1: INTRODUCTION Ema
Page 19 and 20: CHAPTER 1: INTRODUCTION This task C
Page 21 and 22: CHAPTER 2 Chapter 2 Overview of Pro
Page 23 and 24: Referencing SNAP I/O Points CHAPTER
Page 25 and 26: Analog and Digital Systems (N Brain
Page 27 and 28: Digital-Only Systems The following
Page 29 and 30: I/O Point Types CHAPTER 2: OVERVIEW
Page 31 and 32: CHAPTER 2: OVERVIEW OF PROGRAMMING
Page 33 and 34: Watchdog (Digital and Analog Points
Page 45 and 46: Streaming Data CHAPTER 2: OVERVIEW
Page 47 and 48: Logging Data Area Number of Bytes I
Page 49 and 50: Using PID Loops What is a PID? CHAP
Page 51 and 52: Equations Common to All Algorithms
Page 55: CHAPTER 3 Chapter 3 Using the SNAP
Page 59 and 60: CHAPTER 3: USING THE SNAP ETHERNET
Page 63 and 64: Environment Visual Basic 6 Internet
Page 65 and 66: MemMap Example Code CHAPTER 3: USIN
Page 71 and 72: Return Values CHAPTER 3: USING THE
Page 73 and 74: IsOpenDone V Close V Return Values
Page 75 and 76: Digital Point Methods CHAPTER 3: US
Page 77 and 78: SetDigBankOnMask V [in] long nPts63
Page 79 and 80: Analog Bank Methods CHAPTER 3: USIN
Page 81 and 82: GetStatusWatchdogTime [out] long pn
Page 87 and 88: GetLastStreamStandardBlock (ActiveX
Page 89 and 90: CHAPTER 4 Chapter 4 Using the IEEE
Page 91 and 92: CHAPTER 4: USING THE IEEE 1394-BASE
Page 93 and 94: Bytes 0-3 Bytes 4-7 Bytes 8-11 Byte
Page 95 and 96: Bytes 0-3 Bytes 4-7 Bytes 8-11 The
Page 97 and 98: Bytes 0-3 Bytes 4-7 Bytes 8-11 Byte
Page 99 and 100: Read and clear latches for individu
Page 101 and 102: Scaling CHAPTER 4: USING THE IEEE 1
Page 103 and 104: Read and Write Packet Structure Par
Page 105 and 106: CHAPTER 4: USING THE IEEE 1394-BASE
Page 107 and 108:
CHAPTER 4: USING THE IEEE 1394-BASE
Page 109 and 110:
CHAPTER 5 Chapter 5 Advanced Modbus
Page 111 and 112:
CHAPTER 5: ADVANCED MODBUS PROGRAMM
Page 113 and 114:
APPENDIX A Appendix A SNAP Ethernet
Page 115 and 116:
Status Area Read—Read Only This i
Page 117 and 118:
Date and Time Configuration—Read/
Page 119 and 120:
Security Configuration—Read/Write
Page 121 and 122:
Serial Module Configuration—Read/
Page 123 and 124:
Wiegand Serial Module Configuration
Page 125 and 126:
SNMP Configuration—Read/Write (Do
Page 127 and 128:
Starting Address Length Type Descri
Page 129 and 130:
Page 131 and 132:
Digital Point Read—Read Only NOTE
Page 133 and 134:
Analog Point Read—Read Only See
Page 135 and 136:
Analog and Digital Point Configurat
Page 137 and 138:
Digital Events and Reactions—Read
Page 139 and 140:
Page 141 and 142:
Analog Point Calculation and Set—
Page 143 and 144:
Analog Read and Clear/Restart—Rea
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Serial Event Configuration—Read/W
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Data Log—Read/Write (Does not app
Page 159 and 160:
Appendix B Table of Offsets Introdu
Page 161 and 162:
Module Point (Decimal) Point (Hex)
Page 163 and 164:
Index A access, setting up SNMP sec
Page 165 and 166:
error codes IEEE 1394-based protoco
Page 167 and 168:
O off-latch, 20 offset, 24 IEEE 139
show all

snap ethernet-based i/o units protocols and programming guide

Create successful ePaper yourself

Delete template?

Save as template?