Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- trigger:ros [2023/02/08 12:45] – [ROS Trigger integration] oliver
+++ trigger:ros [2023/02/08 12:50] (aktuell) – [Multi cycle recording] oliver
@@ Zeile 34: / Zeile 34: @@
 ^ loading_robot_program_timeout | Timeout in seconds waiting for a response after invocation of loading a robot program. Default value is 10s | Yes |
 ^ starting_robot_program_timeout | Timeout in seconds waiting for a response after invocation of starting a robot program. Default value is 10s | Yes |
-^ localhost | local host uri name, used, if it is not configured by a ROSMeasurementSystem. Can be used to define which of multiple networks cards should be used. | Yes |
+^ localhost | Local host uri name, used, if this is not configured by a ROSMeasurementSystem. Can be used to define which of multiple networks cards should be used. | Yes |
+^ masteruri | ROS master uri name, used, if this is not configured by a ROSMeasurementSystem. This is needed to find the ROS master. | Yes |
 ==== Multi cycle recording ====
@@ Zeile 48: / Zeile 49: @@
 It is possible to use the next-cycle-mechanism independed from the start/stop-triger-functionality. That means you can use a specific trigger implemenatation to load, start and stop a robot and you can use this ROS-implementation only to manage the next-cycle functionality.
+**Hint:** There is a strange bug, which results in, that the ROS-Client-Nodes do not find the ROS system, although the ROS master is found. In this case a in the hosts-file the name of the PC which hosts the ROS-Master has to be added mapping to the ip-adresses of the used network card.
 ==== The corresponding ROS package "robot_control" ====
 The ROS iTrigger implementation communicates with the ROS package [[https://github.com/MobMonRob/robot_control | robot_control]]. This package can be configured by properties in its launch files: