Staircases and walkways - best approach - tip tricks

Staircases and walkways - best approach - tip tricks

bespel
Advocate Advocate
1,543 Views
4 Replies
Message 1 of 5

Staircases and walkways - best approach - tip tricks

bespel
Advocate
Advocate

Hi,

in your opinion/experience which is the best approach to create/manage stairs and walways (plants) in Inventor?

Advices? Tip tricks?

Thanks!

0 Likes
1,544 Views
4 Replies
Replies (4)
Message 2 of 5

kacper.suchomski
Mentor
Mentor

Parameterization.

From the simplest to iLogic configurators.

 


Kacper Suchomski

EESignature


YouTube - Inventor tutorials | LinkedIn | Instagram

Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.


Message 3 of 5

johnsonshiue
Community Manager
Community Manager

Hi! I believe there are quite a few good examples showing this workflow, "Autodesk Inventor ilogic configurable staircase."

Here are two links for you to take a look.

 

https://www.youtube.com/watch?v=JP3FaDWjwmA

https://forums.autodesk.com/t5/inventor-ilogic-and-vb-net-forum/automated-stairs-with-ilogic/td-p/92...

 

Many thanks!

 



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
Message 4 of 5

cadman777
Advisor
Advisor

I've been making platforms an stairs for over 20 years (not bragging).

Off the top of my head:

1. All depends on what kind of stairs (mainly) you want to make.

2. Most of the architectural stairs are one-off's and must comply with local standards (at least).

3. Most of the industrial stairs are made to code or other industrial standards.

4. You have a choice to use structural steel software or Inventor (or other parametric solids modeler).

5. And don't forget about the variation in types of materials used.

6. There is nothing easy about setting up a system for doing stairs with any software.

    A lot can be said about this but I'll leave it at that for the moment.

    Suffice to say that 'the devil is in the details'.

 

With all that in mind, this is how I approach it:

All architectural stairs I would do with a program like Inventor.

The reason is b/c there are too many pesky details that change on a per-customer basis.

You would pull your hair out doing that in a structural steel app.

The platforms are best done in a structural steel app, NOT Inventor.

It all has to do with the connections and the automated drawings.

I don't have piles of money to throw at buying and customizing a structural steel app.

So I use Inventor for stairs (and unfortunately for platforms too).

Industrial stairs are way easier to make a system for than architectural stairs.

But I'm not sure which is easier: To make a library of stair types and reuse them or to use iLogic or both?

Since I'm not a good coder, I use a library.

Ladders and other types of egress equipment are included in this.

I like to use industrial ladders as an example b/c there aren't many variations in ladder types in the USA.

So I've made a couple types and just reused them on other jobs with not too much scrubbing of drawings.

I find most of the work involves fixing the drawings.

The key here is in knowing how you model stairs stringers, tread types, railings and connections.

Once you layout all of that in a spreadsheet, and figure out what parts you need for the various combinations, then you'll be off to a good start. But to get there, you would need to get your hands on the industrial or in-house standard that's used by your customer.

That's a brief survey off the top of my head based on my years of experience doing my fair share of platforms and railings.

 

Addendum:

I use FrameGenerator for platforms and railings, but use basic Inventor for stringers & Treads and all the connections.

... Chris
Win 7 Pro 64 bit + IV 2010 Suite
ASUS X79 Deluxe
Intel i7 3820 4.4 O/C
64 Gig ADATA RAM
Nvidia Quadro M5000 8 Gig
3d Connexion Space Navigator
Message 5 of 5

3D4Play
Collaborator
Collaborator

piling on johnson, without writing a diatribe on stairs:

If you work within parameters run >11<12 and rise >7<8 for architectural purposes that will result in code compliance for all but industrial (OSHA) requirements, which allows an exception for rise and run if the application is not assembly, residential or pubic access. You can set up parametric equations to solve both problems (rise, and run), then tie your stair pattern to those parameters. 

 

That's a generic description, but should be enough to get you productive.