EasyManua.ls Logo

Lenze 9300 Servo PLC User Manual

Lenze 9300 Servo PLC
175 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
Page #1 background imageLoading...
Page #1 background image
L
Global Drive
9300 Servo PLC
Manual
Show/Hide Bookmarks

Table of Contents

Question and Answer IconNeed help?

Do you have a question about the Lenze 9300 Servo PLC and is the answer not in the manual?

Lenze 9300 Servo PLC Specifications

General IconGeneral
BrandLenze
Model9300 Servo PLC
CategoryDC Drives
LanguageEnglish

Summary

1 Preface and general information

1.1 About this Manual

Describes the purpose and scope of the manual for the 9300 Servo PLC.

1.1.1 Conventions in this manual

Explains text and pictogram conventions used for clarity.

1.1.2 Pictograms in this manual

Details the meaning of pictograms used for warnings and notes.

1.1.3 Terminology used

Defines key terms like FB, SB, and parameter codes.

1.1.4 What’s new?

Highlights revisions in the current edition of the manual.

1.2 Lenze software guidelines for variable names

Outlines Lenze's Hungarian Notation for consistent variable naming.

1.2.1 Hungarian Notation

Details conventions for creating variable names with prefixes and data types.

1.2.1.1 Recommendation for designating variable types

Provides guidelines for prefixing variable names with type indicators.

1.2.1.2 Designation of the signal type in the variable name

Explains variable name endings (_a, _b, _v, _p) for signal types.

1.2.1.3 Special handling of system variables

Describes naming conventions for system blocks and variables.

2 System blocks

2.1 Introduction

Introduces system blocks (SBs) as quasi-hardware function blocks within the PLC.

2.1.1 Access through absolute addresses

Explains accessing SB inputs/outputs using IEC1131-3 absolute addressing (%IXa.b.c, %QXa.b.c).

2.1.2 Module numbers

Lists module numbers assigned to each system block in the 9300 Servo PLC.

2.1.3 Definition of the system-block inputs/outputs

Describes how SBs connect to program-organization elements (POEs).

2.2 Automation interface (AIF1_IO_AutomationInterface)

Details the AIF1 SB for input signals from fieldbus modules.

2.2.1 Inputs_AIF1 (AIF1_IN)

Describes the inputs of the AIF1 SB for setpoint/actual values.

2.2.2 Outputs_AIF1 (AIF1_OUT)

Describes the outputs of the AIF1 SB for setpoint/actual values.

2.3 Automation interface (AIF2_IO_AutomationInterface)

Details the AIF2 SB for input signals from fieldbus modules.

2.3.1 Inputs_AIF2 (AIF2_IN)

Describes the inputs of the AIF2 SB for setpoint/actual values.

2.3.2 Outputs_AIF2 (AIF2_OUT)

Describes the outputs of the AIF2 SB for setpoint/actual values.

2.4 Automation interface (AIF3_IO_AutomationInterface)

Details the AIF3 SB for input signals from fieldbus modules.

2.4.1 Inputs_AIF3 (AIF3_IN)

Describes the inputs of the AIF3 SB for setpoint/actual values.

2.4.2 Outputs_AIF3 (AIF3_OUT)

Describes the outputs of the AIF3 SB for setpoint/actual values.

2.5 AIF_IO_Management

Used for control and monitoring of special AIF-modules (fieldbus modules).

2.6 Analog inputs/outputs 1 (ANALOG1_IO)

Interface for analog signals via terminal X6/1-2.

2.6.1 Inputs_ANALOG1 (AIN1)

Describes analog input 1 for setpoints and parameter control.

2.6.2 Outputs_ANALOG1 (AOUT1)

Describes analog output 1 used as a monitor output.

2.7 Analog inputs/outputs 2 (ANALOG2_IO)

Interface for analog signals via terminal X6/3-4.

2.7.1 Inputs_ANALOG2 (AIN2)

Describes analog input 2 for setpoints and parameter control.

