Skip to main content

Skye and Luna: first teleoperation

Skye and Luna support full-body teleoperation with Apex. Each delivered robot integrates a Tianzhun 003 control unit, four cameras, and the hardware required for teleoperation. The operator wears a Pico headset, arm units, one waist tracker, and two leg trackers. Skye maps motion to both arms, BODY, and LIFT, while Luna maps motion to both arms, BODY, and legs.

This page covers the minimum sequence from power-on to first full-body teleoperation. For buttons, recording, playback, and logs, see Classic Apex Teleop.

Product details: Skye, Luna.

1. Kit and product differences​

ComponentDescription
Skye robotExecutes dual-arm, 2-DOF BODY, and 1-DOF LIFT teleoperation; it has no knee joints
Luna robotExecutes dual-arm and 6-DOF BODY teleoperation with a knee-style body structure
Tianzhun 003 control unitRuns Apex and ROS 2 control services
Four camerasProvide a four-tile first-person and environment view
Pico headsetDisplays video and provides head tracking
Wearable arm units (left/right)Capture operator arm motion
Waist trackerCaptures torso pose
Leg trackersTwo trackers capture lower-body motion for Skye BODY/LIFT or Luna leg mapping
Host PCRuns the classic Apex Teleop interface

Skye/Luna standard devices and accessories

Standard accessories​

AccessoryQtyDescription
Pico headset1Headset used for Skye/Luna full-body teleoperation
Wearable arm units (left/right)1 eachCapture arm motion
Waist tracker1Captures torso pose
Leg trackers2Capture lower-body motion for Skye BODY/LIFT or Luna leg mapping
Ethernet cablesSeveralConnect the robot, host PC, network device, and headset adapter
Type-C Ethernet adapter1Connects Pico to the wired LAN

Software​

SoftwareLocationDescription
Apex controller softwareTianzhun 003Current source-review snapshot is v1.0.6.95g-beta-10-g14cfc0d; use the customer package listed in the delivery manifest
Teleop serviceHost PCUse the matching version from the same delivery release; processes teleoperation data
Apex frontendHost PCUse the matching version from the same delivery release; connects the robot, switches modes, records, plays back, and displays logs
Apex Pico clientPico headsetNetwork connection, video display, and full-body teleoperation input

To install or update, see Install or update Apex.

Product differences​

  • Skye has a 2-DOF BODY and 1-DOF LIFT with no knee joints. Luna has a 6-DOF knee-style body structure.
  • Both Skye and Luna use one waist tracker and two leg trackers for full-body mapping. Marvin Pro primarily supports dual-arm teleoperation.
  • Skye/Luna uses Pico waist and leg tracking and does not use Meta Quest as the standard full-body headset.
  • Skye/Luna currently uses the classic Apex Teleop interface.

2. Wear the trackers​

  • Pico headset: adjust for a clear view and secure fit.
  • Wearable arm units: distinguish left and right and keep elbow motion unobstructed.
  • Waist tracker: wear it on the back in the specified orientation.
  • Leg trackers: install both trackers at the specified positions for full-body tracking. Skye still requires the leg trackers even though the robot has no knee joints.
  • Check battery, connection, and tracking state before use.

Install the left and right units and the leg trackers without swapping sides. You calibrate the trackers in the headset client when you connect (step 7).

3. Network wiring​

When Skye/Luna is shipped, the Tianzhun 003 control unit is already integrated inside the robot. On the user side, network, peripheral, and headset connections are mainly completed through the exposed rear interfaces. The overall wiring principle is the same as Marvin Pro: the robot, host PC, headset, and router / switch must be on the same LAN.

Connect the network as follows:

Headset Ethernet Port

For wired headset networking, connect a Tianzhun controller to Ethernet port 1 and a Lingjing Thor controller to Ethernet port 2. Both controllers use 6.6.7.100 as the default connection address. Do not interchange the two ports. If the site network was changed, follow the delivered configuration.

  1. Connect the robot rear Ethernet port to the router / switch.
  2. Connect the host PC to the same router / switch.
  3. Connect the headset to the same router / switch through the Type-C Ethernet adapter.
  4. Confirm that the robot, host PC, and headset are on the same subnet.

