universal_robot | ROS-Industrial Universal Robots support ( https | Robotics library

by ros-industrial C++ Version: 1.3.1 License: No License

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | universal_robot Summary

universal_robot is a C++ library typically used in Automation, Robotics applications. universal_robot has no bugs, it has no vulnerabilities and it has medium support. You can download it from GitHub.

ROS-Industrial Universal Robots support (

Support

Quality

Security

License

Reuse

Support

universal_robot has a medium active ecosystem.

It has 879 star(s) with 987 fork(s). There are 66 watchers for this library.

It had no major release in the last 6 months.

There are 37 open issues and 293 have been closed. On average issues are closed in 382 days. There are 20 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of universal_robot is 1.3.1

Quality

universal_robot has 0 bugs and 0 code smells.

Security

universal_robot has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

universal_robot code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

universal_robot does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

universal_robot releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

It has 2646 lines of code, 102 functions and 87 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed universal_robot and discovered the below as its top functions. This is intended to give you an instant insight into universal_robot implemented functionality, and help decide if they suit your requirements.

Called when a goal is received
Reorder joint_names
Returns True if trajectory has limited velocities
Check if trajectory has all velocities
Sends the current trajectory to the target
Send a message
Sends a servoj
Check if a_vec is within tolerance
Handle a single request
Wait for more data
Set the connected robot
Unpack a RobotState packet
Return an AdditionalInfo instance from buffer
Read AdditionalInfo from buffer
Parse an AdditionalInfo object from buffer
Cancel the current trajectory
Load calibration offsets for given joint names
Handle a SETIO request
Return a connected robot
Set flag
Parse the buffer of RobotStateRT
Connect to robot
Connect to the robot
Set payload
Get a connected robot
Send the program
Get my ip

Get all kandi verified functions for this library.

universal_robot Key Features

No Key Features are available at this moment for universal_robot.

universal_robot Examples and Code Snippets

No Code Snippets are available at this moment for universal_robot.

Community Discussions

Trending Discussions on universal_robot

Difference between the ROS UniversalRobots/Universal_Robots_ROS_Driver and the ros-industrial/universal_robot driver

QUESTION

Difference between the ROS UniversalRobots/Universal_Robots_ROS_Driver and the ros-industrial/universal_robot driver

Asked 2021-Jul-07 at 13:50

I've tried to understand the difference between the two ROS Universal Robot drivers and decide which one to use. So far, I'm mainly confused. As I am new to ROS and robot control I'd appreciate any explanation and hints where to start looking for more details.

From what I've seen, there are two Universal Robot ROS drivers available

(1) https://github.com/ros-industrial/universal_robot

(2) https://github.com/UniversalRobots/Universal_Robots_ROS_Driver

with (1) being "supplemented" by (3) https://github.com/fmauch/universal_robot/tree/calibration_devel.

(1) wasn't updated in while whereas (2) seems to get regular updates. Yet (3) seems to suggest that (1) is still being worked on (see https://github.com/ros-industrial/universal_robot/issues/573 as well). Which one is the "active" one? Which one should be used for which use case?

It also seems to me that I can't use (2) with gazebo. However, as I said, I'm new to ROS and might be misunderstanding something entirely. What I'd like to be able to do is simulate an UR10e to develop my application within gazebo and then swap to the real robot as transparently as possible.

Thanks to all the maintainers of the UR ROS drivers (from both/all repos :))!

...

ANSWER

Answered 2021-Jul-07 at 13:50

The ROS-Industrial set of drivers was the original community driven drivers, started back in 2012. While sparsely updated compared to back then, since it has the force & name of ROS Industrial, the community is still actively submitting issues, PR, and they are (slowly) getting merged in, as needed.

The Universal Robotics drivers were started back in 2016, as the company's official ROS support, with support from ROS Industrial for the "modernization" of the drivers. It's seeing a ton of active development & upkeep, as there are dedicated people to maintaining just this repo & drivers.

They are both active, and functionally, they likely both work for what you're trying to do (since what you want seems simple or solved). Once the driver is written, if the device doesn't change, the driver doesn't need to. For example, the older ROS Industrial has a bunch of documentation (possibly old but still good) on using the drivers with Gazebo, and drivers for UR 10e (a very common device), so that would be sufficient for your needs. If you get done what you need to get done, that's fine.

As for the UR official drivers, they are (with ROS Industrial group's support) the "new" and "modern" drivers, to extend the functionality from the older drivers; I suppose I should be recommending you to use these, but they are still work-in-progress. If there are features/limitations in the old drivers that you need, they should be fixed in the modern drivers. To not date this reply too much, the exact coverage is constantly increasing, and the support should be quicker than the old drivers. Eventually, full functionality and more will be done through this "modern" branch; for example, ROS2 support will/should not be added to the older ROS Industrial drivers.

Source https://stackoverflow.com/questions/68258402

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install universal_robot

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: