Family looks Correct until loaded into a project file

[wcaramella]

I have built a library stack family that you can adjust the number of shelves per side through an array parameter. In the rfa file the stack types look correct (number of shelves, height of stack, width and depth of shelves). But when I load the family into a rvt file, the Stack types no longer appear correct. Say there are 12 shelves per side, only the bottom two shelves and the top shelf appear, while the parameters in the properties dialog read 6 for number of shelves. In all types with more than three shelves, only the bottom two and top one shelves appear. This does not make sense to me since the array consists of geometry that is grouped when it is arrayed, so in essence shoulded the each instance of the array have the same geometry? Any thoughts?

W

[Andre Carvalho]

Did you created your array using the option Move to: 2nd or Move to: Last? Using move to last will create all shelves in between the first and last. Also, constrain the first and the last to avoid the shelves in between to stray.

Andre Carvalho

[nancy.mcclure]

Using the 2nd option in the array will hold the distance between each shelf, while using the Last option in the array will equally space out those shelves, both based upon the # listed in the .rfa.

In either case, you'll want to add a parameter (# of Shelves, for example), or build in a formula that calculates the # based upon the overall shelf height to that array in the family so that the user can either specify the # of shelves, or have the system do the math automatically.

[Mr Spot]

Checkout my tutorial on my blog if you haven't already for arrays. Hopefully you'll be able to use it like a checklist to see where you went wrong.

[wcaramella]

I did use the move to Last in the array command. I started by arraying a reference plane from the bottom shelf position and arrayed it using the last command to the top shelf position. I then Aligned the top plane to a reference with a parameter to adjust the top shelf height. Then added a parameter for # of shelves as was mentioned above. The shelf reference plane arrayed as expected; then edited the group of the bottom shelf reference plane and added the geometry of the shelf. It is a solid extrusion with width and depth parameters to adjust with the over all stack width and height, I used a void to cut out the extraneous solid.

In the family everything works beautifully, when I load it into an rvt file. the visibility of the fourth + shelves in the array is gone.

This may help dig a little deeper.

In the mean time, I will read up on the blog.

Thanks,

W

[Andre Carvalho]

Why did you array the reference plane? Try adding a reference pane to the bottom of the shelf position and other to the top shelf position. Then lock your first shelf to the bottom reference plane and the last shelf to the top reference plane. Control the number of shelves by the number of arrays parameter.

Andre Carvalho

[wcaramella]

I arrayed the Shelf RP because I was having difficultly locking the top (or last) position of the array to the RP with the parameter that allows the height of the top shelf to be adjusted when array had geometry created already created in the group. By arraying the the Shelf RP first, I could lock it to the Height RP outside the group. I could then in crease the # of shelf RP's through the # of Shelves parameter and adjust the top shelf height through the Top Shelf height parameter, all the shelf RP's in the array would adjust there spacing to equal out.

I tried the method you suggest, but each time I would get a error saying that I can't lock elements in groups to things outside the group, hence no height adjustability. I did not get this warning when i locked the arrayed RP to the Height RP outside the array group. Like I said, It works beautifully in the family, but perhaps that is way it is getting tripped up in the RVT file.

W

[Andre Carvalho]

I tried the method you suggest, but each time I would get a error saying that I can't lock elements in groups to things outside the group, hence no height adjustability.

You are probably trying to edit the group and lock it. What I did was to lock the group itself (without editing it) to the reference plane.

See attached example I just created.

Andre Carvalho

[wcaramella]

I will give it a go and letyou know how it goes.

Thanks,

W

[wcaramella]

An added twist....

I went about removing the reference planes from the shelf, arraying the only the goemetry of the shelf, and then adding the # of Shelves parameter to the shelves. Locked the top shelf to the Top Shelf Height Parameter. That worked, I was able to adjust the height of the top shelf, all the shelves below equalled out in spacing and i could adjust the number of shelves no problem.

But when I looked at the stck in 3D, I noticed that I left the void behind to grab the void that cuts the shelf with the group. So, i stepped back, added the void to the group, arrayed, added # of Shelves parameter- that worked. Then aligned and locked the top shelf to the Top shelf Height RP and Constaints Not Satisfied appeared. Does the Void need to have its own array associated with it? should i build the shelf differently so the no vouid is needed? do I lock the void to a seperate height parameter similar to the Top Shelf height?

Thoughts?

W