SW2009, SP4.1
We've just updated our SW to SP4.1. In the past we'd put in our major equipment and do all of our route assemblies, now virtual assemblies thanks to 2009. These assemblies would simply be labled Pipe1-<assembly name> in our design tree. Our understanding was to be able to detail these virtual assemblies in a drawing we'd be required to save them out as an external assembly. This was accomplished by finding that option by right clicking the virtual assembly in the tree. Just noticed that option is no longer there.
However, we can now successfully place these virtual assemblies into a drawing without a promp to save externally. We also were able to send the drawing and virtual assembly into our vault. All good things however we can not find a way to rename the virtual pipe assembly as we desire. We can rename it in the design tree, but the file name remains Pipe1-<assembly name>. We'd like to see them renamed as we catagorize them by function, gas, oil, coolant, etc. Just having a long list of Pipe1-Pipe56 creates confustion when managing data.
One, where did the option to save virtual assemblies as external file go? Is this step even needed?
Two, If not, is there a way to rename these virtual assemblies as such the file name gets changed without the, save as copy/replace.
Thank,
Nathan
Right, changes the name in the design tree. But right click and open that file and it's still named "Pipe#<assembly name>". We need the file names to change. I'm guessing the only way is to save as external file, save as/replace, or use SWX explorer.
Ok, back to the virtual route assembly. As I stated earlier the option to save the virtual assembly to an external file has magically come back today. User claims he didn't just "hide" the option as you can in the customised window. The crazy thing is now when we try to insert that virtual pipe into a drawing we're prompted to save as a external file before being able to detail it!?
Very inconsistent. My only guess now is he had accidently saved out these virtual assemblies as the same name without knowing it? Would PDM Group save these out during a check in? Is there anyway besides the name to indicate it's a virtual route assembly? Up until this last release I've rarely used virtual part/assemblies.
When I right click and open file, the name is changed to what I changed it to in the design tree. What version of SW are you running? I am running SW2009 SP4.1...
I'm not sure why you are having problems? When I check the files into WorkGroupPDM, the main assembly and the insert part file check in. The assemblies I created inside of this assembly do not check in unless I save them externally. Maybe you are having a file issue in general, corruption? This isn't much help I know, sorry.
Does that name change work for both regular and virtual parts, or just virtual?
We are running the same... however I think I've narrowed it down some more.
The reason he wasn't getting the "save to external file" tool or prompt when dropping it into drawing was b/c it wasn't a virtual part. When he drops a flange in his assembly to start a route occasionally SWX doesn't see the route template. (which is wierd b/c my machine doesn't prompt me for a template) His only option is to cancel out. The route still occurs but it seems it act similar to pre virtual route assemblies, SWX saves out the assembly externaly right off the bat. He didn't really know any better to change the name in the window which made me think it was still virtual...(other than the name I don't know how to tell, is there a symbol,...<,>?)
This isn't the first time we've had problems with the route assembly templete either. It seems two of the seats can see it, and the other two can't. For example I can start a new assembly and see the route assembly templete and just make route assembly without having to start in in a larger more complex assembly. The other two machines don't see that templete, but up until now seemed to use the template when starting in a large assembly.
We tryed working with our VAR on this for awhile but got no answers. We let it drop b/c for the time being we were up and running. I'll have to look into our file locations and route settings to see where we went wrong. So I think I've narrowed it down to the template, file locations, or route settings.
Thanks,
Turn this on before re-naming anything.
Update component names when documents are replaced. Under Options/external references/assemblis.
It automatically gets turned off when routing. I don't know why, it is just stupid.
To be honest I don't like the virtual component feature to begin with. It slows down the process. I guess in 2010 they will have an option to turn it off.
Really?! Other than this slip up and one previous errors with seeing custom properties of virtual pipe parts on check in (which was solved with SP4.1) we've absolutly love them. We've found a great boost in design time b/c with virtual parts we're not required to save the assemblies on the front end and saving the actual pipe parts have been eliminated all together. Granted when the time comes to detail the route assemblies one needs to save them externally. That you can do all in one shot and we've often liked the fact that we can name the file names on the tail end after the model is complete and engineering and production can review the runs. Before we'd numerically name them xx1, xx2... so on and then have production request we break a run creating gaps in the numbering or illogical numbering.
In any case I can see how one may not like them and it does slow down performance of the software somewhat. At least they aren't giving up on it for those that like it and offering the choice to turn it off for those that don't.
I can see that many people like it but in my process I prefered it the old way to save it on the front end, the pipes take the name of the assembly, all is good. If you make a change and need to re-name do it in explorer.
Now there is an extra step after the fact. You still need to go back and save externally the assembly and the pipe segments. I guess it is sixes but it was not a welcome change for us.
Hi all,
This thread ran on for a while and it was full on good information for us in development. Time for me to chip in.
We all thought that using virtuals for routing was a good way to go. It streamlines the routing process considerably as you don't get annoying dislogs asking for save names etc. However, some customers don't like them so we have made some changes.
In SP04, if you look at the routing options dialog you'll see some new options.
o Save routing assembly externally
o Save Routing parts externally
The default is to save the assembly externally and save parts internally. These seemed to be the most commonly preferred settings.
With this set, you will still be prompted to set the name for saving the assembly (in the route properties at start of a route). The assembly will be saved externally, the parts will be saved internally. If you also check save parts externally the parts will be saved externally - if possible also check Use automatic naming for route parts, then you won't be prompted to set the name for each pipe/tube part that is created.
Saving the route assembly externally is all you need to be able to create drawings automatically.
Has anyone played with the Pipe Drawing functionality? This creates a drawing of your pipe, dimensions it, adds BOM but typically needs a bit of tidying up to make it useful as a drawing document. Is it useful or do you prefer to create them yourself or use Isogen?
Cheers
Andy
Andy,
Excellent information. Those settings sound like the reason this one user is having his route assemblies save up front and thus the confusion of not being able to save externally. I’ve looked for a bit and can’t find them. I’ve checked dialogue pop ups, routing options under Tool>Options>Routing, and even the Routing Options Setup in the Routing Tools. We’re running 2009 SP4.1 and I can’t seem to find them.
I’m not familiar with Pipe Drawing Functionality... Is it 2010 new? We currently create them ourselves but I’ll have to do some research on this function to see if it’s useful.
Thanks,