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

More documents

Recommendations

Info

CHAPTER 4: USING THE IEEE 1394-BASED PROTOCOL Overview of Programming Developing custom applications for the SNAP Ethernet-based brain requires five basic steps: connect, send Powerup Clear, configure, read/write, and disconnect. This overview section leads you through these steps using a utility application called OptoEIEIO (Easy Interface Ethernet I/O), written in Microsoft ® Visual Basic ® 5.0. The utility is included on the CD that came with the brain and is installed with the typical software installation. To open OptoEIEIO, choose Start➞Programs➞Opto22➞OptoENET-IO➞OptoEIEIO. Connecting To connect with the SNAP Ethernet-based brain, OptoEIEIO uses the Microsoft Winsock control (variable name for this object in OptoEIEIO: tcpIOUnit) and a user-selectable Host Name/IP address and port. Note that the Remote Port defaults to 2001 for the SNAP Ethernet-based brain. tcpIOUnit.RemoteHost = “10.192.0.69” ‘IP address of brain tcpIOUnit.RemotePort = 2001 tcpIOUnit.Connect Sending Powerup Clear Once a connection has been established, the host must send a Powerup Clear message (PUC) to the SNAP Ethernet-based brain. You can’t do anything except read the memory map’s Status area until the Powerup Clear is sent. Other requests will return a negative acknowledgment (NAK), and the error Powerup Clear Expected will appear in the Status area. (See page 107.) After the initial PUC is sent, you do not need to send another unless the brain has been turned off or restarted. To check whether a Powerup Clear is needed, you can read the PUC flag in the Status area. A zero means the PUC has been sent; anything else means you must send a PUC. OptoEIEIO sends a Powerup Clear as follows: Call SendString(BuildWriteQuad(MM_OPERATION_PUC, OPTO_MM_OPERATION_CODE), WRITE_QUAD_REQ) The BuildWriteQuad subroutine builds a Write Quadlet Request packet using the two pieces of information passed. One is the quadlet_data, 00000001, which is represented by the constant MM_OPERATION_PUC. The other is the destination_offset, FFFFF0380000, which is the memory map location for sending a Powerup Clear and is represented by the constant OPTO_MM_OPERATION_CODE. (The complete memory map is shown in Appendix A, starting on page 103.) 82 SNAP Ethernet-Based I/O Units Protocols and Programming Guide
Bytes 0–3 Bytes 4–7 Bytes 8–11 Bytes 12–15 Binary notation is shown on the left side of the window. The buffer shows the data that will be sent, in hex. Write Quadlet Request Packet (PC➞Brain) CHAPTER 4: USING THE IEEE 1394-BASED PROTOCOL The packet constructed by the BuildWriteQuad subroutine appears as follows in binary notation. (For more information on communication packets, see “Read and Write Packet Structure” on page 93). destination_ID tl rt tcode pri 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 source_ID destination_offset 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 destination_offset 1 1 1 1 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 quadlet_data 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 In hex, the packet looks like this: 000004000000FFFFF038000000000001 destination_offset quadlet_data OptoEIEIO shows you the correlation between binary and hex in the Write Quadlet Request dialog box. To see the dialog box, follow these steps: 1. In the OptoEIEIO main window, open the Advanced menu and make sure Auto Parsing is enabled. 2. Also from the Advanced menu, choose Send Packets Manually. 3. In the Manual Mode dialog box, click Write Quadlet Request, and then click Show Selected Type. Hex notation is shown on the right side of the window. Enter data on the hex side of the window for the fields you need to complete. The binary side changes to match. To place changed hex values into the buffer, click this button. To place buffer values into the hex fields, click this button. SNAP Ethernet-Based I/O Units Protocols and Programming Guide 83
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 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42: CHAPTER 2: OVERVIEW OF PROGRAMMING
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 and 56: CHAPTER 3 Chapter 3 Using the SNAP
Page 57 and 58: 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: CHAPTER 4: USING THE IEEE 1394-BASE
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 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 141 and 142: Analog Point Calculation and Set—
Page 143 and 144:
Analog Read and Clear/Restart—Rea
Page 145 and 146:
Starting Address Length Type Descri
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?