OS-T: 1600 Fluid-Structure Interaction Analysis of Piezoelectric Harvester Assembly with new HyperWorks GUI

UD_21543
UD_21543 New Altair Community Member
edited April 15 in Altair HyperWorks

OS-T: 1600 Fluid-Structure Interaction Analysis of Piezoelectric Harvester Assembly

Product Version: Hyperworks 2021.2.1 or above

The purpose of this tutorial is to demonstrate how to carry out Fluid-Structure Interaction analysis that is, with OptiStruct nonlinear transient analysis coupling within AcuSolve fluid dynamic analysis.

In this tutorial, you will explore the possibility of using piezoelectric based fluid flow energy harvesters. These harvesters are self-excited and self-sustained in the sense that they can be used in steady uniform flows. The configuration consists of a piezoelectric cantilever beam with a cylindrical tip body (which is the structure model) which promotes sustainable, aero-elastic structural vibrations induced by vortex shedding and galloping. The structural and aerodynamic properties of the harvester alter the vibration amplitude and frequency of the piezoelectric beam and the fluid flow. As you may know, the Piezoelectric energy harvesting using fluid flow involves the mutual interaction of three distinct dynamic systems, namely the fluid, the structure and the associated electrical circuit.

Note: This tutorial is limited to study only fluid and the structure domain.

Figure 2 illustrates the fluid structural model used for this tutorial: the dimensions of the beam are shown in Figure 1 and Figure 2.

pfsi_energy_harvester_model_intro

Figure 1. Schematic of the Problem

pfsi_beam_with_various_layers

Figure 2. Various Layers of Beam

The AcuSolve fluid model (slab_dcfsi.inp) and the OptiStruct structural beam model (Slab.fem) are located in the fsi_models.zip file. Refer to Access the Model Files in the online help.

Step 1. Launch HyperWorks and Set the OptiStruct User Profile

  1. Launch HyperWorks.
  2. Select OptiStruct solver interface.

This loads the user profile. It includes the appropriate template, macro menu, and import reader, paring down the functionality of HyperWorks to what is relevant for generating models for OptiStruct.

Step 2: Import the Model

  1. Click File > Import > Solver Deck.

A Select OptiStruct file browser opens.

  1. Select the Slab.fem file you saved to your working directory.
  2. Click Open.
  3. Click Import to close the Solver Import Options window.


Step 3: Set Up the Model

3.1 Create Contact Surface

  1. In the contact Browser, right-click and select Create > Contact Surface from the context menu.

A default contact surface template displays in the Entity Editor.

  1. For Name, enter FSI_Interaction_Surf.
  2. Click Color and select a color from the color palette.
  3. For Elements, click 0 elements > elements > face and pick all the faces of the beam except in the front and end faces, as shown in Figure 3.

image

Figure 3. All sides of the beam except in the front

  1. Click imageto add the faces to the contact surface.

3.2 Define Nonlinear Parameters

  1. In the Model Browser, right-click Load Step Inputs collector and select Create > NLPARM, as shown in Figure 4.

A default NLPARM load step inputs collector template displays in the Entity Editor.

image

Figure 4. Create NLPARM card

  1. For Name, enter NLPARM.
  2. Input the values, as shown in Figure 5.

See NLPARM Bulk Data Entry for more information.

image

Figure 5. NLPARM card

3.3 Define Transient Time Step Parameters

  1. In the Model Browser, right-click Load Collectors and select Create > TSTEP.

A default TSTEP load collector template displays in the Entity Editor.

  1. For Name, enter TSTEP.
  2. For TSTEP_NUM, enter 1.
  3. Input the values, as shown in Figure 6.

See TSTEP Bulk Data Entry for more information.

        image

        Figure 6. TSTEP card

3.4 Define Incremental Result Output for Nonlinear Analysis

  1. In the Model Browser, right-click Load Step Inputs collector and select Create > NLOUT.

A default load step inputs collector template displays in the Entity Editor.

  1. For Name, enter NLOUT.
  2. Input the values, as shown in Figure 7.

See NLOUT Bulk Data Entry for more information.

image

Figure7. NLOUT card

3.5 Define Fluid-Structure Interaction Parameters

  1. In the Model Browser, right-click Load Collectors and select Create > FSI.

A default FSI load collector template displays in the Entity Editor.

  1. For Name, enter FSI.
  2. Input the values, as shown in Figure 8.

See FSI Bulk Data Entry for more information.

image

Figure 8. FSI card

3.6 Define Output Control Parameters

  1. In the Model Browser, right-click cards collector and select Create > GLOBAL_OUTPUT_REQUEST, as shown in Figure 9.

image

Figure 9. Create GLOBAL_OUTPUT_REQUEST

  1. For DISPLACEMENT, ELFORCE, OLOAD, STRESS, and STRAIN, set Option to Yes.

3.7 Create Nonlinear Transient Analysis Subcase

  1. In the Model Browser, right-click and select Create > Load Step from the context menu.
  2. For Name, enter FSI.
  3. For Analysis type, select Nonlinear transient.
  4. Select the Load Collector, as shown in Figure 10.

image

Figure 10. Create load step

Step 4: Modify the AcuSolve input file

  1. Open the AcuSolve input file (slab_dcfsi.inp) in a text editor.
  2. Change the socket_host parameter in the EXTERNAL_CODE block to your machines hostname and save the file, as shown in Figure 11.

        os_1600_acusolve_command

        Figure 11. Modify the AcuSolve input deck

Step 5: Submit the Job

  1. Launch the Compute Console (ACC), select CoSim > FSI AcuSolve, select the Slab.fem file as input file and the slab_dcfsi,inp file as Cosimulation file, as shown in Figure 12.
  2. Click Run.

image

Figure 12. Submit the job using ACC


If the job is successful, you will see new results files in the directory where the input decks are located in. The Slab.out file is where you will find error messages that will help you debug your input deck, if any errors are present.

The default files that will be written to your directory are:

cci.txt

Contains information pertaining to model progression. Logs regarding connection establishment, initial external code handshake and subsequent time step data in conjunction with exchange/stagger.

Slab.html

HTML report of the analysis, giving a summary of the problem formulation and the analysis results.

Slab.out

ASCII based output file of the model check run before the simulation begins and gives some basic information on the results of the run.

Slab.stat

Summary of analysis process, providing CPU information for each step during the process.

Slab.h3d

HyperView compressed binary results file.

Step 6: View the Results

Using HyperView, plot the Displacement contour at 0.95 s, as shown in Figure 13.

image

Figure 13. View the Results

Tagged:

Categories