Phoenix Contact FLS FLM PB SYS PRO UM E User Manual
  1. Manuals
  2. Brands
  3. Phoenix Contact Manuals
  4. I/O Systems
  5. FLS FLM PB SYS PRO UM E
  6. User manual
Phoenix Contact FLS FLM PB SYS PRO UM E User Manual

Phoenix Contact FLS FLM PB SYS PRO UM E User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
AUTOMATIONWORX
User Manual
FLS FLM PB SYS PRO UM E
Order No.:
26 99 07 9
Configuring a PROFIBUS-DP System Using Devices
in the Fieldline Product Range

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the FLS FLM PB SYS PRO UM E and is the answer not in the manual?

Questions and answers

Related Manuals for Phoenix Contact FLS FLM PB SYS PRO UM E

Summary of Contents for Phoenix Contact FLS FLM PB SYS PRO UM E

  • Page 1 AUTOMATIONWORX User Manual FLS FLM PB SYS PRO UM E Order No.: 26 99 07 9 Configuring a PROFIBUS-DP System Using Devices in the Fieldline Product Range...
  • Page 3 User Manual Configuring a PROFIBUS-DP System Using Devices in the Fieldline Product Range 08/2005 Designation: FLS FLM PB SYS PRO UM E Revision: Order No.: 26 99 07 9 This manual is valid for: Devices of the Fieldline Product Range for the PROFIBUS-DP Bus System...
  • Page 5 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.
  • Page 6 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.

  • Page 7: Table Of Contents

    Acyclic Communication in DP/V1 Mode ............. 4-6 4.4.1 The Communication Mechanism ............4-6 4.4.2 Examples .................... 4-9 Acyclic Communication in DP/V0 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 ...............4-21 6852_en_02 PHOENIX CONTACT...
  • Page 8 Specification of the Active Configuration via DP/V1 ......5-10 5.3.5 Summary ..................5-11 Appendix..........................A-1 Error Codes for PCP Communication .............. A-1 Error Codes for DP/V1 and VC1 Communication ..........A-3 Format of the Parameter Telegram ..............A-4 Appendix..........................B-1 Ordering Data....................B-1 PHOENIX CONTACT 6852_en_02...

  • Page 9: Fieldline At The Profibus-Dp

    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. 6852_en_02 PHOENIX CONTACT...

  • Page 10: Documentation For Fieldline Devices

    FLS FLM PB SYS PRO UM E 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.

  • Page 11: Profibus-Dp

    DIN 19245 in 1991. In 1996, PROFIBUS was defined as the European standard in EN 50170. 1.3.1 Structure of PROFIBUS-DP Figure 1-1 Typical structure of an PROFIBUS-DP system with remote bus and local bus Key for Figure 1-1: Master Termination resistor Repeater Repeater with termination resistor Segment 6852_en_02 PHOENIX CONTACT...
  • Page 12 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). Repeaters can be found in the latest Phoenix Contact INTERFACE catalog. PHOENIX CONTACT 6852_en_02...

  • Page 13: Address

    Baud Rate in 19.2 93.75 187.5 1500 12000 kbps Line length in 1200 1200 1200 1000 Length of branch lines in < 6.6 None Only one baud rate can be used at a time in a PROFIBUS system. 6852_en_02 PHOENIX CONTACT...

  • Page 14: Laying The Profibus Cable

    FLS FLM PB SYS PRO UM E 1.3.4 Laying the PROFIBUS Cable When laying a PROFIBUS cable, please observe the following: – Do not lay signal and bus cables parallel to power cables or in bundles with power ca- bles.

  • Page 15: Fieldline Modular Local Bus

    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...
  • Page 16 FLS FLM PB SYS PRO UM E PHOENIX CONTACT 6852_en_02...

  • Page 17: Connecting Bus Cables And Setting The Address

    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. Phoenix Contact recommends the use of pre-assembled bus cables (see Phoenix Contact AUTOMATIONWORX catalog).
  • Page 18 FLS FLM PB SYS PRO UM E BUS IN / BUS OUT 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.

  • Page 19: Connecting The Bus And Termination Resistor

    Fieldline Stand-Alone devices Connection via BUS IN / BUS OUT Incoming and outgoing bus Incoming bus and termination resistor Connection via T-piece Incoming and outgoing bus Incoming bus and termination resistor Termination resistor Protective cap for the unused connection 6852_en_02 PHOENIX CONTACT...
  • Page 20 FLS FLM PB SYS PRO UM E 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.

  • Page 21: Connecting The Bus

    Reference potential of the RS-485 transceiver of the station Shield Shield Placed directly on FE Figure 2-6 Connector pin assignment of the M12 connector (connector on the cable) The thread and pin 5 are used for shielding. 6852_en_02 PHOENIX CONTACT...
  • Page 22 FLS FLM PB SYS PRO UM E Pin assignment of the local bus for Fieldline Modular devices Figure 2-7 Pin assignment of the local bus (FLM) LB IN LB OUT PROFIBUS-DP cables available on the market usually have one wire pair (red and green), which is protected by a braided shield and membrane.

  • Page 23: Setting The Address

    The station address set is read upon system startup and accepted in the device settings. 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. 6852_en_02 PHOENIX CONTACT...
  • Page 24 FLS FLM PB SYS PRO UM E PHOENIX CONTACT 6852_en_02...

  • Page 25: Configuration And Startup

    • Select PROFIBUS cables 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.

  • Page 26: Installation

    FLS FLM PB SYS PRO UM E Installation Disconnect the power supply before installing the devices. • Installing devices See FLS FLM SYS INST UM E user manual. • Connecting the Bus See section "Connecting the Bus" on page 2-5.

  • Page 27: Configuration And Startup Using The Step 7® Simatic® Manager

    ® ® ware configurator, e.g., the Siemens STEP 7 SIMATIC Manager, the automatic configuration in the station is overwritten. ® ® ® Starting the STEP 7 Start the STEP 7 SIMATIC Manager under Windows. ® SIMATIC Manager 6852_en_02 PHOENIX CONTACT...
  • Page 28 FLS FLM PB SYS PRO UM E 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.
  • Page 29 Insert a station using the "Insert...Station...SIMATIC 300 Station" menu item. ® ® station into the project In this example, a "SIMATIC 300 Station" has been selected. ® ® Figure 3-2 Inserting a new SIMATIC station into the project 6852_en_02 PHOENIX CONTACT...
  • Page 30 FLS FLM PB SYS PRO UM E On the left-hand side of the project window, click on the small "plus" box next to the ® "Example" folder and select "SIMATIC 300(1)". ® Figure 3-3 Selecting SIMATIC 300(1) ® The SIMATIC Manager displays the "Hardware"...
  • Page 31 Open the "PXC_07E9.gsd" file via "Tools... Install New GSD..." in the dialog box that ap- pears. 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...
  • Page 32 FLS FLM PB SYS PRO UM E 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"...
  • Page 33 Configuration and Startup Next confirm the entries in the "Properties - PROFIBUS Interface DP Master (R0/S2.1)" window with "OK" or "Return". Figure 3-6 Properties - PROFIBUS Interface DP Master (R0/S2.1) 6852_en_02 PHOENIX CONTACT...
  • Page 34 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.
  • Page 35 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". Figure 3-8 Properties - PROFIBUS Interface FLM BK PB M12 DI 8 M12 3-11 6852_en_02 PHOENIX CONTACT...
  • Page 36 FLS FLM PB SYS PRO UM E 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)
  • Page 37 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. 3-13 6852_en_02 PHOENIX CONTACT...
  • Page 38 FLS FLM PB SYS PRO UM E Transfer to the S7 system Save and translate the project using the button or the "Station… Save and Translate" menu item. Transfer the project to the S7 system using the button or the "Target System… Load to Module"...

  • Page 39: Functions Of The Flm Bk Pb M12 Di 8 M12

    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. 3-15 6852_en_02 PHOENIX CONTACT...
  • Page 40 FLS FLM PB SYS PRO UM E Replacement strategy in local bus 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: –...
  • Page 41 1 and byte 0 or the other way around, i.e. connector 1 to 4 and 5 to 8 are copied onto byte 0 and 1. Figure 3-14 Adapting the data format to the control system 3-17 6852_en_02 PHOENIX CONTACT...
  • Page 42 FLS FLM PB SYS PRO UM E 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.
  • Page 43 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. Figure 3-16 Acknowledging I/O errors 3-19 6852_en_02 PHOENIX CONTACT...
  • Page 44 FLS FLM PB SYS PRO UM E 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.

  • Page 45: Local Diagnostic And Status Indicators

    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 Green LED Communications power Communications power present OFF: Communications power too low 3-21 6852_en_02 PHOENIX CONTACT...
  • Page 46 FLS FLM PB SYS PRO UM E Des. Color Meaning 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,...

  • Page 47: Diagnostics

    (header) #1 Channel IN / OUT and channel number #1 Channel and error type #1 Slot Channel-specific diagnostics (header) #2 Channel IN / OUT and channel number #2 Channel and error type #2 10 channel-specific diagnostics, maximum 3-23 6852_en_02 PHOENIX CONTACT...
  • Page 48 FLS FLM PB SYS PRO UM E Table 3-2 Diagnostics FLM BK PB M12 DI 8 M12 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Meaning Revision (start with C1) Status (header)
  • Page 49 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 3-25 6852_en_02 PHOENIX CONTACT...
  • Page 50 FLS FLM PB SYS PRO UM E 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 power supply (1 = 500 kbaud, 2 = 2 Mbaud).

  • Page 51: Object Dictionary

    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: 3-27 6852_en_02 PHOENIX CONTACT...
  • Page 52 FLS FLM PB SYS PRO UM E – 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 -> maximum 48 bytes...
  • Page 53 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. 3-29 6852_en_02 PHOENIX CONTACT...
  • Page 54 FLS FLM PB SYS PRO UM E 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.
  • Page 55 Access: Read and write Length: 8 bytes Note: For write, all counters are set to 0 (index 20 to 25) The objects on slot 0 can be read and written via one individual access via DP/V1. 3-31 6852_en_02 PHOENIX CONTACT...

  • Page 56: Slot 1

    FLS FLM PB SYS PRO UM E 3.6.2 Slot 1 On slot 1, indices are implemented with regard to the integrated DI 8. Index 13: PD-IN Function: Input data of the integrated DI 8 Access: Read Length: 1 bytes 3.6.3...

  • Page 57: Acyclic Communication (Dp/V1 And Pcp)

    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...

  • Page 58: Acyclic Communication Via C2 Master

    FLS FLM PB SYS PRO UM E 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"...

  • Page 59: Pcp Communication Basics

    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...
  • Page 60 FLS FLM PB SYS PRO UM E Parameters of a As an electrical drive controller, a key feature of a frequency inverter is that changes can frequency inverter be made to process variables (e.g., speed, position, and torque) using analog or digital sig- nals.
  • Page 61 Program invocation – Program invocation type objects, i.e., program sequences that can be run. For additional information on PCP communication, please refer to the IBS SYS PCP G4 UM E user manual, Order No. 27 45 16 9. 6852_en_02 PHOENIX CONTACT...

  • Page 62: Acyclic Communication In Dp/V1 Mode

    FLS FLM PB SYS PRO UM E Acyclic Communication 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...
  • Page 63 The meanings of the individual parameters are as follows: – <DP/V1 service>: In the request there is a distinction between DP/V1 Read (5E ) and DP/V1 Write ); in the error response there is a distinction between DE (Read error) and (Write error). 6852_en_02 PHOENIX CONTACT...
  • Page 64 FLS FLM PB SYS PRO UM E – <Slot>: 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.
  • Page 65 Subindex 00 Subindex 01 to 06 Data 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...
  • Page 66 FLS FLM PB SYS PRO UM E Example 1: Reading the connected local PCP devices and their status (Slot 0, Index 5 on the bus coupler) Read request (master -> slave) Data Data Structure 5E 00 05 20 DP/V1 Read / Slot / Index / Maximum Length Read request (slave ->...
  • Page 67 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 are reserved and are indicated as 0. The Invoke ID had been mir- rored and the status indicates that the communication was error-free. 4-11 6852_en_02 PHOENIX CONTACT...
  • Page 68 FLS FLM PB SYS PRO UM E 4. Example: Writing the Config Table for channel 3 on the connected FLM AI 4 SF (Slot 3, Index 0080, Subindex 3) Write request (master -> slave) Data Data Structure 5F 03 2F 08 07 00 00 80 03 02 03 01...
  • Page 69 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. 4-13 6852_en_02 PHOENIX CONTACT...
  • Page 70 FLS FLM PB SYS PRO UM E 6. Example: In the Event of an Error: Reading an object on a device without PCP (Slot 2, Index 0080) Write request (master -> slave) Data Data Structure 5F 02 2F 05 06 00 00 80 00...

  • Page 71: Acyclic Communication In Dp/V0 Mode Via Process Data

    VC1 device at the last position. In this way, the configured slot and the actual slot occupied by the I/O device will always be identical. It is not linked to any hardware, so a device is not actually inserted. 4-15 6852_en_02 PHOENIX CONTACT...
  • Page 72 FLS FLM PB SYS PRO UM E 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...
  • Page 73 Service Byte 2: Data block, if required Byte n: Data block, if required Table 4-8 Byte 1 - Service in end fragment: Byte 1 Request/ Reserved response Bit 7: Request/Response 0 = Request 1 = Response 4-17 6852_en_02 PHOENIX CONTACT...
  • Page 74 FLS FLM PB SYS PRO UM E Bit 7: Request/Response Bits 6 to 5: Fragment type 10 = Last fragment (end fragment) Bits 4 to 0: Reserved 4-18 PHOENIX CONTACT 6852_en_02...
  • Page 75 Request/ Reserved response Bit 7: Request/response 0 = Request 1 = Response Bits 6 to 5: Fragment type 11 = Abort/error fragment Bits 4 to 0: Reserved The communication can reset anytime using 00 and 60 4-19 6852_en_02 PHOENIX CONTACT...
  • Page 76 FLS FLM PB SYS PRO UM E 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:...

  • Page 77: Examples Of Vc1 Services

    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. 4-21 6852_en_02 PHOENIX CONTACT...
  • Page 78 FLS FLM PB SYS PRO UM E 2. Example: Writing the bus restart bit (slot 0, index 4, bit 0 on the bus coupler) Write request (master -> slave) - start fragment Data (6 Words VC1) Data structure 04 00 00 00 04 00 01 01 I 00 00 00...
  • Page 79 FLM AI 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. 4-23 6852_en_02 PHOENIX CONTACT...
  • Page 80 FLS FLM PB SYS PRO UM E 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 process can be started right with the next Read/Write.
  • Page 81 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. 4-25 6852_en_02 PHOENIX CONTACT...
  • Page 82 FLS FLM PB SYS PRO UM E 5. Example: In the event of an error: Reading faulty object indices on the connected FLM AI 4SF (slot 3, index 0180) Read request (master -> slave) - start fragment Data (4 Words VC1)
  • Page 83 - 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. 4-27 6852_en_02 PHOENIX CONTACT...
  • Page 84 FLS FLM PB SYS PRO UM E 4-28 PHOENIX CONTACT 6852_en_02...

  • Page 85: Dynamic Configuration

    ® 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 & drop, see Figure 5-1. 6852_en_02 PHOENIX CONTACT...
  • Page 86 FLS FLM PB SYS PRO UM E Open the "Properties" dialog box by double-clicking on a device. 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.

  • Page 87: Principle Of The Dynamic Configuration

    (reservation of empty spaces) is also indicated here. Struc- Length of 8 bytes ture: Byte 2 Bytes 3 Byte 8 Byte 1 to 7 57 58 59 60 61 Bit = 0: Device and slot inactive Bit = 1: Device and slot active 6852_en_02 PHOENIX CONTACT...
  • Page 88 FLS FLM PB SYS PRO UM E Index 7: Activation / deactivation of devices and slots and bus reset Access: Only via DP/V0, command 8 Function: Indicates which devices are active / inactive. Deactivation via the parameter telegram (reservation of empty spaces) is also indicated here. In addition, a bus reset takes place.

  • Page 89: Startup

    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...

  • Page 90: Options For Specifying The Active Configuration

    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/V0 should be used. For SIMATIC STEP 7 functions are available that have been prepared by Phoenix Contact. PHOENIX CONTACT 6852_en_02...

  • Page 91: Specification Of The Active Configuration Via Dp/V0

    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...
  • Page 92 FLS FLM PB SYS PRO UM E 4 Words VC1 Write request (master -> 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 response (slave ->...
  • Page 93 Write response (slave -> master) Data (4 Words VC1) Data Structure 88 00 02 05 F2 I 00 00 00 Read Write Response / Status / Length / Number of accessible devices / device status / 3 bytes unused 6852_en_02 PHOENIX CONTACT...

  • Page 94: Specification Of The Active Configuration Via Dp/V1

    FLS FLM PB SYS PRO UM E 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.
  • Page 95 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. 5-11 6852_en_02 PHOENIX CONTACT...
  • Page 96 FLS FLM PB SYS PRO UM E 5-12 PHOENIX CONTACT 6852_en_02...

  • Page 97: A Appendix

    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...
  • Page 98 FLS FLM PB SYS PRO UM E Communication Error Messages Table A-4 / 06 (object access unsupported) Meaning The service used cannot be applied to this object. Cause For example, a program sequence can be started or stopped, but not read.

  • Page 99: A 2 Error Codes For Dp/V1 And Vc1 Communication

    Wrong sequence of fragments Wrong data length during 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...

  • Page 100: A 3 Format Of The Parameter Telegram

    FLS FLM PB SYS PRO UM E 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.

  • Page 101: Appendix

    Byte 3 to n n data bytes Following one fail-safe block: Byte x Bit 7 to bit 6 10: Fail-safe value block ID Bit 5 to bit 0 Length of the data block Byte 3 to n n data bytes 6852_en_02 PHOENIX CONTACT...
  • Page 102 FLS FLM PB SYS PRO UM E If one or several function blocks are present, a header byte follows: Byte x Bit 7 to bit 6 11: Function block ID Bit 5 to bit 0 Entire function block length After that the function blocks are decoded:...

  • Page 103: Ordering Data

    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 For additional information about Fieldline devices and accessories, visit the Phoenix Contact e-shop at www.phoenixcontact.com.
  • Page 104 FLS FLM PB SYS PRO UM E PHOENIX CONTACT 6852_en_02...
  • Page 105 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 & Co. KG Documentation Services 32823 Blomberg...
  • Page 106 Job function: City, ZIP Phone: code: Country: Fax: Document: Designation: FLS FLM PB SYS PRO UM E Revision: Order No.: 26 99 07 9 My Opinion on the Document Form In part Is the table of contents clearly arranged? Are the figures/diagrams easy to understand/helpful?

Table of Contents