Inventor - Drawing View Weld Annotations

[hkilic896XF]

Hi.

I have a top weldment assembly that has sub weldment assemblies.

For each sub weldment assembies I set representations design view to Default and Associative.

So on the top weldment assembly , sub assemblie's welding symbols disappeared

This top weldment assembly has 52 weld beads

I create a drawing view for top weldment assembly,

I want to show only these 52 weld symbols.

For the drawing view

I set design view option to associative, 

I set model welding symbols

but the view shows all top level and sub weldment assemblie's weld symbols..

Even if I do this

result is the same..

The question is; how can I show only the welding symbols of top level weldment assembly, within a drawing view? (52 each only)

[dan_inv09]

I always have trouble with Representations and such. Are you supposed to be able to have a Representation at the higher level that "includes" a specific Representation from a lower level assembly?

[And then there is always the possibility that they kind of wanted it to work a certain way but just never quite got around to making do that properly.]

[hkilic896XF]

Hi,

I generally use positions both for model an drawings, rarely I need model states or reps. But in weldments I cant manage what I need..

This is a high level assm..

In sub assm view1 is active..

In sub assm default is active..

If I add a view to top level assm, and in this view set the sub assembly's view to view1 then for model and drawing of the top assembly I can get what I need

[hkilic896XF]

When creating a weld symbol in drawing, I select Sync Preset and create the symbol

bonded-attached to the model welding symbol.

When I change the model welding symbol properties eg. edit tail note..

welding symbol on drawing does not update automatically.

For example when I change tail note of F#5 on model side, after that I need to manually update related welding symbol on drawing side..

[swalton]

I have found similar limitations with weld features and symbols.  They seem to work ok with small weldments but are frustrating when working in larger models.  We are building out the workflows for modeling/documenting large welded frames.  My latest project has 51 seperate sub-weldments with 333 unique parts and 1900 instances.  There are 17,000 inches of weld bead in the top-level weldment alone.

iLogic helps some, but has odd limitations.  

Our current workflow is focused on calculating the total length of weld in the assembly.  Our production team will use that data for cost estimates.  We plan to model all welds as 3d fillets, even grooves.  We will use cosmetics when the fillet tool has issues with specific model geometry.  We don't plan on making 3d annotations.  All annotations will be in the 2d print and will govern what the shop produces.  Autodesk chose not to link the 2d weld annotations with the 3d or cosmetic geometry, so we will have to manually create the annotations. 

We are just starting out, so I expect the workflow will evolve.

[hkilic896XF]

Hi. We also have hundreds of meters weld beads in our products.

I solved the issue for getting each weld bead's mass, volume, length properties. Even if linear and closed type circular groove welds as well, using API / VBA.

Adding a one side End Fill to linear grooves and making some code tricks on circular grooves solved the "getting length problem of groove weld beads". 

Now I'm trying to automate to create model level weld symbol annotations of the existing weld beads. Because without model type weld symbols I can not get some specific information from weld beads only.., to use for drawing type weld symbols.

Thanks.

[heather_tracy]

Hi @hkilic896XF ,

I wanted to check in and see if you still needed assistance, or if you found a solution to your question already? Let us know if you need further assistance by providing an update or if you have found a solution, please share it with the community and mark you reply as the solution by clicking "Accept as Soluton" so other members who may have the same question could learn from your experience.

All the best,

Heather | Community Manager