Verified robot and embodiment directory

Robot platforms connected to Physical AI models

RoboSkin.ai connects robot foundation models, tactile models, humanoids, robot arms, and research setups without turning a paper's hardware label into an unsupported product claim.

Each relation answers a specific question: was the model trained across this platform, quantitatively evaluated on it, or only demonstrated on it? Hardware identity evidence and model relationship evidence remain separate.

24
verified platform entities
6
platform and setup types
17
connected robot AI models
53
evidence-backed relations

Direct answer

A robot model name is not enough to prove a hardware relationship

Robot AI papers mix exact products, unnamed lab platforms, dual-arm configurations, simulations, training fleets, and downstream fine-tuning targets. This directory normalizes only the identities a primary or official source can support and preserves whether the evidence is training, evaluation, or demonstration.

Evaluated on

The source reports experiments, rollouts, trials, task results, or a clearly defined evaluation on the platform.

Included in training

The source explicitly places that platform or setup in the model training mixture. It does not guarantee later task success.

Demonstrated on

An official source shows or states a real-system demonstration without enough disclosed protocol for a quantitative evaluation claim.

Entity type

Humanoid robots

3 records

humanoid robot

Apptronik Apollo 2

Manufacturer / provider: Apptronik

Source aliases: Apollo 2

Official reference

A modular humanoid platform offered in bipedal and wheeled-base configurations. The current directory records only model relationships supported by separate evaluation sources.

Connected model evidence

  • Gemini Robotics 2Evaluated on

    Source wording: Apptronik Apollo 2 humanoid with Inspire hands; Apptronik Apollo 2 humanoid with SharpaWave hand

    Google DeepMind reports task-level success rates for Inspire-hand whole-body manipulation and SharpaWave multi-finger tasks using the same Gemini Robotics 2 checkpoint. These are developer-reported results on selected tasks, not an independent benchmark or blanket Apollo 2 capability claim.

The official product page establishes the Apollo 2 identity. It does not independently verify Gemini Robotics 2 performance, hand-specific results, autonomy, safety certification, deployment scale, or commercial availability in every configuration.

humanoid robot

Unitree G1

Manufacturer / provider: Unitree Robotics

Source aliases: G1 humanoid

Official reference

A humanoid robot platform represented here because Tac4Loco uses a G1 model for simulation training and a physical G1 for plantar-pressure locomotion evaluation.

Connected model evidence

  • Tac4LocoIncluded in training

    Source wording: Unitree G1 model in MJLab simulation with 60 contact geometries per foot

    Tac4Loco is trained through reinforcement learning on a Unitree G1 model in MJLab simulation, with 60 simulated contact geometries per foot. This edge records simulated embodiment coverage and must not be interpreted as training on a physical G1 or as evidence for arbitrary G1 configurations.

  • Tac4LocoEvaluated on

    Source wording: Physical Unitree G1 with bilateral 60-element FSR pressure insoles

    The trained actor is deployed and evaluated on one physical Unitree G1 with research-team bilateral 60-element FSR pressure insoles. Physical comparisons are source-reported, generally use ten trials per configuration, and do not establish transfer to other G1 variants, feet, sensors, payloads, or long-duration field use.

The official page establishes the G1 product identity but lists configuration-dependent G1 and G1 EDU specifications. Tac4Loco’s bilateral 60-element FSR insoles are a research-team integration, not evidence that plantar tactile sensing is standard equipment on every G1 configuration.

humanoid robot

Fourier GR-1

Manufacturer / provider: Fourier Intelligence

Source aliases: GR-1

Official reference

A general-purpose humanoid robot platform used for real-world and simulated GR00T N1 manipulation research.

Connected model evidence

  • Isaac GR00T N1Evaluated on

    Source wording: Fourier GR-1 humanoid

    The GR00T N1 paper reports real-world language-conditioned bimanual manipulation and quantitative evaluation on Fourier GR-1. It does not transfer the same results to other humanoids or later GR00T versions.

  • Isaac GR00T N1Included in training

    Source wording: Fourier GR-1 humanoid

    The GR00T N1 paper states that pretraining uses the authors’ GR-1 humanoid data. This records training-mixture coverage only; it does not imply that every GR-1 variant, downstream checkpoint, or reported evaluation uses the same data and hardware configuration.

