# RMW_IMPLEMENTATION不匹配：发布者和订阅者使用不同的中间件实现，无法通信

- **ID:** `ros2/rmw-implementation-mismatch-discovery-failure`
- **领域:** ros2
- **类别:** network_error
- **验证级别:** ai_generated
- **修复率:** 85%

## 根因

ROS2节点必须使用相同的RMW实现（如rmw_fastrtps_cpp与rmw_cyclonedds_cpp）才能相互发现并交换消息，因为DDS协议变体或传输层不兼容。

## 版本兼容性

| 版本 | 状态 | 引入 | 弃用 |
|------|------|------|------|
| Humble | active | — | — |
| Iron | active | — | — |
| Rolling | active | — | — |

## 解决方案

1. ```
   Set the same RMW_IMPLEMENTATION environment variable for all nodes. For example, in a launch file or shell: export RMW_IMPLEMENTATION=rmw_fastrtps_cpp. Then restart all nodes.
   ```
2. ```
   If using Cyclone DDS, install the rmw_cyclonedds_cpp package and set RMW_IMPLEMENTATION=rmw_cyclonedds_cpp on all machines. For Fast DDS, use rmw_fastrtps_cpp. Run 'ros2 doctor' to verify current RMW.
   ```
3. ```
   To check current RMW: echo $RMW_IMPLEMENTATION. If unset, default is rmw_fastrtps_cpp. Use 'ros2 run demo_nodes_cpp talker' and 'listener' on the same RMW to test discovery.
   ```

## 无效尝试

- **** — Changing ROS_DOMAIN_ID only helps with network segmentation, not RMW incompatibility. Nodes on different RMWs will still not discover each other even on the same domain. (95% 失败率)
- **** — RMW mismatch is a protocol-level issue, not a network routing problem. Tuning discovery interfaces doesn't change the underlying DDS implementation incompatibility. (90% 失败率)
- **** — This only sets the default RMW at build time. If environment variable RMW_IMPLEMENTATION is set differently at runtime, the build-time setting is overridden. (75% 失败率)