Skye/Luna network wiring reference

Rear interfaces differ between the two robots; see Skye rear interfaces and Luna rear control panel.

Wiring check​

Before powering on and starting the system, check each item:

Check itemRequirement
Robot rear Ethernet portEthernet cable is firmly inserted and connected to the router / switch
Host PC networkOn the same LAN as the robot
Headset networkWired access through the Type-C Ethernet adapter
Power and emergency stopPower connection is normal and the emergency stop button is released
Cable statusEthernet cables, adapters, and power cables are not loose

Notes​

  • Headset Wi-Fi is not recommended for teleoperation. Use the wired network connection first.
  • Connect the headset cable to port 1 for a Tianzhun controller and port 2 for a Lingjing Thor controller.
  • After wiring is complete, proceed to environment configuration and startup debugging.
  • If the host PC cannot connect to the robot, first check the Ethernet cable, router / switch, power, and IP subnet.

Network settings​

DeviceDescription
Tianzhun 003Default examples use 6.6.7.100; use the actual site address if changed
Host PCSame subnet as Tianzhun 003, with no conflict
PicoIndependent address on the same subnet; the client connects to Tianzhun 003
ping 6.6.7.100

Pico must not use the same IP as Tianzhun 003. When changing the site subnet, update the host, Pico, and network-service configuration together.

4. Before startup​

  • Connect the robot, host PC, network device, and Pico according to Hardware Wiring.
  • Release the emergency stop and clear the workspace.
  • Put the host PC and the robot's integrated controller on the same subnet.
  • Charge and correctly wear the Pico headset, waist tracker, and leg trackers.

5. Connect to the controller​

Select the address and account for the controller installed in the device. These are factory defaults; use the delivery configuration if the IP address, username, or password has been changed.

ControllerDefault IPUsernameDefault password
Tianzhun 0036.6.7.100nvidianvidia
Lingjing Thor6.6.7.100user1

Tianzhun 003 control unit:

ping 6.6.7.100
ssh nvidia@6.6.7.100

Lingjing Thor controller:

ping 6.6.7.100
ssh user@6.6.7.100

Enter the corresponding default password on the first SSH connection. If the delivered device already uses a changed password, do not attempt to restore the factory default.

Start the Apex backend service:

sudo systemctl start apex-backend.service
sudo systemctl status apex-backend.service --no-pager

After every power-up, start the cameras before you teleoperate.

6. Start classic Apex Teleop​

  1. Open Apex Teleop.
  2. Enter the current controller IP and press Enter.
  3. Start Robot and verify that the 3D model matches the physical robot.
  4. Start Teleop and the network module. Camera is optional.
  5. Use the robot start control to set the robot Ready.
  6. Select Impedance Mode, then execute Home.
  7. Verify both arms and the physical robot pose. For Skye, also verify BODY and LIFT; for Luna, verify BODY and the knee-style body structure.

7. Connect Pico​

Skye/Luna uses Pico with waist and leg trackers for full-body teleoperation. Follow the Pico headset guide for developer mode, network, and Apex client setup.

To switch among full-body, arms-only, arms-and-head, or mobile-base teleoperation, follow Teleoperation Modes and Input Sources. Release both controller enable buttons before changing the motion range.

After connection, test small arm motions first. For Skye, verify torso and lift mapping; for Luna, verify torso and leg mapping. Increase the range only after all directions are correct.

Before connecting, put on and calibrate the body trackers. In the headset client, confirm the operator height, the controller IP, and the end effector, then connect. When the VR indicator in Apex Teleop turns green, press Y on the left controller to start, and hold the side grip to operate.

8. Quick checks​

SymptomCheck
Cannot connect to the controllerController type, IP, account, host subnet, and cable
3D and physical poses differRobot module, model configuration, and startup log
Teleop unavailableRobot running and Ready state
Pico cannot connectNetwork module, headset IP, cable, and client settings
Arms move but BODY/LIFT or lower body does notModel configuration, tracker charge, placement, and tracking state
Camera is blackCamera module and camera connection
No teleoperation motionImpedance Mode, Home, and headset connection