ZGDino
Technical whitepaper v1.0

An animatronic body paired with a replaceable AI brain.

Degrees of freedom, control interfaces, and the boundary between current offerings and project-specific agreements. Written for curators, attraction developers, and system integrators.

Sourcing, outdoor specifications, and compliance responses are collected in the Buyer's Guide.

Engineer wiring a robotic control panel

Every line in this document has a status. By default, nothing marked as per-project is included, and nothing in development is listed as shipped.

AvailablePer projectIn development

One creature, two supply layers

The mechanical base is Zigong's supply chain strength: steel frames, silicone skins, sculptures, and servo mechanisms. The AI layer sits on top as a controller and service suite, with specifications, pricing, and upgrades handled separately.

Hardware base

  • Steel frame with 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 movements from the audio track
  • Local management page and diagnostics

Degrees of freedom

Travel limits are defined per model and documented in the specifications; therefore, this table lists the axes rather than providing angle values that may vary across different model sizes.

AxisMotionDriveStatusNote
Head yawLeft and right turns for visitor trackingServo channel via PCA9685AvailableFirmware sets travel limits per model
Head tiltNods up and down, adjusting to the visitor's heightServo channel via PCA9685AvailableCombined with yaw for smooth tracking
JawOpen and close via speech outputDedicated servo channelAvailableAmplitude follows the audio envelope
EyelidsBlink and expression accentsServo channel, model-dependentPer projectAvailable if the head shell supports it
Neck leanForward and lateral neck base tiltServo or actuator, frame-dependentPer projectSpecified by the frame design
Mobile baseWalking or wheeled locomotionIn development on the same controllerIn developmentNot included in today's standard order

Interfaces and show control

What the controller currently exposes, what's configured on-site, and what falls outside the standard build.

DinoAi control system
  • Local management pageConfiguration, camera preview, voice packs, behavior logic, and diagnostics served by the controllerAvailable
  • Network modeWhether the controller joins the venue network or provides its own access point is determined during commissioning.Per project
  • Sensor inputsExpansion ports reserved for proximity sensors, floor buttons, and similar triggersAvailable
  • Motor expansionSpare servo channels and drive outputs reserved for future axes or upgraded mechanismsAvailable
  • Audio outputSpeaker output with customizable 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 manages its own interaction loop; therefore, any venue that cues exhibits from a console must have the interface reviewed before receiving a quote.

Voice, Language, and Behavior

Voice packs and behavior logic run on the controller, so switching to a second language or a new scene doesn't require new hardware. Only the configuration changes—not the model.

Behavior sequences

Scenes are built on the management page as ordered sequences of motion, speech, and audio, with head and jaw channel order defined per scene. Integrator scripting is included in an integration package, not available as an open SDK.

Content and safety boundaries

Age-appropriate responses and content limits are configured per venue before launch and stored locally, ensuring consistent rules for all visitors within a session.

Three delivery options

The same mechanical base reaches the venue via one of three routes, depending on who owns the integration work.

Available

Turnkey exhibition

One order for hardware, AI layer, commissioning, and operator training. The venue receives a fully ready creature for opening day.

Per project

AI module mounted on a base

The venue or its contractor builds the mechanical base; the AI controller, cameras, audio, and dashboard are supplied as a module.

Per project

Integrator Program

Documentation, channel maps, and configuration formats are provided to the integrator, who creates language packs and behavior scenes.

What's not included

  • No open SDK or public API available today.
  • No native DMX output
  • No walking base in standard order
  • No cloud account needed, so no remote hosting service required.

Integration questions

The mechanical build and AI layer can be ordered and upgraded separately. A venue can start with the steel frame, skin, and servo mechanics as a hardware base, then add the AI module later when budget or program requirements allow—without rebuilding the creature.

The standard interactive head controls yaw, pitch, and jaw on separate servo channels. The exact axis count and travel range are defined per model. Eyelids and neck lean are included if the shell and frame support them, with the final axis mapping documented in the specification.

The unit is not a DMX-native fixture. When venues cue exhibits from a show console, the interface and command set are evaluated on a per-project basis; this option is quoted only after such review.

Voice packs, audio files, and behavior logic are configured via the local management page. Deeper scripting is available for integrators when the project includes the integration package, which documents the configuration format and supported hooks.

External control endpoints are under development. Until release, integration requests are handled on a per-project basis and require written confirmation. API access is not offered as an out-of-the-box feature.

Wiring and channel maps, axis and travel specifications, network and commissioning notes, and the maintenance schedule. Documentation scope is confirmed with the order; drawings are shared under the project's NDA terms.

Request integration notes

Tell us about your show-control system, preferred language, and who creates the behavior scenes. We'll respond with the axis map, interface options, and project-specific documentation.

Request a Quote