2.7.2 Outputs_ANALOG2 (AOUT2)

Describes analog output 2 used as a monitor output.

2.8 Drive control (DCTRL_DriveControl)

Operates the drive controller in specific states like TRIP, QSP.

2.8.1 Quickstop (QSP)

Describes the function to brake the drive to standstill.

2.8.2 Operation disabled (DISABLE)

Disables starting the drive and resets controllers.

2.8.3 Controller inhibit “ControllerInhibit” (CINH)

Disables power output stages and resets controllers.

2.8.4 TRIP-SET

Sets the drive to a specific state and signals "ExternalFault".

2.8.5 TRIP-RESET

Resets an active TRIP if the fault cause is removed.

2.8.6 DCTRL_wFaultNumber

Reads an existing fault using a system variable, C0168.

2.8.7 DCTRL_bExternalFault_b

Manages the external fault state, changing to TRUE when TRIP-Set is triggered.

2.8.8 Controller state

Defines binary-coded states of the controller using system variables.

2.8.9 Output of digital status signals

Defines signals output at DCTRL_wStat as a status word.

2.8.10 Control word and status word

Explains assignment of control/status words to AIF1_IO/CAN1_IO.

2.9 Digital master frequency input (DF_IN_DigitalFrequency)

Converts pulse current to speed/phase-angle setpoint.

2.9.1 Digital frequency input X9

Details the digital frequency input X9 for TTL level signals.

2.9.2 Technical data for the connection of X9 and X10

Provides technical specifications for connecting X9 and X10.

2.9.3 Touch-Probe (TP)

Describes the Touch-Probe function for interval tasks.

2.10 Digital frequency output (DF_OUT_DigitalFrequency)

Converts internal speed signals to frequency signals for output.

2.10.1 Output signals on X10

Explains output signals on X10, simulating an incremental encoder.

2.10.2 Output of an analog signal

Describes outputting analog signals [%] as frequency signals at X10.

2.10.3 Output of a speed signal

Describes outputting speed (rpm) signals [%] as frequency signals at X10.

2.10.4 Encoder simulation of the resolver with zero track in resolver zero position

Details encoder simulation for resolvers connected to X7.

2.10.5 Direct output of X8

Describes using X8 as input for encoders, outputting directly to X10.

2.10.6 Direct output of X9

Describes using X9 as digital frequency input, outputting directly to X10.

2.10.7 Technical data for the connection of X9 and X10

Provides technical specifications for connecting X9 and X10.

2.11 Digital inputs/outputs (DIGITAL_IO)

Reads digital signals at terminals X5/E1...X5/E5 and conditions them.

2.11.1 Inputs_DIGITAL (DIGIN)

Describes the digital inputs of the DIGITAL_IO SB.

2.11.2 Outputs_DIGITAL (DIGOUT)

Describes the digital outputs of the DIGITAL_IO SB at terminals X5/A1...X5/A4.

2.12 Free Codes (FCODE_FreeCodes)

Assigns code values directly to variables via a fixed scaling routine.

2.13 Internal motor control (MCTRL_MotorControl)

Contains control functions for the drive, including phase-angle, speed, and motor control.

2.13.1 Current controller

Details adapting the current controller using parameters C0075 and C0076.

2.13.2 Additional torque setpoint

Explains using MCTRL_nMAdd_a as a torque or additional torque setpoint.

2.13.3 Torque limiting

Allows setting external torque limits via MCTRL_nLoMLim_a and MCTRL_nHiMLim_a.

2.13.4 Speed controller

Describes the speed controller as an ideal PID controller.

2.13.5 Torque control with speed restriction

Activates speed restriction using a second speed controller when MCTRL_bNMSwt_b is TRUE.

2.13.6 Speed-setpoint restriction

Restricts speed setpoint in MCTRL_nNSet_a to ±100% of nmax.

2.13.7 Phase-angle controller

Required for phase synchronization and drift-free standstill.

2.13.8 Quickstop QSP