The official Fourier page establishes the platform identity. Model performance, training-data coverage, hand configuration, and task results are preserved separately in the GR00T N1 paper and NVIDIA publication.

Entity type

Robot arms

4 records

robot arm

Franka Emika Panda

Manufacturer / provider: Franka Robotics

Source aliases: Panda, Franka Panda, Franka Emika Robot (Panda)

Official reference

The older Franka research robot commonly called Panda. Exact experimental configurations can add cameras, grippers, tactile sensors, tables, or mobile fixtures.

Connected model evidence

  • OpenVLA 7BEvaluated on

    Source wording: Franka Emika Panda tabletop setup (fine-tuned-policy evaluation)

    This relation concerns a policy fine-tuned with target demonstrations on the Franka-Tabletop setup. It is not a zero-shot result for the base OpenVLA checkpoint and does not cover every Franka installation.

  • Dream-TacEvaluated on

    Source wording: Franka Emika Panda with dual RealSense D435i cameras and two Xense Photon fingertip sensors

    The Dream-Tac preprint explicitly identifies a Franka Emika Panda with two RealSense D435i cameras and two Xense Photon fingertip tactile sensors for six contact-rich tasks. The preprint does not establish independent replication or cross-robot transfer.

Franka documentation identifies the older Franka Robotics Robot as FER or Panda. This entity must not be conflated with Franka Research 3, a generic Franka arm, Franka Duo, or every DROID installation.

robot arm

Universal Robots UR5e

Manufacturer / provider: Universal Robots

Source aliases: UR5e

Official reference

A six-axis collaborative robot arm represented in both single-arm and bimanual π0 configurations.

Connected model evidence

  • π0 (Pi Zero)Included in training

    Source wording: Universal Robots UR5e (single and bimanual configurations)

    The π0 report explicitly states that the model is trained jointly across the listed platforms, including single and bimanual UR5e configurations. This does not imply the same performance across both configurations or new UR products.

  • π0 (Pi Zero)Evaluated on

    Source wording: Universal Robots UR5e (single and bimanual configurations)

    The π0 report evaluates UR5e and bimanual UR5e tasks under its own pretraining and fine-tuning protocols. Results remain task-, dataset-, and configuration-specific.

The manufacturer datasheet establishes the UR5e identity. UR5 and UR5e are not treated as interchangeable, and the π0 paper—not this datasheet—supports the model-training and evaluation relationships.

robot arm

Universal Robots UR5

Manufacturer / provider: Universal Robots

Source aliases: UR5, UR5 CB-Series

The legacy six-axis UR5 collaborative robot arm named in Octo pretraining and real-robot evaluation evidence.

Connected model evidence

  • OctoIncluded in training

    Source wording: Universal Robots UR5 (represented in the Open X-Embodiment pretraining mixture)

    The Octo paper’s pretraining mixture includes Berkeley Autolab UR5 data. This records training coverage for a legacy UR5 without resolving the CB controller revision and does not imply that every Octo checkpoint or upstream Open X-Embodiment snapshot uses an identical UR5 contribution.

  • OctoEvaluated on

    Source wording: Universal Robots UR5 (zero-shot evaluation; not normalized to UR5e)

    Octo is evaluated on two physical UR5 tasks with ten trials per task. “Zero-shot” means no target-task fine-tuning; it does not mean the UR5 embodiment was absent from pretraining, and the source does not identify this legacy UR5 as UR5e.

The Octo paper says UR5, not UR5e, and does not disclose the CB controller revision. This entity remains separate from the existing e-Series UR5e entity and does not inherit UR5e force-sensing, repeatability, or other generation-specific specifications.

robot arm

Trossen WidowX-250 6DOF

Manufacturer / provider: Trossen Robotics

