Best Of
Re: How I deactivate my licence?
HI,
Your previous license key activation is now deactivated in Altair one, you can now reactivate the product in your machine with the same license key.
Deactivation and reactivation feature is only if a computer breaks down and is only allowed a few times per user.
You can deactivate the license from one machine and reactivate in another if you have access to both machines as per –
https://community.altair.com/discussion/34280/altair-student-edition-deactivate-from-one-computer-to-activate-in-another-in-the-rare-case-a-computer-is-lost-or-malfunctional#latest
Re: How to perform scooter simulation with CVT using the built in two wheeler scooter model
Hi @sudo,
Vehicle models can be easily simulated using the Vehicle Tools Extension.
For best results, please use the most recent release of MotionView (version 2024.1).
Driver models, automotive components, and standard events can all be added easily using the Entity Browser and is extensively covered in our help documentation.
Two and three wheeler vehicle modeling is discussed in this Community post as well:
https://community.altair.com/discussion/36772/two-and-three-wheeler-vehicle-dynamics-and-durability-in-motionsolve?utm_source=community-search&utm_medium=organic-search&utm_term=double+lane+change
Vehicle modeling is extensively covered in the following eLearning course:
https://www.youtube.com/watch?v=k3KhajpZEzY&ab_channel=AltairHyperWorksHow-To
https://learn.altair.com/enrol/index.php?id=497
Hope this helps!
Adam Reid
Re: How can I remove this error in wire meshing? [FEKO 2023.1 Version]
If you'd like to consider the feeder wire's radius, you need to replace the wire with a 3D geometry (cylinder).
Please refer to the following steps.
- Draw a cylinder. ← after deleting the wire feeder.
- Region medium → Free space
- Split the cylinder and union.
- Apply the edge port. → Voltage source.
Best regards,
Jaehoon
Re: EDEM Question
Hi,
If you have a geometry (blue in the above image?) then you should ensure that this is set to be Physical not Virtual. This is set in Creator > Geometries > Geometry Name > Type option.
If the geometry is Physical and particles are passing through it then this is most likely due to time-step value used. Typically simulations are run at 20% Rayleigh time-step but smaller values can often be required for high velocities and forces in the system.
Regards
Stephen
Re: How can I remove this error in wire meshing? [FEKO 2023.1 Version]
Hello,
Feko's wire segment mesh is based on the thin wire approximation. Therefore, the wire segment's radius should be smaller than the segment's length (Maybe 5~10 times smaller).
Please change the wire segment radius (5 → 0.001) in Modify mesh setting as shown below.
Best regards,
Jaehoon
Vehicle Door Slam Simulation in MotionSolve
Overview
INTRODUCTION
This study presents a CAE multibody dynamics simulation of a car door slam event, focusing on detailed kinematic models of hinges, latches, and sliders. The simulation evaluates dynamic constraints, structural integrity under impact, and stress distribution considering material properties. This virtual prototype could also be extended to aid automotive closures engineers in enhancing power window mechanisms, central locking systems, and sensor integration efficiency, reducing reliance on physical testing.
Opening and closing the door should require minimal user effort. The door also needs to survive many thousands of cycles and large impacts. Multibody simulation can be utilized to analyze the performance of a car door to ensure design goals are met.
In this example, a car door slam is simulated in Altair’s MotionView and MotionSolve in order to analyze stresses and locate hotspots. The model accounts for the latch, door check strap, door cushions, and seal rubber to provide a comprehensive simulation.
Understanding the Model Definition in MotionView
Overall Multibody Dynamics Model
The model consists of a vehicle’s frame and a car door attached by two hinges. Inside the car door is a latch and a check strap. The latch mechanism, picture below, consists of two cams with torsion springs. Contacts are built between the cams and the striker. The striker is attached to the vehicle frame while the latch moves with the vehicle. The model also contains a simplified check strap, shown below. The cylinders are pushed into the check strap with springs. As the door swings outward, the check strap translates past the cylinders. The forces between the cylinder and check strap add extra resistance that the passenger must overcome when opening and closing the door.
Latch (Left) and Check Strap (Right)
The car door is modeled with two cushion forces. The forces are treated as impacts dependent on door position, velocity, contact stiffness, and contact penetration. The seal around the car door is modeled using forces as well. Markers attached to the door and frame are used to calculate the distance the seal is deformed. Forces are then computed based on the distance between the markers using curves for stiffness and damping interpolated from data points.
Stiffness on the y-axis (N/mm); Marker displacement on the x-axis (mm).
There are two simulations to perform after setting up the critical interactions between all components. First, a simulation will be used to compute the necessary force to open the door. Then, a second simulation will capture the door slam where stresses and hotspots can be analyzed. In both simulations, in the first 0.5 seconds the latch releases allowing the door to open.
For the opening force estimation simulation, a sensor input sensor output controller (SISO) will be used to calculate the door opening force. The controller will use PID control to open the door 80 degrees at a constant angular velocity in 2.5 seconds. The door angle acts as the process variable and setpoint. The force applied to the door is the output which can be extracted as a curve.
After extracting a force curve from the first simulation, a second simulation will open the door using the opening force curve and then apply a slamming force. The door will be a flexible body allowing the computation of displacements, strains, and stresses.
Pre-Requisite
SOFTWARE REQUIREMENTS
MotionView (2024 or newer)
MotionSolve (2024 or newer)
MODEL FILES
Door_Slam_Model.zip (See Attachments)
Usage/Installation Instructions
MODEL SETUP & SIMULATION STEPS
Opening Force Estimation Model
- Open Opening_Force_Estimation_archive.mdl in MotionView.
- Run the analysis with an appropriate output directory.
- Open the h3d output file in HyperView to review the results.
Door Slam Model
- Open Door_Slam_Model _archive.mdl in MotionView.
- Run the analysis with an appropriate output directory.
- Open the h3d output file in HyperView to review the results.
Post-Requisite
RESULTS
After running the analysis and reviewing the results, additional data can be plotted in the HyperGraph client. The plot below depicts the required opening force vs time and opening force vs angle. The plots are similar because the door was opened at a constant angular velocity with a PID controller. The positive direction indicates a force pushing the door closed while the negative direction indicates a force pulling the door open. Initially the forces from the seal and cushions push the door open. A force against the door is required to maintain a constant velocity. Once the door is partially open, the cushions and seal no longer have an effect requiring the passenger to pull open the door.
Required Force over Time to Open the Car Door
Required Force to Open the Car Door as a Function of Angle
The required force curves are used to inform the motion of the door slam simulation. An 8 Newton force for 0.5 seconds is added to simulate the slamming force.
Passenger Force Input for the Door Slam Simulation
Door Motion and Seal Contact Forces
Latch Mechanism Contact Forces
Check Strap Contact Forces
Door Von Mises Stresses
Door Stress Hotspots
CONCLUSION
Multibody dynamics is a powerful tool allowing for the visualization of motion, forces, and stresses. In this example, we created a multibody model of a car door with a latch, check strap, cushions, and a seal. In one simulation, we used a sensor input sensor output (SISO) to find the required force to open the door. In a second simulation, we performed a door slam with a flexible body door to take into account the deformation of the door during the slam. During post-processing, we were able to review contact forces, door stresses, and identify hotspots.
AUTHORS
John Dagg, Systems Engineering Intern
Chris Fadanelli, Solution Engineer - Systems Integration
Re: Avg. within centroid distance
Hi,
This is a very commonly used formula, so I would recommend searching through academic sources if you think you need a reference. For example, I found this book referencing the measure:
https://www.sciencedirect.com/topics/computer-science/cluster-centroid
Hope this helps,
Roland
Re: Snap-through buckling results
Hi Vladimir,
you can request OLOAD output and use the applied forces computed from the pressure to plot the graph.
Hope this helps.
Alberto
CFD Simulations Made Faster Leveraging AI: A Dive Into Industrial Mixers
This article was co-written by Spiros-Foivos Mallios & Georgios Giannakouros.
Abstract
In this article, we will discuss how to speed up CFD simulations leveraging AI-Enabled Reduced-Order Modeling. More specifically we will focus on the mixing process of an industrial tank.
The goal is to enable fast predictions of the required time to achieve uniform mixing (mixing time), based on various operational and design parameters of the mixer. For this purpose, a dynamic non-linear reduced-order model (ROM) is created using Altair® romAITM
. To generate the training data, high-fidelity simulations are carried out using Altair’s Navier-Stokes CFD solver, AcuSolveTM
.
The trained ROM can estimate the transient response of mixing metrics ~ 20.000 times faster than the original CFD simulation enabling much faster optimization.
Introduction and problem statementOptimizing mixing processes in industrial tanks is essential for enhancing product quality, reducing production time, and ensuring energy efficiency across various industries, including pharmaceuticals, chemicals, and food processing.
Computational Fluid Dynamics has been long established as a powerful tool for designing and improving industrial mixing tanks, allowing engineers to simulate fluid behavior, predict performance, and make data-driven decisions to enhance mixing efficiency.
So, what is the challenge here?
When designing such systems, several operational and design parameters play a role , such as the Blade Pitch Angle, the Impeller Speed and the Viscosity of the Liquid in use. These three variables are common parameters in an industrial mixing case and significantly affect the behavior of the system.
The process of selecting the optimal combination of those parameters can become a quite tedious process, since traditionally even though CFD simulations give great accuracy, they require a considerable amount of solving time. Just to consider, for a medium sized mixing tank, more than 10 million elements are typically needed for an correct representation of the model!
This is where Reduced-Order modelling comes into place. A model can be trained to predict only the needed (of interest) metrics. In this case the ROM focuses on predicting the uniformity of the mixing over time.
WorkflowThe workflow that we follow here is quite common among many applications. Creating a ROM requires data, we can get them from either simulation results or even from real measurements (sensors), in this case it’s Simulation. Then we feed this data into romAI Director and train a romAI model that can be then used to optimize the mixing.
In other applications, it is common that the romAI model is integrated into a larger system simulation, enabling to connect multiple disciplines together and thus opens the road for Digital Twins creation.
AcuSolve Simulations and Data GenerationCFD Setup
AcuSolve is a Navier-Stokes CFD solver based on the FEM, making it ideal for mixing simulations. Its advanced modeling capabilities, along with the intuitive SimLab pre-processing interface, make it perfectly suited for capturing complex fluid behavior in industrial mixing processes.
The geometry of the model is presented in the following image. The driving force of the flow field is a pitch blade turbine impeller with 4 blades.
The mesh includes a total of more than 12 million elements and 3 million computational nodes. Additionally, local mesh refinement techniques were applied in areas requiring higher computational accuracy. A mix of tetrahedral and hexahedral elements was used to capture accurately the different flow effects on each region.
The modeling of the mixing phenomena was conducted using Frozen Flow simulations with the species method. Specifically, two separate simulations were performed.
- First, the steady-state flow field is calculated, and the Moving Reference Frame (MRF) method is used for the rotation of the impeller. With this technique, we define a volume around the rotating geometry in which we numerically specify the rotational phenomena without the physical rotation of the geometry.
- In the second simulation, the flow equations are deactivated, and only the species equation is solved involving convection and diffusion. A common example is injecting dye into water, where the dye spreads with the flow and diffusion, visualizing mixing without affecting the water’s behavior. The cylindrical volume (blue color) at the top of the mixing tank also serves as the initial condition for the species, where the maximum initial concentration is defined at the start
Overall, this technique allows us to model the transient mixing behavior within a steady-state flow field. With this setup each CFD run requires around 6h of CPU time for a total of 30s simulation time.
For the calculation of the mixing uniformity, the Coefficient of Variation metric was selected.
The coefficient of variation quantifies the relative variability of species concentrations in the fluid by expressing the standard deviation relative to the average concentration of the homogeneous mix. Full homogenization is achieved when CοV is less than 0.01, indicating a highly consistent mixture.
Design of Exploration
For the present study, three design variables were selected:
- Viscosity: Affects diffusion and flow resistance
- Impeller Speed: Drives fluid motion, creating vortices and shear layers.
- Blade Pitch Angle: Adjust flow direction and intensity, controlling turbulence and circulation.
A fractional factorial DoE was performed with a total of 13 combinations of the design variables with the levels shown on the image above.
Each combination produces a different transient response on the mixing index, the results from the AcuSolve runs are plotted bellow:
Reduced order model (ROM) generation with romAITMEach transient AcuSolve run generates hundreds of valid training points that can be used during the training process. The generated data was stored in a csv format and was fed into romAI Director.(accessible from Altair Twin ActivateTM
).
We start with the Pre-processor tab where we filter the responses to remove any numerical noise from the simulation. Next, we move on to the Builder tab where we set up the system structure and define the hyper-parameters used during the training. On this example we set the 3 corresponding Inputs and 1 Output & State Variable. (State Variable must be selected in order to create a dynamic rom model)
But how do we make sure that our romAI model is trained properly?
A first indication can be given by the Loss Curve. The Training Loss (blue line) should converge after the given amount of epochs and also the error calculated on the Test dataset (green ‘x’) should be close to the training loss.
Moreover, a dynamic ROM model should be tested by performing a time simulation on completely unfamiliar combination of inputs, to asses the good generalization capability of the ROM generated.
To quickly simulate it, we leverage the Post-Processor tab inside the romAI Director GUI. Alternatively, one can deploy the model in TwinActivate, or on your choice in 3rd party platform that supports the FMI standard or can run C Code.
To validate it, we run 2 more AcuSolve simulations, with unfamiliar combination and values on the design variables. On the Table below are the results of romAI related to the time required to complete the mixing.
The mixing time is calculated based on where the Coefficient of Variation (CoV) reaches the threshold (target) of 0.01, indicating a near homogeneous fluid.
Below are the transient responses of the CoV tested on the 2 unfamiliar cases (No 14 & 15).
Conclusions
- Relatively few AcuSolve transient simulations are needed compared to traditional ML approaches.
- Gain Factor > 20.000 enabling Real Time applications & Optimization
- ROM Able to predict the dynamic response, not just the final steady state value
- Very good generalization capabilities making the model trustworthy on new predictions
Controlling Rocket Fairing Separation in Zero Gravity
Controlling Rocket Fairing Separation in Zero Gravity: Challenges of Cable Retraction and Trajectory Stability. Ensuring Safe Separation Without Compromising Mission Integrity
PREFACEFairing separation in space requires precise control to avoid interference with a spacecraft’s trajectory. Physical testing of these events in space conditions is costly and impractical. Multibody dynamics simulation offers an efficient alternative to study and optimize the separation process in zero gravity. Software such as Altair’s MotionSolve and Inspire Motion enables engineers to model complex systems like fairing separation and evaluate the impact of various forces and constraints. Through these simulations, engineers can refine designs, ensuring the safe and controlled separation of the fairing without compromising mission success.
INTRODUCTIONIn aerospace applications, the controlled separation of components, such as rocket fairings, plays a critical role in ensuring the success of space missions. Fairings protect delicate payloads during launch and must be separated cleanly once the rocket reaches space. However, managing this separation in a zero-gravity environment presents unique challenges. Forces such as gravity, friction, and atmospheric drag, which play significant roles during launch, are absent in space. This demands careful planning and precise control mechanisms to ensure that detached components do not interfere with the rocket’s trajectory or the payload's mission.
This article explores the simulation of fairing separation in a zero-gravity environment, focusing on the dynamics of detachment. The simulation, conducted using Motionsolve, tries to replicate real-world conditions where the fairing separates cleanly but in certain cases is pulled back by cables, deviating from the intended trajectory.
SOFTWARE REQUIREMENTSAltair MotionView (2023 or newer)
Altair MotionSolve (2023 or newer)
MODEL FILESFairing_Separation_Model.zip (See Attachments)
Understanding the Model Definition in MotionViewThis model setup assumes a level of familiarity with Motionview/Motionsolve. A motion-ready model called Fairing_Separation_Model.mdl is available for reference in the attached zip file.
The simulation model represents half of the rocket's geometry, focusing on one of the fairings. The fairing is initially secured to the base via links and brackets held in place by bolts. In real-world scenarios, these bolts are disengaged using an explosive bolt mechanism, which is not modeled in the current simulation. Instead, the study focuses on the sequence that follows bolt disengagement: an actuator mechanism between the base and the fairing activates, pushing the fairing away from the rocket along a predefined trajectory. Additionally, cables remain attached between the fairing and the base, and their effect on the fairing’s movement is explored. The multibody simulation examines how these cables, when not detached, influence the fairing's trajectory and overall dynamics.
MODEL SETUPBodies:
- The model contains a fairing, two actuation mechanisms, base of the fairing (with bolts held to the fairing) and two dummy cables.
- The dummy cables are simple rigid link of bodies constrained with spherical/ball joints to simulate the cable-like behavior.
Joints:
- The actuator mechanism is constrained with translational joints for simplicity
- All the internal joints for the dummy cable bodies are spherical/ball joints, so that we can study its effects on the fairing trajectory when freely floating in space.
Motions:
- Two motions are enabled for the translational joints for the actuator mechanisms, as s STEP function expression.
Contacts:
- Contacts are created between the actuator mechanism and the base of the fairing. Thus, once the motion starts, the reaction from the contact force pushes the fairing away.
- Another contact is defined near the hinge/bolt support of fairing, which pre-determines the trajectory once the separation is initiated.
Hinge/Bolt support for Fairing and Base
Sensors:
- There is also a sensor created in the model, so that once the force in the cable joints exceeds a certain value, the joint is deactivated, and the cable is detached from the fairing/base.
- The deactivation using sensor is achieved with the template command.
The simulation initiates the actuation mechanism, causing a reaction force to push the fairing outwards. A sensor detects the force in the ball joint of the dummy cables, and once the sensor is triggered, the joint is deactivated, letting one of the cables free. Thus another cable pulls the fairing back, deviating it from its predetermined trajectory.
All the mentioned steps are achieved with a simple template script shown below.
- Transient simulation for 6 seconds, to initiate the motion using STEP function and begin the fairing separation.
- Deactivating the force sensor, once the sensor gets triggered.
- Deactivate one of the ball joints of dummy cables to detach it from the base.
- Transient simulation for further 14 seconds, to understand the trajectory of the fairing.
The following animations show the effect of cable not detaching on the fairing separation trajectory
Another iteration is simulated as well and shown in the following animation.
Perfect trajectory with clean detached cables (Fairing_model_Iteration_1.zip)
CONCLUSIONThe simulation of fairing separation in zero gravity using Altair MotionSolve and MotionView offers valuable insights into the challenges associated with cable retraction and trajectory stability. By replicating a real-world detachment scenario, this study demonstrates how even a small anomaly, such as an undetached cable, can significantly alter the fairing’s trajectory. The use of sensors to detect and deactivate forces at specific joints adds realism to the simulation, allowing engineers to better understand the dynamics of fairing separation in space conditions. The results show that even with precise actuation mechanisms, the presence of cables requires careful consideration to avoid interference with the spacecraft’s path.
These findings underscore the importance of simulation-driven design in aerospace engineering, particularly for events like fairing separation where physical testing is impractical. By using multibody dynamics software, engineers can optimize separation processes and reduce the risks of mission failure. Future studies can expand on this by incorporating more complex cable behaviors, including elasticity and non-linear forces, to further enhance the accuracy and robustness of fairing separation mechanisms.
AUTHORVishvam Naik, Solution Engineer - Systems Integration