JDAQ

Benutzer-Werkzeuge

Webseiten-Werkzeuge

Zuletzt angesehen:
trigger:ros

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen RevisionVorhergehende Überarbeitung
Nächste Überarbeitung		Vorhergehende Überarbeitung
trigger:ros [2023/02/08 12:47] – [ROS Trigger integration] olivertrigger:ros [2023/02/08 12:50] (aktuell) – [Multi cycle recording] oliver
Zeile 49: 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. 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 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: 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:
trigger/ros.1675856849.txt.gz · Zuletzt geändert: 2023/02/08 12:47 von oliver
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki