Skip to main content

Earlier Marvin Pro (Orin)

This page covers Marvin Pro units delivered with an NVIDIA Jetson Orin main controller, a separate camera deserializer board, and a router on the 192.168.10.x network. For current units with a Tianzhun controller, use Wiring and Marvin Pro: first teleoperation. Software compatibility compares the two versions.

System components​

The Marvin Pro teleoperation system mainly consists of the robot body, robot controller, Orin main controller, camera deserializer board, VR headset, router, and data recording media.

CategoryDeviceDescription
Robot sideDual-arm robot bodyExecutes teleoperation commands
Robot sideRobot controllerReceives commands from Orin and the control system
Power and safety48 V main power supply220 V to 48 V switching power supply
Power and safety12 V controller power supplyPowers the controller and related peripherals
Power and safetyEmergency stop boxProvides on-site safety protection and emergency stop
Main control and perceptionNVIDIA Jetson Orin main controllerRuns KernelMind Apex and ROS 2 nodes
Main control and perceptionCamera deserializer boardSupports up to four GMSL camera inputs
Operator sideVR headset (Meta Quest) and controllersProvides first-person view and operator input
Network and dataRouter and Ethernet cablesConnects the robot controller, Orin, and VR headset adapter
Network and dataUSB driveUsed for data recording; volume label must be BAG_STORAGE

PRO equipment list

Accessories​

Standard​

AccessoryQtyDescription
VR headset (Meta Quest)1Provides immersive first-person operation view
Controllers (left/right)1 eachControl arm motion and gripper opening/closing
Router1LAN core connecting Orin, controller, and headset
Ethernet cablesSeveralWired connection for stable low-latency transmission
USB drive (label BAG_STORAGE)1Stores ROS bag and MP4 recording data under recorded_bags by default
Type-C data cable1Used for ADB debugging or headset APK installation
Type-C Ethernet adapter1Connects the headset to the wired LAN

Optional​

AccessoryDescription
Manus data glovesCapture fine finger motion; used with Wuji Hand
Wuji HandDexterous hand end effector that receives glove motion commands
Foot pedal (three-key)Maps controller enable actions to foot input; used for motion-capture glove / dexterous hand teleoperation scenarios

Foot pedal key functions:

KeyFunction
Key 1 (left key)Enables both left and right controllers together
Key 3 (right key)Moves both arms back to the Home position

Foot pedal connection example

On Orin units, the foot pedal and incremental teleoperation mode are enabled by factory default.

Software​

Software moduleInstallation locationDescription
KernelMind Apex Orin-side packageOrin main controllerkernelmind-apex_<version>_arm64.deb; provides ROS 2 nodes, motion control, camera, and recording services
KernelMind Apex headset appMeta QuestKernelMind_Apex_meta_<version>.apk; provides the VR teleoperation interface
Host teleoperation softwarePCConnects to Orin, starts the robot, switches modes, records data, and replays data

Network​

ItemDefault / Description
Dual-arm controller IP192.168.10.190
Orin network adapter IP192.168.10.123
Orin dual-arm connection IP192.168.10.190; must match the dual-arm controller IP
Router IP192.168.10.1
Headset Apex app connection IP192.168.10.123; must match the Orin IP
SSH login to Orinssh marvin@192.168.10.123
Login credentialsUse the credentials supplied with the device; they are not published here
ItemSpecification
Operating system (Orin)Ubuntu 22.04 ARM64
Operating system (host development PC)Ubuntu 22.04 AMD64
Robot frameworkROS 2 Humble
Main control hardwareNVIDIA Jetson Orin
HeadsetMeta Quest (VR-side APK)
Package formatkernelmind-apex_<version>_arm64.deb

When an independent router is the LAN gateway, the DHCP gateway must point to the router. Use the Orin address only when Orin is explicitly configured to provide the network service without an independent router.

When changing the DHCP subnet, first assign the Orin Ethernet interface a static address in the new subnet. Otherwise, the DHCP service may fail to listen. A network administrator or technical support should coordinate subnet changes.

Wiring​

Wiring an Orin unit covers the arm power supply and communication, the Orin and its camera deserializer board, and the network.

Disconnect the main power before wiring. Confirm that all Ethernet cables, power cables, and camera harnesses are firmly connected before powering on.

Arm power and communication​

Complete the following wiring while the main power is disconnected:

  1. Connect the dual-arm robot 48V+ / 48V- to the positive and negative DC outputs of the 220V-48V switching power supply.
  2. Connect the discharge module 48V+ / 48V- in parallel to the same 48 V power supply.
  3. Connect the emergency stop box in series to the robot emergency stop control loop.
  4. Connect the left-arm and right-arm EthCart Ethernet ports to the corresponding robot controller ports.
  5. Connect the 12V power supply to the robot controller power input.
  6. Connect the uplink Ethernet cable (Cable 1) to the robot controller network interface.

Robot wiring physical reference

