|
|
|
Description
The fatigue check is divided into individual subtasks FATCOMB in order to be able to map the necessary different evaluation of the input results. No assemblies are to be specified. No other subtasks are allowed, only FATCOMB.
Subtasks follow the same rules as other tasks. The local definition of the start day refers to the start day of the container. All subtasks are FATCOMB given the start day 1/LOCAL.
The use of FATCOMB outside the FATIGUE scope requires the direct use of FATOPEN and FATCLOSE by the user.
Arguments
The basic arguments correspond to those of all tasks (cf. TCL Command TASK). The other arguments are to be entered in the form "key=value".
There are following other specific predefined arguments:
Key |
Value |
Dimension |
Meaning |
env |
envbase |
TEXT |
Non-cyclic envelope, e.g. row from combination table |
env1 |
envcycle |
TEXT |
Cyclic envelope, e.g. row from combination table |
ncycle |
cycles |
INT |
Number of cycles |
Scopes
FATIGUE
Examples
TASK FATCOMB 1 LOCAL 0 "" "env=C7" "env1=C8" "ncycle=200000" "descr=Fatigue according to combination FLM4_200/450"
The fatigue combination is added to the FATIGUE container.
|
(C) ALLPLAN GmbH |
Privacy policy |
