Jump to content

ydigit

Moderators
  • Content Count

    384
  • Joined

  • Last visited

  • Days Won

    14

ydigit last won the day on June 6

ydigit had the most liked content!

2 Followers

About ydigit

  • Rank
    Super User

Profile Information

  • Gender
    Not Telling
  • Country
    Germany
  • Are you University user?
    No

Recent Profile Visitors

2461 profile views
  1. You can follow the details for "Time History Points" from the tutorial: ACU-3000: Enclosed Hot Cylinder: Natural Convection
  2. Even RADIOSS SPH might be able to solve this.
  3. 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.
  4. 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
  5. could you try opening AcuProbe directly without AcuConsole? See screenshot: Also use "clear settings" in AcuConsole to see if it solves the issue.
  6. 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
  7. 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
  8. 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!
  9. 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.
  10. The phenomenon you are trying to simulate requires a compressible solver. AcuSolve currently does not have a compressible solver. You could try with Altair RADIOSS, that is also used for airbag simulations.
  11. Generally I try to avoid elements with small angles <10°. Also check for any really small elements (cannot give an absolute value though). Say you average element size is ~10, then search for elements <1 to see which are smallest (sliver) elements. These are typically going to create big trouble for boundary layer meshing. In a way both are related issues. Small angles lead to small elements.
  12. If the script had a problem, the solver would not have started. It would have ended in AcuPrep stage.
  13. Need more information to know why this error is coming up. Is it possible to send .inp and .log files?
  14. I guess that Project Solutions is not yet implemented for HM-CFD 2017.3. What issue did you face with restarting from the steady state case? An alternative would be to export velcoity and pressure nodal value from steady case (use AcuTrans or AcuOut). The files can be read as NIC (Nodal Initial Condition) files in HM2017.3 See screenshot.
  15. You probably need to adapt the path to your particular installation. Could you post a screenshot of the path you have in your Solver launch path.
×
×
  • Create New...