Retrofit Existing Robot Cells Into Bounded Autonomy
Keep the robot. Add the Xolver brain around it.
Industrial teams shouldn't have to replace working robot cells to make them more adaptive. Xolver Retrofit is an application layer for bringing bounded autonomy to existing industrial robots. It connects robot contracts, OEM compatibility packs, CAD/workcell metadata, safety checks, skill previews, and execution evidence into one unified commissioning flow.
The Retrofit Studio Interface
Configure integration parameters, align CAD coordinate frames, calibrate cameras, and define safety zones directly through our console application.
// Xolver Retrofit Studio: Commissioning setup for KUKA RSI bench workspace.
Configured in Studio
OEM Compatibility Pack
Select and initialize target integration profiles (like `kuka_rsi_bench`) to bridge communication protocols.
CAD & Workcell import
Import target parts (e.g. `.step` models) and match key frames dynamically within the cell's environment coordinates.
Visuals & Safety zones
Map cameras and configure safety zones (e.g. `bench_workspace` bounds) to constrain model actuation behavior.
What It Enables
Turn an existing cell into a skill-executing, contract-gated, evidence-producing workstation.
OEM Compatibility Packs
Deploy native connectivity profiles (starting with KUKA RSI, with support for Fanuc and other OEMs ready for PoC) that speak the controller's exact language out of the box.
CAD & Part Metadata Import
Load 3D CAD files (.step) and metadata definitions directly into the spatial reasoning coordinate workspace.
Sensor & Safety Setup
Interface cameras, fixtures, moving conveyors, and safety-zone grids into a unified calibration frame.
Dry-Run Validation
Simulate and validate path movements in a virtual twin environment before committing execution commands to hardware.
Path Previews & Safety Gates
Review model trajectory proposals filtered through active contract constraints and real-time collision boundaries.
Evidence Record Trails
Generate cryptographic execution audits detailing why actions were approved, modified, or safely refused.
Most factory automation breaks at the boundary between perception, control, and safety.
A robot may be able to move. A vision system may be able to see. A model may be able to infer task intent.
But production teams still need to know exactly what the machine is allowed to do, what it refused to do, and why.
Designed Around That Boundary
Xolver Retrofit coordinates the components of adaptive cells securely:
- Models & Skills Propose:Visual models interpret the scene and propose kinematic paths.
- Contracts & Safety Layers Constrain:Deterministic constraints evaluate and refine trajectories to guarantee safety bounds.
- Runtime Adapters Translate:OEM bridges convert safe path data into controller-specific execution instructions.
Built As An Application, Not A Fork
Xolver Retrofit does not modify the core Xolver runtime brain. It plugs into the standard platform architecture through explicit integration points.
Core Integration Hooks
- Runtime contracts defining joint, space, and safety limits
- Skill catalogs detailing task-specific movement rules
- Deployment blueprints linking safety barriers and watchdogs
- Enforcement layers executing deterministic watchdog routines
- Edge runtime adapters formatting packets for local networks
- OEM compatibility packs bridging hardware protocols
- Console-based commissioning flows guiding initial alignment
This keeps the core platform OEM-agnostic while allowing robot-specific behavior to live safely below the runtime contract layer.
{
"blueprint_id": "kuka_rsi_assembly_cell",
"oem_pack": {
"provider": "kuka_rsi_bench",
"protocol": "RSI_3.x",
"frequency_hz": 250
},
"safety_shield": {
"zone_id": "bench_workspace",
"limit_type": "cartesian_box",
"bounds": { "x": 0.8, "y": 0.8, "z": 0.6 }
},
"contracts": [
"joint_limit_watchdog",
"velocity_ceiling_gating"
]
}// Blueprint defines target pack configurations and seals them with active contract checks.
Current Status & Readiness
We define clear boundaries between actively testable profiles and planned engineering features.
Active in Development
- KUKA RSI bench workflows (active testing)
- Fanuc & other OEM compatibility packs (ready for PoC)
- Workcell configuration & adapter links
- Path preview & joint limit simulation
- Dry-run validation workflows
- Deployment proposal evidence logs
Planned Future Work
- Production-certified CAD matching
- Moving-line conveyor servoing profiles
- Safety I/O and hardware PLC gate integration
Planning a Retrofit Pilot?
Start with a technical assessment of your robot cell, controller version, task specifications, safety constraints, and existing workcell coordinate data.
Discuss integration with an engineer
hello@xolver.aiFAQ
Do we need to modify our robot controller's core firmware?
No. Xolver Retrofit operates as an external application layer. It interfaces via standard native communication protocols (like KUKA RSI) rather than flashing custom firmware onto the controller.
How are safety constraints enforced on a retrofitted cell?
The Retrofit layer maps workspace boundaries (e.g., safety zones) and links them to the active runtime contract. The enforcement layer performs deterministic path and kinematics validation, allowing safe refusal before actions reach the hardware.
What OEM compatibility packs are supported?
Our first production compatibility path is KUKA RSI (Robot Sensor Interface) bench workflows. Additionally, compatibility packs for Fanuc and other major industrial OEMs are currently being built and are ready for Proof of Concept (PoC) validation. Future work will extend standard production profiles across these platforms.