How ros-industrial/fanuc works
This repository is a large meta‐package for ROS-Industrial support of FANUC robots. It isn’t a “full stack” web application in the traditional sense; rather, it is a set of ROS packages that provide drivers, robot description (URDF and meshes), configuration support (including joint names, OPW parameters, etc.), and MoveIt configuration and plugins for various FANUC robot models. In other words, it is a robotics “system” made up of many interrelated packages that integrate with ROS, MoveIt!, and other ROS tools to support industrial robot control and simulation.
Main components
• Robot Hardware and Interfaces – represent the physical FANUC robot (or multiple models such as M10ia, M20ia, etc.) and the underlying industrial control system.
• ROS Nodes for Robot Control – include driver nodes (e.g., fanuc_driver) that handle communication with the actual robot via motion streaming, state feedback, and possibly low-level control.
• Support/Description Packages – show packages that supply the robot description, URDF/XACRO models, meshes (collision and visual), and configuration files (joint parameters, kinematics, etc.). Group these under “robot support packages” (like fanuc_cr7ia_support, fanuc_m10ia_support, fanuc_m20ia_support, etc.).
• MoveIt Components – include separate MoveIt configuration packages (in the moveit_cfgs subfolder) and any associated plugins (in the moveit plugins folders). These handle motion planning, collision checking, and inverse kinematics using IKFast or other kinematics plugins.
• Build and Integration Tools – note that there is a standard ROS Catkin workspace structure, with CMakeLists.txt and package.xml files, along with CI-related configurations (e.g., GitHub workflows) that automate testing and building.
Relationships and interactions
• Dependency Relationships: The driver package depends on the support packages that provide the URDF, meshes, and configuration data. Similarly, MoveIt configuration packages rely on these descriptions to generate a robot model for planning.
• Integration Points: Illustrate how the MoveIt planning components integrate with sensor managers and the driver nodes via ROS topics and services.
• Build and Deployment: Optionally, add a block showing the CI (GitHub Actions) that triggers builds and tests within a Catkin workspace setup.
Architectural patterns and design principles
• Modularity: Each package (driver, support, MoveIt configuration) is self-contained and structured around ROS’s package-oriented ecosystem.
• Separation of Concerns: The robot description (URDF, meshes, configs) is separated from the driver logic and from planning/simulation tools.
• Community-Supported Development: Indicate that many packages are maintained on a best-effort basis with separate branches (e.g., noetic-devel for ROS Noetic).
Technologies and dependencies
• ROS (Robot Operating System) – outlines the communication middleware.
• Catkin Build System – for building and managing packages.
• MoveIt! – for motion planning and robot manipulation.
• IKFast and other kinematics solvers – integrated as plugins in MoveIt.
• Standard configuration files (CMakeLists.txt, package.xml) that dictate package dependencies.
• GitHub workflows for continuous integration (ci_ros1.yml).
Essential architectural elements
• Modular structure: show how multiple robot support packages exist side by side (each handling a particular model) and how they’re unified under the Fanuc meta-package.
• Links between ROS core, robot drivers, hardware, and higher-level planning (MoveIt configurations).
• Build and integration pipeline (for example, a side note on how “catkin build” and GitHub CI ensure system coherence).