![]() |
denso_robot_control package from denso_robot_ros2 repobcap_core bcap_service bcap_service_interfaces denso_robot_bringup denso_robot_control denso_robot_core denso_robot_core_interfaces denso_robot_description_installer denso_robot_descriptions denso_robot_moveit_config denso_robot_moveit_demo |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.2.0 |
License | MIT |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/densorobot/denso_robot_ros2.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-03-14 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- DENSO WAVE INCORPORATED
Authors
- DENSO WAVE INCORPORATED
SlaveMode Control for DENSO Robots
The SlaveMode control modality allows to control DENSO robots by sending the whole trajectory of the robotic arm. The trajectory must be generated by an external motion planner (e.g. MoveIt2), and target points must be sent to the robot controller.
NOTE: The minimum required control frequency is 125 Hz (1 target position each 8 ms).
Usage
1.a Connect to a WINCAPS III-simulated Robot (Optional)
When connecting to a real robot, please be sure to complete the steps for WINCAPS III preparation as described here.
1.b Connect to a Real Controller (Optional)
When connecting to a real robot, please be sure to complete the steps for robot preparation as described here.
2. Start ROS2 Nodes
The main launch file that starts the application is in the denso_robot_bringup
package.
- COBOTTA robot:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=cobotta sim:=false ip_address:=192.168.0.1 send_format:=0 recv_format:=2
- NOT COBOTTA robots (e.g. VS-060 robot):
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=vs060 sim:=false ip_address:=192.168.0.1 send_format:=256 recv_format:=258
2.1 Launch File Details
The main launch file that starts the application is in the denso_robot_bringup
package:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=<robot_model> sim:=false ip_address:=<robot_ip_address> send_format:=<send_format_value> recv_format:=<recv_format_value>
The arguments for launch files can be listed using:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py --show-args
The most relevant arguments are the following:
-
model
(mandatory) - the model of the DENSO robot (COBOTTA, VS-060, etc.). In the original DENSO ROS2 stack 2 robot models are already available ( “cobotta” , “vs060”). To use other robot types, see the ROS2Converter page (under construction) for creating the URDF model and the associated MoveIt2 configuration package -
ip_address
(mandatory) - IP address of the robot -
sim
(default: true) - whether the robot is simulated (Gazebo simulator) or an RC8 controller is connected (either WINCAPS III-simulated or real controller) -
send_format
(default: 288) - parameter to write Hand I/O, Mini I/O or User I/O signals (not considered ifsim:=true
). When Connecting to a COBOTTA robot assign value “0” (no IO configuration) -
recv_format
(default: 292) - parameter to read Hand I/O, Mini I/O or User I/O signals (not considered ifsim:=true
). When Connecting to a COBOTTA robot assign value “2” (no IO configuration) -
bcap_slave_control_cycle_msec
(default: 8.0) - DENSO robot control cycle [ms] (not considered ifsim:=true
)
DENSO ROS2 stack (simulation) |
---|
![]() |
2.2 Send Format Parameter
The send_format parameter can be used for write Hand I/O, Mini I/O or User I/O. Following table shows the details of the send_format parameter.
Value | I/O |
---|---|
0 | None |
32 | Hand I/O (Port 64 to 71) |
256 | Mini I/O (Port 16 to 31) |
288 | Hand I/O and Mini I/O |
512 | User I/O (Port 128 or after) |
544 | Hand I/O and User I/O |
2.3 Receive Format Parameter
The recv_format parameter can be used for write Hand I/O, Mini I/O or User I/O. Following table shows the details of the recv_format parameter.
Value | I/O |
---|---|
0 | None |
34 | Hand I/O (Port 48 to 55 and 64 to 71) |
258 | Mini I/O (Port 0 to 31) |
290 | Hand I/O and Mini I/O |
514 | User I/O (Port 128 or after) |
546 | Hand I/O and User I/O |
3. Read and Write I/O Lines (Optional)
When setting the send_format and recv_format parameters, proper subscribers and publishers are launched.
File truncated at 100 lines see the full file
Changelog for package denso_robot_control
1.2.0 (2024-03-18)
- Implemented support for ROS2 Humble
- Avoid Boost C++ Libaries
1.1.1 (2024-02-09)
- Remove "under construction" sections from README.md
1.1.0 (2023-03-24)
Initial release
Package Dependencies
System Dependencies
Dependant Packages
Name | Deps |
---|---|
denso_robot_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged denso_robot_control at Robotics Stack Exchange
![]() |
denso_robot_control package from denso_robot_ros2 repobcap_core bcap_service bcap_service_interfaces denso_robot_bringup denso_robot_control denso_robot_core denso_robot_core_interfaces denso_robot_description_installer denso_robot_descriptions denso_robot_moveit_config denso_robot_moveit_demo |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.2.0 |
License | MIT |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/densorobot/denso_robot_ros2.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-03-14 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- DENSO WAVE INCORPORATED
Authors
- DENSO WAVE INCORPORATED
SlaveMode Control for DENSO Robots
The SlaveMode control modality allows to control DENSO robots by sending the whole trajectory of the robotic arm. The trajectory must be generated by an external motion planner (e.g. MoveIt2), and target points must be sent to the robot controller.
NOTE: The minimum required control frequency is 125 Hz (1 target position each 8 ms).
Usage
1.a Connect to a WINCAPS III-simulated Robot (Optional)
When connecting to a real robot, please be sure to complete the steps for WINCAPS III preparation as described here.
1.b Connect to a Real Controller (Optional)
When connecting to a real robot, please be sure to complete the steps for robot preparation as described here.
2. Start ROS2 Nodes
The main launch file that starts the application is in the denso_robot_bringup
package.
- COBOTTA robot:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=cobotta sim:=false ip_address:=192.168.0.1 send_format:=0 recv_format:=2
- NOT COBOTTA robots (e.g. VS-060 robot):
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=vs060 sim:=false ip_address:=192.168.0.1 send_format:=256 recv_format:=258
2.1 Launch File Details
The main launch file that starts the application is in the denso_robot_bringup
package:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=<robot_model> sim:=false ip_address:=<robot_ip_address> send_format:=<send_format_value> recv_format:=<recv_format_value>
The arguments for launch files can be listed using:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py --show-args
The most relevant arguments are the following:
-
model
(mandatory) - the model of the DENSO robot (COBOTTA, VS-060, etc.). In the original DENSO ROS2 stack 2 robot models are already available ( “cobotta” , “vs060”). To use other robot types, see the ROS2Converter page (under construction) for creating the URDF model and the associated MoveIt2 configuration package -
ip_address
(mandatory) - IP address of the robot -
sim
(default: true) - whether the robot is simulated (Gazebo simulator) or an RC8 controller is connected (either WINCAPS III-simulated or real controller) -
send_format
(default: 288) - parameter to write Hand I/O, Mini I/O or User I/O signals (not considered ifsim:=true
). When Connecting to a COBOTTA robot assign value “0” (no IO configuration) -
recv_format
(default: 292) - parameter to read Hand I/O, Mini I/O or User I/O signals (not considered ifsim:=true
). When Connecting to a COBOTTA robot assign value “2” (no IO configuration) -
bcap_slave_control_cycle_msec
(default: 8.0) - DENSO robot control cycle [ms] (not considered ifsim:=true
)
DENSO ROS2 stack (simulation) |
---|
![]() |
2.2 Send Format Parameter
The send_format parameter can be used for write Hand I/O, Mini I/O or User I/O. Following table shows the details of the send_format parameter.
Value | I/O |
---|---|
0 | None |
32 | Hand I/O (Port 64 to 71) |
256 | Mini I/O (Port 16 to 31) |
288 | Hand I/O and Mini I/O |
512 | User I/O (Port 128 or after) |
544 | Hand I/O and User I/O |
2.3 Receive Format Parameter
The recv_format parameter can be used for write Hand I/O, Mini I/O or User I/O. Following table shows the details of the recv_format parameter.
Value | I/O |
---|---|
0 | None |
34 | Hand I/O (Port 48 to 55 and 64 to 71) |
258 | Mini I/O (Port 0 to 31) |
290 | Hand I/O and Mini I/O |
514 | User I/O (Port 128 or after) |
546 | Hand I/O and User I/O |
3. Read and Write I/O Lines (Optional)
When setting the send_format and recv_format parameters, proper subscribers and publishers are launched.
File truncated at 100 lines see the full file
Changelog for package denso_robot_control
1.2.0 (2024-03-18)
- Implemented support for ROS2 Humble
- Avoid Boost C++ Libaries
1.1.1 (2024-02-09)
- Remove "under construction" sections from README.md
1.1.0 (2023-03-24)
Initial release
Package Dependencies
System Dependencies
Dependant Packages
Name | Deps |
---|---|
denso_robot_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged denso_robot_control at Robotics Stack Exchange
![]() |
denso_robot_control package from denso_robot_ros2 repobcap_core bcap_service bcap_service_interfaces denso_robot_bringup denso_robot_control denso_robot_core denso_robot_core_interfaces denso_robot_description_installer denso_robot_descriptions denso_robot_moveit_config denso_robot_moveit_demo |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.2.0 |
License | MIT |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/densorobot/denso_robot_ros2.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-03-14 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- DENSO WAVE INCORPORATED
Authors
- DENSO WAVE INCORPORATED
SlaveMode Control for DENSO Robots
The SlaveMode control modality allows to control DENSO robots by sending the whole trajectory of the robotic arm. The trajectory must be generated by an external motion planner (e.g. MoveIt2), and target points must be sent to the robot controller.
NOTE: The minimum required control frequency is 125 Hz (1 target position each 8 ms).
Usage
1.a Connect to a WINCAPS III-simulated Robot (Optional)
When connecting to a real robot, please be sure to complete the steps for WINCAPS III preparation as described here.
1.b Connect to a Real Controller (Optional)
When connecting to a real robot, please be sure to complete the steps for robot preparation as described here.
2. Start ROS2 Nodes
The main launch file that starts the application is in the denso_robot_bringup
package.
- COBOTTA robot:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=cobotta sim:=false ip_address:=192.168.0.1 send_format:=0 recv_format:=2
- NOT COBOTTA robots (e.g. VS-060 robot):
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=vs060 sim:=false ip_address:=192.168.0.1 send_format:=256 recv_format:=258
2.1 Launch File Details
The main launch file that starts the application is in the denso_robot_bringup
package:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=<robot_model> sim:=false ip_address:=<robot_ip_address> send_format:=<send_format_value> recv_format:=<recv_format_value>
The arguments for launch files can be listed using:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py --show-args
The most relevant arguments are the following:
-
model
(mandatory) - the model of the DENSO robot (COBOTTA, VS-060, etc.). In the original DENSO ROS2 stack 2 robot models are already available ( “cobotta” , “vs060”). To use other robot types, see the ROS2Converter page (under construction) for creating the URDF model and the associated MoveIt2 configuration package -
ip_address
(mandatory) - IP address of the robot -
sim
(default: true) - whether the robot is simulated (Gazebo simulator) or an RC8 controller is connected (either WINCAPS III-simulated or real controller) -
send_format
(default: 288) - parameter to write Hand I/O, Mini I/O or User I/O signals (not considered ifsim:=true
). When Connecting to a COBOTTA robot assign value “0” (no IO configuration) -
recv_format
(default: 292) - parameter to read Hand I/O, Mini I/O or User I/O signals (not considered ifsim:=true
). When Connecting to a COBOTTA robot assign value “2” (no IO configuration) -
bcap_slave_control_cycle_msec
(default: 8.0) - DENSO robot control cycle [ms] (not considered ifsim:=true
)
DENSO ROS2 stack (simulation) |
---|
![]() |
2.2 Send Format Parameter
The send_format parameter can be used for write Hand I/O, Mini I/O or User I/O. Following table shows the details of the send_format parameter.
Value | I/O |
---|---|
0 | None |
32 | Hand I/O (Port 64 to 71) |
256 | Mini I/O (Port 16 to 31) |
288 | Hand I/O and Mini I/O |
512 | User I/O (Port 128 or after) |
544 | Hand I/O and User I/O |
2.3 Receive Format Parameter
The recv_format parameter can be used for write Hand I/O, Mini I/O or User I/O. Following table shows the details of the recv_format parameter.
Value | I/O |
---|---|
0 | None |
34 | Hand I/O (Port 48 to 55 and 64 to 71) |
258 | Mini I/O (Port 0 to 31) |
290 | Hand I/O and Mini I/O |
514 | User I/O (Port 128 or after) |
546 | Hand I/O and User I/O |
3. Read and Write I/O Lines (Optional)
When setting the send_format and recv_format parameters, proper subscribers and publishers are launched.
File truncated at 100 lines see the full file
Changelog for package denso_robot_control
1.2.0 (2024-03-18)
- Implemented support for ROS2 Humble
- Avoid Boost C++ Libaries
1.1.1 (2024-02-09)
- Remove "under construction" sections from README.md
1.1.0 (2023-03-24)
Initial release
Package Dependencies
System Dependencies
Dependant Packages
Name | Deps |
---|---|
denso_robot_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged denso_robot_control at Robotics Stack Exchange
![]() |
denso_robot_control package from denso_robot_ros2 repobcap_core bcap_service bcap_service_interfaces denso_robot_bringup denso_robot_control denso_robot_core denso_robot_core_interfaces denso_robot_description_installer denso_robot_descriptions denso_robot_moveit_config denso_robot_moveit_demo |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.2.0 |
License | MIT |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/densorobot/denso_robot_ros2.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-03-14 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- DENSO WAVE INCORPORATED
Authors
- DENSO WAVE INCORPORATED
SlaveMode Control for DENSO Robots
The SlaveMode control modality allows to control DENSO robots by sending the whole trajectory of the robotic arm. The trajectory must be generated by an external motion planner (e.g. MoveIt2), and target points must be sent to the robot controller.
NOTE: The minimum required control frequency is 125 Hz (1 target position each 8 ms).
Usage
1.a Connect to a WINCAPS III-simulated Robot (Optional)
When connecting to a real robot, please be sure to complete the steps for WINCAPS III preparation as described here.
1.b Connect to a Real Controller (Optional)
When connecting to a real robot, please be sure to complete the steps for robot preparation as described here.
2. Start ROS2 Nodes
The main launch file that starts the application is in the denso_robot_bringup
package.
- COBOTTA robot:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=cobotta sim:=false ip_address:=192.168.0.1 send_format:=0 recv_format:=2
- NOT COBOTTA robots (e.g. VS-060 robot):
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=vs060 sim:=false ip_address:=192.168.0.1 send_format:=256 recv_format:=258
2.1 Launch File Details
The main launch file that starts the application is in the denso_robot_bringup
package:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=<robot_model> sim:=false ip_address:=<robot_ip_address> send_format:=<send_format_value> recv_format:=<recv_format_value>
The arguments for launch files can be listed using:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py --show-args
The most relevant arguments are the following:
-
model
(mandatory) - the model of the DENSO robot (COBOTTA, VS-060, etc.). In the original DENSO ROS2 stack 2 robot models are already available ( “cobotta” , “vs060”). To use other robot types, see the ROS2Converter page (under construction) for creating the URDF model and the associated MoveIt2 configuration package -
ip_address
(mandatory) - IP address of the robot -
sim
(default: true) - whether the robot is simulated (Gazebo simulator) or an RC8 controller is connected (either WINCAPS III-simulated or real controller) -
send_format
(default: 288) - parameter to write Hand I/O, Mini I/O or User I/O signals (not considered ifsim:=true
). When Connecting to a COBOTTA robot assign value “0” (no IO configuration) -
recv_format
(default: 292) - parameter to read Hand I/O, Mini I/O or User I/O signals (not considered ifsim:=true
). When Connecting to a COBOTTA robot assign value “2” (no IO configuration) -
bcap_slave_control_cycle_msec
(default: 8.0) - DENSO robot control cycle [ms] (not considered ifsim:=true
)
DENSO ROS2 stack (simulation) |
---|
![]() |
2.2 Send Format Parameter
The send_format parameter can be used for write Hand I/O, Mini I/O or User I/O. Following table shows the details of the send_format parameter.
Value | I/O |
---|---|
0 | None |
32 | Hand I/O (Port 64 to 71) |
256 | Mini I/O (Port 16 to 31) |
288 | Hand I/O and Mini I/O |
512 | User I/O (Port 128 or after) |
544 | Hand I/O and User I/O |
2.3 Receive Format Parameter
The recv_format parameter can be used for write Hand I/O, Mini I/O or User I/O. Following table shows the details of the recv_format parameter.
Value | I/O |
---|---|
0 | None |
34 | Hand I/O (Port 48 to 55 and 64 to 71) |
258 | Mini I/O (Port 0 to 31) |
290 | Hand I/O and Mini I/O |
514 | User I/O (Port 128 or after) |
546 | Hand I/O and User I/O |
3. Read and Write I/O Lines (Optional)
When setting the send_format and recv_format parameters, proper subscribers and publishers are launched.
File truncated at 100 lines see the full file
Changelog for package denso_robot_control
1.2.0 (2024-03-18)
- Implemented support for ROS2 Humble
- Avoid Boost C++ Libaries
1.1.1 (2024-02-09)
- Remove "under construction" sections from README.md
1.1.0 (2023-03-24)
Initial release
Package Dependencies
System Dependencies
Dependant Packages
Name | Deps |
---|---|
denso_robot_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged denso_robot_control at Robotics Stack Exchange
![]() |
denso_robot_control package from denso_robot_ros2 repobcap_core bcap_service bcap_service_interfaces denso_robot_bringup denso_robot_control denso_robot_core denso_robot_core_interfaces denso_robot_description_installer denso_robot_descriptions denso_robot_moveit_config denso_robot_moveit_demo |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.2.0 |
License | MIT |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/densorobot/denso_robot_ros2.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-03-14 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- DENSO WAVE INCORPORATED
Authors
- DENSO WAVE INCORPORATED
SlaveMode Control for DENSO Robots
The SlaveMode control modality allows to control DENSO robots by sending the whole trajectory of the robotic arm. The trajectory must be generated by an external motion planner (e.g. MoveIt2), and target points must be sent to the robot controller.
NOTE: The minimum required control frequency is 125 Hz (1 target position each 8 ms).
Usage
1.a Connect to a WINCAPS III-simulated Robot (Optional)
When connecting to a real robot, please be sure to complete the steps for WINCAPS III preparation as described here.
1.b Connect to a Real Controller (Optional)
When connecting to a real robot, please be sure to complete the steps for robot preparation as described here.
2. Start ROS2 Nodes
The main launch file that starts the application is in the denso_robot_bringup
package.
- COBOTTA robot:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=cobotta sim:=false ip_address:=192.168.0.1 send_format:=0 recv_format:=2
- NOT COBOTTA robots (e.g. VS-060 robot):
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=vs060 sim:=false ip_address:=192.168.0.1 send_format:=256 recv_format:=258
2.1 Launch File Details
The main launch file that starts the application is in the denso_robot_bringup
package:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=<robot_model> sim:=false ip_address:=<robot_ip_address> send_format:=<send_format_value> recv_format:=<recv_format_value>
The arguments for launch files can be listed using:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py --show-args
The most relevant arguments are the following:
-
model
(mandatory) - the model of the DENSO robot (COBOTTA, VS-060, etc.). In the original DENSO ROS2 stack 2 robot models are already available ( “cobotta” , “vs060”). To use other robot types, see the ROS2Converter page (under construction) for creating the URDF model and the associated MoveIt2 configuration package -
ip_address
(mandatory) - IP address of the robot -
sim
(default: true) - whether the robot is simulated (Gazebo simulator) or an RC8 controller is connected (either WINCAPS III-simulated or real controller) -
send_format
(default: 288) - parameter to write Hand I/O, Mini I/O or User I/O signals (not considered ifsim:=true
). When Connecting to a COBOTTA robot assign value “0” (no IO configuration) -
recv_format
(default: 292) - parameter to read Hand I/O, Mini I/O or User I/O signals (not considered ifsim:=true
). When Connecting to a COBOTTA robot assign value “2” (no IO configuration) -
bcap_slave_control_cycle_msec
(default: 8.0) - DENSO robot control cycle [ms] (not considered ifsim:=true
)
DENSO ROS2 stack (simulation) |
---|
![]() |
2.2 Send Format Parameter
The send_format parameter can be used for write Hand I/O, Mini I/O or User I/O. Following table shows the details of the send_format parameter.
Value | I/O |
---|---|
0 | None |
32 | Hand I/O (Port 64 to 71) |
256 | Mini I/O (Port 16 to 31) |
288 | Hand I/O and Mini I/O |
512 | User I/O (Port 128 or after) |
544 | Hand I/O and User I/O |
2.3 Receive Format Parameter
The recv_format parameter can be used for write Hand I/O, Mini I/O or User I/O. Following table shows the details of the recv_format parameter.
Value | I/O |
---|---|
0 | None |
34 | Hand I/O (Port 48 to 55 and 64 to 71) |
258 | Mini I/O (Port 0 to 31) |
290 | Hand I/O and Mini I/O |
514 | User I/O (Port 128 or after) |
546 | Hand I/O and User I/O |
3. Read and Write I/O Lines (Optional)
When setting the send_format and recv_format parameters, proper subscribers and publishers are launched.
File truncated at 100 lines see the full file
Changelog for package denso_robot_control
1.2.0 (2024-03-18)
- Implemented support for ROS2 Humble
- Avoid Boost C++ Libaries
1.1.1 (2024-02-09)
- Remove "under construction" sections from README.md
1.1.0 (2023-03-24)
Initial release
Package Dependencies
System Dependencies
Dependant Packages
Name | Deps |
---|---|
denso_robot_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged denso_robot_control at Robotics Stack Exchange
![]() |
denso_robot_control package from denso_robot_ros2 repobcap_core bcap_service bcap_service_interfaces denso_robot_bringup denso_robot_control denso_robot_core denso_robot_core_interfaces denso_robot_description_installer denso_robot_descriptions denso_robot_moveit_config denso_robot_moveit_demo |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.2.0 |
License | MIT |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/densorobot/denso_robot_ros2.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-03-14 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- DENSO WAVE INCORPORATED
Authors
- DENSO WAVE INCORPORATED
SlaveMode Control for DENSO Robots
The SlaveMode control modality allows to control DENSO robots by sending the whole trajectory of the robotic arm. The trajectory must be generated by an external motion planner (e.g. MoveIt2), and target points must be sent to the robot controller.
NOTE: The minimum required control frequency is 125 Hz (1 target position each 8 ms).
Usage
1.a Connect to a WINCAPS III-simulated Robot (Optional)
When connecting to a real robot, please be sure to complete the steps for WINCAPS III preparation as described here.
1.b Connect to a Real Controller (Optional)
When connecting to a real robot, please be sure to complete the steps for robot preparation as described here.
2. Start ROS2 Nodes
The main launch file that starts the application is in the denso_robot_bringup
package.
- COBOTTA robot:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=cobotta sim:=false ip_address:=192.168.0.1 send_format:=0 recv_format:=2
- NOT COBOTTA robots (e.g. VS-060 robot):
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=vs060 sim:=false ip_address:=192.168.0.1 send_format:=256 recv_format:=258
2.1 Launch File Details
The main launch file that starts the application is in the denso_robot_bringup
package:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=<robot_model> sim:=false ip_address:=<robot_ip_address> send_format:=<send_format_value> recv_format:=<recv_format_value>
The arguments for launch files can be listed using:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py --show-args
The most relevant arguments are the following:
-
model
(mandatory) - the model of the DENSO robot (COBOTTA, VS-060, etc.). In the original DENSO ROS2 stack 2 robot models are already available ( “cobotta” , “vs060”). To use other robot types, see the ROS2Converter page (under construction) for creating the URDF model and the associated MoveIt2 configuration package -
ip_address
(mandatory) - IP address of the robot -
sim
(default: true) - whether the robot is simulated (Gazebo simulator) or an RC8 controller is connected (either WINCAPS III-simulated or real controller) -
send_format
(default: 288) - parameter to write Hand I/O, Mini I/O or User I/O signals (not considered ifsim:=true
). When Connecting to a COBOTTA robot assign value “0” (no IO configuration) -
recv_format
(default: 292) - parameter to read Hand I/O, Mini I/O or User I/O signals (not considered ifsim:=true
). When Connecting to a COBOTTA robot assign value “2” (no IO configuration) -
bcap_slave_control_cycle_msec
(default: 8.0) - DENSO robot control cycle [ms] (not considered ifsim:=true
)
DENSO ROS2 stack (simulation) |
---|
![]() |
2.2 Send Format Parameter
The send_format parameter can be used for write Hand I/O, Mini I/O or User I/O. Following table shows the details of the send_format parameter.
Value | I/O |
---|---|
0 | None |
32 | Hand I/O (Port 64 to 71) |
256 | Mini I/O (Port 16 to 31) |
288 | Hand I/O and Mini I/O |
512 | User I/O (Port 128 or after) |
544 | Hand I/O and User I/O |
2.3 Receive Format Parameter
The recv_format parameter can be used for write Hand I/O, Mini I/O or User I/O. Following table shows the details of the recv_format parameter.
Value | I/O |
---|---|
0 | None |
34 | Hand I/O (Port 48 to 55 and 64 to 71) |
258 | Mini I/O (Port 0 to 31) |
290 | Hand I/O and Mini I/O |
514 | User I/O (Port 128 or after) |
546 | Hand I/O and User I/O |
3. Read and Write I/O Lines (Optional)
When setting the send_format and recv_format parameters, proper subscribers and publishers are launched.
File truncated at 100 lines see the full file
Changelog for package denso_robot_control
1.2.0 (2024-03-18)
- Implemented support for ROS2 Humble
- Avoid Boost C++ Libaries
1.1.1 (2024-02-09)
- Remove "under construction" sections from README.md
1.1.0 (2023-03-24)
Initial release
Package Dependencies
System Dependencies
Dependant Packages
Name | Deps |
---|---|
denso_robot_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged denso_robot_control at Robotics Stack Exchange
![]() |
denso_robot_control package from denso_robot_ros2 repobcap_core bcap_service bcap_service_interfaces denso_robot_bringup denso_robot_control denso_robot_core denso_robot_core_interfaces denso_robot_description_installer denso_robot_descriptions denso_robot_moveit_config denso_robot_moveit_demo |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.2.0 |
License | MIT |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/densorobot/denso_robot_ros2.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-03-14 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- DENSO WAVE INCORPORATED
Authors
- DENSO WAVE INCORPORATED
SlaveMode Control for DENSO Robots
The SlaveMode control modality allows to control DENSO robots by sending the whole trajectory of the robotic arm. The trajectory must be generated by an external motion planner (e.g. MoveIt2), and target points must be sent to the robot controller.
NOTE: The minimum required control frequency is 125 Hz (1 target position each 8 ms).
Usage
1.a Connect to a WINCAPS III-simulated Robot (Optional)
When connecting to a real robot, please be sure to complete the steps for WINCAPS III preparation as described here.
1.b Connect to a Real Controller (Optional)
When connecting to a real robot, please be sure to complete the steps for robot preparation as described here.
2. Start ROS2 Nodes
The main launch file that starts the application is in the denso_robot_bringup
package.
- COBOTTA robot:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=cobotta sim:=false ip_address:=192.168.0.1 send_format:=0 recv_format:=2
- NOT COBOTTA robots (e.g. VS-060 robot):
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=vs060 sim:=false ip_address:=192.168.0.1 send_format:=256 recv_format:=258
2.1 Launch File Details
The main launch file that starts the application is in the denso_robot_bringup
package:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=<robot_model> sim:=false ip_address:=<robot_ip_address> send_format:=<send_format_value> recv_format:=<recv_format_value>
The arguments for launch files can be listed using:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py --show-args
The most relevant arguments are the following:
-
model
(mandatory) - the model of the DENSO robot (COBOTTA, VS-060, etc.). In the original DENSO ROS2 stack 2 robot models are already available ( “cobotta” , “vs060”). To use other robot types, see the ROS2Converter page (under construction) for creating the URDF model and the associated MoveIt2 configuration package -
ip_address
(mandatory) - IP address of the robot -
sim
(default: true) - whether the robot is simulated (Gazebo simulator) or an RC8 controller is connected (either WINCAPS III-simulated or real controller) -
send_format
(default: 288) - parameter to write Hand I/O, Mini I/O or User I/O signals (not considered ifsim:=true
). When Connecting to a COBOTTA robot assign value “0” (no IO configuration) -
recv_format
(default: 292) - parameter to read Hand I/O, Mini I/O or User I/O signals (not considered ifsim:=true
). When Connecting to a COBOTTA robot assign value “2” (no IO configuration) -
bcap_slave_control_cycle_msec
(default: 8.0) - DENSO robot control cycle [ms] (not considered ifsim:=true
)
DENSO ROS2 stack (simulation) |
---|
![]() |
2.2 Send Format Parameter
The send_format parameter can be used for write Hand I/O, Mini I/O or User I/O. Following table shows the details of the send_format parameter.
Value | I/O |
---|---|
0 | None |
32 | Hand I/O (Port 64 to 71) |
256 | Mini I/O (Port 16 to 31) |
288 | Hand I/O and Mini I/O |
512 | User I/O (Port 128 or after) |
544 | Hand I/O and User I/O |
2.3 Receive Format Parameter
The recv_format parameter can be used for write Hand I/O, Mini I/O or User I/O. Following table shows the details of the recv_format parameter.
Value | I/O |
---|---|
0 | None |
34 | Hand I/O (Port 48 to 55 and 64 to 71) |
258 | Mini I/O (Port 0 to 31) |
290 | Hand I/O and Mini I/O |
514 | User I/O (Port 128 or after) |
546 | Hand I/O and User I/O |
3. Read and Write I/O Lines (Optional)
When setting the send_format and recv_format parameters, proper subscribers and publishers are launched.
File truncated at 100 lines see the full file
Changelog for package denso_robot_control
1.2.0 (2024-03-18)
- Implemented support for ROS2 Humble
- Avoid Boost C++ Libaries
1.1.1 (2024-02-09)
- Remove "under construction" sections from README.md
1.1.0 (2023-03-24)
Initial release
Package Dependencies
System Dependencies
Dependant Packages
Name | Deps |
---|---|
denso_robot_bringup |
Launch files
Messages
Services
Plugins
Recent questions tagged denso_robot_control at Robotics Stack Exchange
![]() |
denso_robot_control package from denso_robot_ros repobcap_core bcap_service bcap_service_test denso_robot_bringup denso_robot_control denso_robot_core denso_robot_core_test denso_robot_descriptions denso_robot_gazebo denso_robot_moveit_config denso_robot_ros |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.2.0 |
License | MIT |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/DENSORobot/denso_robot_ros.git |
VCS Type | git |
VCS Version | melodic-devel |
Last Updated | 2021-06-03 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- DENSO WAVE INCORPORATED
Authors
- DENSO WAVE INCORPORATED
Changelog for package denso_robot_control
3.2.0 (2021-06-02)
- Add "ResetStoState" to initialization
3.1.2 (2021-04-02)
3.1.1 (2021-03-03)
- Add ros::spinOnce() for the callbacks
3.1.0 (2020-12-23)
- Add supporting for RC9
- Add bcap_slave_control_cycle_msec
- Add error descriptions of controller
- Fix send_format/recv_format
- Fix Int32 to UInt32 of MiniIO and HandIO
- Remove first 5-seconds-sleep in main()
3.0.4 (2019-11-27)
3.0.3 (2019-09-23)
- Change to sleep in only slave sync mode
3.0.2 (2017-12-15)
- Add clear error step before motor on
- Add subscriber and publisher for I/O function
- Add I/O function for denso_robot_control
- Remove new line from ROS_INFO,ROS_WARN,ROS_ERROR
- Change descriptions and add url, author
- Check the catkin_lint result
- Contributors: MIYAKOSHI Yoshihiro
Forthcoming
- update version to 3.0.0
- first commit
- Contributors: MIYAKOSHI Yoshihiro
Package Dependencies
Deps | Name |
---|---|
bcap_core | |
bcap_service | |
controller_manager | |
denso_robot_core | |
hardware_interface | |
joint_limits_interface | |
roscpp | |
std_msgs | |
transmission_interface | |
catkin |
System Dependencies
Dependant Packages
Name | Deps |
---|---|
denso_robot_ros |
Launch files
- launch/denso_robot_control.launch
-
- ip_address [default: 192.168.0.1]
- robot_name [default: vs060]
- send_format [default: 288]
- recv_format [default: 292]
- bcap_slave_control_cycle_msec [default: 8]
- launch/denso_robot_control.launch.xml
-
- send_format [default: 288]
- recv_format [default: 292]
Messages
Services
Plugins
Recent questions tagged denso_robot_control at Robotics Stack Exchange
![]() |
denso_robot_control package from denso_robot_ros2 repobcap_core bcap_service bcap_service_interfaces denso_robot_bringup denso_robot_control denso_robot_core denso_robot_core_interfaces denso_robot_description_installer denso_robot_descriptions denso_robot_moveit_config denso_robot_moveit_demo |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.2.0 |
License | MIT |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/densorobot/denso_robot_ros2.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-03-14 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- DENSO WAVE INCORPORATED
Authors
- DENSO WAVE INCORPORATED
SlaveMode Control for DENSO Robots
The SlaveMode control modality allows to control DENSO robots by sending the whole trajectory of the robotic arm. The trajectory must be generated by an external motion planner (e.g. MoveIt2), and target points must be sent to the robot controller.
NOTE: The minimum required control frequency is 125 Hz (1 target position each 8 ms).
Usage
1.a Connect to a WINCAPS III-simulated Robot (Optional)
When connecting to a real robot, please be sure to complete the steps for WINCAPS III preparation as described here.
1.b Connect to a Real Controller (Optional)
When connecting to a real robot, please be sure to complete the steps for robot preparation as described here.
2. Start ROS2 Nodes
The main launch file that starts the application is in the denso_robot_bringup
package.
- COBOTTA robot:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=cobotta sim:=false ip_address:=192.168.0.1 send_format:=0 recv_format:=2
- NOT COBOTTA robots (e.g. VS-060 robot):
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=vs060 sim:=false ip_address:=192.168.0.1 send_format:=256 recv_format:=258
2.1 Launch File Details
The main launch file that starts the application is in the denso_robot_bringup
package:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py model:=<robot_model> sim:=false ip_address:=<robot_ip_address> send_format:=<send_format_value> recv_format:=<recv_format_value>
The arguments for launch files can be listed using:
ros2 launch denso_robot_bringup denso_robot_bringup.launch.py --show-args
The most relevant arguments are the following:
-
model
(mandatory) - the model of the DENSO robot (COBOTTA, VS-060, etc.). In the original DENSO ROS2 stack 2 robot models are already available ( “cobotta” , “vs060”). To use other robot types, see the ROS2Converter page (under construction) for creating the URDF model and the associated MoveIt2 configuration package -
ip_address
(mandatory) - IP address of the robot -
sim
(default: true) - whether the robot is simulated (Gazebo simulator) or an RC8 controller is connected (either WINCAPS III-simulated or real controller) -
send_format
(default: 288) - parameter to write Hand I/O, Mini I/O or User I/O signals (not considered ifsim:=true
). When Connecting to a COBOTTA robot assign value “0” (no IO configuration) -
recv_format
(default: 292) - parameter to read Hand I/O, Mini I/O or User I/O signals (not considered ifsim:=true
). When Connecting to a COBOTTA robot assign value “2” (no IO configuration) -
bcap_slave_control_cycle_msec
(default: 8.0) - DENSO robot control cycle [ms] (not considered ifsim:=true
)
DENSO ROS2 stack (simulation) |
---|
![]() |
2.2 Send Format Parameter
The send_format parameter can be used for write Hand I/O, Mini I/O or User I/O. Following table shows the details of the send_format parameter.
Value | I/O |
---|---|
0 | None |
32 | Hand I/O (Port 64 to 71) |
256 | Mini I/O (Port 16 to 31) |
288 | Hand I/O and Mini I/O |
512 | User I/O (Port 128 or after) |
544 | Hand I/O and User I/O |
2.3 Receive Format Parameter
The recv_format parameter can be used for write Hand I/O, Mini I/O or User I/O. Following table shows the details of the recv_format parameter.
Value | I/O |
---|---|
0 | None |
34 | Hand I/O (Port 48 to 55 and 64 to 71) |
258 | Mini I/O (Port 0 to 31) |
290 | Hand I/O and Mini I/O |
514 | User I/O (Port 128 or after) |
546 | Hand I/O and User I/O |
3. Read and Write I/O Lines (Optional)
When setting the send_format and recv_format parameters, proper subscribers and publishers are launched.
File truncated at 100 lines see the full file
Changelog for package denso_robot_control
1.2.0 (2024-03-18)
- Implemented support for ROS2 Humble
- Avoid Boost C++ Libaries
1.1.1 (2024-02-09)
- Remove "under construction" sections from README.md
1.1.0 (2023-03-24)
Initial release
Package Dependencies
System Dependencies
Dependant Packages
Name | Deps |
---|---|
denso_robot_bringup |