dynamic tie + wingnuts

[radek.valenta3HU3M]

Hi,

I wodner if anyone can help me with a block

We are using products with product numbers. We have a database of our products and these products has hidden attribut and from this attribut you can take product number and then more info about products. The tricky thing is that you can use just 1 attribut with product number in one block.  You can find some of our block in attach. I would like to build a new one block with slightly diferrent functionality.

See dwg for better undrestanding.

Thanks a lot.

Radek

[Libbya]

You can create all the different sizes using a lookup or a block properties table.  If you use a lookup, you can use a field in the attribute for the part number.  If you use a block properties table, you can write the value directly.  

[Anonymous]

Best suggestion I can give is to look into using a table.  The table will be able to give you a drop down menu to select your product.  For each product there would be a set selection of dimensions that could scale or stretch your base drawing for what you are looking for.  0.50M, 0.85M, 1.00M, 3.5M...……..  If you wanted to get real fancy you could make an annotation table that uses Fields to reads items in the block so it would automatically generate the table that is next to your examples.  

Attached is a slightly similar drawing but my table in the block reads the visibility parameter because I was looking at different angle of a bolt (top, side, and bottom)  This is a simple drawing that uses 1 dimension and scales the components to fit 1/8, 1/4, 1/2...… bolt sizes.

Also attached is a block for W-Shaped Steel.  This uses 2 attributes because I wanted the dropdown menu to include smaller more organized columns instead of 1 super long column.  This is a much more complex drawing that uses many parametric constraints and dimension.  The table then reads the dimensions that are set for each one and draws the shape accordingly.  I also needed to be able to see Top, Side, and section view so there are those visibility settings in there as well.

[Anonymous]

I've taken the time to manipulate the block on the right no something what you looking for. (I think).

[radek.valenta3HU3M]

Hi Libbya,

I know the functionality you describe but unfortunatelly it does not work properly with our material list. I would like to present you functionality I would like to achive. Do you use MS Teams? It would be much faster.

Thank you.

Radek

[Anonymous]

We don't use MS Teams.  If you have a large spreadsheet of sizes and information you can use the copy/paste into the table. To generate a larger amount of sizes than just the few that you had set for examples. and you could use the dimension constraints to set larger rod diameter sizes. explode the wing nuts and set dimensions to them to scale appropriately to match.  Just a few more options to explore.

[Libbya]

---

@radek.valenta3HU3M wrote:

Hi Libbya,

I know the functionality you describe but unfortunatelly it does not work properly with our material list. I would like to present you functionality I would like to achive. Do you use MS Teams? It would be much faster.

Thank you.

Radek

---

I do not use MS Teams either.  Why won't it work with your materials list?  The values on the tables can be whatever you want them to be.  

[radek.valenta3HU3M]

Hi everybody,

I cant overcome 2 obsticles:

1. I need 3 attributes - 2x constant for wingnuts - works perfectly. 1x for tierod which must be dynamic. I tried to get some functionality between length of tierod and attribute. It gives me result just when I regenerate my drawing and I would like to get rid of regeneration its nonsense to regen everytime.

2. I dont know how to get functionality between length between wingnuts and length of tierod. 

But how to connect these two length without having massive table (300 - 5800mm). Even though the bloc is then to time consuming to use in drawing.

Thank you for your comments.

[Libbya]

When using fields in dynamic blocks, a REGEN is required in order to immediately see the change, but the REGEN is not *needed*.  The field will automatically updated on open, save plot, etransmit, and regen.  I am not sure whether or not you need to regen for DATATRANMSMIT.  Regardless, if you do need to do a regen, I don't see why it is a big deal.  In that case, it is only two letters (RE) and a space.  The prior sentences are the equivalent work of 135 regens and I just wrote those for you for free.  You can also write values directly to attributes using the block properties table.  In that case, there is no field and no need to regen.  However, block properties tables and lookups do not play well together.  They can work fine within a block together, but they cannot be manipulated by each other and you cannot use the same parameters on both at the same time. 

You will need to give a better description of the desired functionality for issue 2 in order to get any decent advice.  However, I would mention that you can use range values on lookup tables and it sounds like that would cure the issue.  

Take some time to draw examples within your file of the EXACT way you would like the block to behave.  Without that it is just a guessing game and I don't like playing those.  

[radek.valenta3HU3M]

HI, I ve tried to describe it better in the dwg I enclose. Thanks.

[Libbya]

Create a visibility state for each size.  Add the linework, parameters, and actions for the appropriate movement to each size.  Add the three attributes visible for all sizes.  Check the visibility state and attributes with a block properties table.  As far as I can tell, that will satisfy ALL of your requirements.  Report back if you get stuck or need further explanation.  

[Libbya]

---

@Libbya wrote:

Check the visibility state and attributes with a block properties table.  

---

That should have read:  "*Change* the visibility state and attributes with a block properties table."

[radek.valenta3HU3M]

I ve tried my best, but I found 2 solutions. Both socks.

[Libbya]

If you need unlimited adjustment, then you will need to use lookups and you will need to do a regen.  I don't see any way you will get around that.  If you can use set increments then you can use a block properties table and write the attribute values directly.  All attributes must have a unique tag.  Right now you have three names ART and that can/will cause problems.