eWON General Reference Guide - Esco Drives & Automation

More documents

Recommendations

Info

General Reference GuideIO Servers Configuration5 The eWON IO Servers5.1 IntroductionThis introduction repeats some information already introduced in chapter “Tag definition: Introduction” on page 67.An IO Server is the interface between a changing value and the eWON monitoring engine. It is a kind of driver. Any variable from any data sourcemust have a common representation for all IO Servers in order to define common interface in the eWON.The data-source representation in the eWON uses 3 fields for the definition of a Tag:• The IO Server Name• The Topic name• The Item NameA Tag’s data-source will be uniquely identified with these 3 parameters:IO Server name:Topic Name:Item Name:Is a kind of driver name. For each IO Server there is a specific Topic Name and Item Name syntax.Example: MODBUS, EWON, MEMIs used to group items inside an IO Server, for example the memory IO Server uses the blank topic("") and the retentive topic ("ret"). All Tags of the MEM IO Server defined in the "ret" topic will havetheir value saved and restored when the eWON boots.All IO servers do not use a Topic Name. In that case the Topic Name field must be left empty.The item name is a string of characters; its syntax is specific to each IO Server.The Item Name describes the physical variable to monitor that uses the IO Server.For example, the MODBUS IO Server needs to poll registers or coils from a slave, so it uses an item name representation todefine the register type, register address and slave address. (Example "40001,5" => Where 4 means "read write register",0001 is the register number and 5 is the slave Modbus address).Table 55: Tags data-source parametersImportant note: For optimisation purpose, the eWON may disable the polling of “invalid tags” (See “IO Server Init” on page 86).5.2 IO servers setupSome of the IO servers are configurable.The IO setup window proposes a list of IO servers:Figure 71: eWON IO servers scrolling listClick on the Edit hyper link or select another IO server to display its edition window.There are 3 possible cases regarding the IO server configuration:• The IO server is not configurable• The IO server has a dedicated configuration page (ex: MODBUS, UNITE, NETMPI, DF1, ...)• The IO server uses the standard IO server configuration page.RG-001-0-EN ver 1.5 eWON® - 20/03/2009 - ©ACT'L sa Page 85
General Reference GuideIO Servers Configuration5.2.1 IO Server ClearTo avoid the useless consumption of CPU and memory, the unusedIO Servers need to be “unloaded” from CPU tasks and the usedmemory need to be cleared.For that purpose, the Clear function must be used.Only set to disable the BaudRate of an IO Server make it idle, but thisIO Server is still in memory and use some CPU time (for nothing).Click on the Clear link to reset the config of the displayed IO Serverand unload it from memory.Some IO Servers are not dynamically stoppable and need an eWON reboot to ensure the unload from memory. You will be warned with thefollowing message.5.2.2 IO Server InitClick on the Init link to initialise an IOServer.This initialisation will reset all IOServer counters (See “Status” onpage 159) and restart the tags validation process (See “Tagsvalidation” on page 68).5.2.3 Global ConfigFigure 72: IOServer Global Config pageItemDescriptionModbus TCP Port Encode here the TCP Port number used for the ModbusTCP server protocol. Default is 502Ethernet/IP Port Encode here the TCP Port used for the Ethernet/IP protocol (Allen Bradley). Default is 44818ISOTCP Port Encode here the TCP Port number used for the ISOTCP protocol (Siemens). Default is 102FINS Port Encode here the TCP Port number used for the FINS protocol (Omron). Default is 9600Disable Tags in Error Activate the Tags Validation See “Tags validation” on page 68RG-001-0-EN ver 1.5 eWON® - 20/03/2009 - ©ACT'L sa Page 86
Page 1 and 2:
eWON Family500, 2001, 4001, 2101, 4
Page 3:
Table of content5.4.3 Tag name conv
Page 6 and 7:
General Reference GuideIntroduction
Page 8 and 9:
General Reference GuideeWON Configu
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37: General Reference GuideeWON Configu
Page 88 and 89: General Reference GuideIO Servers C
Page 136 and 137:
General Reference GuideIO Servers C
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
General Reference GuideMonitoring W
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
General Reference GuideRetrieving d
Page 168 and 169:
General Reference GuideExport Block
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
General Reference GuideUpgrading th
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
General Reference GuideAppendix10 A
Page 202 and 203:
General Reference GuideAppendix10.5
Page 204 and 205:
Page 206:
show all

eWON General Reference Guide - Esco Drives & Automation

Create successful ePaper yourself

Delete template?

Save as template?