Source aliases: WidowX 250 6-DoF, WidowX-250 6DOF, BridgeData V2 WidowX

Official reference

The six-degree-of-freedom WidowX-250 arm used by the BridgeData V2 setup and named in OpenVLA and Octo evaluations.

Connected model evidence

  • OpenVLA 7BEvaluated on

    Source wording: Trossen WidowX 250 6-DoF (zero-shot evaluation)

    The OpenVLA paper reports zero-shot evaluation on 17 BridgeData V2 WidowX tasks with 170 rollouts. BridgeData identifies the arm as a WidowX 250 6-DoF; the result remains specific to the paper protocol.

  • OctoEvaluated on

    Source wording: Trossen WidowX 250 6-DoF (zero-shot evaluation)

    The Octo paper lists the WidowX 250 6-DoF among its real-robot zero-shot setups. The result does not establish compatibility with other WidowX products or untested observation and action adapters.

BridgeData V2 confirms its data-collection arm, while each model paper controls the evaluation claim. This entity does not imply zero-shot success, cross-scene robustness, or compatibility with other WidowX variants.

Entity type

Mobile manipulators

2 records

mobile manipulator

Google RT-series mobile manipulation robot

Manufacturer, configuration owner, or commercial model not established

Source aliases: Google robot, RT-1 Robot, unnamed 7-DoF mobile manipulator

An editorially normalized research-platform entity for the unnamed mobile manipulator shared by RT-series evaluations and called the Google robot or RT-1 Robot in later model papers.

Connected model evidence

  • RT-2Evaluated on

    Source wording: Google RT-series 7-DoF mobile manipulator (hardware model not disclosed)

    The RT-2 paper reports about 6,000 evaluation trials on the authors’ unnamed seven-degree-of-freedom mobile manipulator. The result is tied to that platform and protocol and does not identify a commercial robot model.

  • OpenVLA 7BEvaluated on

    Source wording: Google RT-series mobile manipulator (zero-shot evaluation)

    The OpenVLA paper reports zero-shot evaluation on 12 Google-robot tasks with 60 rollouts. The hardware is normalized only to the unnamed RT-series platform family described by the source.

  • OctoEvaluated on

    Source wording: Google RT-series mobile manipulator / proprietary RT-1 Robot (zero-shot evaluation)

    The Octo paper identifies a proprietary RT-1 Robot as a zero-shot evaluation setup. The manufacturer and commercial product model remain undisclosed.

The reviewed sources do not disclose a manufacturer or commercial model. This record must not be relabeled as Everyday Robots, Franka, xArm, or another product, and the 13 physical training robots reported by RT-2 are not assumed to be one hardware family.

mobile manipulator

PaLM-E mobile manipulator

Manufacturer, configuration owner, or commercial model not established

Source aliases: PaLM-E mobile robot

The real mobile-manipulation platform used in PaLM-E kitchen experiments, retained separately because the source does not establish a commercial robot model or exact equivalence with the RT-series platform.

Connected model evidence

  • PaLM-EIncluded in training

    Source wording: Google mobile manipulator in the kitchen environment (hardware model not disclosed)

    The PaLM-E paper lists the real mobile-manipulator domain in its joint embodied training mixture. The relation does not imply that PaLM-E directly emits low-level motor commands.

  • PaLM-EEvaluated on

    Source wording: Google mobile manipulator in the kitchen environment (hardware model not disclosed)

    The paper evaluates embodied reasoning and long-horizon kitchen tasks on the real mobile manipulator while separate low-level policies execute generated decisions. This is not evidence of direct end-to-end motor control.

The PaLM-E paper supports a real mobile-manipulator environment but does not publish a vendor model. PaLM-E generates high-level textual decisions and relies on separate low-level policies for physical execution.

Entity type

Research configurations

9 records

research configuration

Franka Panda UniVTAC GelSight Mini simulation configuration

Manufacturer, configuration owner, or commercial model not established

Source aliases: UniVTAC simulated Panda platform, UniVTAC Panda–GelSight Mini configuration

