Skip to main content

Understanding the TeleXperience System

If you want to integrate TeleXperience with your own robot and handle the adaptation yourself, please refer to the information in this section.

Service Notice

Advanced development is not covered by official after-sales support. You are responsible for resolving any issues encountered during the adaptation process. You may submit a support form, and we will try to provide suggestions, but we cannot guarantee response times or specific solutions.

If you encounter issues you cannot resolve, please contact your sales representative to purchase adaptation services. Our professional team can provide customized support to ensure your robot is successfully integrated.

Please note the following current limitations for self-adaptation:

  1. Dexterous hand: Independent finger movement is not supported; only simultaneous opening and closing of all fingers is available.
  2. Robot model visualization and real-time motion sync in the VR app are not supported.

Network Topology

Network Topology

There are three ways to establish communication between the TeleSuit and TeleBox:

  1. Direct wired connection
  2. Direct Wi-Fi connection
  3. Via a public server for remote teleoperation across networks (coming soon)

For communication between the TeleSuit and VR:

  1. Direct Wi-Fi connection
  2. Direct wired connection (Pro version and above)

ROS Topic List

TeleXperience uses several ROS2 topics. You can subscribe to these topics for further development.

TopicMessage TypeDescription
/io_teleop/joint_statessensor_msgs/JointStateJoint position feedback from the robot controller
/io_teleop/target_ee_posesgeometry_msgs/PoseArrayDesired end-effector poses for the robot arm
/io_teleop/joint_cmdsensor_msgs/JointStateTarget joint positions for the robot arm (waist)
/io_teleop/target_gripper_statussensor_msgs/JointStateDesired gripper open/close state
/io_teleop/target_base_movestd_msgs/Float64MultiArrayDesired chassis movement speed
/io_teleop/target_finger_jointssensor_msgs/JointStateTarget finger joint angles for the dexterous hand
/io_teleop/target_joint_from_vrsensor_msgs/JointStateTarget joint positions for head and torso lift
/io_teleop/target_joint_from_mocapsensor_msgs/JointStateJoint angle optimization reference from mocap
/io_teleop/vibration_feedbackstd_msgs/Float64MultiArrayHaptic feedback for controllers
/io_teleop/vr_dataio_msgs2/VrDataVR headset and controller data
/mocap/sensor_dataio_msgs2/SquashedMocapDataMotion capture information
/io_fusion/tftf2_msgs/TFMessageTF calculated from mocap data

The io_msgs2 message types are custom-defined. You can access the source files as follows:

ssh orangepi@10.42.0.3 # password:123456
cd /teleopbox_app/ros_ws/src/io_msgs2