[Solved] Struggling with UAV Tutorial

[Syres]

Hi,

I hope someone can please give me some pointers, I'm really struggling making progress with the CFD Tutorial 4 - External Aerodynamics of a UAV https://github.com/opensimsa/opensim/tr ... n/CFD/UAV2

I've tried following the PDF to manually configure the mesh and the CFD properties and when that failed I tried the three macros from https://github.com/opensimsa/opensim/tr ... s/CFD/UAV2 to eliminate any human errors on my behalf.

I didn't see any errors when running the 3 macros and they all appeared to carry out the tasks required.

The meshing and solver output from Report View are attached with relevant filenames. I stopped the solver manually because I noticed that there was only w, k, p in the legend box and was missing Ux, Uy and Uz so I have assumed there must be something wrong.

As a sidenote I also noticed the Solver Case Edit button produces the following error but I'm not sure it's related:

Code: Select all

Traceback (most recent call last):
  File "C:\Users\JPS\AppData\Roaming\FreeCAD\Mod\CfdOF\_TaskPanelCfdSolverControl.py", line 158, in editSolverInputFile
    solverDirectory = os.path.join(self.solver_object.working_dir, self.solver_object.InputCaseName)
AttributeError: 'FeaturePython' object has no attribute 'working_dir'

Any help would really be appreciated,
Thanks
John

Running with the latest CfdOF WB
OS: Windows 7
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.14495 (Git)
Build type: Release
Branch: master
Hash: c717d1121d888fe6cfbd8971b5f59311a34b37bc
Python version: 2.7.14
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.2.0
Locale: English/UnitedKingdom (en_GB)

[thschrader]

I've tried following the PDF to manually configure the mesh and the CFD properties and when that failed..

Use boolean-slice instead of XOR when subtracting the shell vom cube.
Keep in mind that in the tutorial the refinement parameters are given
in m, the input dialog needs mm (on my machine...)

[Syres]

Thanks for the feedback but the PDF and macros were updated with the Slice instead of XOR by Oliver's team 8 days ago so I'm using all the latest info and the macros have the correct sizes in millimetres (e.g. 6000 mm for the height of the Cube) so I'm fairly confident that's OK. It 'feels' like a mesh issue is the root cause but I'm interested to know if Oliver (or anyone else for that matter) with the up-to-date workbench can get it to work just using the macros as is.

Cheers
John

[oliveroxtoby]

Hi,

I hope someone can please give me some pointers, I'm really struggling making progress with the CFD Tutorial 4 - External Aerodynamics of a UAV https://github.com/opensimsa/opensim/tr ... n/CFD/UAV2

I've tried following the PDF to manually configure the mesh and the CFD properties and when that failed I tried the three macros from https://github.com/opensimsa/opensim/tr ... s/CFD/UAV2 to eliminate any human errors on my behalf.

I didn't see any errors when running the 3 macros and they all appeared to carry out the tasks required.

The meshing and solver output from Report View are attached with relevant filenames. I stopped the solver manually because I noticed that there was only w, k, p in the legend box and was missing Ux, Uy and Uz so I have assumed there must be something wrong.

From the output it looks to me as if you might need to update your cfMesh (from the preferences page) - we made a small change to our fork a month or so ago that looks to be absent.

As a sidenote I also noticed the Solver Case Edit button produces the following error but I'm not sure it's related:

Code: Select all

Traceback (most recent call last):
  File "C:\Users\JPS\AppData\Roaming\FreeCAD\Mod\CfdOF\_TaskPanelCfdSolverControl.py", line 158, in editSolverInputFile
    solverDirectory = os.path.join(self.solver_object.working_dir, self.solver_object.InputCaseName)
AttributeError: 'FeaturePython' object has no attribute 'working_dir'

Thanks for the report - fixed.

[Syres]

Updated CfdOF WB which has fixed the case Edit button, thank you.

Updated cfmesh with the 4th July 2018 version and the case is now solving as expected, thanks again.

Appreciate the time and effort,

Cheers
John