On a phone, select View → Show all to reveal Link AI. After Wi-Fi connects, the LED matrix shows the last IP octet for about one minute. An unbound Duck repeats a spoken instruction three times to open its current IP in a browser and complete AI binding.

Bind the complete audio/video robot to an AI agent, then verify the microphone, speakers, camera, light, ToF and motion. The cockpit is at http://<board-ip>/; leave the robot stationary and supported during the first audio tests.

Choose the service region

RegionAgent serviceDefault language
GlobalGlobal agent platformEnglish; wake word “Hey Ducky”
ChinaChina agent platformChinese; use the wake word shown in that region’s interface

Select the region in the cockpit’s AI voice settings before binding. The saved selection takes priority. Without a saved selection, the App checks existing binding data; when both regions are present it selects China. Accounts and bindings are separate between regions, and changing the selector does not migrate a bound device.

Bind the robot

English agent binding view.
English agent binding view.
  1. Create or sign in to an account on the selected platform and prepare an agent. If the robot belongs to another account, have the previous owner unbind it first.

  2. In Chrome or Edge on a supported device, use the cockpit’s Bluetooth binding entry. Turn on Bluetooth, grant the requested permission and choose the nearby Duck.

  3. On an iPhone, use the supported Global app or the China WeChat mini program for the selected service instead of relying on Web Bluetooth. The cockpit provides the corresponding entry.

  4. Finish binding and confirm the robot is shown as bound. Stop microphone monitoring, recording and speaker tests, then wait for the agent to be ready before speaking.

Have the first conversation

  • For Global service, say “Hey Ducky”, wait for the listening prompt, then speak a short question.

  • Set a moderate speaker volume. In a noisy room, move closer and pause until the listening indication appears.

  • If no speech is heard, test speakers and microphone separately in Camera and audio. A successful binding does not by itself prove that audio hardware works.

Verify the complete robot

ToF still undetected after reboot: If the connected ToF is still missing after the acceptance reboot, mark it “pending retest.” Manually turn Duck’s power switch off and on once. After startup, check /api/tof/status again for state=ranging, fresh=true, an increasing seq and valid_zones > 0. Do not mark the sensor as passed before retesting.

FunctionAcceptance check
CameraLive preview changes when the scene moves; a photo can be captured
Fill lightThe light responds to both on and off commands
SpeakersTest audio is audible from the connected speakers
MicrophoneMonitoring or a short recording captures sound near the robot
ToFA nearby object changes the live grid and valid distance readings
AI voiceWake, ask a question and hear the answer
MovementDefault pose and a short low-speed walk work after calibration

Completion check

  • Every function above has been checked; log any unavailable module separately.

  • Understand Stop versus Torque off before handing the robot to another user.

Next: Everyday power, walking and actions