eWON General Reference Guide - Esco Drives & Automation

More documents

Recommendations

Info

General Reference GuideIO Servers Configuration5.9.2.2.2 ABLogix : EIP Ethernet linkThe Global Device Address has the following syntax : IP Address,Port,Link• IP Address = address on your Ethernet network (i.e.: 10.0.30.7)• 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 (for example: 0=CPU)¤ Node ID: value from 0 to 99 (for ControlNet)¤ IP addressFigure 89: ABLogix : EIP address exampleREM: In the case of using a ControlLogix as Gateway, the Device Address could be like following: IP Address, Port, Link[,Port,Link][, Port,Link]…5.9.2.2.3 DH+ polling using ControlLogix gatewayThis 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 the eWON EIP protocol.The ABLOGIX IO server is used to access the “LOGIX” PLC family.The DF1 IO server is used to access the “SLC500” PLC family (See “DH+ polling using ControlLogix gateway” on page 102).The general syntax IP address,Port,Link is still applicable. There is no specific character to indicate the DH+ channel (“2” or “3” should be used).Example: To reach a PLC5 (with CPU in slot 0) with DH+ node Id 3 using channel A of a DHRIO card at slot 9 of a controllogix at IP address10.0.30.21.Topic A Destination = SLC500-10.0.30.21,1,9,2,3,1,0• 10.0.30.21 = IP address of the ControlLogix• 1 = BackPlane• 9 = Slot 9 (COM card)• 2 = Channel A (of the Card present in Slot 9)• 3 = NodeID of the PLC5 (in the COM network)• 1 = BackPlane• 0 = slot (of the CPU in our example)5.9.3 Tag name conventionIO Server ConfigurationIO server NameTopic nameABLOGIXA or B or CItem Name ValueName Topic PLC address is usedValueName, IP address[, Port, Link]ValueName, NodeIDPLC address is defined Tag by TagPLC address is defined Tag by TagTable 92: ABLOGIX IO server Tag name convention tableThe Item Name can contain the PLC address where the value is polled, or not. If the address is also specified at topic level, the address specifiedat Tag level will be ignored.RG-001-0-EN ver 1.5 eWON® - 20/03/2009 - ©ACT'L sa Page 115
General Reference GuideIO Servers Configuration5.9.3.1 ValueNameValueName follows the below syntax:[PROGRAM:ProgName.]SymbolicTagName• ProgName is the name of the program where the Tag is.If no ProgName, the Tag is in the global scope (tag is controller type)• SymbolicTagName:• Symbol of the tag.Only following atomic type are supported: BOOL, SINT, INT, FLOAT, DINT (*), BIT ARRAY• Bit selection with /bitwhere bit is the bit number (from 0 to 31)ex: controlbit/4 read the bit 4 of the controlbit register• TIMER, CONTROL, COUNTER predefined types with .acc (or ctl or pre)ex: MyVar.acc read the counter of MyVar• Element of a table[idx_1].[idx_2].[idx_3].With maximum 3 index.ex: table1[2].subtable[6].element read data named 'element' on the index 6 of the 'sub table' from the index 2 of the 'table1'• Element of a structure.ex: CounterObj.init read the 'init' part of the structure 'CounterObj'(*) Important: See “Tags are stored as Float” on page 67• Status register:The STATUS Tag is a special Tag that returns information about the current state of communication for a given device. As for other Tags, thestatus Tag ValueName is composed of:Status,ComPortNum• You can define a status Tag for each COM port used.• If you use the status address, the Tag must be configured as analog.0Communication not initialized. Status UNKNOWN.If no Tag is polled on that device address, the communication status is unknown.1 Communication OK.2 Communication NOT OK.Table 93: Tag status meaningRG-001-0-EN ver 1.5 eWON® - 20/03/2009 - ©ACT'L sa Page 116
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:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67: General Reference GuideeWON Configu
Page 86 and 87: General Reference GuideIO Servers C
Page 148 and 149: General Reference GuideMonitoring W
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?