| rqt-robot-monitor |
1.0.6-1 |
rqt_robot_monitor displays diagnostics_agg topics messages that are published by <a href="http://www.ros.org/wiki/diagnostic_aggregator">diagnostic_aggregator</a>. rqt_robot_monitor is a direct port to rqt of <a href="http://www.ros.org/wiki/robot_monitor">robot_monitor</a>. All diagnostics are fall into one of three tree panes depending on the status of diagnostics (normal, warning, error/stale). Status are shown in trees to represent their hierarchy. Worse status dominates the higher level status.<br/> <ul> Ex. 'Computer' category has 3 sub devices. 2 are green but 1 is error. Then 'Computer' becomes error. </ul> You can look at the detail of each status by double-clicking the tree nodes.<br/> Currently re-usable API to other pkgs are not explicitly provided. |
meta-ros2-humble |
| rqt-robot-monitor |
1.0.6-1 |
rqt_robot_monitor displays diagnostics_agg topics messages that are published by <a href="http://www.ros.org/wiki/diagnostic_aggregator">diagnostic_aggregator</a>. rqt_robot_monitor is a direct port to rqt of <a href="http://www.ros.org/wiki/robot_monitor">robot_monitor</a>. All diagnostics are fall into one of three tree panes depending on the status of diagnostics (normal, warning, error/stale). Status are shown in trees to represent their hierarchy. Worse status dominates the higher level status.<br/> <ul> Ex. 'Computer' category has 3 sub devices. 2 are green but 1 is error. Then 'Computer' becomes error. </ul> You can look at the detail of each status by double-clicking the tree nodes.<br/> Currently re-usable API to other pkgs are not explicitly provided. |
meta-ros2-jazzy |
| rqt-robot-monitor |
1.0.6-2 |
rqt_robot_monitor displays diagnostics_agg topics messages that are published by <a href="http://www.ros.org/wiki/diagnostic_aggregator">diagnostic_aggregator</a>. rqt_robot_monitor is a direct port to rqt of <a href="http://www.ros.org/wiki/robot_monitor">robot_monitor</a>. All diagnostics are fall into one of three tree panes depending on the status of diagnostics (normal, warning, error/stale). Status are shown in trees to represent their hierarchy. Worse status dominates the higher level status.<br/> <ul> Ex. 'Computer' category has 3 sub devices. 2 are green but 1 is error. Then 'Computer' becomes error. </ul> You can look at the detail of each status by double-clicking the tree nodes.<br/> Currently re-usable API to other pkgs are not explicitly provided. |
meta-ros2-kilted |
| rr-openrover-driver |
1.1.1-1 |
Provides an interface between ros and Rover Robotics rover hardware. Inputs to rr_openrover_driver include emergency stop and velocity commands. It outputs diagnostic data such as encoder readings and battery charge. |
meta-ros1-melodic |
| rubygems-public-suffix |
7.0.5 |
RubyGem: public_suffix |
meta-rubygems |
| ruli |
0.36 |
RULI stands for Resolver User Layer Interface It's a library built on top of an asynchronous DNS stub resolver |
meta-networking |
| schunk-simulated-tactile-sensors |
0.6.14-1 |
This package provides simulated tactile sensors for the Schunk Dextrous Hand (SDH) which is mounted on the Care-O-bot arm. The node subscribes to the Gazebo bumper topics of the SDH. It transforms the Gazebo feedback to the "tactile_data" topic to provide the same tactile sensor interface as the schunk_sdh package. The following parameters can be set: * cells_x: The number of patches on the tactile sensor in the direction perpendicular to the finger. Defaults to 6. * cells_y: The number of patches on the tactile sensor along the direction of the finger. Defaults to 14. * output_range: The maximum output value of one patch. Defaults to 3500. * sensitivity: The change of output in one patch per Newton. Defaults to 350. The sensitivity can be approximated by the following formula: S = output_range / (measurement_range * cell_area) - The measurement range of the tactile pads is 250 kPa (from the data sheet). - The output range can be determined by experiment from the real SDH. It is about 3500. - The cell area is the size of one patch. Length and width of the area are determined by dividing the length/width of the collision surface by the number of cells in the respective direction. Important: In most cases this is NOT the cell area that is given in the data sheet! * filter_length: The length of the moving average filter which smoothes the values from simulation. Defaults to 10. The node subscribes to the following topics to receive data from the simulation: * thumb_2/state * thumb_3/state * finger_12/state * finger_13/state * finger_22/state * finger_23/state The node publishes the processed data on the following topic: * tactile_data The simulated bumper must obtain the collision data in the link that the sensor is attached to. This is achieved by setting the "frameName" property in the gazebo_ros_bumper controller. |
meta-ros1-melodic |
| schunk-simulated-tactile-sensors |
0.6.14-1 |
This package provides simulated tactile sensors for the Schunk Dextrous Hand (SDH) which is mounted on the Care-O-bot arm. The node subscribes to the Gazebo bumper topics of the SDH. It transforms the Gazebo feedback to the "tactile_data" topic to provide the same tactile sensor interface as the schunk_sdh package. The following parameters can be set: * cells_x: The number of patches on the tactile sensor in the direction perpendicular to the finger. Defaults to 6. * cells_y: The number of patches on the tactile sensor along the direction of the finger. Defaults to 14. * output_range: The maximum output value of one patch. Defaults to 3500. * sensitivity: The change of output in one patch per Newton. Defaults to 350. The sensitivity can be approximated by the following formula: S = output_range / (measurement_range * cell_area) - The measurement range of the tactile pads is 250 kPa (from the data sheet). - The output range can be determined by experiment from the real SDH. It is about 3500. - The cell area is the size of one patch. Length and width of the area are determined by dividing the length/width of the collision surface by the number of cells in the respective direction. Important: In most cases this is NOT the cell area that is given in the data sheet! * filter_length: The length of the moving average filter which smoothes the values from simulation. Defaults to 10. The node subscribes to the following topics to receive data from the simulation: * thumb_2/state * thumb_3/state * finger_12/state * finger_13/state * finger_22/state * finger_23/state The node publishes the processed data on the following topic: * tactile_data The simulated bumper must obtain the collision data in the link that the sensor is attached to. This is achieved by setting the "frameName" property in the gazebo_ros_bumper controller. |
meta-ros1-noetic |
| scummvm |
0.6.0 |
Virtual Machine for LucasArts Adventures for Qt/Embedded based palmtop environments w/ SDL. |
meta-opie |
| sidplayer |
1.5.0 |
A SID Player for the Qt/Embedded based Palmtop Environments |
meta-opie |
| slint-cpp |
git-X |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.3.0 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.3.1 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.3.2 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.4.0 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.4.1 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.5.0 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.5.1 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.6.0 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.7.0 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.7.1 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.7.2 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.8.0 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.9.0 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.9.2 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.10.0 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.11.0 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.12.0 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.12.1 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.13.0 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.13.1 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.14.0 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.14.1 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.15.0 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.16.0 |
Slint C++ UI Toolkit |
meta-slint |
| slint-cpp |
1.16.1 |
Slint C++ UI Toolkit |
meta-slint |
| smacc |
1.4.6-1 |
SMACC is a ROS/C++ library to implement in easy and systematic way UML StateCharts (AKA state machines). SMACC is inspired by the SMACH ROS package and it is built on top of Boost StateChart library. Developed by Reel Robotics. |
meta-ros1-noetic |
| smach-ros |
2.0.1 |
The smach_ros package contains extensions for the SMACH library to integrate it tightly with ROS. For example, SMACH-ROS can call ROS services, listen to ROS topics, and integrate with <a href="http://www.ros.org/wiki/actionlib">actionlib</a> both as a client, and a provider of action servers. SMACH is a new library that takes advantage of very old concepts in order to quickly create robust robot behavior with maintainable and modular code. |
meta-ros1-melodic |
| smach-ros |
3.0.3-2 |
The smach_ros package contains extensions for the SMACH library to integrate it tightly with ROS. For example, SMACH-ROS can call ROS services, listen to ROS topics, and integrate with <a href="http://www.ros.org/wiki/actionlib">actionlib</a> both as a client, and a provider of action servers. SMACH is a new library that takes advantage of very old concepts in order to quickly create robust robot behavior with maintainable and modular code. |
meta-ros2-rolling |
| smach-ros |
2.5.3-1 |
The smach_ros package contains extensions for the SMACH library to integrate it tightly with ROS. For example, SMACH-ROS can call ROS services, listen to ROS topics, and integrate with <a href="http://www.ros.org/wiki/actionlib">actionlib</a> both as a client, and a provider of action servers. SMACH is a new library that takes advantage of very old concepts in order to quickly create robust robot behavior with maintainable and modular code. |
meta-ros1-noetic |
| smach-ros |
3.0.3-1 |
The smach_ros package contains extensions for the SMACH library to integrate it tightly with ROS. For example, SMACH-ROS can call ROS services, listen to ROS topics, and integrate with <a href="http://www.ros.org/wiki/actionlib">actionlib</a> both as a client, and a provider of action servers. SMACH is a new library that takes advantage of very old concepts in order to quickly create robust robot behavior with maintainable and modular code. |
meta-ros2-humble |
| smach-ros |
3.0.3-3 |
The smach_ros package contains extensions for the SMACH library to integrate it tightly with ROS. For example, SMACH-ROS can call ROS services, listen to ROS topics, and integrate with <a href="http://www.ros.org/wiki/actionlib">actionlib</a> both as a client, and a provider of action servers. SMACH is a new library that takes advantage of very old concepts in order to quickly create robust robot behavior with maintainable and modular code. |
meta-ros2-jazzy |
| smach-ros |
3.0.3-3 |
The smach_ros package contains extensions for the SMACH library to integrate it tightly with ROS. For example, SMACH-ROS can call ROS services, listen to ROS topics, and integrate with <a href="http://www.ros.org/wiki/actionlib">actionlib</a> both as a client, and a provider of action servers. SMACH is a new library that takes advantage of very old concepts in order to quickly create robust robot behavior with maintainable and modular code. |
meta-ros2-kilted |
| snes9x-sdl-qpe |
1.39 |
Super Nintendo Emulator based on SDL, QtE Palmtop Environments Edition |
meta-opie |
| socketcan-bridge |
0.8.5-1 |
Conversion nodes for messages from SocketCAN to a ROS Topic and vice versa. |
meta-ros1-melodic |
| socketcan-bridge |
0.8.5-1 |
Conversion nodes for messages from SocketCAN to a ROS Topic and vice versa. |
meta-ros1-noetic |
| solid |
6.22.0 |
Desktop hardware abstraction |
meta-wayland |
| solid |
6.25.0 |
Solid |
meta-kf6 |
| sound-play |
0.3.12-1 |
sound_play provides a ROS node that translates commands on a ROS topic (<tt>robotsound</tt>) into sounds. The node supports built-in sounds, playing OGG/WAV files, and doing speech synthesis via festival. C++ and Python bindings allow this node to be used without understanding the details of the message format, allowing faster development and resilience to message format changes. |
meta-ros1-melodic |
| sound-play |
0.3.18-1 |
sound_play provides a ROS node that translates commands on a ROS topic (<tt>robotsound</tt>) into sounds. The node supports built-in sounds, playing OGG/WAV files, and doing speech synthesis via festival. C++ and Python bindings allow this node to be used without understanding the details of the message format, allowing faster development and resilience to message format changes. |
meta-ros1-noetic |