Home

User manual UM EN PROFINET CTRL DEV - Digi-Key

1. Vemendug Besheibung O Z 0 0 a Project ONMBOARD INMPLIT BIT2 BOL VAR GLOBAL Local input IM3 errr jum Libraries oNBOARD BIT3 BOOL VAR GLOBAL Local input IN4 Data Types __ ONBOARD_INPUT_BIT4 BOOL VAR GLOBAL Lacal input INS sys flag types OMBOARD INPLIT BITS BOOL VAR GLOBAL input ING 52 424 Logical POLs oNBOARD INPUT BITE BOOL VAR GLOBAL Local input E Data Acknowlegde ONBOARD INPLUT_BITF BOOL VAR GLOBAL Lacal input INS Data AcknowlegdeT oNBOARD OLITPLIT BOOL VAR GLOBAL Local output OLIT1 Data Acknowlegdev ONBOARD OLITPLIT BIT1 VAR GLOBAL Laocal output OLIT2 1 Data Acknowlegde OMBOARD OUTPLIT BOOL VAR GLOBAL output OUTS v 5 18 Main DAY VAR GLOBAL MainT INT ime month Maini RIC sCOBAL System time year a Main HE PHD 51541 PLC RLIM BOOL GLOBAL Status af the higher level control system Physical Hardware PND S191 VALID DATA BOOL VAR GLOBAL Controller has established the connection STD _ PND 5151 OLITPLIT STAT BOOL GLOBAL status of the higher level control system Ewa STD RES ILCTZO 357 PhD 5151 INPUT STATUS BOOL VAR GLOBAL status of the higher level control system EXT cp Tasks _ PND 5151 DATA
2. PMIO DATA VALID FORCE FAILSAFE OQ PMIO APPL FORCE FAILSAFE PNArr ES L MaincMain Figure 4 31 Inserting and linking variables e Select the 0 array in the byte array by writing the field O after the PNArr Out variable e Then compile the project and save it 4 20 PHOENIX CONTACT 8037 en OO Description of a typical application devices several networks 4 2 Online configuration 4 2 1 Preparing the PC for communication e For configuration and parameterization assign an appropriate IP address for your PC within the 192 168 0 x address area In this example the PC receives the address 192 168 0 10 Internet Protocol TCP IP Properties General fou can get P settings assigned automatically if your network supports this capability you need to ask your network administrator for the appropriate IP settings C5 Obtain an IP address automatically gt Use the following address IP address 168 0 10 Subnet mask 256 55 255 0 gt Use the following ONS server addresses Preferred DNS server Alternate DNS server D 51 Figure 4 32 Assigning an IP address e Select the network card of your PC that is to be used for communication in the Tools PROFINET menu of PC Worx PROFINET
3. GS GRO AO OO 4 Figure 3 4 Typical application all devices in one network In this example a project is created on the lower level controller ILC 170 PN by requesting the status variables of PROFINET communication 5151 For this purpose a function block is created in structured text that sets the value true on the ONBOARD OUTPUT BITO system variable The LED is ON when the ILC 330 PN sends the value 1 In the example a function block is used for logical ANDing The ILC170ETH1 0 PNIO DATA VALID andl ILC170ETH 0 PNIO APPL RUN variables both system variables map the status of the inputs to which the PNIO FORCE FAILSAFE system variable is connected The PNIO DATA VALID system variable indicates for each PROFINET IO device whether the connection to this PROFINET IO device was established successfully Only if this bit is set does the PROFINET IO device supply valid data and all other process values are active A negated result is linked to the PNIO FORCE FAILSAFE variable The PROFINET system is stable when the system variable PNIO FORCE FAILSAFE 0 All outputs are set according to the process data If PNIO FORCE FAILSAFE 1 atleast one PNIO DATA VALID variable set to 0 the safe state 0 is output for all PROFINET device outputs 3 4 PHOENIX CONTACT 8037 en 00 Description of a typical appl
4. Contact GQ AXL CPx CT ELF FZ FET R Insert Device into Bus Structure FLS FF IL IL 2MBD ILE Delete Device Import Device Ctrl I Copy Device Display Data Sheet Say ILC Tax Import GSD File 34 PLC Create new INTERBUS Device Description BN ILC 130 ETH Rev gt 0173 ILC 130 ETH Rev gt 0173 Create Catalog EH ILC 150 ETH Rew gt 017 2 Import Catalog BH ILC 150 ETH Rew gt 0173 BN ILC 150 GSM GPRS Aew gt BN ILC 150 GSM GPRS Aew gt BN ILC 155 ETH Rew gt 0172 ILC 155 ETH gt 01 3 View as Grid Ctrl G ILC 155 ETH Rev gt 01 3 Catalog Representation Ctrl E FILE 170 ETH 2T DEVICE Figure 3 17 Inserting the ILC 170 ETH 2TX as a device in the bus structure 8037 en 00 PHOENIXCONTACT 3 13 UM CTRL DEV The PROFINET device inserted will be displayed in the Bus Structure workspace The IP address is created depending on the IO controller address ILC330 Controller ILC 170 ETH 2TX DEVICE ilc 170 device32 192 168 0 3 PROFINET Settings c NE ILC 330 PN 192 168 0 2 GR Resource STD RES ILC330PN Functional description Functional description PLC Revision 22 StationName DeviceName S o ModueEqupmentID Default Gateway Reductionratioinput 2 Reductionratiooutput Jiems C
5. Mair Main a Physical Hardware a g STD 40 B STD RES RFCAT PN a g Tasks 5 0 STD TSK DEFAULT 5 Main Main hi ain Global Variables IL Configuration gt ES Data Figure 4 18 Creating the variables 8037 en OO PHOENIX CONTACT 4 11 UM EN CTRL DEV e Afterwards insert the created function block in the Main worksheet using drag amp drop Project Tree Window 2 Edit Wizard 4 F El S E Project Group pu Data nos doe all FUs and gt FL Mele wledge Description Logical POUs xti Acknowledge B Data Acknowledge 1 u DELETE Deletes Substring 3 i Data AcknowledgeT 3 DERIVAT Differentiaton with Respect to Time Data Acknowledge T DIGITAL Reads the digital 1 0 channel Data Acknowledge Tr DIGITAL DUT Sets the digital 1 0 channel Main DINT BCD Converts DINT to BCD DWORD i Maint DINT TO BCD Converts DINT to BCD DwW RD 1 DINT TO BODL Converts DINT to BDOL 5 Main i DINT TO BUF al Physical Hardware F DINT TO BYTE Converts DINT to BODL 51D CF PC 40 TO D BED Converts DINT to BCD DWORD z x URBS RM a au F DINT TO D ORD Converts DINT ta D VDORD gt Ji DINT TD INT Converts DINT ta INT Figure 4 19 Inserting the function block into the worksheet e Compile the project and save it 4 12 PHOENIX C
6. EA Module Settings 19191 process Data Data sheet e Replace the EA512 I O module with the EA256 I O module of the RFC As a device the lower level ILC 170 ETH 2TX can transmit up to 256 bytes e Delete the EA512 I O module right click e Drag the EA256 I O module in the bus structure left click The RFC 470 PN 3TX is now available as PROFINET IO device in the ILC330 Controller PC WorX project PHOENIX CONTACT 4 17 8037 en 00 UM CTRL DEV e Switch to the IEC programming and open the Main worksheet e Add the mapped function blocks e Create the following variables at the links as specified e Negate the output at the AND block PNIO_DATA_VALID D PNIO FORCE FAILSAFE PNIO APPL RUN NOT BOOL TO BYTE PNIO FORCE FAILSAFE gt Main Main Figure 4 27 Adding function blocks e Save the modified main program 4 18 PHOENIX CONTACT 8037 en 00 Description of a typical application devices several networks Assigning process data For the system variables for displaying the status of a PROFINET IO device the process data is generated automatically e Switch to the process data assignment workspace e In the top left window Symbols Variables select the program here Main Main e Highlight the PROFINET device in the top right window e Highlight the DATA VALID variable in the bottom right window e Highlight the DATA VALID variable in the botto
7. uU dus E Lo M da ue OR 4 1 4 1 ipi es COMMOUPANOMS ENTE ETE OE 4 3 4 1 1 S 4 3 4 1 2 RFC 470 PN 3TX higher level lower level project 4 8 4 1 3 idet 4 14 4 2 Online connguration 2 EE 4 02 4 2 1 Preparing the PC for communication 4 22 4 2 2 Configuring the ILC 170 2 4 23 4 2 3 Configuring the RFC 470 4 25 4 2 4 Contiguring the ILC 330 PIN 3 ioc Id ae Puta 4 26 4 2 5 Observe startup behavior 4 30 8037 en 00 PHOENIX CONTACT i UM EN CTRL DEV 4 2 6 Checking the program start of the higher level project 4 32 4 2 7 Checking the program start of the lower level project 4 33 ii PHOENIX CONTACT 8037 en 00 PROFINET IO controller device functions 1 PROFINET IO controller device functions Available PROFINET documents 8037 en 00 The PROFINET IO controller device functions UM EN PROFINET CTRL DEV user manual provides an overview of the PROFINET communication system with device functions This system description provides support when installing starting up or operating a PROFINET device system Examples show you how to program IO device diagnostics
8. 0 ILC 170 ETH 2TX DEVICE 1EA256 ILC 170 ETH 2TX DEVICE 3 IMTERBUS 0 0 240140 1 Unconnected J Festo 1 1 Phoenix Contact Universal Monitoring Time Outputs ms 1 Operation in case of configuration differences Drive BF Node ID PROFINET Settings PROFINET Stationnames A Bus interfaces Data sheet Figure 3 18 The ILC 170 ETH 2TX integrated as PROFINET device in the bus structure The process data of the PROFINET device will be displayed in the Device Details workspace of the Process Data tab 1 330 Controller 1 EA256 ILC 170 ETH 2TX DEVICE Process NE 330 PN 192 168 0 2 S R Resource Process Data Byte Bit IQ Function Text Terminal equi R STD RES ILC330PN 1 EE PROFINET D i c Hl ILC 170 ETH 2TX DEVICE ilc 170 device32 192 168 0 3 lt gt 0 170 ETH 2TX DEVICE 1 EA256 ILC 170 ETH 2TX DEVICE Ei gl INTERBUS 0 0 GR si mncaoiao 124 Unconnected Module Settings 3 Process Data 2 Data sheet Figure 3 19 Process data of the PROFINET device 3 14 PHOENIX CONTACT 8037_en_00 Description of a typical application all devices one network e Switch to the IEC programming and open the Main worksheet e Add the mapped function blocks e Negate the output at the AND block Main Main
9. UN Fe 7 lt gt gt Figure 3 13 Inserting the function block into the worksheet e Compile the project and save it e Close the project 3 10 PHOENIX CONTACT 8037 en 00 Description of a typical application all devices one network 3 3 2 Higher level project Select the New Project command from the File menu to create a new project using a template The tree structure and the selection of the control system are now prepared e Select the ILC 330 PN Rev gt 01 4 6F 3 50 control system and confirm your selection with OK New Project CP xx CPX FC ILC ox ILC 2 ILC Sex REC 4 lt gt Se Project Wizard ILC 330 ETH Rev gt 01 4 BF 2 00 ILE 330 ETH Rev ILC 330 PM Rew gt L1 A4 BF 43 50 L1 A4 BF 43 00 ILC 350 ETH Bev gt O1 4 6F ERI Lr A4 BF 72 0 h Figure 3 14 Selecting the controller e Select the File Save Project As Zip Project As command e Enter a project name here ILC330 Controller and save the project Save Zip project as OP QE POExample mut File name ILC330 Controller met File typa Project Files rmt hd zip Options 21 Frontend Code Fw Libranes 21 Pagelayouts Figure 3 15 Save project 8037 en 00 PHOENIX CONTACT 3 11 UM CTRL DEV PC WORX ILC330 Controller Project Build Online Extras 2 D
10. 8 ONBOARD OUTPUT BITO BOOL VSR GLOBAL Local output OLIT1 Dolce FIO MEDUE ONBOARD OUTPUT BIT1 BOOL VAR GLOBAL Local output OLIT2 i Data Acknowlegde oMBOARD 2 VAR GLOBAL output GUTS 5 18 Main _ VAR GLOBAL MainT INT ime month Main System time year E ij Main PMD 5151 PLC RLIM BOOL GLOBAL of the higher level control system Sex hysical Hardware PND 151 vaLiD DATA BOOL VAR GLOBAL 10 Controller has established the connection s STD_CNF PND 5451 ourPUT STAT BOOL VAR GLOBAL status of the higher level control system STD RES ILCTZO 35 _ PhD 5154 IMPUT sTATUS BOOL VAR GLOBAL status of the higher level control system Tasks _ PD S151 DATA LENGTH WORD VAR GLOBAL Process data length 3TD TSK DEFAULT E151 OUTPUTS lO 256 VAR GLOBAL Output process data sot 8 10 Main Main PND 5451 INPUTS PND IO 258 YAR GLOBAL Input process data Main IB DEVICE BOL VAR GLOBAL Interbus device configuration activated Se Global Variables _ B PARAM READY VAR GLOBAL linterbus device configuration completed Configuration _ PARAM ERROR BOOL VAR GLOBAL interbus device configuration error TIT gt gt
11. Eg Data Global Var Figure 4 9 Selecting the process data 4 6 PHOENIX CONTACT 8037 en 00 Description of a typical application devices several networks e Afterwards insert the created function block in the Main worksheet using drag amp drop Project Tree Window 470 Sy Project c Dokumente und Einstellungen 1 Libraries B 69 Data Types sys flag types Logical POUS Data Acknowlegde i Data amp cknowleqdeT Data Acknowlegdev Data Acknowlegde 5 10 Main MainT Main Ei M ain Ez Physical Hardware 5 9 STD eCLR 4 gt 9 5 Data Acknowlegde Acknowlegde 4 gt E ain Figure 4 10 e Compile the project and save it e Close the project 8037 en 00 2 Edit wizard x Group all and FBR lt gt w Mame Ju Jr CTUD O BCD TO DINT BCD TO INT 48D BCD TO SINT Jr Data Acknowlegde DELETE DERIVAT JE DIGITAL IN JE DIGITAL OUT TO B JDIMT TO BCD THE TO nnn Inserting the function block into the worksheet PHOENIX CONTACT 4 7 UM CTRL DEV 4 1 2 RFC 470 PN 3TX higher level lower level project e Select the New Project command from the File menu to create a new project using a template The tree structure and the selection of the control system are now prepared
12. FORCE FAILSAFE 16400 MaircMain Figure 4 50 Program status in Stop Mode PHOENIX CONTACT 4 31 UM CTRL DEV 4 32 4 2 7 Checking the program start of the lower level project The behavior described before can also be observed in the ILC170 Device project Please note that the RFC 470 PN 3TX is operating as a master and as a slave at the same time It acts as the link between the ILC 330 PN controller and the ILC 170 2TX controller e Please open the lower level project of the ILC 170 ETH 2TX e Then open the Data Acknowledge POU and activate the Debug mode The following screen appears 1 FALSE ONBOARD OUTPUT BITO FALSE 2 3 16 00 lif BYTE TO INT PND 5151 5 0 1 4 5 then 6 FALSE ONBOARD OUTPUT BITO TRUE 7 8 end Lf 9 3 Variable Value Default value Type DEE a ae ID 256 STD_CNF STD_R 0 46800 BYTE STD CNF STD z 1 Td BYTE STD CNF STD R 9 2 16 00 STD CNF STD 3 16 00 BYTE STD CNF STD s Watch 4 Watch 2 Watch 3 Watch 4 Figure 4 51 Program status active The value 1 is in array 0 of the PND 5151 INPUTS The ONBOARD OUTPUT BITO variable is TRUE and the Q1 LED on the ILC 170 2TX is ON Now switch the PROFINET IO controller ILC 330 PN and or RFC 470 PN STX to stop Communications is terminated and the value i
13. i SNMP agent IO device status PROFINET Device Settings deactivated activated deactivated Oftline Settings Communication amp g CPU Service Editor 3 Bus interfaces Data sheet Figure 4 41 Extended Settings Device function activated e Click on Transmit e Inthe Settings Communication Path dialog confirm with OK the suggested address or the one you have selected for your application Settings Communication Path Ethernet 192 168 0 7 v Figure 4 42 Setting the communication path Successful execution of the service will be displayed in the status window Device Details LC 170 ETH 2TX 192 168 0 7 Extended Settings Network Settings S Ethernet SNMP agent IO device status 5 PROFINET Device Settings activated v amp Settings Extended Settings 46 Communication amp CPU Service Editor 4 Bus interfaces Data sheet Figure 4 43 Status window To transfer the network settings you have to reset the IO controller 8037 en 00 8037 00 Description of a typical application devices in several networks e Select the Ethernet item in the Device Details window under Network Settings The device name in the higher level project ILC 170 ETH device must match the device name of the lower level project ILC 170 ETH e Inthe Activate Network Settings area cl
14. 1 1 User group of the manual Use this user manual if your are responsible for programming user programs or configuring starting up and servicing automation systems 1 2 Basic knowledge required The following knowledge is required to understand the user manual General knowledge with regard to automation technology Knowledge on how to use computers or equipment similar to a PC e g programming devices under the Windows operating system Knowledge of how to use PC WorX Good knowledge of the PROFINET IO communication method 1 3 Additional PROFINET documentation The PROFINET documentation is modular providing you with optimum information PROFINET basics user manual UM EN PROFINET SYS The manual describes PROFINET system basics This includes PROFINET development PROFINET versions PROFINET properties PROFINET installation and startup PROFINET and wireless PHOENIX CONTACT 1 1 UM CTRL DEV Quick start guides Installing and starting up the starterkit 3 0 quick start guide UM QS EN PROFINET STARTERKIT 3 0 Configuring INTERBUS devices in a PROFINET IO network using the example of STEP 7 UM QS EN PROFINET PROXY IB Device specific data sheets The data sheets describe the specific properties of PROFINET IO devices These include Function description Ordering data and technical data Local diagnostic and status indicators Pi
15. 256 data type as VAR EXTERNAL Type Usage Description Ei Default _ Philo FORCE FAILSAFE BOOL VAR EXTER All PROFINET devices are prompted to set their _ APPL RUN BOOL VAR EXTER DATA VALID BOOL VAR EXTER _ PNArr out 10 256 VAR EXTER 1 iR Main Main Figure 4 29 Creating the PNArr_Out variable 8037_en_00 PHOENIX CONTACT 4 19 UM CTRL DEV e Connect the PNArr Out variable to the 1256 process data item of the 470 device The total available data width of 256 bytes was selected in this example You can change it later in the online configuration Symbols Variables ILC330 Controller STD ARM 40 ILC 330 PN 192 168 1 2 Resource um STD RES ILC330PN System Variables 2 838 PROFINET g STD TSK DEFAULT RFC 470 3TX DEVICE RFC470PN1 192 168 1 5 1 Main Main RFC 470 PN 3TX DEVICE Default 1 EA256 RFC 470 PN 3TX DEVICE Auto Ei gi INTERBUS 0 0 BR si 5n240140 Unconnected SymboljVariable Data Type Process Data Item PNArr Out PND IO 256 EVICE 2 Select all Ctrl 4 Search Ctrl F Fiter v Color coded view Disconnect Create Variable Figure 4 30 Connecting the PNArr Out variable to the process data e Switch to IEC programming and link the variables as shown in the figure below
16. E b Cam ao A BOTS S E Project 28 Libraries Sy Data Types sys_flag_types Sy Logical POUs B Main 1 MainT E Main Physical Hardware mw STD ARM L 40 E STD RES ILC330PN 5 88 Tasks STD TSK DEFAULT lobal Variables Configuration uaa The following window opens Sennen O IP PROFINET Configuration is checked Resource is checked STD_RES INTERBUS is checked ILC 330 PN 0 0 0 Group lt all FUs and gt E Name E 5 ACOS ADD dEADD amp DDR TO ID AND E AR MGT Jr ASIN E AsL E ASR dr ATAN B_BCD_TO_DINT B_BCD_TO_INT B_BCD_TO_SINT BCD_TO_DINT BIT_TEST BOOL TO BYTE BOOL_TO_DINT BOOL TO DwORD 3 12 Figure 3 6 Start screen 8037 00 Description of a typical application all devices one network e First integrate the ILC 170 ETH 2TX as a PROFINET IO device into the bus structure e Change to the bus structure To do this click on the Bus Structure icon in the toolbar e Insert the ILC 170 ETH 2TX as a device into the bus structure right click s Bus Structure ILC330 Controller NE ILC 330 PM 122 168 1 2 E F Resource R STD RES ILC330PN ix PROFIMET 5 9 INTERBUS 0 0 simncapian 1 24 Unconnected 2 Device Catalo Sy
17. Figure 4 34 Selecting Extras BootP SNMP TFTP Configuration e Activate the BootP server active checkbox BootP Settings Figure 4 35 Activate BootP server e Switch to the bus configuration workspace see Figure 4 37 e Select the controller node e Select the IP Settings tab in the Device Details window e Enter the MAC address of the controller It is printed on the device and starts with 00 0 45 4 22 8037 00 Description of a typical application devices several networks ln 7805A012 Figure 4 36 Printed MAC address on the ILC 150 ETH controller 5 Bus Structure q E Device Details 4 F E diia ILC170 Device ILC 170 ETH 2TX 182 168 0 7 VP Settings NE ILC 170 ETH 2 192 168 0 7 SFR Resource Fe STD RES ILC170_35 gfe INTERBUS 0 0 24 Unconnected vendor Phoenix Contact 1 Designation 1 Functional description 7 Inline Controller for Ethernet Networks With 8 Devcetyos Devicefamiy 0 O 1 Ordernumber 2 Revision is E NN pekeName 5 5 Device Catalog F Festo Phoenix Contact Universal Module Equipment ID o Address 00 0 45 18 8 8 Default Gateway IP Settings EJ Extended Settings Communication zn CPU Service Editor 4 Businterfac 4 gt All Figure 4 37 Entering the IP address e Per
18. 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 PHOENIX CONTACT UM CTRL DEV Internet Statement of legal authority This manual including all illustrations contained herein is copyright protected Use of this manual by any third party is forbidden Reproduction 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 an
19. e Select the RFC 470 PN 3TX Rev gt 00 4 6F 3 50 control system and confirm your selection with Mew Project CPx FC xxx ILC 1 ILC 2xx ILC RFC das 5 MAX eh 5 j j RFC 450 ETH IB Rev AFC 450 ETH IB Rev gt 3174 60 5 00 gt 367 4 6D 5 06 E RFC 470 PN 3T Rev fall EFIE REI MET gt 004 BF 73 00 gt 0024 43 50 RFC 4705 3 Rev gt O04 6F 73 50 Figure 4 11 Selecting the controller e Select the File Save Project As Zip Project As command e Enter a project name here RFC470_Controller_Device and save the project Save Zip project as Trait File 470 Controller Device mvt File type Project Files nwt zip Options 1 Lser Libraries 1 Frontend Code Figure 4 12 Save project 4 8 PHOENIX CONTACT 8037_en_00 Description of a typical application devices in several networks The following window opens 9 PC WORX RFC470 Controller Device Edt Project Build Online Extras 2 be L3 A Window cc NE Eas Project c Dokumente und Einstellungen pyr C Libraries 5 83 Data Types i sys flag types 4 Logical POUs 4 1 MainT Main Main 5 88 Physical Hardware Ew STD CNF IPC 40 STD RES RFC470PN 5 88 Tasks m STD TSK DEFAULT 8 0 Main Main Main h Global Variables IO Config
20. project ILC170 Device e Establish an Ethernet connection between your PC and the controller e Inthe PC WorX menu bar select the Extras BootP SNMP TFTP Configuration menu Pagelavaut Editor Create OPC Visualization File Reset DA Addresses 8 Bus Structure PROFINET Configuration BootP i SNMPITFTP Configuration Check Source Storages Shortcuts Options Figure 3 27 Selecting Extras BootP SNMP TFTP Configuration e Activate the BootP server active checkbox BootP Settings Figure 3 28 Activate BootP server e Switch to the bus configuration workspace see Figure 3 30 e Select the controller node e Select the IP Settings tab in the Device Details window e Enter the MAC address of the controller It is printed on the device and starts with 00 A0 45 8037 en 00 PHOENIX CONTACT 3 19 UM CTRL DEV SACO 5 Seay NA NA N OA Figure 3 29 2 Bus Structure ILC170 Device Nl ILC 170 ETH 27x 192 168 0 7 FR Resource R STD RES ILC170_35 Ae INTERBUS 0 0 ES Unconnected 7805A012 Printed MAC address on the ILC 150 ETH controller Device Details ILC 170 ETH 2TX 192 168 0 7 MP Settings Phoenix Contact ILC 170 ETH 2TX ___ Revision 01 3 50 Station Name Device Name Module Equipment ID DNS PROFINET Device Name ILC170ETH1 Phoenix Contact 9 Universal 0
21. select activated in the pull down menu 5 Device Details A m ILC 170 ETH zTX 192 168 0 7 Extended Settings Network Settings 3 25 Ethernet T SNMP agent 25 IO device status 3 PROFINET Device deactivated activated deactivated Offline IP Settings E Extended Settings a communication 8 CPU Service Editor f Bus interfaces 2 Data sheet Figure 3 32 Device function activated e Click on Transmit e Inthe Settings Communication Path dialog confirm with OK the suggested address or the one you have selected for your application Settings Communication Path Ethernet 192 168 0 7 gt Cancel Figure 3 33 Setting the communication path PHOENIX CONTACT 3 21 8037_en_00 UM CTRL DEV 3 22 PHOENIX CONTACT Successful execution of the service will be displayed in the status window 2 Device Details T 170 ETH 2TX 192 168 0 7 Extended Settings Network Settings Ethernet SNMP agent 5 IO device status PROFINET Device Settings activated amp Settings Extended Settings 46 Communication CPU Service Editor Bus interfaces S Data sheet Figure 3 34 Status window To transfer the network settings you have to reset the IO controller e Select the Ethernet item in the Device Detail
22. then is communication for configuration of the ILC 170 ETH 2T X possible In this case the modification was done via the LAN1 interface 192 168 0 x subnet 4 2 4 Configuring the ILC 330 PN Assigning IP settings e When assigning the IP settings for the ILC 330 PN please proceed in the same way as for the ILC 170 ETH 2TX see Configuring the ILC 170 ETH 2TX on page 4 22 e Open the ILC330 Controller project Please not the following modifications Connect the network cable of your PC to the switch Now you have established a connection from the PC to the ILC 330 PN A BootP server is active Enter the MAC address of the ILC 330 PN controller Assign the IP address 192 168 1 2 Switching on the IO PROFINET device function The following applies to the devices ILC 170 330 350 370 390 PN RFC 470 By default upon delivery the PROFINET device function is switched off for every controller To switch it on start your existing project in the example here ILC170 Device in PC WorX and activate the PROFINET device function as follows e Switch to the Extended Settings tab e Select the IO device status item in the device details under Network Settings e Under Settings select activated in the pull down menu PHOENIX CONTACT 4 25 UM CTRL DEV 4 26 PHOENIX CONTACT Device Details ILC 170 ETH 2TX 192 168 0 7 Extended Settings CX Network Settings Ethernet
23. variable Data Type Process Data Item Device Process Data Item I Q Data Type Out IO 256 Ctrl F Search Filter v Color coded view Connect Disconnect Ctrl Create Variable Ctrl E Search Variable tri R g 116 Figure 3 23 Connecting the PNArr Out variable to the process data 3 16 PHOENIX CONTACT 8037 en 00 Description of a typical application all devices one network Switch to IEC programming and link the variables as shown in the figure below e negation to the output of the AND block The PNIO FORCE FAILSAFE system variable is used at the output of the AND block and the input of the NOT block PNMIO DATA VALID o PNIO FORCE FAILSAFE ILC1 0ETH1 0 PMIO APPL quc gn FPNIO FORCE FAILSAFE PNArr Jp Mankan Figure 3 24 Inserting and linking variables Select the 0 array in the byte array by writing the field 0 after the PNArr Out variable Then compile the project and save it PHOENIX CONTACT 3 17 8037 en 00 UM CTRL DEV 3 4 A Online configuration 3 4 1 Preparing the PC for communication For configuration and parameterization assign an appropriate IP address for your PC within the 192 168 0 x address area In this example the PC receives the address 192 168 0 10 Inter
24. 0 A0 45 18 8A A8 IP Address __ amp Settings Extended Settings 46 Communication zB CPU Service Editor 3 Bus interfaci 4 gt Figure 3 30 Entering the IP address e Perform a cold restart for the controller e Todo this switch the supply voltage off and then on again after around 2 seconds The controller is assigned the IP address which is specified in the project for the controller here 192 168 0 7 The following message appears in the message window in the Bus Configurator tab B Configured device ILCI7D ETHl queries for its IP parameters via BontP The device ILCI7D ETHl received its IF parameters IP Address 192 168 0 7 2u bnet Mask 255 255 z255 Default Gateway via BootP FDT J 4 Warmin gs 4 PLC Errors j WMulti User amp Bus Configurator 2 Message Winde Figure 3 31 Message window The IP address will now be permanently stored on the controller Flash memory 3 20 PHOENIX CONTACT 8037 en 00 Description of a typical application all devices one network Switching on the PROFINET IO device function The following applies to the devices ILC 170 330 350 370 390 PN RFC 470 PN 3TX By default upon delivery the PROFINET IO device function is switched off for every controller e Switch to the Extended Settings tab e Select the IO device status item in the device details under Network Settings e Under Settings
25. 5 0 PROFINET device name RFC470PN1 To use the PROFINET device functions the following conditions apply for the HFC470 Device project RFC 470 settings as a PROFINET IO controller IP address 192 168 0 5 Subnet mask 255 255 255 0 PROFINET device name RFC470PN1 ILC 170 ETH 2TX settings as PROFINET IO device IP address 192 168 0 7 Subnet mask 255 255 255 0 PROFINET device name ILC170ETH1 Please make sure that the same PROFINET device name of the RFC 470 PN 3TX IO controller here RFC470PN1 is used in the lower level project as in the higher level project for the 470 PN 3TX as a device here RFC140PN1 Starting up the controller is the easiest way to check whether controller is correctly parameterized I O devices have the right name There are double names or double IP addresses in the system Make sure that the controller has the IP address that was set in the project Start the project control dialog via the menu bar If the message Timeout appears after 10 seconds the project and device addresses do not match It is also possible that the IP address of the computer has not been set correctly 8037 en OO PHOENIX CONTACT 4 29 UM EN CTRL DEV The controller can be reset from the project control dialog The existing project will be deleted Start the download and perform a cold reset Afterwards the BF LEDs must go out on all devices To acces
26. 8037 en 00 Description of a typical application all devices one network The following window opens 4 PC WORX ILC170 Device Edit View Project Build Online Extras Coma lt Y 4 f Project Group Libraries cFavontes Sy Data Types sys flag types 2 39 Logical POUs Addition B 2 Main Bitwise AND 11 Counter Down Main Counter Up Main Counter Up Down I Hardware Division a STD CNF eCLR Equal cow STD RES ILC170 35 EF Falling Edge Detection 5 89 Tasks Greater Than Equal gt m STD_TSK DEFAULT Greater Than gt Less Than Equal lt Less Than lt 2 Disce Modulo Division Assigns Value Multiplication Not Equal lt gt Complement Bitwise OR Name Description cow IP PROFINET Configuration checked Resource is checked STD RES INTERBUS is checked ILC 170 ETH 2 0 0 0 4 P1 Build A Errors Warnings Infos A PLC Errors Print Multi User Bus Configurator Figure 3 7 PC WorX start screen e Right click on Logical POUs e nsertthe function block 4 il Program E Function Function Block STR a Expand All POLI group Save s Network Template Define Placeholders Global Variables i IQ Configuration um m C Project Libraries Hardware tio instances Figure 3 8 Inserting the function block
27. 8037_en_00 PHOENIX CONTACT 3 7 UM CTRL DEV e Select the ST Structured Text language e the block Data Acknowledge Insert Data amp cknawlegde Type Language Program 2 Function gt Function Block Use Reserve type Processor type independent gt zindependent v Figure 3 9 Selecting the programming language and naming the function block e the worksheet by double clicking on Data Acknowledge mec Data Types sis flag B E Logical POUs i Data AcknowlegdeT Data _Acknowlegdey Data _ Acknowlegde a i H mp Physical Hardware m STD eCLR m STD RES ILC170 35 a Tasks Figure 3 10 Opening the worksheet 3 8 PHOENIX CONTACT 8037 en 00 Description of a typical application all devices network e Insert the following program to your worksheet ONBOARD OUTPUT FALSE LE BYTE TO INT PHD 5151 INPUTS O0 1 then ONBOARD OUTPUT BITO TRUE end if 10 syn 2 Data Figure 3 11 Inserting the program The ONBOARD OUTPUT BITO system variable and the PROFINET IO device status variable PND 5151 INPUTS for the process data can be found under the Global Variables e Select the maximum process data length of 256 bytes 256 for the data exchange between master and device
28. AUTOMATION User manual UM EN PROFINET CTRL DEV PROFINET IO controller device functions Em dim dm m h P b y gt a E 8 i 1 T5 m Jj 1 y N 4 E WD VW INSPIRING INNOVATIONS ape AUTOMATION User manual PROFINET IO controller device functions Designation UM EN PROFINET CTRL DEV Revision 00 This user manual is valid for PROFINET IO devices from Phoenix Contact 8037 en 00 2010 04 19 PHOENIX CONTACT UM CTRL DEV BBB PHOENIX CONTACT 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 national 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 products 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 measures that follow this symbol to avoid possible This is the safety alert symbol It is used to alert you to potential personal injury i
29. Figure 3 20 Adding function blocks For the system variables for displaying the status of a PROFINET IO device the process data is generated automatically e Switch to the process data assignment workspace e Inthe top left window Symbols Variables select the program here Main Main e Highlight the PROFINET IO device in the top right window e Highlight the APPL RUN variable in the bottom right window e Enable the context menu on the variable and select the Create Variable command In this case a variable is generated automatically e Proceed in the same way for the PNIO DATA VALID variable ILC330 Controller c Nl ILC 330 PN 192 168 0 2 SR Resource R STD RES ILC330PN BS PROFINET NE ILC 170 ETH 2TX DEVICE ilc 170 device32 192 168 0 3 D 0 ILC 170 ETH 2TX DEVICE 1EA256 ILC 170 ETH 2TX DEVICE ci gl INTERBUS 0 0 240140 1 Unconnected Symbols ariables c mu 5 0 ARM_L_40 5 0 RES ILC330PN Default System Variables 0 STD TSK DEFAULT Main Main Default Auto Symbol Variable Data Type Process Data Item Device Process Data Item IQ Data Type PMIO APPL BOOL Select all Ckri A Search Ctrl F 1 256 ILC 170 ETH 2TX DEVICE 1256 Filter wv Color coded view Disconnect Ctrl Ctrl E Create Variable Figure 3 21 Creating variables 8037 en 00 PHOENIXCO
30. Figure 3 40 Program status The PNIO FORCE FAILSAVE variable is in the FALSE state thus communication is ensured and the outputs are set according to the process data If you remove the voltage connector of the ILC 170 2TX or change the device to the Stop Mode the status of PNIO FORCE FAILSAFE will change to TRUE All outputs will be set to 0 and the value 1 is no longer transferred to the device p PnNIO FOSLE FAILSAFE I IL C1 20ETH1 GO PMIO DATA VALID 0 1 I ILC1 70ETH1 APPL 0 _ _ Parr Cut PRTC FORCE FAILSAFE 16800 lt lt i Main Main Figure 3 41 Program status Stop Mode 3 26 PHOENIX CONTACT 8037 en 00 Description of a typical application all devices network 3 4 6 Checking the program start of the lower level project The behavior described before can also be observed in the ILC170 Device project e Please open the lower level project of the ILC 170 ETH 2TX e Then open the Data Acknowledge POU and activate the Debug mode The following screen appears TRUE ONBOARD OUTPUT FALSE 16 01 BYTE TO INTiPND 3151 INPUTS O0 1 then TRUE ONBOARD OUTPUT BITO TRUE end if lt i Value Default value Type Instance FMD 256 STD CNF STD R 0 16 01 STD EMF STD 1 16 OO STO_CNF STO_A 2 16 00 STD 5 3 15 800 STD CHF STD Wakc
31. ILC 150 GSM GPRS ILC 155 ETH Rew gt Rew gt 0123 50 0172 00 4 z ILC 155 ETH Rev gt ILO 170 ETH Rev gt 0173 50 0173 00 ILE 170 ETH Rev gt 0173 50 Figure 4 2 Selecting the controller e Select the File Save Project As Zip Project As command e Enter a project name here ILC170 Device and save the project Save Zip project as Ore IO PSexample must File name ILC1 U Device mwt File type Project Files rat v Options Figure 4 3 Save project PHOENIX CONTACT 4 3 UM EN CTRL DEV The following window opens 59 PC WORX ILC170 Device Edit Project Build Online Extras 2 eae d pump MTAL AN rE Tr m m c n ERIS T Em 33 3m a 10491919 aN m ES 3s au a Project Group E Libraries lt gt Sy Data Types i sys flag types Name _ Description amp amp y Logical POUs dE ADD Addition amp 8 Main AND Bitwise AND 1 MainT Counter Down Main di CTU Counter Up 5 Main Counter Up Down Physical Hardware dir Div Division 5 88 STD dr EG Equal STD RES ILC170_35 TRIG Falling Edge Detection Tasks d GE Greater Than Equal gt s0 STD_TSK DEFAULT GT Greater Than gt 8 0 Less Than Equal lt an T Less Than lt Ps NM UM dE MOD Modulo Divi
32. LC170ETH1 0 PNIO DATA VALID RFC470DEVICE_PNIO_APPL_RUN i _ILC170ETH1_0_PNIO_APPL_RUN The following devices are used for this application Order No IP address RFC 470 PN 3TX as master RFC 470 PN 3TX as device ILC 170 ETH 2 as device FL SWITCH SMCS optional 29890938 192 168 0 10 Laptop higher level network 1 192 168 1 10 Laptop lower level network 2 8037 en OO PHOENIX CONTACT 4 1 UM EN CTRL DEV 4 2 PHOENIX CONTACT RFC 470 Address areal 192 168 1 x Address area 2 192 168 0 x Subnet 2552552550 Figure 4 1 Typical application devices in several networks In this example a project is created on the lower level controller ILC 170 ETH 2TX by requesting the status variables of PROFINET communication 5151 For this purpose a function block is created in structured text that sets the value true on the ONBOARD OUTPUT BITO system variable The LED is ON when the ILC 330 PN sends the value 1 This example uses two networks the RFC 470 PN 3TX links the process data between ILC 330 PN and ILC 170 ETH 2TX The program is identical with the first example application In the example a function block is used for logical ANDing The PNIO DATA VALID and PNIO APPL variables both system variables of the RFC map the status of the inputs to which the PNIO FORCE FAILSAFE system variable is con
33. LENGTH WORD VAR GLOBAL Process data length 8 10 STD TSK DEFAULT PND 5151 OUTPUTS PND 10 258 VAR GLOBAL Output process data 8 15 Main Main PND S151 INPUTS PND lO 256 VAR GLOBAL process data E EI Main IB DEVICE BODL VAR GLOBAL Interbus device configuration activated Global Variables _ IB DEVICE PARAM READY VAR GLOBAL nterbus device configuration completed Configuration _ IB DEVICE PARAM ERROR vAR GLOBAL nterbus device configuration error lt gt F FE Uu lt gt Data Ackn ES Global Vari Figure 3 12 Selecting the process data 8037 en OO PHOENIX CONTACT 3 9 UM CTRL DEV e Afterwards insert the created function block in the Main worksheet using drag amp drop Project Tree Window 4 Edit wizard avn SS Project Groupe Libraries E zall FUs and FBz GS Data Types il Name sys Hag types Logical POUs Data Acknowlegde mu D ata Acknowlegde Data AcknowlegdeT _Acknowlegde JD BED TO DINT Data Acknowlegdev D TO Data Acknowlegde D TO 5SIMT E E La Data Acknowlegde MainT DELETE 3 amp DERIVAT o Lg Main DIGITAL mE Physical Hardware DIGITAL OUT O STO_CNF eCLR 4 4 CINT_TO_B_BCD az E CINT_TO_BCD ABI Manan
34. ND STRUCT 21 2 STRUCT4 ev STRUCT d StructzElement 25 Struct3Element 26 END STRUCT er 28 Arrayl ARRAT 29 DYTE BYTE Padding Byte WORD WORD BYTE BYTE Padding Byte BYTE BYTE Struct Struct 0 11 OF Struct Figure 3 2 Programming example without data gaps 3 2 Typical application In the following application all devices are in one network see also the topology example on page 2 1 System variables PNIO_FORCE_FAILSAFE TA_VALID PL RUN U Figure 3 3 Typical application 8037 en 00 PHOENIX CONTACT 3 3 UM CTRL DEV The following devices are used for this application ILC 330 PN as master 2988191 192 168 0 5 ILC 170 ETH 2TX as device 2916532 192 168 0 7 FL SWITCH SMCS 4TX optional 2989093 MEM S S Notebook as programming device 192 168 0 10 ILC 330 PN 4141 1444 ILC 170 ETH a i s i l ges tima di p E 5E FEEEEEEE i LLL i i i Address area 182 158 0 x Subnet 299 200 209 0 Gm omm omm GNO GE GAS GARA GO
35. NTACT 3 15 UM CTRL DEV e naddition create the PNArr Out variable with the IO 256 data type as VAR EXTERNAL E Default Pharr Out PND 10 2568 EXTERMAL 0000000000 2 LILCT7 ETH1 0 APPL RUN EXTERMAL LILCTTBETH D DATA WALID BOOL VAR EXTERMAL PMO FORCE FALSAFE Lus 2 h M ain Figure 3 22 Creating the Out variable e To link the process data to the variables proceed as follows e inthe top left window Symbols Variables select Default e Highlight the PROFINET IO controller in the top right window e Highlight the ILC 170 ETH variable in the bottom right window e Connect the PNArr Out variable to the 1256 process data item of the ILC 170 ETH 2TX device The total available data width of 256 bytes was selected in this example You can change it later in the online configuration Process D Symbols V ariables g ILC330_Controller STD CNF ARM L 40 NE ILC 330 PN 192 168 0 2 Resource wj STD RES Default R STD RES ILC330PN System Variables 3 388 PROFINET amp 5 STD TSk DEFAULT c Nl ILC 170 ETH 27x DEVICE ilc 170 device32 192 168 0 3 2 5 Main Main 0 ILC 170 ETH 2TX DEVICE Default 1 EA256 ILC 170 ETH 2TX DEVICE Auto iy INTERBUS 0 0 BR si 5n240140 4 Unconnected Symbol
36. ONTACT 8037 en 00 Description of a typical application devices several networks Assigning process data Switch to the process data assignment workspace e In the top left window Symbols Variables select the System Variables program e Highlight the PROFINET IO device in the top right window e Highlight the 1256 process data item in the bottom right window e Highlight the PNArr_OUT variable in the bottom left window e Enable the context menu on the variable and select the Connect command Process Da Symbols ariables RFC470 Controller Device Sal STD CNF IPC 40 RFC 470 PN 3TX 192 168 0 5 Resource STD RES RFC470PN Default R STD RES RFC470PN System Variables PROFINET STD TSK DEFAULT Nl 170 ETH 2 DEVICE ilct 7Oeth1 192 168 0 7 5 Main i Main 0 ILC 170 ETH 2TX DEVICE 1 E4256 ILC 170 ETH 2TX DEVICE INTERBUS 0 0 84 Unconnected SymboljVariable Data Type Process Data Item Device Data OLIT PMD IO 256 Select all Ckri A Search Ctrl F Filter v Color coded view Connect Disconnect Ctrl Create Variable Ctrl E rch 3r able Ctrl R Figure 4 20 Linking process data e Compile save and close the project 8037_en_00 PHOENIX CONTACT 4 13 UM CTRL DEV 4 1 3 Higher level project e Select the New Project command from the File menu to create a new p
37. POUs Data degde i Lata Data A amp cknowlegdev Data amp cknowlegde E m Li Main T M ain 21 Physical Hardware STD eCLA a ga STD RES ILC170 35 B Tasks Figure 4 7 Opening the worksheet 8037 en 00 PHOENIX CONTACT 4 5 UM CTRL DEV e Insert the following program to your worksheet ONBOARD OUTPUT FALSE LE BYTE TO INT PHD 5151 INPUTS O0 1 then ONBOARD OUTPUT BITO TRUE end if 10 TNT i Data Figure 4 8 Inserting the program The ONBOARD OUTPUT BITO system variable and the PROFINET IO device status variable PND 5151 INPUTS for the process data can be found under the Global Variables e Select the process data length of 256 bytes 256 for the data exchange between master and device 5 Project T Wind Verwendung Beschreibung B 49 Project ie ONBOARD INPUT BIT2 BOL VAR GLOBAL Local input IN3 i Libraries ONBOARD INPUT BIT3 BOOL VAR GLOBAL Local input IN4 3f CE Data Types ONBOARD INPUT BIT4 BOOL VAR GLOBAL Local input INS d oNBOARD INPUT BITS BOOL VAR GLOBAL Local input ING Sy Logical POUs ONMBOARD BOOL VAR GLOBAL Local input Data Acknowlegde ONBOARD INPLIT BIT7 BOOL VAR GLOBAL Local input
38. SEE Communication Ethernet Network Board Generic Marvell Yukon SSE 8053 based Ethernet Controller SecuRem 5 OCF Timeout Marvell Yukon 85E 8055 PCI E Gigabit Ethernet Controller 5ecuHemote Genenc Marvell Yukon 595E 8053 based Ethernet Controller SecuR emote Check Point Virtual Network Adapter For SecureChent SecuRemote Minip Figure 4 33 Selecting the network card Now the PC is ready for communications within the subnet Set the address 192 168 1 10 for the higher level network with the ILC 330 PN as a master and the RFC 470 PN 3TX as a device Set the address 192 168 0 10 for the lower level network with the RFC 470 PN 3TX as a master and the ILC 170 ETH 2TX asa device PHOENIX CONTACT 4 21 UM CTRL DEV 4 2 2 Configuring the ILC 170 ETH 2TX Assigning IP settings To set the IP address in PC WorX proceed as described below e Open your project ILC170 Device e Establish an Ethernet connection between your PC and the controller e Inthe PC WorX menu bar select the Extras BootP SNMP TFTP Configuration menu PC WORX File Edit Wiew Project Build Online Extras gt L pas A Fc Pagelayouk Editor O77 5 OPQ e Create OPC Visualization File Reset DA Addresses Bus Structure PROFINET Configuration BnootP SMPITFTP Canfiguration Check Source Storages Shortcuts Options
39. ata ranges available for the ILC 170 ETH 2TX as PROFINET IO device are displayed under Network Settings gt PROFINET Device Device Details ILC 170 ETH 2TX 192 168 0 7 Extended Settings Cy Network Settings 3 Ethernet Input range 256 bytes Output range 256 bytes m Settings Extended a Communication 5 CPU Service Editor Se Bus interfaces Data sheet Figure 4 47 Input output data ranges Setting the update task To set the update task select the device resource in the Bus Structure window e Set the update task to DEFAULT Bus Structure 4 F 2 Device Details 3 x n E ILC170 Device STD RES ILC170 35 Resource Hd ILC 170 ETH ZTx 122 1868 0 7 A Resource R STD RES ILC170_35 Configuration STD_CNF INTERBLSO 0 STD RES Unconnected PLC type Processor type ILC170 35 Ij Update by Task lt DEFAULT gt Resource Figure 4 48 Setting the update task 4 28 PHOENIX CONTACT 8037_en_00 Description of a typical application devices several networks 4 2 5 Observe startup behavior To use the PROFINET device functions the following conditions apply for the ILCS30 Controller project Higher level controller ILC 330 PN Controller settings IP address 192 168 1 2 Subnet mask 255 255 255 0 PROFINET device name ILC330PN1 RFC 470 settings as a PROFINET IO device IP address 192 168 1 5 Subnet mask 255 255 25
40. d 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 phoenixcontact net catalog Subsidiaries Published by PHOENIX CONTACT 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 FlachsmarktstraBe 8 P O Box 4100 32825 Blomberg Harrisburg PA 17111 0100 Germany USA Phone 49 0 52 35 3 00 Phone 1 717 944 1300 Fax 49 0 52 35 3 4 12 00 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 8037_en_00 Table of contents Table of contents 1 PROFINET IO controller device functions 1 1 1 1 EDU 1 1 1 2 Basic knowledge 4 1 1 1 3 Additional PROFINET documentation 1 1 1 4 System Tedilremiefils 2 RE Ce eain 1 2 1 5 PROFINET IO controller device functions 1 3 io seloe oj metre Pp ArE 2 1 2 1 Topology 1 Mechatronic unit with lower level com
41. e Equipment ID ril IP Address 192 168 1 5 Subnetmask 255 255 255 0 Default Gateway Realtime class Reduction ratio input Reduction ratio output Faulty telegrams until connection is aborted Monitoring Time Inputs ms 192 Monitoring Time Outputs ms 192 Operation in case of configuration differences no amp PROFINET Settings HH PROFINET Stationnames 4 Bus interfaces 2 Data sheet Figure 4 25 RFC 470 PN 3TX integrated as a PROFINET IO device in the bus structure p Phoenix Contact Universal 16 ms 16 ms The process data of the PROFINET device will be displayed in the Device Details workspace of the Process Data tab Bus Structure 1 ILC330 Controller c Na ILC 330 PN 192 158 1 2 CR Resource R STD RES ILC330PN BH PROFIMET zi al 470 PN 3TX DEVICE RFC470PN1 192 168 1 5 g ORFE 470 PM DEVICE 1 E4512 RFC 470 PM DEVICE Egg INTERBUS D 0 B ei mu2apiao 1 Unconnected 2 Device Details 1 E4512 470 PM 3T DEVICE Process Datat Process Data Byte Bit 9 Function Text Terminal equi T Cy 1512 128 REC 470 PN 3TX DEVICE A EA256 AFC 470 PN 3TX DEVICE D EA37 RFC 470 PN 3TX DEVICE ll E5512 RFC 470 PN 3TX DEVICE lll E 54 RFC 470 PN 3TX DEVICE amp 00111 Figure 4 26 Process data of the PROFINET IO device
42. e if there is no application program You can ignore this message Make sure that the controller has the IP address that was set in the project Start the project control dialog via the menu bar If the message Timeout appears after 10 seconds the project and device addresses do not match It is also possible that the IP address of the computer has not been set correctly The controller can be reset from the project control dialog The existing project will be deleted Start the download and perform a cold reset Afterwards the BF LEDs must go out on all devices To access the network status from the program the following system variables are mapped in the global variables of the programming environment Activate the Debug On operating mode and the values of these variables will be displayed PNIO CONFIG STATUS ACTIVE Connection to these devices is being established or has been completed CONFIG STATUS READY The connection establishment to the devices has been completed PHOENIXCONTACT 3 25 UM CTRL DEV 3 4 5 Checking the program start of the higher level project When the program is started correctly the following screen will be shown in the Debug mode JHNIO FORCE FAILSAFE ILC1 0ETH1 PNIO VALID ILC1 0ETH1 PNIO APPL RLIN TO BYTE PNArr PANIC PERLE 16 01 lt i
43. es 192 168 1 1 24 Figure 2 2 Topology 2 Devices in several networks Topology 2 describes a central concept with lower level machine controllers i 470 1 PROFINET i Controller FL Switch SMCS FL Switch SMCS ma i A i i PROFINET 470 8283 RFC 470 po 25 Devices m 192 168 D 1 24 bo 192 168 1 1 24 192 168 1 1 24 192 168 1 1 24 Every machine controller RFC 470 2 3 4 5 comprises a PROFINET IO device This machine controller comprises in parallel IO controllers with their own IO devices The lower level networks can use the identical IP address range since they are separated by the controller The RFC 1 controller as well as the RFCs 2 3 RFCs 4 5 on the device side are located a higher level network Being PROFINET IO devices the individual I Os are located in a lower level network 8037 en 00 Network topologies 2 3 Topology 3 System control with lower level subsystems PROFINET Controller Switch SMCS FL Switch SMCS Li PROFINET Devices PROFINET Controller PROFINET Devices 192 163 1 1 24 Figure 2 3 Topology 3 Devices in several networks Topology 3 describes a central concept with lower level system cont
44. es a padding byte after the ByteElement so that the WordElement is at a WORD address address that can be divided by 2 leaving no remainder The alignment of the overall structure is based on the data type used with maximum alignment In this case the WordElement specifies the alignment The size of Struct2 is calculated based on the elements used and the resulting alignment The corresponding number of padding bytes is inserted so that the size of the data type with the value of the alignment can be divided by 2 leaving no remainder data type size modulo alignment 0 Struct3 does not receive any padding bytes as the maximum alignment corresponds to one byte Due to the padding bytes that belong to the Struct2 structure the Struct3 structure starts at an even address The number of padding bytes in array 1 corresponds to that of two consecutive Struct2 structures 8037 en 00 Description of a typical application all devices network Programming example without data gaps The following program shows an example of how data gaps may be filled in your application program Fill data gaps which are to be expected due to the memory alignment with application data 1 a Structi 3 STRUCT 4 DyteElcment 5 ByteElesment amp WordElement 7 END STRUCT q Structz 10 STRUCT 11 WordE lement 12 ByteElesment 13 ByteElement 14 END STRUCT 15 16 Struct3 17 STRUCT 18 ByteElement1 19 ByteElementz 20 E
45. escription PLC Create Catalog 2 430 ETHAB Rev Import Catalog 2 RFC 430 ETH4B Rev 2 RFC 430 Rev 2 RFC 430 ETH4B Rev 2 RFC 450 ETH4B Rev 2 RFC 450 ETH IB Rev View as Grid Chrl 4G 2 RFC 450 ETH IB Rev 1 Edit Catalog Representation ctrl E ERFC 470 PN 3T DEVICE Display Data Sheet Delete Device EH EH EB EH EH EH EH EHI EH ER ERI EH EE ERI ER ER ERI ER ER ERI ER ER ER FB Figure 4 24 Insert the 470 PN 3TX as a device into the bus structure 4 16 PHOENIX CONTACT 8037 en 00 Description of a typical application devices in several networks The PROFINET device inserted will be displayed in the Bus Structure workspace The IP address is created depending on the IO controller address Bus Structure 2 Device Details ILC330 Controller RFC 470 PN 3TX DEVICE RFC470PN1 192 168 1 5 PROFINET Settings Nl ILC 330 PN 192 168 1 2 SR Resource R STD RES ILC330PN 5 88 PROFINET 470 PN 3TX DEVICE RFC470PN1 192 168 1 5 0 RFC 470 PN 3TX DEVICE 1 EA512 RFC 470 PN 3TX DEVICE S INTERBUS 0 0 240140 ES Unconnected Vendor Phoenix Contact VendorID 0 00 0 Designation DevicelD Functional description Device type PLC Device Family RFC4xx Order number Revision DNS PROFINET Device Name RFC470PN1 Station Mame DeveName Modul
46. forma cold restart for the controller e Todo this switch the supply voltage off and then on again after around 2 seconds The controller is assigned the IP address which is specified in the project for the controller here 192 168 0 7 The following message appears in the message window in the Bus Configurator tab Configured device queries for its IP parameters via BontP The device ILCI7 ETHl received its IP parameters Address 192 168 0 7 Subnet Mask 255 255 z255 Default Gateway via BontP Message inde 4a ww 3 Build Errors Warnings Infos FLC Errors Frint Multi Lizer 4 Bus Configurator A Figure 4 38 Message window The IP address will now be permanently stored on the controller Flash memory 8037_en_00 PHOENIX CONTACT 4 23 UM CTRL DEV 4 24 4 2 3 Configuring the RFC 470 PN 3TX By default upon delivery the diagnostic display has the following status CONTROL RDY Projectname a d IMTERBUS MASTER phd RDY fr FE PROFINET CONTROL WAIT He PROFIMET DEVICE N AIT dnm pri Figure 4 39 Diagnostic display The initial assignment of the IP settings can generally always be carried out using the diagnostic display When using the PC WorX software the initial assignment of the IP settings can be carried out with BootP or using the COM serial interface e Ifthe Remote Field Controller already has IP settings
47. g 0 Configuration B_BCD_TO_SINT dit BED TO DINT BIT TEST dir BDOL TO BYTE BOOL TO DINT Sl E oo TO DWORD d 5 9 IP PROFINET Configuration checked Resource is checked STD RES INTERBUS is checked ILC 330 PN 0 0 0 Eros J Waminge A Ines A PLC Enon Frnt ArT For Help press F1 10 7 c 2GB Figure 4 23 Start screen 8037_en_00 4 15 UM CTRL DEV Integrating the RFC 470 PN 3TX as PROFINET IO device The following section describes how you integrate the 470 as PROFINET device the ILCS330 Controller project e Change to the bus structure To do this click on the Bus Structure icon in the toolbar e Insert the RFC 470 as a device into the bus structure right click 5 Bus Structure ILC330 Controller Na ILC 330 PN 152 158 0 2 Re Resource R STD RES ILC330PN HS PROFIMET 5 9 INTERBUS 0 0 B simncaniao 1 LIncannecked Device Catalog 2 3 Phoenix Contact AXL CT ELR 2 FDT FL FLS FP IL IL 24BD ILB ILC1 ILCZ x ILC Sx Insert Device into Bus Structure IP Import Device Ctrl I qus Copy Device Chr 4 OPTOSUB OPTOSUB 2MBD OT Import GSD File PSM Create new INTERBUS Device D
48. gure the ILC 330 PN controller proceed as described in Section Configuring the ILC 170 ETH 2TX on page 3 19 Assigning IP settings Open the higher level project ILC330 Controller and proceed as described in Section Configuring the ILC 170 ETH 2TX on page 3 19 Please not the following modifications Enter the MAC address of the ILC 330 PN controller Assign the IP address 192 168 0 2 To use the PROFINET device functions the following conditions apply for the ILCS30 Controller project ILC 330 PN settings as PROFINET controller IP address 192 168 0 2 Subnet mask 255 255 255 0 PROFINET device name ILC330PN1 ILC 170 ETH 2TX settings as PROFINET IO device IP address 192 168 0 7 Subnet mask 255 255 255 0 PROFINET device name ILC170ETH1 Please make sure that the same PROFINET device name of the ILC 170 ETH here ILC170ETH1 is used in the lower level project as the higher level project for the ILC 170 ETH as a device here ILC170ETH1 3 24 PHOENIX CONTACT 8037 en 00 8037 00 Description of a typical application all devices one network 3 4 4 Observe startup behavior Starting up the controller is the easiest way to check whether Thecontroller is correctly parameterized ThelO devices have the right name There are double names or double IP addresses in the system Compile the ILC330 Controller project with the bus configuration There will be a warning messag
49. h Window A Watch 1 Watch 2 A Watch 3 A Watch 4 Figure 3 42 Program status active The value 1 is in array 0 of the 5151 INPUTS The ONBOARD OUTPUT BITO variable is TRUE and the LED is ON FALSE ONBOARD OUTPUT FALSE if BYTE TO INT PND 5151 INPUTS O0 1 then FALSE ONBOARD OUTPUT BITO TRUE end if lt E Value Default value Type Instance FMD 256 STD_CNF STD_R 0 4 BELT STD CMF STD 1 16 OO STO_CNF STO_A 2 16 00 STD 5 3 16 00 STD 5 2 wirid A Watch 1 4 Watch 2 A Watch 3 A Watch 4 Figure 3 43 Program is stopped When communication is interrupted by removing the voltage connector of the ILC 170 device or by changing into the Stop Mode through the ILC 330 PN the value is set to O If you need more detailed information call the Diag diagnostic tool from PC WorX under View Diag Here you connect explicitly to a controller and receive further information 8037 en OO PHOENIXCONTACT 3 27 UM EN CTRL DEV 3 28 PHOENIX CONTACT 8037 00 Description of a typical application devices several networks 4 Description of a typical application devices in several networks In the following application all devices are in several networks see also the topology example on page 2 2 UT System variables PNIO_FORCE_FAILSAFE RFCA7ODEVICE PNIO DATA VALID I
50. ication all devices network In addition the value 1 is assigned to the OUT O variable user variable This is done via the negated status of the PNIO FORCE FAILSAFE system variable The value 1 is converted in the BYTE data type since the PROFINET IO process data IO 256 are assigned as ARRAY OF BYTE data type for the variable 8037 en 00 PHOENIX CONTACT 3 5 UM CTRL DEV 3 3 Offline configuration 3 3 1 Lower level project e Select the New Project command from the File menu to create a new project using a template The tree structure and the selection of the control system are now prepared e Select the ILC 170 ETH Rev gt 01 3 50 control system and confirm your selection with New Project General 3xx CPX xxx ILC 1 ILC Zw ILC Sen gt Cancel ILC 150 GSM GPRS ILC 155 ETH Rew gt Rev gt 0173 50 0142 00 Ac h 21 5 T P ILC 155 ETH Rev gt ILC 170 ETH Rew gt 0123 50 0173 00 ILC 170 ETH Rew gt 0173 50 Figure 3 5 Selecting the controller e Select the File Save Project As Zip Project As command e Enter a project name here ILC170 Device and save the project Save Zip project as File name ILC170 Device nwat B File type Project Files ret v ip Options 4 Frontend Code 1 Fagelayauts Figure 3 6 Save project 3 6 PHOENIX CONTACT
51. ick the Reset Control System button 2 Device Details FW UN ILC 170 ETH 2TX 192 168 0 7 Extended Settings a Network ae Network Settings _ SNMP agent 5 Manual definition of the TCP IP settings 3 IO device status IP Address 5 PROFINET Device 192 168 0 7 Subnet Mask 255 255 255 0 Gateway Address O Usage of BootP Server Send DNS PROFINET Device Name ILC170ETH1 Send Real time Clock Settings Time 10 00 31 5 System Time Date Montag 29 2010 Send Settings Read Activate Network Settings Reset Control System FTP Open FTP Folder on Device Offline IP Settings E Extended Settings 46 Communication CPU Service Editor 4 Bus interfaces E C 4 Figure 4 44 Resetting the controller e Inthe Settings Communication Path dialog confirm with OK the suggested address or the one you have selected for your application Settings Communication Path Ethernet 192 168 0 7 bul Cancel Figure 4 45 Setting the communication path PHOENIX CONTACT 4 27 UM CTRL DEV Successful execution of the service will be displayed in the status window Activate Network Settings FTP i a gt Lj IP Settings EJ Extended Settings 4 Communication CPU Service Editor 4 Bus interfaces EJ C lt Figure 4 46 Status window The input output d
52. ing on Data Acknowledge Data Types sis types Logical POU Data Acknowledge i Data Acknowledge T Data Acknowledge Ez Data Acknowledge ES m vg huzical Hardware STD IPC 40 cm STD RES RFCAT PM mL Tasks Figure 4 16 Opening the worksheet 4 10 PHOENIX CONTACT 8037 en 00 Description of a typical application devices several networks e Insert the following program to your worksheet Parr PND 5151 INPUTS U0 Data Figure 4 17 Inserting the program The PNArr OUT O0 variable is linked with the PROFINET device status variable PND 5151 INPUTS so that the ILC 170 device can call the status of the ONBOARD OTPUT BITO system variable Select the maximum process data length of 256 bytes PND_IO_ 256 for the data exchange between ILC 330 PN RFC 470 PN STX and ILC 170 ETH 2TX The RFC 470 PN 3TX can transmit up to 512 bytes of data however the process data length is adapted to the ILC 170 ETH 2TX It can transmit up to 256 bytes Project Tree Window F i o 8 Mame Usage Description la Project _ Ei Default Libraries PND 5151 INPUTS IO 255 VAR EXTER input process data cic Data Types _ PNArr OUT 10 256 VAR EXTER sis E J Logical POUs Data Acknowledge n AcknawledgeT ata Acknowledge Data Acknowledge E Main
53. interface for IO devices was standardized by the PNO Profibus User Organization PROFINET IO and GSD This allows control systems from various manufacturers to communicate with IO devices During configuration IO devices are assigned logically to an IO controller Process data is zent IO Controller CONFIG STATUS ACTIVE PNO CONFIG STATUS FAULT Device variables MD 5151 INPUTS OUTPUTS IO Device Process data is e 71 DATA DIAG 8151 process data is checked Figure 1 1 How communication works PROFINET system variables PROFINET IO controller PNIO FORCE FAILSAFE BOOL All outputs are set to the safe state O PNIO CONFIG STATUS BOOL Status of the active configuration in the context manager PNIO CONFIG STATUS READY BOOL The context manager is active PNIO SYSTEM BF BOOL An error occurred in the PROFINET network that means there is no connection to at least one configured device This value is not set if the Drive BF parameter was set to FALSE for a device This device is removed from connection monitoring PNIO SYSTEM SF BOOL Atleast one device reported a system error diagnostic alarm or maintenance alarm PNIO DIAG AVAILABLE BOOL At least one device reported a diagnostic alarm with an active connection PNIO MAINTENANCE REQUIRED BOOL Atleast one device reported the maintenance demand alarm with an active connection 8037 e
54. llation 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 guarantees 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
55. m left window e Enable the context menu on the variable and select the Connect command e Proceed in the same way for the PNIO APPL RUN variable Data Aui mmm M MK oY IS P D nU 2 i n Il Symbols ariables ILC330_Controller i i Tz Gg STD CNF ARM L 40 5 dg 168 1 2 m STD RES ILC330PN ais Default R STD RES ILC330PN System Variables 5 8 PROFINET 2 0 s n TSK DEFAULT fd RFC 470 PN 3 DEVICE RFC470PN1 192 168 1 5 8 5 y Main BO RFC 470 PN 3TX DEVICE Def mr 1 E4256 RFC 470 PN 3TX DEVICE ge INTERBUSO 0 Auto 240140 1 Unconnected Symbol Variable Data Type Process Data Item Device Process Data Item I Q Data Type PNIO APPL RUN BOOL 0 RFC 470 PN 3TX DEVICE ePNIO STATE I BYTE PNIO VALID BOOL 0 470 PN 3 DEVICE PNIO IS PRIMARY I BOOL RFC 470 PN STX DEVICE VALID JT RFC 470 PN 3TX DEVICE PNIO_APPL_RUN Select all Ctrl 4 0 470 PN 3TX DEVICE PNIO MO DIAG Search Ctrl F 1 E4256 RFC 470 PN 3TX DEVICE Q256 1 E4256 RFC 470 PN 3TX DEVICE 1256 Filter b wv Color coded view Disconnect Ctrl Create Variable Ctrl E i Figure 4 28 Linking variables e naddition create the PNArr Out variable with the IO
56. n OO PHOENIX CONTACT 1 3 UM EN CTRL DEV PNIO MAINTENANCE DEMANDED BOOL At least one device reported the maintenance request alarm with an active connection PNIO DATA DIAG If this bit is set no device diagnostics is present PNIO DATA VALID BOOL The application program must receive information on whether a PROFINET IO device is supplying valid data or not For this reason the PNIO DATA VALID process date exists on each PROFINET IO device Only if this bit is set does the PROFINET device supply valid data and all other process values are valid PROFINET system variables PROFINET IO device PND S181 PLC RUN BOOL Status of the higher level control system IO controller PND 5151 VALID DATA CYCLE BOOL The higher level control system IO controller has established the connection PND S181 OUTPUT STATUS GOOD BOOL I O provider status of the higher level control system IO controller PND 5151 INPUT STATUS GOOD BOOL I O consumer status of the higher level control system IO controller PND S181 DATA LENGTH WORD Process data length that was configured for the IO device PND 5151 OUTPUTS PND IO 512 OUT process data 256 Memory area for OUT process data that the IO device 128 receives from the higher level control system IO controller 64 32 PND 5151 INPUTS PND IO 512 IN process data 256 Memory area for IN process data that the device receives 128 from the higher level control s
57. nassignment and connection example Programming data configuration data PROFINET documents Acyclic communication application note in preparation AH EN PROFINET AZY KOM PROFINET diagnostics application note AH EN PROFINET DIAG Make sure you always use the latest documentation It can be downloaded at www phoenixcontact net catalog 1 4 System requirements Please note that the PROFINET IO device function of the ILC170 ETH 2TX is only available in the PC WorX software from version 6 00 Service Pack 2 or later part of the AUTOMATIONWORX Software Suite 2009 1 50 Service Pack 2 The PC WorX Express software does not support these functions Firmware 3 5x for all controllers including the PROFINET IO device function is at least required to use the PROFINET IO device functions 1 2 PHOENIX CONTACT 8037 00 PROFINET IO controller device functions 1 5 PROFINET IO controller device functions The master slave procedure known from PROFIBUS was transferred to a provider consumer model with PROFINET A Provider generates and transmits data which the Consumer receives and processes In terms of communication all devices in the PROFINET network have equal rights The configuration specifies how the field devices are assigned to a central control system PROFINET IO divides the control devices into IO controllers and IO devices IO controllers are typically control systems e g a central vehicle control The
58. nected The PNIO DATA VALID system variable indicates for each PROFINET IO device whether the connection to this PROFINET IO device was established successfully Only if this bit is set does the PROFINET IO device supply valid data and all other process values are active A negated result is linked to the PNIO FORCE FAILSAFE variable The PROFINET system is stable when the system variable PNIO FORCE FAILSAFE 0 All outputs are set according to the process data If PNIO FORCE FAILSAFE 1 atleast one PNIO DATA VALID variable set to 0 the safe state 0 is output for all PROFINET IO device outputs Assign the value 1 to the OUT O variable user variable This is done via the negated status of the PNIO FORCE FAILSAFE system variable The value 1 is converted in the BYTE data type since the PROFINET process data PND 256 are assigned as ARRAY OF BYTE data type for the variable 8037 en 00 8037 00 Description of a typical application devices in several networks 4 1 Offline configuration 4 1 1 Lower level project e Select the New Project command from the File menu to create a new project using a template The tree structure and the selection of the control system are now prepared e Select the ILC 170 ETH Rev gt 01 3 50 control system and confirm your selection with Mew Project General CP 3xx CPX ILC Tux ILC Zex ILC 3x 5 EENET AA A AA EE TE
59. net Protocol Properties General ou can get IP settings assigned automatically if pour network supports this capability you need to ask your network administrator for the appropriate IP settings Obtain an address automatically gt Use the following IP address address 197 766 0 10 Subnet mask 255 255 255 0 Ibtain ONS server address automatically gt Use the following DNS server addresses Preferred DNS server Alternate DONS server Figure 3 25 Assigning an IP address Select the network card of your PC that is to be used for communication in the Tools PROFINET menu of PC Worx PROFINET Communication Ethernet Network Board Generne Marvell rukon 88E 8053 based Ethernet Controller SecuRem DCP Timeout Marvell Yukon 88E 9055 PCI E Gigabit Ethernet Controller SecuRemote M Genenc Marvell rukon 85E 8053 based Ethernet Controller SecuRemote t Check Point Virtual Network Adapter Far 5ecureClient SecuRemoate Minip Figure 3 26 Selecting the network card Now the PC is ready for communications within the subnet 3 18 PHOENIX CONTACT 8037_en_00 Description of a typical application all devices one network 3 4 2 Configuring the ILC 170 ETH 2TX Assigning IP settings To set the IP address in PC WorX proceed as described below e Open your
60. njury 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 will 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 areference to other sources of information manuals data sheets literature on the subject matter product etc 8037 en 00 8037 00 Please observe the following notes General terms and conditions of use for technical documentation Phoenix Contact reserves 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 insta
61. pact controllers 2 1 2 2 Topology 2 Four identical machine controllers under a machine park controller Ua nsi TUE RON MUS REND QUK QUU 2 2 2 3 Topology System control with lower level subsystems 2 3 3 Description of a typical application all devices In one netWOrk ocu 3 1 3 1 Information on how it was carried 3 1 3 2 Wieioik iole e iio RR EET TIL LLL D 3 4 3 3 OMIMGE COMNGUIATON 2 EE 3 7 3 3 1 21 5 DIO CCE T A 3 7 3 3 2 Higher level 3 12 3 4 Online COMNG UIA a 3 19 3 4 1 Preparing the PC for communication 3 19 3 4 2 Configuring the ILC 170 0 3 20 3 4 3 Contiguring the TEC S30 PIN Wendie 3 25 3 4 4 Observe startup behavior 3 26 3 4 5 Checking the program start of the higher level project 3 27 3 4 6 Checking the program start of the lower level project 3 28 4 Description of a typical application devices In lt
62. r defined data types nsert padding bytes manually in order to ensure the uniform size and layout of the data types When inserting padding bytes please observe the memory alignment method of the controllers used in the application 1 byte 2 byte or 4 byte alignment PHOENIX CONTACT 3 1 UM EN CTRL DEV 3 2 PHOENIX CONTACT Programming example with data gaps The following program example shows how data gaps are filled 1 2 Structi a 4 BytekElement i BYTE 2 WordEleiment WORD END STRUCT 7 8 Structz a STRUCT c 10 WordElement WORD Size 11 ByteElement BYTE 12 END STRUCT 13 14 Structs 15 STRUCT id BYTE 17 ByteElement2z BYTE 18 END STRUCT 19 20 21 STRUCT 22 Struct2Element Srtructz 23 Struct3Element Srruct3 24 END STRUCT 25 26 Arrayl ARRAY 0 1 OF Structz ET END Structi Struct2 Struct3 Struct4 Array1 ByteElement WordElement ByteElement1 WordElement WordElement ByteElement2 ByteElement ByteElement Padding Byte Padding Byte Padding Byte WordElement ByteElement 1 WordElement Padding Byte ByteElement2 d Size 4 bytes Size 4 bytes Size 2 bytes Size 6 bytes Size B bytes Align 2 bytes Align 2 bytes Align 1 bytes Align 2 bytes Align 2 hytes Figure 3 1 Programming example with data gaps Struct1 receiv
63. roject using a template The tree structure and the selection of the control system are now prepared e Select the ILC 330 PN Rev gt 01 4 6F 3 50 control system and confirm your selection with OK Save ip project as CUO em E Example rmat File name ILC330_Controller mwt File type Project Files mwt bull Options zip Frontend Code Figure 4 21 Selecting the controller e Select the File Save Project As Zip Project As command e Enter a project name here ILC330 Controller and save the project project as Speichen Proecs SIO Example Bj Example rmat Dateiname ILC330_Controller rwt Dateityp Project Files nwt Abbrechen ip Uptions ip User Libranes 21 Frontend Code Figure 4 22 Save project 4 14 PHOENIX CONTACT 8037_en_00 Description of a typical application devices several networks The following window opens PC WORX ILC330 Controller Edt Project Buld Online Extras 2 TR oF a A n Sy Project Group Libraries call FUs and gt Data Types i sys_flag_types Logical POUs 8 Main i MainT Main DD T T Main ADDR TO ID com d Hardware dit AND c STD ARM L 40 dE R STD RES ILC330PN di ASIN Sy Tasks ASL m 0 STD TSK DEFAULT ASR El 0 aM Main Ji Main Global Variables T M i
64. rollers Every controller comprises a PROFINET IO device This controller is also an IO controller with its own IO devices All controllers and IO devices are located in one network 8037 en 00 PHOENIX CONTACT 2 3 UM EN CTRL DEV 2 4 PHOENIX CONTACT 8037 00 Description of a typical application all devices one network 3 Description of a typical application all devices in one network 8037 en 00 3 1 Information on how it was carried out Alignment The alignment of the data elements in the Inline controller memory can result in data gaps when storing data in the memory The compiler automatically fills these gaps with padding bytes during the compiler process in order to prevent incorrect processing The disadvantage of the automatic filling of data gaps becomes apparent when data is transmitted from the Inline controller to another controller If this controller does not know the memory algorithm of the Inline controller it will interpret the received data incorrectly It is therefore useful to program the filling of data gaps in your application program Data transmissions to other controllers can thus be taken into consideration For example use byte arrays with an even number of bytes and or word arrays in order to avoid data gaps in your application program The following should be taken into consideration when creating the program Create data types in flat structures i e do not nest use
65. s set to 0 The LED goes out as well because the ONBOARD INPUT BITO variable is reset to FALSE 1 TRUE DNBOARD OUTPUT BITO FALSE 2 3 1564Z01 if BYTE TO INT PND 5151 IHPUTS O0 1 4 5 then TRUE ONBOARD OUTPUT BITO TRUE 7 B end g Instance STO_CNF STD_R Type Value Default salue a ne IL 256 0 16 01 BYTE STD CMF STD i 1 16 00 BYTE STD ECMF STD E 2 16 00 BYTE STD 5 3 16 00 BYTE STD CMF STD 5 A Watch 1 Watch 2 A Watch 3 Watch 4 Figure 4 52 Program is stopped When communication is interrupted by removing the voltage connector of the ILC 170 device a BF error appears on the RFC display at the PROFINET controller If you need more detailed information call the Diag diagnostic tool from PC WorX under View Diag you connect explicitly to a controller and receive further information 8037 en 00
66. s the network status from the program the following system variables are mapped in the global variables of the programming environment Activate the Debug On operating mode and the values of these variables will be displayed PNIO CONFIG STATUS ACTIVE Connection to these devices is being established or has been completed CONFIG STATUS READY The connection establishment to the devices has been completed 4 30 PHOENIX CONTACT 8037 00 8037 00 Description of a typical application devices several networks 4 2 6 Checking the program start of the higher level project e Open the ILC330 Controller project When the program is started correctly the following screen will be shown in the Debug mode PNIO FORCE FAILSAFE PNIO VALID PNIO APPL BOOL TO BYTE PNArr Outo PINIO FORCE 16 201 Main Main Figure 4 49 Program status The PNIO FORCE FAILSAVE variable is in the FALSE state thus communication is ensured and the outputs are set according to the process data If you remove the voltage connector of the RFC 470 PN STX or change the device to the Stop Mode the status of PNIO FORCE FAILSAFE will change to TRUE All outputs will be set to 0 and the value 1 is no longer transferred to the device PNIO FORCE FAILSAFE 1 PNIO DATA VALID PNIO APPL qe TV TE PNArr Qut O
67. s window under Network Settings The device name in the higher level project ILC 170 ETH device must match the device name of the lower level project ILC 170 ETH e Inthe Activate Network Settings area click the Reset Control System button 2 Device Details ILC 170 ETH 2TX 192 168 0 7 Extended Settings Network Settings SNMP agent IO device status PROFINET Device Network Settings 5 Manual definition of the TCP IP settings IP Address 192 168 0 7 Subnet Mask 255 255 Gateway Address E 255 0 Usage of a BootP Server Lisa Fa DI Send DNS PROFINET Device Name ILC170ETH1 Send Real time Clock Settings Time 10 00 31 v System Time Date Marz Send Montag 29 2010 Settings Read Activate Network Settings Reset Control System FTP Open FTP Folder on Device Offine amp Settings EJ Extended Settings Communication 5 CPU Service Editor amp Businterfaces C gt Figure 3 35 Resetting the controller 8037 en 00 8037 00 Description of a typical application all devices network e Inthe Settings Communication Path dialog confirm with OK the suggested address or the one you have selected for your application Settings Communication Path Ethernet 192 168 0 7 w Figure 3 36 Setting the communication path S
68. sion MOVE Assigns Value MUL Multiplication dit NE Not Equal lt gt NOT Complement dir OR Bitwise DR Project IF PROFINET Configuration is checked Resource is checked STD RES INTERBUS is checked ILC 170 ETH ZTX 0 0 0 gt ERE A Errors Warnings A Infos PLC Errors Print Multi User Bus Configurator Bus Configurator FDT Figure 4 4 PC WorX start screen e Right click on Logical POUs e nsertthe function block Insert Function Function Block Nim Paste Expand All POU group Save As Webwork Template Define Placeholders ae Main ma alabal variables Configuration Co Project Pols E Libraries f FE Hardware Jg Eae Figure 4 5 Inserting the function block 4 4 PHOENIX CONTACT 8037 en 00 Description of a typical application devices several networks e Select the ST Structured Text language e the block Data Acknowledge Insert Data Acknowlegde Type Language Program Function gt Function Block Use Reserve type Processor type independent gt lt independent gt Figure 4 6 Selecting the programming language and naming the function block e Open the worksheet by double clicking on Data Acknowledge Sy Data Types sug flag types Sy Logical
69. that are valid in your network you can modify the IP settings via the network using PC WorX e Setthe RFC 470 PN STX to the mapped IP address 192 168 0 5 It can be accessed in the network after a restart of the device SYSTEM MENU IP Config LAN1 IP Parameters for 1 IP Address 0 0 0 0 Subnetmask 0 0 0 0 Gateway 0 0 0 0 address 45 12 MAC LANL 00 40 45 12 LANL 00 40 45 12 e6 cc Edit Subnetmask 1 1 Edit Gateway LAN1 PLZ IB MASTER BM C PR D Game eoe Figure 4 40 SYSTEM MENU IP Config LAN1 EDIT 192 168 000 005 PLC IB MASTER PM C PH D LAN1 configuration display The procedure for assigning the IP settings is essentially the same for the 1 LAN1 1 LAN1 2 and LAN 2 interfaces The following describes the assignment of the IP settings at the LAN1 interface as an example The LAN1 1 LAN1 2 interfaces are switched internally Thus both ports can be accessed using the IP settings defined PHOENIX CONTACT 8037 en 00 8037 00 Description of a typical application devices several networks For the interface proceed as in the previous example however set the IP address to 192 168 1 5 The RFC 470 PN 3TX communicates with this address as a device NOTE The IP address of your PC must be in the same subnet as the LAN1 or LAN interface of the RFC 470 PN 3TX Only
70. uccessful execution of the service will be displayed in the status window Activate Network Settings FTP amp IP Settings E Extended Settings 40 Communication 5 CPU Service Editor f Bus interfaces E C Figure 3 37 Status window The input output data ranges available for the ILC 170 ETH 2TX as PROFINET IO device are displayed under Network Settings gt PROFINET Device Device Details A ILC 170 ETH 2TX 192 168 0 7 TExbtended Settings Network Settings Ethernet SNMP agent IO device status A EPROFIMET Device Input range Output range 256 bytes 256 bytes n Settings Extended Settings Communication 8 CPU Service Editor A Bus interfaces Data sheet Figure 3 38 Input output data ranges PHOENIX CONTACT 3 23 UM CTRL DEV To set the task to update the I Os select the device resource in the Bus Structure window e Set the update task to DEFAULT Bus Structure a H i Device Details avo ILC170 Device STD RES ILC170_35 TResaurcel G E ILC 170 ETH 2T 192 168 0 7 A R Resource R STD RES ILC170_35 gfe INTERBUS 0 0 ES Unconnected Configuration STD CMF STD RES PLC type Processor type ILC170 35 TO Update by Task lt DEFAULT gt Resource Figure 3 39 Setting the update task 3 4 3 Configuring the ILC 330 PN To confi
71. uration pee ee Group all FUs and FBs gt D Name Wags d acos ADD T T ADDR TO ID AND ASIN ASL E ASR 8_BCD_TO_DINT BCD TO SINT BCD TO DINT di BIT TEST BOOL TO BYTE BOOL TO DINT BOOL TO DwWORD BOOL TO INT WONN TA IDEM aa 82 suia h Enos wamings J infos X PLC Eros A Print Muter Bus configurator For Help press F1 Figure 4 13 Figure 4 14 ce Project WorX start screen Right click on Logical POUs Insert the function block ect 1 Libraries 4 Data Types STR V Expand All i 2 7 Program Save 5 Network Template Define Placebolders ee Main Glabal Variables TH ID Cenfiguration TS Inserting the function block POUs NE Libraries Hardware df Instances T Function Function Black PU group 1 4 9 8037 00 UM CTRL DEV Select the ST Structured Text language Name the block Data Acknowledge Insert Data Acknawlegde Type Language Program L O Function IE gt Function Block Use Reserve PLC type Processor type independent gt independent gt v Figure 4 15 Selecting the programming language and naming the function block Open the worksheet by double click
72. ystem IO controller 64 32 1 4 PHOENIX CONTACT 8037 en 00 Network topologies 2 Network topologies The following pages show three typical examples of network topologies These topology examples are to explain the dependence and or independence of the PROFINET IO controller device functions The following hardware was used for the network structure ILC 330 PN 2988191 03 ILC 170 ETH 2TX 2916532 04 RFC 470 2916600 07 FL SWITCH SMCS 4TX PN 2989093 06 2 1 Topology 1 Mechatronic unit with lower level compact controllers ILC RFC 470 PROFINET Controller ILC 170 PROFINET FL Switch SMCS Devices Touch 7 Fana ILC 17 ILC 170 Figure 2 1 Topology 1 All devices in one network Topology 1 describes a central concept with lower level compact controllers Every compact controller ILC 1xx is an independent PROFINET IO device and handles a local mechatronic unit with inputs and outputs All controllers are available in a local network Realtime communication over the central controller RFC 470 PN 3TX ILC 3xx takes place over PROFINET Controllers that are connected over a switch can be disconnected from the network at any time 8037_en_00 PHOENIX CONTACT 2 1 UM CTRL DEV 2 2 PHOENIX CONTACT 2 2 Topology 2 Four identical machine controllers under a machine park controller PROFINET Controller PROFINET Devic

User manual UM EN PROFINET CTRL DEV - Digi-Key

Contents

Download Pdf Manuals

Related Search

Related Contents