deploy: 1127510

foxy/.buildinfo

@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done.
-config: f2cc668ec2e4b368a153e368326056a6
+config: 8273c5d07943cd9199f00b477d740f03
 tags: 645f666f9bcd5a90fca523b33c5a78b7

foxy/index.html

@@ -150,7 +150,7 @@ <h2>Development Organisation and Communication<a class="headerlink" href="#devel
 </dd>
 </dl>
 <hr class="docutils" />
-<p>Built on 2024-11-25 at 13:40 GMT</p>
+<p>Built on 2024-11-26 at 05:39 GMT</p>
 </section>
 </section>
 

galactic/.buildinfo

@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done.
-config: 81019c0594f107ad0090e050fddbf77d
+config: 769f1b6bb2c8f5fb928282c13d50e46e
 tags: 645f666f9bcd5a90fca523b33c5a78b7

galactic/index.html

@@ -150,7 +150,7 @@ <h2>Development Organisation and Communication<a class="headerlink" href="#devel
 </dd>
 </dl>
 <hr class="docutils" />
-<p>Built on 2024-11-25 at 13:40 GMT</p>
+<p>Built on 2024-11-26 at 05:39 GMT</p>
 </section>
 </section>
 

humble/.buildinfo

@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done.
-config: 97d35193501531331febd4979640856d
+config: ce295f3bca30a1aa25435f294b16d246
 tags: 645f666f9bcd5a90fca523b33c5a78b7

humble/index.html

@@ -149,7 +149,7 @@ <h2>Development Organisation and Communication<a class="headerlink" href="#devel
 </dd>
 </dl>
 <hr class="docutils" />
-<p>Built on 2024-11-25 at 13:40 GMT</p>
+<p>Built on 2024-11-26 at 05:40 GMT</p>
 </section>
 </section>
 

iron/.buildinfo

@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done.
-config: c75edb6784f5329d5cdd0bb8325bd527
+config: fd7aaef0df7e4c66ea1276f408cbb670
 tags: 645f666f9bcd5a90fca523b33c5a78b7

iron/index.html

@@ -149,7 +149,7 @@ <h2>Development Organisation and Communication<a class="headerlink" href="#devel
 </dd>
 </dl>
 <hr class="docutils" />
-<p>Built on 2024-11-25 at 13:41 GMT</p>
+<p>Built on 2024-11-26 at 05:40 GMT</p>
 </section>
 </section>
 

jazzy/.buildinfo

@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done.
-config: 58ce2f8e8d396d09a178d36263dfd2d8
+config: ef13d5c766a086605822dc5709c96705
 tags: 645f666f9bcd5a90fca523b33c5a78b7

jazzy/_sources/doc/resources/resources.rst

@@ -45,6 +45,28 @@ Summary:
   Authors:
     - Sai Kishor Kothakota (PAL Robotics)
 
+2023-07-07 ROS Developers Day 2023: Configure a Mobile Manipulator with ros2_control
+,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
+
+`Recording <https://www.youtube.com/watch?v=LvBjVmZxxDA>`__
+
+`Github repo with code <https://github.com/bmagyar/rosdevday2023>`__
+
+TBD add Construct rosject link
+
+
+Summary:
+  In this hands-on presentation, we demonstrate how to set up a mobile manipulator with ros2_control in steps. First, we take a robot mobile base and demonstrate setting up ros2_control simulation for it in the URDF. Once done, a robot arm will be added to the mobile base, turning it into a mobile manipulator robot. The existing ros2_control configuration will be adjusted to accommodate for the new robot parts. Finally, the rosject concludes with a demonstration in Gazebo moving the robot using some off-the-shelf ros2_control controllers.
+
+  Attendees will learn
+
+  * how to prototype a mobile manipulator with URDF and ros2_control
+  * how to configure a gazebo simulation with a given URDF and ros2_control
+
+  *Presenter: Bence Magyar*
+
+  Authors:
+    - Dr. Bence Magyar (FiveAI / Bosch)
 
 2023-02 ROS Meetup Munich #5
 ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

jazzy/_sources/doc/ros2_control/controller_manager/doc/userdoc.rst

@@ -158,7 +158,7 @@ There are two scripts to interact with controller manager from launch files:
 
     $ ros2 run controller_manager spawner -h
     usage: spawner [-h] [-c CONTROLLER_MANAGER] [-p PARAM_FILE] [-n NAMESPACE] [--load-only] [--inactive] [-u] [--controller-manager-timeout CONTROLLER_MANAGER_TIMEOUT]
-                  [--switch-timeout SWITCH_TIMEOUT] [--activate-as-group]
+                  [--switch-timeout SWITCH_TIMEOUT] [--activate-as-group] [--service-call-timeout SERVICE_CALL_TIMEOUT]
                   controller_names [controller_names ...]
 
     positional arguments:
@@ -176,7 +176,9 @@ There are two scripts to interact with controller manager from launch files:
       --inactive            Load and configure the controller, however do not activate them
       -u, --unload-on-kill  Wait until this application is interrupted and unload controller
       --controller-manager-timeout CONTROLLER_MANAGER_TIMEOUT
-                            Time to wait for the controller manager
+                            Time to wait for the controller manager service to be available
+      --service-call-timeout SERVICE_CALL_TIMEOUT
+                            Time to wait for the service response from the controller manager
       --switch-timeout SWITCH_TIMEOUT
                             Time to wait for a successful state switch of controllers. Useful if controllers cannot be switched immediately, e.g., paused
                             simulations at startup

jazzy/_sources/doc/ros2_control/doc/release_notes.rst

@@ -81,6 +81,7 @@ controller_manager
 * The ``ros2_control_node`` node now accepts the ``thread_priority`` parameter to set the scheduler priority of the controller_manager's RT thread (`#1820 <https://github.com/ros-controls/ros2_control/pull/1820>`_).
 * The ``ros2_control_node`` node has a new ``lock_memory`` parameter to lock memory at startup to physical RAM in order to avoid page faults (`#1822 <https://github.com/ros-controls/ros2_control/pull/1822>`_).
 * The ``ros2_control_node`` node has a new ``cpu_affinity`` parameter to bind the process to a specific CPU core. By default, this is not enabled. (`#1852 <https://github.com/ros-controls/ros2_control/pull/1852>`_).
+* The ``--service-call-timeout`` was added as parameter to the helper scripts ``spawner.py``. Useful when the CPU load is high at startup and the service call does not return immediately (`#1808 <https://github.com/ros-controls/ros2_control/pull/1808>`_).
 
 hardware_interface
 ******************