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

More documents

Recommendations

Info

CHAPTER 5: ADVANCED MODBUS PROGRAMMING Determining Modbus Unit ID and Register Address To read and write, you need to determine the Modbus Unit ID and Register Address that are equivalent to the brain’s memory map address. You can use ioManager to convert addresses. The basic steps are shown below; see the ioManager User’s Guide for additional help. You may also need Appendix A to find memory map addresses. 1. In the ioManager main window, with a configuration file open, right-click an I/O unit and choose Configure from the pop-up menu. 2. In the Configure I/O Units dialog box, click the Others button and choose Modbus from the pop-up menu. 3. Click the Advanced button to see the rest of the dialog box. 100 SNAP Ethernet-Based I/O Units Protocols and Programming Guide
CHAPTER 5: ADVANCED MODBUS PROGRAMMING 4. To convert a brain memory map address to a Modbus Unit ID and Register Address, type the last eight digits of the brain’s memory map address in the MemMap Address field. Make sure there are no spaces in the address (for example, type F0300020). 5. Click the right-arrow button . The equivalent Modbus address appears. NOTE: The Modbus numbers are decimal. Example: Reading a Memory Map Address For example, suppose you want to read the status of Scratch Pad bits. You can determine the memory map address in one of two ways: Use the ioManager Inspect window to find the address you want and copy it. Look in Appendix A, find Scratch Pad addresses (page 129), and locate the address for the current state of Scratch Pad bits. Either way, you determine that the memory map address is F0D80000. Using ioManager, you convert the MemMap address F0D80000 to a Unit ID of 110 and a Register Number of 1. Example: Writing to a Memory Map Address As another example, suppose you want to send a powerup clear (PUC) to the brain. This operation code is in the Status Write area of the brain’s memory map address. To determine the address and the data to write to send a PUC, check the Status Write area in Appendix A (page 107). From the appendix, you determine that the memory map address for an operation code is F0380000, and the specific data you must write to send a PUC is 0x00000001. Using the Modbus conversion page, you find that address F0380000 equals a Unit ID of 30 and a Register Number of 1. SNAP Ethernet-Based I/O Units Protocols and Programming Guide 101
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:
Page 43 and 44:
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 53 and 54:
Page 55 and 56:
CHAPTER 3 Chapter 3 Using the SNAP
Page 57 and 58:
CHAPTER 3: USING THE SNAP ETHERNET
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 109: CHAPTER 5 Chapter 5 Advanced Modbus
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 149 and 150: Serial Event Configuration—Read/W
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?