Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by ydigit

  1. ydigit

    Blade Failure

    AcuSolve of NanoFluidX are just CFD solvers and what you probably need is a fatigue solver for your use case. You could get pressure on blades with AcuSolve and map these pressure values to OptiStruct and use HyperLife. https://www.altair.com/hyperlife/
  2. If you can, please upload the .stmod file for VWT. In HyperView go the folder that has the vwtAnalysis.Log.1 file and ACUSIM folder. Use the same .Log file for both Load Model and Load Results, like the screenshot below. Note that if ACUSIM.DIR is not present in the same folder, only .Log file will not be read by HyperView. .
  3. You could directly open the .Log file in HyperView or AcuFieldView in the latest versions (with hotfix). Also, please make sure that the surface mesh that you imported in VWT was properly scaled in Meters in HyperMesh. I never use the scaling in VWT. Please report if scaling the model in HM solves the issue.
  4. One easy way to the frontal area calculation is import the surface mesh (.Nas or Bdf format) in Virtual Wind Tunnel. It calculates the frontal area automatically.
  5. Why are you using the pressure offset in the first case? I would remove it, unless you know why you introducing it. Also the current value of 10135 seems really odd (assuming you meant it 101325 = 1bar?). Keep turbulence (default SA model) on, as that generally helps with convergence. Mesh motion is needed when there is some explicit movement of a part (say FSI or rotating fan or flexible body). In your case I do not see a reason to enable mesh motion.
  6. oops, I understood the question incorrectly. The default when creating a new inflow is 0.03. So it is good to assume that 0.05 would be a good input in your case. Also if you would like to verify this, you can open the .INP file that HM will generate after export in a text editor. Hope this helps.
  7. There are several issues with your setup. Why do you have a mesh motion with ALE? I guess that was unintentional. Also any reason for the pressure offset? Try running with these two adjustments (no mesh motion and no pressure offset) and report if it works...
  8. Here is the screenshot from the Altair_AcuSolve_2019.1_Training_Manual.pdf Hope this clarifies.
  9. AcuSolve results can be visualized in HyperView or AcuFieldView. HyperView is the easier option for most users (especially if you have used HV for some other solver). HV is a generic post-processor, so only basic CFD post processing is possible. However it covers the needs of many users. AcuFieldVIew is the expert tool for CFD, with advanced features for CFD post-processing. As with expert tools, it takes time to get used to it. So if you are new CFD user HV might be a good first choice. HyperView: HV can read results in following formats: 1.AcuSolve .Log file with ACUSIM.DIR in the same run folder. 2. Convert AcuSolve results to H3D a. AcuConsole > Tools > AcuOut. 2b. AcuOut is using the command acuTrans to convert the files. This command can be executed directly from the AcuSolve Cmd Prompt . AcuFieldView: Similar to above process for HyperIvew, you can export files to ..FV format as well.
  10. Virtual Wind Tunnel is the easiest way to get the frontal area. Load the mesh (scaled in meters) als .NAS (to be precise Nastran Fluent Format from HyperMesh) into VWT.
  11. Seeds that one defines in AFV are just, points through which streamlines pass. So there is no way to restrict them (AFAIK). What you could try is creating a "coordinate plane" and then instead of contours, show the vectors. Vectors can be limited to a plane and there is also an option to animate these vectors. The downside maybe that you cannot save these vector animations directly. Two options: - keyframe animations (but costs time) or . just use powerpoint > Insert > screenrecording.
  12. Could you post you .inp file? If not, try: - set Stagnation pressure at inlet. - setup Turbulent intensity, velocitcy and length scale, depending upon your geometry.
  13. Could you please describe the exact setup? What data is available to you? Inlet, Outlet, Mass Flux, Pressure, Velocity? Generally MassFlux at inlet or volume flow rate or velocity at inlet and pressure at outlet is the stable configuration. This is also the default or so called SBD = Simple Boundary Condition in AcuSolve. MassFlux at outlet is possible under adavanced boudnary conditions.
  14. HyperMesh Parasolid export is not always compatible with AcuConsole. Have you tried to setup the case in HyperMesh. With HyperMesh 2019 or 2019.1 you should be able to do most setups in HyperMesh. The latest release also has new tutorials based on HyperMesh interface.
  15. We are porting all features from AcuConsole to HyperMesh. Right now AcuConsole will be the only option for co-simulation with MotionSolve.
  16. You can follow the details for "Time History Points" from the tutorial: ACU-3000: Enclosed Hot Cylinder: Natural Convection
  17. Even RADIOSS SPH might be able to solve this.
  18. The flow from a shower is probably better solved with NanoFluidX than with AcuSolve. AcuSolve is an Eulerian code and in my opinion, a particle based code is better suited for this application.
  19. The virtual wind tunnel you show in your screenshot if very small for any reasonable aerodynamics results. You might get colorful picture, but probably no useful interpretation. Wind tunnel dimensions: o 5 car lengths ahead of the car o 10 car lengths behind the car o 5 car widths on each side of the car o 10 car heights above the car o i.e., wind tunnel dimensions LWT x WWT x HWT = 16Lc x 11Wc x 11Hc. o The mesh farther away from the car will be coarse and increasing the wind tunnel domain would not affect the element count too much but it would still affect the B.Cs if they are too close to the car.  Boundary Layer details o First layer height will depend on the freestream velocity to obtain a maximum y+<100. A first guess would be 0.2mm<y<0.5mm. Ideally y+max<30. o For some applications y+max<100 should still give good results o growth rate of 1.3 o number of layers 5 o all tets in boundary layers
  20. could you try opening AcuProbe directly without AcuConsole? See screenshot: Also use "clear settings" in AcuConsole to see if it solves the issue.
  21. The details of assigning Moving Reference Frame to the inner volume are described in ACU-5000: Blower - Steady (Rotating Frame) You will assign rotational velocity to the inner volume (Reference Frame) and the surfaces (of blades) in the inner volume
  22. Could you post your .inp and .Log file? Your case might be best dealt with Altair Support. Please submit a ticket through: https://connect.altair.com/CP/home.html
  23. What is the problem with Jacobians ? what kind of values are there? If there are no mesh intersections generally AcuSolve will be able to solve. Accuracy might suffer due to some bad elements. It seems there are multiple issues with your setup. Do you have two volumes, one for the moving reference frame and one for the rest of the fluid? Also do you have an interface surface between these two volume? As a start I would recommend working through tutorials, that are available in your installation. Check \HW2018\acusolve\win64\doc folder ACU-5000: Blower - Steady (Rotating Frame) ACU-5001: Blower - Transient (Sliding Mesh) Missing nodal BCs for fluid node is not good. Fluid nodes at any boundary should have BCs. Also "wall" at outlet does not make sense. The outlet surface should have outlet BC!
  24. Did NIC method work for you? Based on the log file, it seems that command was not correct. It seems an issue with path. What command did you try to run and please copy the content of your .rst file.
  • Create New...