[Question] Treppenmodellierer - Eingabe Fixpunkt Austritt


Hallo,

wie kann ich erreichen, das der Treppenmodellierer die Auftrittsbreite und Steigung zwischen zwei Fixpunkten aufteilt?
Kann ich den unten und oberen Punkt nicht in der Isometrie eingeben? Das wäre das einfachste, ich schaffe es nicht....
Wenn nicht 3D wie fixiere ich den oberen Austrittspunkt?

Gruß Jürgen
Allplan V10 bis V2024

Pièces-jointes (1)

Type: image/png
Téléchargé 375 fois
Size: 367,56 KiB

Show most helpful answer Hide most helpful answer

Hallo Jürgen,

...so einfach ist das nicht!
Der neue Treppenmodellierer braucht eine fixe Autrittslänge zu automatischen Berechnung der Stufen
zwischen den Podesten. Die Auftrittslänge lässt sich also nicht aus der Lauflänge berechnen, sobald
Podeste im Spiel sind.
Bei einer gerade Treppe könnte man das natürlich machen, aber dann kommen noch andere Probleme
Deiner Leitertreppe hinzu: Die Stufentiefe ist konstant, und nicht gleich der Auftrittslänge!

Auch das "Picken" des Fix-Punktes oben ist eigentlich bereits drin, allerdings nur im Grudriss als Endpunkt der Achse! Die zugehörige Höhe kann man sich vorher abgreifen, und dann in den Eingabefeldern die Höhe und Auftrittsbreite ausrechnen! Es geht also, wenn auch nicht besonders komfortabel!

Deine "Industrie-Leiter" war leider nicht im Fokus des Treppenmodellierers, da es keine (notwendige) Treppe ist!
Ich denke, mit dem neuen Treppenmodellierer kann man mehr als 80% der gängigen Treppen leichter und detaillierter erzeugen. Falls doch etwas nicht geht, gibt es ja noch die "alte" Treppe!

Und damit auch Du zufrieden bist, habe ich mal ein SmartPart gebaut, mit dem Du einfach Start- und Endpunkt
zeigen brauchst, und alles wird automatisch berechnet.
Diese Leitertreppe kann als Stufen detaillierte Gitterroststufen mit fixer Tiefe haben, und die Wangen können aus U-Profilen sein.

Grüße Jörg

Pièces-jointes (2)

Type: image/png
Téléchargé 114 fois
Size: 68,69 KiB
Type: application/xml
Téléchargé 1158 fois
Size: 39,17 KiB
41 - 50 (69)

some hints about HANDLE:

The three values behing HANDLE are coordinates of 3 Points. The last of the 3 HANDLE statements describes the Referenz point. It is use for determine the direction in which the length between base point (1st statement) and handle point (2nd statement) is measured.
The direction for positive values is determined from reference point to base point! This means that the reference point usually points in the opposite direction to the handle point!

In your case is following right, if you want wo measure l_t in positive X-direction

HANDLE 0 , 0 , 0 , id , "l_t" , 1 !Base Point
HANDLE l_t , 0 , 0 , id , "l_t" , 2 !Handle Point
HANDLE l_t - 1 , 0 , 0 , id , "l_t" , 3 !Ref Point

Cité par Nemo
some hints about HANDLE:
The three values behing HANDLE are coordinates of 3 Points. The last of the 3 HANDLE statements describes the Referenz point. It is use for determine the direction in which the length between base point (1st statement) and handle point (2nd statement) is measured.

The direction for positive values is determined from reference point to base point! This means that the reference point usually points in the opposite direction to the handle point!
In your case is following right, if you want wo measure l_t in positive X-direction
HANDLE 0 , 0 , 0 , id , "l_t" , 1 !Base Point

HANDLE l_t , 0 , 0 , id , "l_t" , 2 !Handle Point

HANDLE l_t - 1 , 0 , 0 , id , "l_t" , 3 !Ref Point


Thank you for clarification but with your script the 2_nd handle (handle point) is not on X=0. I want that 2_nd handle it to be on X=0 and move the steps in direction -X. When I move the steps in -X the dimension of the l1 change (increases towards -X).

Again, as I Wrote:
In your case is following right, if you want wo measure l_t in positive X-direction

HANDLE 0 , 0 , 0 , id , "l_t" , 1 !Base Point
HANDLE l_t , 0 , 0 , id , "l_t" , 2 !Handle Point
HANDLE l_t - 1 , 0 , 0 , id , "l_t" , 3 !Ref Point

I you want to have another handleposition, just Do it!
Without the script and seeing what meaning of "l_t" is, I can (and will) not give further support!
Please open another thread for Questions with SmartParts handles.
I will not give further answers in this thread!

Cité par Danilos
Hi Nemo, again about the stairs I want make command "group_union" for to add 4 group in only one group because maybe I solve the problem area style in section. It's correct the code ? Thank you for help.
result_a = ""
result_a = GROUP_UNION ( "sol" , "gra" )
result_b = ""
result_b = GROUP_UNION ( "ped" , "alz" )
result_t = ""
result_t = GROUP_UNION ( result_a , result_b )
GROUP_PLACE result_t

Hi Nemo, do you know which 3D shapes Allplan uses to make the components of a stair (structure, tread, riser) in the traditional stair module.

Line3D, BSPline3D, Polyhedron3D and BRep3D for winding staircase
BRep3D is not createable in SmartParts. There you can only create Polyhedron3D.

Cité par Nemo
Line3D, BSPline3D, Polyhedron3D and BRep3D for winding staircase

BRep3D is not createable in SmartParts. There you can only create Polyhedron3D.


Thank you for clarification! For Polyhedron3D what do you mean? Basic shapes or Planar shapes or Shapes from polylines? Can you make some example command for smart part?

All functions in a SmartPart-Script which create 3D-Solids resulting in Polyhedrons.
All faces of a Polyhedron are flat!
So for construction of Polyhedrons are only points, lines and polylines with straight segments permitted.
Curves such as circular arcs and splines must be polygonized beforehand.

Cité par Nemo
All functions in a SmartPart-Script which create 3D-Solids resulting in Polyhedrons.
All faces of a Polyhedron are flat!
So for construction of Polyhedrons are only points, lines and polylines with straight segments permitted.
Curves such as circular arcs and splines must be polygonized beforehand.

Ok, thank you for clarification.

Cité par Nemo
You must have a mistake in your script!

I cannot help you, if I don't have the whole SmartPart.
In my Stair it works fine!


Hi Nemo, I'm still having trouble with area styling in sections. If I section a stair built with the traditional Allplan module, the area style in the associative section is correct on all the components (structure, treads and risers) while in the stair built with smartpart like yours, you see the area style of only one component (the first appearing in the 3d script) and the other components remain without any area style. Is there any other way other than SECT FACESTYLE to define the area style in the script? Thank you.

There is no other option except SECT FACESTYLE.

Without seeing the complete script of the SmartPart, it is impossible to say where the error is.
Look at my staircase, there it works perfectly.

I can not help you!

41 - 50 (69)

https://campus.allplan.com/ utilise des cookies  -  Plus d'informations

Accepter