Fuel cell stack simulation method using RVE technology

By automatically generating representative volume element (RVE) single fuel cell model, the problem of complex calculation of existing fuel cell stack finite element model is solved, and fast and efficient fuel cell stack simulation is achieved, which improves the degree of model simplification and simulation efficiency.

CN119066902APending Publication Date: 2024-12-03DASSAULT SYSTEMS AMERICAS CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410691598.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-31
Filing Date
2024-05-30
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

The finite element model of existing fuel cell stacks is complex and time-consuming. Although the use of representative volume element (RVE) method can reduce the degrees of freedom, there are limitations of isotropic, orthogonal anisotropic and nonlinear material models, which is difficult to Effectively optimize the mechanical properties of fuel cells.

Method used

The computer-executed method automatically generates a representative volume element (RVE) single fuel cell model, receives a single cell of the finite element model, generates the corresponding RVE cell area, and uses automation plug-ins to simulate and connect the cell area, creates a Global model and sub-model, which realizes the loading curve of the pressure and closure relationship of the single cell, is used to define the pad thickness behavior.

Benefits of technology

Effectively reduces the computational complexity and time-consuming of fuel cell stack simulation, improves the simplification of the model, and can quickly generate multiple RVE cell areas, replaces the FE cell areas in the model, reduces the number of manual steps, and improves the simulation efficiency. .

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119066902A_ABST
    Figure CN119066902A_ABST
Patent Text Reader

Abstract

The present application relates to a fuel cell stack simulation method using RVE technology, the method being a computer-implemented method that automatically generates a representative volume element (RVE) cell fuel cell model. A finite element model (FEM) of a cell of a proton exchange membrane fuel cell (PEMFC) is received. An input is received that identifies a discretized cell region with FE cell cells. A mesh rule corresponding to the cell region is received. An RVE cell region corresponding to the FE cell region is generated based on the FE cell region and a mesh rule.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to fuel cell technology, and more particularly, to the design and manufacture of proton exchange membrane fuel cells. Background Art

[0002] Proton exchange membrane fuel cell (PEMFC) stack 200 is shown in FIG. 2B. PEMFC stack 200 is formed by a plurality of substantially identical fuel cell units 100 (FIG. 1). As shown in FIG. 1, each fuel cell unit ("monocell") includes a membrane / electrode assembly 130 sandwiched between two bipolar plates (BP) 110. The proton exchange membrane 136 of the membrane / electrode assembly 130 is disposed between the anode 132 and the cathode 134. Hydrogen is provided by the first bipolar plate 110 at the anode 132, and oxygen is provided by the second bipolar plate 110 at the cathode 134. The membrane 136 allows only positively charged hydrogen atoms to pass through the membrane / electrode assembly 130 to combine with oxygen to form water, thereby generating voltage across the anode 132 and the cathode 134. The layers of each fuel cell unit 100 can be sealed using a gasket 150 (FIG. 2A) to prevent fluid leakage. The voltage of a single fuel cell unit 100 is relatively small, so stacking a plurality of fuel cell units 100 into a PEMFC stack 200 will produce a higher voltage.

[0003] As shown in FIG. 2A , the bipolar plate 110 has channels 220 in a grid-like pattern to facilitate the flow of gas and liquid through the unit fuel cell assembly 100 .

[0004] As mentioned in the article "Mechanical simulation of a Proton Exchange Membrane Fuel Cellstack using representative elementary volumes of stamped metallic bipolar plates" (Willy Charon, Marie-Christine Iltchev, Jean-Francois Blachot, International Journal of Hydrogen Energy 39 (2014) 12195-13205), in order to control the performance of the fuel cell, knowledge of the mechanical stresses is required, and early modeling and simulation of the stack structure reduces the cost of the stack and helps to design the size and form of the components. In addition, response simulation enables the prediction of mechanical stresses, which can be analyzed and modified to calculate electrical performance. However, a detailed finite element (FE) model (FEM) of a fuel cell stack can have up to billions of degrees of freedom, which makes it computationally impractical to solve. While replacing some of the basic volumes with representative volume elements (RVEs) can reduce the number of degrees of freedom (DoF) in the modeled BP, the setup of such simulations is very time-consuming and laborious, as are all subsequent iterations to optimize a fuel cell for a given application. In addition, material models developed using the RVE approach are isotropic, orthotropic, and anisotropic (linear elastic models). Therefore, the industry needs to address these shortcomings. Summary of the invention

[0005] Embodiments of the present invention provide a simulation method for a fuel cell stack using RVE. Briefly described, the present invention relates to a method executed by a computer that automatically generates a representative volume element (RVE) single fuel cell model. A finite element model (FEM) of a single cell of a proton exchange membrane fuel cell (PEMFC) is received. An input is received that identifies a unit region with a discretization of a FE single cell. A grid rule corresponding to the unit region is received. Based on the FE unit region and the grid rule, an RVE unit region corresponding to the FE unit region is generated.

[0006] By reading the following drawings and detailed description, other systems, methods and features of the present invention will be or will become apparent to one of ordinary skill in the art. It is intended that all such additional systems, methods and features be included in this specification, be included within the scope of the present invention, and be protected by the appended claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] The accompanying drawings are included to provide a further understanding of the present invention, and are incorporated in and constitute a part of this specification. The components in the drawings are not necessarily drawn to scale, but emphasis is placed on clearly illustrating the principles of the present invention. The accompanying drawings illustrate embodiments of the present invention and together with the description serve to explain the principles of the present invention.

[0008] FIG. 1 is a schematic diagram of an exemplary fuel cell unit.

[0009] FIG. 2A is an exploded schematic diagram showing a bipolar plate of the fuel cell unit of FIG. 1 .

[0010] 2B is a schematic diagram of an exemplary fuel cell stack including a plurality of fuel cell units of FIG. 1 .

