Learning Forum

[timescavenger]

Hi,

I´d like to perform a parameterised design exploration and optimisation of a structure made of beams (i.e. line bodies). I already created the structure in SpaceClaim but now I cannot find out the way to define the beams section dimensions as parameters: they appear already as driving dimensions in the Groups tab of the section window which opens up when you edit the beam profile so it looked like this was the way to go to set them easily: 

...but then, they do not show up anywhere: neither in the main window (where the actual beam structure is) nor are they transferred to Mechanical so that you can use them as parameters...

I know I could build the structure with midsurface-shell bodies and using the thickness (the main dimension I am interested in as input variable) that in this case appears automatically in Mechanical but I´d prefer to stick with the beam-based version and use the Solution beam-tool options...

Any ideas? It´d be appreciated.

[bouzasoscar]

Hello timescavengernI'm facing the same problem. Were you able to solve it?nThanks in advance.n

[HSS]

I'm having the same problem. Did anyone find a soultion or a work-around yet?n

[peteroznewman]

nDesignModeler allows section dimension to be parameters that are passed to Mechanical.n

[HSS]

Hey peteroznewman,nthank you for your reply! Yes, it's easy in DM but I need to stick with SpaceClaim.nI at least found a Work-Around: I create a parametrized sketch with my cross section, then I extrude the beam. I then use the extract function and extract the beam profile from this beam and from here on I can use the profile.n

[dave]

@Holger, I couldn't find how to parameterise the beam section in Spaceclaim either, so used your workaround method, thanks!n

[dave]

Actually, the workaround doesn't seem to update the beams as I had thought, oh well back to the drawing board!n

[dave]

I managed by defining the cross sections in Design Modeler, thanks Peter. Shame I couldn't get it to work in Spaceclaim.n

[HSS]

well there turns out to be a second part to this workaround:nWB seems to have trouble with cross sections having identical names. With this method, every geometrie update results in an additional cross section in the tree. Its all displayed correctly in WB, however the solver always uses THE FIRST CROSS SECTION WITH THE IDENTICAL NAME! Meaning you will always have the first crossections parameters written into your ds.dat, even though in WB you chosse for example the third entry called Cross SectionWork around part 2:Provide every cross section with an unique name, e.g. the current time and date.nVery unsatisfying, but I didnt yet find any other solution.n