Help with an stl file reverse engineering into a solid or surface 5

[poolrod2]

Hi everyone, I had a guitar neck digitally scanned for my daughters school project, to machine it on a router, but no matter what software I try, it comes out as patches of surfaces. Is there a way to make it just one solid or surface as if it was extruded from a 2d sketch?. Thank you all, any help would be great. stl and bad model image attached.

 

[poolrod2]

Thank you very much. I'll post a pic and model of the result when completed.

 

[TheeCircle]

Any chance the people who have created these files could give me a run down on how you did this from the stl?

Thanks in advance!

 

[Dave K]

I used the "rapid surface" tool, on the reverse engineering tab of NX9. Then connected the various surfaces with studio surfaces, fillet-bridge, etc.

NX9 file attached

-Dave

NX 9, Teamcenter 10

 

[Ehaviv]

Hi

Can someone use the cyan curves(see link) to build the guitar solid
and show how

Thanks in advanced

 

[TheeCircle]

Hi Gunman,

What are the steps in using the reverse engineering tools? I have never used them.

Thank you!

John

 

[Dave K]

They way I did it, you pick the STL file, and then draw 4 splines on the part, think of it like a "square", and it will create a sheet. You can adjust the degree, and a couple other things, depending on the surface quality you want. So, I did this in various places, and then filled in the gaps with other tools.

-Dave

NX 9, Teamcenter 10

 

[TheeCircle]

Hi Gunman,

Any chance you could create a quick video so I can try an figure it out?

Thanks again!

John

 

[SS88]

Gunman: did you try to create the whole guitar with only one surface? I did mine by using only one Rapid Surfacing feature as the stl quality seemed to be rather good. Or do you see some advantage on using several of them and then creating surfaces in between?

 

[Dave K]

I've never had luck doing one large surface, so out of habit I did it in a few. Any chance I can see the NX file, where you did it all in one? Hopefully I can learn something.

-Dave

NX 9, Teamcenter 10

 

[SS88]

It depends on the scan quality which way I start building the surfaces. I create several of them too when the quality is too poor to create everything or most at once.

I can share the NX file, note that I've done it with 11.0.1. I share couple pictures of the surface pattern to get the idea what I was doing. I don't know what is the best way to create the pattern, this way is what I've learnt with trial and error.. Basically loose pattern/web where high resolution is not needed and thicker web where resolution is needed like in the variable radius areas in this model. I would be more than happy to receive any tips or better ways to use Rapid Surfacing also.

Model:

http://files.engineering.com/getfil...a-9dfa-a75a79ef5710&file=guitar_neck_NX11.prt

pic1:

http://files.engineering.com/getfil...4b-9a96-a9e50aa527e9&file=guitar_neck_001.jpg

pic2:

http://files.engineering.com/getfil...c0-a9e1-97b5fa9e4020&file=guitar_neck_002.jpg

pic3:

http://files.engineering.com/getfil...f6-a073-a6152e0ac3ee&file=guitar_neck_003.jpg

 

[gbangs]

To get those "over-the-top" results you're looking for, I think you need to turn it up to 11. Seems appropriate.

gbangs
TC 8.3.3
NX 8.5.3.3 MP11

 

[Dave K]

Thanks SS88, that makes sense. From the pix, I can see what you did, I'll have to try it. I have NX11, but only on a test machine...this will be a good test, as it has a very slow processor, minimal ram, and cheap graphics card

@gbangs cranking it to 11 makes even more sense with a guitar neck!!

-Dave

NX 9, Teamcenter 10

 

[Toost]

There is an enormous difference between a single feature and a single surface.
When surfacing, the aim should always be to create as simple as possible surfaces / faces.
Creating the entire neck in a single surface is fully possible for surfacing artists, but the result will be a highly complex and heavy surface which might not be usable for downstream operations. - Don't even try.

A single feature might contain almost any number of faces / surfaces, all hopefully as simple as possible. The resulting model is smaller ( MB) , faster and usable for downstream operations.


Regards,
Tomas

 

[SS88]

Good correction Toost.. I was wrongly talking about creating one surface when it's actually one feature in this case.