X4 Development Platform
A heavy 4WD architecture for demanding robotic missions.
The X4 is a configurable high-mobility UGV development platform. It is being built to prove the physical integration, control, and payload foundation required by security, inspection, logistics, emergency-response, and research programs.
System ownership
From wheel torque to mission-compute interface.
Mobility
Independently managed drive channels, custom suspension, optimized mass placement, and an interacting suspension concept support mobility development on difficult terrain.
Propulsion & power
A mission-tailored, high-power electric architecture uses robust, field-proven hardware selected for control authority, thermal margin, serviceability, and fault visibility.
Real-time control
A dedicated deterministic control core owns motion, calibration gates, command timeouts, link supervision, and safe motor-disable behavior.
Sensor & compute integration
A modular integration layer supports advanced perception, navigation, and edge-intelligence configurations without placing hard real-time safety on mission compute.
Teleoperation
A resilient, low-latency operator-control architecture supports advanced teleoperation and an operator-in-the-loop model. Assisted perception and supervised functions can be layered above it.
Safety architecture
Emergency stop, link loss, stale data, calibration state, motor faults, and electrical or thermal limits are handled explicitly. Final safety functions depend on program configuration and validation.
Payload adaptability
A modular upper structure can be configured around sensor masts, communications, compute, equipment, or a representative manipulator while accounting for power, thermal, mass, and stability limits.
Development status
Core mobility and reusable embedded control infrastructure are functional development work. Vehicle-dynamics, perception, compute, mission payload, and performance validation remain active integration areas.
Configuration reference
Specification and maturity matrix
Ratings describe the current design basis. Targets are not completed test results.
| Group | Characteristic | Current basis | Status |
|---|---|---|---|
| Mobility | Drive architecture | Independently managed, high-torque electric propulsion | Implemented |
| Mobility | Suspension | Proprietary independent architecture optimized for mobility, stability, and serviceability | Integration underway |
| Propulsion | Energy architecture | Modular high-power system tailored to mission duty cycle | Configuration dependent |
| Propulsion | Onboard energy | Up to approximately 9 kWh; usable capacity varies with configuration and reserve strategy | Configuration dependent |
| Propulsion | Continuous drivetrain rating | Up to 16 kW; subject to thermal conditions, duty cycle, and system limits | Configuration dependent |
| Propulsion | Peak drivetrain capability | 80 kW-class short-duration electrical capability; duration and limits are configuration dependent | Configuration dependent |
| Propulsion | Drive control | Custom-engineered control stack built on field-proven hardware with independent health supervision | Implemented |
| Vehicle | Base vehicle weight | Approximately 450 lb in the base configuration; excludes mission payloads and optional equipment | Configuration dependent |
| Vehicle | Target top speed | Approximately 45 mph; subject to configuration and validation | Engineering target |
| Control | Real-time layer | Dedicated deterministic motion and safety-control core | Implemented |
| Control | Operator link | Low-latency, resilient operator-control architecture | Implemented |
| Control | Dynamics | Yaw control, traction logic, stability supervision, rollover mitigation | Integration underway |
| Compute | Mission intelligence | Modular high-performance edge-compute integration layer | Integration underway |
| Sensors | Perception and navigation | Configurable interfaces for multi-modal mission sensing | Configuration dependent |
| Payload | Capacity / power | To be defined by mission configuration and validated test data | Configuration dependent |
Reusable control infrastructure
More than a one-off remote-controlled vehicle.
The embedded control architecture is designed to transfer across fundamentally different mobility platforms. Common health monitoring, input handling, safety states, configuration, and real-time interfaces reduce integration risk without exposing proprietary implementation details.
Technical disclosure boundary
Public capability. Protected implementation.
Roberson Robotics publicly describes system behavior, integration scope, and development maturity. Component selection, control topology, communications implementation, detailed power architecture, security measures, and patent-sensitive mechanical design are reserved for qualified technical review.
Program-specific architecture and interface details are disclosed through a structured engineering engagement under an appropriate NDA.
Start a technical conversation
Can the X4 architecture support your payload?
Share the payload mass, power, interfaces, environment, and mission objective. We’ll identify what is reusable, what needs development, and what must be validated.