[0011] Figure 3 is a schematic diagram showing an exemplary discretization segmentation of a FE single cell.

[0012] Figure 4 is a schematic diagram of a user interface of a first plug-in illustrating a first exemplary embodiment of an automated process for generating a unit region RVE.

[0013] Figure 5 It is a depiction Figure 4 Schematic diagram of the inputs and outputs of the first part of the first plugin.

[0014] Figure 6 It is a depiction Figure 4 Schematic diagram of the inputs and outputs of the second part of the first plugin.

[0015] Figure 7 It is a depiction Figure 4 Schematic diagram of the inputs and outputs of the third part of the first plugin.

[0016] Fig. 8A It is shown Figure 4 Schematic diagram of the data structure of the input of the first step of the first plugin and the output from the first step.

[0017] Figure 8B It shows the direction Figure 4 Schematic diagram of the data structure input to and output from the second step of the first plugin.

[0018] Figure 8C is an extension Figure 8B Schematic diagram of “Scene” 840 .

[0019] Fig.8D is used Figure 4 Schematic diagram of the input and output data flow during the first plugin.

[0020] Fig. 9is a schematic diagram of a user interface of a second plug-in illustrating a second exemplary embodiment of an automated process for generating RVE cells from a plurality of unit regions RVE.

[0021] Fig.10 It is a depiction Fig.11 Schematic diagram of the second plugin's input and output.

[0022] Fig.11 is a flowchart showing the flow of processing of the first embodiment and the second embodiment.

[0023] Fig.12 is a schematic diagram showing an example of a system for performing the functions of the present invention.

[0024] Fig.13 is a schematic diagram indicating a data set before the second plug-in is run, a data set after the first part of the second plug-in is run, and a data set after the third part of the second plug-in is run.

[0025] Fig.14 It is shown by Fig. 9 A flowchart of the functional flow of an exemplary embodiment of the CAD discretization performed by the first portion of the second plugin.

[0026] Fig.15 It is shown by Fig. 9 A flow chart of the functional flow of an exemplary embodiment of a CAD discretization performed by a second portion of a second plugin. DETAILED DESCRIPTION

[0027] The following definitions are useful for explaining terms applied to features of the embodiments disclosed herein and are meant only to define elements in the present disclosure.

[0028] As used in the present disclosure, "proton exchange membrane fuel cell" (PEMFC), also known as polymer electrolyte membrane (PEM) fuel cell, refers to a type of fuel cell commonly used in transportation applications, as well as for stationary fuel cell applications and portable fuel cell applications. Such fuel cells can operate within a certain temperature and / or pressure range (50°C to 100°C) and involve a proton conducting polymer electrolyte membrane. PEMFC produces electricity and works on the opposite principle of PEM electrolysis, which consumes electricity. PEMFC can be formed by a membrane electrode assembly (MEA), which includes electrodes, catalysts and gas diffusion layers (GDL). The cell has a three-phase boundary (TPB), wherein the electrolyte, catalyst and reactants are mixed at the TPB.

[0029] As used in this disclosure, a "membrane electrode assembly" (MEA) refers to the PEM membrane, cathode catalyst layer, and anode catalyst layer of a PEMFC.

[0030] As used in this disclosure, "catalyst layer" (CL) refers to the nano-scale pore structure of the PEMFC. The CL is added on both sides of the membrane, with the anode layer on one side and the cathode layer on the other side, tightly surrounding the PEM.

[0031] As used in this disclosure, "bipolar plate" (BP) or flow field plate refers to the outer layer of a PEMFC to provide flow input and output of gas and water. The BP can be a metal plate that has been stamped to form fluid channels. Complex and irregular channel patterns present significant modeling challenges.

[0032] As used in this disclosure, "top plate" refers to the first plate of a PEMFC to which the translation for uniaxial compression is applied. The corresponding fixed plate is called the bottom plate. When manipulating a single fuel cell in a CAD environment, a user can add "top" to the description of the 3D part to which the user wants to apply the translation. Similarly, the user can add "bottom" to the description of the corresponding 3D part. The CAD environment creates a local coordinate system in which the z-axis is defined as orthogonal to the top plate. The translation is applied to this z-axis.

[0033] As used in this disclosure, "field output" refers to data that is spatially distributed throughout a fuel cell model or a portion of a model.

[0034] As used in this disclosure, "historical output" refers to data at specific points in a fuel cell model, for example, data recorded at those points under different load conditions.

[0035] As used in the present disclosure, "Knowledge Engineering Specification" (KES) refers to a data structure used to specify a physical component (real world product). KES may include, for example, an engineering template for replicating a product. The engineering template may include multiple components of a physical component, wherein at least some of the components are represented by FEM. The engineering template is contained in a resource table for the component design. For KES, the engineering template is instantiated using reaction, wherein the reaction can be triggered by one or more parameters.

[0036] As used in this disclosure, "displacement" refers to the distance between two components of an assembly, for example, the spacing between a first bipolar plate parallel to a second bipolar plate.

[0037] As used in this disclosure, "translation" refers to the change in displacement between components of an assembly, measured in mm, for example.

[0038] As used in this disclosure, "cell" or "cell assembly" refers to a PEMFC subassembly consisting of a solid body and its geometric shape and mechanical properties. An exemplary cell assembly may include a stack of components that form the active portion of the cell:

[0039] Membrane / electrode assembly (MEA), i.e., proton exchange membrane, catalyst on the anode side and catalyst on the cathode side

[0040] Two gas diffusion layers (GDL), and

[0041] Two metallic bipolar plates (BP) sandwich the MEA / GDL and distribute the gas and cooling fluid.

[0042] The cells may also include sealing joints (gaskets) that isolate the active area from the hydrogen, air, and cooling circuits.

