Table of Contents
Advertisement
Advertisement
Chapters
Table of Contents
Related Manuals for Beckhoff BK3 0 Series
Summary of Contents for Beckhoff BK3 0 Series
- Page 1 Documentation BK3xx0 Bus Coupler for PROFIBUS-DP Version: 4.3.0 Date: 2019-04-03...
-
Page 3: Table Of Contents
Documentation issue status ...................... 8 2 Product overview............................ 9 BK30x0, BK3100, BK3110, BK3120, LC3100 - Technical data ............ 9 BK3150 - Technical data ......................... 11 BK35x0 - Technical data (optical fibers) .................. 13 The Beckhoff Bus Terminal system .................... 14 PROFIBUS introduction........................ 15 2.5.1 PROFIBUS DP ........................ 15 2.5.2 PROFIBUS DPV1 ...................... - Page 4 Table of contents 5.1.2 K-bus Cycle ........................ 53 DPV1 - acyclic data transfer ...................... 56 5.2.1 DPV1 Interface ........................ 56 5.2.2 Assignment of the DPV1 slot number................ 57 5.2.3 DPV1 at the coupler...................... 58 6 Diagnostics and error handling...................... 61 LEDs .............................. 61 DP diagnostics.......................... 64 6.2.1 DP Diagnostic Data (DiagData) ..................
-
Page 5: Foreword
The TwinCAT Technology is covered, including but not limited to the following patent applications and patents: EP0851348, US6167425 with corresponding applications or registrations in various other countries. ® EtherCAT is registered trademark and patented technology, licensed by Beckhoff Automation GmbH, Germany. BK3xx0 Version: 4.3.0... - Page 6 Foreword Copyright © Beckhoff Automation GmbH & Co. KG, Germany. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization are prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design.
-
Page 7: Safety Instructions
All the components are supplied in particular hardware and software configurations appropriate for the application. Modifications to hardware or software configurations other than those described in the documentation are not permitted, and nullify the liability of Beckhoff Automation GmbH & Co. KG. Personnel qualification This description is only intended for trained specialists in control, automation and drive engineering who are familiar with the applicable national standards. -
Page 8: Documentation Issue Status
Foreword Documentation issue status Version Stand 4.3.0 • Design of the safety instructions adapted to IEC 82079-1 • Technical data updated • Chapter Instructions for ESD protection added • ATEX added • Update structure 4.2.0 • Mounting and wiring updated 4.1.0 •... -
Page 9: Product Overview
Product overview Product overview BK30x0, BK3100, BK3110, BK3120, LC3100 - Technical data Fig. 1: BK3120 and LC3100 - Bus Couplers for PROFIBUS DP BK3xx0 Version: 4.3.0... - Page 10 Product overview Technical data Type BK3000, BK3010 BK3100, BK3110 BK3120 LC3100 Number of Bus Terminals 64 64 (255 with K-bus exten- sion) Digital peripheral signals 512 inputs/outputs (BK3x00) max. 1020 inputs/outputs 256 inputs/outputs 256 inputs/outputs (BK3x10) Analog peripheral signals 128 inputs/outputs (BK3x00) max.
-
Page 11: Bk3150 - Technical Data
Product overview BK3150 - Technical data Fig. 2: BK3150 - Bus Coupler for PROFIBUS DP BK3xx0 Version: 4.3.0... - Page 12 Product overview Technical data BK3150 Type BK3150 Number of Bus Terminals 64 (255 with K-bus extension) Digital peripheral signals 256 inputs/outputs (BK3x10) Analog peripheral signals 128 inputs/outputs (BK3x00) Configuration possibility Via the KS2000 configuration software or the controller Max. number of bytes 128 bytes (DP operation only) (inputs and outputs) Baud rate (automatic detection)
-
Page 13: Bk35X0 - Technical Data (Optical Fibers)
Product overview BK35x0 - Technical data (optical fibers) Fig. 3: BK3500 and BK3520 - Bus Couplers with optical fiber connection for PROFIBUS DP Technical data Type BK3500 BK3520 Number of Bus Terminals 64 (255 with K-bus extension) Digital peripheral signals max. 512 inputs/outputs max. -
Page 14: The Beckhoff Bus Terminal System
Bus Couplers for all usual bus systems The Beckhoff Bus Terminal system unites the advantages of a bus system with the possibilities of the compact series terminal. Bus Terminals can be driven within all the usual bus systems, thus reducing the controller parts count. -
Page 15: Profibus Introduction
Product overview K-bus The K-bus is the data path within a terminal strip. The K-bus is led through from the Bus Coupler through all the terminals via six contacts on the terminals' side walls. The end terminal terminates the K-bus. The user does not have to learn anything about the function of the K-bus or about the internal workings of the terminals and the Bus Coupler. - Page 16 Product overview checking the IdentNumber (unique to each DP device)), of DPV1-/DPV2 parameters and of application- specific parameters that only have to be transmitted once during the StartUp. If an error is found in the parameter data, this is indicated in the diagnostic data, and the slave either remains in or enters the WAIT- PRM state.
-
Page 17: Profibus Dpv1
Product overview 2.5.2 PROFIBUS DPV1 PROFIBUS DPV1 refers primarily to the read and write telegrams, with which data sets in the slave are acyclically accessed. A distinction between a Class 1 (C1) and a Class 2 (C2) master is also made for DPV1. The acyclic Class 1 or Class 2 connections differ in that the acyclic C1 connection is established with the DP startup of the cyclic DP mode. -
Page 18: Mounting And Wiring
Fig. 4: Spring contacts of the Beckhoff I/O components Dimensions The Beckhoff Bus Terminal system is characterized by low physical volume and high modularity. When planning a project it must be assumed that at least one Bus Coupler and a number of Bus Terminals will be used. -
Page 19: Mounting
Mounting and wiring Fig. 5: Dimensions, using BK3120 and LC3100 as examples The total width in practical cases is composed of the width of the Bus Coupler with the KL9010 Bus End Terminal and the width of the Bus Terminals in use. Depending on function, the Bus Terminals are 12 mm or 24 mm wide. -
Page 20: Fig. 6 Release The Locking Mechanism By Pulling The Orange Tab
Mounting and wiring Fig. 6: Release the locking mechanism by pulling the orange tab Up to 64 Bus Terminals can be attached to the Bus Coupler on the right hand side. When plugging the components together, be sure to assemble the housings with groove and tongue against each other. A properly working connection cannot be made by pushing the housings together on the mounting rail. -
Page 21: Connection
Mounting and wiring Connection 3.4.1 Connection system WARNING Risk of electric shock and damage of device! Bring the bus terminal system into a safe, powered down state before starting installation, disassembly or wiring of the bus terminals! Overview The Bus Terminal system offers different connection options for optimum adaptation to the respective application: •... -
Page 22: Wiring
Mounting and wiring A tab for strain relief of the cable simplifies assembly in many applications and prevents tangling of individual connection wires when the connector is removed. Conductor cross sections between 0.08 mm and 2.5 mm can continue to be used with the proven spring force technology. -
Page 23: Fig. 10 High Density Terminals
Mounting and wiring Terminals for standard wiring ELxxxx/KLxxxx and for pluggable wiring ESxxxx/KSxxxx Fig. 11: Connecting a cable on a terminal point Up to eight terminal points enable the connection of solid or finely stranded cables to the Bus Terminal. The terminal points are implemented in spring force technology. -
Page 24: Potential Groups, Insulation Testing And Pe
3.4.3 Potential groups, insulation testing and PE Potential groups A Beckhoff Bus Terminal block usually has three different potential groups: • The fieldbus interface is electrically isolated (except for individual Low Cost couplers) and forms the first potential group. • Bus Coupler / Bus Terminal Controller logic, K-bus and terminal logic form a second electrically isolated potential group. -
Page 25: Fig. 13 Power Contact On The Left
Mounting and wiring Fig. 13: Power contact on the left It should be noted that, for reasons of electromagnetic compatibility, the PE contacts are capacitively coupled to the mounting rail. This can both lead to misleading results and to damaging the terminal during insulation testing (e.g. -
Page 26: Power Supply
Mounting and wiring 3.4.4 Power supply Supply of Bus Coupler / Bus Terminal Controller and Bus Terminals (Us) 3.4.4.1 BKxx00, BKxx10, BKxx20 and LCxxxx The Bus Couplers / Bus Terminal Controllers require an operating voltage of 24 V The connection is made by means of the upper spring-loaded terminals labelled 24 V and 0 V. This supply voltage is used for the electronic components of the Bus Coupler and Bus Terminal Controllers and (via the K-bus) the electronic components of the Bus Terminals. -
Page 27: Fig. 15 Power Supply Connections For Bkxx50 And Bkxx51
Mounting and wiring 3.4.4.2 BKxx50 and BKxx51 The Bus Couplers / Bus Terminal Controllers require an operating voltage of 24 V . Use a 4 A fuse or a Class 2 power supply to comply with the UL requirements. The connection is made by means of the upper spring-loaded terminals labelled Us and GNDs. This supply voltage is used for the electronic components of the Bus Coupler and Bus Terminal Controllers and (via the K-bus) the electronic components of the Bus Terminals. -
Page 28: Fig. 17 Potential Connection Diagram Of An Ekxxxx
Mounting and wiring 3.4.4.3 Configuration and Programming Interface The standard Bus Couplers have an RS232 interface at the bottom of the front face. The miniature plug connector can be connected to a PC using a connecting cable and the KS2000 configuration software. The interface permits the Bus Terminals to be configured, for example adjusting the amplification factors of the analog channels. -
Page 29: Profibus Cabling
Mounting and wiring 3.4.5 PROFIBUS cabling 3.4.5.1 PROFIBUS Connection M12 round connector The M12 socket is inverse-coded and has five pins. Pin 1 transfers 5 V pin 3 transfers GND for the active termination resistor. These must never be misused for other functions, as this can lead to destruction of the device. -
Page 30: Fig. 21 Pin Assignment Socket/Plug Connector Fieldbus Box Modules
Mounting and wiring Connection of the Fieldbus Box modules The Fieldbus Box modules are connected either directly or via a T-piece (or Y-piece). The B318 series features a socket and a plug connector, i.e. this is where the PROFIBUS is routed in the module. The supply voltage (+5 V ) for the termination resistor is only present at the socket. -
Page 31: Fig. 22 Profibus Cable Assignment
Recommended cables Installation is made a great deal more straightforward if preassembled cables from Beckhoff are used! Wiring errors are avoided, and commissioning is more rapidly completed. The Beckhoff range includes fieldbus cables, power supply cables, sensor cables and accessories such as termination resistors and T-pieces. - Page 32 Mounting and wiring Baud rate in kbits/sec 19,2 93,75 187,5 1500 12000 Cable length in m 1200 1200 1200 1000 Stubs up to 1500 kbaud <6.6 m; at 12 Mbaud stub segments should not be used. Bus segments A bus segment consists of at most 32 devices. 126 devices are permitted in a PROFIBUS network. Repeaters are required to refresh the signal in order to achieve this number.
-
Page 33: Atex
80°C at the wire branching points, then cables must be selected whose tempera- ture data correspond to the actual measured temperature values! • Observe the permissible ambient temperature range of 0 to 55°C for the use of Beckhoff fieldbus compo- nents standard temperature range in potentially explosive areas! •... -
Page 34: Atex - Special Conditions (Extended Temperature Range)
80°C at the wire branching points, then cables must be selected whose tempera- ture data correspond to the actual measured temperature values! • Observe the permissible ambient temperature range of -25 to 60°C for the use of Beckhoff fieldbus com- ponents with extended temperature range (ET) in potentially explosive areas! •... -
Page 35: Parameterization And Commissioning
Parameterization and commissioning Parameterization and commissioning Start-up behaviour of the Bus Coupler Immediately after being switched on, the Bus Coupler checks, in the course of a self-test, all the functions of its components and the communication on the K-bus/E-bus. The red I/O LED blinks while this is happening. After completion of the self-test, the Bus Coupler starts to test the attached Bus Terminals (the "Bus Terminal Test"), and reads in the configuration. - Page 36 Parameterization and commissioning Byte Value Description GSD file MSAC_C1 connection is not active (default) Standard MSAC_C1 connection is active (see DPV1 [} 56]) CfgData checking is active (default) Extended CfgData checking deactivated (see Deactivating the CfgData checking [} 73]) Diagnostic data is transferred in a form compatible with the BK3100 Extended Diagnostic data is transferred in a form compatible with DPV1 (default) K-bus cycle counter is not active (default)
- Page 37 Parameterization and commissioning Byte Value Description GSD file Reaction to PROFIBUS error: K-bus cycle is abandoned (default, Standard digital outputs become 0, complex outputs are set to a configured substitute value) (see Reaction to PROFIBUS errors [} 69]) Reaction to PROFIBUS error: K-bus outputs become 0 Reaction to PROFIBUS error: K-bus outputs remain unchanged Reaction to K-bus error: DP data exchange is abandoned (default) Standard...
-
Page 38: Technical Data - Overview
Parameterization and commissioning Technical data - overview Description BK3010 BK3110 BK3120 BK3150 BK3500 BK3520 LC3100 BC3100 Number of Bus Terminals Baud rate [Mbaud] Physical basis RS 485 RS 485 RS 485 RS 485 Optical Optical RS 485 RS 485 fibers fibers UserPrm Data DPV1 Services... -
Page 39: Configuration Of Complex Modules
Parameterization and commissioning 4.4.3 Configuration of Complex Modules After the DP modules for the activated functions of the Bus Coupler have been added to the Bus Coupler in the DP configuration tool, the next step is for the complex terminals (KL15xx, KL25xx, KL3xxx, KL4xxx, KL5xxx, KL6xxx, KL8xxx) to be added in the sequence in which they are plugged in, regardless of whether digital terminals are plugged in between the complex terminals, or of how many there may be: Complex function... - Page 40 Parameterization and commissioning Complex function Description Associated CfgData (as module hex code) KL5001 compact KL5001 - only the 32 bit input value is transmitted 0x93 (in GSD file) 0xD1 (alternatively) KL5001 complex KL5001 - 40 bits of input/output are transmitted, so that 0xB4 (in GSD file) access can be had to the terminal's registers in addition to 0xB5 (alternatively)
-
Page 41: Configuration Of Digital Modules
8) and that the sum of the digital inputs is 32 bits (the next number larger than 26 divisible by 8). 4.4.5 GSD Files GSD files are required for integrating the PROFIBUS couplers in DP configuration tools. GSD files can be found online at http://www.beckhoff.com/english/download/bkconfg.htm BK3xx0 Version: 4.3.0... -
Page 42: Ks2000 - Introduction
Parameterization and commissioning Note regarding GSD file The GSD file contains a maximum of 244 bytes of input, output and configuration data. These are the maximum values. Below are the default of values and the setting options. DP buffer Default Maximum size Inputs Outputs... -
Page 43: Configuration Via Twincat
TwinCAT turns any compatible PC into a real-time controller, an IEC 61131-3 Multi-PLC, NC positioning system, the corresponding programming environment and user interface. TwinCAT supports several different PROFIBUS DP PC cards. Beckhoff recommends the PROFIBUS DP PCI master card FC3101, which can also be obtained as a two-channel version (FC3102). -
Page 44: Fig. 25 Twincat System Manager
Parameterization and commissioning Fig. 25: TwinCAT System Manager For applications without TwinCAT PLC or NC, the TwinCAT System Manager configures the programming interfaces for a wide range of application programs: • ActiveX control (ADS-OCX) for e.g. Visual Basic, Visual C++, Delphi, etc. •... -
Page 45: Fig. 26 Configuration Of The Profibus Dp I/O Modules - Selection Of The Profibus Dp Master Pc Card
Parameterization and commissioning Fig. 26: Configuration of the PROFIBUS DP I/O modules - selection of the PROFIBUS DP master PC card 2. Following the master card, the bus nodes are then inserted: Fig. 27: Configuration of the PROFIBUS DP I/O modules - inserting the bus nodes 3. -
Page 46: Configuration With Siemens S7 Controller
• Go to Extras \ Install new GSD in the hardware catalog for your Step7. • Select the directory in which the Beckhoff GSD is located, and import the files. • It can then be found in the hardware catalogue under PROFIBUS DP \ Further field devices \ I/O. -
Page 47: Fig. 31 Parameter Data For The Bk3120
Parameterization and commissioning Fig. 31: Parameter data for the BK3120 Parameter data Name DPV1 service (class 1) DPV1 Services [} 56] Reaction to Bus Terminal error Reaction to Bus Terminal error [} 69] Terminal bus diagnostics PROFIBUS diagnosis [} 70] Digital terminal diagnostic data Digital Bus Terminal diagnostics [} 70] Data format Data format [} 35]... -
Page 48: Fig. 32 Example For Entering Individual Bytes
Parameterization and commissioning Digital outputs 11 x KL2xx4, i.e. 10 x 4 bit = 44 bit 44 bit / 8 = 5.5 bytes, rounded up to 6 bytes, i.e. enter 6 x 8 bit or 1 x 48 bit or 1 x 8 bit + 1 x 40 bit etc. (see Fig. Example for entering individual bytes and Fig. Example for entering contiguous bytes) Fig. 32: Example for entering individual bytes. Maximum config data Each individual byte requires one byte of ConfigData. -
Page 49: Fig. 33 Example For Entering Associated Bytes
Parameterization and commissioning Fig. 33: Example for entering associated bytes. Configuration of the BK3120 module with complex and digital input/outputs Byte-oriented modules are the first to be mapped into the process image, and for this reason all the complex modules must first be entered in the sequence in which they are plugged into the Bus Coupler. For some byte-oriented Bus Terminals, it is possible to distinguish between compact and complex mapping. -
Page 50: Fig. 34 Example For Compact Representation Of The Bus Terminal Kl3312
Parameterization and commissioning Fig. 34: Example for compact representation of the Bus Terminal KL3312 Example 2.b: 1 x BK3120 2 x KL1012 1 x KL2022 1 x KL3312 complex mapping 1 x KL9010 Fig. 35: Example for compact representation of the Bus Terminal KL3312 Version: 4.3.0 BK3xx0... -
Page 51: Profibus Dp Communication
PROFIBUS DP communication PROFIBUS DP communication DataExchange - cyclic data exchange 5.1.1 Process data, process image The Bus Coupler includes different memory areas, each having a capacity of 256 words. Telegrams passing over the Lightbus can specifically access any desired memory cell. The control and status bytes in the Lightbus telegrams can be used to distinguish between two relevant regions of the memory and to address them separately. -
Page 52: Fig. 36 Output Data In The Bus Coupler
PROFIBUS DP communication Default assignment of the inputs and outputs to the process image Once it has been switched on, the Bus Coupler finds out how many Bus Terminals are inserted, and creates an assignment list. The analog and digital channels, divided into inputs and outputs, are assembled into separate parts of this list. -
Page 53: K-Bus Cycle
32 + number of analog output channels x 42) The K-bus cycle time can be read via DPV1 [} 60]. If TwinCAT is used, this is possible on the "Beckhoff" tab of the DP coupler in the System Manager. -
Page 54: Fig. 40 K-Bus Mode Fast Freerun
PROFIBUS DP communication Fast FreeRun To avoid the jitter resulting from acyclic communication or events and to achieve fast K-bus update times, the Fast FreeRun mode can be activated. The K-bus cycle is called by a higher priority task, controlled by a timer. -
Page 55: Fig. 42 K-Bus - Synchronous Mode With Optimized Input Update (One Cycle)
PROFIBUS DP communication Fig. 42: K-bus - synchronous mode with optimized input update (one cycle) The delay time is set by means of the UserPrmData [} 35] (in µs, in Motorola format). The extended GSD file of the Bus Coupler is, however, necessary for this: Byte Value: Description Delay time (in µs) high byte... -
Page 56: Dpv1 - Acyclic Data Transfer
PROFIBUS DP communication Byte Value Description Dummy output byte activated It is also necessary for the dummy output byte to be configured in the CfgData before the complex terminals: CfgData DP modules 0x20 Dummy output byte K-bus cycle counter In order for the master to be able to check reliably whether precisely one (or two) K-bus cycles are always being carried out during one DP cycle, a K-bus cycle counter can be transferred in the input data from the Bus Coupler to the master. -
Page 57: Assignment Of The Dpv1 Slot Number
PROFIBUS DP communication PROFIBUS coupler data (Slot_Number = 0) The data associated with the PROFIBUS coupler is addressed via an index: Index Access Description Module assignment in multi-configuration mode [} 73] Firmware information [} 59] 9-19 Device configuration [} 59] (Table 9) K-bus status [} 60] (Table 90) Internal cycle time [} 60] Commands: local bus reset [} 69], starting or stopping the internal cycle time measurement [} 60]... -
Page 58: Dpv1 At The Coupler
PROFIBUS DP communication 5.2.3 DPV1 at the coupler 5.2.3.1 Module Assignment The multi-configuration mode [} 73] is possible with a maximum of 128 modules (terminals, IE modules, etc.). The specification of which of the modules configured in the CfgData are indeed inserted can be written with DPV1 Write and read with DPV1 Read. - Page 59 PROFIBUS DP communication 5.2.3.2 Firmware Information The following firmware information can be read through DPV1. The data is transferred in Intel format (low byte first): Slot number Index Byte Description Bus Coupler number Software version Manufacturer type (table 0, register 245) Coupler type (table 0, register 246) Bus Coupler type (table 0, register 247) 10-11...
- Page 60 PROFIBUS DP communication Error codes in the write response Error_Code_1 Error_Code_2 0xBE Number of terminals 0xBF First faulty byte in the written data 5.2.3.4 K-bus status The K-bus status can be read through DPV1. The data is transferred in Intel format (low byte first): Slot number Index Byte Description...
-
Page 61: Diagnostics And Error Handling
Diagnostics and error handling Diagnostics and error handling LEDs The Bus Coupler has two groups of LEDs for the display of status. The upper group (BK3xx0) or left hand group (LC3100) indicates the state of the fieldbus. On the upper right hand side of the BK3xx0 Bus Coupler are two more green LEDs that indicate the supply voltage. - Page 62 Diagnostics and error handling DIA-LED blink codes If an error occurs in the paramétrisation or configuration during DP start-up [} 67], this is indicated both through the fieldbus LEDs and in the diagnostic data. Flashing Code fast blinking Start of the error code First slow sequence Error code Second slow sequence...
- Page 63 Diagnostics and error handling K-bus LEDs (local errors) Two LEDs, the K-bus LEDs, indicate the operational state of the Bus Terminals and the connection to these Bus Terminals. The green LED (I/O RUN) lights up in order to indicate fault-free operation. The red LED (I/O ERR) flashes with two different frequencies in order to indicate an error.
-
Page 64: Dp Diagnostics
DP Diagnostic Data (DiagData) The DP diagnostic data consists of six bytes of DP standard diagnosis, along with up to 238 bytes of device- specific diagnostic data. The device-specific diagnostic data for Beckhoff slaves is represented in the DPV1 status message. - Page 65 Diagnostics and error handling DP standard diagnostic data Offset Meaning 0x00.0 StationNonExistent: slave did not reply to the last telegram 0x00.1 StationNotReady: slave still processing the Set_Prm / Chk_Cfg telegram 0x00.2 CfgFault: slave signaling a configuration error 0x00.3 ExtDiag: extended DiagData available and valid 0x00.4 NotSupported: slave does not support a feature requested via Set_Prm or Global_Control 0x00.5...
- Page 66 Diagnostics and error handling Byte Description The length of the DPV1 status message (including this byte) StatusType: the StatusType identifies the format of the diagnostic data starting at byte 16 (0x81: max. 64 modules, 0xA1: more than 64 modules) SlotNumber: always 0 Specifier: always 0 EEPROM checksum error (can be cleared by setting the manufacturers setting through KS2000 or DPV1 [} 56], followed by a power off/power on cycle)
-
Page 67: Errors During Dp Start-Up
Diagnostics and error handling Couplers with a maximum of more than 64 possible modules Byte Description Module number (1-255) with an error (bit 6 of the status bytes is set, except for the serial interface modules (KL6001, KL6011, KL6021, IP6002, IP6012, IP6022, IE6002, IE6012, IE6022), where bit 3 of the status byte is set) Associated channel number (0-3) Status byte of the faulty channel (bits 0-5) - Page 68 Diagnostics and error handling Errors when checking the CfgData Error code 2 Error code 2 indicates that a byte in the CfgData is not correct. The error argument describes which CfgData byte has been detected as containing an error (the offset of the faulty byte + 1). Error code 5 Error code 5 indicates that the length of the digital outputs (in bytes) calculated from the CfgData is not correct.
-
Page 69: Reaction To Profibus Error
Diagnostics and error handling Error code 10* Error during the register communication. The settings to be written via the UserPrm data were executed incorrectly. Error argument Description Problems with terminal x Error code 11* Error during the register communication. The settings to be written via the UserPrm data were aborted with a timeout. -
Page 70: Terminal Diagnostics
Diagnostics and error handling Signaling the K-bus error A K-bus error is indicated both on the I/O-ERR LED and in the DPV1 status message in the DP diagnostic data [} 64] (bytes 11-13). Byte Description too many K-bus command errors too many K-bus timeouts too many K-bus receive errors too many K-bus transmit errors K-bus reset error... - Page 71 Diagnostics and error handling but the controller program is only informed of this in the following cycle or the one after that. If the diagnostic bits of digital terminals with diagnostics or the status of complex terminals are mapped to the process image, the control program always has a consistent state between process and diagnostic data.
-
Page 72: Extended Functions
Extended functions Extended functions 2-byte PLC Interface Checking the CfgData can be deactivated if a DP master is not capable of operating with the modules listed in the GSD file. In that case the master can send any CfgData, and as many inputs and outputs are transferred as are described by the CfgData. -
Page 73: Deactivating The Cfgdata Check
Extended functions Deactivating the CfgData Check Checking the CfgData can be deactivated if a DP master is not capable of operating with the modules listed in the GSD file. In that case the master can send any CfgData, and as many inputs and outputs are transferred as are described by the CfgData. - Page 74 Extended functions Assigning the Bus Terminals to freely chosen process image addresses Because digital terminals are always grouped into bytes, which therefore means that the smallest DP configuration module is an 8-bit module, a difficulty arises when the associated terminals are to be distributed over a number of bytes in the PLC process image.
- Page 75 Extended functions Byte Description Assignment for terminal 1 0: DP DataExchange (default) 2: disabled (Multi-Config mode) Assignment for terminal 2 0: DP DataExchange (default) 2: disabled (Multi-Config mode) Assignment for terminal 3 0: DP DataExchange (default) 2: disabled (Multi-Config mode) Assignment for terminal 4 0: DP DataExchange (default) 2: disabled (Multi-Config mode)
-
Page 76: Changing The Size Of The Process Data
Extended functions Enabling/disabling via the 2-byte PLC interface or through KS2000 The terminals are enabled or disabled through table 1, registers 0-31: Register Description Assignment for terminal 1 0: DP-DataExchange (Default) 2: disabled (Multi-Config-Mode) Assignment for terminal 2 0: DP-DataExchange (Default) 2: disabled (Multi-Config-Mode) Assignment for terminal 3 0: DP-DataExchange (Default) -
Page 77: Bus Coupler Versions In Multi-Configuration Mode
Production machines often consist of a machine part that is always present in the machine and of machine extensions that may be added as options. This division also usually applies as well both to the software (the control program) and to the hardware (the necessary process signals via Beckhoff Bus Terminals) BK3xx0... - Page 78 DP slaves, a different configuration of the PROFIBUS DP master interface is necessary in such cases. The following sections explain how this problem can be solved with Beckhoff Bus Couplers, using a single configuration of the PROFIBUS DP master interface.
- Page 79 Extended functions Fig. 47: Process image of the production machine The process signals of a DP slave (Bus Coupler BK3110, BK3120 or BK3520) are always transferred in a Data_Exchange telegram, in which the outputs are sent by the DP master and the inputs are received in the associated telegram response.
- Page 80 Extended functions Fig. 48: Process images of the two different machine configurations In order to solve the problem of the changed mapping rule, a facility is provided in the BK3110, BK3120 and BK3520 Bus Couplers through which the mapping can be carried out in the Bus Coupler (multi-configuration mode), so that they always exchange the same process image with the PROFIBUS DP master, independently of the Bus Terminals present: Setting the Bus Terminal extension in the Bus Coupler...
- Page 81 Extended functions If the Bus Coupler is not already being operated with the maximum Bus Terminal implementation level, the PROFIBUS DP configuration will not agree with the Bus Terminal structure that it finds. So that the Bus Coupler can nevertheless represent the process signals from the connected Bus Terminals in the process image that is to be exchanged with the PROFIBUS DP master, the mapping rule is now required.
- Page 82 Extended functions State transitions in the Bus Coupler If the PROFIBUS DP configuration received does match the Bus Terminal configuration in multi-configuration mode, the Bus Coupler sets the "static diagnostics" bit in the PROFIBUS DP diagnostic data and delays the execution of a terminal bus cycle (I/O RUN LED remains off).
- Page 83 Extended functions Fig. 50: State transitions in the Bus Coupler BK3xx0 Version: 4.3.0...
-
Page 84: Appendix
Appendix Appendix General operating conditions The following conditions must be met in order to ensure flawless operation of the fieldbus components. Environmental conditions Operation The components may not be used without additional protection in the following locations: • in difficult environments, such as where there are corrosive vapors or gases, or high dust levels •... -
Page 85: Approvals
Supply voltage 24 V Data transfer rate 2.5 Mbit/s Manufacturer Beckhoff Automation GmbH CE mark Conformity mark UL mark Mark for UL approval. UL stands for the Underwriters Laboratories Inc., the leading certification Organisation for North America, based in the USA. -
Page 86: Bibliography
Appendix Protection class IP20 conforms to EN60529 Bibliography German books PROFIBUS • PROFIBUS-DP/DPV1 Basic principles, tips and tricks for users by Manfred Popp ISBN: 3778527819 General fieldbus technology • Gerhard Gruhler (Pub.): Fieldbuses and device communication systems Practical knowledge with comparison options Franzis Verlag 2001 244 pages ISBN 3-7723-5745-8... - Page 87 Appendix IP20, IP65, IP66, IP67 Protection class (contact, water, dust) K-bus Terminal Bus: Internal bus for communication between Bus Coupler and Bus Terminals PROFIBUS User Organisation (seewww.profibus.de) Repeater Provides signal conditioning, connecting individual bus segments Programmable logic controller Sync mode This command makes the slave hold its outputs unchanged until it receives the Sync telegram.
-
Page 88: Support And Service
Beckhoff's branch offices and representatives Please contact your Beckhoff branch office or representative for local support and service on Beckhoff products! The addresses of Beckhoff's branch offices and representatives round the world can be found on her internet pages: http://www.beckhoff.com You will also find further documentation for Beckhoff components there. - Page 89 BK3150 - Bus Coupler for PROFIBUS DP ................. Fig. 3 BK3500 and BK3520 - Bus Couplers with optical fiber connection for PROFIBUS DP....Fig. 4 Spring contacts of the Beckhoff I/O components................. Fig. 5 Dimensions, using BK3120 and LC3100 as examples..............Fig. 6 Release the locking mechanism by pulling the orange tab............
- Page 90 List of illustrations Fig. 44 LEDs BK3120 and BK3150 ......................Fig. 45 LEDs LC3100 ..........................Fig. 46 Representation of a production machine ..................Fig. 47 Process image of the production machine................... Fig. 48 Process images of the two different machine configurations............Fig.
Need help?
Do you have a question about the BK3 0 Series and is the answer not in the manual?
Questions and answers