Stops the drive independently of setpoint input within a set time.

2.13.9 Field weakening

Describes automatic or manual field weakening for motor operation.

2.13.10 Chopping frequency changeover

Allows selection of chopping frequency for the inverter (8 or 16 kHz).

2.13.11 Touch-Probe (TP)

Describes the Touch-Probe function for internal motor control.

2.13.12 System marker MCTRL_nNmaxC11

Shows the max. speed set under C0011 as a reference value.

2.13.13 Monitoring

Protects the drive from impermissible operating conditions.

2.13.13.1 Undervoltage (LU)

Monitors the DC-bus voltage and protects the drive.

2.13.13.2 Overvoltage (OU)

Monitors the DC-bus voltage and protects the drive.

2.13.13.3 EarthFault (monitoring for earth fault OC2)

Protects the drive controller from earth faults.

2.13.13.4 ShortCircuit (monitoring for a short-circuit OC1)

Protects the drive controller from short-circuits.

2.13.13.5 TMot>SetValue (motor-temperature monitoring OH3 - fixed)

Protects the motor from overheating with a fixed threshold.

2.13.13.6 TMot>C0121 (motor-temperature monitoring OH7 - adjustable)

Monitors motor temperature with an adjustable threshold.

2.13.13.7 PTCOverTemp (motor-temperature monitoring OH8)

Protects the motor from overheating via PTC signal.

2.13.13.8 Overcurrent diagram for fault signal OC5

Illustrates permitted overcurrent over time.

2.13.13.9 Resolver monitoring for wire breakage Sd2

Monitors cable and resolver for wire breakage.

2.13.13.10 Heatsink monitoring OH4 (adjustable)

Monitors heatsink temperature with an adjustable threshold.

2.13.13.11 Heatsink monitoring OH (fixed)

Monitors heatsink temperature with a fixed threshold.

2.13.13.12 Plant speed monitoring NMax

Monitors plant speed against a maximum limit.

2.14 Statebus (STATEBUS_IO)

Steers controllers to specified states (TRIP, QSP, inhibit) via a device-specific bus.

2.15 System markers (SYSTEM_FLAGS)

Global variables for programming facilitation, including clocks and task info.

3 Networking

3.1 System bus (CAN) in the Lenze drive system

Describes the CAN system bus for drive networking.

3.1.1 Contact assignment

Details terminal assignments for CAN bus communication on controllers and vectors.

3.1.2 Wiring of the system bus

Provides recommendations for system bus cable specifications and basic network structure.

3.1.2.1 System bus wiring complying to EMC

Outlines EMC compliance guidelines for system bus wiring.

3.1.3 Technical data

Covers technical specifications like baud rates, bus lengths, and communication times.

3.1.3.1 General data of the system bus network

Specifies communication media and baud rates for the system bus.

3.1.3.2 Feasible bus length

Lists possible bus lengths based on data transmission speed.

3.1.3.3 Communication times

Explains factors affecting communication times and provides telegram throughput times.

3.1.4 Commissioning

Details steps for commissioning the system bus, including settings.

3.1.5 Programming

Explains the programming capabilities offered by the integrated system bus.

3.1.5.1 General

Highlights features like parameter entries and data exchange between controllers.

3.1.5.2 Parameter channels

Describes using parameter channels for setting parameters via HMI or PC.

3.1.5.3 Process data channels

Explains process data channels for high-speed data exchange.

3.2 System blocks for the system bus

Details system blocks used for CAN communication.

3.2.1 System bus (CAN1_IO)

Describes the CAN1_IO SB for cyclic data communication.

3.2.1.1 Inputs_CAN1 (CAN1_IN)

Details the inputs of the CAN1_IN SB for higher-level control systems.

3.2.1.2 Outputs_CAN1 (CAN1_OUT)

Details the outputs of the CAN1_OUT SB for higher-level control systems.

3.2.2 System bus (CAN2_IO)

