How To Ask Robot Building Questions

Get faster, more accurate help by asking clear, focused questions that define a specific outcome.

1. The answer is only as good as the question

Clear, well-structured questions help you and everyone who may search for the same issue later. Concise posts produce quicker, more accurate replies from the community and better results from Athena, our AI support assistant.

Athena uses a large language model (LLM) that depends on the context you provide. If your goal is vague or important details are missing, the response quality falls quickly. The more precisely you describe the desired outcome and the conditions around the problem, the easier it is for Athena — and people — to provide the right solution.

2. What Athena answers best

Athena performs best when a question focuses on a single, clearly defined outcome and includes the context needed to reach that outcome. Posts that mix topics, goals, or unrelated problems make it harder for Athena to identify the intended solution and for community members to help.

  • Best: One topic, one goal, clear success criteria, and enough detail to reproduce or understand the situation.
  • Harder: Multiple topics in one thread, an unclear goal, or a long list of unrelated requests.
  • Worst: A thread where the subject changes mid-stream and the expected outcome is never clearly stated.

3. Always include a clear outcome

Before you post, write a single sentence that defines the outcome you want. This is the "finish line" for your question—what success looks like. Then list the details that affect that outcome: hardware, software versions, exact steps, expected behavior, and actual behavior.

Outcome statement examples:

  • “I want ARC to connect to my EZ-B v4 over Wi‑Fi consistently without timeouts.”
  • “I want this script to move a servo smoothly from 0° to 180° over 2 seconds, then stop.”
  • “I want the camera to detect motion and trigger a single wave action per detection event.”

4. One thread = one topic

If the subject changes while a thread is active, start a new thread. This keeps discussions focused and searchable.

  • Clarity for people: Focused threads keep solutions visible and easy to follow.
  • Clarity for Athena: Athena builds context from the thread; when topics shift, the model may anchor on the wrong theme or miss the intended outcome.

If your new question does not involve the exact same problem and the same desired outcome, create a separate post and link to the original thread if that helps.


Having more threads is better than having a messy single multi-topic thread. This rule not only applies to using Athena, but is also useful for organizing the forum for other users and searching. It is much easier for you and others to follow the conversation when the topic does not change. 

5. Guidelines for asking a good question

  • Start with the outcome:
    • Write one sentence describing the desired result (success criteria).
    • Write one sentence describing what is happening instead (actual behavior).
  • If it’s an issue or bug:
    • Include the exact error message (copy/paste).
    • List numbered steps to reproduce the problem.
    • Provide environment details: OS, ARC/ARCx version, firmware version, device model, and connection type.
    • Attach screenshots, logs, or diagnostic output that clearly show the problem.
  • If it’s “how do I do this?”:
    • Explain what you are trying to build and why (brief paragraph).
    • List what you’ve already tried and the results you observed.
    • Mention which documentation you reviewed, such as the Getting Started Guide.
  • If it’s a programming question:
    • Provide complete code that reproduces the issue (not partial snippets), or a minimal reproducible example.
    • Clearly state the exact behavior you expect from the code.
    • Describe the inputs, sample data, and the exact output you received.
  • Make it easy to scan:
    • Use short paragraphs, headings, and bullet points.
    • Use code blocks for code and error logs so they are easy to copy and inspect.
  • Don’t hijack threads: If your question is not 100% related to the original post and its outcome, start a new thread instead of appending to the existing one.

6. Why properly asking a question matters

The Synthiam forum is most useful when questions and answers stay clear and discoverable. Well-asked questions let the community respond quickly, help Athena give better guidance, and create resources that others can find through search.

Vague questions, mixed topics, or missing details force responders to guess, producing less reliable answers. Over time this reduces the forum's usefulness and makes it harder for everyone to find proven solutions.

Clear questions keep the forum fast, searchable, and genuinely helpful.

7. How Athena can help

Athena can provide strong initial guidance when a question includes a clear outcome and enough context to reproduce the problem. Typical helpful details are the environment, exact steps taken, relevant logs, and what you expect to happen.

Remember: one thread per topic helps Athena stay focused and improves results for everyone who reads the thread later.

8. Sample questions

Scenario 1: Troubleshooting an issue

Outcome: “I want ARC to connect to my EZ‑B v4 over Wi‑Fi without timeouts.”

Question example: “I’m using Synthiam ARC vX.X.X with an EZ‑B v4 and receive: ‘Connection failed: Timeout.’ Steps to reproduce: (1) Power EZ‑B, (2) connect PC to EZ‑B Wi‑Fi, (3) press Connect in ARC. Expected: ARC connects within 5 seconds. Actual: timeout after X seconds. OS: Windows 11. Firmware: vX. Router/AP: [details]. I have restarted the EZ‑B and PC and tried a second device.”

Scenario 2: Learning how to do something

Outcome: “I want my robot to wave once when motion is detected by the camera.”

Question example: “I have the camera connected and can see the feed in ARC. I followed the camera tutorial but am unsure how to trigger a wave script reliably. Can someone show a simple approach or skill combination that detects motion and runs a wave script once per motion event?”

Scenario 3: Seeking design advice

Outcome: “I want to choose servos that can lift a specific payload with smooth motion.”

Question example: “I’m designing a robot arm to mimic human motion. End effector payload ~X grams, arm length ~Y cm, and I want smooth movement rather than speed. What servo torque range should I target, and are there prebuilt arms or example projects that integrate well with Synthiam ARC?”

9. Additional tips

  • Search the forum before posting — your question may already have an answer.
  • Read the Getting Started Guide, which addresses many common questions.
  • Use clear grammar and consistent formatting so your post is easy to read and respond to.

Thank you for contributing to the Synthiam community. Together we make robotics more accessible.