An animatronic body, plus an AI brain you can replace
Degrees of freedom, control interfaces and the boundary between what ships today and what is agreed per project, written for curators, attraction developers and system integrators.
Sourcing, outdoor specification and compliance answers are collected in the buyer guide.

Every line in this document carries a status. Nothing marked per project is included by default, and nothing in development is quoted as shipping.
One creature, two supply layers
The mechanical base is the part the Zigong supply chain does well: steel frame, silicone skin, sculpture and servo mechanics. The AI layer sits on top as a controller and a set of services. They are specified, priced and upgraded separately.
Hardware base
- Steel frame and anti-rust treatment
- Silicone skin, sculpture and paint
- Servo mechanics and drive channels
- Control box, wiring and safety cut-offs
AI layer
- Raspberry Pi 5 interaction controller
- Vision tracking, speech and language
- Jaw and head motion from the audio track
- Local management page and diagnostics
Degrees of freedom
Travel limits are set per model and recorded in the specification, so this table names the axes rather than quoting angles that would not hold across species sizes.
| Axis | Motion | Drive | Status | Note |
|---|---|---|---|---|
| Head yaw | Left and right turn, used for visitor tracking | Servo channel via PCA9685 | Available | Travel limits set per model in firmware |
| Head pitch | Up and down nod, follows the visitor's height | Servo channel via PCA9685 | Available | Combined with yaw for smooth following |
| Jaw | Open and close, driven from the speech output | Dedicated servo channel | Available | Amplitude follows the audio envelope |
| Eyelids | Blink and expression accents | Servo channel, model dependent | Per project | Offered when the head shell allows it |
| Neck lean | Forward and sideways lean of the neck base | Servo or actuator, frame dependent | Per project | Specified with the frame design |
| Mobile base | Walking or wheeled movement | In development on the same controller | In development | Not part of a standard order today |
Interfaces and show control
What the controller exposes today, what is configured on site, and what stays outside the standard build.
- Local management pageConfiguration, camera preview, voice packs, behaviour logic and diagnostics served from the controllerAvailable
- Network modeWhether the controller joins the venue network or serves its own access point is agreed at commissioningPer project
- Sensor inputsExpansion ports reserved for proximity sensors, floor buttons and similar triggersAvailable
- Motor expansionSpare servo channels and drive outputs reserved for later axes or upgraded mechanismsAvailable
- Audio outputSpeaker output with configurable voice packs and playback settingsAvailable
- Third-party HTTP APIExternal control endpoints for integratorsIn development
- DMX show controlNot native; the interface and command set are reviewed per projectPer project
Show control is a boundary, not a feature. The creature runs its own interaction loop, so a venue that cues exhibits from a console needs the interface reviewed before the option is quoted.
Voice, language and behaviour
Voice packs and behaviour logic live on the controller, so a second language or a new scene does not require new hardware. What changes is configuration, not the model.
Behaviour sequences
Scenes are assembled from the management page as ordered steps of motion, speech and audio, with the order of head and jaw channels defined per scene. Integrator scripting is offered as part of an integration package, not as an open SDK.
Content and safety boundaries
Age-appropriate responses and content limits are configured per venue before opening and stored locally, so the character keeps the same rules for every visitor of a session.
Three delivery paths
The same mechanical base reaches the venue by one of three routes, depending on who owns the integration work.
Turnkey exhibit
Hardware, AI layer, commissioning and operator training in one order. The venue receives a creature that is ready for opening day.
AI module on a base
The venue or its contractor builds the mechanical base, and the AI controller, cameras, audio and dashboard are supplied as a module.
Integrator programme
Documentation, channel maps and configuration format are handed to the integrator, who writes language packs and behaviour scenes.
What is not included
- No open SDK or public API today
- No native DMX output
- No walking base in a standard order
- No cloud account required, so no remote hosting service
Integration questions
The mechanical build and the AI layer can be ordered and upgraded separately. A venue can take the steel frame, skin and servo mechanics as a hardware base, then add the AI module when the budget or the programme allows, without rebuilding the creature.
The standard interactive head runs yaw, pitch and jaw on separate servo channels, with the exact axis count and travel set per model. Eyelids and neck lean are added when the shell and frame allow, and the final axis map is written into the specification.
The unit is not a DMX-native fixture. Where a venue cues exhibits from a show console, the interface and command set are reviewed per project, and only then is the option quoted.
Voice packs, audio files and behaviour logic are configured from the local management page. Deeper scripting by an integrator is possible when the project includes the integration package, which documents the configuration format and supported hooks.
External control endpoints are in development. Until they are released, integration requests are handled per project and confirmed in writing, so no API access is promised as an off-the-shelf feature.
Wiring and channel maps, the axis and travel specification, the network and commissioning notes and the maintenance schedule. Documentation scope is agreed with the order, and drawings are shared under the NDA terms of the project.
Ask for the integration notes
Tell us the show-control system, the language set and who writes the behaviour scenes. We reply with the axis map, the interface options and the documentation that fits the project.