trigger:ros
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende Überarbeitung | ||
trigger:ros [2021/03/25 16:42] – [ROS Trigger integration] oliver | trigger:ros [2023/02/08 12:50] (aktuell) – [Multi cycle recording] oliver | ||
---|---|---|---|
Zeile 12: | Zeile 12: | ||
< | < | ||
< | < | ||
+ | <!-- optional properties, needed if no ROSMeasurementSystem is configured--> | ||
+ | < | ||
+ | < | ||
</ | </ | ||
... | ... | ||
Zeile 31: | 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 | | ^ 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 | | ^ 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 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 ==== | ==== Multi cycle recording ==== | ||
The ROS **iTrigger** implementation determines with invocation of the **nextCycle()** method the following properties, which are collected into the property group **modalities**. This property group is saved into the trial and the property **cycle_nr** is used as the suffix of the next recorded trial. | The ROS **iTrigger** implementation determines with invocation of the **nextCycle()** method the following properties, which are collected into the property group **modalities**. This property group is saved into the trial and the property **cycle_nr** is used as the suffix of the next recorded trial. | ||
Zeile 43: | Zeile 49: | ||
It is possible to use the next-cycle-mechanism independed from the start/ | It is possible to use the next-cycle-mechanism independed from the start/ | ||
+ | |||
+ | **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 " | ==== The corresponding ROS package " | ||
The ROS iTrigger implementation communicates with the ROS package [[https:// | The ROS iTrigger implementation communicates with the ROS package [[https:// |
trigger/ros.1616686948.txt.gz · Zuletzt geändert: 2021/03/25 16:42 von oliver