Raph Rover
Raph Rover – definition
Raph Rover is a larger unmanned ground vehicle (UGV) platform developed by Fictionlab for mobile robotics tasks that require higher payload capacity, more installation space, and stronger field deployment characteristics than a compact educational rover. In mobile robotics terms, it is a research and engineering base platform for integrating compute, perception sensors, power systems, communication modules, and custom mechanical payloads on a wheeled ground robot.
The term should be understood as a complete UGV platform, not only a chassis. In practice, Raph Rover refers to the mobile base together with its drivetrain, embedded power distribution, mounting interfaces, and software integration path for ROS 2-based autonomy. It is intended for applications such as outdoor inspection, experimental autonomy, sensor fusion, terrain perception, and custom robotics projects where a platform like Leo Rover may be too small in payload or footprint. At the same time, Raph Rover does not replace Leo Rover in laboratory teaching or entry-level ROS work. The two platforms serve different integration envelopes.
Raph Rover in the context of mobile robotics
In UGV engineering, platform size directly affects payload budget, available power, wheel-ground interaction, sensor placement, and thermal design. Raph Rover belongs to the class of mobile bases used as configurable integration carriers. This means that the exact sensing and autonomy stack depends on the mission profile, but the vehicle must provide stable interfaces for standard robotics subsystems.
For a robotics engineer, the practical meaning of Raph Rover includes the following system layers:
- Locomotion layer – wheeled drive system, motor controllers, odometry source, and low-level control.
- Power layer – battery, voltage rails, current margins, and protected payload supply.
- Compute layer – onboard computer, optional accelerator, storage, and network connectivity.
- Perception layer – LiDAR, IMU, RGB or depth cameras, GNSS or RTK receivers, and auxiliary sensors.
- Middleware layer – ROS 2 nodes, topics, transforms, diagnostics, launch files, and lifecycle management.
- Application layer – SLAM, navigation, teleoperation, inspection software, or mission-specific autonomy.
This layered view is standard in field robotics because autonomy is rarely delivered by the mechanical platform alone. A UGV becomes operational only after its sensing, state estimation, and navigation stack are matched to terrain, compute resources, and required accuracy.
How Raph Rover is typically integrated with ROS 2
Raph Rover is relevant mainly as a ROS 2 integration target. ROS 2 provides message transport, hardware abstraction patterns, diagnostics, transform handling, and standardized interfaces between perception and navigation components. In current practice, Humble, Iron, and Jazzy are common reference points for mobile robots, especially when using Nav2, ros2_control, robot_localization, and RViz2.
A minimal ROS 2 deployment on a UGV of this class usually exposes these interfaces:
/cmd_vel– commanded base velocity, usuallygeometry_msgs/msg/Twist./odom– wheel or fused odometry, usuallynav_msgs/msg/Odometry./tfand/tf_static– coordinate transforms according to REP-103 and REP-105 conventions./scan– 2D LiDAR data, usuallysensor_msgs/msg/LaserScan./imu/data– inertial output, usuallysensor_msgs/msg/Imu./pointsor/points_raw– 3D LiDAR or depth point clouds, usuallysensor_msgs/msg/PointCloud2./fix– GNSS output, usuallysensor_msgs/msg/NavSatFix.
Coordinate frames should follow REP-103 for units and REP-105 for mobile platform frame semantics. In most UGV stacks, the required frames are base_link, odom, and map. If GNSS is fused, an earth-referenced workflow may also be added through dedicated localization nodes.
ros2 topic list
ros2 topic echo /odom
ros2 run tf2_tools view_frames
ros2 launch nav2_bringup navigation_launch.py use_sim_time:=false
Key parameters and engineering considerations
For a larger rover platform, the most important parameters are not only speed or size. The useful integration metrics are those that determine whether autonomy and payload operation are feasible in the field.
| Parameter group | Why it matters on Raph Rover | Typical engineering impact |
|---|---|---|
| Payload capacity | Determines whether heavier LiDARs, GNSS antennas, industrial cameras, or compute modules can be mounted | Affects center of gravity, suspension behavior, and battery sizing |
| Power budget | Defines whether onboard GPU, multi-sensor stack, and radios can run simultaneously | Limits runtime and peak current margin |
| Wheelbase and track width | Influence stability and turning behavior | Affect odometry model and terrain handling |
| Ground clearance | Important in outdoor inspection and agricultural rows | Reduces risk of underbody collision |
| Ingress protection | Relevant for dust and water exposure | Constrains connector and enclosure choices |
| Compute mounting volume | Needed for Jetson, x86 PC, routers, and sensor hubs | Determines thermal and cable routing options |
For ROS 2 autonomy, update rates also matter. Wheel odometry is often published at 20-100 Hz, IMU at 100-400 Hz, 2D LiDAR at about 5-20 Hz depending on sensor model, and GNSS at 1-20 Hz depending on receiver configuration. Exact values depend on the integrated hardware and should be verified from manufacturer specifications and node configuration.
Supported sensors and custom payloads
Raph Rover is most useful when the mission requires sensors that are difficult to place on smaller platforms. Examples include a 3D LiDAR with elevated mounting, a dual-antenna GNSS setup, stereo or depth cameras, and environmental or inspection payloads. In ROS 2, each added sensor must be integrated at three levels: mechanical mounting, power and communication, and software frame calibration.
Common sensor combinations on a field UGV include:
- 2D LiDAR + IMU + wheel odometry for indoor or mixed-environment navigation.
- 3D LiDAR + IMU for mapping, obstacle detection, and terrain reconstruction.
- GNSS/RTK + IMU + wheel odometry for outdoor localization over larger areas.
- RGB-D or stereo camera + IMU for visual odometry or semantic perception.
Compared with Leo Rover, Raph Rover is better suited to heavier payload stacks and larger battery or compute configurations. Leo Rover remains the more compact platform for education, desktop-scale testing, and lower-mass experiments based on its built-in Raspberry Pi compute path and four-wheel mobile base. Raph Rover is the platform to choose when the payload architecture becomes the main design constraint.
Use cases with Leo Rover and Raph Rover
The distinction between the two Fictionlab platforms is practical. Leo Rover is appropriate when the objective is ROS 2 learning, algorithm prototyping, or lightweight mobile manipulation research payloads mounted on a small four-wheel rover. It is not autonomous out of the box and needs a full navigation stack integration. Raph Rover addresses a different problem: carrying more equipment and operating in scenarios where sensor placement, endurance, and mechanical reserve matter more than compactness.
Typical Raph Rover use cases include:
- Outdoor LiDAR mapping and GNSS-aided navigation experiments.
- Inspection payload integration for construction or infrastructure monitoring.
- Agricultural robotics prototyping where larger sensors or custom frames are needed.
- Research projects that require non-standard compute, power, or sensor combinations.
Limitations and trade-offs
A larger UGV platform solves integration constraints but introduces others. Mass increases transport complexity and can reduce convenience in indoor testing. Higher payload capacity also encourages more complex stacks, which increases power draw, calibration effort, and failure surface. Navigation performance depends on sensing and estimation quality, not on platform size alone.
Raph Rover should therefore be treated as a configurable robotics base. It is not a guarantee of autonomy by itself. Reliable field operation still depends on correct URDF modeling, calibrated transforms, tuned state estimation, validated control loops, and mission-specific safety logic.
Normative references and standards
The following references are relevant when defining and integrating a platform such as Raph Rover in ROS-based mobile robotics:
- REP-103 – Standard Units of Measure and Coordinate Conventions.
- REP-105 – Coordinate Frames for Mobile Platforms.
- ROS 2 documentation on nodes, topics, lifecycle, tf2, and ros2_control at docs.ros.org.
- URDF and robot_state_publisher documentation for robot description and frame publication.
- Manufacturer specifications for integrated sensors and compute modules, such as LiDAR, Intel RealSense, GNSS/RTK receivers, and NVIDIA Jetson devices.