Self-Adjusting Block

Self-Adjusting Block

Anonymous
Not applicable
652 Views
5 Replies
Message 1 of 6

Self-Adjusting Block

Anonymous
Not applicable

Attached is a dynamic block I use at work that I am trying to replicate the functionality of. The block represents a racking beam, and as it is lengthened the number of beam ties (thick, vertical lines above beam--or a single thick line centered inside the beam to represent a crossbeam) and the height of the beam are automatically changed. The beam ties are controlled by visibility states, but I do not understand how this is controlled by changing the length of the beam. I also cannot figure out how that changes the height of the beam to the proper size. The ties are turned On or Off by a lookup parameter, but I again can't figure out how it's changing the visibility state; every time I try to replicate the block, the lookup does not affect the ties at all.

 

I have tried using the Block Properties Table to force the block into predetermined attributes, but it didn't work, and the table is not used in the attached file. The lookup table also has no input properties listed.

 

The properties are:

<8'-9" long: 5" tall, no beam ties

8'-9" -- 10'-9": 6" tall, one beam tie

11'-9" -- 13'-9": 6" tall, two beam ties

>13'-9" long: 8" tall, one crossbeam

(Ignore the 2", 3", and 4" beam heights; they are not a part of this voodoo)

 

If anybody can shed light on how this block works, I'd appreciate it.

0 Likes
653 Views
5 Replies
Replies (5)
Message 2 of 6

Libbya
Mentor
Mentor

I do not believe the block you attached adjusts the visibility state automatically.  Perhaps you attached the wrong block?  

 

There are two ways I know of to automatically adjust the visibility state. One is through a block properties table and the other is through a double lookup.  Neither BP nor double lookup are present in the posted block.   

0 Likes
Message 3 of 6

Anonymous
Not applicable

That's where my confusion comes from. Inside the block editor, you see that the visibility states are '0 Ties', '1 Tie', '2 Ties', and 'Cross Bars'. When you adjust the block in a drawing with the beam ties 'On', you can see the block go through each of these states as you stretch the block. It also changes the height from 5" to 6" to 8" depending on the length. That wouldn't be caused by the visibility state, but I don't know how to get the block to adjust its height by changing its length.

 

I'm trying to figure out if there's some extra functionality in the block editor that I am overlooking that allows extra control over dynamic blocks. The block's function really seems as though it's controlled by code ('if length < 105 then height = 5' for instance), but I don't believe that's the actual case.

 

Thanks for the response, and if this is just over my head, I can just cut my losses if necessary.

0 Likes
Message 4 of 6

Libbya
Mentor
Mentor

Nope.  As I mentioned before, the block you posted does not change visibility states regardless of the ON/OFF setting or adjustment of the various stretch parameters.  I can make a video of it *not* switching visibility states if that is needed to convince you, but I'd rather not take the time.  I think you attached the wrong block file.

0 Likes
Message 5 of 6

Anonymous
Not applicable

It looks like I may be fighting a losing battle. I tried opening the attachment from the original post and it appeared correct. But when I saved it and then inserted it into a new drawing, the functions I described didn't occur at all. I was able to make it 8" tall at its shortest length; it is supposed to correct itself to be just 5" tall at that size. Also, the visibility states weren't changed at all and the beam ties did not appear/disappear when I used the toggle.

 

Attached is a PDF that shows what is supposed to happen as you stretch the block. Without you being able to play with the block itself I may just have to give up on repeating this function, but thank you for taking a look.

0 Likes
Message 6 of 6

Anonymous
Not applicable

Now I'm convinced there must be an external LISP or other file that is influencing that block. I made a copy of it in the same folder (named Rk-Beam - Copy) and when I inserted it in the same way I did the original, none of the aforementioned changes occurred. It was as if it were a completely different block. Sorry for wasting your time, but thanks for the input.

0 Likes