Solidworks into MasterCam programming

[Torn]

So, I've programmed many many parts in Mastercam over the years, using mainly 2D .dxf's, or generating the geometry right in MasterCam. Now that I've gotten my hands on Solidworks. I was so excited the first time I imported a solid into Mcam. Not finding it very intuituve on programming simple parts off of solid models though. Almost tempted to go back to drawing 2D parts.

I know MCAM is more than capable of efficient programming with solids, right? I'm assuming that there is something basic I'm missing. Anyone have any good books or websites to recommend?

X4 and SW2010...

[Superman]

A quick hint
Mastercam is initially setup to program to wireframe and surfaces
-when going to select items from a solid, you need to let Mastercam know that this is happening

chaining dialog box---upper left cube for wireframe, right for solids ---(or is it the other way round ???)
surfacing - upper user toolbar, middle blue icon to go into a solids filter area -by vertex (join), by face, by body)

You can program using solid entities, but you may find that operations go "dirty" for no apparent reason, it is good practice to create surfaces and curves from the solid ( keep each on a different level ), calculation time would also reduce as there are less items needing to be selected to create offsets & check a toolpath to.

[Torn]

So, I import my .xt file into Mcam, it thinks it's a wireframe, so I convert it into a solid? Hmmm....need to do some heavy reading I think....

[WallyL7]

A parasolid file with the extension of .x_t is a solid model. A very clean solid model actually. Mastercam loves them. They have all the edge curves you normally use for profiling, and they have the surface faces you need for 3d type stuff.

Mastercam will recognize it as a solid model.

[Torn]

Well, I think I've made a bit of headway. Right off the bat, one thing I've noticed, and perhaps there is a solution to this, is: When I used 2D .dxf's to generate toolpaths, I could select the start of a closed loop, and the entity right behind it and it would automatically close the loop. Quite quick for complex 2D shapes. Working in 3D, it paueses at every change in profile where it has a wireframe shooting down in the Z. Kinda tedious when your part has several small corner radii. Also, I'm assuming it is better to draw up the solid without any small edge breaks on it, as this leads to problems in Mastercam (it makes it easier to pick the wrong entity unles you are scrolled right in on top of it)

[WallyL7]

You can choose whether or not you want to ignore z-lines by selecting 2d or 3d when choosing your chains. As long as an entire chain is on the same z-level it will grab the entire chain, or partial chain - whatever you select...

iow, if you have 2d chain selected, one click will grab an entire closed loop on a solid model.

[cadcam]

Thorn , why are you using a parasolid file and not the SLDPRT file from SW.
I love programming SW files from there they are clean and easy to work with. oh ya welcome to the 3d world allot of things will change for you and get better.

[ksc]

I am using sw2010 along with MC3, all seems to depend on how you want togo about things. When going from SW to MC I save my sfiles as STP. extensions seems to come over to MC fine but no solids tree.
If you have the solids package on your MC then just use that very easy to use once you get going.

[david martin]

Originally Posted by Superman A quick hint surfacing - upper user toolbar, middle blue icon to go into a solids filter area -by vertex (join), by face, by body) You can program using solid entities, but you may find that operations go "dirty" for no apparent reason, it is good practice to create surfaces and curves from the solid ( keep each on a different level ), calculation time would also reduce as there are less items needing to be selected to create offsets & check a toolpath to.

Can you explain these two points a little more? I've read it a few times and not understanding where these tools are or why one would use them?

I can't find a blue button labeled solids filter area. Why is this useful?

In the second paragraph are you suggesting adding surfaces to imported solid geometry (what you called, solid entites ?) before creating 3d toolpaths? Are you defining solid entity as any geometry not created in mastercam (in other words imported solid geometry)? As I'm writting this it makes a little more sense, but I figure I might as well still ask. Is there any need to add surfaces to imported solid geometry requiring only 2d toolpaths?

Thanks

[david martin]

I have one more question with regard to solidworks to mastercam if someone doesn't mind answering.

When importing geometry from solidworks is there a way to match the top plane (default Tplane) in mastercam? I'm X-form rotating each time. I looked and found a default Cplane / Tplane setting in the general machining parameters in the machine definition, but I don't think that is what I'm looking for. Again, any help would be greatly appreciated.

[cadcam]

When bringing in a SW file that the top plane in SW is Front plane in MC. so when you bring in the SW file if you set the WCS to Front then your part will lay as in SW.

As for supermans thought of creating surfaces and not using Solids I do not agree. I use solids 90% of the time and I do not have issues with operations just going dirty.
I prefer to cut from SW files as they are clean water tight models 99% of the time.
PS, Superman I hope you do not take this wrong Superman I know you are a long time user and have allot of knowledge of the system.

[emonje]

You could model in SW such that xy plane matches your intended T-plane. SW's xy plane becomes MC's "Top" plane in WCS, which by default is also T & C planes.

Alternatively, you can create co-ordinate system in your SW model to match intended T-plane but AFIK you have to export as STEP or Parasolid using newly created co-ordinate system as Output co-ord & then import into MC.

In any case using View Manager in MC to orient your models is much better in my opinion, it may be little unwieldy for new users but once you get the hang of it you may find this method far more useful.