Public User Manual · RSAP v1.3.0 · Commercial configuration

Talk naturally. RSAP responds with character.

Voice, conversation, memory and motion guidance for the commercial RSAP configuration. Orion is his voice and xAI Grok powers conversation.

OrionCurrent voice
GrokAI service
AlwaysSpeaking gestures
Available Commercial capabilityGrok only One AI providerPrivate No calendar connection

1. RSAP 1.3.0 at a glance

RSAP combines a RoboSapien X body with a Raspberry Pi and Pico AI retrofit. Version 1.3.0 provides natural conversation, memory, motion, a startup greeting and gestures while speaking.

Voice

Orion is RSAP’s current voice. His name is pronounced “are sap.”

Wake

Startup performs the WAKE_UP maneuver and gives the user a spoken greeting.

Motion

Motion stays enabled. RSAP uses varied speaking gestures, with TALK_BACK used sparingly.

2. Talk with RSAP

Speak naturally and ask follow-up questions as part of the same conversation. RSAP uses xAI Grok for conversational responses in the commercial configuration.

Commercial AI configuration: Grok is the only supported AI service. The commercial RSAP does not use OpenAI or switch between alternate AI providers.

Good question styles

  • Ask a direct question.
  • Add detail when the subject is ambiguous.
  • Use a natural follow-up while the topic is still active.

Conversation tips

  • Speak at a normal pace and volume.
  • Wait for RSAP to finish his reply.
  • Repeat or rephrase if room noise masks a phrase.

3. Supported languages

The commercial RSAP supports conversation in five languages through xAI Grok:

English

Default language

Spanish

Español

French

Français

Portuguese

Português

Italian

Italiano

RSAP can follow a supported language when you speak it or when you explicitly ask him to switch. A language change keeps the current conversation topic.

Greek is not supported in the commercial version.

4. Hearing and reply timing

RSAP uses half-duplex audio. Begin speaking after Orion finishes; speech spoken over his reply may be discarded to prevent RSAP from hearing his own speaker.

If RSAP misses you: wait for his speech and movement to finish, face the microphone, then repeat the sentence clearly. Mechanical noise, room noise and distance can reduce recognition accuracy.

The audio input uses noise controls to reduce false triggers, but a loud impact or nearby sound may still be detected.

5. Voice and speech

Orion is used for startup greetings, conversation and shutdown farewells. RSAP keeps the same voice and personality across ordinary user interactions.

Wake greeting

RSAP greets the user after the startup maneuver completes.

Conversational replies

Responses can include explanation, context and personality rather than being limited to short command acknowledgements.

6. Motion and gestures

Gestures run while RSAP speaks. He varies the gesture selected for a reply and avoids relying on the same movement every time.

Conversation gestures

  • BURP for attention
  • WHISTLE for bewilderment
  • OOPS for disbelief, surprise or humour
  • ROAR for surprise or celebration

Reserved behavior

  • TALK_BACK is used sparingly.
  • Startup uses WAKE_UP.
  • Shutdown uses the goodbye gesture.

7. Memory and privacy

RSAP can retain supported conversational memories so later exchanges can use established facts and preferences. A request to remember something is separate from temporary conversation context.

No calendar connection: the commercial RSAP does not connect to Google Calendar or any other calendar service. Calendar questions are treated as ordinary conversation and cannot read, create, change or delete personal events.

Do not speak information near RSAP that you would not want nearby people to hear in his spoken response.

8. Restart and shutdown

A software restart restarts RSAP’s service and repeats the normal wake behavior. An explicit shutdown command triggers the goodbye gesture and farewell, followed by STOP, POWER_OFF and the Linux shutdown sequence. The physical robot power switch remains available to the owner.