eWON Family - eWON Support

More documents

Recommendations

Info

eWON DF1 address 5.6.2.2 Topic configuration General Reference Guide IO Servers Configuration Figure 82: DF1 topics configuration Three topics can be used for the IO Server. These topics are used to give a common property to a group of DF1 Tags like: • Enable/Disable • Poll rate • Destination Device Type and Address 5.6.2.2.1 DF1 : serial link The Destination Device Type and address is : • SLC500-x (where x is the address of your SLC500 Device, range 0..254) • PLC5-x (where x is the address of your PLC5 Device, range 0..254) i.e.: Topic A Destination = SLC500-1 Topic B Destination = PLC5-6 5.6.2.2.2 DF1 : Ethernet routing The eWON’s device address on the DF1 link When th eWON acts as a DF1 slave, it will respond to 2 consecutive link addresses; doing this improves the throughput of data across the eWON when acting as a gateway. (eWON DF1 address and eWON DF1 address +1) Destination DF1 address Device Address of Destination on DF1 link when EIP is used Bridge EIP connection When bridging is configured, EIP connections requests are forwarded to the PLC on the DF1 interface (mandatory for Logix family). This is the default configuration. When not configured, connection requests are cancelled by the eWON (must be disabled for SLC family). Topic configuration item Description Topic enabled Enables or disables the polling of all the Tags in the topic Destination Device Type and Address Poll rate Table 74: DF1 communication setup controls The Destination Device Type and Address is a global parameter for all the Tags of the topic. See below for the Device Address syntax. If an address is specified here, it will replace (overload) the address defined Tag by Tag Defines the refresh rate of the Tag name. In a complex application, we can imagine that some Tag name must be refreshed every second – typically for digital input - and other every minute – typically: temperature- Table 75: DF1 topics configuration setup RG-001-0-EN ver 1.6 eWON® - 22/06/2009 - ©ACT'L sa Page 101
General Reference Guide IO Servers Configuration 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) 5.6.3 Tag name convention IO Server Name DF1 IO Server configuration Table 76: DF1 IO server configuration RG-001-0-EN ver 1.6 eWON® - 22/06/2009 - ©ACT'L sa Page 102
Page 1 and 2:
eWON Family 500, 2001, 4001, 2101,
Page 3 and 4:
Table of content 5.4.3 Tag name con
Page 5 and 6:
Table of content 8.3.8 $dtSE [Scrip
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.2 Net services setup General Re
Page 19 and 20:
General Reference Guide eWON Config
Page 21 and 22:
Control Description Enable NTP cloc
Page 23 and 24:
The parameters for Alarm traps are
Page 25 and 26:
Control Description General Referen
Page 27 and 28:
3.3.4 COM Setup section Warning: de
Page 29 and 30:
3.3.4.1.1.2 Modem configuration (GS
Page 31 and 32:
3.3.4.1.1.3 Modem configuration (IS
Page 33 and 34:
3.3.4.1.1.5 ADSL interface General
Page 35 and 36:
3.3.4.2.1 Ethernet LAN (& WAN) 3.3.
Page 37 and 38:
Page 39 and 40:
3.3.4.2.2.2 Outgoing Global paramet
Page 41 and 42:
Page 43 and 44:
3.3.4.2.4 VPN General Reference Gui
Page 45 and 46:
VPN between two eWONs General Refer
Page 47 and 48:
VPN with an ENDIAN Server You can f
Page 49 and 50:
Ethernet WAN Connection - Disconnec
Page 51 and 52: 3.3.4.3 Networking Config 3.3.4.3.1
Page 53 and 54: General Reference Guide eWON Config
Page 59 and 60: 3.3.4.3.6 Proxy 3.3.4.3.6.1 Why a p
Page 61 and 62: 3.3.4.3.7 Security You can define t
Page 63 and 64: 3.3.4.4.2 Default Config General Re
Page 67 and 68: 3.3.4.5.3 Features General Referenc
Page 69 and 70: 3.4.1.2 Tags validation General Ref
Page 71 and 72: 3.4.2.1 Tag main edit window Genera
Page 73 and 74: Control Description Tag name Tag De
Page 77 and 78: 3.4.2.2.1 Email on alarm configurat
Page 79 and 80: Examples: General Reference Guide e
Page 81 and 82: 3.7 Script Setup General Reference
Page 83 and 84: 3.7.2 The Script control link Gener
Page 85 and 86: 4 Configuring the eWON by a file up
Page 87 and 88: 5.2.1 IO Server Clear To avoid the
Page 89 and 90: 5.3 Modbus IO server 5.3.1 Introduc
Page 91 and 92: Parameter name Description PreDelay
Page 93 and 94: General Reference Guide IO Servers
Page 95 and 96: 5.4 NETMPI IO Server 5.4.1 Introduc
Page 97 and 98: 5.5 UNITE IO Server 5.5.1 Introduct
Page 99 and 100: 5.5.3.1 Value Name Value name follo
Page 101: 5.6 DF1 IO Server 5.6.1 Introductio
Page 105 and 106: 5.6.3.1.4 Status File Items Status
Page 107 and 108: 5.7 FINS IO Server 5.7.1 Introducti
Page 109 and 110: 5.7.2.3 Gateway Configuration The f
Page 111 and 112: 5.8 S5-AS511 IO Server 5.8.1 Introd
Page 113 and 114: • Status register: General Refere
Page 115 and 116: 5.9.2.1 Communication Setup General
Page 117 and 118: 5.9.3.1 ValueName ValueName follows
Page 119 and 120: Example of use of SN_LO and SN_HI i
Page 121 and 122: 5.10.2.2.1 ENERGY TAGS The followin
Page 123 and 124: 5.10.2.3.2 PT100 input AI5 and AI6
Page 125 and 126: 5.11 MEM IO Server 5.11.1 Introduct
Page 127 and 128: Baud Rate 5.12.2.2 Topic configurat
Page 129 and 130: Examples • Bit access modifier: G
Page 131 and 132: 5.13 S7-200 (PPI - ISOTCP) 5.13.1 I
Page 133 and 134: 5.13.2.4 Topic configuration Genera
Page 137 and 138: 5.14.1.1.2 Topic configuration Gene
Page 139 and 140: Note: The Modifier can by omitted,
Page 141 and 142: 5.15 MITSUBISHI FX IO Server 5.15.1
Page 143 and 144: 5.15.3.1 Value Name The syntax is t
Page 145 and 146: 5.16 SNMP IO Server 5.16.1 Introduc
Page 149 and 150: 6.1 Real-time screen General Refere
Page 151 and 152: General Reference Guide Monitoring
Page 153 and 154:
6.4 Real time Alarm screen Figure 1
Page 155 and 156:
6.6 Files transfer This link gives
Page 157 and 158:
General Reference Guide Monitoring
Page 159 and 160:
6.7.2.1 Memory Information 6.7.2.2
Page 161 and 162:
6.7.2.5 Info 6.7.3 Scheduled Action
Page 163 and 164:
6.7.4.2 Activate Energy debug mode
Page 165 and 166:
7 Retrieving Data from eWON 7.1 Lis
Page 167 and 168:
7.3 FTP transfer FTP stands for the
Page 169 and 170:
8.2 Export fields syntax definition
Page 171 and 172:
8.2.4 $ut [Update Time] General Ref
Page 173 and 174:
$ft General Reference Guide Export
Page 175 and 176:
For fixed interval, $in parameter m
Page 177 and 178:
8.3.4 $dtAH [Alarm History] General
Page 179 and 180:
8.3.6 $dtEV [EVent file] 8.3.6.1 Ex
Page 181 and 182:
8.3.8 $dtSE [Script Expression] 8.3
Page 183 and 184:
General Reference Guide Export Bloc
Page 185 and 186:
General Reference Guide Export Bloc
Page 187 and 188:
8.3.11 $dtSV General Reference Guid
Page 189 and 190:
8.3.14 $dtSC General Reference Guid
Page 191 and 192:
8.3.16 $dtTR [TAR file] 8.3.16.1 Ex
Page 193 and 194:
9 Upgrading the eWON firmware 9.1 P
Page 195 and 196:
Click on the Finish Button when the
Page 197 and 198:
General Reference Guide Upgrading t
Page 199 and 200:
9.5 Upgrade Bootloader (to upgrade
Page 201 and 202:
10.2.2 Non-volatile configuration T
Page 203 and 204:
If an error is detected during the
Page 205 and 206:
10.7 Duplicate IP detection (User L
show all

eWON Family - eWON Support

Create successful ePaper yourself

Delete template?

Save as template?