Describes the CAN2_IO SB for data exchange between controllers.

3.2.2.1 Inputs_CAN2 (CAN2_IN)

Details inputs for data exchange between controllers and terminals.

3.2.2.2 Outputs_CAN2 (CAN2_OUT)

Details outputs for data exchange between controllers and terminals.

3.2.3 System bus (CAN3_IO)

Describes the CAN3_IO SB for data exchange between controllers.

3.2.3.1 Inputs_CAN3 (CAN3_IN)

Details inputs for data exchange between controllers and terminals.

3.2.3.2 Outputs_CAN3 (CAN3_OUT)

Details outputs for data exchange between controllers and terminals.

3.2.4 Systembus Management (CAN_Management)

Manages CAN bus settings, errors, and reset nodes.

3.3 Synchronization of control program cycles

Synchronizes control program cycles with a higher-level control.

3.3.1 CAN_Synchronization

Details CAN synchronization via sync telegram or terminal signal.

3.4 Application example

Demonstrates setting up communication between drive controllers.

3.4.1 Programming the application example

Describes the programming steps for the application example.

3.4.2 Description of the codes for the system bus

Explains system bus codes for baud rate, master definition, and addressing.

3.4.2.1 Baud-rate setting C0351

Configures the baud rate for the system bus.

3.4.2.2 Defining a master in a drive group C0352

Sets a drive controller as master for initialization.

3.4.2.3 General address assignment C0350

Sets addressing for data objects and parameter channels.

3.4.2.5 Display code of the resulting identifier C0355

Displays identifiers calculated from basis identifier and address.

3.4.2.6 Boot-Up setting C0356/1

Adjusts times for data exchange and CAN output cycle times.

3.4.2.7 Diagnosis codes

Provides codes to observe events on the bus system.

3.4.2.8 Monitoring

Monitors telegram arrival within defined times and bus off states.

3.4.3 Communication profile of the system bus

Describes the CAL-based communication profile DS 301 (CANopen).

3.4.3.1 Data description

Explains identifier and user data structure in CAN telegrams.

3.4.3.2 Addressing the drives

Details how identifiers are derived from addresses for drive communication.

3.4.4 The communication phases of the CAN network

Explains the three states: Initialisation, Pre-Operational, Operational.

3.4.5 Parameterization

Explains parameterization using separate software channels and telegram structures.

3.4.5.1 Example: Write a parameter

Demonstrates writing a parameter value via parameter channel.

3.4.5.2 Example: Read a parameter

Demonstrates reading a parameter value via parameter channel.

3.4.6 Process data

Describes process-data objects (PDOs) for rapid data exchange.

3.4.6.1 Cyclical process-data objects

Details PDOs for rapid cyclical data communication.

4 Appendix

4.1 PLC functionality

Summarizes PLC capabilities, inputs, outputs, memory, and functions.

4.2 System POUs

Lists and describes System POUs and their features.

4.3 Monitoring

Explains monitoring functions for system interfaces, memory, and controller parts.

4.3.1 Reactions

Describes possible reactions (TRIP, Warning, OFF) to monitoring functions.

4.3.2 Possible settings for error messages

Overviews fault sources, meanings, and corresponding reactions.

4.4 Tripping (L_FWM)

Describes the function block for transmitting error messages to the PLC.

4.5 Troubleshooting

Guides on recognizing and analyzing faults using display elements and history buffer.

4.6 Fault analysis with the history buffer

Explains using the history buffer to trace faults and their occurrences.

4.6.1 Structure of the history buffer

Details the structure of the history buffer and its memory units.

4.6.2 Working with the history buffer

Provides instructions on how to read and reset fault messages from the history buffer.

4.7 Error messages

Lists error codes, their causes, and recommended remedies.

4.8 Reset of fault messages

Describes measures for re-commissioning after faults occur.

4.9 Code table

Explains how to read the code table and lists temporary codes.

4.10 Index

An alphabetical index of topics covered in the manual.

Related product manuals