The released UniVTAC benchmark configuration combining a simulated Franka Panda and parallel-jaw gripper with bilateral simulated GelSight Mini observations, head and wrist RGB, and robot-state and action channels.

Connected model evidence

  • UniVTAC EncoderEvaluated on

    Source wording: Simulated Franka Panda with a parallel-jaw gripper and bilateral simulated GelSight Mini observations

    The encoder is integrated into ACT and evaluated on eight simulated UniVTAC tasks using 100 rollouts per method-task. The author-reported 48.0% average applies to this simulated protocol and does not establish physical Panda performance, independent reproduction, or universal sensor support.

This is a simulation-only, paper-specific configuration rather than a stock Franka or GelSight product bundle. The current public collection and evaluation pipeline supports simulated GelSight Mini; ViTai GF225 and Xense WS are listed as planned. Simulation outcomes do not establish physical Panda compatibility, safety, sensor fidelity, or sim-to-real performance.

research configuration

Tianji Marvin UniVTAC GF225 configuration

Manufacturer, configuration owner, or commercial model not established

Source aliases: UniVTAC physical Marvin platform, Tianji Marvin with bilateral ViTai GF225

The physical UniVTAC evaluation configuration comprising one 7-DoF Tianji Marvin arm, a parallel gripper, one wrist RGB camera, and two ViTai GF225 tactile sensors sampled at 30 Hz.

Connected model evidence

  • UniVTAC EncoderEvaluated on

    Source wording: Tianji Marvin 7-DoF arm with a parallel gripper, wrist RGB camera, and bilateral ViTai GF225 sensors

    The paper reports 20 physical rollouts per method-task for Insert Tube, Insert USB, and Bottle Upright on this configuration, with human-observed binary success. The 68.3% tactile-policy average is author-reported and does not establish cross-robot transfer, independent replication, or production reliability.

This is a paper-specific multi-vendor integration, so manufacturer remains unset for the combined configuration. The paper does not disclose the exact Marvin SKU or gripper model, and evidence is limited to three physical tasks, 20 rollouts per method-task, and human-observed binary success. Current product-family specifications must not be transferred to the undisclosed paper SKU.

research configuration

Franka Duo

Manufacturer, configuration owner, or commercial model not established

A named dual-arm Franka research configuration shown with a Robotiq gripper in the Gemini Robotics 2 evaluation.

Connected model evidence

  • Gemini Robotics 2Evaluated on

    Source wording: Franka Duo

    Google DeepMind reports success rates for pick-and-place, tool-kitting, and insertion tasks on a Franka Duo with a Robotiq gripper. The source does not establish independent replication or performance outside the reported checkpoint, hardware configuration, and tasks.

The reviewed Google DeepMind source names the configuration “Franka Duo” but does not identify it as Franka Research 3 Duo, specify every component, or establish a generally available product with that exact name.

research configuration

Dexmate Vega-1 + dual Sharpa Wave T-Rex configuration

Manufacturer, configuration owner, or commercial model not established

Source aliases: T-Rex bimanual dexterous platform, Bimanual Dexmate Vega-1 with two Sharpa Wave hands

The fixed-base bimanual research configuration used to collect the T-Rex tactile-reactive dataset and evaluate its VLA policy, combining a Dexmate Vega-1 with two 22-DoF Sharpa Wave hands and ten fingertip tactile sensors.

Connected model evidence

  • T-RexIncluded in training

    Source wording: Fixed-base bimanual Dexmate Vega-1 with two 22-DoF Sharpa Wave hands

    The T-Rex paper reports tactile-reactive midtraining on data collected with this fixed-base bimanual configuration. The edge does not imply training across multiple robot platforms, release of the complete 100-hour corpus, or transfer to another hand, sensor, or embodiment.

  • T-RexEvaluated on

    Source wording: Fixed-base bimanual Dexmate Vega-1 with two 22-DoF Sharpa Wave hands

    The authors evaluate T-Rex on 12 contact-rich tasks with 16 randomized rollouts per task on this one research configuration. The source-reported 65% macro-average does not establish independent replication, cross-platform performance, or reliability outside the documented task and scoring protocol.