Wiring notes:

  • 48V+ and 48V- polarity must be correct. Reverse connection is strictly prohibited.
  • Release the emergency stop button before starting the system.
  • When using the system for the first time or after replacing the controller, confirm that the robot controller IP is 192.168.10.190.
  • During power-on, turn on the 220V-48V switching power supply first, then the robot controller 12V power supply.

Orin and camera deserializer board​

The camera deserializer board is installed at the bottom of Orin and supports up to four GMSL camera inputs. During installation, remove the Orin base first, install the deserializer standoffs and board, then reinstall the base screws.

Camera interface mapping:

Deserializer interface numberCorresponding camera
8Left-eye camera
6Left-wrist camera
7Right-wrist camera
0Right-eye camera

When connecting cameras and peripherals, connect them in order:

  • Camera harnesses
  • USB drive, label must be BAG_STORAGE
  • Ethernet cable 2, connected to Orin
  • Deserializer board power
  • Orin power

Deserializer wiring diagram

Network cables​

The robot controller, Orin, and VR headset adapter must be connected to the same router through Ethernet, ensuring that all three are on the same LAN.

CableConnection target
Cable 1Connects to the robot controller
Cable 2Connects to Orin
Cable 3Connects to the VR headset adapter

PRO network connection diagram

Default network parameters:

DeviceDefault IP
Robot controller192.168.10.190
Orin main controller192.168.10.123
Router192.168.10.1
Headset Apex app connection IP192.168.10.123

Move the arms to the initial pose​

Use fxstation or MarvinPlatform to move both arms to the initial horizontal end pose before teleoperation. The figure below uses the left arm as an example; the right arm follows the same procedure.

Initial horizontal end pose setup

Procedure:

  1. Enter the robot IP address, default 192.168.10.190, and connect to the robot.
  2. Switch the robot arm to Position Mode.
  3. Switch to Joint Follow mode.
  4. In Joint Follow mode, first return to zero position, then write the target points:
    • Left arm: [0, 0, 0, 0, 0, 0, 0] -> [90, -90, -90, -90, 0, 0, 0]
    • Right arm: [0, 0, 0, 0, 0, 0, 0] -> [-90, -90, 90, -90, 0, 0, 0]
  5. Click Add Point to add the current point to the trajectory list.
  6. Click Run. The default speed is 20%. Move the arm to the target pose.
  7. Exit the software after motion is complete.

Before moving the robot, confirm that there are no people, devices, or obstacles within the arm motion range.

Power-on check​

StepOperationCheckpoint
1Turn on 48 V main powerConfirm robot-side power is normal
2Turn on controller 12 V powerConfirm the robot controller starts normally
3Power the deserializer board firstWait about 10 seconds
4Then power on OrinWait about 1 minute and confirm Orin startup is complete
5Check camera interface indicatorsConfirm all four camera interface indicators are steady on
6Check networkHost PC, Orin, robot controller, and headset are on the same subnet

If not all camera indicators are on, first check the camera harnesses, deserializer interface numbers, and deserializer power supply.

Start teleoperation​

For buttons, recording, playback, and logs, see Classic Apex Teleop.

Start the Orin back end​

The following uses the historical default IP 192.168.10.123. Use the delivered site value if it differs.

ping 192.168.10.123
ssh marvin@192.168.10.123
cd /opt/kernelmind/apex
./bringup_RM.sh

Disable X11-Forwarding in MobaXterm to avoid camera timeout or headset video issues.

Start classic Apex Teleop​

  1. Open the Apex Teleop version delivered with the system.
  2. Enter the Orin IP and connect.
  3. Start Robot and verify that the 3D model matches the physical robot.
  4. Start Teleop and the required network module. Camera is optional.
  5. Use the robot start control to set the robot Ready.
  6. Select Impedance Mode, then execute Home.
  7. Connect the headset and begin teleoperation.

Headset​

Historical deliveries may use Meta Quest or Pico:

Update the software​

  • Use the Orin software, classic Apex Teleop, and headset client delivered for the device.
  • Historical systems may use Meta Quest or Pico.
  • Do not apply current Tianzhun addresses or packages to an Orin system.

Historical Orin systems require packages matched to their hardware and ROS 2 environment. Back up network, robot, camera, Home, and end-effector configuration and record all current versions before updating.

sudo apt install ./<orin-controller-package>.deb

Use host and headset packages from the same delivery release. After updating, verify Robot, URDF, camera, and logs, then test Home and small teleoperation motions in a clear workspace.

Do not install current Tianzhun packages on an Orin system. Confirm compatibility with technical support before robot-controller or servo firmware updates.

Troubleshooting​

SymptomCheck first
Cannot connect to OrinRouter, Orin IP, host subnet, and cables
DHCP service failsOrin interface static IP and DHCP subnet consistency
Robot fails to startE-stop, power, arm-controller network, and Robot log
Teleop unavailableRobot running and Ready state
Headset not connectedTarget IP, router, network service, and adapter
Camera is blackCamera module, wiring, external deserializer, and log
No teleoperation motionImpedance Mode, Home, and headset state

See Classic Apex Teleop. Press the emergency stop immediately for abnormal motion or mechanical interference.