eWON General Reference Guide - eWON wiki

More documents

Recommendations

Info

General Reference Guide IO Servers Configuration 5.6.2.2.2 DF1 : Ethernet routing Thanks to the ABLogix IOServer, the eWON is now able to poll data on SLC500/PLC5 devices by its Ethernet link. Even SLC500 connected behind your ControlLogix Network becomes available for polling. With this use of DF1 IOServer, the Serial config can be left unconfigured (baudrate=disabled), only one Topic enabled is required. You need to use a similar syntax than in ABLogix IOServer. [DeviceType-] IP Address [, Port, Link] • DeviceType = type of PLC ( SLC500 or PLC5 ) • IP Address = address on your Ethernet network (i.e.: 10.0.0.50) • Port = value from 1 to 3 representing: 1 = Backplane, 2 = Channel A, 3 = Channel B • Link could be: ¤ Slot: representing the Slot on the Backplane (0=CPU) ¤ Node ID: value from 0 to 99 (for ControlNet) ¤ IP address To reach a SLC500 with Ethernet address 10.0.0.60: Topic A Destination = 10.0.0.60 or SLC500-10.0.0.60 To reach a PLC5 with Ethernet address 10.0.0.65: Topic A Destination = PLC5-10.0.0.65 To reach a SLC500 connected behind a ControlLogix : Topic A Destination = 10.0.0.80,1,3,2,45 or SLC500-10.0.0.80,1,3,2,45 • 10.0.0.80 = IP address of the ControlLogix • 1 = BackPlane • 3 = Slot 3 (COM card in ControlNet) • 2 = Channel A (of the Card present in Slot 3) • 45 = NodeID of the SLC500 (in the ControlNet network) To reach a PLC5 connected behind a ControlLogix : Topic A Destination = PLC5-10.0.0.90,1,3,2,44 • 10.0.0.90 = IP address of the ControlLogix • 1 = BackPlane • 3 = Slot 3 (COM card) • 2 = Channel A (of the Card present in Slot 3) • 44 = NodeID of the PLC5 (in the COM network) 5.6.2.2.3 DH+ polling using ControlLogix gateway This feature allows the eWON to poll PLC Tags located on a DH+ network, behind a controllogix equipped with one or more DHRIO cards. Polling is done using eWON EIP protocol. The DF1 IO server is used to access the "SLC500" PLC family. The ABLOGIX IO server is used to access the "LOGIX" PLC family. The syntax [Device Type-] IP address [,Port,Link] is still applicable but in this particular case: the [,Port,Link] part becomes mandatory The DH+ channel used to reached the "SLC500" PLC must be specified using the "A" or "B" character. Example: To reach a SLC500 with DH+ node Id 5, using channel A of a DHRIO card at slot 9 of a controllogix at IP address 10.0.30.21. Topic A Destination = SLC500-10.0.30.21,1,9,A,5 • 10.0.30.21 = IP address of the ControlLogix • 1 = BackPlane • 9 = Slot 9 (COM card) • A = Channel A (of the Card present in Slot 9) • 5 = NodeID of the SLC500 (in the COM network) RG-001-0-EN ver 1.14 eWON® - 02/05/2012 - ©eWON sa Page 111
5.6.3 Tag name convention IO Server Name DF1 Topic Name Item Name General Reference Guide IO Servers Configuration The Item Name can contain the PLC address where the value is polled, or not. If the address is also specified at the topic level, the address specified at Tag level will be ignored. 5.6.3.1 Value Name A B C IO Server configuration 5.6.3.1.1 General Description The general format of value names for data from SLC-500 controllers matches the naming convention used by the programming software. The format is shown below (The parts of the name shown between square brackets are optional). General Value Name Format: X[file]:element [.field][/bit] X: Identifies the file type. The below table summarizes the valid file types, default file number for each type and the fields allowed. X File Type ValueName, DeviceType-DeviceAddress • File: File number must be 0-255 decimal • Element: Element number within the file • Field: Valid only for Counter, Timer and Control files • /bit: Valid for all types except Floating (*) Important: To avoid loss of precision due to Integer to float conversion, choose the right storage DataType for your Tag. See "DataType of Tags" on page 75 5.6.3.1.2 Output File Items Output File Item Format: O[n]:e.s[/b] • "n" represents the file number and is optional. Value is always zero • "e" indicates the element number in the file (0..30) • "s" indicates the sub-element number (0..255) Device Type and Address are defined Tag by Tag Only device Type SLC500 is supported Device Address is a number between 0..254 ValueName Topic PLC Address is used Table 83: DF1 IO server configuration Default file Number RG-001-0-EN ver 1.14 eWON® - 02/05/2012 - ©eWON sa Page 112 Fields Automatic Tag type O Output 0 DWord I Input 1 DWord S Status 2 DWord B Binary 3 DWord T Timer 4 .PRE, .ACC, .EN, .TT, .DN DWord C Counter 5 .PRE, .ACC, .CU, .CD, .DN, .OV, .UN, .UA DWord R Control 6 .LEN, .POS, .EN, .DN, .ER, .UL, .IN, .FD DWord N Integer 7 DWord F Floating 8 Float A ASCII none DWord Table 84: value names for DF1 addresses
Page 1 and 2:
eWON Family 500, 2001, 2001CD, 4001
Page 3 and 4:
Table of content 5.4.3 Tag name con
Page 5 and 6:
Table of content 8.3.3 $dtRL [Real
Page 7 and 8:
2 The eWON login page 2.1 Access fr
Page 9 and 10:
3.2 Users Setup The Users Setup pag
Page 11 and 12:
3.2.5 User’s directory restrictio
Page 13 and 14:
3.3 System Setup General Reference
Page 15 and 16:
3.3.1.2 Alarms (globals parameters)
Page 17 and 18:
3.3.1.5 Task Planner Since Firmware
Page 19 and 20:
3.3.1.5.2 Edit Action page When you
Page 21 and 22:
General Reference Guide eWON Config
Page 23 and 24:
When using modem port for VCOM, the
Page 25 and 26:
3.3.2.7 SNMP Setup 3.3.2.7.1 Commun
Page 27 and 28:
3.3.3 Diagnosis 3.3.3.1 Overview Ge
Page 29 and 30:
3.3.3.4 Debug Control Description L
Page 31 and 32:
3.3.4.1.1 Modem setup page Warning:
Page 33 and 34:
Page 35 and 36:
3.3.4.1.1.4 PSTN: Leased line confi
Page 37 and 38:
3.3.4.1.2 Ethernet LAN & WAN From t
Page 39 and 40:
Each mechanisms provides you all or
Page 41 and 42:
Page 43 and 44:
Select next server in case of error
Page 45 and 46:
3.3.4.2.3 ADSL General Reference Gu
Page 47 and 48:
Page 49 and 50:
VPN between two eWONs General Refer
Page 51 and 52:
VPN with an ENDIAN Server You can f
Page 53 and 54:
Ethernet WAN Connection - Disconnec
Page 55 and 56:
3.3.4.3 Networking Config 3.3.4.3.1
Page 57 and 58:
Page 59 and 60:
Page 61 and 62: General Reference Guide eWON Config
Page 63 and 64: 3.3.4.3.6 Proxy 3.3.4.3.6.1 Why a p
Page 65 and 66: 3.3.4.3.7 Security You can define t
Page 69 and 70: 3.3.4.5 STORAGE General Reference G
Page 71 and 72: 3.3.4.5.2 Erase & Format Figure 62:
Page 73 and 74: 3.3.4.5.3.2 Edit parameters General
Page 77 and 78: 3.4.1.2 Tags validation General Ref
Page 79 and 80: 3.4.2.1 Tag main edit window Genera
Page 81 and 82: Control Description Tag name Tag De
Page 85 and 86: 3.4.2.2.1 Email on alarm configurat
Page 87 and 88: Examples: General Reference Guide e
Page 89 and 90: 3.5 Pages configuration Page defini
Page 93 and 94: 3.8 Wizards To help you quickly and
Page 95 and 96: 5 The eWON IO Servers 5.1 Introduct
Page 97 and 98: 5.2.4 Standard IO server configurat
Page 99 and 100: General Reference Guide IO Servers
Page 101 and 102: 5.3.3 Tag name convention IO Server
Page 103 and 104: 5.3.3.2 Slave Address This is the a
Page 105 and 106: 5.4.3.1 ValueName General Reference
Page 109 and 110: • Status register: General Refere
Page 111: eWON DF1 address 5.6.2.2 Topic conf
Page 115 and 116: • "e" indicates the element numbe
Page 117 and 118: Serial FINS network Serial FINS nod
Page 119 and 120: Supported memory areas: Modifier: G
Page 121 and 122: 5.8 S5-AS511 IO Server 5.8.1 Introd
Page 123 and 124: NOTES: • For DB the smallest elem
Page 125 and 126: 5.9.2.1 Communication Setup General
Page 127 and 128: 5.9.3.1 ValueName ValueName follows
Page 129 and 130: Example of use of SN_LO and SN_HI i
Page 131 and 132: 5.10.2.2.1 ENERGY TAGS The followin
Page 133 and 134: 5.10.2.3.2 PT100 input AI5 and AI6
Page 135 and 136: 5.11 MEM IO Server 5.11.1 Introduct
Page 137 and 138: Baud Rate General Reference Guide I
Page 139 and 140: 5.12.2.3 Topic configuration Genera
Page 141 and 142: DB1B13#3 represents bit 3 of Byte 1
Page 143 and 144: 5.13 S7-200 (PPI - ISOTCP) 5.13.1 I
Page 145 and 146: 5.13.2.3 COM configuration (MPI por
Page 147 and 148: 5.13.3.1 Value Name The syntax is t
Page 149 and 150: 5.14 HITACHI IO Server 5.14.1 Intro
Page 151 and 152: 5.14.2.1 Value Name The syntax is t
Page 155 and 156: 5.15.2.2 Topic configuration Genera
Page 159 and 160: 5.16.3 Tag name convention General
Page 161 and 162: 5.17 MITSUBISHI MELSEC IO Server 5.
Page 163 and 164:
Note: The Modifier can be omitted,
Page 165 and 166:
6.1 Real-time screen General Refere
Page 167 and 168:
General Reference Guide Monitoring
Page 169 and 170:
6.4 Real time Alarm screen Figure 1
Page 171 and 172:
6.6 Files transfer This link gives
Page 173 and 174:
General Reference Guide Monitoring
Page 175 and 176:
6.7.2.1 Memory Information 6.7.2.2
Page 177 and 178:
6.7.2.5 Info 6.7.3 Scheduled Action
Page 179 and 180:
6.7.4.2 Activate Energy debug mode
Page 181 and 182:
6.7.5 ADSL Log General Reference Gu
Page 183 and 184:
General Reference Guide Retrieving
Page 185 and 186:
8 Export Block Descriptor Exports a
Page 187 and 188:
8.2.3 $st [Start Time] and $et [End
Page 189 and 190:
8.3 Data Types description and synt
Page 191 and 192:
8.3.2 $dtHT [Historical Table] Gene
Page 193 and 194:
8.3.3 $dtRL [Real time Logging] Gen
Page 195 and 196:
8.3.5 $dtAR [Alarm Real time] 8.3.5
Page 197 and 198:
8.3.7 $dtSS [Scheduled Status] Gene
Page 199 and 200:
8.3.9 $dtUF [User File] 8.3.9.1 Exp
Page 201 and 202:
8.3.10 $dtIV [Instant Values] Gener
Page 203 and 204:
General Reference Guide Export Bloc
Page 205 and 206:
8.3.12 $dtPP General Reference Guid
Page 207 and 208:
8.3.15 $dtRE [Real Time Diagnostic]
Page 209 and 210:
8.3.16.5 Examples $dtTR $fnmytar.ta
Page 211 and 212:
The new firmware is uploaded to the
Page 213 and 214:
9.3 Upgrading the eWON firmware by
Page 215 and 216:
9.4 Downgrade firmware 9.4.1 Firmwa
Page 217 and 218:
10 Appendix 10.1 Access to the eWON
Page 219 and 220:
10.5 Resetting the eWON 10.5.1 Over
Page 221 and 222:
10.6 Table of comparisons between e
Page 223 and 224:
10.9 GSM modem Led behavior Figure
show all

eWON General Reference Guide - eWON wiki

Create successful ePaper yourself

Delete template?

Save as template?