This is a source-specific multi-vendor research integration, not a single product or compatibility claim. The sources do not establish equivalent behavior for another Vega-1 revision, Sharpa hand, tactile sensor, camera layout, mobile base, humanoid body, or independent implementation.

research configuration

RealMan RM65-B ViTaR tactile configuration

Manufacturer, configuration owner, or commercial model not established

Source aliases: RM65-B/DH-gripper platform, ViTaR physical-robot platform

A mixed research configuration comprising a 6-DoF RealMan RM65-B arm, a DH Robotics PGIA-series parallel-jaw gripper, a custom rigid adapter with two mirror-symmetric 9DTact sensors, one wrist RealSense D455, and one fixed third-person D455.

Connected model evidence

  • ViTaREvaluated on

    Source wording: 6-DoF RealMan RM65-B with a DH Robotics PGIA-series parallel-jaw gripper, dual 9DTact sensors, and wrist plus third-person RealSense D455 cameras

    The paper reports three physical tasks with 20 binary-success trials per method-task pair on this configuration. It does not justify transfer to another RM65-B, gripper, sensor, camera layout, or task family.

This is a paper-specific multi-vendor integration, not a standard single-manufacturer product. The custom adapter, dual 9DTact mounting, camera placement, calibration, 10 Hz controller, and software stack must not be represented as standard RM65-B or DH Robotics features. Evidence covers only the three physical tasks and protocol reported by ViTaR.

research configuration

XHand–UR7e ReTouch tactile manipulation platform

Manufacturer, configuration owner, or commercial model not established

Source aliases: XHand–UR7e platform, ReTouch real-world platform

A mixed research platform comprising a UR7e arm, an XHand five-finger dexterous hand, one wrist RGB camera, and two fixed external RGB cameras. Each finger supplies 120 three-axis force taxels; demonstrations use a VIVE wrist tracker and MANUS glove.

Connected model evidence

  • ReTouchIncluded in training

    Source wording: UR7e arm with an XHand five-finger tactile dexterous hand, one wrist RGB camera, and two fixed external RGB cameras

    The paper supports 900 successful demonstrations collected on this platform, with 800 used in the common training pool and 100 held out for diagnostics. It does not disclose per-task counts or a public split manifest.

  • ReTouchEvaluated on

    Source wording: UR7e arm with an XHand five-finger tactile dexterous hand, one wrist RGB camera, and two fixed external RGB cameras

    The paper reports 20 rollouts per method-task under the seven-task standard protocol and 20 rollouts per method-setting under four challenges. Most reported scores are graded normalized task scores rather than binary completion.

This record represents the exact ReTouch research configuration, not a standard product from one manufacturer. The paper does not disclose RGB-camera models, a complete tactile-sensor part number, force range, sampling rate, calibration uncertainty, or production certification. XHT retains 900 successful demonstrations and excludes interrupted or corrupted demonstrations, so that count is not an all-attempt failure rate.

research configuration

Franka Research 3 + bilateral DM-Tac WS τ configuration

Manufacturer, configuration owner, or commercial model not established

Source aliases: τ Franka tactile platform, Franka Research 3 with DM-Tac WS

A Franka Research 3 with a Franka Hand whose stock fingers are replaced by two DM-Tac WS vision-based tactile sensors, observed by two static RealSense D435i cameras and one wrist RealSense D405.

Connected model evidence

  • τ (Touch-Augmented VLA)Included in training

    Source wording: Franka Research 3 with a Franka Hand whose fingers are replaced by bilateral DM-Tac WS sensors, two RealSense D435i cameras, and one wrist RealSense D405

    The paper reports 100 synchronized teleoperated demonstrations per task across four tasks on this one configuration. TacAura was announced but no downloadable corpus or license was verified.

  • Source wording: Franka Research 3 with a Franka Hand whose fingers are replaced by bilateral DM-Tac WS sensors, two RealSense D435i cameras, and one wrist RealSense D405

    The paper reports 20 physical trials per model-task pair across four tasks. Baselines marked with a dagger were adapted to this tactile setup, and the fixed τ variants must not be merged into one synthetic best-task checkpoint.

