LoadControl Custom Task

A custom task run a load control simulation based on calculations contact or reaction forces. .

Introduction

This CustomTask tries to achieve the load requested from a provided user defined function by adjusting the velocity of a block of rigid material points. The control is done using a non-linear PID control algorithm.

Specifying the Force

A LoadControl custom task is based on a block of RigidBC or RigidContact particles. These particle are typically placed on the edge of the specimen. The following steps are used to setup all simulations with load control. First pick a direction as 1, 2, or 3 for x, y, or z direction. Load control is limited to be along grid axes. Next create rigid particles to apply the load:

1. Define a RigidBC to control velocity is the specified direction or define a RigidContact material type. Do not use any setting functions in the rigid material definition.
2. Place a block of those material points using that defined rigid material on the edge to be loaded.
3. Include displacement of the defined rigid material in the global archive using dispx, dispy, or dispz for the chosen direction.
4. When using RigidBC particles, include reaction force for the defined rigid material in the global archive using reactionx, reactiony, or reactionz for the chosen direction.
5. When using RigidContact particles, include contact force for the defined rigid material in the global archive using contactx, contacty, or contactz for the chosen direction.
6. Choose global archiving time to provide stable load control

Start the custom task and define following force defining parameters

CustomTask LoadControl
Parameter direction,(loaddir)
Parameter material,(matnum)
Parameter load,(loadfunction)

where

• (loaddir) is 1, 2, or 3 for x, y, or z direction loading.
• (matnum) is the defined rigid material by number
• (loadfunction is a user defined function that defines desired load (in force units) as a function of time (in alt time units)

Non-Linear PID Control

The control loop starts by estimating the error in current displacement using

      [math]\displaystyle{ e = \frac{F - L(t)}{A_t} }[/math]

where [math]\displaystyle{ F }[/math] is the rigid material force in the global archive, [math]\displaystyle{ L(t) }[/math] is the desired load from the Load parameter function, and [math]\displaystyle{ A_t }[/math] is the tangent stiffness for rigid material force (in force units) per unit displacement (in displacement units). If [math]\displaystyle{ A-t }[/math] is constant, the control is a linear PID. But for many simulations, such as those with plasticity, damage, or non-linear elasticity, [math]\displaystyle{ A_t }[/math] will evolve during the simulation leading to non-linear PID. The PID algorithim changes the rigid material points velocity in the control direction to

      [math]\displaystyle{ v = \frac{1}{t_g}\left(K_pe + \frac{K_i}{t_g}\int_0^t e\thinspace d\tau + K_dt_g\frac{de}{dt}\right) }[/math]

where [math]\displaystyle{ K_p }[/math], [math]\displaystyle{ K_i }[/math], and [math]\displaystyle{ K_d }[/math] are dimensionless gain factors for proportional (P), integral (I), and derivative (D) errors and [math]\displaystyle{ t_g }[/math] is the simulation's global archiving time.

Selecting PID Control Parameters

Load control depends on global archiving time [math]\displaystyle{ t_g }[/math], [math]\displaystyle{ A_t }[/math] (and how it evolves), [math]\displaystyle{ K_p }[/math], [math]\displaystyle{ K_i }[/math], and [math]\displaystyle{ K_d }[/math]. In addition, reaction and contact forces on rigid materials are typically noisy meaning that some of the control variables will require smoothing for stable control. All relevant parameters are set with the following commands:

Parameter velocity,(initvelocity)
Parameter startupTime,(inittime)
Parameter At,(initAt)
Parameter smoothF,(smoothF)
Parameter smoothA,(smoothA)
Parameter smoothErr,(smoothErr)
Parameter Kp,(Kp)
Parameter Ki,(Kp)
Parameter Kd,(Kp)

Methods to choose these parameters are in the following sections.

Choosing Start Up Conditions

To get started, a load control task needs an initial velocity and an initial stiffness [math]\displaystyle{ A_t }[/math] (which is required to calculate control error). Furthermore, reaction and contact forces in dynamic calculations take a while to settle into reasonable values (such as when loading at constant velocity). A load control task thus normally needs a startupTime, which is time where the rigid particle move at the (initvelocity) without imposing any control. Once the start up time has pasted, the load control begins using an initial [math]\displaystyle{ A_t }[/math] that can be determined one of two methods:

1. If you do not want to (are not able to) calculate an initial [math]\displaystyle{ A_t }[/math], specify a positive (inittime). The initial [math]\displaystyle{ A_t }[/math] will be found by least squares slope for force vs. displacement up to (inittime). Any provided (initAt) will be ignored.
2. Specified [math]\displaystyle{ A_t }[/math]: If you can calculate initial stiffness for the simulation, you can enter it in (initAt) parameter and then set (inittime) to minus the desired start up time. Once the time is passed, control will the provided [math]\displaystyle{ A_t }[/math].

Finding [math]\displaystyle{ A_t }[/math] from slope of force vs. displacement required that (inittime) be 10-20 multiples of [math]\displaystyle{ t_g }[/math] to have enough points to fit a line. The start up time must also be long enough that the calculation is not affect by dynamic start-up artifacts. Even when specifying [math]\displaystyle{ A_t }[/math] with negative start up time, the time should be long enough to bypass dynamic start-up artifacts. If control is started too soon, those artifacts may lead to unstable results.

Task Scheduling

In scripted files, a LoadControl custom task is scheduled with the following block:

CustomTask LoadControl
Parameter Load,(function)
... all remaining parameters with similar command

In XML files, these task options are scheduled using a <Schedule> element, which must be within the single <CustomTasks> block:

<Schedule name='LoadControl'>
   <Parameter name='Load'>(function)</Parameter>
   ... all remaining parameters with similar elements
</Schedule>