[0043] As used in this disclosure, a "PEMFC stack" is an assembly formed from a plurality of similar single cells.

[0044] As used in the present disclosure, “FE cell” of “FE cell” refers to a finite element model of the cell.

[0045] As used in this disclosure, a "basic volume" refers to a repeating three-dimensional portion of a single cell having a specific shape. An equivalence domain is associated with each basic volume, such as a cuboid surrounding the basic volume.

[0046] As used in the present disclosure, representative volume element (RVE) refers to a method of simplifying the model by replacing the basic volume of the FE battery part with a composite finite element with homogenized properties. Here, the surface of the single cell is divided into multiple smaller areas ("unit areas"). The unit areas may have irregular sizes and shapes. Unit areas with the same geometry and similar properties can be marked as unit nodes, where some unit areas (basic volumes) are replaced by RVEs with the same volume. The properties of interest include mechanical properties (such as elastic modulus) and thermal properties, which can be any average quantity used to describe the physical system.

[0047] As used in this disclosure, an "RVE battery" refers to a FE battery in which at least some of the FE battery cell areas have been replaced by RVE cell areas having the same volume.

[0048] RVE is a unit material volume element, which represents the constitutive response of the corresponding structure. A single fuel cell is discretized into smaller element volumes (called unit regions). A specific unit region is composed of linear elastic, superelastic and super foam materials. The combined effect of all these materials is interesting for representing the unit region as a basic volume. Therefore, a liner element with a liner thickness behavior (damage type) material model is used to define the unit region to take into account the geometric shapes and nonlinearity of materials of different fuel cell components. The loading curve of the pressure and closure relationship generated by the uniaxial compression of the unit region is used to define the liner thickness behavior.

[0049] As used in this disclosure, "generating wireframes and surfaces" refers to a method of modeling a physical surface using multiple smaller geometric surfaces ("surface-based models") that have edges similar to physical wireframes. These smaller geometric surfaces are collectively referred to as "meshes." The granularity and accuracy of the surface model can be controlled by specifying the shape and size of the mesh elements. "Partitioning" involves cutting the surface-based model into smaller parts (partitioned parts) without losing any frames.

[0050] As used in this disclosure, "partitioning" refers to the operation of cutting a surface or solid, which is usually handled as two separate commands of a computer-aided three-dimensional interactive application (CATIA). For example, in order to remesh the geometry contained within a bounding box, the geometry of a single fuel cell needs to be partitioned (cut) by the bounding box. For BP, MEA, top plate, and bottom plate, the mesh is created on the surface geometry, so the surface geometry partitioning operation is used. For GDL, the pad mesh is created on the solid geometry, so the solid geometry partitioning operation is used.

[0051] As used in this disclosure, "reaction" generally refers to a feature that enables a user to create a script that specifies how to change one or more feature properties when an event occurs. For example, an event can be any common event associated with a CAD object, such as creation, deletion, update, attribute change, and parameter value change.

[0052] As used in this disclosure, a "project template" refers to a data structure for (usually) commonly used components. Instantiating a project template enables pre-existing components to be reused for new purposes.

[0053] It should be noted that one of ordinary skill in the art is familiar with the process of selecting elementary volumes and determining the associated RVE for each elementary volume.

[0054] Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numerals are used in the drawings and the description to refer to the same or like parts.

[0055] The present disclosure provides an exemplary embodiment of a representative volume element (RVE) method for achieving model reduction of a fuel cell assembly. RVE is a unit material volume element that represents the constitutive response of the corresponding structure. A single fuel cell is discretized into smaller element volumes (referred to as unit regions). A specific unit region may include linear elastic, hyperelastic and / or super foam materials. The combined effects of all these materials are combined to represent the unit region as a basic volume. Thus, for example, a gasket element with a gasket thickness behavior (damage type) material model can be used to define the unit region to account for the geometry and material nonlinearity of different fuel cell components. The loading curve of the pressure and closure relationship generated by the uniaxial compression of the unit region can be used to define the gasket thickness behavior.

[0056] In a first embodiment, the strategy for automating the simulation of a PEMFC can be summarized as follows:

[0057] 1. Receive the initial design of PEMFC.

[0058] 2. Prepare the FE cell of PEMFC. This includes analyzing the cell used for simulation (including the geometric features of the bipolar plates), for example, identifying repeated features and symmetric areas.

[0059] 3. Generate RVE. This includes discretization of the FE single cell (dividing the FE single cell into multiple unit regions), identifying repeated unit regions, modeling each repeated unit region, and performing simulation of each unit region. Figure 3 The exemplary discretization strategy shown includes selecting a rectangular pattern of single cell FEM 310 to create the surface geometry. It should be noted that this is for demonstration purposes only. Figure 3 Uniformly sized cell regions 510 are shown that do not correspond to the geometry of the single cell FEM 310. The behavior of the gasket may also be accounted for (eg, the gasket may be created as a volume element preloaded with an initial condition).

[0060] 4. Global model (with RVE). This includes creating a global model (with pad behavior) in the presence of clamping forces and recording the simulation results of the global model.

[0061] 5. Sub-model. Here, a sub-model is a local part of the full model, in this case a detailed FE model with a refined mesh (similar to a cell region). The sub-model is driven by interpolations from the solution of the initial global RVE model.

[0062] It should be noted that a more detailed description of this simulation can be found in the reference authored by Charon.

[0063] In a first exemplary embodiment, a first application ("first plugin") accepts parameters associated with a portion of a FE cell to automatically generate a corresponding RVE unit region. Figure 4 A first exemplary embodiment of a graphical user interface (GUI) for a first plug-in 400 is shown. The interface includes a first unit portion 410 (corresponding to the first step) for receiving user input related to a selected unit area ("box") 510, a second portion 450 (corresponding to the second step) for receiving user input related to a model scenario, a third portion 460 (corresponding to the third step) for receiving a path of an RVE generated by the plug-in as output, and a fourth portion 470 displaying a progress status indicator.

