even those of us that use this routinely miss reading the instructions - been using this for years and never noticed the option to turn off selected mates
As with a lot of the tools in SW, you need to use it a few times to figure it out. Copy with mates is very useful, but you need to start off with it in mind. Say you've got a bolt 2 washers and a nut, I like to mate the bolt nut and washers up to each other first. Then I just use 3 mates (2 coincident and 1 concentric) to the parts that are bolted together. If I do it in that order I have more success especially if all the bolts are using the same planes.
Very good point Matt Peneguy. It only prompts for outside mates, so that any mates between included components do not have to be reassigned. This becomes far more helpful when what you're copying is many items strung together, like an entire pipe discharge train. Sidenote: do not include weldments, fixed, or virtual components in a copy with mates unless you planned ahead for such.
A simple example:
When I mate flange hardware, I chain it so that the gasket is mated to the flange, the stud is mated to the gasket, and the heavy hex nut is mated primarily to the stud, also with a coincident to the flange face. Copy w mates on HHNut leaves repeat, repeat, select 2nd flange face. Copy w mates on stud and nut pair leaves repeats & a concentric. Copy w mates on gasket, 4 studs, and 8 nuts applies to the next flange (pair). It could be even simpler to perpetuate a set if I had mated the 2nd 3rd and 4th nut to the 1st nut seat face instead of the flange face.
I used to use a pattern to repeat the hardware, but got sick of controls for hiding components inside vs outside the pattern. Now I revert to copy with mates instead.
Also, Some CwM typically need distance reversal for correct placement. Opportunity is given to alter dimensions, directions, and alignments before accepting the placement (i.e., don't accept yet if it's easier to bump it around in the preview).
Contextual Isolate can be really helpful if your assembly is very dense or complex with other objects.
Now I use only 2 mates as you can lock rotation in concentric mate.
On a side note....interesting to note however.
This is a good example of SW putting in a ton of check boxes and workflow that could easily be simplified.
That is A-typical for SW. There strategy is to add, and add and add. Resulting in a overloaded, slow user interfaces.
It takes skill to minimize user-input while still providing full functionality. I wished SW would expand in that department.
The lack of streamlined user interface is particularly visible in the drawing environment.
Remove the individual Repeat button - List the original reference instead and have the first one highlighted.
Remove the Enable/Disable - Instead if a reference is specified it is enabled. If the input box is blank, guess what - skip it.
Add one single repeat button at the top. Use the pin button instead like we have with feature manager.
Once you set up your selection entries (remove the ones you don't want) you simply click the pin.
Meaning I want to cycle through the command again, with SW asking for new input for all selection boxes that are filled.
Let me tab through the input boxes top to bottom and use the delete key to clear the selection in each input box.
The pin functions like it always does (no need to learn extra procedure). The interface is smaller and takes less time to generate (note the dark mate icons would no longer be a toggle button, just a symbol. If you don't want to use the tab key to skip past repeated selection then you can keep the toggle to indicate it is repeated.
Now all you have to do is make sure Users know that when ever an input box is missing it is simply skipped if the function allows for it.
I removed 6 interactive toggles and added 1. For ever mate SW adds 2 toggle buttons that I don't need.
The workflow is simple without any added switches.
Just one example of many.
Note: I haven't touched on the subject to change the mate selection midway in the copy mate function. I can account for that with the same user input if someone was to ask.
Not what I intended the page to be about but yep....I have noticed that most of the programmers do not know what the heck the work follow is. I am not sure who they get direction from. I guess that if you don't like some of this new stuff that you could be like I have been and just ignore it and work old school the way that I have been. I decided that it is hi time that I get back up to speed and start learning some of the commands out there.
I apologize if I deviated your thread somewhat. Your initial post has a lot of merit.
start up a side one.....how to improve commands...or something....I sent in quite a few enhancement request for just that purpose over the years....
David Matula wrote:
I have been encouraged by all the wonderful questions about some of the new commands that have been added and it is time to start thinking about using some of them. So this week it is going to be copy with mates.....
Good thing that I was good at mirroring components and notice the next arrow...
this here looks simple enough but as always when I go back to explain this I notice that just about every command has something that helps you work threw it. All you need to do is put your reading glasses on and read.
so far so bad.....not one component had been in the right place. flip a mate alignment or edit a mate to pick a new face for a distance mate cause picking the right one was not as easy. One out of three isn't bad though. at least I did not have to edit all three mates or put them all back in individually. By the end of the week if I get to keep making more assemblies I may have this down to no edits needed.
David Kudos for trying something new.
One thing I encourage when we have an intern or new designer to utilize this function is design intent prior or re-distributing mates before using the copy with mates.
Let's say you have 6 components you want to use this function with.Only 1 of those parts should have mates to the rest of the assembly(treat the parts as though they are their own little sub assembly) This greatly enhances the workflow and the capabilities of the copy with mates function. The more you play with it the better it works.
I too suffered from the not using it because it was new and I could not get it to work the way I wanted, but once I got used to it I definitely would not want to use a multi mate enviroment again.(Ctrl drag re-mate, rinse repeat...etc)
Time to work on the property Tab builder. will this thing do what I want?
I have a drawing that in group 1 I am looking to fill out title block info.
on another part of the drawing I want a group for design data.
then a few other groups for miss info and notes to be filled out
Is this going to work?
the property tab builder does work, but I'm not sure what you want it to do. it makes a customized form for entering file properties. to have those properties drive stuff in your model and/or drawing involves other tools.
just looking to fill out data in the title block and other places on the drawing. Hope that I can get it todo what I need....have to get some drawings out or I could spend some time working on it.
Property Tab Builder is a means of creating an interface to push Custom Properties around. So, it sounds to me more like what you may need is a macro. That is unless these fields are already present in the drawings, you'd have to create them first.
To directly answer your question, I am unfamiliar with PTB use. This response may be more detailed than you desired.
I think it'll do what you want by retroactively populating existing files with properties, but instead I put what's needed into our templates when we started using SWx. I had these references already worked out from an earlier failed attempt at creating a company-wide database that scales to all roles, like Client info for sales/estimating, BOM info for docs and purchasing, small details for assembly, and big picture for shipping. Now I have similar functions within all my models, but it only suits engineering reference needs. It all depends on what you want to extract in what context, based on your workflows. Take what's useful and discard what doesn't apply.
I have Drawing templates which contain only the custom properties related immediately to that document: DrawingType, DrawingNoSuffix, initial and date fields (DrawnBy, DrawnDate, CheckedBy, CheckedDate, EngineeringApproval, EngAppDate), Revision, LatestRevDate, LatestRevNote. This is because one Assembly can be shown in multiple documents to show different purposes in my workflow. My Revision Block (A DLibrary .SLDBLK file) also pulls these to automatically populate once dropped into the border. Edit: these are particularly useful in multi-sheet representations to avoid editing same thing in many places.
My drawings usually contain Assemblies only, except for Fabrication Detail drawings which are exclusively used to describe a weldment component. I use the same drawing template for both purposes by placing the same descriptor fields into Assembly template as well as Weldment Part template. These are the fields linked into the drawing template, in both notes template (a handful of .sldnotestl files in Design Library with references to other standard documents) and the drawing's titleblock. The common fields for this purpose are: ProjectNo, ProjectName, Customer, Client, ClientNo, SiteName, SiteLoc, SystemLetter, & SysTagNo. Not all of these are necessary, but are present if needed.
Subassembly and Part templates are treated here as purchasable items, with BOM fields such as PartType (for sort purposes), Brand, Vendor, PartNo, & BOMDescription, with additional check fields: MakeOrBuy, Comment (freeform data source notes), Material (linked), Weight (ok, it's linked to mass), Mfr Tolerance, WettedMaterial, SealMaterial, PressureRating, PortType, DateCompleted, Author, FirstUsedIn (a project number reference), CutSheet (a file location / name reference), Manual (another file location / name reference), sometimes AltManual1, AltManual2, etc, MSDS, ElectricalPower, ElectricalLoad, & ElectricalRating. The check fields catch irregularities such as Materials for chemical compatibility, or PressureRating and ElectricalRating for adherence to specification. Fields referring to other document files can be used in quickly gathering all Cut Sheets, Manuals, or MSDS (usually included lubricants) for all components included in the assembly through a custom BOM which is only used in a supporting document.
Pipe/Tube Part template is a subset which lacks irrelevant fields and has pre-filled default choices to choose from by deleting what isn't relevant instead of typing what is relevant. I.e., Wetted Material lists seven commonly used materials, PressureRating contains Schedules and thicknesses, PortType contains "NPT / SW / BW / Compression". The most useful field here is OAL, or overall length, which is currently measured and filled manually, then totaled automatically with Excel. That feature could use improvement in my workflow, but shows a specialized use for perpetuating model data.
I've thought of some more that I don't know yet how to implement well or easily, like BoundingBox (shipping dimensions), CenterOfGravity (XYZ coordinates from a BoundingBox corner), LiftPoints (dims) and NoLift or NoStack or NoCut properties for areas what have restrictive handling. These are not currently needed in our legacy workflow, but rather an idea I have of improving it. Time will tell if that's ever approved or developed.
When I began using SWx, I defined everything that would ever be needed about anything used, considering how and where. Properties belong where they are relevant and useful to fetch within drawings, depending on purpose and context. Interlink many types of entities for automatic text without repetitive manual typing that can lead to typos.
"Is this going to work?" Yes. Consider your needs fully, and use what is relevant in context(s).
The amazing thing about Property Tab Builder is the following:
Have a field in which you want the user to select ONLY 1 of 4 different values? Easy....Use Property Tab Builder and create a drop down menu (or a radio button) with those 4 values. Even better, link the drop down menu to a text document and you can add items to the list just by editing the text document.
Want a drop down menu dependent on another drop down menu? Cool....since SW 2016, you can create "list groups" that are based on excel columns that are dependent on each other.
Basically, it gives you a place to communicate to your users as to what you want in the properties if the properties might be different based on different types of models.
Thanks that sure looks better than the help file right now....will take a look at it when I have the time.
WELL a little trial and error and I am on a roll. the groups are not working like I thought yet but will see what happens
I got text boxes working good.... how about a list?
learning is so much fun...