Home

1 The Inline Ethernet/IP Bus Coupler

1. 1 2 2 3 2 45 CDE a Z lt X7 X8 x9 fao A fas Z a X18 19 Mee ale a 5 i EtherNet IP 00 93 HEIE EtherNei iP EP m m Oo Oo P T EEG FERNE RENNEN p 7 BE HE HM HE mM O Bdoobobolassesasanaseaer Bdge co Kal OO BE EHE mE mE mE mE ee nu mE mm i e8JooI0000eeeswe8saeesee aaa naar OO IE I U IN I HI HI HI EI ILDD mE mm dem ex ox 0 elee ee Oo COCO Oo Coo pi 000000 olo to DI BI BI BI HT HT Po IH I KH I IL L I AAOCICCIOO 2 Oe 2 e 2 20 2 PPE 3388 aaa ee 6 Network N LB our IN LB OUY N LB our connector si 5 o B DERE 24 V DC Ep gt Power O O 5 supply O 5 O O5 Ee Ee Er 5 Oo 5 Er Lr Er Oo Ce Q DI 8 REMES DIE MEERES 102 R O O O Fieldline Modular I O modules 75380002 Figure 2 1 Example of a basic Inline station Key 1 Bus coupler here IL EIP BK DI8 DO4 2TX PAC 2 l O modules 3 Power terminal 4 Segment terminal here IB IL 24 SEG F D 5 Branch terminal for integrating a Fieldline Modular local bus in an Inline station
2. Onboard DO8 DO2 AO1 DOs DEE ___P gt I O Data Tables Malh i Input Data Output Data s a s eiz 7 i ee Wee Ale ISIS Bit 7 4 0 Bit 7 4 0 mr lee ol W ll Dos Dos DO8 Dos DO4 DO4 DO4 DO4 eererner r MR Byte 0 Status word low byte Bit 3 Bit 2 Bit 1 Bit O Bit 3 Bit 2 Bit 1 Bit O e ae a H Bit 15 lt 8 Bit 7 4o RESET 1 211 2 1 2 1 12 1 2 1 2 esiocolooloolsolsolsoloooono Byte 1 Status word high byte UsedlUsed Bit BRO Bit7 BiG Bits Bita ac 00 OO OO OO OO OO OO OO OO OO r 88150109100100001000000100 KA Em A OB EEE mE eu mj j EI OO OO SO OO 0000000 Byte 2 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Analog output low byte ig oo oo oojoojogodjagageq OO 00010010 0100000000000 Byte 3 Analog output high byte PE PE PE PE PE PE Fie 75380005 Figure 3 11 Example of an I O table memory map consisting of analog and digital output modules 7538_en_01 PHOENIX CONTACT 3 27 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC Figure 3 12 shows an Inline station and an example I O table The station consists of the following modules Inline terminal with 2 digital inputs Inline terminal with 1 analog output Inline terminal with 2 digital outputs Inline terminal with 4 digital inputs Inline terminal with 2 analog inputs
3. 5 6 7 8 9 10 11 12 Number of Digital Inputs Number of Digital Outputs Number of Analog Inputs Number of Analog Outputs Add All I O Accept New Configuration Module Change Status Add All Mode Use Inline Status Include DSUP 7538 en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configuration Object Class Code 100gac 64hex B11 4 Values for Configuration Object Class Attributes The Number of Digital Inputs attribute determines the number of input channels to be returned in the I O produced packet The number of I O produced bytes can be calculated as Number of bytes number of channels 7 8 The Number of Digital Outputs attribute determines the number of output bytes to be processed in the I O consumed packet The number of I O consumed bytes can be calculated as Number of bytes number of channels 7 8 The Number of Analog Inputs attribute determines the number of analog input channels returned in the I O produced packet Each analog input produces 2 bytes of data in the I O produced data The number of bytes may be calculated as Number of bytes number of channels 2 The Number of Analog Outputs attribute determines the number of analog output channels Each analog output consumes two bytes of data in the I O request packet The number of bytes may be calculated as Number of bytes number of channels 2 The Add All I
4. Event8 gt 0 14 0 14 EIEZEZEIEIEZE Statice Rx Rx Rx Rx Rx Rx Rx Data 1 Data2 Data3 Data4 Data5 Data6 Data lt q Event 9 EEE 7426A138 1 1 1 1 1 4 Figure A 4 Serial fragmentation error example 1 Event 5 An error has occurred The communications path between the bus coupler and its I O has been broken If incoming serial data overflows the buffer on the serial module overflow data will be lost Events 6 to 9 Error is repaired and the connection is reestablished thus data continues to be received Fragmented Error Handling Loss of Communications from the Host to the Bus Coupler If communications is lost between the host controller an the Inline bus coupler during a read or write service the bus coupler will wait for the error to be corrected network cable is repaired and then continue to finish the serial fragmentation transaction A 16 PHOENIX CONTACT 7538_en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Communications Methods A 2 2 Method 2 Transfer of Serial Data Using Explicit Messages il The ability to send explicit messages is a function of the Ethernet IP I O scanner Not all scanners have an explicit messaging channel available to the user This manual will not document the mechanics of the actual sending of an explicit message Information of this type must be provided in the documentation for the I O scanner Configuration software can be an option to unde
5. Inline terminal with 4 digital outputs Inline counter terminal Inline power terminals I O Data Tables As seen by the master IL EIP BK DI8 DO4 2TX PAC RIN RIN Input Data Output Data Onboard DI2AO1 amp DOZDI4 Al2 DOA CNT DO4 DIE WN NO Bit 7 lt 0__ Bit 7 4 0 Ly ACHT DO4 DO4 DO4 En zta a jatele jaie Byte Status word low byte Bir T BO Bit 1 Bio BiS Bit2 Bit Bio Eae ee WE Weary ois Were dy Te 1 Bit 15 lt _ _ _ 8__ Bit 7 4 0 G So es SS J i Not Not Not Not Not Not DO4 DO4 EtherNet P Byte 1 Status word high byte Used Used Used Used Used Used Bit 3 Bit 2 m F H I ce EIT L II E IE Lid F Ta 112171 2 3 217 2 1 2 11721 1 211 2 1312 772 Bit 7 lt _ _ 0 Bit 7 lt _____ _ 0 ae OO OO OOJOO OO OO0jOoOJO0 00 00 00 00 00 Byte 2 Analog output low byte m act OO OO OO OO OO OO OO OO OO OO OO OO OO OO T 1 9520316960 aa aaaea atarata no AO mem BD ESS SSCSOTCI IS syes ee 5 BS 24 Tr Er Er nao gupit nah bye
6. Data 1 Data2 Data3 Data 4 Data5 Data6 Data Event5 gt Rx Rx O 1 1 0 1 4 ESEIEIEIEIEIEIEN Rx Rx Rx Rx Rx Status Data 1 Data2 Data3 Data4 Data5 Data6 Data lt lt Event 6 Tx Tx Tx Tx Tx Tx Tx 1 1 1 1 1 4 05 Tu 6 Gres 2f xX XX o r d Data 1 Data2 Data3 Data4 Data5 Data6 Data Event7 gt 0 1 1 0 1 4 ESEZEZIEIEZEIEIE Rx Rx Rx Rx Rx Rx Rx Status Data 1 Data2 Data3 Data4 Data5 Data6 Data lt j Event 8 1 1 1 1 1 4 COCCOLE 7524A128 Figure A 2 Serial fragmented read example The following paragraphs explain those events listed in Figure A 2 Table A 3 to Table A 9 demonstrate the order of events when issuing a fragmented read service to a PCP device Each Event should be referenced to the I O data table shown in Figure A 2 Event 1 Table A 3 shows the transmission from a master to slave when the serial fragmentation is in Idle mode Table A 3 Master to slave idle transmission Tx Tx Tx Tx Tx Tx Tx Control Data 1 Data2 Data3 Data4 Data5 Data6 Data7 ow mK a MK KK MK OK A 10 PHOENIX CONTACT 7538_en_01 Event 2 Event 3 Event 4 Event 5 7538 en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Communications Methods Table A 4 shows the slaves response to the idle state by replying with a OOnex Table A 4 Slave to master idle response Rx Rx Rx Rx Rx Rx Rx Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 Data 7 Master still sending the id
7. Interface Configuration Status 0 Not Configured 1 Valid Configuration 2 15 Reserved 2 Configuration The Configuration Capability indicates the devices support for optional network capabilities En En Client TRUE indicates the device can receive its congue via BootP DNS Client TRUE shall indicate the device is capable of lie host names by querying a DNS server 2 DHCP Client 1 TRUE shall indicate the device is capable of Da its network configuration via DHCP DHCP DNS Update TRUE shall indicate the device is capable of sending a host name in the DHCP request Configuration Settable TRUE shall indicate the Interface Configuration ae is settable 3 Configuration The configuration control attribute tells the device how to determine its network Control configuration Startup Configuration O Use configuration stored in NV 1 Use BootP 2 Use DHCP 3 15 Reserved DNS Enable If 1 the device will resolve host names by using DHCP Currently O and 1 are the only valid values for Attribute 3 Future revisions will include the value of 2 7538_en_01 PHOENIXCONTACT B 41 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC B20 Ethernet Link Object Class Code 246 gac F6hex B20 1 Ethernet Link Object Class Attributes ibe _JAocass name mm ie B 20 2 Link Object Instance Attributes Access Name Type Ta 0 nennen Tr a oo Get___ PhysicalAacr
8. Installation Table 2 3 Terminal point assignment of the output connector 2 O1 GND GND Table 2 4 Terminal point assignment of the input connector 3 11 Ca a2 o U i U Ethernet IP 75370005 Figure 2 4 Connection example J internal jumper in the module 7538 _en_01 PHOENIX CONTACT 2 5 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC 2 6 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Startup Operation 3 Startup Operation 7538 en_01 3 1 Default Upon Delivery Default Settings Upon delivery the following functions and features are available IP Configuration IP Address 0 0 0 0 Subnet Mask 0 0 0 0 Default Gateway 0 0 0 0 BootP Requests Enable Software Update Software Update on Next Reboot Disable TFTP Server IP Address 0 0 0 0 Downloadable File Name c2897758 fw System Identification Name of Device IL EIP BK DI8 DO4 2TX PAC Description Ethernet IP Bus Terminal Physical Location Unknown Contact Unknown Process Data Monitoring Process Data Watchdog Timeout O ms Disabled Fault Response Mode Reset Fault Mode Default Plug and Play Mode Enable inputs amp outputs 3 2 Starting the Firmware Upon delivery the IL EIP BK DI8 DO4 2TX PAC bus coupler has no valid IP parameters Once you have connected the power to the bus coupler the firmware is started The
9. Output Data Type The analog output data type is fixed as 6 UINT 9 Fault State The Fault State determines what action is taken if a fault condition is detected Fault conditions include software conditions connection timeout Action Taken Hold the last value Set to low limit 0 V DC Set to high limit 10 V DC Set to value determined by Fault Value 10 Idle State The Idle State determines what action is taken if an idle condition is detected Idle conditions occur if an I O request packet is received with less than the calculated number of bytes or the run idle header is set to idle and the run idle header is enabled Refer to the Configuration Object to determine the size of the I O request data An I O request of 0 bytes is typically used to force an idle condition if the run idle header is not enabled Idle State Action Taken Hold the last value Set to low limit 0 V DC Set to value determined by Fault Value t Set to high limit 10 V DC 11 Fault Value The Fault Value determines the output if the Fault State bit is set to 3 and a fault condition occurs The value must be in the range 0 65535 0 FFFFyax 12 Idle Value The Fault Value is used to set the output if the Idle State bit is set to 3 and an idle condition occurs The value must be in the range 0 65535 0 FFFFhex 100 AOP Response This attribute allows the user to see the response coming back from the AOP module Dat
10. Device Lonfiguration a J Device Configuration a ee eae Inline Station i i Diagnostic Parameter No additional information available EEE Register Process Data Monitoring Remote Diagnostics Bus Configuration PCP Configuration J Home Figure 3 3 Remote diagnostics in WBM PHOENIX CONTACT 3 5 IL EIP BK DI8 DO4 2TX PAC 3 6 PHOENIX CONTACT THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS 3 5 2 Services In this example website the user can set or reset the Plug amp Play Modes The user can acquire and store the currently connected I O configuration Also the user can confirm any I O station peripheral faults Ba IL EIP BK DI8 DO4 2TX PAC last update 13 12 39 CONTACT Services Plug amp Play Plug amp Play O IL EIP BK DI8 DO4 Mode Inputs Only Inputs amp Outputs Disable When in Plug and Play Mode during power up the buscoupler will automatically attempt to start the local I O When disabled the buscoupler will compare the stored I O configuration with the connected I O and start if equal C Device Configuration Note Reboot not required to implement changes d General Instructions C Device Information y Inline Station Sonne Enter password Apply Apply and Reboot Process Data Monitoring Remote Diagnostics Store Connected I O Configuration S Confi Click Store Config to acquire store and utilize the currently connected I O E Bus Configuration configuration The P amp P mode o
11. following sequence appears on the LEDs Table 3 1 LEDs during the starting sequence Display BO flashing Starting Boot loader Transmitting BootP requests Extracting firmware BO off Starting firmware RY flashing Firmware ready to operate PHOENIX CONTACT 3 1 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC 3 3 Sending BootP Requests BootP Enabled During start up the device sends BootP requests without interruption until it receives a valid IP address The requests are transmitted at varying intervals 2 s 4s 8s 2 s 4 s etc so the network is not loaded unnecessarily If valid IP parameters are received the device will use these parameters until the device is reset or power is cycled BootP Disabled With a valid IP configuration saved to the device and BootP disabled the device will start with the stored IP configuration and will not send BootP requests il NOTE Before disabling automatic BootP setting be sure to record the current IP address You will need the current IP address if you want to re enable BootP setting of the IP address If you forget the IP address the only way is to delete the whole configuration with the reset button during power up 3 4 Web Based Management WBM The IL EIP BK DI8 DO4 2TX PAC has a web server which generates the required pages for web based management and depending on the requirements of the user sends them to the Factory Manage
12. memory of the bus coupler If the bus coupler is replaced the serial configuration will need to be sent again unless the configuration explicit messages are embedded into the control program The explicit message format required to configure the RS 232 or RS 485 RS 422 modules is as follows service Set_Attribute_Single 16gec 1 Ohex Class Code 106 gec 6Anex Serial Communications Object Instance 1 1st serial module Attribute 12 This attribute is used to modify the baud rate Data 08 Refer to the RS 232 module s data sheet Code 08 represents a baud rate of 19 2K Instance is the occurrence of the module within the Serial Communications Object Instances are assigned by the physical order of the serial Inline modules on the station starting with the module closest to the bus coupler being assigned to instance 1 The next module to follow will be assigned to instance 2 and so on up to a maximum of 8 instances There is amaximum of 8 PCP modules of any kind allowed to reside on the Inline station Both the RS 232 and RS 485 RS 422 modules occupy instances in the Serial Communications Object If one of each reside on the station the closest to the bus coupler will be assigned to instance 1and the other will be assigned to instance 2 7538_en_01 PHOENIX CONTACT A 43 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC A 44 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUT
13. the buscoupler will compare the stored I O configuration with De Informati p pa g Device In u the connected I O and start if equal C Device Configuration Note Reboot not required to implement changes Inline Station ores Enter password Apply Apply and Reboot Process Data Monitoring Remote Diagnostics Store Connected I O Configuration Bus Configurati Click Store Config to acquire store and utilize the currently connected I O Bus Configuration configuration The P amp P mode of the device will be set to disabled following PCP Configuration completion of this function Home Enter password Store Config Control Device Function This service can be used to confirm the peripheral faults of all modules Enter password Figure 3 9 Plug and Play mode PHOENIX CONTACT 3 19 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC 3 20 il Sending an Explicit Message Method When configuring the bus coupler of an Inline station by sending an explicit message observe the decisions stated under Section Electronic Data Sheet EDS File Method on page 3 17 The parameters listed there can also be configured by sending multiple explicit messages to the Configuration Object Class Code 100gec 64hex When using the explicit message method to change defaults the following command structure must be used to configure the Ethernet IP bus coupler Service Code 16gec 10hex
14. 101 Attributes 3 Produced input Data Array of USINT B 6 4 Assembly Object Common Services Service Code Class all Service Name B 6 5 Assembly Instance 100 Assembly instance 100 is used to consume the I O data and consists of a variable number of digital output states and a variable number of analog output values as specified by the Configuration Object B 6 6 Assembly Instance 101 Assembly instance 101 is used to generate the I O produced data Assembly Instance 101 consists of a variable number of bytes that is specified by the Configuration Object B 6 PHOENIX CONTACT 7538 _en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Digital Input Point DIP Object Class Code 084ecs O8hex B7 Digital Input Point DIP Object Class Code 08 g O8hex The Digital Input Point DIP Object models digital inputs in a product You can use this object in applications as simple as a toggle switch or as complex as a digital I O control module There is a separate instance for each digital input available on the device B 7 1 DIP Object Class Attributes atwibute Access Name tye Vale UINT Max Object Instance UINT Number of DIPs B7 2 DIP Object Instance 1 Number of DIPs Attributes Access Name me Vae see BTA Input State BOOL OFF 1 ON Input Status BOOL Okay 4 1 Fault 100 Get Set Latch Enable BOOL 0 Off 1 Latch 101 Get Set Latch State BOOL 0 Latch Low 101 1 Latch high B 7
15. 3 DIP Object Common Services Service Code Service Name Get_Attribute_Single 7538 _en_01 PHOENIX CONTACT B 7 IL EIP BK DI8 DO4 2TX PAC 3 4 Input State Input Status 100 Latch Enable 101 Latch State B 8 PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS B 7 4 Values for DIP Object Class Attributes This attribute provides the state of the specific digital input A value of O indicates an OFF state and a value of 1 indicates an ON state The digital inputs provide feedback of the digital output states If the corresponding output state is set to O these points may be used as inputs The Input Status bit indicates if an error has occurred associated with a physical input If the 24 V DC power is not present the circuitry cannot accurately determine the state of the inputs and will set the Input Status bits of inputs 1 24 The status bits are cleared when the 24 V DC power is restored When set to 1 the corresponding input instance is latched at the state defined in Attribute 101 This attribute defines the state of the inputs that will be latched O latch low input 1 latch high input 7538 _en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Digital Output Point DOP Object Class Code O9gac O9hex B8 Digital Output Point DOP Object Class Code O9 yec O9nex The Digital Output Point DOP Object models digital outputs in a produ
16. BCE O Padding Actual AlPs Reserved AlPs AOP Response Data Special Function Data PCP Data PCP Module X Process Data PCP Module X Response Fragment SCO Data SCO Module X Status Word SCO Module X Receive Fragment gt Enabled Disabled gt All produced elements of the same priority will be mapped together regardless of their location However their relative location to the bus coupler will be used to determine their instance values sequential ordering This same approach applies to consumed elements Analog channels will start at the first completely unused byte after the last digital module If the total number of digital points of the same image is not modulus 8 there will be unused bits between the digital data area and the analog data area u ES Fe ce eo ES 3 26 PHOENIX CONTACT 7538_en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Startup Operation Depending on what I O modules are connected to the bus coupler determines whether or not analog data starts on an even or odd byte In those cases when analog data starts on an odd byte analog data will span two words in the master scanner If you prefer to have analog data to start on an even byte set the EDS parameter 2 Pad I O toa 1 Then download to the bus coupler This will prevent analog data from starting on an odd byte without regard to the I O modules connected to the bus coupler Once parameter Pad
17. Byte Byte Byte 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 Control Tx Tx Tx Tx Tx Tx Tx Data 1 Data2 Data3 Data4 Data5 Data6 Data Event1 gt 0 1 1 0 1 4 ENEZEIEIEIEZEIEZ Status _ R Rx Rx Rx Rx Rx Rx Data 1 Data2 Data3 Data4 Data5 Data6 Data7 11 1 1414 lt q Event 2 ENEZEIEIEIEZEIEZ Tx T Data 1 Data2 Data3 Data4 Data5 Data6 Data7 1 1 0 1 4 x Tx Tx Tx Tx Tx Even gt i g 17 AB hex 65hex 6Chex 6Chex DF hex 20hex IT hex hex H e P ii o ee W Status Rx Rx Rx Rx Rx Rx Rx Data 1 Data2 Data3 Data4 Data5 Data6 Data 1 1 1 1 1 4 lt q Event 4 Tx Tx Tx Tx Tx Tx Tx Data 1 Data2 Data3 Data 4 Data5 Data6 Data Event 5 BF 724 Cry 64 21 eee 05 i hex hex a hex 7 hex hex XX XX ai O r d Status Rx Rx Rx Rx Rx Rx Rx Data 1 Data2 Data3 Data4 Data5 Data6 Data HEERE lt q Event 6 oom x a o ax a Tx Tx Tx Tx Tx Tx Tx Data 1 Data2 Data3 Data4 Data5 Data6 Data Event7 gt 0 1 1 0 1 4 ENEIEZEIEIEIEIEZ Rx Rx Rx Rx Rx Rx Rx Status Data 1 Data2 Data3 Data4 Data5 Data6 Data lt Event 8 1 1 1 1 1 4 ESEIEIEIEIEIDIEN 7426A134 Figure A 3 Serial fragmentation write example The following paragraphs explain in detail those events listed in Figure A 3 Table A 10 to Table A 15 demonstrate the order of events when issuing a fragmented write service to a PCP device Each Event should be referenced to the I O data table shown in Figure A 3 Event 1
18. Class Code O2 gag O2hex eceeeceeeeeeceeeeeeeeteeeeeeeeeeeaneaeneeeeeeeees B 5 B6 Assembly Object Class Code OAgac OAnax rrseseeeerenenennnnnnnnnnnnnnnnnnnnnnnnnnnnnnnen B 6 B7 Digital Input Point DIP Object Class Code O08 gac O8hax rmmmmmnnnnnennnnnnnnn nenn B 7 B8 Digital Output Point DOP Object Class Code O9gecs O9p ex eeeeeeeeeeeeeeeeeeeeees B 9 B9 Analog Input Point AIP Object Class Code 10gac OAney rem B 11 B10 Analog Output Point AOP Object Class Code 11 gag OBhax eeeeeeeeeeeeeeeeeees B 13 B11 Configuration Object Class Code 100 gec O4hey eeeeeeeeeeeeeeeeeeeteteeteeeteeeeeeenaees B 15 B12 Inline Interface Object Class Code 101 gag 65hax essssesseeereeeeeeeeeeeeeeeeeeeeeeeeeeas B 20 B13 Inline Module Object Class Code 102gac 66 hey sssseeseeeeeeeeeeeeeeeeeeeeeeeeeeeeeas B 23 B14 Inline Special Function Object Class Code 103 qe 67 hey Hr een B 25 B15 COS Mask Object Class Code 104 ga 68hax HHHHH 34H nennen nennen B 27 B16 PCP Object Class Cog WS doc 69hax ssssseeeeeeesssssecceseesseseeeeeerseeeseeeeaseeseeees B 30 B17 Serial Communications Object Class Code 106gac 6Ahax eeeesceeeeeeeeeeeetteeeees B 34 B18 Port Object Class Definition Class Code 244gecs Fahey svccccccccrettttttetttteteen B 39 B19 TCP IP Interface Object Class Code 245gecs FShax rrrrseeere een e nennen nennen B 40 B20 Ethernet Link Object Class Code 246gec F6hex ceeceeeeeeeeeeeeeeeteeee
19. Class Code 100 gec 6Ahex Instance 1 Attribute X X Attribute to be changed Attribute Data 1 If no default settings need to be changed you still must send one explicit message using the following command structure to configure the Ethernet IP bus coupler Service Code 16 gece 10hex Class Code 100 gec 6Ahex Instance 1 Attribute 7 Add All I O Attribute Data 1 Setting Attribute 7 Add All I O to a 1 instructs the bus coupler to scan its local bus and store its current configuration into the bus coupler s flash memory This configuration will remain in flash memory until the next Add All I O is sent or until a different configuration method is used The service that allows Attribute 7 to be set is Service Code 16gac 10hex Set_Attribute_Single Object classes and services are described in Appendix B Ethernet IP Object Classes Message Types and Services The construction software RSNetworx for EIP or Pyramid EIP scan software can be used to send explicit messages PHOENIX CONTACT 7538 _en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Startup Operation 3 10 2 Analog Input Al Modules General Configuration Non multiplexed standard analog input Al modules default to a unipolar range of O V DC to 10 V DC To change this range the range attribute can be set in the Analog Input Point AIP Object Class Code 10gac OAhex Set the range by sending an explicit message usi
20. Failure Endpoint 2 a connection failure 4 2 6 Inline Control Byte The Inline Control Byte is used to acknowledge latched peripheral faults bit 0 or to clear latched inputs states bit 1 For an explanation of latching input states refer to Section I O Data Transfer on page 3 30 By default the Inline Control Byte is not added to the poll It can be added by setting Instance 1 Attribute 32 of the Configuration Object Class Code 64 to a 1 If the user would rather access this byte through an explicit message a Get or Set can be sent to the Inline Interface Object Class Code 65pex Instance 1 Attribute 20 Bit 0 When set to a 1 will attempt to clear all latched peripheral faults Bit 1 When set to a 1 will clear all latched input states The latched peripheral fault can only be generated by certain Inline modules Examples of this type of module are the IB IL SEG ELF and the IB IL 24 EDI 2 DESINA 4 6 PHOENIX CONTACT 7538_en_01 Parameter 16 Parameter 17 Parameter 18 Parameter 19 Parameter 20 Digital Output Support Analog Output Support 7538 en_01 il onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Diagnostics 4 2 7 I O Point Channel Status The fault status of a digital analog or special function point is either O functioning or 1 failed The fault status can be added to the poll through the EDS file or solicited by issuing an explicit message to the Co
21. For other terminals the number of process data words is indicated Example An IB IL AO 2 has two process data channels and an IB IL 24 DO 8 has eight bits and therefore eight process data channels PHOENIX CONTACT 3 11 IL EIP BK DI8 DO4 2TX PAC 3 12 PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS PD_WORDS Number of process data words in an Inline terminal Please note that analog terminals always have the same number of output and input words An IB IL AO 2 therefore also has two input words and an IB IL Al 2 also has two output words PD_IN This area is used by all terminals that occupy input data The number of process data words depends on the terminal type PD_OUT This area is used by all terminals that occupy output data see also PD_OUT on page 3 13 Examples a Inline terminal with two active inputs lt IL_MODULE number 1 gt lt MODULE_TYPE gt DI lt MODULE_TYPE gt lt PD_CHANNELS gt 2 lt PD_CHANNELS gt lt PD_WORDS gt 1 lt PD_WORDS gt lt PD_IN word 1 gt 3 lt PD_IN gt lt IL_MODULE gt b Inline terminal with two digital inputs and only the second input is active lt IL_MODULE number 3 gt lt MODULE_TYPE gt DI lt MODULE_TYPE gt lt PD_CHANNELS gt 2 lt PD_CHANNELS gt lt PD_WORDS gt 1 lt PD_WORDS gt lt PD_IN word 1 gt 2 lt PD_IN gt lt IL_MODULE gt c Inline terminal with 16 digital inputs and the 13th and the 14th input are active l
22. Fragmented Read Fragmented Write Error Handling Communications Backplane Break Error Handling Host Communications Loss PHOENIX CONTACT A 9 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC Fragmented Read Example Figure A 2 shows an example I O data table that contains only eight bytes of input data and eight bytes of output data This I O is shown in an event by event sequence that demonstrates how these eight bytes of I O are updated when reading data using Serial PCP fragmentation The sequence works on this following basic principle Event x Client issues server 8 bytes of output data Event x 1 Server responds by updating 8 bytes of input data Input Data Table Output Data Table Event Sequence for Bytes 0 to 7 Event Sequence for Bytes 0 to 7 Byte Byte Byte gt Byte 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 eR e r TX Ree Control Data1 Data2 Data3 Data4 Data5 Data6 Data7 Event 1 0 1 1 0 1 4 ESEIEZEIEIEIEIEN Status Rx Rx Rx Rx Rx Rx Rx Data 1 Data2 Data3 Data4 Data5 Data6 Data 1 1 1 1 1 4 lt q Event 2 ESEIEZEIEIEIEIEN Tx Tx Tx Tx Tx Tx Tx Data 1 Data2 Data3 Data4 Data5 Data6 Data7 Event3 gt 0 1 1 0 1 4 EHEIEIEIEIEIEIEN Rx Rx Rx Rx Rx Rx Rx Status Data 1 Data2 Data3 Data4 Data5 Data6 Data 1 1 1 1 1 4 lt j Event 4 27 AB nex Bi 6C BC nex BF 4 ZU Sf hex nex H e pP p o m W Tx Tx Tx Tx Tx Tx Tx X
23. I O is set one byte of unused I O data may be added to the produced consumed size This byte of unused I O data will force the analog word to always start on an even byte in the master scanner If the physical configuration dictates that the analog word starts on an even byte and parameter Pad I O will not add a byte of data to the I O data size The physical order of data in the I O table is determined by the position of the modules on the local bus The first module connected to the Inline Ethernet IP bus coupler will reside in the first I O byte keeping in mind the which data type comes first rule Furthermore the LSB of the first module will be assigned to the first instance The next module of the same type and image will line up next to the first module without leaving any gaps in the I O table The example in Figure 3 11 consist of the following modules Inline bus coupler with 4 digital outputs and 8 digital inputs onboard Inline terminal with 8 digital outputs Inline terminal with 2 digital output Inline terminal with 1 analog output Figure 3 11 shows an example I O table memory map for the station shown below The total amount of input bytes Inline Status Word would be 3 and the total amount of output bytes would be 4 IL EIP BK DI8 DO4 2TX PAC ae E
24. O attribute will add all Inline I O modules to the I O connection The Accept New Configuration attribute will keep the current I O setup even though modules may have been added or deleted This will clear the I O Module change flag in the status attribute Inline Modules have been changed since the last configuration veins sma Bis Bm2 em Bio Bio me ear ete Bis ma ms Bie ein Bio The Add All Mode attribute allows the user to select which type of I Os and faults will be added when the add all attribute Attribute 7 is set Default is 000Fhex meaning all DIPs DOPs AIPs and AOPs will be added no faults or special function modules are added When set the first byte of the I O produced data contains the Inline Status and the second byte contains the number of the first module in the stack with a fault Adds 2 bytes to produced size When set the first byte of the I O produced data contains the Device Supervisor exception status byte Adds 1 byte to produced size PHOENIX CONTACT B 17 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC 13 Special Function When set the Inline EIP BK will put the process data for the Special function modules with Modules the Data In Attribute set in the I O consumed and I O produced 14 Pad I O When set this attribute will add an extra byte if necessary to align the analog inputs and outputs to word boundaries Will ad
25. Object SCO is the Transmit Data parameter This attribute is required to transfer data to a serial module To transmit data to the serial module the user will send an explicit message with the following parameters Node address Service Code 16 ge Set_Attribute_Single Class 106 gec Serial Communications Object Instance 1 In this case the 1st occurrence of a serial module Attribute 8 Transmit data Instance is determined by the physical location on the Inline station The 1st instance will be assigned to the serial module RS 232 or RS 485 RS 422 located closest to the bus coupler and the last instance maximum of 8 will be assigned to the right most module When this message is sent the bus coupler will send its response back to the sender Typically an I O scanner control bit is set when an explicit response is present At that point the response can be read When sending a transmit command the user can expect a positive or negative confirmation in return The first byte transmitted to the bus coupler will be the number of bytes to follow These A 18 PHOENIX CONTACT following bytes are the actual data that is being sent to the serial module 7538 _en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Communications Methods A 2 3 Method 3 Transfer of Data Using PCP Fragmentation This method defines how PCP data is exchanged using process cyclic data with an Inline module
26. Service 000 BYTE ss ee ARRAY ARRAY of USINT 7 en Get Set Transmit Data ae STRUCT of 10 B 34 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Serial Communications Object Class Code 106gac 6Ahex Type Value see B 17 4 OTR Contol oe DTR Control z B 17 3 Serial Communications Object Common Services Get_Attribute_Single B 17 4 Values for Serial Communications Object Class Attributes 3 Module Type This value indicates the module type of the serial module 0 RS 232 1 RS 485 RS 422 4 Module Status This value indicates the module status 0 Ok 1 Faulted 5 Serial Status Word MSB Bits Bit14 Bit13 Bit12 Bit11 Bitto Bio Bits Number of Received Characters Mode Dependent LSB Reserved Transmit Transmit Receive Re Init Send Error Receive Received Buffer Not Buffer Full Buffer Full Executed Error Buffer Not Empty Empty 7538_en_01 PHOENIX CONTACT B 35 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC 6 Serial Control Word MSB enas Bita itis sie Bit sitio Bio Bie Pe a ae on ae oe e o Reserved Reserved Reserved Execute Reset Send Reserved Re Init Error Receive Error Receive Data This attribute allows the user to read the serial data in one Get_Attribute_Single The format is a SHORT_STRING 8 Transmit Data This attribute allows the user to transmit serial
27. a level of network traffic it can not accomplish In these cases the module will stop communicating and go into a fault state In addition to physically larger I O stations use of PCP communications RS 232 modules etc requires extra processing therefore potentially higher larger ms RPI settings While actual settings will vary based on the station configuration and application requirements as a general rule of thumb the following considerations should be followed Configurations requiring RPI rates below 10ms should be tested in advance to confirm operation Configurations requiring PCP modules should use RPI settings at a minimum of 20 ms Settings below 20 ms should be tested in advance 3 13 2 Maximum Connection Consideration The module firmware supports up to 128 connections total any mix implicit or explicit Application considerations such as CPU loading frequency of data updates RPI parameter and I O quantity scanned will impact the actual maximum connections Fewer connections allow faster data update rates RPI value For maximum I O performance the quantity of connections should be limited to 8 or less 7538_en_01 PHOENIX CONTACT 3 33 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC 3 34 PHOENIX CONTACT 7538_en_01 4 Diagnostics Diagnostic Indicators Status Indicators il LEDs on the Ethernet IP Bus Coupler 7538_en_01 THE ONLINE DISTRIBUTOR OF E
28. back of the module The Electronic Data Sheet EDS can be found on the Internet at www download phoenixcontact com PHOENIX CONTACT 1 1 IL EIP BK DI8 DO4 2TX PAC Features Module Features Inline Features Ethernet and CIP Features Applications il 1 2 PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS The key features of the IL EIP BK DI8 DO4 2TX PAC are listed below 2 x Ethernet twisted pair according to 802 3 with auto negotiation and auto crossover connected via an integrated 3 port switch 2 external ports 1 internal port Ethernet connection via 8 pos RJ45 female connector Ethernet TCP IP with 10 100 Base T X Industrial Ethernet IP Version 1 2 Process data access via XML Web based management WBM IP parameter configuration BootP WBM Static IP DHCP to be added on later revision Integrated web server Eight digital inputs Four digital outputs Diagnostic and status indicators Up to 61 other Inline terminals can be connected process data channel Up to eight other PCP modules can be connected Can be installed in the field software for automatic configuration of the station is not required Automatic baud rate detection on the local bus 500 kbaud or 2 Mbaud For additional information about the supported Inline modules please refer to the I O Modules at Bus Couplers application note It can be downloaded at www download
29. each PCP module that is designed for serial communications It is possible to access an instance of the Serial Communication Object into an instance in the PCP Special Function Object Examples of Serial Communications PCP modules are RS 232 RS 485 3 13 System Operational Guidelines 3 13 1 Repeat Packet Interval RPI Settings When setting up an Ethernet IP system care must be exhibited when setting the RPI value in the control system scanner Depending on the vendor s implementation this value may range from 5 ms to 100 s of ms in 5 ms increments The RPI value establishes the rate at which the scanner will send Ethernet IP messages packets It also establishes the maximum rate that the Inline station in this case will send messages Though the value is set in the PC PLC scanner is also transferred by the scanner to the BK so that the system is working on the same time base In addition to setting the speed of the network updates the RPI value is used to set the rate at which the scanner expects to receive back in time the scanner will assume there is a problem stop I O communications and the I O station will go into its fault response mode As is true with most Ethernet IP devices Inline included the CPU in the BK splits its time servicing the Ethernet IP network performing internal functions such as updating internal websites and of course scanning O In larger I O systems setting the RPI too low may overload the BK with
30. event 6 bit 5 0 Indicates that new data is present Bits 2to0 5 Shows the number of bytes received Table A 8 shows the master to slave acknowledgment of a Receive Request indication Table A 8 Master to slave receive data acknowledgement Control Tx Tx Tx Tx Tx Tx Tx Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 Data 7 Control byte 0 OOnex Bit5 0 After the 5 bytes have been received and processed the Receive Ack bit is set to the same value as the Receive request bit to signal the module that the master is ready to receive more data Table A 9 shows the slave to master indication that no more data is present Table A 9 Slave to master no more data indication Rx Rx Rx Rx Rx Rx Rx Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 Data 7 7538 _en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Communications Methods Fragmented Write Example Figure A 3 shows an example I O data table that contains only eight bytes of input data and eight bytes of output data This I O is shown in an event by event sequence that demonstrates how these eight bytes of I O are updated when reading data using serial PCP fragmentation The sequence works on this following basic principle Event x Client issues server 8 bytes of output data Event x 1 Server responds by updating 8 bytes of input data Input Data Table Output Data Table Event Sequence for Bytes 0 to 7 Event Sequence for Bytes 0 to 7 Byte gt
31. ex Ox OO 000000000000 00000000000000 l gh aml 00 00 00 ool yoo Im Bit 7 lt _ 0 Bit74 0 Se OOO OOO OOOO OOOO Byte 4 Analog input 1 low byte 1 Counter word 0 low byte PE PE PE PE PE PE PE PE PE PE Bit 15 lt lt ____ _ 8 Bit 15 3 Byte 5 Analog input 1 high byte 1 Counter word 0 high byte Bit 7 lt _ _ 0 Bit7 0 Byte 6 Analog input 2 low byte 2 Counter word 1 low byte Bit 15 lt lt _ 8 Bit 15 8 Byte 7 Analog input 2 high byte 2 Counter word 1 high byte Bit7 lt __ 0 Byte 8 Counter word 0 low byte Bit 15 4 8 Byte 9 Counter word 0 high byte Bit7 0 Byte 10 Counter word 1 low byte Bit 15 lt 8 Byte 11 Counter word 1 high byte 75380006 Figure 3 12 Example of an I O table memory map consisting of digital and analog input and output modules The I O configuration is for data mapping example only Please follow the installation guidelines in the IL SYS INST UM E user manual Figure 3 12 shows that the total number of input bytes is 12 byte O through byte 11 This includes the Inline Status word Figure 3 12 also shows that the total number of output bytes is 8 byte O to byte 7 3 28 PHOENIX CONTACT 7538_en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Startup Operation 3 11 2 Reserving I O Memory for Future System Expansion Memory reservation is only available for digita
32. how the start fragment request is sent from the master to the slave to initiate a write This message is built with the format shown below Note that the target index IS SFEOpex Table A 34 Master to slave write request sending a O2hex service Module Index Service byte 0 12 pes Fragmented write Bit 4 Indicates that the write is fragmented Bits 0 to 3 Write service 02hex Module Number byte 1 O1pe First PCP module on the Inline station Index Low byte 2 EQnex Low byte of the PCP index to be read Index High byte 3 OF pax High byte of the PCP index to be read Subindex byte 4 OOnex Subindex is zero Length byte 5 10pex 16 bytes Bytes 6 and 7 XXhex First 2 data bytes Event 4 Table A 35 shows the acknowledge from the slave that indicates the write request fragment was processed In this acknowledge the service byte reflection is the indication that the 1st response was received Table A 35 Slave to master acknowledgement of the write service Service 1 2hex A 32 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Communications Methods Event 5 Since the reception of the first 2 bytes of data has been processed and acknowledged the master is ready to send the next fragment This second fragment is a middle fragment with a slightly different format Table A 36 shows the service byte and the next 7 bytes of data to be written to index 5FEO This request is explained as follows Table A 36 Mas
33. it Power down and reconnect the I O to the bus coupler The Module Connection Error bit will be set when the bus coupler is no longer able to talk to the modules connected to it and can determine the failure position This failure occurs due to a broken data path The exact path between what two modules can be read from the Inline Interface Object Class Code 65pex This bit can only be set in the Fault Response mode 2 It is made available to let the application know that the local outputs have gone to their preprogrammed Ethernet IP fault state and will no longer respond to the controller Reserved for future use 4 2 4 Bit Meanings for Inline Status Word Byte 1 Contains the first failed device number The device number determines the position on the Inline station where a failure or warning has occurred These positions are numbered starting at the bus coupler being assigned with a 1 The numbering will continue to the right up to 64 which is the maximum number of devices that can be connected to an Inline station 63 I O devices including two devices on the bus coupler 1 bus coupler Inline local errors will not be sent over the network unless the Inline Status Word is in the poll or an explicit message to the Inline Object is sent periodically These errors by default are considered a major except for a peripheral fault error and the MS LED on the bus coupler will blink red A determination must be made regarding the Inlin
34. messages is a function of the Ethernet IP I O scanner Not all scanners have an explicit messaging channel available to the user This manual will not document the mechanics of the actual sending of an explicit message Information of this type must be provided in the documentation for the I O scanner Configuration software can be an option to understand the structure of an explicit message before the message is actually integrated into the control program The PCP Special Function Object Class Code 105gac 69hex is detailed further in Appendix B Ethernet IP Object Classes Message Types and Services When sending PCP messages using explicit messages I O scan size can be reduced by removing the eight bytes of fragmentation data that is added to the produced and consumed sizes by default This can be accomplished by using the PCP Special Function Object PHOENIX CONTACT A 37 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC A 2 4 1 Reading PCP Data When reading PCP data from a PCP module that is not a serial based module the PCP Special Function Object Class Code 105 ge 69hex Must be used Within this object there are two sub methods that can be used to read data explicitly Sub method A involves directly requesting reading the complete PCP services using attributes 6 and 7 Sub method B provides greater efficiency It fixes the module number index and subindex so that only t
35. nen 4 7 4 2 9 Inline Analog Input Thermocouple and RTD Fault Codes 4 8 42 10 Error IANS OY ae ee Wenns 4 8 5 Technical Data and Ordering Data u 4u0044400444nRRnnnnnnRnn nenne nenn nenne nenne nenne nenne nennen ern 5 1 5 1 Technical Data seinien nn AERO Taia 5 1 52 Ordering Dad Wine ut 5 5 A Serial and Other PCP Inline Modules u0 40002000220400 Renee nnnnennnnn nenne nnnnn nenne nenne nennen A 1 A1 CSONGl Als E a Wee nnstiecsdwsestershhasndiaediieenddedadbeeneieeiiideteisddceexdendedevenndeedicns A 1 A2 Communications Methods ccccsecccceeeeeceeceeseeecaeeceeeeseaseeeeseaueeeeesaeeeeesseeees A 7 A3 Serial and Generic PCP Modules Produced and Consumed Sizes A 40 A4 O Memory Mapping Serial and Special Function PCP Modules A 42 A5 Configuration Brief for the RS 232 and RS 485 RS 422 Modules A 43 il PHOENIX CONTACT 7538_en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Table of Contents B Ethernet IP Object Classes Message Types and Services nuueasssensnnenenenennnnnnnnnnnennneennne B 1 B 1 MS FNS E escent saat ees se Sees acpi cess esas eee de pees en aoe cae B 1 B2 Ge Glass 2 6 6 coe ee eee ee ee B 1 B3 CIP Object Classes eecccceseeccccceseeeeceneeeececeuseeeceaaeeeeseaeeeesseuseeesseeeeesseaeeesens B 2 B4 identity Object Class Code 011 gags Dis anne ae B 3 B5 Router Object
36. occurrence of the PCP device within the object Attribute 9 PCP Write Index Example Index number 5FEO hex 2 Build Select Subindex Message Message is sent using the Set_Attribute_Single service 16 gec Class Code 105gec 69h ex POP Special Function Object Instance Select the occurrence of the PCP device within the object Attribute 10gec PCP Write Subindex Example Subindex number 0 3 Build Read Data Message Message is sent using the Set_Attribute_Single service 16gec Class Code 105gec 69hex POP Special Function Object Instance Select the occurrence of the PCP device within the object Attribute 11gec PCP Write Data Data First byte contains the number of bytes to be sent then the actual data Instance is determined by the physical location on the Inline station The 1st instance will be assigned to the PCP module located closest to the bus coupler and the last instance maximum of 8 will be assigned to the right most PCP module Serial modules will occupy an instance in this object The PCP module attribute attribute 8 defaults to the instance value When message 3 is sent the bus coupler will receive the data from the sender The first data byte returned by bus coupler will be the number of bytes to follow These following bytes are the actual data that was sent by the PCP module PHOENIX CONTACT A 39 IL EIP BK DI8 DO4 2TX PAC THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS A3 Serial and Generic PC
37. service confirmation a Write Response This is sent back as a service confirmation in our example as a Write Confirmation The bus transmits the content of the information in the form of a PDU message Protocol Data Unit A service consists of the following four basic operations Service Request The client transmits its service request with this basic operation Service Indication The service input is reported to the server with this basic operation Service Response The server transmits the service confirmation with this basic operation Service Confirmation This basic operation confirms execution of the service it is the service acknowledgement Figure A 1 gives an overview of the interaction of the basic operations REQUEST INDICATION Request message i Client k s Server Response message execution CONFIRMATION RESPONSE 5067A204 Figure A 1 PCP basic service operations confirmed services A 2 PHOENIX CONTACT 7538 _en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS General Connection Establishment Phase Data Transfer Phase Connection Abort Phase Command Code Message Code Parameter Counter Invoke ID Communication Reference CR A 1 3 Communication Phases The Inline bus coupler supports connection oriented one to one communication relationships The communication oriented communication is divided into three phases Connection establishment Data transfer C
38. that supports the Peripherals Communications Protocol PCP and is not a serial module An example of this type of module would be the Inline AS i Gateway ASI MA IB IL Typically the ASI MA IB IL will not require the use of PCP data exchange However PCP data exchange will be required if there are more than 31 slaves on the AS i subnetwork The messages that are required to read and write data are encoded into the high speed data stream The protocol is handled using a series of message fragments that are initiated by aclient start request and then followed up with a server response These fragments were specifically designed to be used with any Inline PCP modules These process data messages are used to read or write to a specific slave device s memory location that is access by an Index and subindex designation Beside the exchange of normal I O data PCP process data communications can be used to parameterize an Inline module or retrieve informative data Information pertaining to the supported indexes subindexes and Invoke ID can be found in the specific module s data sheet and or manual For each PCP Inline module by default 8 bytes 1 fragment are added to the Ethernet IP produced size and eight bytes are added to the consumed size These eight bytes can only be used to send PCP data messages and are in addition to any other I O data that might also be added into the scan This type of information can be found in the specific mo
39. the right to alter correct and or improve the technical documentation and the products described in the technical documentation at its own discretion and without giving prior notice insofar as this is reasonable for the user The same applies to any technical changes that serve the purpose of technical progress The receipt of technical documentation in particular data sheets installation instructions manuals etc does not constitute any further duty on the part of Phoenix Contact to furnish information on alterations to products and or technical documentation Any other agreement shall only apply if expressly confirmed in writing by Phoenix Contact Please note that the supplied documentation is product specific documentation only and that you are responsible for checking the suitability and intended use of the products in your specific application in particular with regard to observing the applicable standards and regulations Although Phoenix Contact makes every effort to ensure that the information content is accurate up to date and state of the art technical inaccuracies and or printing errors in the information cannot be ruled out Phoenix Contact does not offer any guarantees as to the reliability accuracy or completeness of the information All information made available in the technical data is supplied without any accompanying guarantee whether expressly mentioned implied or tacitly assumed This information does not include any gua
40. therefore depends on the specific station structure Communications Power U 7 5 V and Analog Supply Uana The bus coupler supply U 24 V generates the communications power U 7 5 V and the analog supply U ana 24 V for the Inline station Communications Power Potential Jumper Nominal value Maximum output current Safety equipment Analog Supply Potential Jumper Nominal value Maximum output current Safety equipment Current Consumption Power Consumption Current consumption from U 24 V Current consumption of module electronics Current consumption of local bus 800 mA load at 7 5 V Current consumption from Uana 24 V Total current consumption from UL Current consumption from Us 24 V Current consumption from Uy 24 V Power dissipation of entire device Bus Interface of the Lower Level System Bus Interface Electrical isolation Number of Inline terminals that can be connected Limitation by software Limitation by power supply unit 7 5VDC 2 A DC observe derating Electronic short circuit protection 24V DC 0 5 A DC observe derating Electronic short circuit protection 0 08 A maximum 0 4 A maximum 0 5 A maximum 0 98 A maximum 3 mA 4 mA for each output set load typical 8 A maximum 3 mA 3 mA for each output set load typical 8 A maximum 3 W typical Inline local bus No 63 maximum including two devices on the bus coupler Maximum logic current consumption of the connected
41. 0 O bytes are being received at this time Table A 14 shows the master to slave acknowledgment of Transmit Request indication Table A 14 Master to slave indication for data transmission Tx Tx Tx Tx Tx Tx Tx oe Data 1 Data 2 Data3 Data4 Data5 Data6 Data7 05 hex 6Fhex 72 hex 6Chex 64 hex 0 r 13 d Control byte 0 O5hex Bit4 0 Transmit Request has been toggled indicating that there is more data to be transmitted Bits 2to0 5 Shows 5 bytes to transmit 7538 _en_01 Event 6 Event 7 and Event 8 7538 en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Communications Methods Table A 15 shows that the slave has received 5 additional bytes of data This indication is explained as follows Table A 15 Slave to master output data is Queued response Rx Rx Rx Rx Rx Rx Rx Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 Data 7 Status byte 0 OOhex Bit4 0 Transmit Acknowledge is being set to the same value as Transmit Request to indicate that the module is ready to received more data Bits2t00 5 No data is being received at this time Master to slave and slave to master idle mode No more data to send PHOENIX CONTACT A 15 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC Fragmented Error Handling Loss of Inline Backplane Communications Example This serial fragmentation error handling example shown in Figure A 4 will show how th
42. 5 CIP Class Reflects the number of the CIP class that the module is mapped to i e 8 DIP 9 DOP etc 6 First CIP Instance Reflects the first instance of the CIP object that this module is mapped to 7 Last CIP Instance Reflects the last instance of the CIP object that this module is mapped to B 24 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Inline Special Function Object Class Code 103 gec 67 hex B14 Inline Special Function Object Class Code 103gec 67hex The Inline Special Function SF Object allows the user to control and monitor the Inline modules attached to the IL EIP BK DI8 DO4 2TX PAC that do not map to any standard CIP Object B14 1 Inline Special Function Object Class Attributes ibe Aoeess name Imme Te E eo Max Object Instance UINT Number of Inline SFs 6 Get Max Class Identifier UINT 7 7 Get Max Instance Attribute UINT Mr B 14 2 Inline Special Function Object Instance 1 Number of Inline Special Function Modules Attributes Access Name re Vaea en nen ame fa ea oaase m jo Fam fea o B 14 3 Inline Special Function Object Common Services Service Name Get_Attribute_Single Set_Attribute_Single 7538_en_01 PHOENIX CONTACT B 25 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC B 14 4 Values for Inline Special Function Object Class Attributes 3 IN Data Data returned from
43. 7 Event 1 gt 0 1 1 0 1 4 EHEIEIEZEIEIEIEN 1 1 1 1 1 4 lt q Event 2 COOCOO Event3 gt 0 1 1 0 1 4 1 1 1 1 1 4 lt q Event 4 ENEIEIEIEIEIEIEN Event5 0 1 1 0 1 4 lt Event 6 1 1 1 1 1 4 ESEIEIEIEIEIEIEN Event7 gt O 1 1 0 1 4 Oe On Oh Oe i in 1 1 1 1 1 4 lt q Events Event9 0 1 1 0 1 4 ESEIEIEIEIEIEIEN Event 10 044 044 EHEIEIEIEIEIEIEN Usa sea dies Uea Uea Uea Uei gaya 1 1 1 1 1 4 7426A155 Figure A 6 I O events for a write sequence using PCP fragmentation In the following paragraphs the events in Figure A 6 will be explained in detail Table A 32 to Table A 42 demonstrate the order of events when issuing a fragmented write service to a PCP device Each Event should be referenced to the I O data table shown in Figure A 6 7538 _en_01 PHOENIX CONTACT A 31 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC Event 1 Table A 32 shows the transmission from a master to slave when the PCP fragmentation is in Idle mode Note that in byte O the service 00 is being sent Table A 32 Master to slave idle request sending a 00 no action service Service O0hex Event 2 Table A 33 shows the slaves response to the idle state by replying with a OOhex no action acknowledge Table A 33 Slave to master idle response 00 no action acknowledgement Service OOhex Event 3 Table A 34 shows
44. 7538 en_01 here IB IL 24 FLM PAC 6 Fieldline Modular local bus PHOENIX CONTACT 2 1 IL EIP BK DI8 DO4 2TX PAC Bus Coupler Module Tasks of the Bus Coupler Module Maximum Number of Devices 2 2 PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS The first step in setting up a modular I O station is to connect the bus coupler module to the Ethernet IP cable I O modules may be installed branching off from these bus coupler modules to create a local bus The bus coupler module also supplies communications power to the connected I O modules A breakdown of the supply voltage on the bus coupler module stops the communications to the modules connected to the bus coupler and causes an error message for the node Coupling of Ethernet IP and the Inline I O modules Supplying the I O modules with communications power Electrical isolation of the local I O Providing diagnostic information from the connected I O to Ethernet IP The maximum number of devices that you can connect to a bus coupler is determined by the following parameters Upto 61 devices can be connected to a bus coupler This number includes all the devices after the bus coupler with input or output data i e the Inline modules and the modules for Fieldline Modular local bus The bus coupler can supply a maximum of 0 8 A for communications power and 0 5 A for analog supply power The current carryin
45. A 20 Service byte definition of the PCP abort error fragment Fragmen Module Reserved tation Comm Error Bit 7 to 4 Reserved Bit 3 Fragmentation Error Anerror has occurred with either the type or sequence of the fragments i e middle received after last middle fragment 2 received before 1 etc Bit 2 PCP Channel Busy A PCP transaction is already in progress such as from an explicit request Bit 1 PCP Error A PCP Service Specific error has occurred See the Error Class and Error Code bytes Bit O Module Comm Error When set communication with the module is no longer possible Byte 2 7 Error Class and Error Code Bytes 2 and 3 will display the error class and error code If there is any additional error information it will be displayed in bytes 4 to 7 To interpret the error information a PCP reference manual must be consulted 7538 _en_01 7538 en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Communications Methods A 2 3 2 PCP Fragmentation Examples The following examples will show how to read write and handle errors using PCP process data fragmentation The examples to follow are Fragmented Read Fragmented Write Error Handling Communications Backplane Break Error Handling Host Communications Loss PHOENIX CONTACT A 25 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC Fragmented Read Example Figure A 5 sh
46. Attribute_Single 7538_en_01 PHOENIXCONTACT B 11 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC B 9 4 Values for AIP Object Class Attributes 3 Value This attribute contains the desired value to be sent to the AOP 4 Status If the analog input status bit is set it indicates that a hardware fault has occurred during the previous analog read The value is left at the last valid value read A fault during the analog input function results in a Major Unrecoverable Fault condition see Section Identity Object Class Code 01dec 01hex on page B 3 7 Range The AIP range value is used to configure the measuring range of the Inline analog input module The AIP Range values are stored in non volatile memory 10 to 10 V Oto 10 V O to 20 mA 20 mA to 20 mA non standard CIP value 8 Type The Type attribute determines the data type to be used by the attribute Value The type is fixed as UINT 6 100 Override Range When set the control data is sent to the AIP as the control word instead of the value corresponding to the range 101 AIP Control Data If the Override Range attribute is set the value in this attribute is sent to AIP as the control word instead of the value corresponding to the range Note this is a NV attribute and constant changing will use NV life cycles Use Control Data in I O for dynamic changing of the control word 102 Control Data in I O When set the Contro
47. Code 100gac 64he Attribute 32 If the user does not want to clear the latches through the produced data I O then an explicit message to the Inline Interface Object Class Code 101 gece 65pex Attribute 20 can be sent Setting attribute 20 to a 2 will reset all latches enabling the next input latch It will also automatically reset the attribute 20 value to O PHOENIX CONTACT 3 31 IL EIP BK DI8 DO4 2TX PAC il 3 32 PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Latch values are retained during operation and will not be cleared until the latches are reset Once a reset is received the latches will re initialize to the value that allows the input level to be captured This initialization depends on the value determined by attribute 101 Latch Level Digital Output Point DOP Object Class 09 The DOP object models digital outputs in the Ethernet IP bus coupler There is a separate instance for each digital output point available on the device However the value of the status is the same for all the given points on a particular I O module Other attributes include Value Status Fault State Fault Value Idle State and Idle Value Analog Input Point AIP Object Class 0A The AIP object models analog inputs in the Ethernet IP bus coupler There is a separate instance for each analog input point available on the device Attributes include Value Status and Range Analog O
48. E ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Communications Methods A2 Communications Methods Communications to an Inline serial module and to a generic PCP Inline module can be accomplished in two main ways each The type of module being used either serial or generic PCP determines what types of communication methods are available to the user The first method available to the user is the sending or receiving of data using process cyclic data channel fragmentation and the second is by sending explicit messages Choosing between the two methods is a matter of the capabilities of the Ethernet IPTM scanner and or personal preference When using the Inline RS 232 or RS 485 422 modules simplified methods 1 or 2 can be used If using any including serial that supports PCP methods 3 or 4 must be used il Serial modules are not supported under mapping revision 0 Method 1 Transfer of Serial Data Using Serial Fragmentation Method 2 Transfer of Serial Data Using Explicit Messages Method 3 Transfer of Generic PCP Data Using PCP Fragmentation Method 4 Transfer of Generic PCP Data Using Explicit Messages Supported serial modules are IBILRS 485 422 Inline RS 485 422 module IBILRS 232 Inline RS 232 module An example of a Generic PCP Inline module is the ASI MA IB IL Inline AS I Gateway il 1 PCP is not required when using the ASI MA IB IL if the AS i branch has less than 32 slaves 2 Ifthe PCP
49. EIP BK DI8 DO4 2TX PAC A value of 1 indicates a power supply out of range A value of 0 indicates power supply is ok 07 one ets ena ets Bia Bir mo Clear DIP Acknowl Latches edge PF Contains the most recent logged error information Contains the last logged error information Attributes 22 29 contain the intermediate error log history 7538 _en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Inline Module Object Class Code 102gac 66nex B 13 Inline Module Object Class Code 102 ac 66hex The Inline Module Object allows the user to monitor the Inline modules attached to the IL EIP BK DI8 DO4 2TX PAC B13 1 Inline Module Object Class Attributes Attribute Access Name Type Vatu 1 Get Revision UINT Bo a Max Object Instance UINT Number of Inline Modules B 13 2 Inline Module Object Instance 1 Number of Inline Modules Attributes fatwibute Access Name iye aee e en Frstorinsince m o B 13 3 Inline Module Object Common Services Service Code Class fale Service Name Yes Get Attribute Single _ Attribute GetAttibute Single 7538_en_01 PHOENIX CONTACT B 23 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC B13 4 Values for Inline Module Object Class Attributes 3 Inline Module ID Displays the Inline ID for the module as the unit was configured Config 4 Inline Module ID Displays the current Inline ID for the module Current
50. LECTRONIC COMPONENTS Diagnostics 4 1 Diagnostic and Status Indicators All modules are provided with diagnostic and status indicators for rapid local error detection The diagnostic indicators red or green show the state of the Inline modules When a module is operating normally all its diagnostic LEDs are green After an error is detected the indicators immediately display the current status The status indicators yellow display the status of the relevant inputs outputs or of the connected device Each different type of module has different diagnostic and status indicators Refer to the IL SYS INST UM E user manual and to the module specific data sheet to see which diagnostic and status LED indicators apply to that module Figure 4 1 and Table 4 1 provide the different LED states that can be read from the bus coupler 2 ETH 75370002 Figure 4 1 Diagnostic and status indicators on the bus coupler PHOENIX CONTACT 4 1 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC Table 4 1 Local status and diagnostic indicators on the bus coupler LED Color Meaning State Description of the LED States O O EH LNK1 Green Link at ON Link connection at port 1 present iN Seen port 1 OF F Link connection at port 1 not present LNK2 Green Link at Link connection at port 2 present e Seen port 2 o Link connection at port 2 not present ACT1 Yellow Activity on ON Data trans
51. M In WBM click on Device Configuration and then Software Update Enter the IP address of the TFTP server in the TFTP Server IP Address field Then enter the file name of the firmware and the path name if necessary in Downloadable File Name In the Software Update on Next Reboot field click Enable Enter your password To wait until later to apply the update with a restart click Apply To start the update immediately click Apply and Reboot Check the execution of the update by checking the firmware version under Device Information General In the event of an error during the download a restart repeats the download To abort the update set Disable in the Software Update on Next Reboot field 7538_en_01 PHOENIX CONTACT 3 9 IL EIP BK DI8 DO4 2TX PAC 3 10 me me PHOENIX CONTACT Software Update TFTP Server IP Address TFTP 172 16 40 201 Downloadable File Name c2897758 fw Software Update on Next Reboot Enable Disable A Firmware Update was not initiated before the last restart If the software update status is set ta enable the IL EIP BK DIE DO will ty to load new software within the next reboot Press the apply button to change the software update status The settings will take effect after the next reboot of the IL EIP BK DIS DOE TFTP Update Status Enter password Apply Apply and Reboot Software Update via FTP on Next Reboot Enabl
52. OENIX CONTACT 7538 _en_01 7538 en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Communications Methods A 2 1 2 Format of Fragmented Serial Input Data Produced Response Byte 0 Status Byte See Table A 2 Byte 1 to 7 Data block if necessary Table A 2 Status Byte BEE Receive Transmit Reset Number of Data Bytes Request Ack Ack Received Per Fragment Bit 7 Error When this value is set an error has occurred such as parity or overrun The user should query the status parameter for more information Bit 6 Reserved Bit 5 Receive Request This value is toggled to indicate new data has been received The user must acknowledge the reception of data by echoing back this value in the Receive Ack bit Bit 4 Transmit Ack When this value is equal to the Transmit Request it indicates that the output data has been queued into the output buffer Once they are equal the user can then send more data Bit 3 Reset Ack If a Reset has been requested this value will be set to 1 to indicate that the serial port has been reset and the buffers have been flushed This causes the TxAck and RxReq to be reset to 0 allowing re sync of protocol Bits 2 to 0 Number of Bytes Received Indicates the number of valid data bytes that are in the data section of the input data A 2 1 3 Serial Fragmentation Examples The following examples will show how to read write and handle errors using serial process data fragmentation
53. OR OF ELECTRONIC COMPONENTS Ethernet IP Object Classes Message Types and Services B Ethernet IP Object Classes Message Types and Services B 1 General The IL EIP BK DI8 DO4 2TX PAC is an Ethernet IP capable adapter that functions as a generic device type The BK maps the I O connected via the backplane to standard or user defined CIP objects The bus coupler supports CIP using ODVA standard Digital Input Points DIP Digital Output Points DOP Analog Input Points AIP and Analog Output Points AOP Additional objects include user defined configuration Inline Interface Inline Module Inline Special Function PCP Special Function and Serial Communication Objects B2 CIP Class Services The IL EIP BK DI8 DO4 2TX PAC supports the following class services and instance services Service Code Service Name KY o eee 7538_en_01 PHOENIX CONTACT B 1 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC B3 CIP Object Classes The IL EIP BK DI8 DO4 2TX PAC supports the following CIP object classes Class Code Object Type On 08 o8 Digital Input Point DIP Object B 7 09 o Digital Output Point DOP Object Analog Input Point AIP Object B 11 ou OB Analog Output Point AOP Object B 13 B 2 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Identity Object Class Code 01 gec 01 hex BA Identity Object Class Code 01 ga 01 nex The Identity Ob
54. OR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC Event 9 Table A 29 shows the master to slave acknowledgment of the last fragment being received In this acknowledge the service byte reflection is the indication that the last fragment response was received Table A 29 Master to slave last fragment acknowledgement Service COhex Events 10 and 11 Knowing that the last fragment was received the master issues an idle service to the slave as shown in Table A 30 and the slave respond with its reply as shown in Table A 31 Table A 30 Master to slave idle service Service OOhex Table A 31 Slave to master idle service response Service OOhex A 30 PHOENIX CONTACT 7538_en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Communications Methods Fragmented Write Example Figure A 6 shows an example I O data table that contains only eight bytes of input data and eight bytes of output data This I O is shown in an event by event sequence that demonstrates how these eight bytes of I O are updated when reading data using PCP fragmentation The sequence works on this following basic principle Event x Client issues server 8 bytes of output data Event x 1 Server responds by updating 8 bytes of input data Input Data Table Output Data Table Event Sequence for Bytes 0 to 7 Event Sequence for Bytes 0 to 7 Byte _ gt Byte Byte _ _ gt Byte 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6
55. P Modules Produced and Consumed Sizes Section 3 Startup Operation provides additional information in regard to how data is mapped into the scanner and other considerations A 3 1 Determining Produced and Consumed Size The bus coupler can auto configure itself to the Inline I O connected to it Refer to Section 3 Startup Operation Once this is done the total number of produced and consumed data for the entire Inline station will include fragmentation data can be read from the EDS file A 40 PHOENIX CONTACT By default any module that uses the PCP protocol includes the serial modules will have 8 bytes of produced data and 8 bytes of consumed data added to the network scan These bytes are used to transfer data back and forth between an Ethernet IP scanner and for example an Inline serial module This data transfer using 8 bytes is required when using process cyclic data to Tx Rx serial data fragmentation In addition to the bytes used for transferring serial or other PCP data there may be additional data produced or consumed by the I O module This additional data must be added to the 8 bytes described in the previous paragraph The number of additional process data bytes can be found in the specific Inline module s data sheet or manual These process data bytes will be added to the scan ahead of the 8 bytes of fragmentation data in the scanner s I O memory Table A 44 gives and example of calculating the total number of
56. RIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC Event 8 Table A 39 shows the slave to master acknowledgment of the last fragment being received and processed In this acknowledge the service byte reflection is the indication that the last fragment data was received It is important to realize that event 8 is really a start fragment from the slave signaling the response and status information for the write request Table A 39 Slave to master last fragment acknowledgement Service 82 hex Event 9 Table A 40 shows the master to slave acknowledgment of the last fragment being received In this acknowledge the service byte reflection is the indication that the last fragment response was received Table A 40 Master to slave acknowledgement Service 82 hex Events 10 and 11 Knowing that the last fragment was received the master can issue an idle service to the slave as shown in Table A 41 and the slave respond with its reply as shown inTable A 42 Table A 41 Master to slave idle Service OOhex Table A 42 Slave to master response to idle Service OOhex A 34 PHOENIX CONTACT 7538_en_01 online components com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Communications Methods Fragmented Error Handling Loss of Inline Backplane Communications This PCP fragmentation error handling example shown in Figure A 7 will show how the fragmentation will react during a break in the communications path on t
57. S file Parameter 56 most recent through Parameter 65 oldest or by using the Inline Interface Object Class 101 Instance 1 Attribute 21 most recent to attribute 30 oldest As error values are added existing values will be shifted to older parameters The new value is then placed in the most recent parameter and the value in the Last Saved parameter is discarded The error history entry will contain the faulted module number in the high byte and the Inline status code in the low byte A 0 for an error history entry represents a point where an error was removed An error history value may be recorded at a point where an error is detected but is not yet localized When the error is localized a new error history value will be added 4 8 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Technical Data and Ordering Data 5 Technical Data and Ordering Data 5 1 General Data Housing dimensions width x height x depth Weight Ambient temperature operation Ambient temperature storage transport Permissible humidity storage transport Permissible air pressure operation storage transport Degree of protection Class of protection Preferred mounting position Connection to functional earth ground Ambient compatibility Resistance to solvents Connection data for Inline connectors Connection type Conductor cross section System Limits of the Bus Coupler Number of devices per station N
58. Serial Communications Object Fragment Data 0 Removes data 1 Adds data If the user has any other PCP module and wants to add remove the fragmentation data 8 bytes they must send an explicit message This must be sent to the PCP Special Function Object Class Code 105 ga 69hex using the proper instance and attribute 17 PCP Fragment Data in Ethernet IP I O To add or remove the Other PCP Data from the Ethernet IP I O set the following Class 105 Instance X Attribute 17 PCP Fragment Data 0 Removes data 1 Adds data PHOENIX CONTACT A 41 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC A4 I O Memory Mapping Serial and Special Function PCP Modules Section 3 Startup Operation provides additional information in regard to how data is mapped into the scanner and other considerations I O Mapping Rules Section 3 Startup Operation describes configuration methods mapping in greater detail The I O image in the bus coupler flash memory contains all produced data input data and consumed data output data derived from the I O modules connected to it I O image data is added to the poll through the use of parameter 9 Add All I O or by using auto configuration An I O image could contain the Inline Status word included by default in the produced data command byte not included in the consumed data by default module fault data reserved I O space digital
59. Supported Traps ColdStart is sent twice each time the device is restarted PasswordChange is sent after the password is changed successfully FWHealth is sent after any changes to the firmware operating status Configuration is sent after any changes to the hardware configuration SNMP is not supported in the first development step The integration of SNMP is planned for the second step 3 Autoconfiguration That means you can now change your local bus configuration and make it active via the website To use this function you have to stop your I O connection That means you cannot use the ADD ALL function when you have a running I O connection 3 8 Configuration Configuration services can be accomplished by using the defined CIP Objects Some configuration features are also made available to the user through the web server PHOENIX CONTACT 3 15 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC 3 9 The CIP I O Module Capacity The bus coupler is capable of processing the maximum number of instances points for objects listed below Digital Input Points DIP 510 instances Digital Output Points DOP 510 instances Analog Inputs Points AIP 128 instances Analog Output Points AOP 128 instances Special Function Object 61 instances PCP Special Function Object 8 instances Serial Communication Object 8 instances Total instances shared between the PCP Specia
60. TR Control Only Type fo 1 OOOO Codethex Meaning o No votaton O Code then Meaning OOO 22 Rotation Switch 23 XON Pattern XX Any character not the same as XOFF pattern 24 XOFF Pattern Codethex Meaning SSS Any character not the same as XON pattern 31 Status Control IN If set the serial status word is added to the produced data of all the I O connections and the CIP I O serial control word is ADDed to the I O consumed data This attribute affects the produced and the consumed sizes of the I O connections and is therefore only settable when there are no I O connections in the established state 32 Fragment Data IN If set the Receive Data Fragment is ADDed to the produced data of all the CIP I O CIP I O connections and the Transmit Data Fragment is added to the I O consumed data This attribute affects the produced and the consumed sizes of the I O connections and is therefore only settable when there are no I O connections in the established state 33 Serial Object If set the Serial Object will handle the buffering of the serial data Set this attribute to O to Enable enable direct access of the serial modules using the PCP class instead of the SCO class B 38 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Port Object Class Definition Class Code 244 ac F4nex B18 Port Object Class Definition Class Code 244 gac FAhex B 18 1 Port Object Class A
61. Table A 10 shows the transmission from a master to slave when the serial fragmentation is in Idle mode Table A 10 Master to slave idle transmission Tx Tx Tx Tx Tx Tx Tx Control Data 1 Data2 Data3 Data4 Data5 Data6 Data7 ow x a mK MK KK MK OK 7538_en_01 PHOENIX CONTACT A 13 IL EIP BK DI8 DO4 2TX PAC Event 2 Event 3 Event 4 Event 5 A 14 PHOENIX CONTACT THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Table A 11 shows the slave s response to the idle state by replying with a OOnax Table A 11 Slave to master idle response Rx Rx Rx Rx Rx Rx Rx Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 Data 7 Table A 12 shows the master to slave transmission of 7 bytes of data Table A 12 Master to slave data transmission Control Tx Tx Tx Tx Tx Tx Tx Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 Data 7 1 T hex 48hex 65 hex 6Chex 6Chex 6Fhex H e l ssl 0 Control byte 0 17nex Bit4 1 Transmit request is toggled indicating that new data is being transmitted Bits2t00 7 Shows the number of bytes to transmit Table A 13 shows that the BK has received the data Table A 13 Slave to master acknowledgement of data transmission Rx Rx Rx Rx Rx Rx Rx Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 Data 7 Status byte 0 10hex Bit 4 1 Transmit acknowledge is being set to the same value as Transmit request to indicate that the module is ready to receive more data Bits 2to0
62. _01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Startup Operation 3 11 Understanding I O Memory Mapping 3 11 1 Bus Coupler Mapping The I O image in the bus coupler flash memory contains all produced data input data and consumed data output data derived from the I O modules connected to it I O image data is added to the poll through the use of parameter 9 Add All I O Configuration through EDS and configuration software was explained in the previous section An I O image could contain the following produced and consumed elements in the priority order listed below Consumed Data Table 3 2 Consumed data Location Default Control Object Attribute Setting Instance Attribute Run Idle a Enabled 64 Inline Control Byte Disabled 64 Actual DOPs Enabled 64 Reserved DOPs 3 Disabled 64 O Enabled if number of Zu DOP bytes uneven 7538_en_01 Z Z oA 7 sabes sabes 5 isabies eA oA PHOENIX CONTACT 3 25 IL EIP BK DI8 DO4 2TX PAC Produced Data Table 3 3 Produced data Location Instance Run ldie Inline Status Byte Oo OD or O1 Inline First Faulted Module DIP Faults DOP Faults AIP Faults AOP Faults Special Function Faults Attribute THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Default Setting Instance Disabled Disabled Disabled Control Object Attribute Actual DIPs Reserved DIPs Enabled 3 Disabled Enabled if uneven OB BCE
63. a B 14 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configuration Object Class Code 100gac 64hex B11 Configuration Object Class Code 100 gac 6Ahex The Configuration Object allows the user to configure what data they want in each I O connection In addition the configuration object gives access to several operational parameters such as status info B11 1 Configuration Object Class Attributes Atvibute Access Name Types B11 2 Configuration Object Instance 1 Attributes Number of Digital Inputs USINT 7 es eo Add All I O BOOL Get Set Special Function Modules BOOL 19 Get Set Number of Special Function UINT Faults G Produced Size UINT w fea et Bytes Reserved for DOPs UINT Fault Mode USINT 24 7538_en_01 PHOENIX CONTACT B 15 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC Inline Control Byte in Poll BOOL Number of PCP Modules UINT 38 3 40 4 Connections I O Size Word Align USINT 48 B11 3 Configuration Object Common Services Service Name Yes Get_Attribute_Single Changing the configuration object will cause the CONSUMED and PRODUCED size of the I O connection to be changed These values are retained in non volatile memory and may only be set when the I O connection is not in the RUNNING state Values retained in non volatile storage B 16 PHOENIX CONTACT 7538_en_01 3 4
64. allow for future system expansion s without having to change the master scanner s I O tables The actual reservation can be done in the following two ways 1 By using EDS file Parameter 3 Reserve Digital Inputs Parameter 4 Reserve Digital Outputs Parameter 5 Reserve Analog Inputs Parameter 6 Reserve Analog Outputs The entry downloaded to the bus coupler will be equal to the current physical number of I O points on the local bus plus the number of I O points to be reserved 2 By sending an explicit message to the Configuration Object Class Code 100gac 64hex The user can reserve a digital bit by writing to parameters 22 Reserve Digital Inputs 23 Reserve Digital Outputs 35 Reserve Analog Inputs and 36 Reserve Analog Outputs The entry downloaded to the bus coupler will be equal to the current physical number of I O points on the local bus plus the number of I O points to be reserved 7538_en_01 PHOENIX CONTACT 3 29 IL EIP BK DI8 DO4 2TX PAC 3 30 il PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS 3 12 NO Data Transfer A detailed explanation of the following objects and their attributes can be found in Appendix B Ethernet IP Object Classes Message Types and Services I O data transfer can be accomplished by establishing an I O connection implicit or by establishing a message connection explicit For operational considerations see Section Maximum Connec
65. also counted Invoke ID does not apply to this PCP version 00 The value is therefore always 00 CR indicates the communication reference that is set for the communication relationship between host controller board and the remote device The standard setting for the first PCP module is CR 2 for the second PCP module CR 3 etc PHOENIX CONTACT A 3 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC Basic Service Request Index LSB Service Request w Invoke ID Basic Service Response Success Basic Service Response Success w Invoke ID A 4 PHOENIX CONTACT 7538 _en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS General Basic Service Error Response Additional Error LSB Additional Error MSB Service w Invoke ID Error Response Additional Error MSB Basic Service Abort Response Service w Invoke ID Abort Response Abort Code Abort Reason 0 Abort Reason 1 7538 _en_01 PHOENIX CONTACT A 5 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC Basic Service Reject Response PDU Type Reject Code Additional Error LSB Additional Error MSB Service w Invoke ID Reject Response Additional Error MSB Supported Services PN BEE VE EEE 1 ete re eS 9 PCP Read w invoke ID aA O PCP Write w lnvoke ID 01 02 03 Read PDU Size 10 A 6 PHOENIX CONTACT 7538_en_01 onlinecomponents com TH
66. analog special function no PCP special function PCP modules or serial modules process data first then fragmentation data Mapping priority is determined by the type of module without regard to its location to the BK or other modules of different types However it does take into account the order of modules of the same type that exist on the station A 42 PHOENIX CONTACT 7538_en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configuration Brief for the RS 232 and RS 485 RS 422 Modules A5 Configuration Brief for the RS 232 and RS 485 RS 422 Modules General Configuration Appendix B Ethernet IP Object Classes Message Types and Services provides details of the Serial Communications Object Class Code 106gec Anex for configuration attributes This section describes how to change default settings for the Inline RS 232 and RS 485 RS 422 modules Information provided in this section must be used in conjunction with the specific module s data sheet In order to change any setting refer to the module s specific data sheet to determine the appropriate attribute settings for the Serial Communications Object Class Code 1064gec 6Ahex The default settings can only be changed by sending an explicit message An explicit message can either be sent from a control program or an Ethernet IP configuration software package Once the desired parameters have been updated the settings are stored in flash
67. ass Byte 4 Error code Byte 5 Additional error code 1 LSB if necessary Byte 6 Additional error code 1 MSB if necessary Byte 7 Additional error code 2 LSB if necessary Byte 8 Additional error code 2 MSB if necessary The data length is determined by the PCP Index and PCP Subindex of the object to be read written the max data length is variable and can be up to the PDU size for the module typically 64 bytes See 3 PDU Size on page B 31 This attribute allows the user to set the PCP module number that the reads and writes Attributes 11 and 14 will access This attribute sets the Index of the PCP Object Dictionary that will be written when the user writes to the PCP Write Data Attribute Attribute 11 This attribute sets the SubIndex of the PCP Object Dictionary that will be written when the user writes to the PCP Write Data Attribute Attribute 11 This attribute allows the user to write data to the PCP Object Dictionary that is referenced by the PCP Module Attribute PCP Write Index and PCP Write Sublindex This attribute sets the Index of the PCP Object Dictionary that will be read when the user reads from the PCP Read Data Attribute Attribute 14 This attribute sets the SubIndex of the PCP Object Dictionary that will be read when the user reads from the PCP Read Data Attribute Attribute 14 This attribute allows the user to read data from the PCP Object Dictionary that is referenced by the PCP Module Attribute PCP Rea
68. bytes produced and consumed by an individual Inline RS 232 module Table A 44 Calculation of a serial module s produced and consumed bytes Fresco consumed Bytes required by the RS 232 module for status and control found in data sheet Bytes required to Tx Rx serial data fragmentation Total used by each RS 232 module 10 bytes 10 bytes 7538 _en_01 7538 en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Serial and Generic PCP Modules Produced and Consumed Sizes A 3 2 Removing or Adding Fragmentation Data Fragmentation data must not be removed if using methods 1 or 3 described in Appendix A 2 Communications Methods If serial or other PCP data is going to be transmitted using explicit messages then the 8 bytes used for the process cyclic data messaging fragmentation that is added to the scan by default will not be needed The unused 8 bytes of produced and 8 bytes of consumed should be removed to ensure the best possible network performance If the user has a serial module and wants to remove or add the fragmentation data 8 bytes they must send the following explicit messages This must be sent to the Serial Communications Object Class Code 106 ge 6Anex using the proper instance and attribute 32 Fragment Data in Ethernet IP I O To add or remove the Serial Data 8 bytes of fragment data from the Ethernet IP I O set the following Class 106 Instance X Attribute 32
69. changes state 11 Enable DOP Faults When set to a 1 generates a bit pattern in the COS Mask Array that cause a COS message to be generated when any DOP Fault changes state 12 Enable AIP Faults When set to a 1 generates a bit pattern in the COS Mask Array that cause a COS message to be generated when any AIP Fault changes state 13 Enable AOP Faults When set to a 1 generates a bit pattern in the COS Mask Array that cause a COS message B 28 PHOENIX CONTACT to be generated when any AOP Fault changes state 7538 _en_01 14 15 16 17 18 Enable SF Fault Enable DIPs Enable AIPs Enable Special Function IN Data AIP Mask 7538 en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS COS Mask Object Class Code 104 yac 68hex When set to a 1 generates a bit pattern in the COS Mask Array that cause a COS message to be generated when any Special Function Module Fault changes state When settoa 1 generates a bit pattern in the COS Mask Array that cause a COS message to be generated when any DIP value changes state When set to a 1 generates a bit pattern in the COS Mask Array that cause a COS message to be generated when any AIP value changes state When set to a 1 generates a bit pattern in the COS Mask Array that cause a COS message to be generated when any bit in the Special Function IN Data changes state This value is used to generate a bit pattern use
70. crossover Two 8 pos RJ45 female connector CAT 5 twisted pair cable with a conductor cross section of 0 14 mm to 0 22 mm 100 Q 10 Mbps 10Base T 100 Mbps 100Base TX half duplex full duplex auto detection 100 m Through data routing 30 m maximum routing cables through outdoor areas is not admissible Through potential routing The supplies Uyy Us and the bus coupler supply Ugg do not have the same ground potential because they are supplied by two separate power supply units PHOENIX CONTACT 5 1 IL EIP BK DI8 DO4 2TX PAC Supply Voltage for U Us Uy Continued Behavior in the event of voltage fluctuations Nominal value Permissible range according to EN 61131 2 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Voltages main and segment supply that are transferred from the bus coupler to the potential jumpers follow the supply voltages without delay 24V DC 19 2 V to 30 V ripple included NOTE Module is damaged in the event of overload This 24 V area must be externally protected The power supply unit must be able to supply 4 times the nominal current of the external fuse to ensure that it trips in the event of an error Observe the logic current consumption of each device when configuring an Inline station This information is given in every module specific data sheet The current consumption can differ depending on the individual module The permissible number of devices that can be connected
71. cs Pkt 4 10 Pcs Pkt This software can be downloaded at www download phoenixcontact com Order No Pcs Pkt 9015358 1 2698737 1 PHOENIX CONTACT 5 5 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC 5 6 PHOENIX CONTACT 7538 _en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Serial and Other PCP Inline Modules A Serial and Other PCP Inline Modules 7538_en_01 A1 General A 1 1 Exchanging Device Parameters Communication Relationships Before data can be exchanged between two PCP devices a logical connection must exist between the two devices Such logical connections are called communication relationships Communication relationships are established between application processes Communication Relationship List CRL The host controller board creates a list for every PCP device Within this list all permitted communication relationships are specified independent of their time of use The connection type and the context requirements the connection parameters by which the communication relationship can be established are stored in this communication relationship list CRL The CRL can be manually changed as required The logical connections configured in the communications relationship list guarantee a smooth data exchange between two communication devices The connection parameters context conditions of both communication partn
72. ct You can use this object in applications as simple as an actuator or as complex as a digital I O control module There is a separate instance for each digital output available on the device B 8 1 DOP Object Class Attributes atwibute Access Name tye Vale UINT Max Object Instance UINT Number of DOPs Get Set Max Instance Attribute UINT Bo B 8 2 DOP Object Instance 1 Number of DOPs Attributes ivbute Access vane pe vate ee Get Output Status 00 Output Status 00 BOOL sis Status of Output a 1 3 Fault State ee 0 Fault value 1 No change 6 GevSet Fault Value Value BOOL sd O OFF 1 ON E Idle en S C Idle value i No change 8 Get Set Idle Value BOOL 0 OFF 1 ON 8 B 8 3 DOP Object Common Services Service Code Class ka Service Name 7538_en_01 PHOENIX CONTACT B 9 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC B 8 4 Values for DOP Object Class Attributes 3 Output State This attribute contains the desired state of the output 4 Output Status The output status bit indicates a fault condition 5 Fault State The Fault State determines what action is taken if a software fault condition is detected due to a connection timeout Action Taken 0 default Set the output to the stated determined by the Fault Value Leave the output in the current state 6 Fault Value The Fault Value determines the state of the DOP output if the Fault Sta
73. cupy instances 9 10 11 and 12 3 22 PHOENIX CONTACT 7538_en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Startup Operation Bus Coupler 2UTH Al2 AI2 2UTH Al2 Al2 BR NIT N PHCENIX CONTACT IL EIP BK DI8 DO4 2TX PAC Order No 2897758 HWIFW Xx xxx MAC Addr xx xx xx xx EtherNet IP EtherNet IP RESET Kk act gh uwe Oacr AAZ T SAZA SATSAA TSA T SA 75380004 Figure 3 10 I O station with analog input terminals and thermocouple terminals Default settings are modified by sending an explicit message to a specific instance This message can be sent using a Class Instance Editor window in a configuration software Using attribute 100 along with the correct instance in the AIP object is one way to determine how a thermocouple RTD or analog input module is configured If Attribute 100 O default in the AIP the user has access to all standard AIP attributes If Attribute 100 1 the user has access to Attribute 101 Input Configuration word By assigning a value to the Attribute 101 the user will be able to configure the thermocouple or RTD module s The correct configuration value for attribute 101 can be determined by using the module specific data sheets for the thermocouple or RTD modules It is also possible to use th
74. d 1 gt 0 lt PD_OUT gt lt PO_OUT word 2 gt 0 lt PD_OUT gt lt IL_ MODULE gt lt IL_MODULE number 4 gt lt MODULE T PE gt DI lt MODULE_TYPE gt lt PO CHANNELS gt 32 lt PD_CHANNELS gt lt PD_ WoORDS gt 2 lt PD_WORDS gt lt PO_IN word 1 gt O0 lt PD_IN gt lt PO_IN word 2 gt 0 lt PD_IN gt lt IL_MODULE gt lt IL_MODULE number 5 gt lt MODULE T YPE gt AIO lt MODULE_TYPE gt lt PE_CHANNELS gt 2 lt PO_CHANNELS gt lt PD WORDS gt 2 lt PD_WORDS gt lt PO_IN word 1 gt 1 lt PD_IN gt lt PO_IN word 2 gt 0 lt PD_IN gt lt PO_OUT word 1 gt 0 lt PD_OUT gt lt PO_OUT word 2 gt 0 lt PD_OUT gt lt TL_MODULE gt lt IL_MODULE number 6 gt lt MODLLE_TYPE gt AO lt MODLLE_TYPE gt lt PE_CHANNELS gt 1 lt POE_CHANNELS gt lt PD WoORDS gt 1 lt PD_WoORDS gt lt PE_OUT word 1 gt 0 lt PD_OUT gt lt IL_MODULE gt SIL Buss lt 1L_STATION gt Data of the first digital Input terminal eO O S a 4 Figure 3 8 Screen for XML data 3 14 PHOENIX CONTACT 7538_en_01 7538 en_01 il onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Startup Operation 3 6 Traps Trap Generation When important events occur e g a configuration change the bus coupler sends a trap to a trap manager defined by the user This enables the network administrator to react quickly to these events and to ensure network availability Traps are usually only transmitted once
75. d Index and PCP Read Subindex This attribute allows the user to send requests to the PCP module This attribute performs the same function as the PCP Request Attribute except that the request is broken up into packets of 8 bytes each This allows the user to include the attribute in the I O data without consuming an excess amount of bandwidth or to use CIP tools that do not support variable length explicit services 7538 _en_01 16 17 18 19 20 21 22 23 PCP Response Fragment PCP Fragment in CIP I O Process Data Size Process Data IN Process Data OUT Process Data IN CIP O PCP Write Invoke ID PCP Read Invoke ID 7538_en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS PCP Object Class Code 105gac 69hex This attribute allows the user to get responses from PCP modules This attribute performs the same function as the PCP Response Attribute except that the response is broken up into packets of 8 bytes each This allows the user to include the attribute in the I O data without consuming an excess amount of bandwidth or to use CIP tools that do not support variable length explicit services If set the PCP Response Fragment is added to the produced data of all the I O connections and the PCP Request Fragment is added to the consumed data This attribute affects the produced and the consumed sizes of the I O connections and is therefore only settabl
76. d O or 1 byte to consumed and or produced size 15 Number of DIP Selects the number of DIP Faults added to the I O produced data maulis Number of bytes number of channels 7 8 16 Number of DOP Selects the number of DOP Faults added to the I O produced data Faults Number of bytes number of channels 7 8 17 Number of AIP Selects the number of AIP Faults added to the I O produced data Faults Number of bytes number of channels 7 8 18 Number of AOP Selects the number of AOP Faults added to the I O produced data Faults Number of bytes number of channels 7 8 19 Number of Special Selects the number of Special Function Faults added to the I O produced data Function Faults Number of bytes number of channels 7 8 20 Produced Size This attribute allows the user to determine the produced size of the device 21 Consumed Size This attribute allows the user to determine the consumed size of the device 22 Bytes Reserved for This attribute allows the user to reserve bytes in the I O data for future expansion of actual DIPs Digital Input Points The I O data contains the number of bytes defined by the greater of either the actual number of DIPs or the number of bytes reserved by this attribute 23 Bytes Reserved for This attribute allows the user to reserve bytes in the I O data for future expansion of actual DOPs Digital Output Points The I O data contains the number of bytes defin
77. d above 3 16 PHOENIX CONTACT 7538_en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Startup Operation 3 10 Configuring the Inline Station If using a serial or another type of PCP module read this section then refer to Section Serial and Other PCP Inline Modules on page A 1 3 10 1 Bus Coupler Configuration of the bus coupler allows it to read and communicate specific information about the I O modules connected on its local bus backplane Specific local bus information includes How many I O modules are on the local bus Position of the I O modules on the local bus How many points or channels instances each module contains Bytes of produced and consumed data Types of I O modules Digital input Digital output Analog input Analog output Special function incremental encoder absolute encoder high speed counter other PCP and serial AS i master RS232 RS485 and others Any module that is not recognized will be placed into the special function category When configuring the Inline Ethernet IP bus coupler it is recommended that you remove the connection to the Ethernet IP scanner or make sure the scan list for the Ethernet IP scanner is empty 3 10 1 1 Configuration Methods When creating adding to or changing an Inline Ethernet IP station the I O configuration stored in the bus coupler must be updated to match the new confi
78. d to mask each AIP value when the Add All Attribute is set Example AIP Mask FFOO any time an AIP s upper 9 bits changes a COS message will be generated PHOENIX CONTACT B 29 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC B16 PCP Object Class Code 105geac 69hex The PCP Object allows the user to access I O modules that support the PCP protocol B16 1 PCP Object Class Attributes Aivibute Access name Type iV ao o Get 2 Get Max Object Instance UINT 0 8 Number of attached PCP modules 6 Get Max Class Identifier UINT 7 B16 2 PCP Object Instance 1 Number of PCP Modules Attributes panini ees in tt PCP Channel Size USINT Get Get Set PCP Request ARRAY of BYTE Get PCP Response ARRAY of BYTE PCP Module USINT PCP Write Index UINT PCP Write SubIndex USINT on as 6 B 30 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS PCP Object Class Code 105gac 69hex 21 PCP Write Invoke ID USINT 22 PCP Read Invoke ID USINT 23 B16 3 PCP Object Common Services Service Name Yes Get_Attribute_Single Set_Attribute_Single B16 4 Values for PCP Object Class Attributes 3 PDU Size Attribute contains the value of the PDU size used for the PCP channel of the module Typically 64 bytes This is the maximum number of bytes the PCP channel can transfer per request response 4 PCP Channel Size Attribute contains the va
79. data in one Set_Attribute_Single The format is aSHORT_STRING 9 Receive Data This attribute allows the user to read the serial data in pieces This can be useful for tools Fragment that do not support variable length or non standard length data sizes It is also used to map the data into the process data 10 Transmit Data This attribute allows the user to write the serial data to transmit in pieces This can be useful Fragment for tools that do not support variable length or non standard length data sizes It is also used to map the data into the process data 11 Protocol Code hex meaning o Transparent 02 Dual buffer 03 3964R o e e f 12 Baud Rate e fw w feo B 36 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Serial Communications Object Class Code 106gac 6Ahex 13 Data Width Code hex Even Even Without 1 Without 1 Even Without 2 Code hex Meaning a OBEN o Code hex Meaning oo NU Carriage Return CR Codethex Meaning Une Feed LF Code hex Meaning OOS o 7 7 O 16 Error Pattern 17 First Delimiter 18 Second Delimiter 19 3964R Priority 20 Output Type Code hes Meaning O RS 232 Default for RS 232 Module Type RS 485 Default for RS 485 Module Type 7538_en_01 PHOENIX CONTACT B 37 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC 21 D
80. discharge without labeling field 8 kV air discharge with labeling field Criterion A Criterion B Criterion B PHOENIX CONTACT 5 3 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC Conformance With EMC Directives IEC 61000 4 6 conducted noise immunity Criterion A IEC 61000 4 8 noise immunity against magnetic fields Criterion A EN 55011 noise emission Class A Approvals Information on current approvals can be found on the Internet at www download phoenixcontact com or www eshop phoenixcontact com 5 4 PHOENIX CONTACT 7538_en_01 5 2 Bus Coupler Description Inline bus coupler for Ethernet IP with eight digital inputs and four digital outputs including accessories end plate Inline connector and labeling fields Accessories Description Connector set for Inline bus coupler with connected I Os Gray RJ45 connector set for linear cable Green RJ45 connector set for crossed cable Keying profile Zack marker strip to label the terminals Zack marker strip to label the terminals Labeling field covering one connector Labeling field covering four connectors Insert strips for IB IL FIELD 2 perforated can be labeled using a laser printer marker pen or CMS system 72 sheets Insert strips for IB IL FIELD 8 perforated can be labeled using a laser printer marker pen or CMS system 15 sheets DIN EN 50022 DIN rail 2 meters End clamp can be snapped on wit
81. dule s data sheet An example of this type of information would be a status and control word These two bytes would also be added to the produced size and to the consumed size in addition to the eight bytes allocated for the I O messaging connection For this example there would be a total of 10 produced bytes and 10 consumed bytes allocated for this one Inline PCP module When using PCP fragmentation a request will be sent and a response will be returned the format of a request and a response is as follows Request Output Data NO Invoke ID Byte 0 Service Byte 1 Module number Byte 2 Index low Byte 3 Index high Byte 4 Subindex Byte 5 Length Byte6toN Data block if necessary 7538_en_01 PHOENIX CONTACT A 19 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC Request Output Data With Invoke ID Successful Response Input Data NO Invoke ID Errored Produced Response Input Data NO Invoke ID Successful Response Input Data With Invoke ID Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 to N Byte 0 Byte 1 Byte 2 Byte 3 to N Service Invoke ID Module number Index low Index high Subindex Length Data block if necessary Service Status Length Data block if necessary If the response was not successful the response will be returned in the following format Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byt
82. e Disable If the software update status is set ta enable the IL EIP BK DIE DOA will try to load new software after reboot Press the apply and reboot button to change the software update status and start eboot of the IL EIP BK DIE DO Enter password Apply and Reboot Figure 3 7 Software Update menu THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS If BootP is set to Enable and a reply with values for TFTP Server IP Address and Downloadable File Name is received on a restart these values overwrite the entries made in WBM The received values are displayed in WBM after the restart In the event of an error during Flash programming e g voltage interrupt the bus coupler can only be restarted by repeating the update The bus coupler starts the update automatically after a restart Access to WBM is no longer possible 3 5 8 Process Data Access via XML The integrated web server of the IL EIP BK DI8 DO4 2TX PAC offers the option of accessing the process data of the connected Inline terminals via a web page in XML format You can access the web pages via a standard web browser To access the XML pages with the process data in the address line of the browser enter the address in the following format http lt IP address gt procdata xml 7538 _en_01 7538 en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Startup Operation 3 5 9 XML File Structure The XML
83. e fragmentation will react during a break in the communications path on the Inline station s backplane The error handling sequence is also applicable for a write sequence Events 1 to 4 Refer to the fragmented read example for an explanation of events 1 to 4 Input Data Table Output Data Table Event Sequence for Bytes 0 to 7 Event Sequence for Bytes 0 to 7 Byte 2 Byte Byte er Byte 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 Tx Tx Tx Tx Tx Tx Tx Data 1 Data2 Data3 Data4 Data5 Data6 Data7 0 1 1 0 1 4 XX XX XX XX XX Rx Rx Rx Data 1 Data2 Data3 Data4 Data5 Data6 Data XX XX XX XX XX XX Status 1 1 1 1 1 4 00 Control Tx Tx Tx Tx Tx Tx Tx Data 1 Data2 Data3 Data4 Data5 Data6 Data 7 0 1 1 0 1 4 Status Rx Rx Rx Rx Rx Rx Rx Data 1 Data2 Data3 Data4 Data5 Data6 Data lt lt Event 4 27 48 ox 65x 6C ex BO OF hex 20 ex 5T hex hex H e le o oy N B A data path is broken on the Inline Station s communications Eventa backplane during a read 1 1 1 1 1 4 00 hex Control Tx Tx Tx Tx Tx Tx Tx Data 1 Data2 Data3 Data4 Data5 Data6 Data 41 0 Event 6 gt O0 1 1 0 1 4 ENEZEIEIEIEZEIEZ Status Rx Rx Rx Rx Rx Rx Rx Data 1 Data2 Data3 Data4 Data5 Data6 Data AA ere ST eT lt q Event 7 05 fs hex hex hex i hex a hex XX XX er 0 r d Control Tx Tx Tx Tx Tx Tx Tx Data 1 Data2 Data3 Data4 Data5 Data6 Data
84. e when there are no I O connections in the established state Number of bytes of process data used by the module Data returned from the Inline module to the IL EIP BK DI8 DO4 2TX PAC Data size is determined by the I O module Data sent from the IL EIP BK DI8 DO4 2TX PAC to the Inline module Data size is determined by the I O module If set the PCP Process Data IN is added to the produced data of all the I O connections and the PCP Process Data OUT is added to the consumed data This attribute affects the produced and the consumed sizes of the I O connections and is therefore only settable when there are no I O connections in the established state This attribute defines what invoke ID is used for PCP writes Default is 0 This attribute defines what invoke ID is used for PCP reads Default is O PHOENIX CONTACT B 33 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC B17 Serial Communications Object Class Code 106gac 6Ahex The Serial Communications Object allows the user to control and transfer serial data on RS232 and RS485 485 422 modules B17 1 Serial Communications Object Class Attributes ne Get Revision FUINT i a eooo 0 8 Number of attached T FPN D B 17 2 Serial Communications Object Instance 1 Number of Serial Modules Attributes Type Value C En B 17 4 so je po N a ooo s fe IV Sonata word w Jo s oosa v Serano em e en Data Fragment EEE of a ZZ
85. e 7 Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 to N Service Status Error class Error code Additional error code 1 LSB if necessary Additional error code 1 MSB if necessary Additional error code 2 LSB if necessary Additional error code 2 MSB if necessary Service Invoke ID Status Length Data block if necessary If the response was not successful the response will be returned in the following format A 20 PHOENIX CONTACT 7538_en_01 Errored Produced Response Input Data With Invoke ID Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Byte 8 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Communications Methods Service Invoke ID Status Error class Error code Additional error code 1 LSB if necessary Additional error code 1 MSB if necessary Additional error code 2 LSB if necessary Additional error code 2 MSB if necessary The Response Service byte is a reflection of the request service byte with the exception of the request response bit see the definition of the Start Fragment for more information on this bit It is important to keep track of the client service relationship between the master and the slave For example a read request involves a single non fragmented service The slave responds with a completely new service to transfer the response data This new service begins with a start fragment and ends if enough data was requested with a last frag
86. e Object allows the user to control and monitor the Inline interface on the IL EIP BK DI8 DO4 2TX PAC B 12 1 Inline Interface Object Class Attributes fatwibute Access Name ie Vie B 12 2 Inline Interface Object Instance 1 Attributes First Faulted Module USINT ae Get Loop Diagnostic Count UINT G G G G 1 Connection Failure USINT Endpoint 1 Connection Failure USINT 14 Endpoint 2 14 3 Latched Connection Failure Endpoint 1 Endpoint 2 i a eooo e e O 30 Error History last saved UINT 30 Latched Inline Status BYTE 15 16 1 19 et et et et et et et et 2 et et B 20 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Inline Interface Object Class Code 101 gac 65hex B 12 3 Service Code Class Eulen Service Name Inline Interface Object Common Services Yes Rest 4 Inline Status B12 4 Values for Inline Interface Object Class Attributes EEE EE EE eee Fault Cycles ne Timeout Inline Connection Error Peripheral Fault Configuring Module Power Fault Change 5 First Faulted Contains the number of the first module that is faulted 1 Inline BK Module 6 Max Retry Sets the number of bad responses the IL EIP BK DI8 DO4 2TX PAC will accept before flagging an error Default 32 7 Number of Modules Displays the number of Inline modules that the IL EIP BK DI8 DO4 2TX PAC detected 8 Number of Bits Di
87. e Status Word and its desired effect on the network and or failing node through the users application PHOENIX CONTACT 4 5 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC 4 2 5 Latched Diagnostics The bus coupler will latch the last occurring Inline Status word fault module number and connection point 1 and 2 failures This benefits the user by capturing any fault that may be occurring intermittently and that is occurring too quickly to be updated by the Ethernet IP implicit or explicit message These latched values can not be cleared until the station is reconfigured The following latched diagnostics are available through the EDS file or by sending an explicit message to the Inline Interface Object Class Code 65nex Latched Inline Status This parameter will contain the last reported Inline station failure The bit weights signify the Word same failures as described in the Inline Status word byte 0 Latched Faulted Module This parameter will contain the first failed module location that was reported during the last Inline station fault The bit weights signify the same failures as described in the Inline Status word byte 1 Latched Connection This parameter will contain the number of the module that was reported on the first end of a Failure Endpoint 1 connection failure Latched Connection This parameter will contain the number of the module that was reported on the other end of
88. e same method as for multiplexed modules whereby the configuration word is placed permanently into the poll data Once the new thermocouple setting is made the new configuration will be stored in the flash memory of the bus coupler If the bus coupler is replaced the configuration will need to be redone AIP Object Class Code 10gac OAhex Settings are described in Appendix B Ethernet IP Object Classes Message Types and Services of this manual 7538_en_01 PHOENIX CONTACT 3 23 IL EIP BK DI8 DO4 2TX PAC 3 24 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS 3 10 4 Special Function Modules General Configuration Special function modules such as the incremental encoder absolute encoder and the high speed counter are configurable through the produced consumed data channel by default Output word s that are assigned to the special function module are used to program the terminal The user must refer to the specific special function module s data sheet or manual to determine what codes need to be written to the associated output word s If the special function module is not included in the poll it can be programmed through the use of explicit message Special Function Object Class Code 103gec 67 hex The programming of a special function module cannot be stored in the bus coupler flash memory The user s application will have to implement a programming subroutine PHOENIX CONTACT 7538 _en
89. ead request this bit will be set by the bus coupler as soon as the read request is called For a write request this bit is set as soon as all data reaches the PCP module 0 Request Service in process 1 Response Service is processed Fragment Type For a start fragment these bits will always be a zero 00 Start fragment Fragmented Bit 4 informs the slave as to whether the message contains more than eight bytes 7 data bytes or not 0 Does not fragment 1 Fragments PCP Service Bits 3 to 0 informs the slave of the type of message service being sent The means are described as follows OOnex No action Clears input bytes in response O01 hex Read O2 hex Write O3nex Read PDU length O4nextO OF hex Reserved 7538 _en_01 Middle Fragment Last Fragment 7538 en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Communications Methods Any write request or read response requires more than the available number of data bytes in both a start fragment and a last fragment then a middle fragment must be used Middle fragments have the following format Byte O Service Byte 1 Data block if necessary Bytes 2to7 Data blocks if necessary Byte 0 Service Definition of a Middle Fragment Shown in Table A 17 Table A 17 Service byte definition of the middle fragment BE Bit 7 Request Response See start fragment for definition Bit 6 to 5 Fragment Type For a middle fragment these bits will always be a 01 01 M
90. ecoverable faults Checksum A D 6 Serial Number The Serial Number is encoded in the product during the manufacturing cycle and is guaranteed to be unique across all product lines produced by Phoenix Contact 7 Device Name The Device Name provides a character array containing the short string IL EIP BK DI8 DO4 2TX PAC B 4 PHOENIX CONTACT 7538 _en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Router Object Class Code 02 ac O2hex B5 Router Object Class Code 02 4ac O2hex The Router Object provides a messaging connection point through which a client may address a service to any object class or instance residing in the physical device B 5 1 Router Object Class Attributes tbo cess name ve vate B 5 2 Router Object Instance 1 Attributes Access Name Type Valu Router Class List ARRAY 07 00 01 00 02 00 04 00 06 00 F4 00 F5 00 F6 00 B 5 3 Router Object Common Services Service Code Class Service Name Get_Attribute_Single 7538_en_01 PHOENIX CONTACT B 5 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC B6 Assembly Object Class Code 04 gac OAnex The Assembly Object binds attributes of multiple objects to allow data to or from each object to be sent or received over a single connection B 6 1 Assembly Object Class Attributes u et B 6 2 Assembly Object Instance 100 Attributes 3 Consumed output Data Array of USINT B 6 3 Assembly Object Instance
91. ed by the greater of either the actual number of DOPs or the number of bytes reserved by this attribute 24 Fault Mode This attribute allows the user to select which action is taken during a major failure 32 Inline Control Byte When set to a 1 the first byte of the Poll Command is the Inline Control Byte See Inline in Poll Object Default 0 38 Number of PCP Indicates how many PCP capable modules are present on the Inline configuration Modules 39 Number of SCO Indicates how many PCP capable modules capable of serial communications are present Modules on the Inline configuration 40 Number of PCP Selects number of PCP fault data bits to add to the I O PCP Fault Data area If the number Faults entered is less than the number of PCP modules the first modules in order of instance will receive bits until the bits are filled 41 Number of SCO Selects number of SCO fault data bits to add to the I O PCP Fault Data area If the number Faults entered is less than the number of SCO modules the first modules in order of instance will receive bits until the bits are filled B 18 PHOENIX CONTACT 7538_en_01 42 Run ldle in Produced I O 43 Run ldle In Consumed I O 44 Watchdog Timeout Action 45 P amp P Mode 46 Delete All Timed Out Connections 47 Confirm Peripheral Faults 48 1 O Size Word Align 49 BootP Operation 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configura
92. eeeeeeeeeeeeennees B 42 7538 _en_01 PHOENIX CONTACT iii onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP DI8 DO4 2TX PAC IV PHOENIX CONTACT 7538_en_01 1 The Inline Ethernet IP Bus Coupler Ethernet IP Bus Coupler 7538 en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS The Inline Ethernet IP Bus Coupler The Ethernet IP bus coupler shown in Figure 1 1 provides an interface between Ethernet IP and the Phoenix Contact range of Inline I O modules It also provides the required bus signal conditioning and the power supply for the connected station components The bus coupler provides the initial connection for the main supply Um and the segment I O supply Us to the station You can also provide the main supply U and the segment supply Us using a power terminal and or a segment terminal respectively rd und 08 u er i 260 ont En un Ha j t hpa u IP Figure 1 1 Key 1 Electronics base 2 Reset button 3 Ethernet IP connections twisted pair cables in RJ45 format 4 Power connector 5 Connector for digital outputs 6 Connector for digital inputs 7 8 9 10 11 4x 75380001 Features of the Inline Ethernet IP bus coupler Diagnostic and status indicators Labeling field End plate MAC address in clear text and as a barcode Two FE contacts for grounding the bus coupler using a DIN rail on the
93. eproduction translation and public disclosure as well as electronic and photographic archiving or alteration requires the express written consent of Phoenix Contact Violators are liable for damages Phoenix Contact reserves all rights in the case of patent award or listing of a registered design Third party products are always named without reference to patent rights The existence of such rights shall not be excluded How to Contact Us Up to date information on Phoenix Contact products and our Terms and Conditions can be found on the Internet at www phoenixcontact com Make sure you always use the latest documentation It can be downloaded at www download phoenixcontact com A conversion table is available on the Internet at www download phoenixcontact com general 7000_en_00 pdf If there are any problems that cannot be solved using the documentation please contact your Phoenix Contact subsidiary Subsidiary contact information is available at www phoenixcontact com PHOENIX CONTACT GmbH amp Co KG PHOENIX CONTACT FlachsmarkstraBe 8 586 Fulling Mill Road 32825 Blomberg P O Box 4100 Germany Harrisburg PA 17111 0100 Phone 49 0 52 35 3 00 USA Fax 49 0 52 35 3 4 12 00 Phone 1 717 944 1300 Should you have any suggestions or recommendations for improvement of the contents and layout of our manuals please send your comments to tecdoc phoenixcontact com 7538 _en_01 onlinecomponents c
94. eral Configuration This section describes how to change default settings for the Inline 2 channel thermocouple module However changing the default settings for the 2 channel RTD modules is accomplished in the same manner There is no Thermocouple or RTD Object To change default settings the Analog Input Points AlPs Object Class Code 10gac OAhax Must be used Refer to Appendix B Ethernet IP Object Classes Message Types and Services Default settings for the thermocouple modules are Sensor type K Resolution 0 1 C 1 microvolt Output format 15 bits and 1 sign bit with extended diagnostics Cold junction Internal In order to change any setting Refer to the thermocouple data sheet to determine the appropriate attribute settings for the AIP Object Class Code 10gac OAhex Keep in mind that thermocouple or RTD instances will appear as analog input instances There are 2 instances for every thermocouple or RTD module Channel 0 will be the first instance and Channel 1 will be the second The user must keep track of which instances are analog inputs and which instances are thermocouple inputs Figure 3 10 shows a station where instances 1 and 2 of the AIP are used by the 2 channel thermocouple Instances 3 4 5 and 6 of the AIP are used by the next two 2 channel analog input modules Instances 7 and 8 of the AIP are used by the next 2 channel thermocouple module The last two 2 channel analog input modules oc
95. ers are checked for agreement before the information is exchanged during the connection establishment Communication Reference CR The communication relationship list is set up line by line Every permissible communication relationship contains a number the communication reference CR The communication relationship is thereby unambiguously coded An unambiguous code is necessary in order to distinguish between the individual devices The Inline bus coupler numbers the devices automatically during local bus initialization It allocates the numbers beginning with 2 in the order of the physical bus configuration PHOENIX CONTACT A 1 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC A 1 2 Communication Services The client and the server use communication services for the service order and execution If in our example the parameter value for the speed acceleration is to be transmitted to the frequency inverter then this is done by means of a write command which implies using the write service A service is divided into individual basic service operations primitives First a service request is transmitted in our example a Write Request the parameter value is transmitted The frequency inverter receives the parameter value as a service input in our example a Write Indication After execution of the command when the parameter value has been entered the frequency inverter transmits a
96. ess arnav oFeusnrs o 7 fea mereme om o o ooo o em meracetae sortene je B 20 3 Ethernet Link Object Common Services Service Code Class mE Service Name B 42 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Ethernet Link Object Class Code 2464 F6nex B 20 4 Values for Ethernet Link Interface Object Class Attributes 1 Interface Speed The Interface Speed attribute shall indicate whether the interface is running at 10 Mbps 100 Mbps 1 Gbps etc The scale of the attribute is in Mbps so if the interface is running at 100 Mbps then the value of the Interface Speed attribute shall be 100 The Interface Speed is intended to represent the media bandwidth the attribute shall not be doubled if the interface is running in full duplex mode 2 Interface Flags Link Status Indicates whether or not the Ethernet 802 3 communications interface is connected to an active network O indicates an inactive link 1 indicates an active link Half Full Duplex O indicates the interface is running half duplex 1 indicates full duplex Note that if the Link Status flag is O then the value of the Half Full Duplex flag is indeterminate 3 Physical Address The Physical Address attribute contains the interface s MAC layer address The Physical Address is an array of octets The recommended display format is XX XX XX XX XX XX starting with the first octet Note that the Physical Address is not a se
97. f the device will be set to disabled following PCP Configuration completion of this function J Home Enter password Store Config Control Device Function This service can be used to confirm the peripheral faults of all modules Enter password Figure 3 4 Website of the services 7538 _en_01 7538 en_01 3 5 3 Bus Configuration THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Startup Operation This example website shows the current configuration of the Inline station including the I O produced and consumed sizes and local bus baud rate If an error occurs the error location is indicated The number of the affected element is highlighted in red Qcontact IL EIP BK DI8 DO4 Bus Configuration IL EIP BK DI8 DO4 2TX PAC last update 13 20 30 Produced size in bytes 8 Module Inputs Consumed size in bytes 4 Module Outputs Baudrate 500 kBaud __ General Instructions Number Symbol _ Device Information C Device Configuration y Inline Station Services Process Data Monitoring Remote Diagnostics Bus Configuration PCP Configuration 4 Figure 3 5 o Bus configuration of the station Description IL EIP BK Dis DO4 Module with 4 digital outputs Module with 8 digital inputs Module with 4 digital inputs Module with 4 digital inputs Module with 4 digital outputs Module with 4 digital outputs Module with 4 digital outputs Module with 2 analog input and output chan
98. figuration Object Class Code 64pex and Inline Object Class Code 65hex 4 2 1 Inline Status Word By default Inline Status word data is made available to the user as two bytes of diagnostic data in the produced data These two bytes contain the Inline fault code byte 0 and the number of the first module in the local bus that is faulted byte 1 The status word adds 2 bytes to the produced data size by default The status word updates status automatically so when an error is cleared the status will be set back to a 0 If the user needs to remove this data from the produced data the status word can be disabled by setting Configuration Object Class 100gec 64nex Attribute 11 Use Inline Status to 0 then setting Configuration Object Class 100gac 64 nex Attribute 7 Add All I O to 1 4 2 2 Major Minor Faults By default all Inline Status word fault bits byte O bits 0 2 6 except for bit 1 are considered major recoverable faults as defined in the Identity Object state and status attributes and will flash the red MS LED on the bus coupler when that specific type of failure occurs Bit 1 peripheral fault is assigned as a minor recoverable default value fault and will not flash the MS LED when in a faulted condition These default values can be changed by using the EDS file or by sending an explicit message to the Configuration Object Class Code 64 Possible fault action settings are 0 None 1 Minor Recoverable Fault 2 Majo
99. file contains different data areas IL_STATION Frames for the entire XML file The mandatory elements of this frame are IL_BUS_TERMINAL and IL_BUS IL_BUS_TERMINAL This data area contains information on the entire Inline station bus coupler and all connected terminals This data area includes TERMINAL_TYPE This area contains the name of the bus coupler which is always IL EIP BK DI8 DO4 2TX PAC NAME Contains the user specific station name The station name can be modified via WBM IP_ADDRESS Contains the IP address of the station MODULE_NUMBER Contains the number of connected Inline terminals including local I Os In the event of a bus error the number of the last known operable configuration is indicated DIAGNOSTIC_STATUS_REGISTER Contains the status of the Inline station represented by all bits of the diagnostic status register A detailed description can be found in the diagnostic parameter register Whenever an error bit is set the diagnostic parameter register is rewritten IL_BUS Frame for the connected Inline terminals IL_MODULE Frame for the data of an individual Inline terminal The terminals are numbered consecutively from one to a maximum of 63 MODULE_TYPE Contains the terminal type Possible types are DI DO DIO Al AO AlO and PCP PD_CHANNELS Number of process data channels in an Inline terminal For digital terminals the number of channels is equal to the number of supported bits
100. g capacity of the voltage jumpers is limited For the limit values of the individual voltage jumpers refer to the IL SYS INST UM E user manual Observe the current consumption of each device for a given power supply Current consumption specifications can be found in the product specific data sheets 7538 _en_01 7538 en_01 il onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Installation 2 2 Bus Coupler Wiring 2 2 1 Connecting the Ethernet IP System Connect the Ethernet IP system to the bus coupler see Figure 2 2 via an RJ45 connector For the pin assignment please refer to Table 2 1 th gone 80 g i GP ai On ase p ee net n p tt Table 2 1 Pin assignment of the RJ45 connector TxD transmit data TxD transmit data RxD receive data RxD receive data Both Ethernet interfaces have an auto crossover function PHOENIX CONTACT 2 3 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC 2 2 2 Connection of Supply Actuators Sensors Figure 2 3 and Table 2 2 to Table 2 5 list terminal assignments for the bus coupler connectors Figure 2 4 shows a wiring schematic for the power connector Note that the bus coupler provides I O power to the main U and segment Us circuits for the Inline station Communications logic power and analog power U ana are also supplied by the bus coupler through the U connec
101. grated free running circuit in the output chip 0 7 A minimum 10 WA il When not loaded a voltage can be measured even at an output that is not set Digital Inputs Number Connection method for sensors Input design Definition of switching thresholds Maximum low level voltage Minimum high level voltage Common potentials Nominal input voltage Un Permissible range Nominal input current for Un Current flow Delay time Permissible cable length to the sensor Use of AC sensors Safety equipment Error message to the higher level control system Mechanical Requirements Vibration test sinusoidal vibrations according to IEC 60068 2 6 EN 60068 2 6 Shock test according to IEC 60068 2 27 EN 60068 2 27 Conformance With EMC Directives Developed according to IEC 61000 6 2 IEC 61000 4 2 ESD IEC 61000 4 3 radiated noise immunity IEC 61000 4 4 burst IEC 61000 4 5 surge 7538_en_01 8 2 and 3 wire technology According to EN 61131 2 Type 1 Ulmax lt 5 V Vermin gt 15 V Sensor supply Uy ground 24V DC 30 V lt Un lt 30 V DC 3 mA typical Limited to a 3 mA maximum lt 500 ms 100 m AC sensors in the voltage range lt Uy are limited in application Surge voltage polarity reversal Sensor supply not present 5g load 2 hours in each space direction 25g load for 11 ms half sinusoidal wave three shocks in each space direction and orientation Criterion B 6 kV contact discharge 6 kV air
102. guration of the station Configure the bus coupler using one of the following 3 methods 1 Electronic Data Sheet EDS file 2 Auto configuration no software required 3 Sending an explicit message Electronic Data Sheet EDS File Method The EDS file is the software interface between the bus coupler and a configuration software package The EDS file contains information about the number of produced and consumed bytes and user settable parameters The following procedure describes how to configure a bus coupler using the Electronic Data Sheet Repeat this procedure for each bus coupler on the network 7538_en_01 PHOENIX CONTACT 3 17 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC 1 Obtain a list of VO modules that will be used in the Ethernet IP station 2 Determine which types of I O modules will be included in the scan By default all modules will be included If the default needs to be altered a new value must be downloaded to the bus coupler through EDS Parameter Add All Mode 3 Determine whether the Inline Status diagnostic word needs to be included in the produced size By default these 2 bytes will be added to the produced size By using the produced data channel the Inline Status word gives the user the ability to locate and define any faults that could occur on the Inline local bus If the user decides to disable this feature then the user must download a 0 to
103. hat was requested from index 5FEO This reply is explained as follows Table A 26 Slave to master reply with first middle fragment Service os or be o or om Service byte 0 A1hex Bit 7 1 This signifies that the fragment is a response Bit6 0 Designates a middle fragment when bit 6 0 and bit 5 1 Bit5 1 Designates a middle fragment when bit 6 O and bit 5 1 Bit 4toO 1 These bit count the fragmenis 1 the 1st middle fragment Bytes 1 to 7 7 Specifies 7 additional bytes of data 5 received in the first response Event 7 Table A 27 shows the master to slave acknowledgment of the response being received In this acknowledge the service byte reflection is the indication that the 1st middle fragment response was received Table A 27 Master to slave acknowledge of the first middle fragment Service Al hex Event 8 Table A 28 shows the slave to master reception of the last fragment that was requested from index 5FEOpex This fragment returns the last 4 data bytes as expected by the length byte shown in Figure A 5 This response is explained as follows Table A 28 Slave to master acknowledge last fragment response Service byte 0 COnex Bit 7 1 This signifies that the fragment is a response Bit 6 1 Designates a last fragment when bit 6 1 and bit 5 0 Bit5 0 Designates a last fragment when bit 6 1 and bit 5 O Bits 4 to 0 Reserved 7538_en_01 PHOENIX CONTACT A 29 THE ONLINE DISTRIBUT
104. he Inline station s backplane Input Data Table Output Data Table Event Sequence for Bytes 0 to 7 Event Sequence for Bytes 0 to 7 Byte Byte Byte Byte 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 Event1 gt 0 1 1 0 1 4 HEHHEHE biaa lt q Event 2 fhe Fo a me a Event 3 gt 0 1 1 0 1 4 ESCSESESCSDSEIE 1 1 11 4 lt q Event 4 tan O0 an tm a a he an Event 5 0 1 1 0 1 4 CHEIEIEIEIEIEIET 1 1 1 1 1 4 lt q Ereignis 6 Fate or on 00m fom 08 oe Event 7 gt 0 1 1 0 1 4 ESMEIEIEIEIEIEIEN Error Inline Station encounters a communications path break Event 8 gt between local I O modules 1 1 1 1 1 4 lt q Event 9 1 1 1 1 1 4 O0 1 1 0 1 4 1 1 1 1 1 4 O0 1 1 0 1 4 7426A164 Figure A 7 Local communications error sequence using PCP fragmentation 7538_en_01 PHOENIX CONTACT A 35 IL EIP BK DI8 DO4 2TX PAC Events 1 to 7 Event 8 Event 9 Event 10 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS For an explanation of events 1 to 7 look at the examples in this section for a read sequence An error has occurred The communications path between the bus coupler and its I O has been broken A PCP abort error fragment has been issued from the slave to the master as shown in Table A 43 Table A 43 Abort error fragment Service byte 0 EQnex Bit 7 1 This signifies that the fragment is a response Bit6 1 Designates an abort error fragme
105. he data is received for each request attributes 8 12 13 and 14 The following procedure uses sub method B Three explicit messages will be required to read a specific PCP memory area They are as follows 1 Select index 2 Select subindex 3 Read data These messages will have the format shown below and will need to be sent with the required service 1 Build Select Index Message Message is sent using the Set Attribute Single service 16 geC Class Code 105gec 69hex POP Special Function Object Instance Select the occurrence of the PCP device within the object Attribute 12dec PCP Read Index Example Index number 5FEOnax 2 Build Select Subindex Message Message is sent using the Set Attribute Single service 1 6 dec Class Code 105gec 69hax PCP Special Function Object Instance Select the occurrence of the PCP device within the object Attribute 13gec PCP Read Subindex Example Subindex number 0 3 Build Read Data Message Message is sent using the Get_Attribute_Single service 1 4 dec Class Code 105 gec 69hex PCP Special Function Object Instance Select the occurrence of the PCP device within the object Attribute 14gec PCP Read Data Instance is determined by the physical location on the Inline station The 1st instance will be assigned to the PCP module located closest to the bus coupler and the last instance maximum of 8 will be assigned to the right most PCP module Serial modules will occupy an instance in this
106. hout tools End clamp can be fixed using screws Additional System Components Description Double sheathed Ethernet cable Flexible Ethernet cable Media converter 660 nm Voltage supplies Tools Description Assembly tool for RJ45 connector Screwdriver according to DIN 5264 blade width 3 5 mm Software Description BootP IP Addressing Tool Documentation Description I O Modules at Bus Couplers application note Automation Terminals of the Inline Product Range user manual 7538 en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Technical Data and Ordering Data Ordering Data Type IL EIP BK DI8 DO4 2TX PAC Type IL BKDIO PLSET FL PLUG RJ45 GR 2 FL PLUG RJ45 GN 2 CP MSTB ZB 6 see CLIPLINE catalog ZB 12 see CLIPLINE catalog IB IL FIELD 2 IB IL FIELD 8 ESL 62X10 ESL 62X46 NS 35 7 5 PERFORATED NS 35 7 5 UNPERFORATED CLIPFIX 35 5 E UK Type FL CAT5 HEAVY FL CAT5 FLEX FL MC 10BASE T FO POF QUINT PS see INTERFACE catalog Type FL CRIMPTOOL SZF 1 0 6X3 5 Type IPAssign exe Type AH IL BK IO LIST IL SYS INST UME Order No 2897758 Order No 2878599 2744856 2744571 1734634 1051003 0812120 2727501 2727515 0809492 0809502 0801733 0801681 3022276 1201442 Order No 2744814 2744830 2744513 Order No 2744869 1204517 Order No Pcs Pkt 4 Pcs Pkt 4 2 2 100 10 10 10 10 4 50 50 Pcs Pkt 1 meter 1 meter 1 P
107. iddle fragment Bit 4 to O Count Bits 4 to O keep track of how many middle fragments have been sent 31 is the maximum number of middle fragments that can be counted 01 to 1 Frey If more fragments are needed the fragment number will roll over to 0 and fragments can continue to be sent To recognize the end of a fragmented message a last fragment must be issued A last fragment has the following format Byte O Service Byte 1 to 7 Data block if necessary Byte 0 Service Definition of the Last Fragment see Table A 18 Table A 18 Service byte definition of the last Far Response Bit 7 Request Response See start fragment for definition Bit6t05 Fragment Type For a last fragment these bits will always be a 10 10 Last fragment Bit 4t0 0 Reserved PHOENIX CONTACT A 23 IL EIP BK DI8 DO4 2TX PAC Abort Error fragment A 24 PHOENIX CONTACT THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS If a transmission error is detected an abort error fragment will be generated Byte 0 Service Definition of a PCP Abort Error Fragment see Table A 19 Table A 19 Service byte definition of the PCP abort error oe m O a Response Bit 7 Request Response See start fragment for definition 0 Request 1 Response Bit 6 to 5 Fragment Type For an abort error fragment these bits will always be an 11 11 Abort error fragment Bit 4 to 0 Reserved Byte 1 Status Definition of a Abort Error Fragment See Table A 20 Table
108. igned for the serial Inline modules and will not work for other PCP based Inline modules Depending on the amount of data to be sent the number of fragments required to read write data can vary Fragments are eight bytes in length Each fragment contains a request format and a response format These formats are detailed in the following paragraphs A 2 1 1 Format of Fragmented Serial Output Data Consumed Request Byte 0 Control Byte See Table A 1 Bytes 1to 7 Data block if necessary Table A 1 Control Byte Receive Transmit Reset Number of Data Bytes to Ack Request Request Transmit Per Fragment Bit 7 Reserved Bit 6 Reserved Bit 5 Receive Ack RxAck This bit must be set to the value of the Receive Request bit RxReq in order for the module to receive more data This tells the module that the master has received the data and has processed it Bit 4 Transmit Request This bit must be toggled to signal the module that there is new data to transmit On devices that cannot ensure data consistency the user should first set the number of bytes and place the proper data into the TxData mapping before toggling this bit Bit 3 Reset Request When this bit is set all errors are cleared the buffers are flushed and the RxReq and TxAck bits are cleared This allows re sync of the protocol Bit 2 to 0 Number of Bytes to Transmit This tells the module how many bytes of the data are valid and should be transmitted A 8 PH
109. in the following menus lt ip address gt index htm General Instrucions Information geninst htm Device Information General devinfo htm Technical Data techdata htm Hardware Installation hwinstal htm Local Diagnostics locdiag htm Device Configuration IP Configuration ipconfig htm ipconinf htm System Identification sysconf htm sysinfo htm Software Update swupdate htm swupinfo htm ftpinfo htm Change Password password htm passinfo htm Inline Station Services services htm svppinfo htm svpfinfo htm Process Data Monitoring pdmonit htm pdmoninf htm pdnfinfo htm Remote Diagnostics remdiag htm Bus Configuration busconf htm PCP Configuration pcpconf htm pcpinfo htm Figure 3 2 Structure of the web pages example 7538_en_01 7538 en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Startup Operation 3 5 1 Diagnostics On this website example you can have a look at the local bus diagnostics The diagnostic status and diagnostic parameter register are shown here Din IL EIP BK DI8 DO4 2TX PAC last update 13 10 37 CONTACT Remote Diagnostics Controller board ready to operate V Selected configuration ready to operate IL EIP BK DI8 DO4 Data transmission active en 2 i j j j 1 __ General Instructions Diagnostic Status Register Diagnostic routine active I Controller board hardware error J Device Information l Bus error Peripheral fault
110. is no triggering during timeout an error occurred Two reactions follow The selected fault response mode is executed The NetFail signal is set For safety reasons the user cannot stop the watchdog once it has been activated In case the user terminates the controlling application there is no watchdog triggering when timeout has expired the NetFail signal is set and the selected fault response mode is executed The NetFail signal is acknowledged using the web based management and the fault response mode is reset Read calls do not trigger the process data watchdog By acknowledging the error the watchdog is restarted This means that it must be triggered during timeout otherwise an error is detected again Dass IL EIP BK DI8 DO4 2TX PAC last update 14 33 58 CONTACT i Process Data Monitoring Reset Fault Mode default Fault Response Mode Standard Fault Mode IL EIP BK DI8 DO4 Hold Last State Mode _ General Instructions Process Data Watchdog 0 a Timeout _ Device Information The time is indicated in milliseconds and ranges from 200 ms to 65 000 ms Dans Coalitions A value of 0 ms disables the Process OUT Data Monitoring y Inline Station 3 Services Enter password Apply Process Data Monitoring Remote Diagnostics i 2 Remote Diagnostics Network Failure E Bus Configuration Status No Network Status failure NS occurred PCP Configuration J Home Enter password Figure 3 6 Process data mon
111. itoring 3 8 PHOENIX CONTACT 7538_en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Startup Operation 3 5 5 Password Protection All status changes to the bus coupler require the entry of a password The password can be changed at any time Your unique password must be between four and twelve characters long please note that it is case sensitive By default upon delivery the password is private If you forget the password the only way to access the bus coupler again is to reset the entire configuration using the reset button 3 5 6 Ethernet Speed and Configuration The IL EIP BK DI8 DO4 2TX PAC firmware will include a website setting that allows for the selection of Fixed Manual override or auto negotiate of transmission speeds Auto Negotiation plus Manual Override provides support for the widest possible range of network infrastructure devices such as switches This will allow the BK to adapt to virtually all possible system applications including older systems that do not support the higher auto data rates By providing the manual over ride the system is freed of any auto negotiate traffic that could possibly impact an older system However by default the module will be in the auto negotiate detect mode of data transmission to allow for easiest connection to current systems 3 5 7 Firmware Update via WBM and TFTP The following steps must be carried out when executing a firmware update using WB
112. ject is required on all devices and provides identification of and general information about the device B 4 1 Identity Object Class Attributes bots Access nome ve vate Get Set Max Instance Attribute UINT he B 4 2 Identity Object Instance Attributes Aivibute Access Name type vaesena oo qa pow um ja rn re fe A a STRING 6 IL EIP BK DI8 DO4 2TX PAC 7538_en_01 PHOENIX CONTACT B 3 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC B 4 3 Identity Object Common Services Service Code Class Service Name Yes Yes Get_Attribute_All Yes Yes Get Attribute Single B 4 4 Values for Identity Object Class Attributes 3 Product Code The product code is fixed at 8167 for the IL EIP BK DI8 DO4 2TX PAC The product code is used within the Electronic Data Sheet format to uniquely identify the product type 4 Revision The major revision number will increment as functional enhancements are implemented The minor firmware revision control number is incremented if minor changes are incorporated 5 Device Status 1 allocated Besma OOOO S SS Reseed CdS SSOSOSOSOSOCSCSC S Minor Recoverable Fault 0 no fault 1 minor recoverable faults DOP short circuit Minor Unrecoverable Fault 0 no fault 1 minor unrecoverable faults Major Recoverable Fault 0 no fault 1 major recoverable faults Loss of 24 V DC Major Unrecoverable Fault 0 no fault 1 major unr
113. l Data is added to the I O connection allowing dynamic changing of the AIP control word B 12 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Analog Output Point AOP Object Class Code 11 ec OBhex B10 Analog Output Point AOP Object Class Code 11gec OBhex The IL EIP BK DI8 DO4 2TX PAC supports Analog Output Points AOP There is a separate instance for each analog channel available on the device B 10 1 AOP Object Class Attributes Aivibute Access name fiye Tee Number of AOPS C e um B 10 2 AOP Object Instance 1 Number of AOPs Attributes eases name Tipe vate 104 7 7 fe a i en ToupunDaia type umr J e owsa Fansee eve o 9 fe a0 wo Gesa wese jene fos Geuse Famvas r dO Re E 100 B 10 3 AOP Object Common Services Service Code Class en Service Name 0 FFFFhox u 7538_en_01 PHOENIX CONTACT B 13 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC B10 4 Values for AOP Object Class Attributes 3 Value The analog output value is given in offset binary format The value provided must be in the range 0 65535 0 FFFFhex Reference Inline analog output module specific data sheet for actual values 7 Output Range The analog output range defaults to a fixed value of 1 0 V DC to 10 V DC If the AO module reports that it the range is different it will change to 3 10 V DC to 10 V DC 8
114. l Function and Serial Communication Objects cannot exceed 8 There are certain considerations that must be observed when determining the number of I O devices that can be connected to the bus coupler These considerations are described in the following paragraphs 1 The bus coupler cannot provide more than 0 8 A of communications logic power U If U power requires more than 0 8 A a IB IL 24 PWR IN R terminal can be inserted to reinject U power 2 The maximum number of devices connected to the bus coupler cannot exceed 61 3 Analog modules cannot draw more than 0 5 A from the analog supply Uana Note that analog modules also require current from the 0 8 A communications logic supply U 4 FLM devices Only the IB IL 24 FLM PAC uses the logic supply U b FLM I O devices will use current from the segment power Us see documentation for the IB IL 24 FLM PAC The IB IL 24 FLM does not count towards the 61 device maximum Each FLM I O device does count towards the 61 device maximum There are 0 8 A of the current available on the Inline communications supply U and 0 5 A of current available on the analog supply U ana Refer to the specific I O module s data sheet or the Phoenix Contact Automation Catalog to determine the amount of current draw required for each I O module or device to be connected to the bus coupler The total current consumption of all modules devices cannot exceed the 0 8 A and 0 5 A ratings state
115. l and analog modules It is not required for special function modules Rules for Reserving I O Memory 1 Reserved I O points will take up physical space in the produced and or consumed data 2 After reserving digital and or analog I O any new modules added must be connected after anywhere to the right of the last digital analog module of the same type and image input or output on the local bus 3 If special function modules are added they must be added after the right most special function module on the station After adding the special function module the station must be reconfigured to add the special function data to the scan This additional data will not effect existing mapping of the master scanner 4 Ifyou want to reserve space for analog input configuration words you must add the number of analog input configuration words to be reserved to the number of analog output words to be reserved This will be the total number of analog output words to be reserved When adding modules to this shared reserve space analog output words will be added to the lower end of this space and analog input configuration words will be added to the upper end of this space until the entire space is used For information about analog input configuration words refer to the Section Analog Input Al Modules on page 3 21 Ways to Reserve I O Memory The bus coupler can reserve digital or analog I O in either the input or output image This will
116. lass 106 gee Serial Communications Object Instance 1 In this case the 1st occurrence of a serial module Attribute 7 Receive data Instance is determined by the physical location on the Inline station The 1st instance will be assigned to the serial module RS 232 or RS 485 RS 422 located closest to the bus coupler and the last instance maximum of 8 will be assigned to the right most module When this message is sent the bus coupler will send its response back to the sender Typically an I O scanner control bit is set when an explicit response is present At that point the response can be read The response will include a positive or negative confirmation The first data byte returned by bus coupler will be the number of bytes to follow These following bytes are the actual data that was received by the serial module Keep in mind that the user will need to understand the explicit message response format dictated by the I O scanner It is probable that several bytes of data pertaining to the response header will be returned before the actual data returned from the serial module is present This header may include such information as transaction ID command nodes address and confirmation positive or negative 7538 _en_01 PHOENIX CONTACT A 17 IL EIP BK DI8 DO4 2TX PAC onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS A 2 2 2 Transmitting Serial Data Attribute 8 of the Serial Communications
117. le message Table A 5 shows that the slave has received 7 bytes of new data This indication is explained as follows Table A 5 Slave to master indication that new data has been received Rx Rx Rx Rx Rx Rx Rx Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 Data 7 27 hex 48hex 65 hex 6Chex 6Chex 6Fhex 20hex 57 hex H e l al 0 Pa W Status byte 0 21 hex Bit5 1 Receive request being toggled indicates that new data is present Bits 2to0 7 Shows the number of bytes received Table A 6 shows the master to slave acknowledgment of a Receive Request indication Table A 6 Master to slave receive data acknowledgement Control Tx Tx Tx Tx Tx Tx Tx Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 Data 7 Control byte O 20nex Bit 5 1 After the 7 bytes have been received and processed the Receive Ack Bit is set to the same value as the Receive Request bit to signal the module that the master is ready to receive more data PHOENIX CONTACT A 11 IL EIP BK DI8 DO4 2TX PAC Event 6 Event 7 Event 8 A 12 PHOENIX CONTACT THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Table A 7 shows that the slave has received 5 additional bytes of data Table A 7 Slave to master indication that more data is present Rx Rx Rx Rx Rx Rx Rx Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 Data 7 05 hex 6F nex 72 hex 6Chex 64 hex 0 w l a Status byte 0 O5hex Bit5 0 Receive request being toggled In
118. lid except for the data of the faulty terminal PHOENIX CONTACT 3 13 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC Adresse http 172 16 113 38 procdata xml E wechseln zu Links lt xml version 1 0 encoding IS0 8859 1 7 gt lt DOCTYPE IL_STATION View Source for full doctype J gt lt IL_STATION gt lt IL_BUS_TERMINAL gt lt TERMINAL_TYPE gt IL EIP BK DIS DO4 lt TERMINAL_TYPE gt Data of Inline Station lt NAME gt IL EIP BK DIE DO4 2TR PAC NAME gt lt IP_ADDRESS gt 172 16 113 98 1P_ADDRESS gt lt MODULE NUMBER 6 lt MODULE NUMBERS lt DIAGNOSTIC_STATUS_PEGISTERS gt 224 lt DIAGNOSTIC_STATUS_REGISTER gt gem Register lt DIAGMOSTIC_PARAMETER_REGISTER gt 0 lt S OIAGNOSTIC_PARAMETER_REGISTER lt IL_ BUS TERMINALS lt IL_BUS gt lt IL_MODULE number 1 gt lt MODULE _T YPE gt DO lt MODULE_TYPE gt lt PO_CHANNELS gt 4 lt PO_CHANNELS gt lt PO_WoOPRDS gt 1 lt PD_WoORDS gt lt PD OUT word 1 gt 0 lt PD_OUT gt gem Data of the first digital Output terminal lt IL_MODULE gt lt IL_MODULE number 2 gt lt MODULE T PE gt DI lt MODULE_TYPE gt lt PO_CHANNELS gt 8 lt PDO_CHANNELS gt lt PO_WoORDS gt 1 lt PD_WoORDS gt lt PD_IN word 1 gt 0 lt PD_IN gt eu lt TL_ MODULE gt lt IL_MODULE number 3 gt lt MODULE TY YPE gt DO lt MODULE_TY PE lt PE_CHANNELS gt 32 lt S POD_CHANNELS gt lt PDO_ WORDS gt 2 lt PD_WoORDS gt lt PO_OUT wor
119. local bus modules Imax lt 2 ADC data sheet The current consumption can differ depending on the individual module The permissible number of devices that can be il Observe the logic current consumption of each device when configuring an Inline station This information is given in every module specific connected therefore depends on the specific station structure Digital Outputs Number Connection method for actuators Nominal output voltage UouT Differential voltage at Inom Nominal current lhom per channel 5 2 PHOENIX CONTACT 4 2 and 3 wire technology 24V DC lt 1V 0 5A 7538 _en_01 Digital Outputs Continued Total current Protection Nominal load Ohmic Lamp Inductive Switching frequency with nominal inductive load Overload response Response with inductive overload Reverse voltage protection against short pulses Resistance to permanently applied reverse voltages Response upon power down Limitation of the voltage induced on circuit interruption Safety equipment Overcurrent shutdown Maximum output current when switched off THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Technical Data and Ordering Data 2A Short circuit overload 12W 12W 12 VA 1 2 H 0 5 Hz 1 2 H maximum Auto restart Output may be damaged Protected against reverse voltages Protected against reverse voltages permissible current 2 A maximum The output follows the supply voltage without delay 30 0 V approximately Inte
120. lt value for the idle state is also zero Holds last state Turn off during a faulted condition default Turn on during a faulted condition Hold last value Set to low limit Set to high limit Set to value determined by the fault value attribute Appendix B Ethernet IP Object Classes Message Types and Services will detail the DOP Class Code 09hex and AOP Class Code OB fault idle values and states PHOENIX CONTACT 4 7 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC 4 2 9 Inline Analog Input Thermocouple and RTD Fault Codes Inline analog inputs thermocouples and RTDs can report diagnostic codes These codes must be read from the produced response or the AIP detailed in Appendix B Ethernet IP Object Classes Message Types and Services A list of these codes in Inline format IL is shown in Table 4 2 Error codes are dependent on the type of module and how that module s format is configured By default error codes are received in the Inline IL format and can be viewed as shown inTable 4 2 If the format has been changed the user must refer to the module specific data sheet to determine what error code has been received Table 4 2 Error messages of analog input modules Code hex 4 2 10 Error History Error history provides access to the last ten errors that have been stored in the bus coupler These errors can be accessed using either the ED
121. lue of the PCP channel size This indicates the number of bytes that are transferred during each Inline scan 5 PCP Module Status Attribute is set to a 1 to indicate an error with the module a zero indicates the module is ok 6 PCP Request This attribute allows the user to send a request to the PCP module The response can be read in attribute 4 The format is as follows Byte 1 Service 1 Read PCP 2 Write PCP 3 Read PDU size Byte 2 Module number Byte 3 Index LSB Byte 4 Index MSB Byte 5 Subindex Byte 6 Length Byte 7toN Data block if necessary The data length is determined by the PCP Index and PCP Subindex of the object to be read written the max data length is variable and can be up to the PDU size for the module typically 64 bytes See 3 PDU Size above 7538_en_01 PHOENIX CONTACT B 31 IL EIP BK DI8 DO4 2TX PAC 7 8 9 10 11 12 13 14 15 B 32 PCP Response PCP Module PCP Write Index PCP Write SubIndex PCP Write Data PCP Read Index PCP Read SubIndex PCP Read Data PCP Request Fragment PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS This attribute allows the user to get responses from PCP modules The format is as follows Successful response Byte 1 Service Byte 2 Status Byte 3 Length Byte4toN Data block if necessary Error response Byte 1 Service Byte 2 Status Byte 3 Error cl
122. ment The write request on the other hand starts with a start fragment and ends if enough data was sent with a last fragment The slave responds with a non fragmented start fragment Start Fragment 7538 en_01 A 2 3 1 Fragment Types Four transfer fragment types are distinguished by the service byte byte 0 of each fragment The types are as follows Start fragment Middle fragment Last fragment Abort error fragment To begin any message a start fragment must be sent The start fragment s eight bytes have the following format Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Service Module number Index low Index high Subindex Length Data block if necessary Data block if necessary PHOENIX CONTACT A 21 IL EIP BK DI8 DO4 2TX PAC THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Byte 0 Service Definition of the Start Fragment Shown in Table A 16 Table A 16 Request Response Bit 7 Bit 6 to5 Bit 4 Bit 3 to 0 A 22 PHOENIX CONTACT Service byte definition of the start fragment Request Response The request response bit is set when the actual Inline PCP module responds to the PCP service that the user requested The amount of time that it takes to process this service depends on the PCP channel size the number of Inline modules and the actual service requested The user can use this bit to know when the service is actually processed by the Inline PCP module For a r
123. mission on port 1 active AOT veto port 1 i Data transmission on port 1 not active ACT2 Yellow Activity on E MN Data transmission on port 2 active Are Yalow port 2 OFF Data transmission on port 2 not active Green Boot Boot loader active firmware started je Waiting for BootP DHCP reply Firmware started successfully 24 V communications supply 7 5 communications power present ili BEL e present Green Usegment _ 24 V segment circuit supply present oe oer 24 V segment circuit supply not present Green U Main woo 24 V I O supply present iN Seen 24 V I O supply not present RY Green Ready oO Ready Connection to a process data client established ee Firmware ready to operate OFF Firmware not active ee status Normal operation Flashing green Device not configured or device configuration not complete or faulty Device in standby mode Flashing red Recoverable error Flashing red Selftest areen 4 2 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Diagnostics Table 4 1 Local status and diagnostic indicators on the bus coupler Color Meaning Description of the LED States Red ON Error preventing communication with the network e g bus offline or double MAC ID Flashing green Device online connections not established Device has finished the double MAC ID test but has not established connections to other n
124. module looses power a reset service with a data value of 1 can be issued to the Inline Interface object 101 gac 65hex or the BK can be power cycled 3 Youcan access a serial module as a PCP Special Function module To do this first disable the module s instance in the Serial Communication Object Then remove the module s serial process and fragment data from the poll using the Serial Communication Object Finally add the PCP special function process and fragment data into the poll using the PCP Special Function Object If the autoconfiguration switch is ON at next power up the BK will erase any custom settings described in the note 3 above The bus coupler can hold up to 64 bytes of incoming and 64 bytes of outgoing data before data will overflow internal buffers 7538 _en_01 PHOENIX CONTACT A 7 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC A 2 1 Method 1 Transfer of Data Using Serial Fragmentation This method defines how serial data is exchanged using process cyclic data The messages that are required to read and write data are encoded into the high speed data stream The protocol is handled using a series of message fragments that are initiated by a client request and then followed up with a server response Each fragment contains 8 bytes Every fragment includes a control byte for a request output data and a status byte for a response input data These fragments were specifically des
125. munications Objects 2 2uus024444snnnnnne nennen nnnnnnn nennen 3 31 3 13 System Operational Guidelines s 404080000n00nnnn nenn nnnnnnennnnnnnnnnnennnnn 3 33 3 13 1 Repeat Packet Interval RPI Settings uss044444004eHR nennen 3 33 3 13 2 Maximum Connection Consideration cccccsseseecceeeeeeeeeeeeeeesanees 3 33 7538 _en_01 PHOENIX CONTACT i onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP DI8 DO4 2TX PAC 4 WV AQMO SU CS anni aaa gene en meer A EEEE 4 1 4 1 Diagnostic and Status Indicators cece cece cece eeeeeeeeeeeaeeeeeeeeeeasaaaeeeeeeeeaaaeeeeeees 4 1 4 2 Available Network Diagnostics ccccceceeeeeee cece ee eee reese rere neers eeaaeeeeesaaeeeeeaas 4 4 4 2 1 Inline Status Word ccceccccceeeeeeceeeeeeeeeaeeeeeseceeeeseaeeeeeeeeeeeessagseeessaaaes 4 4 4 2 2 Major Minor Faulls zeuceneseeeeeeeeeanen 4 4 4 2 3 Bit Meanings for Inline Status Word Byte 0 ccccseeceeeseseeeeeeeeees 4 5 4 2 4 Bit Meanings for Inline Status Word Byte 1 cccccseeeeeeeeseeeeeeeeees 4 5 4 2 5 Latched Diagnostics ccccceccccseeceeseeeeeseeeeseeeeeeeeeeseceeeseeeeseeeeesaaeees 4 6 4 2 6 Inline Control Byle s sun aaa 4 6 4 2 7 O Point Channel Status us044440400Ree nen nnnnnnnn nennen nennen nnnnnnn nen 4 7 4 2 8 Fault Idle State and Value uus0224u0u0onsonnnnnnnnnnnn nennen nennen nennen
126. n Services Service Code Class Service Name B 15 4 Values for COS Mask Object Class Attributes Get_Attribute_Single Set_Attribute_Single Yes Yes Yes 3 Mask Value Contains the actual array of bytes that is ANDed with the produced to determine whether to generate a COS message or not 4 Index Points to specific byte in the COS Mask Value Attribute allowing the Byte Value Attribute to be get or set 5 Byte Value Gets or sets the byte in the COS Mask Array that is indexed by the Index Attribute 6 Add All Mode Automatically generates a COS Mask based on the following bits when the add all attribute is settoa 1 Faults Bits Bits Bit13 Bit12 Bit11 Bitto Bits Bits Inline PCP SF AOPs AlPs DOPs DIPs Status I Os Bit7 Bits Bits Bits Bits Bit2 Biti Bito 7 Add All When set to a 1 generates a COS Mask based on the Add All Mode attribute 8 Enable Device When set to a 1 generates a bit pattern in the COS Mask Array that cause a COS message Supervisor to be generated when any bits in the Device Supervisor Exception Status byte changes Exception state 9 Enable inline Status When setto a 1 generates a bit pattern in the COS Mask Array that cause a COS message to be generated when any bits in the Inline Status Word changes state 10 Enable DIP Faults When set to a 1 generates a bit pattern in the COS Mask Array that cause a COS message to be generated when any DIP Fault
127. ndently configured to latch on a desired state This is accomplished by using attributes 100 and 101 Figure 3 13 shows how actual input or latched data is selected Inline Digital Input Latch Enable Latch Current Digital Input ae Value Default Select Latched or Actual Input Data Figure 3 13 Latched or current data selection Current Digital Input Data Input Table Nework Cable 1436A073 Attribute 100 is used it to enable the latching feature for any specific DIP When set to a logic O default the latching feature is OFF When set to logic 1 the latching feature is ON enabled Attribute 101 determines the latch level of a specific DIP Setting Attribute 101 to a logic O enables the DIP to select a low level latch Setting Attribute 101 to alogic 1 enables the DIP to select a high level latch Enabling the latch and setting the desired latch state must be done by sending an explicit message Resetting the latched condition must be done by setting bit 1 in the Inline Control byte This clear will effect all latched inputs After the latches are reset bit 1 in the Inline Control byte must be set back to 0 to allow for the next latched condition to occur when the control byte is in the consumed data By default the Inline Control byte is not included in the consumed data command The user can add this to the consumed data by issuing an explicit message to the Configuration Object Class
128. nels Module with 1 analog output channel PHOENIX CONTACT 3 7 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC 3 5 4 Process Data Monitoring Monitoring the Ethernet IP connections is executed by the Ethernet IP protocol stack with the help of connection timers If a connection is aborted due to a broken cable or a control system without connection reset the outputs are set back to the pre defined state The state is set either in the DOP digital output point or in the AOP analog output point objects In order to regain control over the outputs the error must be removed An additional process data watchdog is integrated into the bus coupler to avoid uncontrolled setting resetting of the Inline station outputs in the event of an error If outputs of the stations are set ensure access of the controlling process to the station In the event of an error e g network line interrupted or function error in the controlling process the bus coupler can react appropriately via the process data watchdog By default upon delivery the watchdog is deactivated with a 0 ms timeout If the watchdog timeout is set to a value other than O e g 500 ms The first write process activates the process data watchdog The next write process is expected during timeout 500 ms During error free operation the write process is performed during timeout and the watchdog is restarted triggered If there
129. nfiguration Object Class Code 64hex see Appendix B Ethernet IP Object Classes Message Types and Services When adding this status to the poll a bit for each point or channel will be assigned to the input image This will occur before the mapping of the actual point or channel The mapping assignments of these status bits will occur in order of their instances on the local bus I O status bits can be added to the poll through the use of the EDS file Parameters 16 through 20 described in the following paragraphs allow for respective status bits to be added to the poll Selects the number of DIP faults added to the poll response on a point basis Selects the number of DOP faults added to the poll response on a point basis Selects the number of AIP faults added to the poll response on a channel basis Selects the number of AOP faults added to the poll response on a channel basis Selects the number of special function faults added to the poll response on a channel basis 4 2 8 Fault Idle State and Value The bus coupler supports the standard Ethernet IP DOP Digital Output Points AOP Analog Output Points fault or idle states and values These values can be set and read by the use of an explicit message Fault states will only occur during a network error They will not occur after an Inline local error The default value for the AOPs and DOPs is zero Idle states and values will occur when a PLC is taken out of the run state The defau
130. ng Class Instance Editor in the construction software Additionally attributes 100 and 101 could be used to write a custom configuration value to the analog input module Refer to the Thermocouple and RTD module paragraph below to determine how to use attributes 100 and 101 Enabling attribute 101 will override any range settings Once the range is set for the new value the bus coupler will retain that setting in flash memory If the bus coupler is replaced the configuration will need to be redone Appendix B Ethernet IP Object Classes Message Types and Services provides details of the AIP Object Class Code 10gac OAnex range settings Multiplexed analog input Al modules such as the Al8 will appear to have only as many channels as the module has data words The BK has no way of determining how many channels are contained within those words By default the control words for an analog input module are not placed in the poll However with multiplexed modules it is often desirable to change the control word frequently The user can instruct the BK to place these control words into the poll This is done by enabling attribute 102 AIP configuration word in poll of the AIP object Enabling attribute 102 will override both attribute 101 and any range settings 7538_en_01 PHOENIX CONTACT 3 21 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC 3 10 3 Thermocouple and RTD Modules Gen
131. nnnnnannnnnnannnnunnnnnnannnnnannnnnannne 3 9 3 5 6 Ethernet Speed and Configuration cccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeaaes 3 9 3 5 7 Firmware Update via WBM and TFTP cccccsseeeeeseeeeeeeeeeeeeeesnaeees 3 9 3 5 8 Process Data Access via XML cccccsssececesseeceeeesseeeessaeeeeseeeessees 3 10 3 5 9 XML File Structure ccceccccccsseeeceeeeeeeeceeeeeeeeeeeeeeeeeeeeeseeseeeesseeeeeeas 3 11 3 6 TaD Wie een ee 3 15 3 7 AUBLOBIOUTAU0ON anne ee 3 15 3 8 DO8IgUrAtloNn n een 3 15 3 9 The CIP VO Module Capacity uuunuusuusnnennennnnnnnnnnnennnnnnnnnnnn nennen nennnn nennen 3 16 3 10 Configuring the Inline Station 44s 04044nnnnnennnnnnnnnnnnnnnnnnnnnnnnnnnnnnnennn 3 17 3 10 1 BUS COU essen ae ana 3 17 3 10 2 Analog Input Al Modules us 2244400044440RRRnennn en nnnnnn nennen 3 21 3 10 3 Thermocouple and RTD Modules 0222202240002400Renn nennen 3 22 3 10 4 Special Function Modules ccccceeeececeeeeeeeeeeeeeeeneneeeeeeaaeeeesaseees 3 24 3 11 Understanding I O Memory Mapping ccccsseseeccceeeeeeceeeeeeeseeeeeeeeaeeeeessaaaees 3 25 3 11 1 Bus Coupler Mapping cccccsecceccssseeeeeeseeeeeceeeeeeessaeeeeeeeneeessaaees 3 25 3 11 2 Reserving I O Memory for Future System Expansion c000008 3 29 3 12 WO Data Transier cnne see nee 3 30 3121 WO Scan Methods zes nennen na ran engen 3 30 3 12 2 I O Com
132. nt when bit 6 1and bit 5 1 Bit5 1 Designates an abort error fragment when bit 6 1 and bit 5 1 Bits 4 to 0 O Reserved Byte 1 1 Identifies a module communication error Bytes 2 to 7 XX Not used Data is no longer being received in the input table il Once the connection is reestablished the data will continue to be sent Event 11 Events 12 15 A 36 PHOENIX CONTACT In this example the communications error is corrected at this point Read service is completed as described previously in the section Fragmented Error Handling Loss of Communications from the Host to the Bus Coupler If communications is lost between the host controller an the Inline bus coupler during a read or write service the bus coupler will wait for the service to be completed network cable is repaired and acknowledge the completion of the service once the transaction has ended 7538 _en_01 7538 en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Communications Methods A 2 4 Method 4 Transfer PCP Data Using Explicit Messages Explicit messages can be sent as an alternative to using the high speed data channel and PCP fragmentation to send PCP messages For method 4 the PCP Special Function Object Class Code 105gec 69h ex will need to be directly accessed using an explicit message By default this method does not apply to serial modules Refer to Communications Methods on page A 7 The ability to send explicit
133. object The PCP module attribute attribute 8 defaults to the instance value When message 3 is sent the bus coupler will send the data back to the sender The first data byte returned by bus coupler will be the number of bytes to follow These following bytes are the actual data that was sent by the PCP module A 38 PHOENIX CONTACT 7538_en_01 7538 en_01 il onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Communications Methods A 2 4 2 Sending PCP Data When sending PCP data from a PCP module that is not a serial based module the PCP Special Function Object Class Code 105 ge 69hex Must be used Within this object there are two sub methods that can be used to write data explicitly Sub method A involves directly requesting writing the complete PCP services using attributes 6 and 7 Sub method B provides greater efficiency It fixes the module number index and subindex so that only the data is sent for each request attributes 8 9 10 and 11 The following procedure uses sub method B Three explicit messages will be required to write a specific PCP memory area They are 1 Select index 2 Select subindex 3 Write data These messages will have the format shown below and will need to be sent with the required service 1 Build Select Index Message Message is sent using the Set_Attribute_Single service 16 gec Class Code 105gec 69hex POP Special Function Object Instance Select the
134. odes Flashing red One or more connections in timeout state green OFF Device not online Device has not yet finished the double MAC ID test Device has no IP address or is not supplied with voltage Green Boot IP parameters received from BootP DHCP server on BootP request responses in process Stored IP parameters are used Green Diagnos Data transmission within the station active I Flashing Data transmission within the station not active Error Short circuit overload of outputs Dun No short circuit overload of outputs Yellow Output 1to Output active St ven Output 4 Output not active Yellow Input 1 to Input active sate Green Network PY Network status red Status Module is online and has established a connection 7538_en_01 PHOENIX CONTACT 4 3 IL EIP BK DI8 DO4 2TX PAC 4 4 il PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS 4 2 Available Network Diagnostics A detailed explanation of object classes can be found in Appendix B Ethernet IP Object Classes Message Types and Services Diagnostic information is made available through several mechanisms The EDS file allows the user to read the Inline Status word and condition of the standard DIPs DOPs AlPs AOPs and special function modules This Inline Status word and I O point channel status can also be mapped directly to the produced data The final method of retrieval is to explicitly query the attributes from the Con
135. oducts from Phoenix Contact or third party products resulting from disregard of information contained in this manual Explanation of Symbols Used and Signal Words hazards Obey all safety messages that follow this symbol to avoid possible This is the safety alert symbol It is used to alert you to potential personal injury IN injury or death DANGER This indicates a hazardous situation which if not avoided will result in death or serious injury WARNING This indicates a hazardous situation which if not avoided could result in death or serious injury CAUTION This indicates a hazardous situation which if not avoided could result in minor or moderate injury The following types of messages provide information about possible property damage and general information concerning proper operation and ease of use NOTE This symbol and the accompanying text alerts the reader to a situation which may cause damage or malfunction to the device either hardware or software or surrounding property This symbol and the accompanying text provides additional information to the reader It is also used as a reference to other sources of information manuals data sheets literature on the subject matter product etc 7538 _en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC General Terms and Conditions of Use for Technical Documentation Phoenix Contact reserves
136. om THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Table of Contents 1 The Inline Ethernet IP BUS Coupler 002200204002nn0nennennnnnnnno nenn nnene nenn nenn nnnnennnnonnne nennen 1 1 2 AUO e E 2 1 2 1 PANTING sx aO e ee ee 2 1 2 2 BUS Coupler WINA Seesen EEEE 2 3 2 2 1 Connecting the Ethernet IP System ccceccccsseeeeeceeeeeeeeeeseeeesaaaeees 2 3 2 2 2 Connection of Supply Actuators Sensors ccccssseeeeeeseeeeeeeaeeeeees 2 4 3 ANUP OPEO ee ee ee ee ee eee ere 3 1 3 1 Default Upon Delivery Default SettingS ccccseececcssseeeeceseeeeeeceeeeeeeaeeeesseaeees 3 1 3 2 Starting the Firmware ccccceseceeeeceeeeseeeeeeceeeeeeeedeaceaudbeeeeeeeeaseeeeeeeeeaaeeeeeeeaaas 3 1 3 3 Sending BootP Requests cccsssececceeeeceeccegeeeceeueseeeeseeseeeeeeseeeceeeseeeessuseeees 3 2 3 4 Web Based Management WBM sccccsseeceeeeeeeeeceaeeeeeeeeneeeessseeeeesaneeeeseas 3 2 3 5 Structure of the Web Pages c ccsseeeccsseseecceesseeeceeeseeeeceuseeeseeaeeeeseeeeesssseeees 3 4 3 5 1 DIAGNOSICS en nase ae 3 5 3 5 2 SEWICES 202222n0nnnnneen A oe enc ce cca enececccaceescoeeeeescusenenccoaseescusesenses 3 6 3 5 3 Bus Configuration WE W 2000000020002eneonannnannennnnnnnnnnneennu nn eenen 3 7 3 5 4 Process Data Monitoring u 44444444sBRRnn nennen nennen nenne nenne nennen 3 8 3 5 5 Password ProPWOH P 24200 na0000nan0nananna
137. onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS AUTOMATION EtherNe yip gt User Manual UM EN IL EIP BK DI8 DO4 2TX PAC Order No Inline Bus Coupler for Ethernet IP With Eight Digital Inputs and Four Digital Outputs O GD OO GD GD OGD OO dD Lond OGD INSPIRING INNOVATIONS THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS AUTOMATION User Manual Inline Bus Coupler for Ethernet IP With Eight Digital Inputs and Four Digital Outputs 02 2008 Designation UM EN IL EIP BK DI8 DO4 2TX PAC Revision 01 Order No This user manual is valid for Designation Order No IL EIP BK DI8 DO4 2TX PAC 2897758 7538_en_01 PHOENIX CONTACT IL EIP BK DI8 DO4 2TX PAC BB D PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Please Observe the Following Notes In order to ensure the safe use of the product described you have to read and understand this manual The following notes provide information on how to use this manual User Group of This Manual The use of products described in this manual is oriented exclusively to qualified electricians or persons instructed by them who are familiar with applicable standards and other regulations regarding electrical engineering and in particular the relevant safety concepts Phoenix Contact accepts no liability for erroneous handling or damage to pr
138. onnection abort In the connection establishment phase a PCP device acting as a client tries to establish a communication link to another PCP device acting as a server In the process the context conditions the connection parameters that are determined in the communication relationship list of both devices are checked If the context requirements agree then the data transfer phase is initiated Otherwise the connection establishment is cancelled with an error message In the data transfer phase the PCP devices exchange data under the context conditions The connection remains until it is intentionally aborted or a communication error occurs After the data exchange has been completed the connection can be cancelled by a connection abort If a communication error occurs then the connection is automatically aborted Data exchange can then only be carried out after a renewed connection establishment A 1 4 Description of the Communication Services Each PCP service is described in this section together with all of its basic operations The parameters that apply in all basic operations are shown from the beginning and are not always repeated for the individual services Preset number that is set for each command and each message Command Code and Message Code are each given in the description of the basic operations Indicates the number of the subsequent data words each of 2 bytes If there is only a 1 byte parameter in a line then this is
139. ows an example I O data table that contains only eight bytes of input data and eight bytes of output data This I O is shown in an event by event sequence that demonstrates how these eight bytes of I O are updated when reading data using PCP fragmentation The sequence works on this following basic principle Event x Client issues server 8 bytes of output data Event x 1 Server responds by updating 8 bytes of input data Input Data Table Output Data Table Event Sequence for Bytes 0 to 7 Event Sequence for Bytes 0 to 7 Byte gt Byte Byte _____________ gt Byte 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 Event 1 gt 0 1 1 0 1 4 EHEIEIEZEIEIEIEN 1 1 1 1 1 4 lt q Event 2 fhe Fo a me a Event 3 gt 0 1 1 0 1 4 an One e a Oe Oe 2 2 1 1 1 1 1 4 lt q Event 4 a Mn Oe he hn a Event5 0 1 1 0 1 4 CHEIEIEZEIEIEIEN lt Event 6 1 1 1 1 1 4 a Bn a Bh Event 7 gt 0 1 1 0 1 4 DHEIEIEIEIEIEIEN itii lt q Event8 Event9 gt GAANA MEE Event 10 gt 0 1 1 0 1 4 EMEIEIEIEIEIEIEN Usa dies Usea Ubea Uaa can 1 1 1 1 1 4 ESEIEIEIEIEIEIEN 7426A144 Figure A 5 I O events for a read sequence using PCP fragmentation In the following paragraphs the events in Figure A 5 will be explained in detail Table A 21 to Table A 31 demonstrate the order of events when issuing a fragmented read service to a PCP device Each E
140. phoenixcontact com Electrical isolation of Ethernet interface and logic Type of device profile OChex communication adapter Supported CIP connections in total 128 eight typical Explicit signaling Max number of connections 128 eight typical I O signaling Max number of connections 128 eight typical Device configuration possibilities EDS individual software MAC parameter configuration Rate 10 Mbps 100 Mbps automatic Duplex half full automatic Connection of sensors actuators via Ethernet IP 7538 _en_01 2 Installation onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Installation 2 1 Inline Station The Inline product range is a modular automation system Inline modules are joined together to create functional units that meet the requirements of the application See Figure 2 1 shown with the Ethernet IP bus coupler Both communication and power routing is accomplished automatically by the physical interconnections between the I O modules Additional networking options permit the Inline station to branch out to various machine mounted I O modules such as Fieldline Modular or AS i devices For general information on the setup of an Inline station please refer to the IL SYS INST UM E user manual Inline I O station example
141. r or a standard web browser Web based management can be used to access static information e g technical data MAC address or dynamic information e g IP address status information or to change the configuration password protected Calling Web Based Management The IL EIP BK DI8 DO4 2TX PAC web server can be addressed using the IP address if configured correspondingly The bus coupler homepage is accessed by entering the URL http lt P address gt Example http 172 16 113 38 If you cannot access the WBM pages check the connection settings in your browser and deactivate the proxy if set 3 2 PHOENIX CONTACT 7538_en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Startup Operation DEHENIX IL EIP BK DI8 DO4 2TX PAC last update 14 43 46 IL EIP BK DI8 DO4 General Instructions Device Information Device Configuration Inline Station EtherNet ip gt gt Figure 3 1 WBM homepage PHOENIX CONTACT 3 3 7538_en_01 IL EIP BK DI8 DO4 2TX PAC 3 4 PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS 3 5 Structure of the Web Pages The web pages for the Ethernet IP bus coupler are divided into two sections The left hand side has the selection menu with the relevant submenus The right hand side displays the information related to the menu item Static and dynamic information about the bus coupler can be found
142. r Recoverable Fault 7538 _en_01 Bit O CRC Error Bit 1 Peripheral Fault Bit 2 Power Fault Bit 3 Module Change Bit 4 Configuring Error Bit 5 Module Connection Error Bit 6 Outputs Set to Preprogram Ethernet IP Fault State Bit 7 7538 en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Diagnostics 4 2 3 Bit Meanings for Inline Status Word Byte 0 The CRC error bit will be set when a data transmission error occurs due to unwanted interference on the Inline local bus The EDS parameter number 23 Max Retry will allow the module to retransmit the data cycle up to the number of times that the Max Retry parameter is set to If the transmission does not pass the CRC Cyclic Redundancy Check after the Max Retry has expired then the CRC error bit is set The Peripheral Fault bit will be set when any output is shorted or a loss of power to an intelligent segment module The Power Fault bit will be set when any of the power supplies UL Us Um Ethernet IP is in an under voltage condition less than 11 V DC The Module Change bit will be set when the configuration present on the Inline local bus does not match the configuration that was stored in flash during the last configuration cycle The Configuring Error bit will be set when the bus coupler is not able to talk to the first I O module connected to it Possible failures include the bus coupler itself or the first O module connected to
143. rantees regarding quality does not describe any fair marketable quality and does not make any claims as to quality guarantees or guarantees regarding the suitability for a special purpose Phoenix Contact accepts no liability or responsibility for errors or omissions in the content of the technical documentation in particular data sheets installation instructions manuals etc The aforementioned limitations of liability and exemptions from liability do not apply in so far as liability must be assumed e g according to product liability law in cases of premeditation gross negligence on account of loss of life physical injury or damage to health or on account of the violation of important contractual obligations Claims for damages for the violation of important contractual obligations are however limited to contract typical predictable damages provided there is no premeditation or gross negligence or that liability is assumed on account of loss of life physical injury or damage to health This ruling does not imply a change in the burden of proof to the detriment of the user 7538 _en_01 PHOENIX CONTACT IL EIP BK DI8 DO4 2TX PAC Internet Subsidiaries Published by PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Statement of Legal Authority This manual including all illustrations contained herein is copyright protected Use of this manual by any third party is forbidden R
144. rstand the structure of an explicit message before the message is actually integrated into the control program Explicit messages can be sent as an alternative to using fragmentation and the high speed data channel For this method the Serial Communications Object Class Code 106 ga 6Anex Will need to be directly accessed using an explicit message The Serial Communications Object contains attributes used for the sending and receiving of data to or from a serial module When using Method 2 the 8 bytes of fragmentation produced and consumed data as well as the Status and Control words can be removed from the scan For easy access it may be advantageous to allow the Status and Control words to remain in the scan A 2 2 1 Receiving Serial Data Attribute 7 of the Serial Communications Object SCO is the Receive Data parameter Using this attribute along with the status word bit O Receive Buffer is not Empty is required to receive data from a serial module The status word and a control word from the serial module s is automatically added to the Ethernet IP scan by default See the respective serial modules data sheet for more information on specific control functions and status capabilities The user will need to monitor bit 0 When bit O is set there is data present from the serial module At this point the user will send an explicit message with the following parameters Node address service Code 14gec Get_Attribute_Single C
145. se from the slave that includes the first 5 bytes of actual data that was requested from index 5FEOnax This reply is explained as follows Table A 24 Slave to master response to the read request Sun Se u ee a Service Byte 0 91 hex Bit 7 1 This signifies that the fragment is a response Bit6 0 This signifies a start fragment Bits 0 This signifies a start fragment Bit 4 1 This denotes that the response will be sent in fragments Bits 3to0 1 This signifies a read service Status OOhex No errors Length 10hex Informs the master that there will be 16 data bytes in the message DO D4 First 5 bytes of the message bytes D5 D15 to be sent in the following fragments It is important to realize that event 4 is really the start fragment of the slave s message containing the requested data Table A 25 shows the master to slave acknowledgment of the response being received In this acknowledge the service byte reflection is the indication that the 1st response was received Table A 25 Master to slave acknowledgement Service 91 hex 7538 _en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Communications Methods Event 6 Since the reception of the first 5 bytes of data has been acknowledged the slave is ready to send the next fragment This second fragment is a middle fragment with a slightly different format Table A 26 shows the response from the slave that includes the service byte and 7 more bytes of data t
146. splays the process data size of the Inline modules in bits 9 Number of Bytes Displays the process data size of the Inline modules in bytes 11 Scans Per Second Displays the number of local I O scans per second 12 Loop Diagnostic Displays the loop diagnostic count during a connection failure Count 13 Connection Failure Displays the number of the module at the first end of a connection failure Endpoint 1 14 Connection Failure Displays the number of the module at the second end of a connection failure Endpoint 2 15 Latched Inline Sta Displays the latched value of the Inline Status during the last failure See 4 Inline Status tus on page B 21 16 Latched Faulted Contains the number of the first module that was faulted during the last fault Module 1 Bus coupler 17 Latched Connec Displays the number of the module at the first end of a connection failure latched during the tion Failure End last connection failure point 1 7538_en_01 PHOENIX CONTACT B 21 IL EIP BK DI8 DO4 2TX PAC 18 Latched Connec tion Failure End point 2 19 Power Supply Fault 20 Inline Control Byte 21 Error History most recent 30 Error History last saved B 22 PHOENIX CONTACT THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Displays the number of the module at the second end of a connection failure latched during the last connection failure Displays the status of the power supplies connected to the IL
147. t IL_MODULE number 7 gt lt MODULE_TYPE gt DI lt MODULE_TYPE gt lt PD_CHANNELS gt 16 lt PD_CHANNELS gt lt PD_WORDS gt 1 lt PD_WORDS gt lt PD_IN word 1 gt 12288 lt PD_IN gt lt IL_MODULE gt The input word returns the value 12288 21 213 d Inline terminal with two analog inputs only the first channel being active 14970 lt IL_MODULE number 10 gt lt MODULE_TYPE gt Al lt MODULE_TYPE gt lt PD_CHANNELS gt 2 lt PD_CHANNELS gt lt PD_WORDS gt 2 lt PD_WORDS gt 7538_en_01 7538 en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Startup Operation lt PD_IN word 1 gt 14970 lt PD_IN gt lt PD_IN word 2 gt 8 lt PD_IN gt lt PD_OUT word 1 gt 0 lt PD_OUT gt lt PD_OUT word 2 gt 0 lt PD_OUT gt lt IL_MODULE gt PD_OUT This area is used by all terminals with output data The use of bits is identical to the use of PD_IN In the event of an error in the Inline station this is indicated in the diagnostic registers The D LED flashes on the bus coupler The process data is invalid because only internal values are indicated not the values on local bus In order to make sure that only valid data is displayed the diagnostic register must also always be requested The same is valid in the event of a faulty configuration In this case local bus does not run and only internal values can be read in the XML file In the event of a peripheral fault all data is va
148. tation configuration parameters into the flash memory of the bus coupler by changing the default value of parameter Add All I O from a 0 False to a 1 True Depending on the size of the local bus the user may have to wait until the downloading of the new configuration is completed Completion of the download can be determined by observing the state of the MS LED on the bus coupler and the D LEDs on the I O modules While downloading the LEDs will blink Once the download is completed the blinking stops and the new configuration is now stored in the flash memory of the bus coupler 3 18 PHOENIX CONTACT 7538_en_01 7538 en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Startup Operation Plug and Play Mode When in Plug and Play Mode during power up the bus coupler will automatically attempt to start the local I O When disabled the bus coupler will compare the stored I O configuration with the connected I O and start if equal Reboot not required to implement changes Setting the Store Config button will read in the current connected local bus and store it as the I O configuration Disses IL EIP BK DI8 DO4 2TX PAC last update 15 25 57 CONTACT Services Plug amp Play Plug amp Play O i IL EIP BK DI8 DO4 Mode Inputs Only Inputs amp Outputs Disable When in Plug and Play Mode during power up the buscoupler will C General Instructions automatically attempt to start the local I O m z 5 When disabled
149. te bit is clear and a fault condition occurs Default 0 7 Idle State The Idle State determines what action is taken if an idle condition is detected Idle conditions occur if an I O request is received with less than the calculated number of bytes or the Run Idle header is set to idle and the Run Idle header is used Refer to the Configuration Object to determine the size of the I O consumed data An I O request of 0 bytes is typically used to force an idle condition Idle State Action Taken O default Set the output to the stated determined by the Idle Value Leave the output in the current state 8 Idle Value The Fault Value is used to set the output if the Idle State bit is clear and an idle condition occurs Default 0 B 10 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Analog Input Point AIP Object Class Code 10gac OApex B9 Analog Input Point AIP Object Class Code 104ac OAhex The IL EIP BK DI8 DO4 2TX PAC supports variable analog inputs There is a separate instance for each analog channel available on the device B 9 1 AIP Object Class Attributes Attibute Access Name Type ae o UINT Max Object Instance UINT Number of AlPs B 9 2 AIP Object Instance 1 Number of AIPs Attributes Name Tope aeee Get Set Override Range BOOL Get Set AIP Control Data UINT 102 Get Set AIP Control Data in I O BOOL consumed data 1 In consumed data Yes Get_
150. ter to slave sending the 1st middle fragment Service D2 os pa os os o m Service byte 0 2 lax Bit 7 0 This signifies that the fragment is a request Bit 6 0 Designates a middle fragment when bit 6 0 and bit 5 1 Bit5 1 Designates a middle fragment when bit 6 0 and bit 5 1 Bits 4toO 1 These bit count the fragments 1 the 1st middle fragment Bytes 1 to 7 7 More bytes of data 2 sent with first request Event 6 Table A 37 shows the slave to master acknowledgment The service byte reflection indicates that the 1st middle fragment data was received and processed Table A 37 Slave to master acknowledgement of 1st middle fragment Service 21 hex Event 7 Since the reception of the first middle fragment of data has been acknowledged the master is ready to send the next fragment This next fragment is the last fragment Table A 38 shows the last fragment that includes the service byte and 7 more bytes of data that is being sent to index 5FEOpex 16 bytes total This last fragment request is explained as follows Table A 38 Master to slave last fragment foresee be be eee 40ne Service byte 0 A0nex Bit 7 0 This signifies that the fragment is a request Bit 6 1 Designates a last fragment when bit 6 1 and bit 5 O Bit5 0 Designates a last fragment when bit 6 1 and bit5 0 Bits 4 to 0 0 Reserved Bytes 1 to 7 Last 7 bytes of data 7538_en_01 PHOENIX CONTACT A 33 THE ONLINE DIST
151. the Inline module to the IL EIP BK DI8 DO4 2TX PAC Data size is determined by the module 4 OUT Data Data sent from the IL EIP BK DI8 DO4 2TX PAC to the Inline module Data size is determined by the module 5 Data Size Number of bytes of process data used by the module 6 Status Reflects the status of the Special Function Module 0 ok 1 Faulted 7 Data IN I O When set the IN Data is in the I O produced and the OUT data is in the I O consumed This attribute affects the produced and consumed sizes of the IL EIP BK DI8 DO4 2TX PAC and is therefore only settable when the I O connections are not in the established state B 26 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS COS Mask Object Class Code 104 yac 68hex B15 COS Mask Object Class Code 104 gac 68hex The COS Mask Object allows the user control which bits in the produced input data cause a COS message to be generated B 15 1 COS Mask Object Class Attributes atwibute Access neme Type Vie B15 2 COS Mask Object Instance 1 Attributes Atvibute Access Name iye vawe CE Add All Mode WORD na i BOOL T Get Set Enable Device Supervisor BOOL Exception T7 1 1 4 Get Set Enable Special Function BOOL Faults 1 Get Set Enable Special Function IN BOOL Data 7538_en_01 PHOENIX CONTACT B 27 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC B15 3 COS Mask Object Commo
152. the bus coupler using Parameter 1 Use Inline Status in the EDS file 4 Determine whether analog or special function modules are used If used the user has the option to set the Pad I O parameter to a0 or 1 default If not used proceed to step 5 Depending on the I O configuration the analog or special function data may start on an odd byte If this is the case it is possible that this word could span two words in the master scanner By setting the parameter Pad I O to 1 default one byte will be added to the produced consumed size thereby forcing the first word based module to start on an even byte If this word already starts on an even byte and the user sets parameter 2 Pad I O to 1 default no additional bytes will be added to the produced consumed size 5 If future system expansions are anticipated determine if there is a need to reserve digital points bits or analog words in the scan If so determine the number of points bits or words to be reserved then add to this the number of points or words currently being used For more information refer to Section Reserving I O Memory for Future System Expansion on page 3 29 This total number of points or words must be downloaded to the bus coupler Reserving points or words in local I O memory is accomplished by using parameter Reserve Digital Inputs parameter Reserve Digital Outputs parameter Reserve Analog Inputs and parameter Reserve Analog Outputs 6 Enter the new s
153. tion The bus coupler has 3 external power supply connections U logic Us segment and Um main The 7 5 volt internal U communications supply and the 24 V Uana analog supply are derived from the external 24 V U The 24 V U external power supply can be connected to Ethernet IP or another external supply For information on special features of an Inline station such as voltage supply voltage distribution and grounding please refer to the IL SYS INST UM E user manual O1 1 12 1 1 er 21 11 50 21 3 1 agl 4 1 89 pE PE 1240022 1 240022 32 0042 Bo Bo OGY 1355 23 13 558 23 3 3 5043 Bo X 2 Pay 1456 24 1486 24 341 66 44 Och SG Sch 2 3 4 75370008 Figure 2 3 Terminal point assignment of the Inline connector Table 2 2 Terminal point assignment of the power connector 1 NOTE Module is damaged in the event of overload The GND Uy Us potential jumper carries the total current of the main and segment circuits The total current must not exceed the maximum current carrying capacity of the potential jumpers 8 A If in the course of configuring it is found that the 8 A limit is reached at one of the potential jumpers Us Uy and GND a new power terminal must be used The functional earth ground must be connected to the 24 V DC supply functional earth ground connection 2 4 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS
154. tion Consideration on page 3 33 Implicit An implicit connection provides a dedicated path from a producing application to one or more consuming applications and is typically used for real time data transfer Explicit An explicit connection is a generic connection between two devices where a request is sent and an acknowledge is expected It is used for configuration and data transfer 3 12 1 O Scan Methods The Ethernet IP master will scan the bus coupler through the use of several implicit explicit I O scan types The following scan methods are available to the user Cyclic Change of State COS Application triggered 7538 _en_01 7538 en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Startup Operation 3 12 2 I O Communications Objects Bus coupler I O communication objects can be accessed through the use of the explicit messages Listed below are the objects used to transfer I O data for the bus coupler If data needs to be transferred to a device that is not in a scan list a Get or Set explicit message service can be sent to the proper class instance and attribute in question 3 12 2 1 Digital Input Point DIP Object Class Code 08 g O8hex The DIP object models digital inputs in the bus coupler There is a separate instance for each digital input point available on the device Attributes include Value and Status Setting DIP Inputs to Latch Each DIP point can be indepe
155. tion Object Class Code 100gac 64hex This attribute allows the user to select if the 32 bit Run Idle header is in the produced data 00 No default 01 Yes This attribute allows the user to select if the 32 bit Run Idle header is in the consumed data 00 No 01 Yes default Connection State Interpretation oO mew Auto Delete default 2 Auto Reset Deferred Delete This attribute allows the user to select the Plug and Play mode 2 P amp P MODE ENABLED with inputs ONLY 1 P amp P MODE ENABLED with inputs and outputs active 0 P amp P MODE DISABLED the configuration must match last saved configuration This attribute allows the user to delete all timed out connections This attribute allows the user to confirm all peripheral faults This attribute will enable byte padding if required to keep the produced and consumed sizes to 16 bit boundaries 1 Pad byte default 0 No pad byte This attribute allows the user to select the BootP operation 0 If BootP is enabled the module issues BootP requests without interrupt until a valid IP configuration is received default 1 If BootP is enabled the module issues 3 BootP requests If a valid IP configuration is not received it will then use the last stored IP configuration PHOENIX CONTACT B 19 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC B 12 Inline Interface Object Class Code 101gac 65hex The Inline Interfac
156. ttable attribute The Ethernet address shall be assigned by the manufacturer and shall be unique per IEEE 802 3 requirements 7 Interface Type The Interface Type attribute shall indicate the type of physical interface Fixed at a value of 2 Twisted Pair 10 100 base T 10 Interface Label Text String describing the interface Instance 1 IL EIP 10 100 Port X1 Instance 2 IL EIP 10 100 Port X2 7538_en_01 PHOENIX CONTACT B 43 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC B 44 PHOENIX CONTACT 7538_en_01
157. ttributes m ases m in im u 2 Get Max Objectinstance UINT 1 one CIP Port on BK 3 Get Number of Object Instances UINT 8 Get EntryPort UINT 1 only one port supported 9 Get All Ports ARRAY OF STRUCT 00 00 00 00 04 00 02 00 B 18 2 Port Object Instance Attributes Access W neme Tre Tele ea v Ponte um ja GV Pontumber fm je 3 Ge Vo Port Objet Port Object UNT 02 00 20 0200201552401 24 01 Get KA Port Name Mew STRING IL EIP BK C 00 EIP Port B 18 3 Port Object Common Services Service Code Class Ba u Service Name Yes Get Attribute AN _ Attribute_ All 7538_en_01 PHOENIX CONTACT B 39 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS IL EIP BK DI8 DO4 2TX PAC B19 TCP IP Interface Object Class Code 245 gec F5nex B 19 1 TCP IP Interface Object Class Attributes ibe owes ame pe ie B19 2 TCP IP Interface Object Instance Attributes Type Value KT DE EEE B 19 4 Path Padded 5 Get NV Structof 0000 of Structof Configuration Get NV Host Name STRING Configuration specific B 19 3 TCP IP Interface Object Common Services Service Code Class Eulen Service Name Yes Get Attribute AN _ Attribute_ All B 40 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS TCP IP Interface Object Class Code 245 gec F5pex B19 4 Values for TCP IP Interface Object Class Attributes 1 Status Indicates the status of the configuration attribute
158. umber of I O data Transmission rate on the local bus Power supply at U 7 5 V Power supply at Una Power supply at Us Power supply at Um Interfaces Ethernet Type Number Connection format Connection medium Cable impedance Transmission speed Maximum network segment extension Local bus Supply Voltage for U Us Um Recommended cable lengths Continuation Special demands on the voltage supply 7538 en_01 Technical Data 80 mm x 121 mm x 70 mm 270 g with connectors 25 C to 60 C 25 C to 85 C 10 to 95 according to EN 61131 2 70 kPa to 106 kPa up to 3000 m above sea level IP20 according to IEC 60529 Class 3 according to EN 61131 2 IEC 61131 2 Perpendicular to a standard DIN rail The functional earth ground must be connected to the supply connection The contacts are directly connected to the potential jumper and FE springs on the bottom of the housing The terminal is grounded when it is snapped onto a grounded DIN rail Functional earth ground is only used to discharge interference Free of substances which would hinder coating with paint or varnish Resistant to standard solvents Spring cage terminals 0 2 mm to 1 5 mm solid or stranded 24 16 AWG 63 maximum including two devices on the bus coupler 512 bytes maximum 500 kbps or 2 Mbps automatic detection 0 8 A maximum 0 5 A maximum 8 A maximum 8 A maximum Ethernet 10Base T and 100Base TX with auto negotiation and auto
159. utput Point AOP Object Class 0Bpex The AOP object models analog outputs in the Ethernet IP bus coupler There is a separate instance for each analog output point available on the device Attributes include Value Output Range Value Data Type Fault State Idle State Fault Value and Idle Value Accessing Analog and Digital Instances 1 Through 128 The bus coupler automatically supports the following number of instances for the specific object types when accessed using produced consumed data that is mapped to a scanner Digital Inputs 510 instances Digital Outputs 510 instances Analog Inputs 128 instances Analog Outputs 128 instances Inline Special Function Object Class 43hex The Inline special function object gives the user the ability to control and monitor the below listed modules and any other module that does not map to a standard Ethernet IP object Incremental encoder Absolute encoder High Speed counter PCP Special Function Object By default the PCP Special Function Object contains one instance for each PCP module If the bus coupler detects that the modules is designed for serial communications it will also create an instance in the Serial Communications Object An example of a PCP module is AS i master 7538 _en_01 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Startup Operation Serial Communications Object The Serial Communications Object contains one instance for
160. vent should be referenced to the I O data table shown in Figure A 5 A 26 PHOENIX CONTACT 7538_en_01 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Communications Methods Event 1 Table A 21 shows the transmission from a master to slave when the PCP fragmentation is in Idle mode Note that in byte O the service 00 is being sent Table A 21 Master to slave idle request sending a 00 no action service Service OOhex Event 2 Table A 22 shows the slaves response to the idle state by replying with a OOhex no action acknowledge Table A 22 Slave to master idle response 00 NO action acknowledgement Service OOnex Event 3 Table A 23 shows how the start fragment request is sent from the master to the slave to initiate a read This message is built with the format shown below Note that the target index is 5FEQnex Service Byte 0 Ol hax Read Module Number byte 1 07 First PCP module on the Inline station Index Low byte 2 EQnex Low byte of the PCP index to be read Index high byte 3 TF hex High byte of the PCP index to be read Subindex byte 4 OOnex Subindex is zero Length byte 5 OOnex No length requirement Bytes 6 and 7 XX Not used Table A 23 Master to slave read request sending a 01 service 3 Module Index 7538_en_01 PHOENIX CONTACT A 27 IL EIP BK DI8 DO4 2TX PAC Event 4 il Event 5 A 28 PHOENIX CONTACT THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Table A 24 shows the respon

1 The Inline Ethernet/IP Bus Coupler

Contents

Download Pdf Manuals

Related Search

Related Contents