[0064] The first part 410 is used for the first step of unit region model cutting and unit region mesh connection creation. Figure 5 A representation of the inputs and outputs to be populated of the first portion 410 of the first plug-in user interface 400 is depicted. The user selects a cell region 510 from a cell FEM 310. For example, by clicking on a box 422, the host CAD program can graphically display a plurality of cell regions of the cell FEM 310 to the user. The user can select the cell region 510 in the graphical representation of the cell FEM 310 through the host CAD program, for example, by clicking on a particular cell region of the cell FEM 310 (e.g., using a mouse or trackpad) to select the cell region 510 so that the plug-in receives the selection. The "box number" field 411 displays the number of the selected cell region 510 in the cell region ("box") identifier field 411 and displays the corresponding FEM identifier of the cell FEM 310 in the FEM identifier field 412 of the first portion 410. In an alternative embodiment, the user can select the cell region by entering a box number in the box identifier field 411 and a FEM identifier in the FEM identifier field 412.

[0065] The user may then use the cell area mesh rules box 413 to specify rules for different portions of the identified cell area, in this example, the cell area mesh rules for the bipolar plate 414 , gasket 415 , proton exchange membrane (PEM) 416 , and gas diffusion layer (GDL) 417 .

[0066] Here, the user assigns elements 890 to the unit area grid according to the components of the unit area, for example, as shown in Table 1, and with reference to Figure 8C :

[0067] Table 1

[0068]

[0069]

[0070] Alternative embodiments may use other component types as well.

[0071] The FEM box 424 is used to verify whether the FEM representation of the single cell is replicated in the cell area model. In some cases, the replication may fail. In such a failure scenario, the replication of the FEM representation has not been achieved in the cell area, and the plug-in will not execute further steps, but will display an error message, such as, "The user selected FEM does not exist in the product."

[0072] To complete the first step, when triggered by the user, for example, via the "Step 1" button 418, the first plug-in uses the received fields to generate a unit area model 500, as further described below. Fig. 8A is a schematic diagram showing the input and output of the first step of the first plug-in 400. The input of the first step is a single fuel cell model 810, which may include, for example, a KES 812, a 3D part 814 containing an RVE bounding box, and / or a 3D product 816 (containing a single cell FEM) to be copied to generate a unit area model. The 3D product may be, for example, a CAD representation or a FEM representation of the product.

[0073] When executed, the first step of the first plug-in generates a first RVE 821. The first step may be executed a second time, the second execution receiving the definition of the second unit area 822 of the cell FEM 810 and generating a corresponding second RVE 822. The first plug-in 400 may be executed n times, and for each of the n unit volumes, the first plug-in 400 may be executed once, thereby generating n RVEs 821, 822, ..., 82n.

[0074] Once the first plug-in 400 has generated the unit area model 500 in the first step, the second step (corresponding to the second part 450) receives user input related to the model scenario 840, which defines the forces that can act on the unit area model.

[0075] The goal of the second step scenario 450 is to establish a uniaxial compression simulation load case, which generates force-displacement data when executed. In a third step 460, the force-displacement data is further converted into pressure-closure data, as further described below.

[0076] For example, the user can move the top panel to the field 452 ( Figure 4) inputs the top plate translation value (e.g., distance in mm). The translation value is used to describe the scene 840, wherein the plug-in passes the translation value to an application, such as a "mechanical scene application", to determine the dynamic behavior of the unit area in the presence of external forces. The second step 450 of the first plug-in applies the data of the scene 840 to the unit area model 500 to generate the unit area scene 600.

[0077] When the user clicks the step 2 button 458, the user interface script calls the application to perform the second step, thereby generating the unit area scene 610. For example, Dassault Systemes' 3DS mechanical scene creation application provides tools to define and perform any type of simulation related to the mechanical model, including analysis combined with transient loading events or dynamic loading events. Here, the script passes the user input data and the results of the first step to the application.

[0078] Figure 8B The output of the second step 450 of the first plug-in 400 is shown, where a scenario 840 is applied to multiple RVEs 831, 832, ..., 83n. Each scenario 840 can correspond to a specific analysis case 841, 842, ..., 84n of the corresponding RVE 831, 832, ..., 83n. The user can use the specific analysis case 841, 842 to determine the corresponding result RVE 861, 862, ..., 86n containing the corresponding scenario-specific analysis case 841, 842, ..., 84n.

[0079] Figure 8C supply Figure 8B Additional details of the scenario processing of the unit area. A static step 87 can be defined for a load case, where the static step performs a stress analysis of a stable problem, where inertial effects are neglected. Here, the interactions 871, 872 between the unit area components are assumed to be "normal contact" 872, where the contact properties define the friction coefficient. The top plate translates along the thickness direction of the unit area by the value manually entered by the user in the second step 450. The bottom plate is fixed and does not translate or rotate in all 3 axes. Symmetric boundary conditions 873 can be assigned to the boundary nodes of the unit area. The output request 874 can include field output 875 of displacement U, reaction force RF, and contact pressure CPRESS; the script has requested historical output 876 of displacement and reaction force at the reference point of the top plate rigid body along the translation direction. When the user clicks the Step 2 button 458, the entire simulation scenario setup is generated and then executed for further post-processing.

[0080] The third part 460 of the first plug-in is used to extract and process the results of the simulation run on the RVE cell area under the scenario input by the user in the second step 450 of the first plug-in. The third part 460 receives as input a path from the user, which the plug-in uses as the destination for the cell area pressure-closure data 720 results.

