CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > Siemens > STAR-CCM+

Boundary conditions for portal interface

Register Blogs Members List Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   March 29, 2017, 03:19
Default Boundary conditions for portal interface
  #1
New Member
 
Yanyan Huang
Join Date: Dec 2012
Posts: 9
Rep Power: 13
yanyanh is on a distinguished road
Hi all,

I'm currently doing a car exterior CFD simulation (StarCCM+) and would like to extract the air from one location and reinsert it into another location, kinda like a portal. The idea is to find the best place to flush the waste air of the engine bay.

My question here is, how to define the boundaries for this case. I did some trials with a pressure outlet at one site and couple it to a mass flow inlet at the other side by matching pressures and mass flow. In a simple model it worked, but in the full scale car model I'm not able to get convergence and the two mass flow does not match up.

Does anybody has an idea how I can do this "teleporting" of air (two-way since the mass flow need to match the pressure drop)?

Thank you so much for your help!
yanyanh
yanyanh is offline   Reply With Quote

Old   March 30, 2017, 15:32
Default
  #2
Senior Member
 
Join Date: Nov 2010
Location: USA
Posts: 1,232
Rep Power: 24
me3840 is on a distinguished road
I can see a couple ways to do this:

1. Dumb and simple method is to just make a pipe between the two points (even if it wildly goes through other geometry) and set the walls to be slipping.

2. Create similar coordinate systems on each interface side. Create a macro that will use data mappers to iteratively update velocity and pressure back and forth. Run the job with the macro.

3. Write a similar procedure to 2 using user code. Best solution, most effort required.
me3840 is offline   Reply With Quote

Old   March 31, 2017, 03:35
Default
  #3
New Member
 
Yanyan Huang
Join Date: Dec 2012
Posts: 9
Rep Power: 13
yanyanh is on a distinguished road
Quote:
Originally Posted by me3840 View Post
I can see a couple ways to do this:

1. Dumb and simple method is to just make a pipe between the two points (even if it wildly goes through other geometry) and set the walls to be slipping.

2. Create similar coordinate systems on each interface side. Create a macro that will use data mappers to iteratively update velocity and pressure back and forth. Run the job with the macro.

3. Write a similar procedure to 2 using user code. Best solution, most effort required.
Thank you very much for the reply.

1. I did this draw-a-pipe way already to compare with the interface/boundary method for "validation". I haven't set the walls of the pipe to non-slip, that I will correct to get closer to the portal method.

2. and 3. What kind of interface are you talking about? Since these two portal boundaries are neither close to each other for in-place interface, nor have the same area for a periodic interface. I'm using a mass flow inlet to adjust to the different surface areas.

Thank you for the help!
yanyanh is offline   Reply With Quote

Reply

Tags
bounadry condition, car aerodynamics, interface, star ccm+

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Basic Nozzle-Expander Design karmavatar CFX 20 March 20, 2016 08:44
Problem with SIMPLEC-like finite volume channel flow boundary conditions ghobold Main CFD Forum 3 June 15, 2015 11:14
An error has occurred in cfx5solve: volo87 CFX 5 June 14, 2013 17:44
Concentric tube heat exchanger (Air-Water) Young CFX 5 October 6, 2008 23:17
Replace periodic by inlet-outlet pair lego CFX 3 November 5, 2002 20:09


All times are GMT -4. The time now is 23:56.