Ask the engineering community | Engineer Marketplace

Your question

Title*Write it as the specific question you want answered, not a topic.

Board*

Post type*

The problem*Include the system, the condition, the numbers, what you already checked, and what you expected versus what happened.

Standards citedNaming the code gets you answers from people who work to it.

Software involved

TagsComma separated. Three or four specific tags beat ten broad ones.

Cancel

Before you post

State the system, the loading or operating condition, and the code you are working to
Say what you have already checked and ruled out — it stops people repeating your work
Give the numbers: sizes, grades, load cases, measured values, software version
Say what you expected to happen and what actually happened
Ask one answerable question rather than three vague ones

Do not post confidential materialThe community is public and indexed. If your question involves a client's drawings, a product design or anything under NDA, post a private or NDA-gated project instead.

Community answers are not certified adviceNobody answering has reviewed your full design. Use answers to understand a problem and narrow your options — then engage an engineer properly for anything that gets built, submitted or certified.

Need more than an answer?

If the question is really a scoping problem, a 45-minute consultation with a specialist will settle it faster than a thread — and you get a written recommendation either way.

Browse consultations

Questions

Posting to the community

Will an engineer actually answer this?

Questions that carry real technical detail almost always get answered, usually within hours. Questions that state a symptom with no context often sit unanswered, because nobody can say anything useful without guessing. The difference is entirely in how the question is written.

Is an answer here engineering advice I can build on?

No. Community answers are professional discussion, not a certified engineering opinion, and nobody answering has reviewed your full design. Use answers to understand a problem and narrow your options — then engage an engineer properly for anything that gets built, submitted or certified.

Can I post something confidential?

Do not. The community is public and indexed. If your question involves a client's drawings, a product design or anything under NDA, post a private project instead — private and NDA-gated projects exist precisely for this.

How does ranking work?

Correct answers, peer endorsement from verified engineers, accepted answers and cited standards all carry weight. Raw posting volume does not. Answering three questions well is worth more here than posting thirty times.

Your question

Title*Write it as the specific question you want answered, not a topic.

Board*

Post type*

The problem*Include the system, the condition, the numbers, what you already checked, and what you expected versus what happened.

Standards citedNaming the code gets you answers from people who work to it.

Software involved

TagsComma separated. Three or four specific tags beat ten broad ones.

Questions that state the assumptions get answered in hours

Your question

Posting to the community

Questions that state the assumptions get answered in hours

Your question

Posting to the community