L−force Communication Ä.G÷hä EDSMF2133IB .
i 1 2 3 4 5 6 2 Contents About this documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.1 Document history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.2 Conventions used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.3 Terminology used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 7 8 i 6.5 Setting the software compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 6.6 Preparing the standard device for communication . . . . . . . . . . . . . . . . . . . . . . . . 6.6.1 Frequency inverter 82XX / 8200 vector . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.2 93XX servo inverter / 9300 Servo PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.3 Drive PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i 9 10 11 12 13 4 Contents 8.2 DRIVECOM parameter data channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.1 Addressing of the parameter data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.2 Addressing of the Lenze parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.3 Telegram structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.4 Error codes (DRIVECOM) . . . . . . . . . . . .
About this documentation 1 0Fig. 0Tab. 0 1 About this documentation Contents This documentation only contains descriptions for the EMF2133IB communication module (PROFIBUS−DP). ) Note! This documentation supplements the mounting instructions supplied with the communication module and the documentations for the standard devices used. The mounting instructions contain safety instructions which must be observed! ƒ The features and functions of the communication module are described in detail.
1 About this documentation Document history 1.1 Document history Material no. Version Description − 1.0 11/2001 TD06 First edition − 2.0 06/2004 TD06 l l − 4.0 12/2006 TD17 l l As of software version 1.3: code C1883 added Structural and editorial adjustments Extended descriptions for the use on the ECS servo system. .G÷h 5.0 09/2011 TD14 l l As of software version 1.
About this documentation 1 Conventions used 1.2 Conventions used This documentation uses the following conventions to distinguish between different types of information: Type of information Identification Examples/notes Spelling of numbers Point Decimal separator Decimal Hexadecimal Binary l Nibble Standard notation 0x[0 ... 9, A ... F] In quotation marks Point In general, the decimal point is used. For instance: 1234.56 For example: 1234 For example: 0x60F4 For example: ´100´ For example: ´0110.
1 About this documentation Terminology used 1.3 Terminology used Term Meaning PROFIBUS The term stands for the PROFIBUS−DP variant according to IEC 61158 / IEC 61784. A different PROFIBUS variant is not described in these Instructions. Standard device Lenze controllers/frequency inverters with which the communication module can be used. ^ 12 Controller Frequency inverter 8 Master PROFIBUS station which takes over the master function in the fieldbus system.
About this documentation 1 Notes used 1.4 Notes used The following pictographs and signal words are used in this documentation to indicate dangers and important information: Safety instructions Structure of safety instructions: } Danger! (characterises the type and severity of danger) Note (describes the danger and gives information about how to prevent dangerous situations) Pictograph and signal word Meaning { Danger! Danger of personal injury through dangerous electrical voltage.
2 Safety instructions General safety information 2 Safety instructions ) Note! It is absolutely vital that the stated safety measures are implemented in order to prevent serious injury to persons and damage to material assets. Always keep this documentation to hand in the vicinity of the product during operation. 2.
Safety instructions 2 Device− and application−specific safety instructions 2.2 Device− and application−specific safety instructions ƒ During operation, the communication module must be securely connected to the standard device. ƒ With external voltage supply, always use a separate power supply unit, safely separated in accordance with EN 61800−5−1 in every control cabinet ("SELV" / "PELV"). ƒ Only use cables that comply with the given specifications (¶ 25).
3 Product description Application as directed 3 Product description 3.1 Application as directed The communication module ... ƒ is an accessory module which can be used in conjunction with the following Lenze standard devices: Device type Version Design Variant Explanation HW SW 82EVxxxxxBxxxXX Vx 1x 8200 vector 82CVxxxxxBxxxXX Vx 1x 8200 vector, cold plate 82DVxxxKxBxxxXX Vx 1x 8200 vector, thermally separated Drive PLC EPL 10200 E 1x 8x 33.93XX xE. 2x 1x 33.938X xE.
Product description 3 Identification 3.2 Identification L K 1D74 Type Id.-No. Prod.-No. Ser.-No. Input E82AF000P0B201XX 9371BC019 W 33.2133IB Vx 0X Series Hardware version Software version EDSMF2133IB EN 5.
3 Product description Product features 3.3 14 Product features ƒ Interface module for the PROFIBUS communication system with the PROFIBUS−DP−V0 (DRIVECOM profile) and PROFIBUS−DP−V1 (PROFIdrive) communication profiles ƒ Drive profiles: – DRIVECOM profile "drive technology 20" (can be switched off) – PROFIdrive (can be switched off, state machine and PROFIdrive parameter data channel) ƒ Support of the I&M0 functionality for identifying the standard device ƒ Automatic detection of the baud rate (9.
Product description 3 Connections and interfaces 3.4 Connections and interfaces 01 EMF2133IB 5 7 2131 64 32 16 8 4 2 1 PROFIBUS DP 4 6 Adresse 3 L 2 ON 1 2 3 4 5 6 7 8 OFF 24V DC + _ 2133 2133PFB003 Fig. 3−1 2102LEC007 EMF2133IB communication module (PROFIBUS−DP) Pos. Description 0 1 2 3 Status of the voltage supply (green LED) Status of the PROFIBUS communication (yellow LED) Operating status of the standard device (red/green LED) DIP switches for setting the ...
4 Technical data General data 4 Technical data 4.1 General data Area Order designation PNO ID number Communication profile (DIN 19245 Part 1 and Part 3) Communication medium Interface Drive profile Network topology PROFIBUS nodes Baud rate [kbps] Process data words DP user data length Max. number of stations Max.
Technical data 4 Protective insulation 4.2 Protective insulation { Danger! Dangerous electrical voltage If Lenze controllers are used on a phase earthed mains with a rated mains voltage 400 V, protection against accidental contact is not ensured without implementing external measures.
4 Technical data Communication time Processing time 820X 4.3 Communication time The communication time is the time between the start of a request and the arrival of the corresponding response. The communication times depend on ... 4.3.1 ƒ the processing time in the controller ƒ the transmission delay time – the baud rate – the telegram length Processing time 820X For the 820X series several processing steps are required in the controller, which are processed cyclically.
Technical data 4 Communication time Processing time 821X / 822X / 824X / 8200 vector 4.3.2 4.3.3 Processing time 821X / 822X / 824X / 8200 vector Parameter data Process data 30 ... 50 ms 2 ... 3 ms Processing time 93XX / ECSxS There are no interdependencies between parameter data and process data. 4.3.4 Parameter data Process data Approx. 30 ms + 20 ms tolerance (typical) For some codes, the processing time can be longer (see documentation for 9300 and ECS servo system).
4 Technical data Dimensions Dimensions b L ON 1 2 3 4 5 6 7 8 OFF 2131 64 32 16 8 4 2 1 PROFIBUS DP Adresse 4.4 24V DC + _ 2133 a 18 e1 e 2133PFB003 a b e e1 20 61 mm 75 mm 28 mm 18 mm l EDSMF2133IB EN 5.
Installation 5 5 Installation } Danger! Inappropriate handling of the communication module and the standard device can cause serious personal injury and material damage. Observe the safety instructions and residual hazards described in the documentation for the standard device. ( Stop! Electrostatic discharge Electronic components of the communication module can be damaged or destroyed through electrostatic discharge. Possible consequences: ƒ The communication module is damaged.
5 Installation Mechanical installation 5.1 Mechanical installation 2102LEC014 Fig. 5−1 Attaching the communication module ƒ Plug the communication module onto the standard device (here: 8200 vector). ƒ Tighten the communication module to the standard device using the fixing screw in order to ensure a good PE connection.
Installation 5 Electrical installation Wiring according to EMC (CE−typical drive system) 5.2 Electrical installation 5.2.1 Wiring according to EMC (CE−typical drive system) For wiring according to EMC requirements observe the following points: ) Note! ƒ Separate control cables/data lines from motor cables. ƒ Connect the shields of control cables/data lines at both ends in the case of digital signals.
5 Installation Electrical installation Wiring with a host (master) 5.2.2 Wiring with a host (master) { Danger! You have to provide additional electrical isolation if ... ƒ an 820X and 821X controller is connected to the host and ƒ a safe electrical isolation (reinforced insulation) according to EN 61800−5−1 is required. Basic wiring of the PROFIBUS The connection of the PROFIBUS bus system is shown in the general layout drawing.
Installation 5 Electrical installation Wiring with a host (master) Number of bus devices M R S S S R S 1 S 2 3 2133PFB004 Segment Master (M) Slave (S) Repeater (R) 1 1 2 31 30 − − 2 − 30 1 3 − 30 1 I Tip! Repeaters do not have a device address. When calculating the maximum number of bus devices, they reduce the number of devices by 1 on each side of the segment. Repeaters can be used to build up line and tree topologies. The maximum total bus system expansion depends on ...
5 Installation Electrical installation Wiring with a host (master) Bus cable length The length of the bus cable depends on the baud rate used: Baud rate [kbps] Length [m] 9.6 ... 93.75 1200 187.5 1000 500 400 1500 200 3000 ... 12000 100 ) Note! The baud rate depending on the data volume, cycle time, and number of nodes should only be selected as high as required for the application. I Tip! For high baud rates we recommend to consider the use of optical fibres.
Installation 5 Electrical installation Connection of the PROFIBUS 5.2.3 Connection of the PROFIBUS The PROFIBUS network is connected via the 9−pole Sub−D socket. View 9 6 EDSMF2133IB EN 5.
5 Installation Electrical installation Voltage supply 5.2.4 Voltage supply Internal voltage supply ) Note! Internal voltage supply has been selected in the case of standard devices with an extended AIF interface opening (e.g. front of 8200 vector). The area shown on a grey background in the graphic marks the jumper position. ƒ By default, this is not supplied internally in the standard device. ƒ For internal voltage supply place the jumper on the position indicated below.
Installation 5 Electrical installation Voltage supply External voltage supply ) Note! Always use a separate power supply unit in every control cabinet and safely separate it according to EN 61800−5−1 ("SELV"/"PELV") in the case of external voltage supply and larger distances between the control cabinets. External voltage supply of the communication module is required if communication via the fieldbus is to be maintained even when the power supply of the standard device fails.
5 Installation Electrical installation Cable cross−sections and screw−tightening torques 5.2.5 Cable cross−sections and screw−tightening torques Area Values Electrical connection Plug connector with screw connection Possible connections rigid: 1.5 mm2 (AWG 16) flexible: without wire end ferrule 1.5 mm2 (AWG 16) with wire end ferrule, without plastic sleeve 1.5 mm2 (AWG 16) with wire end ferrule, with plastic sleeve 1.5 mm2 (AWG 16) 30 Tightening torque 0.5 ... 0.6 Nm (4.4 ... 5.
Commissioning 6 Before switching on 6 Commissioning During commissioning, system−dependent data as e.g. motor parameters, operating parameters, responses and parameters for fieldbus communication are selected for the controller. In Lenze devices, this is done via codes. The codes are stored in numerically ascending order in the Lenze controllers and in the plugged−in communication/function modules. In addition to these configuration codes, there are codes for diagnosing and monitoring the bus devices.
6 Commissioning Initial switch−on 6.2 Initial switch−on ) Note! ECS servo system ECS devices cannot be used with the DRIVECOM or PROFIdrive control. ) Note! Manual settings are not required for the baud rate. The communication module is automatically adjusted to the baud rate of the master. Step−by−step commissioning of the communication module with DRIVECOM device control is described below. Step Procedure 1.
Commissioning 6 Initial switch−on Step Procedure 11. It is now possible to communicate with the controller, i.e. l exchange process data (setpoints and actual values); l read all codes; l change all codes that can be written. See the attribute table or code description of the corresponding standard device. Response The yellow LED on the communication module is blinking when the PROFIBUS is active. Enable standard device via terminal. Documentation of the standard device 12. EDSMF2133IB EN 5.
6 Commissioning Configuring the host system (master) 6.3 Configuring the host system (master) The host must be configured before communication with the communication module is possible. Master settings For configuring the PROFIBUS, the device data base file (GSE file) of the communication module has to be imported into the configuring software of the master. I Tip! The GSE file can be downloaded in the "Services & Downloads" area at www.Lenze.com.
Commissioning 6 Configuring the host system (master) ƒ POFIdrive control and DP−V1 parameter data channel Selection text in Len_2133.
6 Commissioning Configuring the host system (master) Defining the user data length The user data length is defined during the initialisation phase (configuration). Up to 12 process data words can be configured (depending on the basic device used). Optionally you can activate the parameter data channel. If the parameter data channel is active, it additionally occupies 4 words of the process data inputs and outputs.
Commissioning 6 Activating the bus terminating resistor 6.4 Activating the bus terminating resistor Bus terminating resistor The PROFIBUS must be terminated by a bus terminating resistor at the physically first and last station. The bus terminating resistor is in the bus connector (¶ 128)and is activated using a switch. ) Note! ƒ If you want to disconnect individual bus devices, ensure that the bus terminators at the cable ends remain active.
6 Commissioning Preparing the standard device for communication Frequency inverter 82XX / 8200 vector 6.6 Preparing the standard device for communication 6.6.1 Frequency inverter 82XX / 8200 vector Step Procedure 1. In order that you can operate the controller via PROFIBUS, set the Lenze parameter "Operating mode" C0001 = 3.
Commissioning 6 Preparing the standard device for communication 93XX servo inverter / 9300 Servo PLC 6.6.2 93XX servo inverter / 9300 Servo PLC Step Procedure 1. 93XX Detailed information ^ 46 4. Select speed setpoint unequal to 0. ^ 47 5. Change to status "READY TO SWITCH ON". Select value for DRIVECOM control word: 0b0000 0000 0111 1110 (0x007E). Wait for status "READY TO START" to be reached. Value for DRIVECOM status word: 0bxxxx xxxx x01x 0001. Change to the "OPERATION ENABLED" state.
6 Commissioning Preparing the standard device for communication Drive PLC 6.6.3 Drive PLC Step Procedure 1. Implement the system blocks AIF−IN1 ... 3, AIF−OUT1 ... 3 and, if available, the AIF management into the control configuration of the IEC61131 project. The controller can now accept control and parameter setting data via the PROFIBUS. Select speed setpoint unequal to 0. 2. 3. 4. 5. 6. 7. 40 Change to status "READY TO SWITCH ON".
Commissioning 6 Preparing the standard device for communication Axis modules ECSxS / ECSxA 6.6.4 Axis modules ECSxS / ECSxA Step Procedure 1. ECSxS 2. 3.
6 Commissioning Setting the node address Setting via code 6.7 Setting the node address ) Note! ƒ The addresses of all controllers connected to the network must differ from each other. ƒ If the DIP switches S1 ... S7 are in the OFF position, the code setting for the station address is active (Lenze setting). ƒ Switch off the voltage supply of the function module and the controller and then switch it on again to activate the changed settings. The setting of the station address can be freely selected ...
Commissioning 6 Setting the node address Settings by a master (class 2) 6.7.3 Settings by a master (class 2) ƒ With this method only one device must be connected to the bus. This can be achieved by a special switch−on sequence. ƒ In the "Power On" status, the master (class 2) can set a device address via the "Set_Slave_Address" telegram. ƒ Settings made through the master (class 2 only) have an effect on the setting in standard device code C0009.
6 Commissioning Connecting the mains voltage Settings by a master (class 2) 6.8 Connecting the mains voltage ) Note! If you use the external voltage supply for the communication module, please switch it on.
Process data transfer 7 7 Process data transfer request response 2133PFB008 Fig. 7−1 PROFIBUS process data transfer PROFIBUS transmits parameter data and process data between the host (master) and the controllers connected to the bus (slaves). Depending on their time−critical nature, the data are transmitted via different communication channels. ƒ Process data are transmitted via the process data channel. ƒ Process data serve to control the drive controller.
7 Process data transfer Lenze device control Setpoint source selection 7.1 Lenze device control 7.1.1 Setpoint source selection ) Note! Note that the selection of the setpoint source must be set the same in all parameter sets. 82XX / 8200 vector frequency inverters For these controllers the setpoint source selection is determined under code C0001.
Process data transfer 7 Lenze device control Process data signals for 82XX frequency inverters 7.1.2 Process data signals for 82XX frequency inverters Process data telegram from drive Byte 1 Byte 2 Byte 3 Status word High byte ) Byte 4 Actual value Low byte High byte Low byte Note! ƒ Frequency and speed values are scaled with 24000 480 Hz. ƒ Torque values are scaled with 16384 100%. EDSMF2133IB EN 5.
7 Process data transfer Lenze device control Process data signals for 82XX frequency inverters Device status word AIF−STAT for 82XX (C0150, I−5F69) 820X Bit 0 821X / 822X / 824X Assignment Bit 0 Current parameter set 0 1 1 Parameter set 1 or 3 active Parameter set 2 or 4 active 2 1 Pulses for power stage enabled Pulses for power stage inhibited 2 3 Current limit not reached Current limit reached 3 fd fdset fd = fdset 0 1 6 5 Qmin not active Qmin active 6 7 fd 0 fd = 0 7 8 ...
Process data transfer 7 Lenze device control Process data signals for 82XX frequency inverters PAR IMP Imax - / fd=fdsoll fd=fdsoll / HLG Qmin fd>0 RSP B11 B10 B9 B8 STAT 0 0 0 0 0 0 0. ... .. 0 0. ... .. 1 0 1. 1. ... ... .. .. 2 3. ... .. Tü Ugmax R/L RDY .B0 .B1 .B2 .B3 .B4 .B5 .B6 .B7 .B8 .B9 .B10 .B11 .B12 .B13 .B14 .B15 C0050 16 Bit AIF 16 Bit 2141LON012 Fig.
7 Process data transfer Lenze device control Process data signals for 82XX frequency inverters Device control word AIF−CTRL for 82XX (C0135, index 5F78hex) 820X 821X / 822X / 824X Bit 0/1 2 Assignment Bit JOG values 0/1 Bit 1 0 0 0 0 0 C0046 active 0 0 C0046 active 1 JOG1 in C0037 active 0 1 JOG1 in C0037 active 1 0 JOG2 in C0038 active 1 0 JOG2 in C0038 active 1 1 JOG3 in C0039 active 1 1 JOG3 in C0039 active 0 1 CW rotation CCW rotation 0 1 QSP not active QSP active
Process data transfer 7 Lenze device control Process data signals for 82XX frequency inverters .B0 0 0 11 .B1 0 10 1 JOG/ C046 .B2 .B3 R/L QSP .B4 ... ... ... .B8 .B9 16 Bit CINH .B10 TRIP-SET .B11 TRIP-RESET .B12 AIF PAR .B13 .B14 .B15 16 Bit GSB C0046 2141LON010 Fig.
7 Process data transfer Lenze device control Process data signals for 8200 vector frequency inverters 7.1.3 Process data signals for 8200 vector frequency inverters General Digital and analog input and output signals can be configured freely (see 8200 vector" documentation: codes C0410, C0412, C0417 and C0421). The change of code C0001 to 3 starts the preconfiguration of the process data words in the controller (¶ 46).
Process data transfer 7 Lenze device control Process data signals for 8200 vector frequency inverters Device status word AIF−STAT for 8200 vector (C0150, index 5F69hex) Bit Assignment (Lenze setting) Set under C0417/...
7 Process data transfer Lenze device control Process data signals for 8200 vector frequency inverters Process data telegram to drive Byte 1 Byte 2 Control word High byte Low byte Byte 3 Byte 4 AIF−IN.W1 High byte Low byte Byte 5 Byte 6 AIF−IN.W2 High byte Low byte AIF−IN.Wx see C0412. ) Note! ƒ Frequency and speed values are scaled with 24000 480 Hz. ƒ Torque values are scaled with 16384 100%. 54 l EDSMF2133IB EN 5.
Process data transfer 7 Lenze device control Process data signals for 8200 vector frequency inverters Device control word AIF−CTRL for 8200 vector (C0135, index 5F78hex) Assignment (Lenze setting) Bit C0001 = 3 with C0007 51 0/1 2 C0001 = 3 with C0007 > 51 Freely configurable JOG values Bit 1 0 0 0 00 = C0046 active 0 1 01 = NSET1−JOG1 (C0037) active 1 0 10 = NSET1−JOG2 (C0038) active 1 1 11 = NSET1−JOG3 (C0039) active Current direction of rotation (DCTRL1−CW/CCW) Set under C0410/..
7 Process data transfer Lenze device control Process data signals for 8200 vector frequency inverters AIF-IN .B0 .B1 .B2 DCTRL .B3 AIF-CTRL 16 Bit 16 Bit ... ... ... DCTRL CINH .B10 TRIP-SET .B11 TRIP-RESET .B12... ... ... .B15 16 Bit QSP .B4 ... ... ... .B8 .B9 AIF C0410/x = 10 C0410/x = 11 C0410/x = 12 C0410/x = 22 ... ... ... C0410/x = 25 AIF-IN.W1 AIF-IN.W2 C0412/x = 10 C0412/x = 11 2141LON011 Fig.
Process data transfer 7 Lenze device control Process data signal for 9300 servo inverters 7.1.4 Process data signal for 9300 servo inverters The assignment of the process data for the 93XX controller can be changed by configuring the system blocks AIF−IN and AIF−OUT. Process data telegram from drive Byte 1 Byte 2 DRIVECOM status word High byte Low byte Byte 3 Byte 4 Byte 5 AIF−OUT.W1 High byte Low byte Byte 6 AIF−OUT.W2 High byte Low byte Byte 7 Byte 8 AIF−OUT.
7 Process data transfer Lenze device control Process data signal for 9300 servo inverters Device status word AIF−STAT for 93XX Bit 9300 servo inverter C0005 = 1xx3 C0005 = 4xx3 C0005 = 5xx3 C0005 = 6xx3, 7xx3 0 DCTRL−PAR1−0 DCTRL−PAR1−0 DCTRL−PAR1−0 DCTRL−PAR1−0 1 DCTRL−IMP DCTRL−IMP DCTRL−IMP DCTRL−IMP 2 MCTRL−IMAX MCTRL−IMAX REF−OK REF−OK 3 MCTRL−MMAX Not used MCTRL−MMAX Not used 4 NSET−RFG−I=0 MCTRL−IMAX negated NSET−RFG−I=0 MCTRL−IMAX negated 5 QMIN QMIN REF−BUSY REF−
Process data transfer 7 Lenze device control Process data signal for 9300 servo inverters 9300 POS 9300 CRV 9300 vector C0005 = 2xxx3 C0005 = xxx3 C0005 = 1xxx, 2xxx, 3xxx, 5xxx, 10xxx, 11xxx C0005 = 4xx3 C0005 = 6xx3, 7xx3 0 Not used CERR1−ERR DCTRL−PAR1−0 DCTRL−PAR1−0 DCTRL−PAR1−0 1 DCTRL−IMP DCTRL−IMP DCTRL−IMP DCTRL−IMP DCTRL−IMP 2 POS−REF−OK MCTRL−IMAX MCTRL−IMAX MCTRL−IMAX MCTRL−IMAX 3 Not used MCTRL−MMAX MCTRL−MMAX MCTRL−IMAX negated MCTRL−MMAX 4 MCTRL−MMAX negated
7 Process data transfer Lenze device control Process data signal for 9300 servo inverters Process data telegram to drive Byte 1 Byte 2 Control word High byte Low byte Byte 3 Byte 4 Byte 5 AIF−IN.W1 High byte Low byte Byte 6 AIF−IN.W2 High byte Byte 7 Byte 8 AIF−IN.W3 Low byte High byte Low byte Assignment of AIF−IN.W1 ... W3 depending on the signal configuration selected under C0005: Signal configuration (C0005) AIF−IN.W1 AIF−IN.
Process data transfer 7 Lenze device control Process data signal for 9300 servo inverters Device control word AIF−CTRL for 93XX Bit 9300 servo inverter C0005 = 1xx3 C0005 = 4xx3 C0005 = 5xx3 C0005 = 6xx3, 7xx3 0 NSET−JOG*1 Not used NSET−JOG*1 Not used 1 NSET−JOG*2 Not used NSET−JOG*2 Not used 2 NSET−N−INV NSET−N−INV NSET−N−INV NSET−N−INV 3 AIF−CTRL.QSP AIF−CTRL.QSP AIF−CTRL.QSP AIF−CTRL.
7 Process data transfer Lenze device control Process data signal for 9300 servo inverters A IF -IN D C T R L A IF -C T R L .B 3 Q S P A IF -C T R L .B 8 D IS A B L E A IF -C T R L .B 9 C IN H A IF -C T R L .B 1 0 T R IP -S E T A IF -C T R L .B 1 1 B it 0 T R IP -R E S E T A IF -C T R L .B 0 S te u e rw o rt A IF -C T R L .B 1 A IF -C T R L .B 2 A IF -C T R L .B 4 A IF -C T R L .B 5 1 6 B it A IF -C T R L .B 6 A IF -C T R L .B 7 A IF -C T R L .B 1 2 A IF -C T R L .B 1 3 A IF -C T R L .
Process data transfer 7 Lenze device control Process data signals for 9300 Servo PLC and Drive PLC 7.1.
7 Process data transfer Lenze device control Process data signals for 9300 Servo PLC and Drive PLC Outputs_AIF2 Outputs_AIF1 AIF2_nOutW1_a Byte 1 AIF1_wDctrlStat ... 16 Bit AIF2_bFDO15_b Byte 2 AIF2_nOutW2_a Byte 3 AIF1_nOutW1_a 16 binary signals 16 Bit Byte 2 ...
Process data transfer 7 Lenze device control Process data signals for 9300 Servo PLC and Drive PLC Process data telegram to the drive Name / variable name Meaning AIF1_wDctrlCtrl Device control word AIF1_nInW1_a AIF word 1 AIF1_nInW2_a AIF word 2 AIF1_nInW3_a AIF word 3 AIF2_nInW1_a AIF word 4 AIF2_nInW2_a AIF word 5 AIF2_nInW3_a AIF word 6 AIF2_nInW4_a AIF word 7 AIF3_nInW1_a AIF word 8 AIF3_nInW2_a AIF word 9 AIF3_nInW3_a AIF word 10 AIF3_nInW4_a AIF word 11 AIF1_dnInD1_p AIF
7 Process data transfer Lenze device control Process data signals for 9300 Servo PLC and Drive PLC Inputs_AIF2 AIF1_wDctrlCtrl 16 Bit AIF1_bCtrlB0_b Byte 1 AIF1_bCtrlB1_b 16 Bit AIF1_bCtrlB2_b AIF2_nInW1_a AIF2_bInB0_b AIF1_bCtrlQuickstop_b Byte 2 AIF1_bCtrlB4_b 16 binary signals ...
Process data transfer 7 Lenze device control Process data signals for axis modules ECSxS / ECSxA 7.1.6 Process data signals for axis modules ECSxS / ECSxA , Detailed information .... on the process data transfer for the ECS servo system and the required system blocks and settings can be found in the documentation of the following devices: ƒ ECSxS axis module (speed and torque) ƒ ECSxA axis module (application) EDSMF2133IB EN 5.
7 Process data transfer DRIVECOM control Provide DRIVECOM compatibility 7.2 DRIVECOM control ) Note! ECS servo system ECS devices cannot be used with the DRIVECOM or PROFIdrive control. 7.2.1 Provide DRIVECOM compatibility Drivecom Profile 20 is a non−proprietary definition of important parameters and the controller behaviour. Apart from DRIVECOM definitions, there are other Lenze specific functionalities which must be adapted to achieve full compatibility to the DRIVECOM Profile.
Process data transfer 7 DRIVECOM control DRIVECOM state machine 7.2.2 DRIVECOM state machine For the PROFIBUS control and the use of the EMF2133IB communication module the Lenze controllers feature the standardised device states in accordance with the "Drive technology 20" DRIVECOM profile.
7 Process data transfer DRIVECOM control DRIVECOM state machine 82XX, 8200 vector (C0001 Ø3) For standard device control you enter the control information via the corresponding control inputs (terminal): Information on the current device status (see Fig. 7−11, marked by rectangles) is stored in the DRIVECOM parameter "status word". Commands in the DRIVECOM parameter "control word are switched off and cannot change the device status.
Process data transfer 7 DRIVECOM control DRIVECOM control word 7.2.
7 Process data transfer DRIVECOM control DRIVECOM control word 72 Bit Name Meaning 15 Manufacturer 820X Process input data inhibit: Inhibit update of the process output data of the controller (input data for the master). The updating of status and actual information of the process data channel can be inhibited in order to transmit control information more precisely in time.
Process data transfer 7 DRIVECOM control DRIVECOM status word 7.2.
7 Process data transfer DRIVECOM control DRIVECOM status word 74 Bit Name Description 15 Manufacturer 82xx / 821x / 822x Qmin (fd < dQmin ) 0 = Qmin not active 1 = Qmin active 8200 vector / 93XX Mapping to bit C0150.B5 l EDSMF2133IB EN 5.
Process data transfer 7 DRIVECOM control Bit control commands 7.2.5 Bit control commands The bit control commands of the control word depend on other bit settings.
7 Process data transfer DRIVECOM control Status bits 7.2.6 Status bits The current device status is clearly coded in bits 0 ...
Process data transfer 7 PROFIdrive control Establishing PROFIdrive compatibility 7.3 PROFIdrive control ) Note! ECS servo system ECS devices cannot be used with the DRIVECOM or PROFIdrive control. 7.3.1 Establishing PROFIdrive compatibility The PROFIdrive profile, version 2, is a non−proprietary definition of important parameters and the controller behaviour.
7 Process data transfer PROFIdrive control PROFIdrive state machine 7.3.2 PROFIdrive state machine Example: Status information by parameter "status word" bit 15 ...
Process data transfer 7 PROFIdrive control PROFIdrive control word 7.3.
7 Process data transfer PROFIdrive control PROFIdrive control word 80 Bit Name Meaning 15 Manufacturer 820X Process input data inhibit Inhibit update of the process output data of the controller (input data for the master). The updating of status and actual information of the process data channel can be inhibited in order to transmit control information more precisely in time.
Process data transfer 7 PROFIdrive control PROFIdrive status word 7.3.
8 Parameter data transfer 8 Parameter data transfer PROFIBUS transmits parameter data and process data between the host (master) and the drives connected to the bus (slaves). The data is transmitted via corresponding communication channels depending on their time−critical behaviour. 82 ƒ Parameter data are transferred via the parameter data channel.
Parameter data transfer 8 Lenze parameter sets Parameter sets for 82XX controllers 8.1 Lenze parameter sets ( Stop! 82XX / 8200 vector / Drive PLC and communication module: ƒ The cyclic writing of parameter data into the EEPROM is not permissible. It may damage or destroy the EEPROM. Only 8200 vector: ƒ After every mains switching, set code C0003 to the value "0" if you want to change the parameter data cyclically. 8.1.
8 Parameter data transfer Lenze parameter sets Parameter sets for 8200 vector controller 8.1.2 Parameter sets for 8200 vector controller The 8200 vector controller has four parameter sets the parameters of which can be directly addressed via the bus. Addressing Addressing is carried out with a code offset: ƒ Offset "0" addresses parameter set 1 with codes C0000 ... C1999. ƒ Offset "2000" addresses parameter set 2 with codes C2000 ... C3999.
Parameter data transfer 8 Lenze parameter sets Parameter sets for controller 93XX 8.1.3 Parameter sets for controller 93XX The drive controllers 93XX feature up to four parameter sets for storage in the EEPROM for each technology variant. An additional parameter set is located in the main memory of the drive controller. This parameter set is referred to as "current" parameter set. Addressing ƒ Only the current parameter set can be directly addressed via the bus.
8 Parameter data transfer Lenze parameter sets Parameter sets for Drive PLC and ECSxS / ECSxA axis modules 8.1.4 Parameter sets for Drive PLC and ECSxS / ECSxA axis modules The Drive PLC and ECSxS / ECSxA axis modules each have a parameter set for storage in the EEPROM. Another parameter set is stored in the main memory. This parameter set is called "current" parameter set. Addressing l l Only the current parameter set can be directly addressed via the bus.
Parameter data transfer 8 DRIVECOM parameter data channel Addressing of the parameter data 8.2 DRIVECOM parameter data channel The DRIVECOM parameter data channel ... 8.2.1 ƒ enables parameter setting and diagnostics of the controller. ƒ allows access to all Lenze parameters (codes). ƒ additionally occupies 4 words of the input and output data words in the master. ƒ has an identical structure for both directions of transmission.
8 Parameter data transfer DRIVECOM parameter data channel Telegram structure Byte 1: Service, request and response control for the parameter data channel Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Byte 8 Service Subindex Index High byte Index Low byte Data 4 / Error 4 Data 3 / Error 3 Data 2 / Error 2 Data 1 / Error 1 7 6 5 4 2 1 0 3 2 1 0 Arrangement of bits 0 ... 7 in byte 1 Request Request to the controller. The bits are set only by the master.
Parameter data transfer 8 DRIVECOM parameter data channel Telegram structure Byte 2: Subindex Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Byte 8 Service Subindex Index High byte Index Low byte Data 4 / Error 4 Data 3 / Error 3 Data 2 / Error 2 Data 1 / Error 1 ƒ The 82XX series do not have codes with subindex, the value is always 0.
8 Parameter data transfer DRIVECOM parameter data channel Telegram structure Bytes 5 ... 8: Parameter value (data) / error information (error) Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Byte 8 Service Subindex Index High byte Index Low byte Data 4 / Error 4 Data 3 / Error 3 Data 2 / Error 2 Data 1 / Error 1 The status of the (status) bit 7 in byte 1 (job) determines the meaning of this data field: Meaning of the bytes 5 ... 8 if ... Bit 7 = 0 Bit 7 = 1 Parameter value (data 1 ...
Parameter data transfer 8 DRIVECOM parameter data channel Error codes (DRIVECOM) 8.2.
8 Parameter data transfer DRIVECOM parameter data channel Reading parameters 8.2.5 Reading parameters General procedure 1. Define the user data range of the controller. (Where are the user data located in the host system?) Observe manufacturer−specific information. 2. Enter the address of the required parameter into the "Index" and "Subindex" fields (DP output data). 3. Request in the service byte = read request The status of the handshake bit in the service byte must be changed (DP output data). 4.
Parameter data transfer 8 DRIVECOM parameter data channel Reading parameters Result: ƒ Request telegram from master to drive: Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Byte 8 Service Subindex Index Index Data 4 Data 3 Data 2 Data 1 (High byte) (Low byte) 01hex 00hex 5Fhex C2hex 00hex 00hex 00hex 00hex 00000001bin 00000000bin 01011111bin 11000010bin 00000000bin 00000000bin 00000000bin 00000000bin Waiting for change of handshake bit in the response (bit 6 here: 0 à
8 Parameter data transfer DRIVECOM parameter data channel Writing parameters 8.2.6 Writing parameters General procedure 1. Define the user data range of the controller. (Where are the user data located in the host system?) Observe manufacturer−specific information. 2. Enter the address of the required parameter into the "Index" and "Subindex" fields (DP output data). 3. Enter the parameter value into the "Data/Error" field. 4.
Parameter data transfer 8 DRIVECOM parameter data channel Writing parameters Result: ƒ Request telegram from master to drive: Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Byte 8 Service Subindex Index Index Data 4 Data 3 Data 2 Data 1 (High byte) (Low byte) 72hex 00hex 5Fhex F3hex 00hex 03hex 0Dhex 40hex 01110010bin 00000000bin 01011111bin 11110011bin 00000000bin 00000011bin 00001101bin 01000000bin Waiting for change of handshake bit (bit 6 here: 0 à 1) ƒ Response
8 Parameter data transfer PROFIdrive parameter data channel 8.3 PROFIdrive parameter data channel Data communication with PROFIBUS−DP−V0 is characterised by cyclic diagnostics and cyclic process data and parameter data transfer. An optional service extension is the acyclic parameter data transfer of PROFIBUS−DP−V1. This service does not impair the functionality of the standard services under PROFIBUS−DP−V0. PROFIBUS−DP−V0 and PROFIBUS−DP−V1 can be operated simultaneously in the same network.
Parameter data transfer 8 PROFIdrive parameter data channel PROFIdrive DP−V1 8.3.1 PROFIdrive DP−V1 Features 8.3.1.1 ƒ Parameter number and subindex addresses with a width of 16 bits each. ƒ Several parameter requests can be combined to one request (multi−parameter requests). ƒ Processing of one parameter request at a time (no pipelining). ƒ A parameter request or a parameter response must fit into one data block (max. 240 bytes). Requests/responses cannot be split over several data blocks.
8 Parameter data transfer PROFIdrive parameter data channel PROFIdrive DP−V1 8.3.1.2 Acyclic data transfer ) Note! A parameter request refers to one or several parameter(s) (multi−parameter request). Master Parameter request DP−V1 Write.req Slave Parameter request with data (parameter request) Write.res without data Read.req without data Parameter processing Read.res(−) without data Read.req without data Parameter response Read.
Parameter data transfer 8 PROFIdrive parameter data channel PROFIdrive DP−V1 8.3.1.3 Telegram structure SD LE LEr SD DA SA FC DSAP SSAP DU FCS ED E82ZAFP015 Fig. 8−2 PROFIBUS data telegram with DP−V1 The data unit (DU) contains the DP−V1 header and the parameter request or the parameter response. In the following subchapters, the parameter request and the parameter response are described in detail.
8 Parameter data transfer PROFIdrive parameter data channel PROFIdrive DP−V1 8.3.1.4 Reading parameters ) Note! ƒ When a read request is processed, no parameter value is written to the slave. ƒ A response to a read request does not contain the parameter attribute, index and subindex. ƒ When a multi−parameter read request is transferred, the parameter attribute, index and subindex are repeated according to the number "n" of the parameters requested.
Parameter data transfer 8 PROFIdrive parameter data channel PROFIdrive DP−V1 8.3.1.5 Response to a correctly executed read request ) Note! ƒ When a read request is processed, no parameter value is written to the slave. ƒ A response to a read request does not contain the parameter attribute, index and subindex. ƒ When a multi−parameter read request is transferred, the parameter format and parameter value are repeated according to the number "n" of parameters requested.
8 Parameter data transfer PROFIdrive parameter data channel PROFIdrive DP−V1 Parameter value Depending on the data type, the user data are assigned as follows: Assignment of the user data Data type Length String x bytes U8 1 byte Byte 7 Byte 8 Byte ... Low byte 2 bytes High word High byte U32 Byte 10 00 High byte U16 Byte 9 Low word Low byte High byte Low byte 4 bytes (This representation applies to one parameter value.) 102 l EDSMF2133IB EN 5.
Parameter data transfer 8 PROFIdrive parameter data channel PROFIdrive DP−V1 8.3.1.6 Response to a read request error Response header Byte 1 Byte 2 U8 Request reference (mirrored) Byte 3 U8 Response identification Byte 4 U8 Axis (mirrored) U8 Number of indexes Request reference: Mirrored value of parameter request Response identification: 0x81 (read error) An error code is transmitted (see below).
8 Parameter data transfer PROFIdrive parameter data channel PROFIdrive DP−V1 8.3.1.7 Writing parameters ) Note! ƒ When a multi−parameter write request is processed, the ... – parameter attribute – index and subindex and then the – parameter format and – parameter value are repeated according to the number "n" of parameters requested. ƒ A write request must not exceed the maximum data length of 240 bytes.
Parameter data transfer 8 PROFIdrive parameter data channel PROFIdrive DP−V1 Parameter format Byte 11 Byte 12 U8 Format U8 Number of values Format: 0x01 ... 0x36, data types 0x41, byte 0x42, word 0x43, double word Number of values: 0x01 or number of subindexes requested l If there is more than one subindex, only the parameter value is repeated.
8 Parameter data transfer PROFIdrive parameter data channel PROFIdrive DP−V1 8.3.1.9 Response to a write request error ) Note! For a multi−parameter request, the correct and possibly faulty messages are combined in one telegram.
Parameter data transfer 8 PROFIdrive parameter data channel PROFIdrive DP−V1 8.3.1.10 Programming of read requests Procedure 1. Define the user data range of the controller (define the location of the user data in the host system). Observe manufacturer−specific data. 2. Enter the code of the desired parameter into the "code" field (output data). 3. Job identification / service = read request 4.
8 Parameter data transfer PROFIdrive parameter data channel PROFIdrive DP−V1 8.3.1.11 Programming of write requests Procedure 1. Define the user data range of the controller (define the location of the user data in the host system). Observe manufacturer−specific data. 2. Enter the code of the desired parameter into the "code" field (output data). 3. Enter parameter value into the "Data/Error" field. 4. Job identification / service = write request 5.
Parameter data transfer 8 PROFIdrive parameter data channel Error codes (PROFIdrive) 8.3.
8 Parameter data transfer Consistent parameter data 8.4 Consistent parameter data In the PROFIBUS communication system, data are permanently exchanged between the host (CPU + PROFIBUS master) and the standard device via the plugged−on slave interface module. Both the PROFIBUS master and the CPU (central processing unit) of the host access a joint memory − the dual port memory (DPM).
Parameter data transfer 8 Consistent parameter data Configuring consistent data Consistency is achieved by an appropriate PROFIBUS master configuration. Please refer to the corresponding documentation for your configuring software for this purpose. I Tip! Consistency configuration depends on the PROFIBUS master configuring software.
9 Diagnostics LED status displays 9 Diagnostics 9.1 LED status displays 01 EMF2133IB 5 7 2131 64 32 16 8 4 2 1 PROFIBUS DP 4 6 Adresse 3 L 2 ON 1 2 3 4 5 6 7 8 OFF 24V DC + _ 2133 2133PFB003 Pos. Colour Status Description 0 green on The communication module is supplied with voltage and has a connection to the drive controller. off The communication module is not supplied with voltage. The controller or the external voltage supply is switched off.
Diagnostics 9 Troubleshooting and fault elimination Controller is inhibited 9.2 Troubleshooting and fault elimination 9.2.1 Controller is inhibited The controller cannot be enabled via PROFIBUS process data, i. e. the status "OPERATION ENABLED" is not reached.
9 Diagnostics Troubleshooting and fault elimination Controller is inhibited 1 Select POW1 = 007Ehex No PIW1 = xxxx xxxx x011 0001bin (ready to switch on)? Yes Select POW1 = 007Fhex PIW1 = xxxx xxxx x011 0111bin (operation enabled)? No Enable controller (terminal 28, C40) For 821X/8200 vector/822X setpoint selection with C0106 <> 0 via POW2 Yes OK 114 Setpoints or other control signals can be selected l EDSMF2133IB EN 5.
Diagnostics 9 Troubleshooting and fault elimination Checking PROFIBUS 9.2.2 Checking PROFIBUS Short check of the PROFIBUS system in the case of faulty initialisation: ƒ Take into account the diagnostics information of the PROFIBUS communication module in the host. ƒ It might be useful for troubleshooting to reduce the bus to such an extent that only one device remains connected to the PROFIBUS.
9 Diagnostics Troubleshooting and fault elimination Activation of communication module 9.2.
Diagnostics 9 Troubleshooting and fault elimination Reset fault (TRIP) 9.2.4 Reset fault (TRIP) Fault reset via PROFIBUS process data: Select POW1 = 0080hex PIW1 = xxxx xxxx x100 0000bin (switch−on inhibit)? Yes No Selection: POW1 = 0000hex then POW1 = 0080hex No PIW1 = xxxx xxxx x100 0000bin (switch−on inhibit)? Yes OK EDSMF2133IB EN 5.
9 Diagnostics Monitoring with interrupted PROFIBUS communication Permanent interruption of communication 9.3 Monitoring with interrupted PROFIBUS communication 9.3.1 Permanent interruption of communication If the PROFIBUS communication is interrupted permanently, e.g. by cable breakage or failure of the PROFIBUS master, no process data are transmitted to the slave in the "Data_Exchange" (DATA_EXCH) state.
Diagnostics 9 Monitoring with interrupted PROFIBUS communication Short−time interruption of communication 9.3.2 Short−time interruption of communication POWER ON Set_Slave_Add Slave_Diag WAIT_PRM Slave_Diag Get_Cfg WAIT_CFG Slave_Diag Set_Prm Get_Cfg Chk_Cfg, o.k. Chk_Cfg, not o.k. Set_Prm, not o.k. DATA_EXCH 2133PFB006 The master detects the communication fault and only after a few microseconds transfers the slave to the "WAIT_PRM" state of the DP state machine (see above).
10 Codes Overview 10 Codes 10.1 Overview 120 Code Subcode Index Designation See C0126 − 24449d = 5F81h Behaviour with regard to communication errors ^ 122 C1812 − 22763d = 58EBh Software ID ^ 124 C1813 − 22762d = 58EAh Software creation date ^ 124 C1882 − 22693d = 58A5h Monitoring response for PCD communication fault ^ 122 C1883 − 22692d = 58A4h Response time to exiting "Data_Exchange" ^ 123 l EDSMF2133IB EN 5.
Codes 10 Overview How to read the code table Column Code Meaning Subcode (Lenze) code The parameters of a configurable code marked with an asterisk (*) can only be accessed via the communication module. l The value of a configurable code marked with a double asterisk (**) is not transmitted with the parameter set transfer. Subcode Name Designation of the Lenze code Index Lenze Index under which the parameter is addressed. l Values Access Data type EDSMF2133IB EN 5.
10 Codes Monitoring codes 10.2 Monitoring codes C0126: Behaviour with communication error (extract) Code Subcode Index C0126 − 24449d = 5F81h Possible settings Lenze Data type Selection See documentation for the controller. FIX32 Monitoring the internal communication between communication module and controller.
Codes 10 Monitoring codes C1883: Response time to exiting "Data_Exchange" Possible settings Code C1883 Subcode − Index 22692d = 58A4h Lenze Selection 65535 0 [1 ms] Data type 65535 FIX32 A value of 65535 deactivates monitoring. A change in the monitoring time becomes effective immediately. Monitoring starts with the arrival of the first telegram. I Tip! Observe the notes with regard to interruptions of the PROFIBUS communication (¶ 118) EDSMF2133IB EN 5.
10 Codes Diagnostics codes 10.3 Diagnostics codes C1812: Display of software identification code Possible settings Code C1812 Subcode 1 ... 4 Index 22763d = 58EBh Lenze Selection g − Data type U32 Display of software identification code (ID) in 4 subcodes with 4 characters each. C1813: Display of software creation date Possible settings Code C1813 Subcode 1 ...
Indextabelle 11 DRIVECOM profile parameter 11 Index table 11.1 DRIVECOM profile parameter I−6004hex: Process data monitoring selection code The parameter determines the controller reaction when the process data monitoring time has expired. Possible settings Index [hex] I−6004 EDSMF2133IB EN 5.
12 Appendix Parallel operation of AIF and FIF interfaces 12 Appendix 12.1 Parallel operation of AIF and FIF interfaces ) Note! The option of parallel operation ... ƒ of a communication module (AIF) and a function module (FIF) exists for the standard devices 8200 vector and Drive PLC. ƒ of two function modules (FIF) exists for the standard devices 8200 motec, Drive PLC and starttec. Notes on parallel operation Attach/detach the communication module to/from the AIF interface.
Appendix 12 Parallel operation of AIF and FIF interfaces Possible combinations Function module on FIF (Design: Standard or PT) Communication module on AIF Keypad E82ZBC 1) Keypad XT EMZ9371BC 1) üü PROFIBUS−DP 2131/2133 üü Standard I/O E82ZAFS Application I/O E82ZAFA üü ü INTERBUS E82ZAFI üü x PROFIBUS−DP E82ZAFP üü X LECOM−B (RS485) E82ZAFL üü X System bus (CAN) System bus I/O RS System bus I/O E82ZAFC E82ZAFC100 E82ZAFC200 üü üü CANopen / DeviceNet 2) E82ZAFD üü X ASI E82Z
12 Appendix Accessories 12.2 Accessories In the following, you will find the accessory components for PROFIBUS: ) Note! Please ask the manufacturer of the components for the latest order information and the technical data. 128 Designation Note Bus connector Bus connector for 9−pole Sub−D plug with plug−in terminals for connecting the bus cable (order designation: Bus connector PROFIBUS RS485). l Contains connectable bus terminating resistor.
Index 13 13 Index 0 ...
13 Index DRIVECOM − bit control commands, 75 − control word, 71 − error codes, 91 − Parameter data channel, 87 − Provide DRIVECOM compatibility, 68 − state machine, 69 − status bits, 76 − status word, 73 L LED status displays, 112 Lenze codes, 120 − C0126, − C1812, − C1813, − C1882, − C1883, 122 124 124 122 123 DRIVECOM control, 68 Lenze parameter sets, 83 DRIVECOM profile parameter, 125 Lenze parameters E − DRIVECOM, 87 − PROFIdrive, 96 Electrical installation, 23 M Electrical isolation, 24 M
Index Parameter sets, 83 Protection against restart, 44 − 8200 vector, 84 − 82XX, 83 − 93XX, 85 − Drive PLC, 86 − ECSxS / ECSxA axis modules, 86 Protection of persons, 11 PNO ID number, 16 Preparing the standard device for communication, 38 Process data, monitoring selection code, 125 13 Protective insulation, 17 Provide compatibility, DRIVECOM, 68 R Reading parameters − PROFIdrive (DP−V0), 92 − PROFIdrive (DP−V1), 100 Process data monitoring response, C1882, 122 Repeaters, 25 Process data monito
13 Index T V Technical data, 16 Validity of the documentation, 5 Voltage supply, 28 − internal, 28 Voltage supply: external, 29 Telegram structure, DRIVECOM, 87 Telegram structure (DP−V1), 99 Transmission cable, specification, 25 Troubleshooting, 113 Type code, 13 − finding, 13 132 W Wiring according to EMC, 23 Wiring with a host (master), 24 Writing parameters − PROFIdrive (DP−V0), 94 − PROFIdrive (DP−V1), 104 l EDSMF2133IB EN 5.
Index EDSMF2133IB EN 5.
Q © 09/2011 F Lenze Automation GmbH Hans−Lenze−Str. 1 D−31855 Aerzen Germany Service Lenze Service GmbH Breslauer Straße 3 D−32699 Extertal Germany ( Ê ü +49 (0)51 54 / 82−0 ( Ê 00 80 00 / 24 4 68 77 (24 h helpline) +49 (0)51 54 / 82 − 28 00 Lenze@Lenze.de +49 (0)51 54 / 82−11 12 Service@Lenze.de www.Lenze.com EDSMF2133IB § .G÷h § EN § 5.
