eWON General Reference Guide - Esco Drives & Automation

More documents

Recommendations

Info

General Reference GuideeWON ConfigurationTag VisibilityPublished valueModbus TCP visibilityRegisterConsider as floatSNMP VisibilityInstant ValueEach Tag in the eWON can be accessed by a modbus TCP master. If the Tag must be visible: Enablethis checkbox.Address of the register, starting with 1.Only the register address has to be specified, the type of Tag (coil, contact, Input register or Holdingregister) is obtained from the Tag type (Analog or Boolean) and the Tag Read Only or Read/Writeproperty (obtained from the IO server).If this option is checked, then 2 consecutive 16 bits registers will be reserved and the value will be outputas a 4 bytes IEEE float in those 2 registers (standard Modbus float representation).If the Tag is published as integer it may need to be scaled to fit the 16 bits modbus register. Thisoperation will be applied to the Tag value to publish it.If this is checked, the Tag can be seen by the SNMP manager. The OID of the Tag can be defined. Thebase OID is already defined, the only parameter is the end of the OID.Instant value means values of Tags at a given time.The Tag's instant values are stored in the inst_val file (available in txt and binary format from the FilesTransfer link from the Main menu navigation bar from eWON). The 4 checkboxes that match the groupsthat you want to choose will work accordingly to the $ft Export Block Descriptor Tag that is described inchapter “$dtIV [Instant Values]” on page 183 in this manual. You will find there detailed information aboutInstant Value too.Table 45: Tag visibility controlsAlarm Setup‘Alarm Enabled’Check BoxAlarm level lowAlarm level highAlarm level lowlowAlarm level hihiValue Dead bandBoolean Alarm levelActivation delayAuto acknowledgeAlarm HintCheck if you want to generate an alarm on the current Tag name.Low "warning" threshold value for alarm detection.High "warning" threshold value for alarm detection.Low "danger" threshold value for alarm detection.High "danger" threshold value for alarm detection.The dead band is the difference between the alarm level and the RTN level (Return To Normal).e.g. if the alarm value is 20°C with a DeadBand=1, the alarm is triggered when the Temperature crossesthis 20°C boundary. On the other hand, the AlarmStatus will be RTN when the temperature passes below19°C (20-1).The alarm value ('0' or '1') of a Boolean Tag name –not applicable for analog Tag name-.Time in seconds for which the Tag has to be out of threshold before declaring the Tag is in an alarmstate. (This is mainly to avoid non significant alarms)If checked, the alarm will be automatically acknowledged when the alarm state goes to RTN value. Thus,the alarm is directly ended.Information related to the alarm action - This Information will be included on the alarm email-Table 46: alarm setup configuration controlsRG-001-0-EN ver 1.5 eWON® - 20/03/2009 - ©ACT'L sa Page 73
General Reference GuideeWON Configuration• Historical and real-time logging:Those fields display only for some eWON's versions (c.f. “Tags monitoring and handling” on page 68)Historical and real-time loggingHistorical logging enabledLogging dead bandLogging IntervalReal time enabledTime spanLogging IntervalIf checked, the Tag values will be logged in a circular file.Warning: This is a non-volatile logging; data are stored in the flash file system. All the data are stored inthe same file, the maximum number of values that can be saved is from 16384 to 139264, depending onthe way you have set up the resources storage in the eWON (when maximum size is reached, then theolder data will be erased first).If one Tag “a” is recorded very often (every seconds) and another Tag “b” is recorded rarely (every day),you may have your Historical Log filled with a lot of tag “a” and few (or none) tag “b” because of thecircular storage mechanism.Defines the dead band of the Tag’s incremental recording (use a negative value to disable it)Defines the interval, in seconds, for the Tag recording (set to zero to disable the logging interval).Can be used at the same time as logging dead band.If checked, the Tag values will be logged in memory.Real time logging is different from historical logging because data are saved in a circular memory buffer.The other difference with historical time logging is that incremental recording is not possible, only fixedinterval recording can be performed.Defines the total logging window time in seconds.Defines the interval, in seconds, of the Tag recordingTable 47: Historical and real-time logging controls3.4.2.1.1 Publish as Modbus TCPThis feature allows to access a Tag Value through Modbus/TCP. In that configuration, the eWON acts as a slave. Actually, there is no data mapas in most PLC, instead of that you define Tag by Tag its Modbus TCP address.3.4.2.1.1.1 Defining the Modbus TCP addressThere are 4 types of Modbus variable, Contact (RO), Coil (RW), Input Register (RO), Holding register (RW). The type selected for the Tag thatyou want to publish will depend on its type:Tag propertyBoolean, ROBoolean, RWAnalog, ROAnalog, RWModbus data typeContactCoilInput registerHolding registerTable 48: the 4 Modbus variable typesUsually, the RO or RW property of a Tag is obvious. But in case of doubt, you can confirm the type by checking the View IO for the Tag:• Remove the "Force Read Only" option in the Tag configuration (disabled by default).• Check the View IO page, if the Tag has an update field, it means it is a RW Tag otherwise the Tag is RO.• The address selected will be the address of the Modbus 16 bit register. The address range starts with register 1 (in the Modbus frame,eWON register 1 is transmitted as 0).• Publish as floatThe eWON supports accessing Tag values as float registers. The float is published with the IEEE representation and the value can be read on 2consecutive registers, with the first register starting at the user defined address.3.4.2.1.1.2 Modbus TCP rules• When accessing Modbus registers or coils that are not mapped to an eWON register, the returned value is 0.• Maximum number of registers readable in 1 request: 25• Maximum number of coils readable in 1 request: 2000RG-001-0-EN ver 1.5 eWON® - 20/03/2009 - ©ACT'L sa Page 74
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: General Reference GuideeWON Configu
Page 86 and 87: General Reference GuideIO Servers C
Page 124 and 125:
General Reference GuideIO Servers C
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?