Fatigue Analysis of Notched Laminates: A Time-Efficient Macro-Mechanical Approach

A coupled transversely isotropic deformation and damage fatigue model is implemented within the finite element method and was utilized along with a static progressive damage model to predict the fatigue life, stiffness degradation as a function of number of cycles, and post-fatigue tension and compression response of notched, multidirectional laminates. Initially, the material parameters for the fatigue model were obtained utilizing micromechanics simulations and the provided [0], [90] and [plus or minus 45] experimental composite laminate S-N (stress-cycle) data. Within the fatigue damage model, the transverse and shear properties of the plies were degraded with an isotropic scalar damage variable. The damage in the longitudinal (fiber) ply direction was suppressed, and only the strength of the fiber was degraded as a function of fatigue cycles. A maximum strain criterion was used to capture the failure in each element, and once this criterion was satisfied, the longitudinal stiffness of the element was decreased by a factor of 10 (sup 4). The resulting, degraded properties were then used to calculate the new stress state. This procedure was repeated until final failure of the composite laminate was achieved or a specified number of cycles reached. For post-fatigue tension and compression behavior, four internal state variables were used to control the damage and failure. The predictive capability of the above-mentioned approach was assessed by performing blind predictions of the notched multidirectional IM7/977-3 composite laminates response under fatigue and post-fatigue tensile and compressive loading, followed by a recalibration phase. Although three different multidirectional laminates were analyzed in the course of this study, only detailed results (i.e., stiffness degradation and post-fatigue stress-train curves as well as damage evolution states for a single laminate ([30/60/90/minus 30/minus 60] (sub 2s)) are discussed in detail here.