How to best handle quilts made in Pro/E

BigBaboo · September 30, 2011, 11:00

I have some complex geometry made with surfacing in Pro/E. When I try to import the file into CFDesign using the Granite configuration I get the standard error "PTC Granite kernel cannot process the quilt geometry". When I try the Pro/Mechanica configuration I get the standard tesselation errors.

I've tried exporting the files as NEU & STEP and then re-importing them but still end up with the same errors, sometimes even more.

How are we supposed to deal with geometry that is not simply prismatic?

yoavmatia · October 7, 2011, 03:10

he Big

well i used to be a Pro/E user not to long ago until i thanfully switched back to SW in my new work place ...

in any case what i found useful when i encountered your problem in the past was (and i emphesis this) -
1. save the file as a parasolid or STEP.
2. open the file with SolidWorks (most work places some sort of version, so that they can open or manipulate files from contractors that use SW without a problem)
3. save the file again this time useing SW as an X_T (parasolid)
4. then opening the in CFDesign

i know it is an ugly work-around... but it worked and its the best i can offer

BigBaboo · October 7, 2011, 09:18

Thanx yoavmatia. I don't have a SW license available unfortunately. (since I've always used Pro/E I find myself on the other side of the SW/Pro-E fence)

I did get a response from a tech that suggested this using a shrinkwrap to smooth out any weird surfaces or to make sure when I export the STEP to only export 'solids' and no surfaces. I haven't tried this yet. And unfortunately I don't have shrinkwrap in my base package.

He also said there is new technology in CFDesign 2012 called Fusion that helps with this sort of problem. I don't have that either, though.

derrek.cooper · October 15, 2011, 22:53

Hello Tony.. If you have access to Autodesk Simulation CFD 2012(former CFdesign), Fusion installs automatically. Sounds liek the issue is that you need to create solid geometry from the surfaces

BigBaboo · October 17, 2011, 08:50

Hey Derrek. I believe all the surfaces have been used to create solid geometry. There were some cosmetic features that were suppressed, but the error still remains. I don't see any quilts visible at all in the model.

Unfortunately we cannot afford maintenance at the moment so we are stuck on 2010/2011. I think I've had the same issue before and have sent it in to BRNI for help and they have fixed the problem, but I don't really know how they did it.

swetkyz · November 5, 2011, 10:04

CFdesign can process quilt geometries using the "mechanica" kernel. It is an option when you start CFdesign from Pro/E. I used it extensively for 2-D modeling. I can't speak for 3-D modeling, but in 2-D, using this option means that Pro/E meshes your model instead of CFdesign. I found that this configuration was quite touchy in the Spring 2011 version, but it worked. Most of the time in 3-D, I have simply had to make my own 'clean' geometry for CFdesign.

-Zachariah

BigBaboo · November 7, 2011, 08:17

Zachariah,
I am aware of the Mechanica option as I stated in my original post. Unfortunately, I get errors with that method too. I would think that using the Mechanica option would be the most reliable but that doesn't seem to be the case.

swetkyz · November 7, 2011, 09:28

Quote:

Originally Posted by BigBaboo

Zachariah,
I am aware of the Mechanica option as I stated in my original post. Unfortunately, I get errors with that method too. I would think that using the Mechanica option would be the most reliable but that doesn't seem to be the case.

I see. Occasionally, ramping up the model accuracy in Pro/E helped me get geometry to mesh. If you want a science project, you could probably use OpenFOAM with snappyHexMesh and an STL file. The learning curve is a bit of a challenge through. Best of luck.

yoavmatia · November 7, 2011, 11:47

Hi Big

well, like i said as the first reply to the thread.

i used to be a Pro/E for 2.5 years, thanfully switched back to SW

i know your on the other side ot the Pro/E VS. SW fence.
however, since i see you are still stuck with the same problem!?!

i would strongly recomend you take the the solution/work-around i used to do when ever i stumbled to your exact problem... say what you may - it works.
(see my initial reply up in the begining of the thread)

Mithrandir · April 4, 2012, 14:44

interesting...

I have been doing a lot of external flows extensively using surfaces... (wings, fuselages and tails)...
the Pro/E model has a lot of surfaces used for construction.. on hidden layers.. and I get the same warning when I start up... but none of the domain that gets meshed is defined by a surface... so I click "OK" and carry on.... (Merged surfaces are used to cut [via solidify/cut] from the domain)

can you post any screen snaps?

