Best Of
Re: Monarch Classic Will Not Open
I had a similar issue you can try this to see if it helps:
1. Open Control Panel
2. Click on Programs
3. Click on Program and Features
4. Find Microsoft Access database engine
5. Right click and select Repair
Matt G
Re: implicit modelling
Sir, will I be able to use Inspire 2023 on my laptop which has Amd ryzen 5, 16 GB ram, and an integrated Radeon graphics card?
I'm attaching a picture of the system requirements for Inspire 2023:
Your question really depends on the specs of your CPU/GPU and the size/complexity of the models you want to work with. While the recommended ram is 32 GB, you still have more than the minimum required of 8 GB.
It should also be noted that using Inspire Implicit Modelling has it's own recommended specs where an Nvidia GPU is recommended. AMD GPUs may still work but have not yet been qualified for implicit modelling.
nalbert
Re: implicit modelling
Hi Narain,
The Implicit Modelling ribbon is a new addition to Inspire Version 2023, is that the version you are using? If you are using 2023, try going View -> Ribbons -> Make sure 'Implicit Modelling' is selected. Hope that helps!
nalbert
Re: implicit modelling
Sir, I was able to install the Altair inspire 2023 from the link you provided. Thanks, sir.
Glad I could help!
nalbert
Re: implicit modelling
Hi sir,
I installed the Altair Inspire 2022.3 version from the provided educational license. How to get access to the Altair Inspire 2023 version. Kindly let me know sir.
I am not very familiar with the educational licenses, could you go to this AltairOne link (https://altairone.com/Marketplace?queryText=inspire&tab=Download&app=Inspire) and download the 2023 version and see if your educational license works for that version?
nalbert
Re: How to reduce penetration
Hi Yoseob,
Full vehicle contact models are quite complex, especially tracked models, and can lead to this behaviour that you are currently seeing. The contact definition as well as the CAD are critical elements to ensuring a smooth and accurate simulation. If you haven't already, I would review the MotionSolve documentation for 3D contacts best practices here:
Contact Penetration
Incremental changes to the contact stiffness and stiffness exponent is a good starting point. Since you are still seeing penetration, then another area to investigate would be the quality of the CAD used for the obstacles and tracks. If the mesh sizing is very coarse, then there is a higher probability of penetration to occur. I believe this is what is occurring in the third picture. Try a finer mesh for the 3D contact entities either in HyperMesh or change the mesh coarseness for contacts in the Entity Editor for the Graphics body in MotionView:
Additionally, I would simplify the geometry on the bottom of the track as it looks like there is a hole in it. By making that flat, you will improve contact and not reduce the ability to traverse the block.
The Advanced options will help to improve the simulation as well. By enabling "Find precise contact event", once the solver detects contact it will rewind slightly to make sure that contact did not occur a split second earlier. This can help correct poor integration time step settings. As well, "Change simulation max step size" will allow you to set a much smaller step size when contact is detected, so if there is a portion of the simulation before contact is made, you can set a coarse step size initially that will be corrected when contact begins. This can save simulation time potentially. Lastly, you can change where the contact force is computed, either at the center of the mesh element or at the nodes. Changing the location may improve contact detection, but it may effect the force orientation during contact.
The documentation for these options can be found easily here: https://help.altair.com/hwsolvers/ms/topics/solvers/ms/best_practices_for_modeling_3d_contacts_ms.htm?zoom_highlight=contact
Reaction Force
It is typical to see higher reaction forces when dealing with completely rigid models that also experience 3D rigid contact. If the contact forces are extremely sharp, then that will propagate into your roller bearings. I would look into the damping properties for your contacts to see if you can smoothen out the impact using the damping coefficients. The high reaction forces you are seeing is likely due to the less than ideal contact behaviour you have highlighted in the pictures. This small obstacle contact you are trying to simulate is not ideal, and you may want to explore allowing more penetration between the track and the obstacle to help smoothen out this simulation as well.
I would not advise connecting your ground surface to Ground through a bushing, as this is merely covering up an issue from the contact approach in the model.
Hope this helps!
Adam Reid
Hello Adam,
Thank you for your detail advices.
I already read linked document several times, it is very nice and valuable document. thank you.
I am not sure my ground should be set as rigid because the ground is thick steel plate seated on concrete (not bonded). And now I understand the contact event option with your explanation. I will try again with your advices.
Thank you and Happy New Year, Adam
Re: Rotor mechanical set - how to define position at time t=0s
Hello Melih,
The rotor position at "startup" in the magnetic model depends on the BEMF analysis and 7.5° is the zero crossing point of the phase one voltage [see the example "Brushless IPM motor (embedded magnes)" page 71 Overview document - Motor Performance at constant speed]; therefore, it is necessary to align the rotor position to control the gamma angle.
This is normally done by FluxMotor, and there is a macro in Flux to help the user, but it is sufficient to do a BEMF analysis to find it.
However, if you take the losses from the FluxMotor model, you don't need to consider the position in the thermal models because the temperatures are not related to the position in Flux.
Best regards,
Letizia
HyperMesh CFD: Known Issues
List of known issues that were discovered after release. (Note: This article will continuously be updated when issues are reported)
HyperMesh CFD 2023.0 known issues:
Geometry - Meshing
-
Manage tool: Manage tool in Simulation ribbon does not list meshing or runs residing in same folder as hmcfd file.
Workaround: You have to submit meshing or AcuSolve job to review the list.
-
Right click -->Reverse displayed for Geometry and FE geometry data is not working properly. Works fine for Lite and Discrete data.
-
Busy cursor: Busy cursor does not come up for few tools like CAD Wrap.
Work around: Moving mouse cursor to browser or ribbon area may bring back busy cursor. Wait till you see message at bottom like "Wrap Mesh End"
-
Import Solver decks: Importing with All(*.*) filter in dialog causes import failure randomly.
Work around: Select file filter first and then select files in the dialog
-
CAD Wrap – higher overlap tolerance value:
High value compared to model dimension values of overlap tolerance can distort model.
Work around: Define very small value for overlap tolerance
-
CAD Wrap - Quality cleanup option can distort shape.
Work around: Turn off Quality cleanup option, use any repair tools to improve quality separately.
Caser Setup (Aerodynamics and Aeroacoustics):
-
Section cut inclination is not reset on selecting new base plane. Multiple transformations can also lead to an incorrect normal.
-
Importing template file with overset fan volumes can throw a warning without any parts mentioned in the dialog.
-
MRF fan parts are not written to the xml and stl files correctly.
-
Aerodynamic coefficients plot background is black and cannot be modified.
-
Resizing belts does not result in the correct graphics rendering or collision calculations.
Post Processing:
-
Plots - Rake/Intersection: AcuSolve derived data fields: Known to cause application to crash when fields are read in from AcuSolve direct reader, for Derived or Miscellaneous fields.
-
Signal Processing - Probe: The window overlap must be defined as the integer value of sample points of the overlapping size(i.e. block size= 1024, window overlap=512 for 50% overlap).
-
Signal Processing - Surface - Integration: OASPL needs to be computed using p**2, not SPL, use Calculate toolset to recompute from SPL and then integrate.
-
HWCFDReport Automation - GSP - Surface: Definitions for view, colormap and background_color are not honored. The user is requested to manually Open/Import the resulting .gsph5 file into
Re: Change medium properties in Altair Activate Modelica Thermal
Hi Tomas,
Custom media can be declared using the Medium block and referencing it in all the thermal blocks.
Look at the example I've attached and notice the block called Custom Medium and how all the thermal blocks reference it with "FromModelica('/Custom Medium')". If you play around with any medium parameter, you'll see changes in the simulation.
Hope this helps.
Rafael
Re: How do I configure regional date formats?
Hi Daniel,
The SAS language includes a number of options to control the layout of dates, but I'm not sure whether your problem relates to MS Office, Altair SLC, or the way you are importing the Excel data.
Anyway, the SAS national options are:
- LOCALE=en_GB (also en_US, fr_FR, fr_BE, fr_CH, de_DE, de_CH, hu_HU), which controls language, dates, currency, etc.
- DATESTYLE=DMY (also MDY, YMD, LOCALE), which controls only reading and writing dates.
- You appear to be using a default of DDMMYY8.
- Others include MMDDYYw. YYMMDDw., DATEw., NLDATEw., MONYYw., etc., where w=width.