UserDrivePeakCurrent

General

Type

EF

Devices supporting the parameter

Lexium LXM52 Drive, Lexium LXM52 Linear Drive,

Lexium LXM62 Drive, Lexium LXM62 Linear Drive,

Lexium ILM62 Drive Module,

Sercos Drive

Traceable

Yes

Functional Description

This parameter is used for the limitation of the drive peak current. If for this parameter, a value not equal 0 and less than the MaxDrivePeakCurrent read out from the drive is entered, then this value is used as DrivePeakCurrent during the phase up of the Sercos bus (phase 0 -> 4) and is used as the basis for limitations by UserCurrentLimit.

The magnetizing current is not limited with this parameter (more information see Current parameter). This allows for example, a servo amplifier Lexium 62 type 15 A to be replaced by a Lexium 62 type 27 A, if a replacement part is needed, and to continue to use the same current limits if the corresponding DrivePeakC of Lexium 62 type 15 A is entered as UserDrivePeakCurrent.

NOTE: A modified parameter value is transferred with a new Sercos phase up (phase 0 -> phase 4).

The following graphic shows the dependency with other object parameters for rotary drives:

G-SE-0061424.2.gif

 

 

The following graphic shows the dependency with other object parameters for linear drives:

G-SE-0061423.2.gif

 

 

Yellow parameters are input parameters, whose values are taken over by the Sercos phase up. Green parameters are input parameters, whose values are taken over immediately. Gray parameters are output parameters. Thick arrows show that a parameter makes an impact on another parameter immediately by the input. Thin arrows show that a parameter does not have an impact until the next Sercos phase up or when the dependent parameter is entered. The arrow indicates the effective direction of the dependency.

Example:

Entering J_Load has a direct impact on the parameter MaxAcc. A revision of MaxAcc only has an impact on ControllerStopDec if,

oa Sercos phase up takes place or

othe parameter ControllerStopDec is modified.