[0081] While the first embodiment generates the cell region pressure-closure data 720, in an alternative embodiment, the first plug-in 400 may provide data received through the plug-in interface and / or additional data / parameters associated with the RVE cell region to an external module to simulate additional scenarios generating additional data sets as outputs of the first plug-in 400. Such additional outputs may be provided as inputs to the second plug-in 900 ( Fig. 9 , described below).

[0082] For each unit area analysis 841, 842, ..., 84n, the results from the second step 450 include field outputs 875 of displacement, reaction force, and contact pressure.

[0083] Similarly, for each cell region, the displacement history output 876, the results from the second step 450 include the reaction force requested at the rigid body "top plate". The history output graph in the form of xy data is used to extract the pressure closure data points for a specific cell region. For example, the first plug-in provides the cell pressure-closure data 720 results and / or other derived or received data (e.g., displacement scenarios) to an external module to determine a set of material properties suitable for components of a real-world fuel cell.

[0084] After the simulation of the cell area is performed, the third step 460 exports the reaction force versus displacement history graph 710 to a database file (eg, .xsls file). The reaction force data is divided by the "top plate" area to obtain pressure data relative to the closure (displacement) data.

[0085] The fourth portion 470 of the first widget may display a graphical progress indicator.

[0086] Fig.8D The inputs and outputs of each of the three steps performed by the first plug-in 400 are depicted. The inputs to the first step 410 of the first plug-in include prerequisite information (located above the dashed line) and additional inputs (located below the dashed line), including inputs to plug-in text boxes 411, 412, and 414 to 417 ( Figure 4) user parameters. It should be noted that in alternative embodiments, the specific input mechanisms and fields may be different. Prerequisite data is typically associated with the single fuel cell model 810, such as engineering rules (e.g., reactions and formulas), component designs, and engineering templates, among other examples. The host CAD environment can collect prerequisite data through an engineering rule capture application that is used to embed knowledge (e.g., formulas, rules, and checks) in the design and use the knowledge to assist in engineering decisions, reduce errors, or automate the design. Similarly, an engineering template application helps efficiently create operations for copying and referencing database components (e.g., products, simulations, or parts).

[0087] Input data includes data related to generating wireframe and surface parameters and structural model creation 804. Structural model creation 804 may be facilitated by applications native to the CAD environment to add and edit model features that affect the simulated structural response, including, for example, FEM 816 and cell area mesh rule editor 806.

[0088] The first step 410 of the first plug-in discretizes the FEM 816 into a plurality of parts (unit regions) using the prerequisites and inputs, for example, including a plurality of partitioned parts 802. As described above, the first plug-in 400 is based on Figure 4 The illustrated plug-in graphical user interface (GUI) receives user-defined unit area and unit area grid rule parameters 414 to 417 to create a unit area RVE model 500. The user can trigger the generation of the RVE model 500 through the first plug-in GUI, for example, by selecting the step 1 button 418 after manually filling in the appropriate fields 411, 412, 414 to 417 to trigger the generation of the RVE model 500.

