How bharatm11/geomagic_touch_ros_drivers works
Main Components
• Hardware: 3D Systems Geomagic Touch haptic device.
• External Device Drivers & Libraries: OpenHaptics and Geomagic Touch device drivers (installed in /opt/OpenHaptics/ and /opt/geomagic_touch_device_driver/ respectively) along with low-level libraries like libraw1394, libPHANToMIO, libHD, and libHL.
• ROS Packages:
• omni_common: Contains the main driver logic including C++ source files (omni.cpp and omni_state.cpp), launch configurations (launch files for different modes), and a subfolder (dummyraw1394) that contains low-level hooks for device communication. This package is the central node that interfaces directly with the device via hardware libraries.
• omni_msgs: Defines custom ROS message types (OmniButtonEvent, OmniFeedback, and OmniState) that standardize the communication between the hardware interface node and other components or nodes in the ROS ecosystem.
• ROS Ecosystem (Middleware): The ROS core concepts (like the ROS Master, topics, and messages) that manage the communication between nodes.
Relationships and Interactions
• The haptic device communicates with the system via USB and its low-level drivers. The drivers (installed externally) provide an interface that is used by the "omni_common" package.
• The omni_common nodes process the device signals and convert them into standard ROS messages (as defined in omni_msgs). These messages are published on topics (such as /phantom/button, /phantom/force_feedback, /phantom/joint_states, /phantom/pose, and /phantom/state).
• The omni_description package holds the robot’s description (URDF and meshes) which is used by visualization tools (like RViz) to visually represent the device’s state and for simulation purposes.
• Launch files in omni_common coordinate the startup of these nodes. They define parameters and, in the case of dual device operation, orchestrate different device nodes with unique identifiers.
Architectural Patterns and Design Principles
• Modularity: Each package is designed to focus on a separate aspect of the overall system (driver functionality, robot description, message definitions), allowing for easy maintenance and potential future extension.
• Separation of Concerns: Hardware interfacing (within omni_common) is decoupled from the visual/model-related components (omni_description) and the standardized message definitions (omni_msgs).
• Standard ROS Communication: The system leverages ROS messaging (with custom message types) which simplifies integration with other ROS-based systems and nodes.
Relevant Technologies and Frameworks
• ROS (Robot Operating System): Central to the entire system for message passing, node management, and launching.
• C++: The primary language for the driver nodes within omni_common.
• CMake: For building the ROS packages, as indicated by the CMakeLists.txt files.
• URDF and RViz: Used for the robot description and visualization in omni_description.
Elements
• Clear Labels: Name each component (e.g., "3D Systems Geomagic Touch Hardware", "OpenHaptics / Geomagic Device Drivers", "omni_common Node", "omni_msgs Message Definitions", "omni_description URDF and Meshes", "ROS Master").
• Relationships: Mark dependencies such as the need for symbolic links to specific libraries (e.g., libraw1394, libPHANToMIO) that enable hardware communication.
Detailed Step-by-Step Outline
• "omni_description" component which provides URDF and meshes for visualization, and link it to the overall ROS ecosystem or directly to visualization tools such as RViz.