![]() |
manymove_signals package from manymove repomanymove_bringup manymove_cpp_trees manymove_hmi manymove_msgs manymove_object_manager manymove_planner manymove_py_trees manymove_signals |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | BSD-3-Clause |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | To plan and execute moves with manipulators in ROS2 |
Checkout URI | https://github.com/pastoriomarco/manymove.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-07-29 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Marco Pastorio
Authors
- Marco Pastorio
ManyMove Signals
This manymove_signals
package is part of the manymove
project for ROS 2 Humble. It provides a unified signals interface (digital I/O, robot state checks, and robot reset logic) for various robot models, using xArm or UFactory-like services and topics.
Use at your own risk; this repository is experimental and does not provide safety features.
Overview
Key Functionalities
-
Digital I/O
Action servers to set or get I/O pins (SetOutput
,GetInput
) for both tool and controller IO types. -
Robot State Check & Reset
Action servers to check if the robot is ready (CheckRobotState
) and to reset it if needed (ResetRobotState
), wrapping lower-level services (clean_error
,motion_enable
,set_mode
, etc.). -
Multi-Model Support
Adjusts namespace and service calls depending on therobot_model
parameter (lite6
,uf850
, orxarm
).
Architecture
-
signals_node.cpp
- The main node (
manymove_signals_node
) sets up:-
Service Clients:
set_tgpio_digital
,get_tgpio_digital
,set_cgpio_digital
,get_cgpio_digital
, plus xArm’sset_mode
,set_state
,clean_error
,motion_enable
. -
Action Servers:
set_output
,get_input
,reset_robot_state
,check_robot_state
. -
Subscription: E.g.,
<robot_prefix>ufactory/robot_states
or<robot_prefix>xarm/robot_states
for continuous monitoring.
-
Service Clients:
- Each action server delegates to the relevant service calls to handle the requested logic.
- The main node (
-
Reset Robot Flow
- Cleans errors, re-enables motion, sets mode/state, and verifies the result by checking the subscription to
robot_states
.
- Cleans errors, re-enables motion, sets mode/state, and verifies the result by checking the subscription to
-
Check Robot State
- Reads the last known
robot_states
message, checking forerr == 0
,mode == 1
, etc.
- Reads the last known
Installation & Dependencies
Follow the main ManyMove README.
Usage
Run the Signals Node
ros2 run manymove_signals manymove_signals_node
Parameters:
-
robot_model
: e.g., lite6, uf850, or xarm -
robot_prefix
: optional namespace prefix (e.g., R_)
Action Servers
-
<robot_prefix>set_output
: Takes an io_type (tool or controller), ionum, and value (0/1). -
<robot_prefix>get_input
: Returns the digital input for a given pin. -
<robot_prefix>reset_robot_state
: Cleans error, re-enables motion, sets mode/state, and checks the robot’s readiness. -
<robot_prefix>check_robot_state
: Returns current error, mode, and state, plus a boolean for “ready.”
Compatibility
Typically used by manymove_planner
or manymove_cpp_trees
for logic that requires direct I/O or resetting the robot at runtime.
Notes & Disclaimer
- Experimental: This package is under active development.
- No Safety Features: Always configure your hardware’s safety mechanisms separately.
- Check Main README for disclaimers, licensing, and additional info.
Package Dependencies
System Dependencies
Dependant Packages
Name | Deps |
---|---|
manymove_cpp_trees |
Launch files
Messages
Services
Plugins
Recent questions tagged manymove_signals at Robotics Stack Exchange
![]() |
manymove_signals package from manymove repomanymove_bringup manymove_cpp_trees manymove_hmi manymove_msgs manymove_object_manager manymove_planner manymove_py_trees manymove_signals |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | BSD-3-Clause |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | To plan and execute moves with manipulators in ROS2 |
Checkout URI | https://github.com/pastoriomarco/manymove.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-07-29 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Marco Pastorio
Authors
- Marco Pastorio
ManyMove Signals
This manymove_signals
package is part of the manymove
project for ROS 2 Humble. It provides a unified signals interface (digital I/O, robot state checks, and robot reset logic) for various robot models, using xArm or UFactory-like services and topics.
Use at your own risk; this repository is experimental and does not provide safety features.
Overview
Key Functionalities
-
Digital I/O
Action servers to set or get I/O pins (SetOutput
,GetInput
) for both tool and controller IO types. -
Robot State Check & Reset
Action servers to check if the robot is ready (CheckRobotState
) and to reset it if needed (ResetRobotState
), wrapping lower-level services (clean_error
,motion_enable
,set_mode
, etc.). -
Multi-Model Support
Adjusts namespace and service calls depending on therobot_model
parameter (lite6
,uf850
, orxarm
).
Architecture
-
signals_node.cpp
- The main node (
manymove_signals_node
) sets up:-
Service Clients:
set_tgpio_digital
,get_tgpio_digital
,set_cgpio_digital
,get_cgpio_digital
, plus xArm’sset_mode
,set_state
,clean_error
,motion_enable
. -
Action Servers:
set_output
,get_input
,reset_robot_state
,check_robot_state
. -
Subscription: E.g.,
<robot_prefix>ufactory/robot_states
or<robot_prefix>xarm/robot_states
for continuous monitoring.
-
Service Clients:
- Each action server delegates to the relevant service calls to handle the requested logic.
- The main node (
-
Reset Robot Flow
- Cleans errors, re-enables motion, sets mode/state, and verifies the result by checking the subscription to
robot_states
.
- Cleans errors, re-enables motion, sets mode/state, and verifies the result by checking the subscription to
-
Check Robot State
- Reads the last known
robot_states
message, checking forerr == 0
,mode == 1
, etc.
- Reads the last known
Installation & Dependencies
Follow the main ManyMove README.
Usage
Run the Signals Node
ros2 run manymove_signals manymove_signals_node
Parameters:
-
robot_model
: e.g., lite6, uf850, or xarm -
robot_prefix
: optional namespace prefix (e.g., R_)
Action Servers
-
<robot_prefix>set_output
: Takes an io_type (tool or controller), ionum, and value (0/1). -
<robot_prefix>get_input
: Returns the digital input for a given pin. -
<robot_prefix>reset_robot_state
: Cleans error, re-enables motion, sets mode/state, and checks the robot’s readiness. -
<robot_prefix>check_robot_state
: Returns current error, mode, and state, plus a boolean for “ready.”
Compatibility
Typically used by manymove_planner
or manymove_cpp_trees
for logic that requires direct I/O or resetting the robot at runtime.
Notes & Disclaimer
- Experimental: This package is under active development.
- No Safety Features: Always configure your hardware’s safety mechanisms separately.
- Check Main README for disclaimers, licensing, and additional info.
Package Dependencies
System Dependencies
Dependant Packages
Name | Deps |
---|---|
manymove_cpp_trees |
Launch files
Messages
Services
Plugins
Recent questions tagged manymove_signals at Robotics Stack Exchange
![]() |
manymove_signals package from manymove repomanymove_bringup manymove_cpp_trees manymove_hmi manymove_msgs manymove_object_manager manymove_planner manymove_py_trees manymove_signals |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | BSD-3-Clause |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | To plan and execute moves with manipulators in ROS2 |
Checkout URI | https://github.com/pastoriomarco/manymove.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-07-29 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Marco Pastorio
Authors
- Marco Pastorio
ManyMove Signals
This manymove_signals
package is part of the manymove
project for ROS 2 Humble. It provides a unified signals interface (digital I/O, robot state checks, and robot reset logic) for various robot models, using xArm or UFactory-like services and topics.
Use at your own risk; this repository is experimental and does not provide safety features.
Overview
Key Functionalities
-
Digital I/O
Action servers to set or get I/O pins (SetOutput
,GetInput
) for both tool and controller IO types. -
Robot State Check & Reset
Action servers to check if the robot is ready (CheckRobotState
) and to reset it if needed (ResetRobotState
), wrapping lower-level services (clean_error
,motion_enable
,set_mode
, etc.). -
Multi-Model Support
Adjusts namespace and service calls depending on therobot_model
parameter (lite6
,uf850
, orxarm
).
Architecture
-
signals_node.cpp
- The main node (
manymove_signals_node
) sets up:-
Service Clients:
set_tgpio_digital
,get_tgpio_digital
,set_cgpio_digital
,get_cgpio_digital
, plus xArm’sset_mode
,set_state
,clean_error
,motion_enable
. -
Action Servers:
set_output
,get_input
,reset_robot_state
,check_robot_state
. -
Subscription: E.g.,
<robot_prefix>ufactory/robot_states
or<robot_prefix>xarm/robot_states
for continuous monitoring.
-
Service Clients:
- Each action server delegates to the relevant service calls to handle the requested logic.
- The main node (
-
Reset Robot Flow
- Cleans errors, re-enables motion, sets mode/state, and verifies the result by checking the subscription to
robot_states
.
- Cleans errors, re-enables motion, sets mode/state, and verifies the result by checking the subscription to
-
Check Robot State
- Reads the last known
robot_states
message, checking forerr == 0
,mode == 1
, etc.
- Reads the last known
Installation & Dependencies
Follow the main ManyMove README.
Usage
Run the Signals Node
ros2 run manymove_signals manymove_signals_node
Parameters:
-
robot_model
: e.g., lite6, uf850, or xarm -
robot_prefix
: optional namespace prefix (e.g., R_)
Action Servers
-
<robot_prefix>set_output
: Takes an io_type (tool or controller), ionum, and value (0/1). -
<robot_prefix>get_input
: Returns the digital input for a given pin. -
<robot_prefix>reset_robot_state
: Cleans error, re-enables motion, sets mode/state, and checks the robot’s readiness. -
<robot_prefix>check_robot_state
: Returns current error, mode, and state, plus a boolean for “ready.”
Compatibility
Typically used by manymove_planner
or manymove_cpp_trees
for logic that requires direct I/O or resetting the robot at runtime.
Notes & Disclaimer
- Experimental: This package is under active development.
- No Safety Features: Always configure your hardware’s safety mechanisms separately.
- Check Main README for disclaimers, licensing, and additional info.
Package Dependencies
System Dependencies
Dependant Packages
Name | Deps |
---|---|
manymove_cpp_trees |
Launch files
Messages
Services
Plugins
Recent questions tagged manymove_signals at Robotics Stack Exchange
![]() |
manymove_signals package from manymove repomanymove_bringup manymove_cpp_trees manymove_hmi manymove_msgs manymove_object_manager manymove_planner manymove_py_trees manymove_signals |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | BSD-3-Clause |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | To plan and execute moves with manipulators in ROS2 |
Checkout URI | https://github.com/pastoriomarco/manymove.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-07-29 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Marco Pastorio
Authors
- Marco Pastorio
ManyMove Signals
This manymove_signals
package is part of the manymove
project for ROS 2 Humble. It provides a unified signals interface (digital I/O, robot state checks, and robot reset logic) for various robot models, using xArm or UFactory-like services and topics.
Use at your own risk; this repository is experimental and does not provide safety features.
Overview
Key Functionalities
-
Digital I/O
Action servers to set or get I/O pins (SetOutput
,GetInput
) for both tool and controller IO types. -
Robot State Check & Reset
Action servers to check if the robot is ready (CheckRobotState
) and to reset it if needed (ResetRobotState
), wrapping lower-level services (clean_error
,motion_enable
,set_mode
, etc.). -
Multi-Model Support
Adjusts namespace and service calls depending on therobot_model
parameter (lite6
,uf850
, orxarm
).
Architecture
-
signals_node.cpp
- The main node (
manymove_signals_node
) sets up:-
Service Clients:
set_tgpio_digital
,get_tgpio_digital
,set_cgpio_digital
,get_cgpio_digital
, plus xArm’sset_mode
,set_state
,clean_error
,motion_enable
. -
Action Servers:
set_output
,get_input
,reset_robot_state
,check_robot_state
. -
Subscription: E.g.,
<robot_prefix>ufactory/robot_states
or<robot_prefix>xarm/robot_states
for continuous monitoring.
-
Service Clients:
- Each action server delegates to the relevant service calls to handle the requested logic.
- The main node (
-
Reset Robot Flow
- Cleans errors, re-enables motion, sets mode/state, and verifies the result by checking the subscription to
robot_states
.
- Cleans errors, re-enables motion, sets mode/state, and verifies the result by checking the subscription to
-
Check Robot State
- Reads the last known
robot_states
message, checking forerr == 0
,mode == 1
, etc.
- Reads the last known
Installation & Dependencies
Follow the main ManyMove README.
Usage
Run the Signals Node
ros2 run manymove_signals manymove_signals_node
Parameters:
-
robot_model
: e.g., lite6, uf850, or xarm -
robot_prefix
: optional namespace prefix (e.g., R_)
Action Servers
-
<robot_prefix>set_output
: Takes an io_type (tool or controller), ionum, and value (0/1). -
<robot_prefix>get_input
: Returns the digital input for a given pin. -
<robot_prefix>reset_robot_state
: Cleans error, re-enables motion, sets mode/state, and checks the robot’s readiness. -
<robot_prefix>check_robot_state
: Returns current error, mode, and state, plus a boolean for “ready.”
Compatibility
Typically used by manymove_planner
or manymove_cpp_trees
for logic that requires direct I/O or resetting the robot at runtime.
Notes & Disclaimer
- Experimental: This package is under active development.
- No Safety Features: Always configure your hardware’s safety mechanisms separately.
- Check Main README for disclaimers, licensing, and additional info.
Package Dependencies
System Dependencies
Dependant Packages
Name | Deps |
---|---|
manymove_cpp_trees |
Launch files
Messages
Services
Plugins
Recent questions tagged manymove_signals at Robotics Stack Exchange
![]() |
manymove_signals package from manymove repomanymove_bringup manymove_cpp_trees manymove_hmi manymove_msgs manymove_object_manager manymove_planner manymove_py_trees manymove_signals |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | BSD-3-Clause |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | To plan and execute moves with manipulators in ROS2 |
Checkout URI | https://github.com/pastoriomarco/manymove.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-07-29 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Marco Pastorio
Authors
- Marco Pastorio
ManyMove Signals
This manymove_signals
package is part of the manymove
project for ROS 2 Humble. It provides a unified signals interface (digital I/O, robot state checks, and robot reset logic) for various robot models, using xArm or UFactory-like services and topics.
Use at your own risk; this repository is experimental and does not provide safety features.
Overview
Key Functionalities
-
Digital I/O
Action servers to set or get I/O pins (SetOutput
,GetInput
) for both tool and controller IO types. -
Robot State Check & Reset
Action servers to check if the robot is ready (CheckRobotState
) and to reset it if needed (ResetRobotState
), wrapping lower-level services (clean_error
,motion_enable
,set_mode
, etc.). -
Multi-Model Support
Adjusts namespace and service calls depending on therobot_model
parameter (lite6
,uf850
, orxarm
).
Architecture
-
signals_node.cpp
- The main node (
manymove_signals_node
) sets up:-
Service Clients:
set_tgpio_digital
,get_tgpio_digital
,set_cgpio_digital
,get_cgpio_digital
, plus xArm’sset_mode
,set_state
,clean_error
,motion_enable
. -
Action Servers:
set_output
,get_input
,reset_robot_state
,check_robot_state
. -
Subscription: E.g.,
<robot_prefix>ufactory/robot_states
or<robot_prefix>xarm/robot_states
for continuous monitoring.
-
Service Clients:
- Each action server delegates to the relevant service calls to handle the requested logic.
- The main node (
-
Reset Robot Flow
- Cleans errors, re-enables motion, sets mode/state, and verifies the result by checking the subscription to
robot_states
.
- Cleans errors, re-enables motion, sets mode/state, and verifies the result by checking the subscription to
-
Check Robot State
- Reads the last known
robot_states
message, checking forerr == 0
,mode == 1
, etc.
- Reads the last known
Installation & Dependencies
Follow the main ManyMove README.
Usage
Run the Signals Node
ros2 run manymove_signals manymove_signals_node
Parameters:
-
robot_model
: e.g., lite6, uf850, or xarm -
robot_prefix
: optional namespace prefix (e.g., R_)
Action Servers
-
<robot_prefix>set_output
: Takes an io_type (tool or controller), ionum, and value (0/1). -
<robot_prefix>get_input
: Returns the digital input for a given pin. -
<robot_prefix>reset_robot_state
: Cleans error, re-enables motion, sets mode/state, and checks the robot’s readiness. -
<robot_prefix>check_robot_state
: Returns current error, mode, and state, plus a boolean for “ready.”
Compatibility
Typically used by manymove_planner
or manymove_cpp_trees
for logic that requires direct I/O or resetting the robot at runtime.
Notes & Disclaimer
- Experimental: This package is under active development.
- No Safety Features: Always configure your hardware’s safety mechanisms separately.
- Check Main README for disclaimers, licensing, and additional info.
Package Dependencies
System Dependencies
Dependant Packages
Name | Deps |
---|---|
manymove_cpp_trees |
Launch files
Messages
Services
Plugins
Recent questions tagged manymove_signals at Robotics Stack Exchange
![]() |
manymove_signals package from manymove repomanymove_bringup manymove_cpp_trees manymove_hmi manymove_msgs manymove_object_manager manymove_planner manymove_py_trees manymove_signals |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | BSD-3-Clause |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | To plan and execute moves with manipulators in ROS2 |
Checkout URI | https://github.com/pastoriomarco/manymove.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-07-29 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Marco Pastorio
Authors
- Marco Pastorio
ManyMove Signals
This manymove_signals
package is part of the manymove
project for ROS 2 Humble. It provides a unified signals interface (digital I/O, robot state checks, and robot reset logic) for various robot models, using xArm or UFactory-like services and topics.
Use at your own risk; this repository is experimental and does not provide safety features.
Overview
Key Functionalities
-
Digital I/O
Action servers to set or get I/O pins (SetOutput
,GetInput
) for both tool and controller IO types. -
Robot State Check & Reset
Action servers to check if the robot is ready (CheckRobotState
) and to reset it if needed (ResetRobotState
), wrapping lower-level services (clean_error
,motion_enable
,set_mode
, etc.). -
Multi-Model Support
Adjusts namespace and service calls depending on therobot_model
parameter (lite6
,uf850
, orxarm
).
Architecture
-
signals_node.cpp
- The main node (
manymove_signals_node
) sets up:-
Service Clients:
set_tgpio_digital
,get_tgpio_digital
,set_cgpio_digital
,get_cgpio_digital
, plus xArm’sset_mode
,set_state
,clean_error
,motion_enable
. -
Action Servers:
set_output
,get_input
,reset_robot_state
,check_robot_state
. -
Subscription: E.g.,
<robot_prefix>ufactory/robot_states
or<robot_prefix>xarm/robot_states
for continuous monitoring.
-
Service Clients:
- Each action server delegates to the relevant service calls to handle the requested logic.
- The main node (
-
Reset Robot Flow
- Cleans errors, re-enables motion, sets mode/state, and verifies the result by checking the subscription to
robot_states
.
- Cleans errors, re-enables motion, sets mode/state, and verifies the result by checking the subscription to
-
Check Robot State
- Reads the last known
robot_states
message, checking forerr == 0
,mode == 1
, etc.
- Reads the last known
Installation & Dependencies
Follow the main ManyMove README.
Usage
Run the Signals Node
ros2 run manymove_signals manymove_signals_node
Parameters:
-
robot_model
: e.g., lite6, uf850, or xarm -
robot_prefix
: optional namespace prefix (e.g., R_)
Action Servers
-
<robot_prefix>set_output
: Takes an io_type (tool or controller), ionum, and value (0/1). -
<robot_prefix>get_input
: Returns the digital input for a given pin. -
<robot_prefix>reset_robot_state
: Cleans error, re-enables motion, sets mode/state, and checks the robot’s readiness. -
<robot_prefix>check_robot_state
: Returns current error, mode, and state, plus a boolean for “ready.”
Compatibility
Typically used by manymove_planner
or manymove_cpp_trees
for logic that requires direct I/O or resetting the robot at runtime.
Notes & Disclaimer
- Experimental: This package is under active development.
- No Safety Features: Always configure your hardware’s safety mechanisms separately.
- Check Main README for disclaimers, licensing, and additional info.
Package Dependencies
System Dependencies
Dependant Packages
Name | Deps |
---|---|
manymove_cpp_trees |
Launch files
Messages
Services
Plugins
Recent questions tagged manymove_signals at Robotics Stack Exchange
![]() |
manymove_signals package from manymove repomanymove_bringup manymove_cpp_trees manymove_hmi manymove_msgs manymove_object_manager manymove_planner manymove_py_trees manymove_signals |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | BSD-3-Clause |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | To plan and execute moves with manipulators in ROS2 |
Checkout URI | https://github.com/pastoriomarco/manymove.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-07-29 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Marco Pastorio
Authors
- Marco Pastorio
ManyMove Signals
This manymove_signals
package is part of the manymove
project for ROS 2 Humble. It provides a unified signals interface (digital I/O, robot state checks, and robot reset logic) for various robot models, using xArm or UFactory-like services and topics.
Use at your own risk; this repository is experimental and does not provide safety features.
Overview
Key Functionalities
-
Digital I/O
Action servers to set or get I/O pins (SetOutput
,GetInput
) for both tool and controller IO types. -
Robot State Check & Reset
Action servers to check if the robot is ready (CheckRobotState
) and to reset it if needed (ResetRobotState
), wrapping lower-level services (clean_error
,motion_enable
,set_mode
, etc.). -
Multi-Model Support
Adjusts namespace and service calls depending on therobot_model
parameter (lite6
,uf850
, orxarm
).
Architecture
-
signals_node.cpp
- The main node (
manymove_signals_node
) sets up:-
Service Clients:
set_tgpio_digital
,get_tgpio_digital
,set_cgpio_digital
,get_cgpio_digital
, plus xArm’sset_mode
,set_state
,clean_error
,motion_enable
. -
Action Servers:
set_output
,get_input
,reset_robot_state
,check_robot_state
. -
Subscription: E.g.,
<robot_prefix>ufactory/robot_states
or<robot_prefix>xarm/robot_states
for continuous monitoring.
-
Service Clients:
- Each action server delegates to the relevant service calls to handle the requested logic.
- The main node (
-
Reset Robot Flow
- Cleans errors, re-enables motion, sets mode/state, and verifies the result by checking the subscription to
robot_states
.
- Cleans errors, re-enables motion, sets mode/state, and verifies the result by checking the subscription to
-
Check Robot State
- Reads the last known
robot_states
message, checking forerr == 0
,mode == 1
, etc.
- Reads the last known
Installation & Dependencies
Follow the main ManyMove README.
Usage
Run the Signals Node
ros2 run manymove_signals manymove_signals_node
Parameters:
-
robot_model
: e.g., lite6, uf850, or xarm -
robot_prefix
: optional namespace prefix (e.g., R_)
Action Servers
-
<robot_prefix>set_output
: Takes an io_type (tool or controller), ionum, and value (0/1). -
<robot_prefix>get_input
: Returns the digital input for a given pin. -
<robot_prefix>reset_robot_state
: Cleans error, re-enables motion, sets mode/state, and checks the robot’s readiness. -
<robot_prefix>check_robot_state
: Returns current error, mode, and state, plus a boolean for “ready.”
Compatibility
Typically used by manymove_planner
or manymove_cpp_trees
for logic that requires direct I/O or resetting the robot at runtime.
Notes & Disclaimer
- Experimental: This package is under active development.
- No Safety Features: Always configure your hardware’s safety mechanisms separately.
- Check Main README for disclaimers, licensing, and additional info.
Package Dependencies
System Dependencies
Dependant Packages
Name | Deps |
---|---|
manymove_cpp_trees |
Launch files
Messages
Services
Plugins
Recent questions tagged manymove_signals at Robotics Stack Exchange
![]() |
manymove_signals package from manymove repomanymove_bringup manymove_cpp_trees manymove_hmi manymove_msgs manymove_object_manager manymove_planner manymove_py_trees manymove_signals |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | BSD-3-Clause |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | To plan and execute moves with manipulators in ROS2 |
Checkout URI | https://github.com/pastoriomarco/manymove.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-07-29 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Marco Pastorio
Authors
- Marco Pastorio
ManyMove Signals
This manymove_signals
package is part of the manymove
project for ROS 2 Humble. It provides a unified signals interface (digital I/O, robot state checks, and robot reset logic) for various robot models, using xArm or UFactory-like services and topics.
Use at your own risk; this repository is experimental and does not provide safety features.
Overview
Key Functionalities
-
Digital I/O
Action servers to set or get I/O pins (SetOutput
,GetInput
) for both tool and controller IO types. -
Robot State Check & Reset
Action servers to check if the robot is ready (CheckRobotState
) and to reset it if needed (ResetRobotState
), wrapping lower-level services (clean_error
,motion_enable
,set_mode
, etc.). -
Multi-Model Support
Adjusts namespace and service calls depending on therobot_model
parameter (lite6
,uf850
, orxarm
).
Architecture
-
signals_node.cpp
- The main node (
manymove_signals_node
) sets up:-
Service Clients:
set_tgpio_digital
,get_tgpio_digital
,set_cgpio_digital
,get_cgpio_digital
, plus xArm’sset_mode
,set_state
,clean_error
,motion_enable
. -
Action Servers:
set_output
,get_input
,reset_robot_state
,check_robot_state
. -
Subscription: E.g.,
<robot_prefix>ufactory/robot_states
or<robot_prefix>xarm/robot_states
for continuous monitoring.
-
Service Clients:
- Each action server delegates to the relevant service calls to handle the requested logic.
- The main node (
-
Reset Robot Flow
- Cleans errors, re-enables motion, sets mode/state, and verifies the result by checking the subscription to
robot_states
.
- Cleans errors, re-enables motion, sets mode/state, and verifies the result by checking the subscription to
-
Check Robot State
- Reads the last known
robot_states
message, checking forerr == 0
,mode == 1
, etc.
- Reads the last known
Installation & Dependencies
Follow the main ManyMove README.
Usage
Run the Signals Node
ros2 run manymove_signals manymove_signals_node
Parameters:
-
robot_model
: e.g., lite6, uf850, or xarm -
robot_prefix
: optional namespace prefix (e.g., R_)
Action Servers
-
<robot_prefix>set_output
: Takes an io_type (tool or controller), ionum, and value (0/1). -
<robot_prefix>get_input
: Returns the digital input for a given pin. -
<robot_prefix>reset_robot_state
: Cleans error, re-enables motion, sets mode/state, and checks the robot’s readiness. -
<robot_prefix>check_robot_state
: Returns current error, mode, and state, plus a boolean for “ready.”
Compatibility
Typically used by manymove_planner
or manymove_cpp_trees
for logic that requires direct I/O or resetting the robot at runtime.
Notes & Disclaimer
- Experimental: This package is under active development.
- No Safety Features: Always configure your hardware’s safety mechanisms separately.
- Check Main README for disclaimers, licensing, and additional info.
Package Dependencies
System Dependencies
Dependant Packages
Name | Deps |
---|---|
manymove_cpp_trees |
Launch files
Messages
Services
Plugins
Recent questions tagged manymove_signals at Robotics Stack Exchange
![]() |
manymove_signals package from manymove repomanymove_bringup manymove_cpp_trees manymove_hmi manymove_msgs manymove_object_manager manymove_planner manymove_py_trees manymove_signals |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | BSD-3-Clause |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | To plan and execute moves with manipulators in ROS2 |
Checkout URI | https://github.com/pastoriomarco/manymove.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2025-07-29 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Marco Pastorio
Authors
- Marco Pastorio
ManyMove Signals
This manymove_signals
package is part of the manymove
project for ROS 2 Humble. It provides a unified signals interface (digital I/O, robot state checks, and robot reset logic) for various robot models, using xArm or UFactory-like services and topics.
Use at your own risk; this repository is experimental and does not provide safety features.
Overview
Key Functionalities
-
Digital I/O
Action servers to set or get I/O pins (SetOutput
,GetInput
) for both tool and controller IO types. -
Robot State Check & Reset
Action servers to check if the robot is ready (CheckRobotState
) and to reset it if needed (ResetRobotState
), wrapping lower-level services (clean_error
,motion_enable
,set_mode
, etc.). -
Multi-Model Support
Adjusts namespace and service calls depending on therobot_model
parameter (lite6
,uf850
, orxarm
).
Architecture
-
signals_node.cpp
- The main node (
manymove_signals_node
) sets up:-
Service Clients:
set_tgpio_digital
,get_tgpio_digital
,set_cgpio_digital
,get_cgpio_digital
, plus xArm’sset_mode
,set_state
,clean_error
,motion_enable
. -
Action Servers:
set_output
,get_input
,reset_robot_state
,check_robot_state
. -
Subscription: E.g.,
<robot_prefix>ufactory/robot_states
or<robot_prefix>xarm/robot_states
for continuous monitoring.
-
Service Clients:
- Each action server delegates to the relevant service calls to handle the requested logic.
- The main node (
-
Reset Robot Flow
- Cleans errors, re-enables motion, sets mode/state, and verifies the result by checking the subscription to
robot_states
.
- Cleans errors, re-enables motion, sets mode/state, and verifies the result by checking the subscription to
-
Check Robot State
- Reads the last known
robot_states
message, checking forerr == 0
,mode == 1
, etc.
- Reads the last known
Installation & Dependencies
Follow the main ManyMove README.
Usage
Run the Signals Node
ros2 run manymove_signals manymove_signals_node
Parameters:
-
robot_model
: e.g., lite6, uf850, or xarm -
robot_prefix
: optional namespace prefix (e.g., R_)
Action Servers
-
<robot_prefix>set_output
: Takes an io_type (tool or controller), ionum, and value (0/1). -
<robot_prefix>get_input
: Returns the digital input for a given pin. -
<robot_prefix>reset_robot_state
: Cleans error, re-enables motion, sets mode/state, and checks the robot’s readiness. -
<robot_prefix>check_robot_state
: Returns current error, mode, and state, plus a boolean for “ready.”
Compatibility
Typically used by manymove_planner
or manymove_cpp_trees
for logic that requires direct I/O or resetting the robot at runtime.
Notes & Disclaimer
- Experimental: This package is under active development.
- No Safety Features: Always configure your hardware’s safety mechanisms separately.
- Check Main README for disclaimers, licensing, and additional info.
Package Dependencies
System Dependencies
Dependant Packages
Name | Deps |
---|---|
manymove_cpp_trees |