[0089] like Figure 6 As shown, the second step 450 of the first plug-in uses the RVE unit model 500 created by the first step 410 of the first plug-in to create a unit area mesh and create a uniaxial compression analysis case. The second step 450 of the first plug-in receives the mechanical scene 840 through the first plug-in GUI, such as the top plate translation 452 ( Figure 4 The user can trigger the generation of the unit area scene 600 through the first plug-in GUI, for example, by selecting the step 2 button 458 ( Figure 4 ) to trigger the generation of the unit area scenario 600. Here, the second step of the first plug-in calls a mechanical scenario creation application or similar existing utility to provide appropriate tools to define and execute simulations of the unit area model 500, including analysis incorporating transient loading events or dynamic loading events.

[0090] like Figure 7As shown, the third step 460 of the first plug-in uses the unit area scene 600 created by the first step 450 of the first plug-in. The third step 460 of the first plug-in (for example, through the path text box 462 ( Figure 5 )) receives the file path input by the user and calls an application, such as a physical result browser, a native application that accepts the unit area scene 600 and creates a graphical output and / or animation of the model response. For example, the output of the third step of the first plug-in can be a graph 710 that plots the relationship between pressure and closure (distance between bipolar plates) in the unit area scene 600.

[0091] As described above, the first plug-in 400 can be used to automatically create multiple RVE cell regions, where the RVE cell regions effectively replace the FE cell regions in the model. The output of the first plug-in 400 is the pressure closure data generated for all cell regions. In a second exemplary embodiment, the pressure closure data is input to the second plug-in 800 to generate the RVE single cell.

[0092] like Fig. 9 As shown, in a second exemplary embodiment, a second application ("second plug-in") 900 accepts parameters related to the RVE unit of the FE battery cell to automatically generate a corresponding RVE battery cell. Fig. 9 A second exemplary embodiment of a user interface for a second plug-in 900 is shown.

[0093] The interface includes a first portion 910 (corresponding to a first step) for receiving user input related to CAD discretization, a second portion 950 for receiving user input related to the RVE cell grid and properties, and a third portion 970 for displaying a progress status indicator.

[0094] The first part (CAD discretization) 910 deals with the geometry preparation to generate the RVE single cell model. The input to this part is the bounding box generated in the discretization step (according to the first part 410 and the second part 450 of the first plug-in 400 described above), the intermediate surface of the fuel cell, and an optional symmetry plane. The second plug-in 900 cuts the input intermediate surface into smaller surfaces, i.e., the area enclosed in the bounding box. If the user has given an input for a symmetry plane, these partitions are used to create symmetry surfaces associated with the plane. For example, the model may have a quarter symmetry, so partitions are generated for one quarter of the surface area, while partitions for the remaining three quarters of the area are generated by symmetry operations. Thus, the user saves time creating a bounding box for the entire geometry. These partitions (and symmetry surfaces, if present) are used as geometric support to generate the surface mesh of the RVE element.

[0095] The first portion 910 of the second plug-in is used to select RVE cell regions to be incorporated into a FE cell to generate an RVE cell ("RVE model"). The second portion 950 of the second plug-in is used to define the properties of the RVE cell regions and the RVE cell mesh to be included in the RVE cell. The second plug-in 900 receives as input a wireframe surface, such as data generated by the first plug-in 400, such as an RVE cell model and pressure (MPa) and closure relationship (data) from a generate wireframe and surface application. The second plug-in 900 also receives parameters manually entered by a user through the GUI of the second plug-in.

[0096] The first portion 910 of the user interface of the second plug-in includes the following controls. The RVE button 921 enables the user to select all bounding boxes (duplicate bounding boxes and unique bounding boxes) created in the discretization step (according to the first portion 410 and the second portion 450 of the first plug-in 400 described above). The "RVE Total" field 911 displays the total number of bounding boxes selected by the user.

[0097] The surface button 922 enables the user to select a surface located at a mid-level of the thickness of the cell, which the bounding box divides into smaller surfaces for creating the RVE surface mesh. The "Name" field 912 displays the name of the selected mid-level surface.

[0098] If there are any symmetry planes, the plane button 924 button enables the user to select a symmetry plane (if there are no symmetry planes, the user can skip this button). The "Plane Number" field 914 displays the number of the symmetry plane selected by the user. The Run button 916 of the first part causes the second plug-in to generate a partition for the selected surface. If the user has provided a symmetry plane, a symmetry surface for the partition is created.

[0099] The second section (Mesh and Properties) 950 receives as input the RVE element thickness values ​​and the path to the folder containing the pressure-closure data generated by the first plugin. The FEM representation is inserted into the RVE cell model. The partitioned sections (and symmetry surfaces, if present) are used to create 2D surface meshes, and these 2D surface meshes are extruded on both sides along the normal direction with a thickness / 2 value. Pad profile properties are created for all 3D meshes. The pressure closure data 720 generated by the first plugin is used to model the pad thickness behavior (damage type) by inserting it in the loading curve section of the material definition. The material is then assigned to the pad properties.

[0100] The second section 950 of the user interface of the second plug-in includes the following controls. The user can type the thickness (in mm) of the RVE element in the "RVE Thickness (mm)" field 952. The RVE surface mesh is extruded at "Thickness" / 2 on both sides of the surface in a direction orthogonal to the surface mesh. The folder button 954 enables the user to select the following folder, which stores the output (database, such as Excel) file of the pressure closure data of the unit area. The "Path" field 956 displays the selected folder path. Clicking the Run button 966 of the second section causes the second plug-in to generate the RVE surface mesh using the partitioning parts and symmetry (the output of the process of the Run button 916 of the first section). These meshes can then be extruded to form RVE 3D elements. The pressure closure data from the database file is used to create a liner behavior material, which is used when defining the liner properties for all RVE elements. The third section progress bar 970 shows the completion status after selecting either Run button 916, 966.

[0101] The second plug-in converts the single fuel cell model to an RVE single cell model. The second plug-in 900 creates the RVE elements by dividing the middle surface of the fuel cell, generating symmetry surfaces (if any symmetry exists in the fuel cell), creating RVE liner thickness behavior materials, and assigning sections to corresponding RVE elements.

[0102] The RVE cell model provides mesh, material and section assignments only to the RVE cell. Material definition application is used to define materials and apply them to objects. Compression of the entire fuel cell model is simulated by using appropriate boundary conditions and loading environments (the minimum boundary conditions required to establish different scenarios for different situations).

[0103] To generate an assembly pattern with "n" fuel cell stacks, the second plugin generates an RVE cell grid. This RVE cell model can then be used to manually create a fuel cell stack to perform further assembly load case simulations. The creation of the assembly pattern to generate the fuel cell stack and the scenario setup for the fuel cell stack is done manually. The assembly pattern now reflects a complete fuel cell stack. To generate an assembly pattern with "n" fuel cell stacks, the second plugin generates an RVE cell grid. This RVE cell model can then be used to manually create a fuel cell stack to perform further assembly load case simulations. The creation of the assembly pattern to generate the fuel cell stack and the scenario setup for the fuel cell stack are done manually. The assembly pattern now reflects a complete fuel cell stack.

[0104] Fig.10 A graphical representation of inputs and outputs for populating a user interface 900 of a second plugin is depicted.

[0105] Fig.131 is a schematic diagram indicating a data set 901 (left side) before the second plug-in 900 is run, a data set 902 (middle) after the first part 910 of the second plug-in is run, and a data set 903 (right side) after the second part 950 of the second plug-in is run. Specifically, the first part 910 of the second plug-in receives the RVE unit area bounding box surface geometry 1310 and generates a corresponding RVE geometry set 1315. Here, "geometry set" refers to a container that stores surface and wireframe geometries, and the RVE geometry set refers to a geometry set generated by the second plug-in 900 to store decomposition patterns of repeated bounding boxes or unique bounding boxes.

[0106] The first part 910 of the second plug-in receives data related to the intermediate surface 1320 of the fuel cell and the symmetry plane 1322, and generates a geometry partition set 1325 (a geometry set storing the partitions and the symmetries of the partitions). The second part 950 of the second plug-in uses the geometry partition set 1325 to generate a FEM representation of the single cell 1350 with a corresponding RVE surface mesh 1352, RVE liner profile 1354, and material 1356.

[0107] Fig.14 is a flow chart 1400 illustrating the functional flow in an exemplary embodiment of CAD discretization performed by the first portion 910 of the second plug-in.

[0108] As shown in block 1420, input is received. Here, the user provides input to the first portion 910 of the plugin via the GUI, including the definition of the fuel cell intermediate surface 1422, the unique bounding box and the repeating bounding box 1424, and / or the symmetry reference plane 1426. For each bounding box (i) as shown in block 1430, a surface partition is received, as shown in block 1440. If a reference plane is received as input for the current bounding box (as shown in block 1450), surface symmetries of the partition associated with that plane are also generated, as shown in block 1460. The process is iterated for each bounding box, as shown in block 1470.

[0109] Fig.15 is a flow chart 1500 illustrating the functional flow in an exemplary embodiment of CAD discretization performed by the second portion 950 of the second plug-in.

[0110] As shown in box 1510, input is received. Here, the user provides input to the first part 950 of the plug-in through the GUI, including RVE thickness 1511 and the folder path of the output file. For each partitioned part (i) as shown in box 1520, a surface mesh is created, as shown in box 111525, and an extruded offset mesh is created, as shown in box 1530. For each material data file (e.g., Excel data file (j) as shown in box 1550), pad properties are created (box 1560), pad property support is assigned (box 1562), and pad material is created and assigned (box 1564). This process iterates until all material data files have been processed, as shown in box 1570. As shown in box 1580, any properties that lack support are removed.

[0111] Fig.11 It is a high-level flowchart of the process of both the first plug-in (1110 to 1150) and the second plug-in (1160 to 1190). It should be noted that any process description or box in the flowchart should be understood to represent modules, fragments, code portions or steps, which include one or more instructions for implementing specific logical functions in the process, and alternative implementations are included within the scope of the present invention. In alternative implementations, depending on the functions involved, the functions can be performed in a different order than shown or discussed, including substantially simultaneously or in reverse order, as understood by a person of ordinary skill in the art of the present invention.

[0112] As shown in block 1120, the first plug-in 400 ( Figure 4 ) steps 1 and 2 discretize the single fuel cell model (block 1110) into unit regions according to a user-specified discretization scheme, create a mesh for the unit regions, and create a uniaxial compression analysis case, as shown in block 1130. As shown in block 1140, step 3 receives the unit region analysis model, determines and publishes the output of the force and displacement relationship of the unit region analysis in a database file, and converts the data into a pressure and closure relationship through the database.

[0113] As shown in block 1160, the second plug-in 900 ( Fig. 9 ) receives pressure versus closure relationship data and the RVE model 1155 to generate a modified RVE model (1170).

[0114] The RVE model input to the second plug-in 900 includes the middle surface of the fuel cell, the bounding box (unique bounding box + repeated bounding box) and the symmetry plane (if any). Differently, the RVE model output by the second plug-in 900 includes the partitioned parts of the middle surface of the fuel cell according to the bounding box. These partitioned parts are used to create an RVE single cell grid with cross-sections and material properties defined for the RVE elements. The second plug-in performs an assembly operation, as shown in block 1180, to generate a global model of the fuel cell, as shown in block 1190.

[0115] As mentioned previously, the present system for performing the functions described in detail above may be a computer, an example of which is shown in FIG. Fig.12 . The system 1200 includes a processor 1202, a storage device 1204, a memory 1206 storing software 1208 defining the functions mentioned above, an input and output (I / O) device 1210 (or peripheral device), and a local bus or local interface 1212 that allows communication within the system 1200. The local interface 1212 can be, for example, but not limited to, one or more buses, or other wired or wireless connections, as known in the art. The local interface 1212 may have additional elements (omitted for simplicity), such as controllers, buffers (cache), drivers, repeaters, and receivers to enable communication. In addition, the local interface 1212 may include address, control, and / or data connections to enable appropriate communication between the aforementioned components.

[0116] The processor 1202 is a hardware device for executing software, particularly software stored in the memory 1206. The processor 1202 can be any custom or commercially available single-core or multi-core processor, a central processing unit (CPU), a secondary processor in a plurality of processors associated with the present system 1200, a semiconductor-based microprocessor (in the form of a microchip or chipset), a macroprocessor, or generally any device for executing software instructions.

[0117] The memory 1206 may include any one or a combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.) and non-volatile memory elements (e.g., ROM, hard drive, tape, CDROM, etc.). In addition, the memory 1206 may include electronic, magnetic, optical and / or other types of storage media. It should be noted that the memory 1206 may have a distributed architecture, in which components are located at locations remote from each other but can be accessed by the processor 1202.

