"Repetition" or "chain distance" constraint

Hello again,

Imagine a " floor " component of a building, in several copies, and I want to superimpose them with a constant spacing between each floor. And I want to keep their independence of horizontal motions, so I don't use component repeat.

Is there a way, like a chain dimensioning, to manage the distance between the floors, but with a single constraint, rather than inserting a distance constraint between each floor?

Hello,

I don't know from which version it is possible to perform a repetition on the reference geometries.
By repeating a plan, and by providing an adapted constraint reference on your " building floor" component (coincidence), it could work for you, right?
The constraint reference is used for insertion, for the rest it is " copy with constraint "...

1 Like

Hello Sylk,
For your problem, I can advise you to base yourself on a point sketch, and then to use repetition compared to a sketch it will be much easier to manage

3 Likes

Hello and best wishes

You can optionally use sketch repeat. You position via points

1 Like

I'll use a sketch-driven component repeat.

1 Like

Hi @Sylk ,
Do you want to be able to move them to the :mouse2:? And in the whole horizontal plane?

Hello everyone, and Happy New Year to you, thank you for the answers. This project is currently on standby, but your answers are still useful.

@Le_Bidule they are rather superimposed but evenly spaced racks, which slide only in X/-X.

Hello @Sylk

As said before, you can use a repetition driven by a sketch, so by side points sliding on a grid in construction line, and this one can also be driven by sides. The stitches can be repeated when creating a sketch, I think the spacing of your racks is regular.

I'll come back to your subject, have you ever tried top-down design with schematic representation sketches of an assembly?
Personally, due to lack of time (always the same thing) I didn't dwell on it, but it can be a path to explore.
Below is an excerpt from the SW Help (Assembly\Top-Down Design)

1 Like

@Le_Bidule
I prefer this method.
But in this case, if he didn't design his set in this way, it may be a big job to start again.
In the past, I have taken over large assemblies by creating a reference skeleton (origin, level, etc.) and reconstrained disappointed assemblies and subassemblies. The result was stunning, the mass of the file had been reduced and the whole thing was more flexible.
I don't know if this helps the subject and your @Le_Bidule solution @Sylk