Home

1 Fieldline at the PROFIBUS-DP

1. O O Ol Ol TYO OO y o o d o0 08 Ol Ol 5 J oo 2 GO OCO OO oon i a D oo DTO sr gl COG oos 9 a cla O oo or or or To OO OO OF N u Q Par E Q nd N dp io 0 100 OOOO DO 2 ee en ee I DEE 5 nm U Neo 2222 01 OO 4 Px O O O ol oo B oo aa o 0 5 ae 2 ISSSSSSIO oo ode de ol 0 ol Qo O 6 6 OOf OO ie be Ol ol ol oo B O oo an o 5 Sa lO
2. 6852C005 Typical structure of an PROFIBUS DP system with remote bus and local bus Figure 1 1 Key for Figure 1 1 Master Termination resistor Repeater Repeater with termination resistor R T Sx Segment 1 3 PHOENIX CONTACT 6852_en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME Table 1 1 Basic network specifications Topology Linear active bus connection at both ends of a segment termination resistor branch lines are permitted Number of stations in a segment 32 without repeater 127 with repeater Number of repeaters between two devices 9 maximum Maximum expansion of the bus Depending on the transmission speed see Table 1 2 on page 1 5 up to 1 2 km at 93 75 Kbps maximum the expansion can be increased with the help of repeaters Transmission speed 9 6 Kbps to 12 Mbps can be adjusted in increments see Table 1 2 on page 1 5 E Repeaters can be found in the latest Phoenix Contact INTERFACE catalog 1 4 PHOENIX CONTACT 6852_en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Fieldline at the PROFIBUS DP 1 3 2 Address In the PROFIBUS DP network each device is identified by its address device ID station address For Fieldline Stand Alone devices all addresses between 1 and 99 are allowed whereas the addresses for Fieldline Modular devices are between 1 and 126 Ina PROFIBUS DP network an address can only be assigned once The device a
3. lt Length of PCP data gt This value specifies how many bytes of PCP object data object contents follow lt PCP object data gt This is the actual contents of a PCP object lt Status gt For a positive PCP response the status is OOpex in the event of an error it is 44 lt Error data PCP DP V1 gt the structure of the error data is lt PCP confirmation code gt lt Invoke ID gt lt Status 44 x gt lt PCP error code 4 bytes gt PCP error code see Error Codes for DP V1 and VC1 Communication on page A 3 During the access onto PCP please note the first byte in the DP V1 data block With O6nex PCP Read and with O7hex a PCP Write is executed EJ 4 8 PHOENIX CONTACT 6852_en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Acyclic Communication DP V1 and PCP 4 4 2 Examples The section below provides a few examples to aid understanding all values in hex These examples indicate how objects on the bus coupler and the I O devices can be read and written The station structure is as follows FLM BK PB M12 DI 8 M12 FLM DIO 4 4 M12 2A _FLM AI 4 SF M12 FLMAO4SF M12 PD PCP x words The FLM Al 4 SF M12 and the FLM AO 4 SF M12 are PCP capable devices For a better understanding of the examples the object directory of the FLM Al4 SF M12 device should be given The FLM Al 4 SF M12 object directory contains among others the following object Table 4 4 Object D
4. CPU 314 A CPU 314 IFM CPU 315 A CPU 315 2 DP CPU 316 CPU 316 2 DP CPU 318 2 CPU 614 A CPU M7 Properties PROFIBUS interface DP Master RO S2 1 Fa General Parameters neel EEE Address 2 x If a subnet is selected the next available address is suggested Highest address 126 Transmission rate 1 5 Mbit s 2 Subnet not networked New Properties Delete Properties New subnetPROFIBUS Q M7 EXTENSION C3 PS 300 Ed RACK 300 9 SM 300 FM SIMATIC 400 B SIMATIC PC Based Control 300 400 B SIMATIC PC Station General Network Settings Name PROFIBUS 1 3 es sam Fee Project path Mawa 6ES 3 e E El Tre A feeen DASiemens Step S7poi Manual SS of the project D Siemens Step S proj Manual_1 Ls EN ss __ Author IH ans Wenger Date created 09 04 2003 16 36 58 Last modified 09 04 2003 16 36 58 Comment Sample for Manual 57 300 power supply modules Abbrechen Hilfe Press F1 to get Help M Start SIMATIC Manager Manual a HW Config SIMATI Dokument Microsoft word z Paint Shop Pro m2 PA 16 49 Figure 3 5 Selecting the CPU 3 8 PHOENIX CONTACT 6852_en_02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configuration and Startup Next confirm the entries in the Properties PROFIBUS Interface DP Master R0 S2 1 window with
5. 6852 en_02 Object types Simple variable THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Acyclic Communication DP V1 and PCP Table 4 1 Object Description example Object Description OD Object Description The object description includes all the properties of the object such as data type object type name etc There are various different object types Simple variable type objects Examples include measured values the time or status of a device Array Array type objects i e several simple variable objects of the same type which are grouped to form one object Each element can be accessed individually An example of an array is a range of the same type of measured values Record Record type objects i e several simple variable objects of different types which are grouped to form one object As for the array type each element of a record can be ac cessed individually An example of a record is the group of data in a test report which contains not only the actual measured value but also additional information e g the time of the measurement Program invocation Program invocation type objects i e program sequences that can be run 6852 en 02 For additional information on PCP communication please refer to the IBS SYS PCP G4 UM E user manual Order No 27 45 16 9 PHOENIX CONTACT 4 5 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME 4 4 Acyclic Co
6. Incl Ripple 5 This corresponds to a range of 18 V to 30 V ripple included A selection of suitable voltage supplies can be found in the INTERFACE catalog from Phoenix Contact e Select PROFIBUS cables IS For interference free transmission Phoenix Contact recommends a 2 wire twisted pair and shielded cable specified as cable type A in EN 50 170 Part 8 2 The cable type B which is also described must not be used anymore Select the type of connections for the cables to the devices BUS IN BUS OUT or T pieces for FLS devices only see section Connecting the Bus on page 2 5 Please observe the notes in section Laying the PROFIBUS Cable on page 1 6 PHOENIX CONTACT 3 1 6852 en 02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME 3 2 Installation N Disconnect the power supply before installing the devices e _ Installing devices See FLS FLM SYS INST UM E user manual e Connecting the Bus See section Connecting the Bus on page 2 5 e Installing mains termination resistors See section Mains Termination Resistors on page 1 6 e Setting the address See section Setting the Address on page 2 7 e Connecting the supply voltage See FLS FLM SYS INST UM E user manual 3 2 PHOENIX CONTACT 6852 en _02 Requirements I Starting the STEP 7 SIMATIC Manager 6852_en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configuration
7. Addiess fi g FLS PB M12 DIO 4 4 M12 24 FLS PB M12DI8 M12 B FLS PB M12DO8M12 24 FLS PB M12 DI 16 M12 g FLS PB M12 1EHEL 501 Fs FLM BK PB M12 DI8 M12 BE 5 BLOCKLINE EHDI ET200eco 5 BR3120 Typ 8644 0 PVT gg VersaPoint Profibus MIU 3 Verzahdax IP 4Pt In 4Ft Out Valves FC Gateway fy PLC H O Compatible PROFIBUS DP Slaves I Closed Loop Controller E Configured Stations 9 DP VO slaves 49 DP AS4 Hg DP PA Link H ENCODER H E ET 2008 ce ET 200C Transmission rate 9 6 Kbps Subnet hot networked 4a PROFIBUS 1 DP Mastersystem 1 Properties Delete PROFIBUS address Abbrechen Hilfe Figure 3 8 Properties PROFIBUS Interface FLM BK PB M12 DI 8 M12 6852 en 02 PHOENIX CONTACT 3 11 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME Positioning the Select the bus coupler by clicking on the bus coupler icon using the mouse 1 bus coupler Select a free slot line by clicking with the mouse in a free slot row 2 A HW Config SIMATIC 300 1 Configuration doku al Station Edit Insert PLC View Options Window Help olala B S ola JE 32 e H Phoenix Contact aie jj PS 307 Ya PROFIBUS 1 DP Mastersystem 1 B FLS PB M12 DIO4 4 M1 2 24 B FLS PB M12 DI8 M12 B FLS PB M12 D08 M12 24 B FLS PB M12 DI 16 M12 B FLS PB M12 16REL 501 El B FLM BK PB M12 DIS M12 4 Universal module PD PCP 4 words PD PCP 6 words
8. OK or Return pH 0 UR 4 PS 307 5A a Efi SIMATIC 300 l EE C7 aS CP 300 2 0 CPU 3121FM H CPU 313 2 9 CPU 314 2 9 CPU 314 IFM 2 9 CPU 315 dr EEE 5 Mbit s PROFIBUS 1 1 5 Mbit 0 CPU 31620P ZZ GQ CPU 318 2 E E CPU 614 B CPUM 2 0 FM 300 EST eG IM 300 2 M7 EXTENSION Ps 0 RACK 300 3 9 SM 300 H SIMATIC 400 B SIMATIC PC Based Control 300 400 SIMATIC PC Station S Modde 1 f EEN EE F safi Fme Ln 3 4 5 6 7 8 a 1 1 0 1 Figure 3 6 Properties PROFIBUS Interface DP Master RO S2 1 6852 en_02 PHOENIX CONTACT 3 9 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME Select PROFIBUS FLM Click on Sample project DP master system 1 bus coupler Click with the mouse in the free slot 2 Select the FLM bus coupler from the hardware catalog 3 in the PROFIBUS DP menu Additional Field Devices I O Phoenix Contact FIELDLINE FLM BK PB M12 DI 8 M12 by double clicking on FLM BK PB M12 DI 8 M12 id HW Config SIMATIC 300 1 Configuration doku al Station Edit Insert PLC View Options Window Help laj x Dlel ie sola JED A we PROFIBUS DP 2 2 Additional Field Devices i CJ General H Drives a 1 0 S 1 0 i E VIPA H Phoenix Contact CJ INLINE 2 9 FIELDLINE gg FLS PB M12 DIO4 4 M12 2A B FLS PB M12 DIS M12 FLS PB M12 DO8 M12 2 amp g
9. Since the addressed device does not support PCP the request is rejected immediately A message from the DP V1 occurs in this case the error code D2 stands for device does not have PCP See also section Error Codes for DP V1 and VC1 Communication on page A 3 4 14 PHOENIX CONTACT 6852_en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Acyclic Communication DP V1 and PCP 4 5 Acyclic Communication in DP VO Mode via Process Data The DP V1 communication is relatively new compared to cyclic DP VO communication However the life of control systems and plants is so long that expansions and modifica tions are made In many cases the control system is not DP V1 compatible but is ex pected to operate complex devices Acyclic services For this purpose the operation of the acyclic services is also possible within the process data i e also control systems that does not have DP V1 can operate more complex de vices Additional information on PCP communication can be found in sections PCP Communi cation Basics on page 4 3 and Acyclic Communication DP V1 and PCP on page 4 1 4 5 1 Mechanism for Transmission in the Process Data VC1 device Transmission is via a virtual C1 device VC1 device A C1 device should be selected in the hardware configurator in the same way as normal I O devices and therefore specified in the configuration and parameter telegram The VC1 device is only a virtual device because the process data c
10. 1 Turn DI32 and DO32 data 0 SET_PRM does not overwrite dynamic configuration 1 SET_PRM overwrites dynamic configuration 0 Do not turn DI16 and DO16 data 1 Turn DI16 and DO16 data Reserved set to 0 Reserved set to 0 0 Automatically acknowledge I O errors 1 Manually acknowledge I O errors 0 Stop local bus during device failure 1 Operating local bus with accessible devices The data for the configuration and the data for the fail safe value can be found in the de vice specific data sheets PHOENIX CONTACT 6852 en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Appendix Table A 9 Parameters for the I O devices byte 1 O Bits to bits Configuration OOS 00 No configuration e g DO Pfr Permanent configuraton 110 Temporary configuration OOO 00 No fail safe value e g DI fot outputzero Tre Valueremains the same pa Value tom datafiedis used _ 5 L_ O omowe S 1 Function block also several 1 7 Oooo receeemaed Following one configuration block Bit 7 to bit6 01 Configuration block ID 2 Bit 5 to bit O_ Length of the data block Byte 3 ton R n data bytes Following one fail safe block Bit 7 to bit 6 10 Fail safe value block ID 22 Bit 5 to bit 0 Length of the data block Byte 3 ton el n data bytes 6852 en 02 PHOENIX CONTACT A 5 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME If one or several function blocks a
11. FEIGHT 2 SIMATIC 300 Edit Catalog Profiles SIMATIC 400 Update Catalog SIMATIC PC Based Control Install New GSE Files Import Station GSE Files 0 UR PROFIBUS DP slaves for SIMATIC 57 M and C distributed rack Installs new device database files in the system and updates the contents of the catalog Figure 3 4 Installing a new GSD file The new GSD file is loaded in the appropriate directory and the hardware catalog is updated 6852 en 02 PHOENIX CONTACT 3 7 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME Selecting DIN rail Now select the DIN rail and the power supply and power supply For the corresponding procedures please refer to your STEP 7 SIMATIC Manager user manual Selecting the CPU Now select the CPU by double clicking on the CPU folder in the right hand window 1 CPU 315 2DP in this example Click on the New button in the Properties PROFIBUS Interface DP Master R0 S2 1 window 2 Enter the name in this example Sample project in the Properties New Subnet PROFI BUS dialog box 3 and confirm the entry with OK or Return al Hw Config SIMATIC 300 Station Configuration Manual mi Station Edit Insert PLC View Options Window Help olele g S e il afm 38 rel 0 UR IJ PS 307 54 l Hardware catalog Profle standad PROFIBUS DP SIMATIC 300 mm C7 CP 300 CPU 300 CPU 312 IFM CPU 313
12. Module menu item a Hw Config SIMATIC 300 1 Configuration testi_0607 mi Station Edit Insert PLC View Options Window Help Dee Sul S olsa mf 32 rel 0 UR 1 fj Ps 307 2 fi CPU Press F1 to get Help 3 14 PHOENIX CONTACT a Additional Field Devices ld 2 8 FLS PB Blom eres 1 Closed Loop Controller PHOENIX IL PEER Configured Stations EE i DP VO slaves DP AS i DP PA Link ENCODER ET 2008 ET 200C ET 20015 ET 200L ET 200M ET 2005 eg M151 CPU leg IM151 CPU FO MIS er He Hr IM151 1 Slot 9 Module Order number Firmware MPI address address Q address Comment 2 IM151 1 Tg Pssorsa fees fT Ee ei 2 gfcrusis2op 6ES7 315 2AFO3 0ABO Wi o 3 1 ia ie EEE an 3 ey a Ss nn nn nn ee EEE m i Function Modules mm nn a nn ee wl IDENT C ee ee ee aaa aa 7 eg nn En mn ee nn a ae ere E R SIMADYN T ae io fe ttl Sl N H E SIMOREG FC SIMOVERT lelx Profle standad O PROFIBUS 1 DP master system 1 PROFIBUS DP modules send capability for direct data exchange cycle synchronous po Chg Figure 3 11 Connecting additional devices to the DP master system and downloading them After data transmission is complete the PROFIBUS system starts automatically 6852 en_02 O parameters 6852 en 02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC CO
13. PD PCP 8 words PD PCP 10 words PD PCP 12 words PD PCP 14 words PD PCP 16 words FLM DI8 M12 FLM DIS M12 QTY 2 16Bit FLM DOS M12 FLM DOS M12 QTY 2 16 Bi FLM DIO 4 4 M12 24 FLM DIO 16 16 M12 8 DIAG FLM DIO 4 4 QTY 2 8 Bit FLM DIO 4 4 QTY 4 16 Bit FLM Al 4 SF M12 FLM AO 4 SF M12 CJ BLOCKLINE J ET200eco B BK3120 B Typ 8644 DP 1 B YersaPoint Profibus NIU B VersaMax IP 4Pt In 4Pt Out 7 FLM BK PB M12 DIS M12 Slot 4 Module Order number Address O Address Comment E FE 66 FLMDBM2 Mo Cd 130 mem CT tC 194 LM DIO 16 16 M12 8 DIAG 3 4 12 3 6 FLMAI4SFMI2 25625 EEE E HE E Press F1 to get Help Figure 3 9 Positioning the bus coupler The FLM components can now be selected from the hardware catalog and assigned to the bus coupler according to their physical position in the sequence drag amp drop IS If the FLM BK PB M12 DI 8 M12 device is not automatically inserted into the first position by the hardware configurator please manually select it from the hardware catalog 3 12 PHOENIX CONTACT 6852 en 02 Dlelsjelsj S ele online components com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configuration and Startup If necessary the I O addresses can be changed by double clicking on the rows of the FLM components Entries can be made in the Properties DP Slave dialog box Confirm your entries with OK or Return lo
14. a T piece is used to connect the bus this must be connected at the BUS OUT connection To ensure IP65 IP67 protection cover the unused connection with a protective cap 1 BUS OUT 6852A003 Figure 2 2 Bus connection via T piece Accessories Two M12 connectors 1 T piece 1 protective cap Advantage When the bus is running devices can be removed or added without physical interruption To do this the master and the control program must support the removal and addition of devices Supports all transmission rates Disadvantage Additional accessories required 6852 en_02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Connecting Bus Cables and Setting the Address 2 2 Connecting the Bus and Termination Resistor FLS For a Fieldline Stand Alone device that is followed by another device the incoming and outgoing bus must be connected Figure 2 3 A1 and B1 For the last device of a PROFIBUS segment only the incoming bus is connected Figure 2 3 A2 and B2 A ter mination resistor 1 is placed in the connection for the outgoing bus To ensure IP65 IP67 protection cover the unused BUS IN connection with a protective cap 2 BUS OUT B B1 B2 BUS IN BUS OUT BUS IN END 6852A009 Figure 2 3 Options for connecting the bus and termination resistor of Fieldline Stand Alone devices A Connection via BUS IN BUS OUT A1 Incoming and outgoing bus
15. are reserved and are indicated as 0 The Invoke ID had been mir rored and the status indicates that the communication was error free 6852 en _02 PHOENIX CONTACT 4 11 FLS FLM PB SYS PRO UME 4 12 PHOENIX CONTACT THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS 4 Example Writing the Config Table for channel 3 on the connected FLM Al 4 SF Slot 3 Index 0080 Subindex 3 Write request master gt slave 5F 03 2F 08 07 00 00 80 03 020301 DP V1 Write Slot Index Length Write PCP Request Invoke ID PCP Index high PCP Index low PCP Subindex Length of the PCP object data PCP object data Write response slave gt master Data Structure DP V1 Write Slot Index Length Data 5F 03 2F 08 Read request master gt slave Data Structure DP V1 Read Slot Index Maximum Length Data 5E 03 2F 20 Read response slave gt master 5E 03 2F 03 87 00 00 DP V1 Read Slot Index Actual Length Write PCP Response Invoke ID Status In the Read Response the mirrored Invoke ID is the result and the status is 00 6852 en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Acyclic Communication DP V1 and PCP 5 Example In the event of an error reading faulty object indices on the connected FLM Al 4SF Slot 3 Index 0180 Write request master gt slave 5F 03 2F 05 06 00 01 80 00 DP V1 Write Slot Index Length Read PCP Request Invoke ID PCP Index high P
16. attribute inconsistent A service parameter has been specified with a value that is not permit ted Cause For example an incorrect length specification or subindex that is not permitted Remedy Check the parameters in the object description and send the service again with the corrected values 6852 en 02 PHOENIX CONTACT A 1 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME Communication Error Messages Table A 4 O6nex O6hex object access unsupported Meaning The service used cannot be applied to this object For example a program sequence can be started or stopped but not read Remedy Check the object description to find out which services are supported for this object Table A 5 O6hax 07hex object non existent Meaning The object does not exist The index parameter probably contains an invalid value Check the object index in the object description and send the service again Other Error Messages Table A 6 O8hex OOpex application error Meaning Device specific error message no communication error cause PN GE Refer to your device description Depending on the I O device other specific error codes may also be used These codes IS are listed in the relevant data sheet A 2 PHOENIX CONTACT 6852 en 02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Appendix A2 Error Codes for DP V1 and VC1 Communication N Always observe the individual display
17. be mixed up Socket AC B Figure 2 8 Difference between A and B encoding connections on the device 6851A005 6852 en _ 02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Connecting Bus Cables and Setting the Address 2 4 Setting the Address The address of a device device ID station address is set using two rotary encoding switches Rotary encoding switch X10 is used to specify the tens and switch X1 is used to specify the units of the device ID le 1 2 ooo SEY TE NS OUT 7 gt O 2MBD UL 6852B004 Figure 2 9 Rotary encoding switches FLS FLM X10 2 on 4 X10 12 4 g 6 10 4 6 X1 X10 904 T2 Os E 78 Ore 6651B032 Figure 2 10 Example Setting address 46 Adjust the rotary encoding switches using a suitable screwdriver blade width 3 5 mm Use of an unsuitable tool may damage the rotary encoding switches Set the station address immediately after installation and before connecting the supply voltages The station address which the PROFIBUS master uses to address the Fieldline Stand Alone device is set in the range between 1 and 99 using both rotary encoding switches The station address which the PROFIBUS master uses to address the Fieldline Modular device is set in the range between 1 and 126 using both rotary encoding switches Another address cannot be set Therefore do not turn rotary encoding switch X10 past position 9 FLS or 12 FLM The stat
18. bytes in order to display 15 devices If 25 devices are configured you will need 4 bytes On a write action at least as many bytes are to be used that the activation status for each device can be transmitted It is also possible to transmit more bytes However only up to 8 bytes can be transmitted because the station can only manage a maximum of 63 devices PHOENIX CONTACT 3 29 FLS FLM PB SYS PRO UME 3 30 PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS On read action the number of data specifies the number of configured and accessible de vices If e g k 18 devices are configured you will receive the response m 3 1 byte The following is valid for bytes on and behind position 5 Status and specification are identical Activated and connected Write 1 Read 1 Not activated and not connected Write 0 Read 0 Status and specification in conflict Activated but not connected Write 1 Read O Not activated but connected Write 0 Read 1 Since the specification must be identical with the connected devices you can derive from the comparison of the desired state in the output data with the real state in the input data and a simple specification of the activation whether and which devices are present or not An example for the access onto index 7 is illustrated in section 5 3 3 on page 5 7 pp Index 12 Device Diagnostics Function Station diagnos
19. in again This option is only useful if those devices are connected where object 18 Diag State is implemented Usually this includes all Fieldline Modular devices using PCP For this reason check in the respective data sheet whether the device supports PCP Bit 3 can be used in the context of dynamic configuration If a new activation status has been given via object 6 or 7 it is obligatory If in the course of this the connection to the PROFIBUS master is interrupted and if the original parameterization is transmitted by the master during restart the activation status is maintained The dynamic configuration needs not to be executed again However if the activation status is set back during restart set bit 3 once after having exe cuted a dynamic configuration via index 6 or 7 In this way both possibilities are available 6852 en _02 PHOENIX CONTACT 3 27 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME Restart with original configuration Restart with the latest dynamic configuration Index 5 PCP Status Function Position and communication status PCP devices Access Read Length 3 bytes per PCP device gt maximum 48 bytes Structure Byte 1 Position in the station slot number Byte 2 Status of PCP connection OOpex NO connection Ope connection ok FFhex error during connection establishment Byte 3 Reserved Index 6 Enabling a Device Function De activating I O
20. note that adjustments to the configuration and actual structure are also carried I gt out for inactive devices A message is displayed if deactivated devices are connected Properties DP slave Address ID Parameter Assignment Cancel Help Figure 5 3 Activating deactivating a device 5 2 PHOENIX CONTACT 6852_en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Dynamic Configuration Following activation deactivation the configuration can be saved translated and down loaded as usual Depending on the device type substitute values DO and AO to be output in the event of an error can also be set at this point for example Furthermore inputs Al can be para meterized This is also carried out via the dialog box shown in Figure 5 3 5 2 Principle of the Dynamic Configuration In dynamic configuration a maximum configuration is specified during configuration The addresses are thus reserved in the PLC Any subgroup of this maximum configuration can be operated Such a group can be selected and activated during configuration and during run time The advantage is that the application can divide an identical hardware configura tion into active and inactive devices Optional devices that are only required for additional functions need not to be connected They can simply be deactivated by the application If an extension is to be realized later on the application can activate the new devices Pre requisite is only
21. shortest route Avoid extending the PROFIBUS cables with connectors Do not lay PROFIBUS cables in bundles with telephone lines and cables leading to potentially explosive areas Asa rule avoid branch lines 1 3 5 Mains Termination Resistors In PROFIBUS DP the individual branches must each be terminated with a termination resistor The Fieldline devices do not have a resistor of this type For recommended termination resistors please refer to the device specific data sheet It is either screwed on to the BUS OUT connection or if T pieces are used for Fieldline Stand Alone devices screwed onto the open connection of the T piece 1 3 6 Assembly Guidelines for PROFIBUS Networks Important information on system planning installation instructions when using PROFIBUS and starting up PROFIBUS systems can be found in the assembly guidelines for PROFIBUS This information is published by the PROFIBUS user organization see also www profibus com If you are designing your system with Fieldline and PROFIBUS you must observe the information provided in the documentation in section 1 2 as well as the assembly guide lines for PROFIBUS 6852 en_02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Fieldline at the PROFIBUS DP 1 3 7 Fieldline Modular Local Bus A Fieldline Modular local bus is a bus connection that branches off from a remote bus via a bus coupler FLM BK PB and connects
22. valid as I gt soon as the bus is restarted 2 corresponding examples If as described in this example the configuration and the accessible devices are not identical because e g 2 devices are not connected the bus is read in continuously until it is identical with the configuration In the course of this the activation status on Index 6 is evaluated automatically If the dynamic bus structure is expanded and if previously inactive devices are attached to the end these devices are activated via Index 6 at first During the next bus start the new devices are integrated into data traffic The bus can be started via Index 4 bit 0 Please note that during reset the device output data are reset to their device specific reset values If the continuous bus structure is expanded and previously inactive devices are attached to the end device activation and bus restart can simultaneously be realized via Index 7 In the course of this the new devices are integrated into data traffic Please note that during reset the device output data are reset to their device specific reset values 6852 en 02 PHOENIX CONTACT 5 7 FLS FLM PB SYS PRO UME 5 8 PHOENIX CONTACT THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS 4 Words VC1 Write request master gt slave start fragment Data 4 Words VC1 Data Structure 14 00 00 00 06 00 08 F2 Write Slot Invoke ID Index High Index Low Subindex Length 1 byte data Write resp
23. 03 00 03 01 1 Continue fragment 7 bytes PCP object data Write response slave gt master Data 4 Words VC1 Data Structure 21 100 00 00 00 00 00 00 Response 7 bytes unused Write request master gt slave end fragment Data 4 Words VC1 Data Structure 40 00 00 00 00 I 00 00 00 End fragment 4 bytes PCP object data 3 Byte unused Write response slave gt master Data 4 Words VC1 Data Structure 87 00 I 00 00 00 00 00 00 Response Status 6 bytes unused Clear request master gt slave Data 4 Words VC1 Data Structure 00 00 00 00 00 00 00 00 Clear Request 7 bytes unused Clear Response slave gt master Data 4 Words VC1 Data Structure 00 00 00 00 00 00 00 00 Clear Response Here the Write specification is given in 3 fragments Only after the reception of the last fragments the bus coupler takes over the request The response 87 shows that the 07 command was executed The status 0 shows that the transmission was successful Via Clear the communication data can be reset to the initial state 6852 en _02 PHOENIX CONTACT 4 25 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME 5 Example In the event of an error Reading faulty object indices on the connected FLM Al 4SF slot 3 index 0180 Read request master gt slave start fragment Data 4 Words VC1 Data Structure 06 03 00 01 80 00 I 00 00 Read Request I O Slot Invoke ID Ind
24. 1 service negative gt lt Error decode gt lt Error code 1 gt lt Error code 2 gt Foran I O device error lt DP V1 service positive gt lt Slot gt lt DP V1 index gt lt DP V1 length gt lt Error data PCP DP V1 gt The lt Data PCP DP V1 gt is optional depending on the service and has the following structure Table 4 3 Structure of the data depending on the service sevice Date I O device PCP Write index Length PCP Data x Byte PCP Object Data DP V1 Read Response Write PCP Ack Invoke ID Status Read objects DP V1 Write Request PCP Read PCP Reg Invoke ID Index High Index Low I O device Read Subindex DP V1 Read Response Read PCP Ack Invoke ID Status Length of PCP data x bytes of PCP object data The meanings of the individual parameters are as follows lt DP V1 service gt In the request there is a distinction between DP V1 Read 5E and DP V1 Write 5Fhex in the error response there is a distinction between DEpex Read error and DFhex Write error 6852 en 02 PHOENIX CONTACT 4 7 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME lt Slot gt The slot of the device to be addressed in the station The bus coupler is addressed with slot 0 the integrated DI 8 is addressed with slot 1 and starting with the first connected device with slot 2 up to 63 lt DP V1 index gt During accesses onto the PCP object
25. A2 Incoming bus and termination resistor B Connection via T piece B1 Incoming and outgoing bus B2 Incoming bus and termination resistor 1 Termination resistor 2 Protective cap for the unused connection 6852 en _02 PHOENIX CONTACT 2 3 FLS FLM PB SYS PRO UME onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLM For a Fieldline Modular device the incoming and the outgoing bus must be connected Figure 2 4 A1 For the last device of a PROFIBUS segment only the incoming bus is connected Figure 2 4 A2 A termination resistor 1 is placed in the connection for the outgoing bus Figure 2 4 Al A2 2 4 PHOENIX CONTACT BU UL MD LB e et BF RUN SE o nf PE OU X1 EOD 4 Ka o 1422 x1 4 OUT er UL MD LB 0 BF RUN Xe 11 2 X10 es OU o 6852B009 Options for connecting the bus and termination resistor of Fieldline Modular devices Connection via BUS IN BUS OUT Incoming and outgoing bus Incoming bus and termination resistor Termination resistor 6852_en_02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Connecting Bus Cables and Setting the Address 2 3 Connecting the Bus Connect the PROFIBUS via BUS IN BUS OUT or via a T piece for FLS only see section Connection Options for the Bus on page 2 1 LB IN LB OUT N 6625A004 Figure 2 5 PROFIBUS DP pin assignment connections on the dev
26. CP Index low PCP Subindex Write response slave gt master 5F 03 2F 05 DP V1 Write Slot Index Length Read request master gt slave 5E 03 2F 20 DP V1 Read Slot Index Maximum Length Read response slave gt master 5E 03 2F 07 86 00 44 06 070000 DP V1 Read Slot Index Actual Length PCP Read Response Invoke ID Status Error Data PCP The status byte 44 characterizes an error during execution In this case the PCP Read Request is transmitted to the I O device first However the I O device does not know this index and acknowledges it using the error code 06 07 In accordance with the section Er ror Codes for PCP Communication on page A 1 this means that the object does not ex ist The last 2 bytes are also part of the PCP error data however they are not used in this example If it does not equal zero the respective data I O device data sheet contains more detailed information 6852 en _02 PHOENIX CONTACT 4 13 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME 6 Example In the Event of an Error Reading an object on a device without PCP Slot 2 Index 0080 Write request master gt slave 5F 02 2F 05 06 00 00 80 00 DP V1 Write Slot Index Length Read PCP Request Invoke ID PCP Index high PCP Index low PCP Subindex Write response slave gt master DF 80 D2 00 DP V1 Write Error Error Decode Error Code1 Error Code 2
27. CTRONIC COMPONENTS FLS FLM PB SYS PRO UME 5 6 5 3 2 Options for Specifying the Active Configuration In the following example the 8 channel digital devices are not part of the station i e these devices are part of the maximum configuration but are to be deactivated at this station There are two options for startup 1 Deactivating devices in the hardware configuration per default This option can easily be realized Having set the Module activation parameters to inactive the configuration can be downloaded to the controller as usual see Acti vating deactivating a device on page 5 2 2 Via DP V1 or DP VO with maximum configuration and final specification in the application Specify the maximum configuration in the hardware configuration and download it Goto cyclic data exchange On the I O devices no data are exchanged as long as the connected configuration is not identical with the accessible activated devices Specify the configuration connected to the station in a non volatile memory via Index 6 or Index 7 Data exchange is started For the second option the example from Figure page 5 5 is used and the DI 8 as well as the DO 8 is activated via DP VO and DP V1 In each case the data are to be written is in dicated For further information on the protocol please refer to section Acyclic Communi cation in DP V1 Mode on page 4 6 and section Acyclic Communication in DP VO Mode via Proces
28. LM PB SYS PRO UME Replacement strategy in local bus Properties DP slave x Address ID Parameter Assignment Value Bas Station parameters dn E3 Device speciic parameters Behaviour on PB Failure Output 0 r Replacement Value Channel 1 E Replacement Value Channel 2 Hald last Value Replacement Value Channel 3 switch replacement value Replacement Value Channel 4 Hex parameter assignment Cancel Help Figure 3 13 Presetting substitute values During errors in PROFIBUS or when the control system fails you can check the correct future behavior of the outputs Here you have the following options output of the value O maintains last value select substitute value can be set I gt The response monitoring on the slave must be activated so that the settings are activated 3 16 PHOENIX CONTACT 6852 en 02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configuration and Startup Adapting the data format When using 16 channel digital devices you have the possibility to adapt the data format to to the control system the control system Here the inputs and outputs of the connectors 1 to 4 and 5 to 8 can either be copied onto byte 1 and byte O or the other way around i e connector 1 to 4 and 5 to 8 are copied onto byte O and 1 Properties DP slave General Parameter Assignment Value Station parameters E DP Interupt
29. MPONENTS Configuration and Startup 3 4 Functions of the FLM BK PB M12 DI 8 M12 3 4 1 Parameters Besides the PROFIBUS standard functionalities you have the possibility to select different additional functions in the Parameterize dialog of your configuration tool after having im ported the GSD file as well as the configuration of the station Properties DP slave Address D PFarameter Assignment Value ie Station parameters 7 J Device speciic parameters _ Y v Y Y D Y Y 2 2 E Filter Channel 1 Format Channel 1 Input Range Channel 1 O up to 10 z Filter Channel 2 un to io vo En EO Format Channel 2 Input Range Channel 2 Filter Channel 3 Format Channel 3 Input Range Channel 3 4 Filter Channel 4 16 Values Format Channe ormed Representation E Forme Channel 4 Input Range Channe up to H Ch 4 Oy 10 Het parameter assignment mn Figure 3 12 Parameters for the FLM Al 4 SF M12 device Especially for the analog I O devices you have the option to set parameters in order to adapt the device to the individual requirements For example you could preset a measur ing range or a data format This option is prepared in the GSD file and can be accessed under the features of the corresponding I O device PHOENIX CONTACT 3 15 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS F
30. Mode General DP parameters Device specific parameters Behaviour on lost 1 0 modules Acknowledge of peripheral Faults channel wize Diagnostics 0116 0016 byte position Byte xfet 1 Plug 5 6 1 4 Hex parameter assignment Bute wel Plug BEA Bute s Plug Cancel Help Figure 3 14 Adapting the data format to the control system 6852 en 02 PHOENIX CONTACT 3 17 3 18 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME Operation during device In the event of a device failure in the local bus you can either continue to operate the re failure on the local bus maining still available devices or you can stop the local bus until all devices are available Properties DP slave General Parameter Assignment Parameters Value Sy Station parameters DP Interrupt Mode J General OP parameters J Device speciic parameters 2 Behaviour on lost 1 0 modules Acknowledge of peripheral Faults Local Bus Stop Local Eu E too Local Bus Aun Byte sve Plug 5 6 1 4 channel w se Diagnostics 0116 0016 bete position Hex parameter assignment Cancel Help Figure 3 15 Operation during device failure on the local bus If you select restart using those devices that are still available please note that the out IS puts will be temporarily reset during a restart With the Stop setting the local bus only starts if
31. NTERBUS 5745 7_300 PROJECT ETHE D ASIEMENS STEP7 E kam PROJECT PROFI D SIEMENS STEP SExamp 7_300_DemoTa E Thomas Step _Programrr 57_400 DemoTa E Thomas Step _Programrr 57_400 Lasco E Thomas Step _Programrr 2Dt01_01_STEP D SIEMENS STEP Exame ef gt Type Project 7 Storage location path Browse EST homas Step _Programme L_a Cort Heb Press F1 for help nj i Figure 3 1 Creating a new project 3 4 PHOENIX CONTACT 6852 en 02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configuration and Startup Inserting a new SIMATIC Insert a station using the Insert Station SIMATIC 300 Station menu item S7 station into the project In this example a SIMATIC 300 Station has been selected RJ SIMATIC Manager Example E Thomas Step 7_Programme Example If x Ep File Edit BRS PLC View Options Window Help l x 3 A Station SIMATIC 400 Station Norte W DIE Subnet SIMATIC 300 Station S lt No Filter gt y x2 Program gt 3 Other Station oon SSIMATICH Station B7 Block _ SSIMATIC PC Station eee rem Sumibol Table External Source kilen Inserts SIMATIC 300 Station at the cursor position Figure 3 2 Inserting a new SIMATIC s7 station into the project 6852 en 02 PHOENIX CONTACT 3 5 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME On the left hand side of the project w
32. RO UME 3 32 PHOENIX CONTACT 3 6 2 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Slot 1 On slot 1 indices are implemented with regard to the integrated DI 8 Index 13 Function Access Length 3 6 3 PD IN Input data of the integrated DI 8 Read 1 bytes Slot 2 to 63 On slot 2 63 indices are implemented with regard to connectable I O devices Index 13 Function Access Length Index 47 Function Access Length Structure Note PD IN Input data on the slot of connected devices Read O up to 128 bytes PCP Access Read and write of PCP data on connected devices via DP V1 Read and write Depending on the command and the PCP object See section 4 4 on page 4 6 pp During access via DP VO the PCP objects can be accessed directly via index 47 6852 en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Acyclic Communication DP V1 and PCP 4 Acyclic Communication DP V1 and PCP DP V1 DP V1 expands the cyclic data exchange function according to IEC 61158 to include acy clic services This makes it easy to operate even complex devices PCP PCP is used in the local bus to exchange data acyclically Usually parameterization data of complex devices or data with variable length e g FLM DIO 16 16 M12 8 DIAG are used DP V1 is a mechanism which corresponds to PCP and PROFIBUS The FLM BK PB M12 DI 8 M12 bus coupler prepares the data records which are sent via DP V1 from the C1 o
33. SYS INST UM E user manual Order No 26 98 97 3 and the device specific data sheet For PROFIBUS DP there are two ways of connecting the bus 1 Connect the incoming PROFIBUS to the BUS IN socket and the outgoing PROFIBUS to the BUS OUT socket 2 When using Fieldline Stand Alone you can also connect the PROFIBUS via a T piece When using Fieldline Stand Alone the PROFIBUS DP can be connected via the BUS IN and BUS OUT connections or via T pieces up to a maximum transmission speed of 1 5 Mbaud If higher transmission speeds are used the bus must be connected via T pieces with integrated series inductance For transmission rates of more than 3 MBaud series inductance is available in the Fieldline Modular devices For this reason we recommend to connect Fieldline Modular de vices via BUS IN and BUS OUT Please observe the installation instructions of the PROFIBUS User Organization 6852_en_02 PHOENIX CONTACT 2 1 FLS FLM PB SYS PRO UME BUS IN BUS OUT T piece FLS 2 2 PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS 6852B002 Figure 2 1 Bus connection via BUS IN BUS OUT Accessories Two M12 connectors Advantage No additional accessories required Disadvantage When the bus is running no devices can be removed or added without physical interruption Supports transmission rates of up to 1 5 Mbaud FLS For Fieldline Stand Alone devices f
34. T 1 1 FLS FLM PB SYS PRO UME 1 2 PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS 1 2 Documentation for Fieldline Devices The documentation for Fieldline devices is modular providing you with the optimum information for your specific bus system This user manual describes only the PROFIBUS specific features of the devices You also require the following documentation Installation of Devices in the Fieldline Product Range FLS FLM SYS INST UM E Order No 26 98 97 3 This user manual describes the devices for all bus systems This includes The device properties which are the same for all bus systems Mounting The voltage supply concept and connection Device Specific Data Sheet The data sheet describes the specific properties of a device This includes Function Local diagnostic and status indicators Connector pin assignment and connection example Configuration data Technical data 6852 en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Fieldline at the PROFIBUS DP PROFIBUS DP 1 3 PROFIBUS was developed as an open fieldbus in 1983 and was standardized in DIN 19245 in 1991 In 1996 PROFIBUS was defined as the European standard in EN 50170 Structure of PROFIBUS DP 1 3 1 S1
35. a bus reset takes place Length 5 up to a maximum of 12 bytes O8hex OOnex O7nex Length of data n 1 2 3 4 5 6 7 8 XXX XK XK XK XX X Bit 0 Device and slot inactive Bit 1 Device and slot active 6852 en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Dynamic Configuration 5 3 Startup 5 3 1 Planning Configuration Figure 5 4 shows an example of the maximum configuration as provided All devices are activated by default PROFIBUS 1 OP Mastersystem 1 rf 3 FLM BK El a CO OD on CT En aa j ea Figure 5 4 Configuration in the STEP 7 hardware configurator The accesses onto the indices 4 and 6 described in the introduction can either be realized via PROFIBUS DP V1 or via the process data interface Index 7 is intended to be used if no DP V1 master exists or if the specification as well as the bus restart are to be realized using one single service in the process data interface only If the process data interface is used the effort is minimized For the access via process data please configure the so called VC1 process data inter face This is the PD PCP x Words x 4 6 16 module You can specify it as first or as last module in the station and you can select the data width and address in accordance with the options in the CPU The residual devices can be configured as usual 6852_en_02 PHOENIX CONTACT 5 5 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELE
36. als we would appreciate it if you would send us your comments Please use the universal fax form at the end of the manual for this Statement of Legal Authority This manual including all illustrations contained herein is copyright protected Use of this manual by any third party deviating from the copyright provision is forbidden Reproduction translation or electronic and photographic archiving or alteration requires the express written consent of Phoenix Contact Violators are liable for damages Phoenix Contact reserves the right to make any technical changes that serve the purpose of technical progress Internet Up to date information on Phoenix Contact products can be found on the Internet at www phoenixcontact com 6852 en_02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Table of Contents 1 Fieldline at the PROFIBUS DP aan aaneen eeen eeenenenenenerenerenerenenenensnensnerenerenersnenen 1 1 1 1 The Fieldline Product Range unun nnen ers enners ennen eneen venten ennnenvennenenn 1 1 1 2 Documentation for Fieldline Devic S n nnunrnnnenreneenenn vaneen ennen vennen eeens 1 2 1 3 PROFIBU DIR es ea een 1 3 1 3 1 Structure of PROFIBUS DP u 1 3 1 3 2 18 0 ee ee ee 1 5 1 3 3 Baud Rale sersa E Ea A EERE 1 5 1 3 4 Laying the PROFIBUS Cable nnn onnnnen eenn ennnn enen nene 1 6 1 3 5 Mains Termination Resistors an aannsennnr venen venen eenen venen
37. an be used to transmit communication data PCP and is not linked to a specific device During active process data exchange it is possible to assign the VC1 device sequentially to different devices with communication objects and to exchange parameter data parallel to the process data Process data width The process data width occupied by the VC1 devices in the process data channel can be selected from 4 to 16 words in increments of 2 words This means that communication ob jects can be used even if resources are scarce If there are sufficient free resources a data width of up to 16 words can be used providing the same ease of operation as for DP V1 communication As the data width of the VC1 devices is between 4 and 16 words but the user data can be up to 72 bytes 36 words per communication it may be necessary to split the data and transmit it in several steps This leads to Start fragment Continue fragment End fragment Error or abort fragment Each fragment contains a service byte which is used for the precise assignment of the fragment The individual fragments and the service byte are explained in detail in the fol lowing The VC1 device listed as PD PCP x words in the GDS file can be configured at any AN position behind the FLM BK PB M12 DI 8 M12 bus coupler We recommend to configure the VC1 device at the last position In this way the configured slot and the actual slot occupied by the I O device will al
38. and Startup 3 3 Configuration and Startup Using the STEP 7 SIMATIC Manager This section describes an example of configuration and startup using the STEP 7 Sl MATIC Manager English Version 5 1 Service Pack 3 Release K5 1 3 0 You can apply the procedures to other similar software PROFIBUS network is installed Termination resistors are specified PROFIBUS addresses on the device are set Baud rate is specified If FLM devices with a data width of less than 5 bits and with the same ID and length code are connected next to each other they are automatically packed during auto configura tion i e their data is combined If you carry out the configuration yourself using a hard ware configurator e g the Siemens STEP 7 SIMATIC Manager the automatic configuration in the station is overwritten Start the STEP 7 SIMATIC Manager under Windows PHOENIX CONTACT 3 3 components com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME Creating a new Call the New dialog box using the File New menu item Enter the desired name In this project example the name Example has been chosen If necessary change the project type and storage location Confirm the entry with OK or Return The project Example is saved SIMATIC Manager File PLC View Options Window Help Dealer wl rel New project New library Name Example IBSWDO10 2 D I
39. aster gt slave Data Data Structure 5F 00 04 01 01 DP V1 Write Slot Index Length 1 byte of data Write response slave gt master Data Structure DP V1 Write Slot Index Length Data 5F 00 04 01 The data block is only important in the request The response indicates that the command has been received As can be seen in Object Dictionary on page 3 27 the local bus is restarted using bit O O1hex at index 4 slot O 4 10 PHOENIX CONTACT 6852_en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Acyclic Communication DP V1 and PCP 3 Example Reading the Config Table on the connected FLM Al 4 SF slot 3 index 0080 Write request master gt slave 5F 03 2F 05 06 00 00 80 00 DP V1 Write Slot Index Length Read PCP Request Invoke ID PCP Index high PCP Index low PCP Subindex Write response slave gt master 5F 03 2F 05 DP V1 Write Slot Index Length Read request master gt slave 5E 03 2F 20 DP V1 Read Slot Index Maximum Length Read response slave gt master 5E 03 2F 10 86 00 00 OC 03 01 03 DP V1 Read Slot Index Actual Length 00 03 01 03 00 00 00 00 00 PCP Read Response Invoke ID Status Length of PCP data 12 bytes of PCP object data In the Read Response the user will receive the 12 bytes of object 80 on the FLM Al 4 SF as described above The settings on channel 1 and 3 are identical as well as of channel 2 and 4 Bytes 9 and 12
40. ation level and thus also reserve memory in the PLC However optional devices must not be connected They can be de activated in the configuration If the station is subsequently expanded to include previously deactivated devices the new devices can be connected and activated in the hardware configurator gt r FLM BK PB M12 DIS M12 Slot f Module Order number Address O Address Comment i ee 2 3 66 FMA4SFM2 ja 4 5 66 FMDBM2 fe 6 130 FMDOBM2 O 7 g See 11 Figure 5 1 Configuration table in the STEP 7 hardware configurator The configuration e g in STEP 7 is carried out in the same way as for other modular slaves The configuration can be created from the hardware catalog using drag amp drop see Figure 5 1 PHOENIX CONTACT 5 1 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME Open the Properties dialog box by double clicking on a device Properties DP slave Address I Parameter Assignment li pe Breet Erit Input Address Length rt Eongeletent over Start i Byte ri uni ri 24 End Process image partition 081 PI ri Wate for Specic Menace EES Mieeimun 14 bytes heradecimal separated y camma on blank space Cancel Help Figure 5 2 DI 8 features dialog The Parameter Assignment tab can be used to specify whether a device should be active or inactive see Figure 5 3 Please
41. ck including the header is given The minimum length of this block is 2 the maximum length is 9 The size of the ID specific diagnostics block also depends on the number of the configured devices Block 3 Status PDU Device Status For every local bus device there are 2 bits for status coding ST LT x 00 Device data are valid ST LT x 01 Device data are invalid because of an error ST LT x 11 Device data are invalid because the wrong module had been connected ST LT x 11 Device data are invalid or no device has been connected despite con figuration The specifier SP equals 1 in the event of a faulty state The specifier equals 2 if the device changes from a faulty into an error free state If the specifier equals O the state did not change 3 24 PHOENIX CONTACT 6852 en _02 6852 en 02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configuration and Startup SP 0 No evaluation SP 1 An error occurs number gt 0 SP 2 An error disappears number 0 SP 3 Reserved In the first byte of the block in bit O up to 5 the length L of the entire status PDU block in cluding the header is given The minimum length of this block is 5 the maximum length is 20 The size of the status PDU block also depends on the number of the configured de vices Block 4 Channel Specific Diagnostics Up to 10 channel errors are indicated here Each channel error is an individual and inde pendent er
42. d Byte 12 indicates the number of available devices The FLM BK PB M12 DI 8 M12 is always counted as local bus device LT If an error occurs on this device the corresponding bits in the diagnostics are set for local bus de vice 1 6852 en_02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configuration and Startup 3 6 Object Dictionary 3 6 1 Slot 0 On slot 0 the following station specific indices are implemented Index 3 PDU Length Function Data width of the virtual C1 module process data interface for acyclic communication in bytes Access Read Length 1 bytes Note For DP VO access only Index 4 Master Control Function Control bits for station Access Write Length 1 bytes Structure Bit 0 Restart local bus Bit 1 Acknowledge PF Bit 2 Update diagnostics evaluation of index 18 on PCP devices Bit 3 Unlock dynamic configuration Bit 4 Reserved set to 0 Bit 5 Reserved set to 0 Bit 6 Reserved set to 0 Bit 7 Reserved set to 0 With the help of bit 0 the local bus can be restarted anytime If a new activation status has been given via index 6 it is used for this restart Please note that during reset the device output data are reset to their device specific reset values With bit 1 errors that have to be acknowledged can be set back This function has been prepared for future devices Set bit 2 if the diagnostics of all connected devices is to be read
43. ddress is set using the rotary encoding switches see section Setting the Address on page 2 7 1 3 3 Baud Rate Fieldline devices for PROFIBUS DP have an automatic baud rate detection function which therefore must not be set After power up the Fieldline device detects the baud rate and stores it as long as the supply voltage is present If you modify the baud rate of the master you must disconnect and reconnect the supply IEY voltage for the Fieldline Stand Alone device so that it detects the modified baud rate The bus cables for the PROFIBUS DP system are specified in standard EN 50170 Ac cording to this standard the maximum length of a bus segment depends on the baud rate Table 1 2 Baud rate and line lengths Baud Rate in 93 75 187 5 kbps Length of branch lines in lt 6 6 None m IS Only one baud rate can be used at a time in a PROFIBUS system 6852 en 02 PHOENIX CONTACT 1 5 FLS FLM PB SYS PRO UME 1 6 PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS 1 3 4 Laying the PROFIBUS Cable When laying a PROFIBUS cable please observe the following Donot lay signal and bus cables parallel to power cables or in bundles with power ca bles Lay PROFIBUS cables and cables with direct voltages gt 60 V and alternating voltages gt 25 V in separate bundles or cable ducts Always lay signal cables and equipotential bonding together in one channel following the
44. devices Access Read and write Length 8 bytes Structure Byte 1 Byte 2 Bytes 3 Byte 8 to 7 tjejsjejsjejrjeje joo lili 13 Ita fis jie 57 58 se eo 61 62 63 x Bit 0 Device and slot inactive Bit 1 Device and slot active 3 28 PHOENIX CONTACT 6852 en _02 6852 en 02 Index 7 Function Access Length Struc ture THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configuration and Startup Activating a Device Restart De activating I O devices bus restart write number of devices and status read Simultaneously read and write via DP VO with command 08 3 byte header 1 byte length specification up to n 8 bytes for up to 63 devices Write eves h 2 Js ja 8 es 7 e lay _ Bit 0 Device and slot inactive Bit 1 Device and slot active Read Write Response Byte 3 Length of the following data m Number of accessible devices k Byes 1 2 j4 Is e 7 8 os do T C ST C S ee o o Bit 0 Device and slot inactive Bit 1 Device and slot active This object is especially intended for use under DP VO The data length of the write is al ways depending on the number of configured devices In this context the number of de activated devices is entirely irrelevant If e g you configured 15 devices 4 of which are to be deactivated and 11 of which are to be activated only the number of configured devices is relevant In this case you would need 2
45. devices can be found on the Internet at www download phoenixcontact com 6852 en 02 PHOENIX CONTACT B 1 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME B 2 PHOENIX CONTACT 6852_en_02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS We Are Interested in Your Opinion We would like to hear your comments and suggestions concerning this docu ment We review and consider all comments for inclusion in future documentation Please fill out the form on the following page and fax it to us or send your com ments Suggestions for improvement etc to the following address PHOENIX CONTACT GmbH amp Co KG Documentation Services 32823 Blomberg GERMANY Phone 49 0 52 35 3 00 Telefax 49 0 52 35 3 4 20 21 E Mail tecdoc phoenixcontact com FAX Reply PHOENIX CONTACT GmbH amp Co KG Documentation Services From Company Address City ZIP code Country Document Designation FLS FLM PB SYS PRO UME My Opinion on the Document Form Is the table of contents clearly arranged Are the figures diagrams easy to understand helpful Are the written explanations of the figures adequate Date Fax No Name Department Job function Phone Fax Revision 02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS PHCENIX CONTACT 49 0 52 35 3 4 20 21 Order No Does
46. e una anise dns dbi A 1 A 1 Error Codes for PCP Communication ccccceeeeeeeeeeeeeeeeeeeeeeeseaeeeeeseaeeeeeens A 1 A2 Error Codes for DP V1 and VC1 Communication nennen eneen A 3 A3 Format of the Parameter Telegram ccccccceeeeeeeeeeeeeeeeeaaeeeeeeeeeaaaeeeeeeeesaaees A 4 B ADDEN Dee einer Wiener B 1 B 1 Ordering Data mm eeneneneeenern evenaren sonnnen eenen B 1 il PHOENIX CONTACT 6852 en 02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Fieldline at the PROFIBUS DP 1 Fieldline at the PROFIBUS DP 6852 en 02 1 1 The Fieldline Product Range The input and output devices in the Fieldline product range are designed for distributed au tomation tasks in harsh environmental conditions The devices meet the requirements for IP65 IP67 protection They enable the direct connection of sensors and actuators in an en vironment close to the station The Fieldline product range includes the Fieldline Stand Alone FLS and Fieldline Modular FLM product groups Fieldline Stand Alone devices cannot be extended and have a directly integrated fieldbus connection and I O level They are used for distribution in the field when only a few digital I O points are required Fieldline Modular devices consist of a bus coupler gateway and I O devices that can be connected They are used for special functions primarily for applications with a high I O node density and complex functions PHOENIX CONTAC
47. en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Acyclic Communication DP V1 and PCP 3 Example Reading the Config Table on the connected FLM Al 4 SF slot 3 index 0080 Read request master gt slave start fragment Data 4 Words VC1 Data Structure 06 03 00 00 80 00 I 00 00 Read Request I O Slot Invoke ID Index high Index low Subindex 2 Byte unused Read response slave gt master Data 4 Words VC1 Data Structure 96 00 OC 03 01 03 00 03 Read Response Status Length 5 bytes object data Read request master gt slave acknowledgment of start fragment Data 4 Words VC1 Data Structure 96 00 00 00 00 00 00 00 Acknowledgement start fragment 7 bytes un used Read response slave gt master Data 4 Words VC1 Data Structure CO 01 03 00 00 00 00 00 Termination fragment 7 object data bytes In the Read Response the user will receive the 12 bytes of object 80hex on the FLM Al 4 SF as described above The first 5 object data bytes are transmitted in the start fragment The missing 7 bytes follow in the second fragment which is already the last The status byte indicates that the communication was correct 6852 en _02 PHOENIX CONTACT 4 23 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME For the bus coupler the service is finished as soon as the last fragment has been transmit ted If the next service byte differs from the previous the
48. eneen 1 6 1 3 6 Assembly Guidelines for PROFIBUS Networks 1 6 1 3 7 Fieldline Modular Local BUS ann aanneem rene venenn eneen enenvenen 1 7 2 Connecting Bus Cables and Setting the Address oan onanen enn enenenvenen enne renen ennen 2 1 2 1 Connection Options for the BUS cccccseeceecneeeeeeceeeeeeecseeeeseeeeeeeeaaeeesessseeees 2 1 2 2 Connecting the Bus and Termination ReSIStOM cccccssseeeeesseeeeeeaeeeeeeaeeeeees 2 3 2 3 Connecting the Bus SP eneennenenennenen 2 5 2 4 Setting the Address nan aaann enn eennn err ennanenseenneneneennnenrrennneen vennen eeens 2 7 3 Configuration and Startup 0E enen eneenrnennrvenrenenenenned ennen 3 1 3 1 Configuring the PROFIBUS DP System unu eannnnnneneenenseen vennen 3 1 3 2 Installation GMM ME eennennnneennsennrennnrenne ennen esmee 3 2 3 3 Configuration and Startup Using the STEP ZQRAINBRTNO Managesl cccccsssessccecessssssecetsesscesseeesecssoasseersenseeaseserees 3 3 3 4 Functions of the FLM BK PB M12 DI 8 M12 anneer eenennenen 3 15 3 4 1 Pe UNG Seien een 3 15 3 4 2 Local Diagnostic and Status Indicators aaneen 3 21 3 5 Bte ple SNS seele 3 23 3 6 ODIECT DIC ON EN 3 27 3 6 1 OEO are ee ee ee ae 3 27 3 6 2 OL ee ee E een 3 32 3 6 3 EEN 3 32 4 Acyclic Communication DP V1 and PCP an oenner eenen enner enne eenenvenenenenvenen enne rvenenen 4 1 4 1 Acyclic Communication via C1 Master uuu
49. ents follow Depending on the slot this may be bus coupler object data or I O device object data 4 20 PHOENIX CONTACT 6852 en _02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Acyclic Communication DP V1 and PCP lt Data block gt This is only the contents of an object The length and scope of the data has already been described by the lt Length gt parameter To aid understanding the same examples are used in the following section as for DP V1 services This means that the description of the examples for DP V1 communication is valid again here see Section Examples on page 4 9 See also Error Codes for DP V1 and VC1 Communication on page A 3 4 5 2 Examples of VC1 Services 1 Example Reading the connected local PCP devices and their status slot 0 index 5 on the bus coupler Read request master gt slave Data 8 Words VC1 Data Structure 03 00 00 00 05 00 I 00 00 00 00 00 Read Request bus coupler Slot Invoke ID 00 00 00 00 00 Index high Index low Subindex 10 Byte unused Read response slave gt master Data 8 Words Data 8 Words VC1 si Data Data Structure 83 00 06 03 01 00 04 01 00 eN 00 00 Read response bus coupler C Status Actual 00 00 00 00 00 length 6 bytes of object data 7 bytes unused Clear request master gt slave Data 8 Words VC1 Data Structure 00 I 00 00 00 00 00 00 00 00 00 00 Clear Request 15 bytes unused 00 00 00 00 00 Clear respo
50. ex high Index low Subindex 2 bytes unused Write response slave gt master Data 4 Words VC1 Data Structure 86 44 06 07 00 00 I 00 00 Read Response Status 4 bytes error code 2 bytes unused Clear request master gt slave Data 4 Words VC1 Data Structure 00 00 00 00 00 00 00 Clear Request 7 bytes unused Clear Response slave gt master Data 4 Words VC1 Data Structure 00 00 00 00 00 00 00 00 Clear response The status byte 44 characterizes an error during execution In this case the PCP Read Request is transmitted to the I O device first However the I O device does not know the index 0180 and acknowledges it using the error code 06 07 In accordance with the section Appendix on page A 1 this means that the object does not exist The last 2 bytes are also part of the PCP error data however they are not used in this example If it does not equal zero the respective data I O device data sheet contains more detailed informa tion Via Clear the communication data can be reset to the initial state 4 26 PHOENIX CONTACT 6852 en _02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Acyclic Communication DP V1 and PCP 6 Example In the event of an error reading an object on a device without PCP Slot 2 Index 0080 Read request master gt slave Data 4 Words VC1 Data Structure 06 02 00 00 80 00 I 00 00 Read Request Slot Invoke ID Index High Index Low Sub
51. f x 18 x me SD BJ Standard 2 29 Phoenix Contact fy INLINE 2 9 FIELDLINE ii Fe FLS PB M12 DIO4 4 M12 24 FLS PB M12 DIG M12 FLS PB M12 DO8 M12 24 FLS PB M12 DI 16 M12 FLS PB M12 16REL S01 FLM BK PB M12 DI8 M12 PRC Properties DP slave AAI OE UITECLENT Js Sial f GE KMAN 66 FL DIS M12 130 FLMDOBM12 194 66 FLMAI4SFM12 194 LM AD 4 SF M12 ERS 5 6 7 8 3 10 11 12 13 14 15 16 17 FLM DIO 4 4 M12 24A 194 FLM DID 16 16 M12 8 DIAL FLM DIS M12 FLM DIS M12 QTY 2 16Bit FLM DO8 M12 FLM DO8 M12 QTY 2 16 Bi FLM DIO 4 4 M1 2 24 FLM DIO 4 4 QTY 2 8 Bk FLM DIO 4 4 QTY 4 16 Bit FLM Al 4 SF M12 ij g FLMAO 4 SF M12 BC BLOCKLINE CJ ET200eco i g BK3120 Typ 8544 DPV1 VersaPoint Profibus NIU VersaMax IP 4Pt In 4Pt Out Be METU S Dytes NEUE SEPA EEN by Conia Gl ats SPECE area tor Specie Mm anulacurer 6852 en 02 Figure 3 10 Checking or changing I O addresses It is possible to connect additional PROFIBUS DP devices to the DP master system in this case Example and parameterize and address each one according to the device type PHOENIX CONTACT 3 13 FLS FLM PB SYS PRO UME Transfer to the S7 system THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Save and translate the project using the in button or the Station Save and Translate menu item Transfer the project to the S7 system using the da button or the Target System Load to
52. g FLS PB M12DI 16 M12 _ FLS PB MI216REL 501 EEE HA BLOCKLIN ET200eco B 8K3120 ga Typ 8644 DPV1 g VersaPoint Profibus NIU B VersaMax IP 4Pt In 4Pt Out Valves I Gateway fs PLC J Compatible PROFIBUS DP Slaves CJ Closed Loop Controller C Configured Stations 59 DP VO slaves CJ DP AS i LJ DP PA Link 4 ENCODER Cg ET 2008 ET 200C 0 UR jj Ps 307 1 PROFIBUS 1 DP Mastersystem 1 PROFIBUS 1 DP Mastersystem 1 PROFIBUS address Order number Firmware Diagnostic address Comment EE H A EIER Press F1 to get Help Cho 4 Figure 3 7 Select the FLM bus coupler 3 10 PHOENIX CONTACT 6852 en 02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configuration and Startup The Features PROFIBUS interface window opens FLM BK PB M12 DI 8 M12 Check the PROFIBUS address of the bus coupler in the dialog field and if required adjust this according to the application Confirm your entry with OK N HW Config SIMATIC 300 1 Configuration doku ah Station Edit Inset PLC View Options Window Help Diela 4 sl dada SJE we Profle Standard PROFIBUS DP Son ii Fe eli jj PS 307 PROFIBUS 1 DP Mastersystem 1 E Drives em H E 10 Properties PROFIBUS interface FLM BK PB M12 DIS H12 HL VIPA Phoenix Contact General Parameters EED INLINE FIELDLINE
53. ice Supply voltage for active bus connection termination resistor En RxD TxD N A RxD TxD N A EN DGND DGND RXD TXD P B RxD TxD P B Reference potential of the RS 485 transceiver of the station Shield Shield Outgoing bus Placed directly on FE Incoming bus DEN RXD TXD N A green RxD TxD N A DGND DGND aX 3 RxD TxD P B 4 red 4 RxD TxD P B 3 AB 5 Shield Shield 5 Solder side Shield u i Solder side 6852A010 Figure 2 6 Connector pin assignment of the M12 connector connector on the cable IS The thread and pin 5 are used for shielding 6852_en_02 PHOENIX CONTACT 2 5 FLS FLM PB SYS PRO UME Pin assignment of the local bus for Fieldline Modular devices Encoding of the connections 2 6 PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS LB IN UT a O I 6625A004 Figure 2 7 Pin assignment of the local bus FLM PROFIBUS DP cables available on the market usually have one wire pair red and green which is protected by a braided shield and membrane The data lines are labeled A and B If a cable with red and green wires is used you should select the following assignment for both the incoming and outgoing bus Data line A Green Data line B Red Inthe PROFIBUS DP system the connections for the bus are B encoded and the connec tions for the supply voltage are A encoded In this way the bus and supply voltage cannot
54. index 2 bytes unused Write response slave gt master Data 4 Words VC1 Data Structure 86 D2 00 00 00 00 00 00 Read Response Status 6 bytes unused Clear request master gt slave Data 4 Words VC1 Data Structure 00 00 00 00 00 00 00 00 Clear Request 7 bytes unused Clear Response slave gt master Data 4 Words VC1 Data Structure 00 00 00 00 00 00 00 00 Clear Response Since the addressed device does not support PCP the request is rejected immediately A message from the bus coupler managing the PCP devices occurs In this case the error code D2 stands for device does not have PCP See also Error Codes for DP V1 and VC1 Communication on page A 3 Via Clear the communication data can be reset to the initial state 6852 en _02 PHOENIX CONTACT 4 27 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME 4 28 PHOENIX CONTACT 6852 en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Dynamic Configuration 5 Dynamic Configuration 6852 en 02 Dynamic configuration is the specification and configuration of a maximum configuration Any subgroup of this maximum configuration can be operated In addition to dynamic configuration empty spaces can be reserved for future expansions 5 1 Empty Spaces It can be helpful to reserve empty spaces for a station which may be used at different con figuration levels You can configure the maximum configur
55. indow click on the small plus box next to the Example folder and select SIMATIC 300 1 RJ SIMATIC Manager Example E T homas Step _Programme E xample BEJ E3 EP File Edit Insert PLC View Options Window Help ma Ee E if El zal B Sal aaf erer ES En lt No Filter gt ae R EP Example Ze Hardware ER SIMATIC 300 1 iel xl Press F1 for help Figure 3 3 Selecting SIMATIC 300 1 The SIMATIC Manager displays the Hardware object in the right hand window Double click on Hardware to start the hardware configurator which can be used to edit the configuration table 3 6 PHOENIX CONTACT 6852_en_02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configuration and Startup Installing a new GSD file The characteristic communication features of a PROFIBUS DP device are defined in the form of an electronic device data sheet GSD device database file The GSD file for the Fieldline devices can be found on the Internet at www phoenixcontact com If this file is not in the system you must import the file into your configuration program Open the PXC_07E9 gsd file via Tools Install New GSD in the dialog box that ap pears oh Hw Config SIMATIC 300 1 Configuration Example Dl Station Edit Insert PLC View MOSES Window Help l x olele Bl 8 ESL Customize Ctrl Alt E Speci Module Configure Network Profile Standard x Spmboleble IH
56. ion address set is read upon system startup and accepted in the device settings gt e amp Changing the switch positions during operation has no effect on the address settings A new address value is only accepted upon device power up Dynamic address modifi cation via the fieldbus is not supported 7 6852_en_02 PHOENIX CONTACT 2 7 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME 2 8 PHOENIX CONTACT 6852_en_02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configuration and Startup 3 Configuration and Startup 3 1 Configuring the PROFIBUS DP System To configure your system proceed as follows e Describe and define the task Specify the device range for the I O devices Specify the type and number of input and output signals e Select the devices required Specify the devices to be installed according to the input and output signals e Consider the system restrictions Take into account the basic system specifications see Table 1 1 on page 1 4 e Select the voltage supply Please refer to the information on the power supply in the FLS FLM SYS INST UM E user manual Order No 26 98 97 3 The selection of suitable voltage supplies always depends on the particular sys tem The following criteria should always be met for the 24 V DC voltage supply Nominal value 24 V Tolerance 25 complies with EN 61131 2 15 20
57. irectory of the FLM Al 4 SF M12 Index Data Type A L Meaning ObjectName Rights 0080hex Array of Unsigned 16 6f 2 Config Table A Number of elements rd Read access permitted L Element length in bytes wr Write access permitted Table 4 5 Object Description Array of Unsigned 16 6 x 2 bytes Subindex OOhex Write all elements Ohr 5 Configuration channel 1 O2hex Configuration channel 2 O3hex Configuration channel 3 O4 nex Configuration channel 4 O5hex Reserved O6hex Reserved Length byte OChex Subindex OOhex O2h y Subindex O1hex to O6hex Device configuration Objects 4 and 4 on the bus coupler are also used in these examples For an explanation regarding these objects please refer to section Object Dictionary on page 3 27 6852_en_02 PHOENIX CONTACT 4 9 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME Example 1 Reading the connected local PCP devices and their status Slot 0 Index 5 on the bus coupler Read request master gt slave 5E 00 05 20 DP V1 Read Slot Index Maximum Length Read request slave gt master 5E 00 05 06 03 01 00 04 01 00 DP V1 Read Slot Index Actual Length 6 bytes object data The data shows that there is one PCP device each on slot 3 and 4 and its connection sta tus is OK see section Object Dictionary on page 3 27 Example 2 Writing the bus restart bit slot 0 index 4 bit 0 on the bus coupler Write request m
58. is indicated when local PCP transmission is complete and in the event of an error Inthe event of an error the data block can provide details An error has occurred if the value of the status byte does not equal OOpex OOrex No error A4nex Error during communication Other errors see Error Codes for DP V1 and VC1 Communication on page A 3 For VC1 the parameters have the following meaning lt Device no gt The FLM BK PB M12 DI 8 M12 bus coupler counts the device as 0 the integrated DI 8 as 1 and starting with the first connected node as device 2 63 lt Invoke ID gt The Invoke ID has a length of one byte and is used for some I O devices only Test it in the respective data sheet at hand lt Index high and Index low gt This specifies the object index of the addressed object in two bytes This is also valid for objects on the FLM BK PB M12 DI 8 M12 bus coupler e g for index 5FEOpex the value 5Fhex Should be entered for Index high and the value EOpex should be entered for Index low For index 4hex on the bus coupler OOhex is Index high and 04 is Index low lt Subindex gt When working with a PCP object the subindex can be used to select a specific element from an array or record Thus the subindex is to be indicated during accesses onto I O de vices The bus coupler has no arrays or records so subindex 0 should be entered lt Length gt This value specifies how many bytes of object data object cont
59. lot x b Receiving the DP V1 Write Response often automatically via the master 2 a Sending a DP V1 Read to slot x b Receiving the DP V1 Read Response often automatically via the master Write 1 a Send the request as DP V1 Write Request PCP Write to slot x b Receiving the DP V1 Write Response often automatically via the master 2 a Sending a DP V1 Read to slot x b Receiving the DP V1 Read Response often automatically via the master 4 6 PHOENIX CONTACT 6852 en _02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Acyclic Communication DP V1 and PCP Note that when communicating with objects on local bus devices the response should be fetched using Read Otherwise the result will be overwritten during the next communica tion Communication is always carried out via DP V1 index 47 and the object index and assigned subindex of the I O device are transmitted as part of the data field Request and Response The section below provides additional information about the format of write and read ac cesses Request and Response The format for all types of access Request and Response positive Read and Write in DP V1 is lt DP V1 header gt lt Data PCP DP V1 gt The DP V1 header for a positive DP V1 response always has the following format lt DP V1 service positive gt lt Slot gt lt DP V1 index gt lt DP V1 length gt In the event of a faulty response the format is as follows Fora DPM error lt DP V
60. mmunication in DP V1 Mode 4 4 1 The Communication Mechanism Data access types accesses onto local bus device data or onto FLM BK PB M12 DI 8 M12 bus coupler data Table 4 2 Objects on the FLM BK PB M12 DI 8 M12 bus coupler Data Type Accessing I O Devices Access to FLM BK PB M12 DI 8 M12 Device PDU Length Master Control PCP Status Enabling a Device Enabling a Device Restart Device diagnostics Cycle Count Cycle Error Count ID Cycle Count ID Cycle Error Count Data Cycle Count Data Cycle Error Count PD IN PCP access PDULengh OP MasterControl 3 x ld Popstaus o T o Enabinga Device _ x ee Enabling a Device Restat OO Device diagnoses A AY Cydecont l OS Cycle Error Cout _ 3 AS DCydeCout _ e ID Cycle Eror Count Data Cycle Count Data Cycle Eror Count ANY s BMO a PDN eN PCPaccess mT During the access onto the FLM BK PB M12 DI 8 M12 bus coupler use the well established DP V1 format Read and write accesses can be executed in one step request gt response The PCP data from I O devices is usually addressed via 16 bit object indices DP V1 only has fields for 8 bit indices Additional parameters have therefore been added to the data block for use when accessing the local bus as for PROFIDrive A sequence involving 2 steps is used which follows the PROFIDrive profile Read 1 a Send the request as DP V1 Write Request PCP Read to s
61. n via SAP49 and 50 If DP V1 devices are already in use the routines for connection man agement can be adapted easily The C2 master can be implemented in various forms e g in the form of a display device or operator interface In a display device the data is fetched from the slave on request if for example a specific parameter is to be read Access to the operator interface is usually acyclic You can connect up to 16 PCP compatible devices to the IRE FLM BK PB M12 DI 8 M12 buscoupler 4 2 PHOENIX CONTACT 6852 en _02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Acyclic Communication DP V1 and PCP 4 3 PCP Communication Basics PCP Peripherals Communication Protocol controls the transmission of parameter data in the local bus Special PCP services are available for this purpose Application Example To explain the basics of PCP communication the following concrete PCP application is used as an example A frequency inverter FI together with other field devices is connected to a PLC via a bus interface The device versions are standardized according to the drives profile PLC Bus interface Master Slaves gz Figure 4 1 Application example Frequency inverter 5067C201 Device parameters Device parameters are data from intelligent field devices PCP devices which is required for the startup phase of machines and sys
62. n ennen ene nen enen ennn een venn 4 1 4 2 Acyclic Communication via C2 Master nun eenn ennn ene saneren ennn eeneenn 4 2 4 3 PCP Communication Basics ccccccsseceeeeeceeeeecaueeeeaueeeeeaeeeseaeeeeeaeeeesaeeesaaes 4 3 4 4 Acyclic Communication in DP V1 Mode nanus eeen eenen eneen een venn 4 6 4 4 1 The Communication Mechanism ccccecccceeeceeceeeeeceeeceaeeeesaeeeseaes 4 6 4 4 2 SEE 4 9 4 5 Acyclic Communication in DP VO Mode via Process Data 4 15 4 5 1 Mechanism for Transmission in the Process Data 4 15 4 5 2 Examples of VC1 Services uuuunuessnsnnnnennnnnnnennnnnnnnnnnnnnennnnnnnn nennen 4 21 6852 en 02 PHOENIX CONTACT i onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UM 5 Dynamic Configuration nun annnnn enn neneeneennenrennneneennnenvennenr vennen eennneneennens ennen v nennen denn 5 1 5 1 EMPII PAC ne en ee ene eee eee ere eee ee eee 5 1 5 2 Principle of the Dynamic Configuration ccccccseeeeeesseeeeeceeeeeeeeceeeeeeeeeeeeseaaess 5 3 5 3 ED o A eu setae ncaa E EEE E E N ER EE N E E A E T 5 5 5 3 1 Planning Configuration nnn nennnneereneennenneene nennen eneen 5 5 5 32 Options for Specifying the Active Configuration nn 5 6 5 3 3 Specification of the Active Configuration via DP VO 5 7 5 3 4 Specification of the Active Configuration via DP V1 nn 5 10 5 3 5 SN A nee een 5 11 Pe APDONAE nungen ernennen O M
63. no End Fragment Byte 1 Service Byte 2 Data block if required Byte n Data block if required Table 4 8 Byte 1 Service in end fragment aye 1 ma Reserved response Bit 7 Request Response O Request 1 Response 6852 en _02 PHOENIX CONTACT 4 17 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME Bit 7 Request Response Bits 6 to 5 Fragment type 10 Last fragment end fragment Bits 4to0 Reserved 4 18 PHOENIX CONTACT 6852_en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Acyclic Communication DP V1 and PCP Abort Error Fragment Byte 1 Service Byte 2 Error code if required Byte n Error code if required Table 4 9 Byte 1 Service in abort error fragment Byte 1 pte o7 6 5 4 tt AN tje response Bit 7 Request response O Request 1 Response Bits 6 to 5 Fragment type 11 Abort error fragment Bits 4 to 0 Reserved IS The communication can reset anytime using OOhex and 60pex 6852 en_02 PHOENIX CONTACT 4 19 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME A response is sent after every request This response indicates that the request has been received and shows its current status Response Structure Byte 1 Service mirrored request with set response bit Byte 2 Status if required Byte 3 Length only on first read response Byte n Data block if required The status
64. nse slave gt master Data 8 Words VC1 Data Structure 00 00 00 00 00 00 00 00 00 00 00 00 Clear response 00 00 00 00 The status byte equals zero This means that the communication was correct The data shows that there is one PCP device each on slot 3 and 4 and its connection status is OK see section Object Dictionary on page 3 27 Via Clear the communication data can be reset to the initial state 6852_en_02 PHOENIX CONTACT 4 21 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME 2 Example Writing the bus restart bit slot 0 index 4 bit 0 on the bus coupler Write request master gt slave start fragment Data 6 Words VC1 Data structure 04 00 00 00 04 00 01 011000000 Write Request bus coupler Slot Invoke ID Index high Index low Subindex Length 1 data byte 4 bytes unused Write response slave gt master Data 6 Words VC1 Data Structure 84 00 00 00 00 00 00 00 00 00 00 Write Response bus coupler Status 00 10 bytes unused Clear request master gt slave Data 6 Words VC1 Data Structure 00 I 00 00 00 00 00 00 00 00 00 00 Clear Request 11 bytes unused 00 Clear response slave gt master Data 6 Words VC1 Data Structure The response indicates that the command has been received Here the status is positive 0 Via Clear the communication data can be reset to the initial state 4 22 PHOENIX CONTACT 6852
65. o 8 LT 16 LT15 LT14 LT13 LT12 LTM LT 10 CS er 9 to 16 NE e 57 to 63 A eee 4 ws Status header 0 Status type device status Status type device status device status EN 0 general status of the bus B po jojo o o o SP SP Speer STLT 4 Status local bus device 1 to 4 oe ee e e e e o e o sure sre STitet Staus local bus device 6tto63 Tf HERE _ Channel specific diagnostics an header 1 4 _ Channel specific diagnostics header 2 10 channel specific diagnostics maximum 6852 en _02 PHOENIX CONTACT 3 23 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME Table 3 2 Diagnostics FLM BK PB M12 DI 8 M12 aus XX X X XX RevsongartwihC 2 es a P o je je je pH jo jo Status header a oe je je jo jo jo Reserved header 2 o je jo joe jo jo jo jo Reserved header 2 o je jo joe jo jo jo jo Reserved header 72 Baud rate local bus 1 500 kbaud 2 2 Mbaud Cn ee er U ID code SEEE ee a ee 1st local bus device with error Cn ee eae l l XX XP iB state ow bye efo je je fo fo Jo omenimtoat X X X X X X X X Number of accessible local bus devices Block 1 PROFIBUS Standard Diagnostics Block 2 ID Specific Diagnostics The table shows the faulty local bus devices For every faulty device a 1 is entered In the first byte of the block in bit O up to 5 the length L of the entire ID specific diagnostic blo
66. observed to achieve error free operation It also gives you tips and advice on the efficient use of hardware and on software optimization to save you extra work The attention symbol refers to an operating procedure which if not carefully followed could result in damage to hardware and software or personal injury The text symbol refers to detailed sources of information manuals data sheets literature etc on the subject matter product etc This text also provides helpful information for the orientation in the manual For use in potentially explosive areas please observe the following AN THIS EQUIPMENT IS SUITABLE FOR USE IN CLASS DIVISION 2 GROUPS A B C AND D OR IN NON HAZARDOUS LOCATIONS ONLY WARNING EXPLOSION HAZARD SUBSTITUTION OF COMPONENTS MAY IMPAIR SUITABILITY FOR CLASS DIVISION 2 WARNING EXPLOSION HAZARD DO NOT DISCONNECT EQUIPMENT UNLESS POWER HAS BEEN SWITCHED OFF OR THE AREA IS KNOWN TO BE NON HAZARDOUS ALL WIRING OF THESE DEVICES MUST BE IN ACCORDANCE WITH THE NATIONAL ELECTRICAL CODE ARTICLE 501 4 B FOR CLASS I DIVISION 2 6852_en_02 PHOENIX CONTACT FLS FLM PB SYS PRO UME PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS We Are Interested in Your Opinion We are constantly attempting to improve the quality of our manuals Should you have any suggestions or recommendations for improvement of the contents and layout of our manu
67. ocal bus not complete 1 Hz Station in process data mode Green red Flashing flicker Device in selftest state Red ON An error is present that cannot be corrected Red flashing Local bus is read no process data transmission on local bus 1 Hz Yellow flashing More than 64 devices configured or system restriction of 244 bytes of 1 Hz process data configuration data exceeded Voltage not present F LED green red yel Status of local bus communication low Local bus is running data cycles Red yellow There are differences between specified and current configuration Flashing 1 Hz Flashing Pre programmed error values are written to the outputs green yellow 1 PLC stopped or PROFIBUS connection interrupted cable connector Hz Yellow flashing PCP error on an I O device 1 Hz Voltage not present Green red LED Voltage supply for inputs IN1 to IN8 Voltage supply present Red ON Overload or voltage supply too low Voltage supply not present 3 22 PHOENIX CONTACT 6852 en _02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configuration and Startup 3 5 Diagnostics Table 3 2 Diagnostics FLM BK PB M12 DI 8 M12 Station status 1 Es I Station status2 23 PROFIBUS master address 1 Manufacturer ID high byte 07 hex ooo ron Diet or re Ef L Block length ID specific diagnostics Header LT8 aw LT 6 LT 5 LT 4 LT 3 LT 2 LT 1 Local bus device 1 t
68. onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS DGD EB OO OD Kenn OGD O OE INSPIRING INNOVATIONS AUTOMATIONWORX User Manual FLS FLM PB SYS PRO UME Order No 26 99 07 9 Configuring a PROFIBUS DP System Using Devices in the Fieldline Product Range THE ONLINE DISTRIBUTOR OF ELECTRONIG COMPONENTS THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS AUTOMATIONWORX User Manual Configuring a PROFIBUS DP System Using Devices in the Fieldline Product Range 08 2005 Designation FLS FLM PB SYS PRO UME Revision 02 Order No 26 99 07 9 This manual is valid for Devices of the Fieldline Product Range for the PROFIBUS DP Bus System 6852 en 02 PHOENIX CONTACT THE ONLINE DISTRIBUTOR OF ELECTRONIG COMPONENTS THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME Please Observe the Following Notes In order to ensure the safe use of your device we recommend that you read this manual carefully 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 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 The note symbol informs you of conditions that must strictly be
69. onse slave gt master Data 4 Words VC1 Data Structure 14 100 00 00 00 00 00 00 Write Response 7 bytes unused Write request master gt slave end fragment Data 4 Words VC1 Data Structure 40 00 00 00 00 00 00 00 Write 7 bytes of data Write response slave gt master Data 4 Words VC1 Data Structure 84 00 00 00 00 00 00 00 Write Response Status 6 bytes unused 8 Words VC1 Write request master gt slave start fragment Data 8 Words VC1 Data Structure 14 00 00 00 06 00 08 F2 00 00 00 00 Write Slot Invoke ID Index High Index Low 00 00 00 00 Subindex Length 8 byte data 1 byte unused Write response slave gt master Data 8 Words VC1 Data Structure 14 100 00 00 00 00 00 00 00 00 00 Write Response 15 bytes unused 00 00 00 00 00 6852 en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Dynamic Configuration Access via Index 7 Please observe the structure of Index 7 when accessing it Byte 1 O8nex Byte 2 OOnex Byte 3 07 hex Byte 4 Length of data n Byte5 1 2 3 4 5 6 7 8 Byte4 n X X X X X X X X Bit 0 Device and slot inactive Bit 1 Device and slot active In this example there are 7 connected devices The devices 1 2 3 4 and 7 must be active The devices 5 and 6 are inactive The resulting data for object 7 are the following O8hex O0hex O7hex 01 hex F2hex The fourth byte for Index 7 contains the length Thus only as many by
70. parameters Behaviour on lost 1 0 modules Acknowledge of peripheral Faults channel wize Diagnostics inactive DI116 D016 byte position AE ae eal Hex parameter assignment active Cancel Help Figure 3 17 Setting the channel specific diagnostics 3 20 PHOENIX CONTACT 6852 en 02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configuration and Startup 3 4 2 Local Diagnostic and Status Indicators UL MD x10 12 7008A003 Figure 3 18 Diagnostic and status indicators of the FLM BK PB M12 DI 8 M12 device Table 3 1 Diagnostic and status indicators Des Color Meaning S O O UL Green LED Communications power ON Communications power present OFF Communications power too low 6852 en _02 PHOENIX CONTACT 3 21 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME coo Meaning S O Red LED No cyclic data transmission PROFIBUS not connected master not active Incorrect settings configuration via master station address Timeout expired LED OFF The device is addressed by the PROFIBUS it received a parameterization No power supply for the device In this state the UL LED does not light up either because of the missing 24 V communications power LED Device status green red yel low Device is ready to operate Green flashing An error is present that can be corrected l
71. plication In this example the devices FLM DI 8 and FLM DO 8 have been deactivated via the illustrated services and thus must not be connected For further information and examples regarding the communication via the process data inter face as well as DP V1 please refer to section Acyclic Communication DP V1 and PCP on page 4 1 The PD PCP x words process data interface module does not have to be configured for normal operation You only need it if you want to access the objects such as Index 6 via the process data If you want to use the PD PCP x words process data interface module VC1 you can configure it at any position However we recommend to use the last position because here the configured slot and the actual slot will always be identical PHOENIX CONTACT 5 11 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME 5 12 PHOENIX CONTACT 6852_en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Appendix A Appendix A 1 Error Codes for PCP Communication Table A 1 O6hax O2hex hardware fault Meaning Access to the object failed due to a hardware fault For example no I O voltage Remedy Remove the hardware fault Table A 2 O6hax OShex object access denied Meaning The object has limited access rights It may be a read only object or it may be password protected Remedy Check the access rights in the object description Table A 3 O6nex O5hex object
72. process can be started right with the next Read Write Alternatively the last fragment can either be acknowledged or a Clear can be sent Acknowledgement of the last fragment Read request master gt slave acknowledgment of end fragment Data 4 Words VC1 Data Structure CO I 00 00 00 00 00 00 00 Acknowledgement end fragment 7 bytes unused Read response slave gt master Data 4 Words VC1 Data Structure 00 00 00 00 00 00 00 00 Clear Or Clear Clear request master gt slave Data 4 Words VC1 Data Structure 00 00 00 00 00 00 00 00 Clear Request 7 bytes unused Clear Response slave gt master Data 4 Words VC1 Data Structure 00 00 00 00 00 00 00 00 Clear Response 4 24 PHOENIX CONTACT 6852 en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Acyclic Communication DP V1 and PCP 4 Example Writing the Config Table for channel 3 on the connected FLM Al 4 SF slot 3 index 0080 subindex 3 Write request master gt slave start fragment Data 4 Words VC1 Data Structure 17 03 00 00 80 00 OC 03 Write Request I O Slot Invoke ID PCP Index high PCP Index low PCP Subindex Length of the PCP object data 1 byte PCP object data Write response slave gt master Data 4 Words VC1 Data Structure 17 1 00 00 00 00 00 00 00 Write Response 7 bytes unused Write request master gt slave 1st continue fragment Data 4 Words VC1 Data Structure 21 00 03 01
73. r C2 master for the PCP mechanism in the local bus PCP data from the local bus in turn are realized by the bus coupler in DP V1 telegrams IS Before programming the application check whether your control system or configuration tool supports DP V1 If not you can use the functions offered by the cyclic process data channel DP VO see section 4 5 on page 4 15 pp The following decisions must be made regarding communication 4 1 Acyclic Communication via C1 Master C1 master The C1 master carries out parameterization during slave startup and is also the master for cyclic data traffic It may also be necessary to acyclically read a parameter from the device as an option using this C1 master Corresponding read and write accesses are therefore defined for the C1 master As it already has a connection to the slave during cyclic data traffic the C1 master does not have to establish an explicit connection using Initiate but can communicate with the slave directly via Read and Write 6852 en _02 PHOENIX CONTACT 4 1 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME 4 2 Acyclic Communication via C2 Master C2 master For communication in the C2 master the data fields are identical to those of C1 communi cation and it is only the SAPs Service Access Points which are different The additional effort required is the use of Initiate and Abort to establish and release the connectio
74. re present a header byte follows Byte x Bit 7 to bit6 11 Function block ID Bit 5 to bitO Entire function block length After that the function blocks are decoded a PCP Function Block Byte x 1 Bit 7 to bit 6 01 PCP function block Bit 5 to bit O PCP function block length Byte x 3 Index high byte Byte x 4 Index low byte Byte x 6 n data bytes to x 6 n b Additional Function Block Byte x 1 Bit 7 to bit 6 10 Additional function block Bit 5 to bit O Length of the additional function block Byte x 2 BitO 1 I O data rotate correctly 0 I O data do not rotate correctly Bit 7 to bit 1 Reserved c ID Function Block n lt 16 Byte x 1 Bit 7 to bit 6 11 ID function block Bit 5 to bit O Length of the ID function block Byte x 2 Bit 7 to bit O Order No last n sign ASCII Byte Bit 7 to bit O Order No last sign ASCII X 2 N A 6 PHOENIX CONTACT 6852 en 02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Appendix Ordering Data B Appendix Ordering Data The Phoenix Contact AUTOMATIONWORx catalog contains the ordering data for all Fieldline products This includes Fieldline devices Bus cables Shielded bus connectors Unshielded connectors Other accessories IS For additional information about Fieldline devices and accessories visit the Phoenix Contact e shop at www phoenixcontact com Complete documentation for the Fieldline
75. ror The prerequisite for the display of the channel errors is that the I O device supports PCP and that the channel specific diagnostics in the bus coupler are enabled lO OOpin Reserved lO Olpin Input lO 1Opin Output lO 11 pin Input and Output Channel Channel number of the respective channel 0 up to 63 CT 000 Reserved CT 001 1 Bit CT 010yn 2 Bit CT Ol1pin 4 Bit CT 100 1 Byte CT 101pin 1 Word CT 110pin 2 Words CT 111 Reserved ET O Reserved ET 1 Short circuit ET 2 Undervoltage ET 3 Surge voltage ET 4 Overload ET 5 Overtemperature ET 6 Cable break ET 7 Upper limit value exceeded ET 8 Lower limit value exceeded ET 9 General error PHOENIX CONTACT 3 25 FLS FLM PB SYS PRO UME 3 26 PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Block 5 Revision Diagnostics Block 6 Status PDU The sixth block also is encoded as status PDU however in manufacturer specific format The information stored here usually needs not be evaluated Byte 5 indicates the baud rate with which the local bus is operated and it indicates the status of pin 5 of the U s power supply 1 500 kbaud 2 2 Mbaud Byte 7 and byte 8 show the ID and length code of the first faulty devices This can be used as additional information for blocks 2 and 3 if required The value of byte 11 is 1 if the system limit was exceede
76. s the local bus device is to be used as PROFI BUS index 47 gec 2Fhex The PCP index is transmitted as part of the data field During accesses onto the bus coupler the object index can be used directly lt DP V1 length gt On a write access the length of the subsequent data is entered here and on a read access the length of the expected data is entered On a response this parameter con tains the actual length of the DP V1 data lt Error decode gt 80nex indicates an error in DP V1 lt Error code 1 gt and lt Error code 2 gt Contain the error codes from the DP V1 access see Error Codes for DP V1 and VC1 Communication on page A 3 lt Write PCP Read PCP gt This indicates whether the following object index should be written or read Read PCP O6hox Write PCP 07 hoax _ lt Object data gt This is only the contents of an object The length and scope of the data has already been described by lt DP V1 length gt lt Invoke ID gt The Invoke ID is used for some I O devices Check it in the respective data sheet at hand lt Index high and Index low gt This specifies the object index of the addressed PCP object in two bytes For example for index 2300rex the value 23ex should be entered for Index high and the value OOhex should be entered for Index low lt Subindex gt When working with a PCP object the subindex can be used to select a specific ele ment from an array or record
77. s Data on page 4 15 Here you will find further examples on communication via DP VO and DP V1 The individual indices are explained in section Slot 0 on page 3 27 Which option will be used in the end depends on the support of DP V1 in the master If the DP V1 is not well supported DP VO should be used For SIMATIC STEP 7 CPU functions are available that have been prepared by Phoenix Contact PHOENIX CONTACT 6852 en_02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Dynamic Configuration 5 3 3 Specification of the Active Configuration via DP VO For DP VO you can access the activation status via Index 6 or 7 There are different object structures Thus example accesses are illustrated for both objects Access via Index 6 Please observe the structure of Index 6 when accessing it Byte 1 Byte 2 Bytes 3 Byte 8 to 7 1 ja sj 1sje 7jejs to 11 12 ra r4 is je 57 58 pee e2 63 x Bit 0 Device and slot inactive Bit 1 Device and slot active In this example there are 7 connected devices The devices 1 2 3 4 and 7 must be active The devices 5 and 6 are inactive The resulting data for object 6 are the following F2nex OOhex O0hex OOhex OOnex O0hex O0hex OOhex In the following the description of these 8 data bytes serves as example for two optional data widths of the VC1 device If a new activation status is described via Index 6 or Index 7 it becomes only
78. s in your working environment DP V1 error Function code Response DE pex Error Read or function code Response DFphex Error Write Error decode 80hex DP V1 communication Error with reference to I O device Status 44 hex characterizes an error for DP V1 on byte 3 of the data block for VC1 Byte 2 in the response Table A 7 Error codes for DP V1 and VC1 communication Bix o gt Invalid data length during writing Bae jo malgdeicenme Bfr o Satu confi ast Reade not rished yet Bres o Access onto device or index not permitted Bhe e manm o o wrong dat enh auring access PCP PDU size of 64 bytes 58 bytes user data per communication exceeded Internal timeout while reading Internal error when transmitting a request Internal error when receiving a service 6852_en_02 PHOENIX CONTACT A 3 FLS FLM PB SYS PRO UME A 4 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS A3 Format of the Parameter Telegram This section provides a detailed description of the format of the parameters for the bus cou pler and the input and output devices This may be useful when setting parameters using acyclic services or if there is no interface for the simple selection of parameters Table A 8 Parameters for the bus coupler Bytes 1to 7 DP standard Bytes 8 to 10 DP V1 standard 0 Hide channel specific diagnostics 1 display channel specific diagnostics 0 Do not turn DI32 and DO32 data
79. scribed via Index 6 it becomes only valid as soon as the IEY bus is restarted 2 Corresponding Examples If as described in this example the configuration and the accessible devices are not identical because e g 2 devices are not connected the bus is read in continuously until it is identical with the configuration In the course of this the activation status on Index 6 is evaluated automatically If the dynamic bus structure is expanded and if previously inactive devices are attached to the end these devices are activated via Index 6 at first During the next bus start the new devices are integrated into data traffic The bus can be started via Index 4 bit 0 Please note that during reset the device output data are reset to their device specific reset values Write request master gt slave Data 8 Words VC1 Data Structure 5F 00 06 08 F2 00 00 00 00 00 00 00 Write Slot Index Length Data Total Length 8 bytes object data Write response slave gt master Data 8 Words VC1 Data Structure 5F 00 06 08 Write Slot Index Length 5 10 PHOENIX CONTACT 6852_en_02 6852 en 02 A g onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Dynamic Configuration 5 3 5 Summary According to the respective task and the prerequisites in the control system you can use the illustrated services process data interface DP VO or DP V1 to specify the actually op erated configuration of the ap
80. tems Once it has been entered this data only has to be modified upon a change in the parameterization or in the event of an error The parameters are pre configured and can be taken from the device documentation provided by the manufacturer 6852 en _02 PHOENIX CONTACT 4 3 FLS FLM PB SYS PRO UME Parameters of a frequency inverter Index 4 4 PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS As an electrical drive controller a key feature of a frequency inverter is that changes can be made to process variables e g speed position and torque using analog or digital sig nals Additional information is required to optimize the adaptation of the drive controller and motor to the process As well as setpoint information the frequency inverter also requires information about the motor type point the minimum and maximum permissible speed of the system the maximum speed variation during acceleration and deceleration starting ramp starting current etc These types of additional information are device specific parameters which can be modi fied via the parameter data channel The parameter values for all PCP devices are the subject of communication via the param eter data channel To enable the individual parameters to be distinguished during commu nication each parameter has a number the index The index is the address of the communication object It is required to identify the object
81. tes as devices to be de activated need to be transmitted These 5 data bytes are described in the following 4 Words VC1 Write request master gt slave start fragment Data 4 Words VC1 Data Structure 08 00 07 01 F2 I 00 00 00 Read Write Index High Index Low Length 1 byte data 3 bytes unused Write response slave gt master Data 4 Words VC1 Data Structure 88 00 02 05 F2 00 00 00 Read Write Response Status Length Number of accessible devices device status 3 bytes unused 6852 en 02 PHOENIX CONTACT 5 9 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME 5 3 4 Specification of the Active Configuration via DP V1 For DP V1 you can access the activation status via Index 6 Index 7 is not supported here because it was optimized for the access via process data interface in particular Access via Index 6 Please observe the structure of Index 6 when accessing it Byte 1 Byte 2 Bytes 3 Byte 8 to 7 12 sj 1sje 7jejs 10 11 12 ra r4 is te Sr pee e2 63 x Bit 0 Device and slot inactive Bit 1 Device and slot active In this example there are 7 connected devices The devices 1 2 3 4 and 7 must be active The devices 5 and 6 are inactive The resulting data for object 6 are the following F2hex O0hex O0hex O0hex O0hex O0hex O0hex OOnex These 8 data bytes are transmitted via DP V1 in the following If a new activation status is de
82. that they are part of the maximum configuration All settings are stored in the volatile memory Thus easy replacement is ensured The de vice must not be parameterized in advance Three indices on the bus coupler are used for the handling Index 4 General control bits Access Write Function Details under Slot 0 on page 3 27 Please observe bit O and bit 3 during dynamic configuration Struc Length of 1 byte ture Bit 0 Restart local bus Bit 3 Unlock dynamic configuration Index 6 Activation deactivation of devices and slots Access Read and Write Function Indicates which devices are active inactive Deactivation via the parameter telegram reservation of empty spaces is also indicated here Struc Length of 8 bytes ture Byte 2 Bytes 3 to 7 112 1 1415 Is 7 lsjs to 11 12 183 14 15 16 57 58 59 60 61 62 63 x Bit 0 Device and slot inactive Bit 1 Device and slot active 6852 en 02 PHOENIX CONTACT 5 3 FLS FLM PB SYS PRO UME 5 4 PHOENIX CONTACT onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Index 7 Activation deactivation of devices and slots and bus reset Access Function Struc ture Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 4 n Only via DP VO command 8 Indicates which devices are active inactive Deactivation via the parameter telegram reservation of empty spaces is also indicated here In addition
83. the Fieldline Modular local bus devices with each other The bus coupler opens a powerful local bus which can be used to connect up to 16 more devices Devices are Fieldline modular local bus devices used to implement a local bus station The bus coupler provides the power supply The maximum total length of a local bus is 20 m The transmission speed can be switched from 500 kBaud to 2 MBaud The bus coupler can be connected with up to 8 digital sensors via M12 connectors The slots are double occupied The bus coupler supplies the supply voltage for the sensors and reads in the provided signals 6852_en_02 PHOENIX CONTACT 1 7 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME 1 8 PHOENIX CONTACT 6852_en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Connecting Bus Cables and Setting the Address 2 Connecting Bus Cables and Setting the Address 2 1 Connection Options for the Bus In the following a cable that conforms to the fieldbus specification must be used to connect PROFIBUS DP Use shielded M12 connectors to connect the bus The thread of the M12 connector is used to connect the shielding to functional earth ground and in some cases a pin is also used 7 Phoenix Contact recommends the use of pre assembled bus cables see Phoenix Contact AUTOMATIONWORX catalog 7 If you assemble the cables yourself please follow the description provided in the Fieldline FLS FLM
84. the configuration corresponds to the presetting PHOENIX CONTACT 6852 en _ 02 Acknowledging I O errors 6852 en 02 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configuration and Startup This option has been prepared for future I O devices If you are using a device where those I O errors will be reported that have to be acknowledged this message can either be ac knowledged automatically or from the application Properties DP slave General Parameter Assignment Value E Sy Station parameters DP Interrupt Mode General OP parameters Device speciic parameters Behaviour on lost 1 0 modules Acknowledge of peripheral Faults channel wise Diagnostics 0116 0016 byte position Hex parameter assignment Local Bus Stop automatically automatically mantall Figure 3 16 Acknowledging I O errors PHOENIX CONTACT 3 19 onlinecomponents com THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME Channel Specific Diagnostics Several devices support channel specific diagnostics If you would like to read them if re quired please enable the diagnostics here Please note that this procedure lengthens the diagnostic telegram Up to 10 diagnostics will be displayed simultaneously Froperties DP slare x General Parameter Assignment Parameters Value Station parameters EZ DP Interupt Mode General OP parameters I zz K__ Device specific
85. the quality of the figures meet your expectations needs Does the layout of the document allow you to find information easily Contents Is the phraseology terminology easy to understand Are the index entries easy to understand helpful Are the examples practice oriented Is the document easy to handle Is any important information missing If yes what Other Comments Yes lt oo 000 O 0 0 Do Inp O O JO UO OD Oo si U OJ 26 99 07 9 art No o o O o O art No o O o o O
86. tics starting with byte 7 without standard diagnostics Access Read Length 72 bytes maximum Structure As described in section Diagnostics on page 3 23 Index 20 Cycle Count Function Cycle count all cycles Access Read and write Length 8 bytes Note For write all counters are set to O index 20 to 25 Index 21 Cycle Error Count Function Cycle count all faulty cycles Access Read and write Length 8 bytes Note For write all counters are set to O index 20 to 25 Index 22 ID Cycle Count Function Cycle count all ID cycles 6852 en_02 6852 en 02 Access Length Note Index 23 Function Access Length Note Index 24 Function Access Length Note Index 25 Function Access Length Note THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Configuration and Startup Read and write 8 bytes For write all counters are set to O index 20 to 25 ID Cycle Error Count Cycle count all faulty ID cycles Read and write 8 bytes For write all counters are set to O index 20 to 25 Data Cycle Count Cycle count all data cycles Read and write 8 bytes For write all counters are set to O index 20 to 25 Data Cycle Error Count Cycle count all faulty data cycles Read and write 8 bytes For write all counters are set to O index 20 to 25 The objects on slot O can be read and written via one individual access via DP V1 PHOENIX CONTACT 3 31 FLS FLM PB SYS P
87. ways be identical It is not linked to any hardware so a device is not actually inserted 6852 en _02 PHOENIX CONTACT 4 15 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS FLS FLM PB SYS PRO UME Start Fragment Byte 1 Service Byte 2 Device no Byte 3 Invoke ID Byte 4 Index high Byte 5 Index low Byte 6 Subindex Byte 7 Length if required Byte 8 Data block if required Byte n Data block if required Table 4 6 Byte 1 Service in start fragment Byte 1 EZ Fragmen Action response tation Bit 7 Request response 0 Request 1 Response Bits 6 to 5 Fragment type 00 start fragment Bit 4 Fragmentation 0 Not fragmented 1 fragmented Bits 3 to 0 Action OOhex No action clear Olpex up to Reserved 02hex O3hex Read FLM BK PB M12 DI 8 M12 O04 nex Write FLM BK PB M12 DI 8 M12 O5hex Reserved O6hex Read PCP I O terminal 07 hex Write PCP I O terminal O8hex Read and Write simultaneously special objects only O9hex to OFhex Reserved 4 16 PHOENIX CONTACT 6852 en_02 THE ONLINE DISTRIBUTOR OF ELECTRONIC COMPONENTS Acyclic Communication DP V1 and PCP Continue Fragment Byte 1 Service Byte 2 Data block if required Byte n Data block if required Table 4 7 Byte 1 Service in continue fragment ave 1 Tea Bit 7 Request response 0 Request 1 Response Bits 6 to 5 Fragment type 01 Continue fragment Bits 4 to 0 Numerator Olhex UP to 1Fhex fragment

1 Fieldline at the PROFIBUS-DP

Contents

Download Pdf Manuals

Related Search

Related Contents