28.06.2013 Views

Fatigue behaviour of composite tubes under multiaxial loading

Fatigue behaviour of composite tubes under multiaxial loading

Fatigue behaviour of composite tubes under multiaxial loading

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

J Lambert, A R Chambers, etc. / <strong>Fatigue</strong> damage characterisation for wind turbine blade GFRPs using computed tomography<br />

Fig. 1. µCT setup <strong>of</strong> a complete test specimen.<br />

The XTek system uses two main scan types, “slow” and “fast”. During a slow scan, the specimen<br />

stage stops rotating while each radiograph is taken, whereas with a fast scan the specimen is rotated<br />

continuously. It was found that fast scans, taking 1910 different projection during the 360 o rotation,<br />

<strong>of</strong>fered the most efficient option. Scans took 1 hour and 7 minutes to perform. The reconstruction was<br />

performed using the Metris CT Pro s<strong>of</strong>tware, and the reconstructions were visualised using VGStudio<br />

Max.<br />

3 Results<br />

3.1 Mechanical test results<br />

The static test results yielded an average failure stress <strong>of</strong> 440 MPa with a standard deviation <strong>of</strong> 27<br />

MPa. The fatigue tests that were conducted to failure gave the following results. All tests were<br />

performed at 352 MPa alternating stress, corresponding to -/+ 40% UTS.<br />

Fig. 2. <strong>Fatigue</strong> test results in the form <strong>of</strong> a single load level S-N plot, including the failure mode.<br />

Two different failure mechanisms were observed as shown in Fig.3. The compressive failures, Fig<br />

3.(a) were characterised by multiple large-scale delaminations along the whole gauge length between<br />

many, if not all the plies (discussed further in section 3.3).<br />

57

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!