[0118] According to the present invention, the software 1208 defines the functions performed by the system 1200. The software 1208 in the memory 1206 may include one or more separate programs, each of which contains an ordered listing of executable instructions for implementing the logical functions of the system 1200, as described below. The memory 1206 may contain an operating system (O / S) 1220. The operating system essentially controls the execution of programs within the system 1200 and provides scheduling, input-output control, file and data management, memory management, communication control, and related services.

[0119] I / O devices 1210 may include input devices such as, but not limited to, keyboards, mice, scanners, microphones, etc. In addition, I / O devices 1210 may also include output devices such as, but not limited to, printers, displays, etc. Finally, I / O devices 1210 may further include devices that communicate via input and output, such as, but not limited to, modulators / demodulators (modems; used to access another device, system, or network), radio frequency (RF) or other transceivers, telephone interfaces, bridges, routers, or other devices.

[0120] When the system 1200 is in operation, the processor 1202 is configured to execute software 1208 stored within the memory 1206, to communicate data to and from the memory 1206, and to generally control the operation of the system 1200 according to the software 1208, as explained above.

[0121] When the functions of the system 1200 are in operation, the processor 1202 is configured to execute software 1208 stored in the memory 1206, to transfer data to and from the memory 1206, and to generally control the operation of the system 1200 according to the software 1208. The operating system 1220 is read by the processor 1202, possibly buffered within the processor 1202, and then executed.