This is the source-specific τ research setup, not a stock Franka product configuration. The paper reports approximately 40 FPS 320 × 240 tactile capture, 15 FPS camera capture, and a synchronized 10 Hz dataset, but does not disclose the deployed policy rate, exact action tensor, cross-sensor transfer, or production safety evidence.

research configuration

RealMan RM75B + bilateral DM-Tac W UniTacVLA configuration

Manufacturer, configuration owner, or commercial model not established

Source aliases: UniTacVLA RM75B tactile platform, RM75B with bilateral DM-Tac W

A RealMan RM75B slave arm with a 3D-printed one-degree-of-freedom parallel gripper, two DM-Tac W fingertip sensors, a wrist RealSense D405, and a first-person RealSense L515, paired with another RM75B in an ALOHA-style teleoperation system.

Connected model evidence

  • UniTacVLAIncluded in training

    Source wording: RealMan RM75B with a 3D-printed parallel gripper, bilateral DM-Tac W fingertip sensors, a wrist RealSense D405, and a first-person RealSense L515

    The paper reports approximately one hour of demonstrations per subtask across eight subtasks on this configuration, but does not disclose trajectory counts, an aggregate duration, a split manifest, or a public dataset.

  • UniTacVLAEvaluated on

    Source wording: RealMan RM75B with a 3D-printed parallel gripper, bilateral DM-Tac W fingertip sensors, a wrist RealSense D405, and a first-person RealSense L515

    The paper reports 50 trials for each of eight clean and eight perturbed subtask settings on this configuration. It publishes per-setting results but no aggregate mean and does not establish cross-robot or cross-sensor transfer.

This is a paper-specific mixed research configuration rather than a commercial bundle or compatibility claim. The authors do not disclose tactile pixel resolution, policy and correction frequencies, action dimension, public calibration files, or cross-robot transfer. Results remain limited to eight paper-defined subtasks and clean or prescribed perturbation settings.

UniTacVLA primary paperReviewed 2026-08-22

research configuration

Franka Panda + Robotiq 2F-140 + GelSight Mini VLA-Touch configuration

Manufacturer, configuration owner, or commercial model not established

Source aliases: VLA-Touch Franka setup, Franka Panda VLA-Touch platform

A Franka Emika Panda with a Robotiq 2F-140 gripper, one GelSight Mini mounted on one gripper finger, one fixed overhead RealSense camera, one wrist RealSense camera, and an RTX 4090 inference workstation.

Connected model evidence

  • VLA-TouchIncluded in training

    Source wording: Franka Emika Panda with a Robotiq 2F-140 gripper, one GelSight Mini on one gripper finger, and overhead plus wrist RealSense cameras

    The paper reports task-specific RDT fine-tuning without touch and interpolant-controller training from 380 demonstrations collected through the three task pipelines on this configuration. It does not establish a tactile-native base VLA or a complete public RDT checkpoint.

  • VLA-TouchEvaluated on

    Source wording: Franka Emika Panda with a Robotiq 2F-140 gripper, one GelSight Mini on one gripper finger, and overhead plus wrist RealSense cameras

    The complete system is evaluated for 20 trials on each of Cup, Wipe, and Peel. The resulting 9/20, 12/20, and 7/20 end-to-end counts remain task- and hardware-specific and do not establish cross-task generalization.

This is the exact source-specific VLA-Touch configuration, not a standard product bundle. Touch is unilateral, the RealSense camera models are not disclosed, and evidence covers three contact-rich task pipelines on one single-arm setup. It does not establish general compatibility, cross-task transfer, cross-sensor reliability, or a complete released deployment stack.

Entity type

Platform families

2 records

robot platform family

1X humanoid platform family

Manufacturer / provider: 1X

Source aliases: 1X humanoid, 1X humanoids

Official reference

A family-level entity used when a model source names 1X humanoids without disclosing the exact 1X robot model or revision.

