Does it work in assemblies?
-
- Posts: 7
- Joined: Thu Aug 06, 2009 12:24 pm
Does it work in assemblies?
Got a demo this morning on your new program.
Does it work in assembly mode or just a single part?
Does it work in assembly mode or just a single part?
-
- Posts: 2405
- Joined: Wed Aug 01, 2007 4:15 pm
- Location: Irvine, CA, USA
- Contact:
-
- Posts: 7
- Joined: Thu Aug 06, 2009 12:24 pm
-
- Posts: 2405
- Joined: Wed Aug 01, 2007 4:15 pm
- Location: Irvine, CA, USA
- Contact:
-
- Posts: 2
- Joined: Wed Aug 01, 2007 4:15 pm
- Location: Weyburn, Sask, Canada
Assemblies
It's also usefull when working on say a rough casting. Rather than machine it as if it were a solid block.
Having clamps modeled in or possibly multiple parts are also good reasons to make it work in assembly mode.
I'm sure there are others
Having clamps modeled in or possibly multiple parts are also good reasons to make it work in assembly mode.
I'm sure there are others
-
- Posts: 2405
- Joined: Wed Aug 01, 2007 4:15 pm
- Location: Irvine, CA, USA
- Contact:
In our Pro configuration you can actually create a stock model that is a constant radius offset from the part - thereby simulating a casting of the part. This stock model can be used as the starting stock in a Roughing operation. I am not sure if you need the assembly mode for this.It's also usefull when working on say a rough casting. Rather than machine it as if it were a solid block.
As for fixtures/clamps that seems to be the valid reason to do this. However at present since VisualMILL can handle clamps only as 2D containment geometry (Sketches) this becomes a moot point. At present the plans are to introduce "Avoid Regions" but again these regions will be 2-D geometry.
I think working with assemblies is extremely important. For instance, each time you have a welded assembly and want to machine it as a whole. Same applies to woodworking when the product is assembled of smaller parts which each have been modelled as parts and you only want to machine the assembly.MecSoft Support wrote:No it works in Part mode only. Also why would you want CAM in assembly mode?
Just a couple of "comments" not directed at anybody in particular.
I know of a few circumstances where I have needed to machine assemblies. I have saved my assemblies as a part (yes - "save as", "part") and then imported into VM for machining. You could do this for the integrated CAM as well but the new part turns "dumb" during the save-as, which removes all features and also will not be associated with your original mechanical project anymore.
As far as stock goes, there has been a few times where I have had to model some horny looking, semi-machined part specifically to import into VM so I could make 3D toolpaths that didn't cut too much air.
If I was a conventional machine shop just working with parts this product would likely suit me well.
I find that less than 20% of my machining is making more of the same/similar parts, so associativity with a "changing" model is not important too my business.
I also find that I can program parts much more quickly by using 2.5d methods so I convert my slddrw to dwg for CAM (programming 2.5d from a dwg is super duper quick in VM).
I assume that I would lose this capability (dwg usage) by having the integrated CAM?
I am also curious as to what will happen to associativity of a toolpath edited Mop?
I know of a few circumstances where I have needed to machine assemblies. I have saved my assemblies as a part (yes - "save as", "part") and then imported into VM for machining. You could do this for the integrated CAM as well but the new part turns "dumb" during the save-as, which removes all features and also will not be associated with your original mechanical project anymore.
As far as stock goes, there has been a few times where I have had to model some horny looking, semi-machined part specifically to import into VM so I could make 3D toolpaths that didn't cut too much air.
If I was a conventional machine shop just working with parts this product would likely suit me well.
I find that less than 20% of my machining is making more of the same/similar parts, so associativity with a "changing" model is not important too my business.
I also find that I can program parts much more quickly by using 2.5d methods so I convert my slddrw to dwg for CAM (programming 2.5d from a dwg is super duper quick in VM).
I assume that I would lose this capability (dwg usage) by having the integrated CAM?
I am also curious as to what will happen to associativity of a toolpath edited Mop?
integratedmechanical.ca
-
- Posts: 2405
- Joined: Wed Aug 01, 2007 4:15 pm
- Location: Irvine, CA, USA
- Contact:
In the integrated CAM you can use the sketches directly for 2.5 axis operations. No need to translate the sketches to DWG.I assume that I would lose this capability (dwg usage) by having the integrated CAM?
When a sketch is changed we flag the Mop as edited. You will have to regenerate the Mop and recreate the toolpath to use the edited sketch.I am also curious as to what will happen to associativity of a toolpath edited Mop?
-
- Posts: 34
- Joined: Fri Jan 22, 2010 10:08 am
This is why you need to have assembly mode VM for Solidworks
This is why you need to have assembly mode VM for Solidworks. Not everybody does one part one setup. The router crowd needs this. It would be nice to be able to move everything around if I just need a smidge between parts. I know I can do this in the stand- alone, but the only reason I bought the solidworks plugin is because of the far superior sketching. Yes, I can save the assembly as a part and go from there, but that's not the point, because moving parts becomes an awkward pain in the a$$. JPEG is attached to this message, log in to view it.
- Attachments
-
- 4x8 all sheets all parts.JPG (271.75 KiB) Viewed 22903 times
Andy Baker
Brooklyn, NY
Brooklyn, NY
-
- Posts: 7
- Joined: Thu Aug 06, 2009 12:24 pm
-
- Posts: 2405
- Joined: Wed Aug 01, 2007 4:15 pm
- Location: Irvine, CA, USA
- Contact:
-
- Posts: 7
- Joined: Thu Aug 06, 2009 12:24 pm