September 30, 2011, 11:00	How to best handle quilts made in Pro/E	#1
BigBaboo New Member Tony DelNegro Join Date: Jul 2011 Posts: 10 Rep Power: 14	I have some complex geometry made with surfacing in Pro/E. When I try to import the file into CFDesign using the Granite configuration I get the standard error "PTC Granite kernel cannot process the quilt geometry". When I try the Pro/Mechanica configuration I get the standard tesselation errors. I've tried exporting the files as NEU & STEP and then re-importing them but still end up with the same errors, sometimes even more. How are we supposed to deal with geometry that is not simply prismatic?

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Pro/E to cfx attach issues.	Jmac	ANSYS Meshing & Geometry	1	July 24, 2011 16:03
problem when converting mesh (made by ICEM) using fluentMeshToFoam	Forrest_Lei	OpenFOAM	11	October 16, 2009 06:28
unable to handle model wwith handle "-1" in CFX-Pre	info_bahaider	CFX	3	August 19, 2009 19:27
pro/e to gambit	Ana Raquel Rosado	FLUENT	1	October 12, 2006 07:46
a way to make lots of money quick and easy no lies	Dob	Main CFD Forum	0	October 10, 2006 16:45

October 7, 2011, 03:10		#2
yoavmatia New Member yoav Join Date: Mar 2011 Posts: 7 Rep Power: 15	he Big well i used to be a Pro/E user not to long ago until i thanfully switched back to SW in my new work place ... in any case what i found useful when i encountered your problem in the past was (and i emphesis this) - 1. save the file as a parasolid or STEP. 2. open the file with SolidWorks (most work places some sort of version, so that they can open or manipulate files from contractors that use SW without a problem) 3. save the file again this time useing SW as an X_T (parasolid) 4. then opening the in CFDesign i know it is an ugly work-around... but it worked and its the best i can offer

October 7, 2011, 09:18		#3
BigBaboo New Member Tony DelNegro Join Date: Jul 2011 Posts: 10 Rep Power: 14	Thanx yoavmatia. I don't have a SW license available unfortunately. (since I've always used Pro/E I find myself on the other side of the SW/Pro-E fence) I did get a response from a tech that suggested this using a shrinkwrap to smooth out any weird surfaces or to make sure when I export the STEP to only export 'solids' and no surfaces. I haven't tried this yet. And unfortunately I don't have shrinkwrap in my base package. He also said there is new technology in CFDesign 2012 called Fusion that helps with this sort of problem. I don't have that either, though.

October 15, 2011, 22:53		#4
derrek.cooper New Member Derrek Cooper Join Date: Mar 2009 Location: Philadelphia, PA USA Posts: 19 Rep Power: 17	Hello Tony.. If you have access to Autodesk Simulation CFD 2012(former CFdesign), Fusion installs automatically. Sounds liek the issue is that you need to create solid geometry from the surfaces

October 17, 2011, 08:50		#5
BigBaboo New Member Tony DelNegro Join Date: Jul 2011 Posts: 10 Rep Power: 14	Hey Derrek. I believe all the surfaces have been used to create solid geometry. There were some cosmetic features that were suppressed, but the error still remains. I don't see any quilts visible at all in the model. Unfortunately we cannot afford maintenance at the moment so we are stuck on 2010/2011. I think I've had the same issue before and have sent it in to BRNI for help and they have fixed the problem, but I don't really know how they did it.

November 5, 2011, 10:04		#6
swetkyz Member Zachariah Swetky Join Date: Aug 2011 Posts: 36 Rep Power: 14	CFdesign can process quilt geometries using the "mechanica" kernel. It is an option when you start CFdesign from Pro/E. I used it extensively for 2-D modeling. I can't speak for 3-D modeling, but in 2-D, using this option means that Pro/E meshes your model instead of CFdesign. I found that this configuration was quite touchy in the Spring 2011 version, but it worked. Most of the time in 3-D, I have simply had to make my own 'clean' geometry for CFdesign. -Zachariah

November 7, 2011, 08:17		#7
BigBaboo New Member Tony DelNegro Join Date: Jul 2011 Posts: 10 Rep Power: 14	Zachariah, I am aware of the Mechanica option as I stated in my original post. Unfortunately, I get errors with that method too. I would think that using the Mechanica option would be the most reliable but that doesn't seem to be the case.

November 7, 2011, 11:47		#9
yoavmatia New Member yoav Join Date: Mar 2011 Posts: 7 Rep Power: 15	Hi Big well, like i said as the first reply to the thread. i used to be a Pro/E for 2.5 years, thanfully switched back to SW i know your on the other side ot the Pro/E VS. SW fence. however, since i see you are still stuck with the same problem!?! i would strongly recomend you take the the solution/work-around i used to do when ever i stumbled to your exact problem... say what you may - it works. (see my initial reply up in the begining of the thread)

April 4, 2012, 14:44		#10
Mithrandir New Member Mike Stroup Join Date: Sep 2011 Posts: 13 Rep Power: 14	interesting... I have been doing a lot of external flows extensively using surfaces... (wings, fuselages and tails)... the Pro/E model has a lot of surfaces used for construction.. on hidden layers.. and I get the same warning when I start up... but none of the domain that gets meshed is defined by a surface... so I click "OK" and carry on.... (Merged surfaces are used to cut [via solidify/cut] from the domain) can you post any screen snaps?