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

More documents

Recommendations

Info

CHAPTER 2: OVERVIEW OF PROGRAMMING Setting Up Event Messages You may need to send a message—via email, data streaming, SNMP, or a serial module—from the SNAP Ethernet-based I/O unit when a specific event occurs. For example, you could send a message if a digital point is on, if an analog point reaches a certain value, or if a specific string is received through a serial module. You can send one type of message or more. Your program monitors the event and triggers the message you have configured. You can configure up to 128 messages, either in ioManager or in your program. See “Event Message Configuration—Read/Write” on page 136 for memory map addresses to use. Copying Memory Map Data You can use memory map copying to do the following: Copy data from one memory map location to another on the same SNAP Ethernet-based I/O unit. Copy data from a memory map location on one I/O unit to a memory map location on another unit. Set up memory map copying when you configure event messages. Using Email You can send an email message or page someone in response to an event. In addition to setting up the email message when you configure event messages, you also need to tell the I/O unit where to send the email. See “Email Configuration—Read/Write” on page 138. Using Plugins Several plugins are available for use in event/reactions and messages. To do this Use this plugin In these places Include the pattern string from a serial communication module. 34 SNAP Ethernet-Based I/O Units Protocols and Programming Guide $!_str_ Serial event/reactions Show which serial port sent the pattern string. $!_port_ Serial event/reactions Include data from a memory map address. X = type of data (S=string, D=integer, F=float, P=IP address, B=4 binary bytes) YYYYYYYY = memory map address (see examples below) $!X_YYYYYYYY_ Serial event/reactions Event messages Memory map copying Email Number emails with a sequence ID. $!_seqid_ Email Turn digital points on or off using a bit mask. &#x00000000_ Memory map copying Event messages
Streaming Data CHAPTER 2: OVERVIEW OF PROGRAMMING NOTE: For email messages, message text including plugins must be 126 bytes (characters) or less. The message length after all plugins have been expanded into their data values must be 255 bytes or less. Examples: Including Data from Memory Map Addresses Memory map addresses are shown in ioManager, or see Appendix A for the complete memory map. Here are a couple of examples: To include the on/off state of a switch on point 3, you would put this in the message: $!D_F08000C0_ To include the temperature of an ICTD input on point 16, you would use: $!F_F0A00400_ Sending Binary Data in Event Messages To send binary data in the text of an event message, begin with &#x and end with _. You can include any number of ASCII hex digits up to the 127-byte limit for the message field. You can also include multiple &#x plugins. This plugin is resolved after all other plugins have been resolved, and only just before sending the contents of the message field out of the specified serial ports. Examples: To include an embedded null (one binary character): To include a number of binary characters: &#x00_ &#x0a0dCF0034_ Most communication involves the two-step process of request and response. A faster way of getting information from the SNAP Ethernet-based brain, however, is by streaming data. Streaming does not use TCP/IP; it uses the User Datagram Protocol (UDP) instead. NOTE: Because Modbus/TCP runs on TCP, not UDP, streaming data via Modbus/TCP is not possible. However, you can stream to a non-Modbus host at the same time you are using the Modbus/TCP protocol for another purpose. Streaming is a fast way to get continuous information about I/O from the SNAP Ethernet-based brain and is ideal for data acquisition applications. When it streams, the brain sends data at regular intervals to specified IP addresses. You set up the interval, the IP addresses to receive the data, and (optionally) the port number. The brain sends the data at the specified interval. The communication is one-way; the brain does not wait for a response. CAUTION: If you stream to multiple IP addresses, and one or more of the streaming targets is either offline or not running the application that receives the stream, delays may occur. If a target SNAP Ethernet-Based I/O Units Protocols and Programming Guide 35
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 43: CHAPTER 2: OVERVIEW OF PROGRAMMING
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 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?