Thanks in advance for all the help for what are potentially very elementary questions.
I have a seimple line-based family with array that distributes "couplers" depending on the total length.
Question 1: When this family is inserted into the project, the array does not work. In other words, you can stretch the family, but is still the variation of the family when it was saved. How can the array work properly in the project?
Question 2: Is there a way to omit (not just visibly turn off) the first and last pieces of the array?
Question 3: Is there a way to tell the family not to array anything when "Max Length" is not exceeeded? Not just thru visibility turn on/off.
Thank you very much.
Solved! Go to Solution.
For points 1 and 2 see the two attached files:
I verified them into a project and for me it worked. I work in metric , so I tranformed you file in order to can contol it....
Verfy them into you Project file
As for point 3 , I am sure it can be done using a conditional formula...I'll try it in the afernoon....
It's all very clear. Thank you.
Going back to my original question... the offset method from the ends only work if the array number is at least 2 (just like any array). If maximum length was 10', and the length needs to be 20' for the array to work. If the length is less than 20', it should idealy place one coupler in the middle. I am assuming at this point that the array method will not work for this application? Please take a look at the updated family file. Thanks again.
First , beside the array group made before, insert another coupler in the middle of the segment and lock it to the reference plane placed there.
Then, made two new visibility parameters VIS1 and VIS 2 , the first for the array group (in edit group mode ),the second for the single coupler.
Then , in Family types introduce the Formulas:
Load the family into the Project. Streching the bar , if under Max Length will show one coupler, if longer the Max Length will show the compete array...
Just as a follow up:
The visibility method turns out to be the way to do it, as I was able to confirm that turned-off objects do not get tallied in schedules. Having the two coupler conditions caused problems though, when the couplers started overlapping due to short length. I made two sub families: "Coupler - Single" for one coupler condition, and "Coupler - Multiple" for multiple coupler conditions. Max Length value is associated, and fed in frmo the assembly family down into the sub-"Coupler" families.
1. All couplers turned off when, Length < Max Length
2. "Coupler - Single" only turns on when, Max Length < Length AND Length < Max Length * 2
3. "Coupler - Multiple" only turns on when, Max Length * 2 < Length
Thanks again for the help! See attached file for your reference.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Start with some of our most frequented solutions to get help installing your software.