[0122] When the system 1200 is implemented in software 1208, it should be noted that the instructions for implementing the system 1200 may be stored on any computer-readable medium for use by or in combination with any computer-related device, system, or method. In some embodiments, such a computer-readable medium may correspond to one or both of the memory 1206 and the storage device 1204. In the context of this document, a computer-readable medium is an electronic, magnetic, optical, or other physical device or apparatus that can contain or store a computer program that is used by or in combination with a computer-related device, system, or method. The instructions for implementing the system may be contained in any computer-readable medium, used by or in combination with a processor or other such instruction execution system, device, or device. Although the processor 1202 has been mentioned by way of example, in some embodiments, such an instruction execution system, device, or device may be any computer-based system, a system containing a processor, or other system that can obtain instructions from an instruction execution system, device, or device and execute instructions. In the context of this document, a "computer-readable medium" can be any means that can store, communicate, propagate, or transport the program for use by or in connection with a processor or other such instruction execution system, apparatus, or device.

[0123] Such a computer readable medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared or semiconductor system, device, apparatus or propagation medium. More specific examples of computer readable media (a non-exhaustive list) may include the following: an electrical connection having one or more conductors (electronic), a portable computer floppy disk (magnetic), a random access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM, EEPROM or flash memory) (electronic), an optical fiber (optical), and a portable compact disc read-only memory (CDROM) (optical). It should be noted that the computer readable medium may even be a sheet of paper or another suitable medium on which the program is printed, since the program may be captured electronically, for example, by optical scanning of the paper or other medium, and then compiled, interpreted or otherwise processed in a suitable manner if desired, and then stored in a computer memory.

[0124] In an alternative embodiment where system 1200 is implemented in hardware, system 1200 may be implemented using any one or a combination of the following technologies, each of which is well known in the art: discrete logic circuits having logic gates that implement logic functions on data signals, application specific integrated circuits (ASICs) having appropriate combinations of logic gates, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), etc.

[0125] Automatically generating RVE unit regions (first embodiment) and including multiple RVE unit regions in a FE cell (second embodiment) advantageously reduces the size of computer resources by at least an order of magnitude. In addition, embodiments provide ergonomic advantages by reducing the number of manual steps required to define and select FE unit regions, generate RVE unit regions from each selected FE region, and include multiple RVE unit regions in a FE cell.

[0126] The more laborious task is to manually develop multiple (n) cell area models and then use these cell area models to create multiple analysis cases, with the need to keep track of 2×n files. Since the single cell model must be cut within the bounding box before meshing, connection definition, and analysis creation, creating "n" cell area models was previously a time-consuming and error-prone task.

[0127] The above embodiment is based on the MSR (Modeling, Simulation and Results) approach. The output (plug-in) of the embodiment strings together all data (geometry, FE representation, analysis and results) in a single container (i.e., a unit area analysis model that serves as a single repository for all data).

[0128] It will be apparent to those skilled in the art that various modifications and changes may be made to the structure of the present invention without departing from the scope or spirit of the present invention. In view of the foregoing, it is intended that the present invention encompass modifications and changes of the present invention as long as these modifications and changes fall within the scope of the claims and their equivalents.

Claims

1. A computer-implemented method for automatically generating a representative volume element (RVE) single fuel cell model, the method comprising the following steps: A finite element model (FEM) of a single cell of a proton exchange membrane fuel cell (PEMFC) is received, wherein: The single cell includes a first bipolar plate and a second bipolar plate; receiving an input that identifies a discretized unit region including the FE unit cell based on at least one of the group consisting of: a geometric feature of the first bipolar plate and / or the second bipolar plate of the unit cell, a repeated feature in the geometric feature, and a symmetric region in the geometric feature; receiving a grid rule corresponding to the unit area; and Based on the FE unit area and the grid rule, an RVE unit area corresponding to the FE unit area is generated.

2. The method according to claim 1, wherein: The RVE unit region corresponds to a FE unit region including a portion of a gasket disposed between the first bipolar plate and the second bipolar plate.

3. The method according to claim 2, wherein: The single cell further comprises a polymer electrolyte membrane, a gas diffusion layer, a cathode and an anode.

4. The method according to claim 2, further comprising the steps of: receiving a scenario definition associated with a clamping force applied to the FE battery cell; and An RVE unit area scenario is generated based on the scenario definition.

5. The method according to claim 4, wherein: The scenario definition also includes a translation of the first bipolar plate relative to the second bipolar plate.

6. The method of claim 4, further comprising the step of simulating pad behavior of the RVE unit region in the presence of the clamping force.

7. The method of claim 6, further comprising the step of recording simulation results of the RVE unit region in the presence of the clamping force.

8. The method of claim 6, further comprising the step of determining material properties of components of the RVE cell region based on a simulation of the pad behavior of the RVE cell region in the presence of the clamping force.

9. A computer-implemented method for automatically generating a representative volume element (RVE) fuel cell global model, the method comprising the steps of: Receive RVE single cell battery model; Receiving pressure and closure data of the RVE single cell model; Receiving surface data of the RVE single cell model; and Performing CAD discretization of the RVE single cell model, in, The RVE cell includes a bounding box.

10. The method according to claim 9, further comprising the steps of: Reference plane data of the RVE single cell model is received.

11. The method of claim 10, further comprising the step of determining surface symmetry relative to the reference plane data.

12. The method according to claim 9, wherein: The surface data includes the middle surface of the RVE single cell.

13. The method of claim 9, further comprising the step of receiving data indicating that the RVE cell model is one of the group consisting of a unique bounding box and a duplicate bounding box.

14. The method according to claim 9, further comprising the steps of: Receiving grid parameters of the RVE fuel cell global model; determining the material of the RVE fuel cell global model; and A global model of the RVE fuel cell is formed.

15. The method according to claim 14, further comprising the steps of: receiving material properties of components in the RVE unit region; and Materials are assigned to corresponding components of the RVE fuel cell global model.