Connected model evidence

  • Isaac GR00T N1Demonstrated on

    Source wording: 1X humanoid

    NVIDIA’s official research page says GR00T N1 demonstrates language-conditioned bimanual household manipulation on 1X humanoids. The exact 1X model and a model-specific quantitative protocol are not disclosed in the reviewed source.

This record deliberately does not resolve the GR00T N1 demonstration to NEO, EVE, NEO Beta, NEO Gamma, or another 1X product. The cited NVIDIA source supports only the family-level wording “1X humanoids.”

robot platform family

Trossen ViperX arm family

Manufacturer / provider: Trossen Robotics

Source aliases: Trossen ViperX, ViperX

Official reference

A family-level record for experiments that name ViperX arms without disclosing the exact ViperX-250, ViperX-300, or six-degree-of-freedom product code.

Connected model evidence

  • OctoEvaluated on

    Source wording: Trossen ViperX and ALOHA configurations (fine-tuned-policy evaluation)

    Octo evaluates a target-data-fine-tuned policy on a ViperX setup. The ViperX embodiment was not present in Octo pretraining, so this is neither a base-checkpoint zero-shot result nor evidence that Octo was trained across ViperX.

  • π0 (Pi Zero)Included in training

    Source wording: Trossen ViperX arms (bimanual and mobile configurations)

    The π0 report says the joint training set includes bimanual and mobile setups using Trossen ViperX arms. It does not disclose an exact ViperX product code, and “based on ALOHA” does not make these setups identical to an original ALOHA system.

The π0 and Octo sources use ViperX wording without enough evidence to resolve every setup to a product variant. ALOHA bimanual systems and mobile configurations remain configuration qualifiers, not aliases for a single arm.

Entity type

Research setups

4 records

research setup

ALOHA bimanual teleoperation setup

Manufacturer, configuration owner, or commercial model not established

Source aliases: ALOHA, A Low-cost Open-source Hardware System for Bimanual Teleoperation

Official reference

The original open-source bimanual teleoperation workcell built from two ViperX follower arms, two WidowX leader arms, four RGB cameras, and a 50 Hz data-collection stack.

Connected model evidence

  • OctoEvaluated on

    Source wording: Trossen ViperX and ALOHA configurations (fine-tuned-policy evaluation)

    The Octo paper evaluates a physical Berkeley bimanual ALOHA setup after reinitializing a 14-dimensional action head and fine-tuning on target ALOHA demonstrations. This is not zero-shot base-checkpoint transfer, does not imply ALOHA data in Octo pretraining, and does not apply to ALOHA 2.

ALOHA is a complete research workcell rather than an alias for one ViperX arm or a single-manufacturer product. Octo evidence concerns a target-data-fine-tuned policy with a reinitialized 14-dimensional action head, not zero-shot use of the base checkpoint; ALOHA 2 remains a separate later system.

research setup

Language Table research setup

Manufacturer, configuration owner, or commercial model not established

Source aliases: Language Table

A tabletop instruction-following research setup represented in both simulated evaluation and qualitative real-robot evidence.

Connected model evidence

  • RT-2Evaluated on

    Source wording: Language Table setup (RT-2-PaLI-3B simulation and qualitative real-world evaluation)

    The quantitative Language Table result is a simulation evaluation for RT-2-PaLI-3B. It must not be generalized to all RT-2 checkpoints or presented as a real-robot success rate.

  • RT-2Demonstrated on

    Source wording: Language Table setup (RT-2-PaLI-3B simulation and qualitative real-world evaluation)

    The paper shows qualitative real-world Language Table behavior for RT-2-PaLI-3B. The simulation metric is not transferred to this real setup.

  • PaLM-EIncluded in training

    Source wording: Language Table setup (real and simulated)

    The PaLM-E training mixture includes Language Table data from simulated and real settings. This relationship records training coverage, not a claim of cross-platform deployment reliability.

  • PaLM-EEvaluated on

    Source wording: Language Table setup (real and simulated)

    PaLM-E reports quantitative Language Table evaluation primarily in simulation and also presents real-tabletop behavior. The relation retains that mixed-domain boundary and does not turn simulation success into a real-robot metric.

Simulation results and real-world demonstrations are not interchangeable. RT-2 evidence is limited to the RT-2-PaLI-3B checkpoint where stated, and PaLM-E quantitative results must retain their simulation or real-world qualifier.

research setup

KUKA iiwa7 + Allegro Hand ADEPT configuration

Manufacturer, configuration owner, or commercial model not established

Source aliases: ADEPT KUKA-Allegro setup, KUKA iiwa7 with Allegro Hand

A fixed-workbench ADEPT research configuration combining a 7-DoF KUKA iiwa7 arm, a 16-DoF Allegro Hand, and two calibrated Intel RealSense RGB cameras for a 23-DoF vision-only student policy.

Connected model evidence

  • ADEPTIncluded in training

    Source wording: 23-DoF KUKA iiwa7 plus 16-DoF Allegro Hand workbench configuration with two RGB cameras (vision-only student)

    ADEPT uses embodiment-specific simulation pretraining and downstream training for this KUKA-Allegro configuration. The KUKA student is vision-only, each downstream task is trained independently, and this relation does not imply physical-robot training, tactile input, or one checkpoint shared with the Flexiv-Sharpa setup.

  • ADEPTEvaluated on

    Source wording: 23-DoF KUKA iiwa7 plus 16-DoF Allegro Hand workbench configuration with two RGB cameras (vision-only student)

    The paper reports ten physical trials for each KUKA-Allegro FMB star, square-and-round, and dish condition. These author-run results are vision-only and do not establish tactile benefit, independent replication, cross-embodiment transfer, or production reliability.

This is a source-specific research setup, not a single-manufacturer product. The paper does not disclose the exact RealSense camera model, does not add tactile input to the KUKA branch, and does not establish transfer to another Allegro revision, iiwa model, mobile base, sensor layout, or task family.

research setup

Flexiv Rizon + Sharpa hand ADEPT configuration

Manufacturer, configuration owner, or commercial model not established

Source aliases: ADEPT Flexiv-Sharpa setup, Flexiv Rizon with Sharpa hand

A fixed-workbench ADEPT research configuration combining a 7-DoF Flexiv Rizon arm, a 22-DoF five-finger Sharpa hand, two RGB cameras, and five fingertip vision-based tactile sensors for a 29-DoF student policy.

Connected model evidence

  • ADEPTIncluded in training

    Source wording: 29-DoF Flexiv Rizon plus 22-DoF Sharpa hand workbench configuration with two RGB cameras and five fingertip vision-based tactile sensors

    ADEPT uses separate embodiment-specific simulation and downstream training for the Flexiv-Sharpa configuration. This relation does not imply training on a released tactile dataset, reuse of the KUKA checkpoint, or transfer to a different hand, arm, sensor, or task family.

  • ADEPTEvaluated on

    Source wording: 29-DoF Flexiv Rizon plus 22-DoF Sharpa hand workbench configuration with two RGB cameras and five fingertip vision-based tactile sensors

    In one matched square-and-round insertion condition with ten physical trials per modality, the source reports 3/10 final success for vision-only and 8/10 for visuo-tactile. The result does not establish statistical significance or generalize to other tasks, robots, hands, sensors, or operating environments.

The paper does not disclose the exact Sharpa hand revision, RGB camera models, or fingertip tactile-sensor product. This record must not be relabeled SharpaWave or treated as evidence for another Sharpa, Flexiv, optical-tactile, mobile, or humanoid configuration.

Methodology and limits

This is an evidence map, not a compatibility list

A platform appearing in training data does not prove the released checkpoint works on that hardware. A fine-tuned downstream policy is not a zero-shot base-model result. A simulated score is not a real-robot score. Family-level records remain family-level until a source identifies the exact product revision.

Coverage is intentionally incomplete. Generic phrases such as “nine robot configurations,” undisclosed simulation embodiments, sensors, and dataset mixtures are not converted into robot entities merely to increase the count.