Skip to content

description dev #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 104 commits into from
Nov 24, 2020
Merged

description dev #1

merged 104 commits into from
Nov 24, 2020

Conversation

fmessmer
Copy link

ref: UniversalRobots#97
update mojin-devel branch to support e-series

axelschroth and others added 30 commits March 20, 2020 12:47
fixes problem that no messages are published if robot program is not running
Co-Authored-By: Felix Exner <felix_mauch@web.de>
This launchfile was created for local testing in the past and slipped through.
Use github actions for CI instead of Travis
…iversalRobots#115)

* Improve the quick start guide to make the start order more clear.

* Added a couple of suggested improvements

Thanks @gavanderhoorn

* Made clear that we are extracting calibration, not calibrating the robot.
Before, the main badge could get to failure when there was a PR coming in that failed.
…entation

Use section commands for each individual topic/service/parameter url
set motion_possible to true only of robot can be actually moved
fmauch and others added 29 commits July 10, 2020 14:02
Add integration tests for automated testing
Use a parameter to set the wrench name

This name will be picked up by the `force_torque_sensor_controller` in order to name the respective topic.

Co-authored-by: carebare47 <tom@shadowrobot.com>
* Added a service to setup the active payload
Before, the default Docker network in the range 172.17.0.0/16 was used. Since a specific IP cannot be chosen/guaranteed within this range, a network is now created with range 192.168.0.0/16, which allows for assigning specific IPs to the containers.

Co-authored-by: Emil Vincent Ancker <emva@universal-robots.com>
modified hardware interface to look for joints parameter under the robot_hw node handle
The trajectory test seems to not work anymore since a
couple of weeks. Running those locally (also with a
ursim running inside a docker container) works perfectly
fine, but running it inside the github action not.

As this is blocking many merges currently, I suggest
to disable this temporarily while opening an issue to fix it.
* Added explanation of scaled trajectory controller

* Apply suggestions from code review

Thanks @gavanderhoorn for this in-depth review!

Co-authored-by: G.A. vd. Hoorn <g.a.vanderhoorn@tudelft.nl>

* Added another suggestion I missed

Co-authored-by: G.A. vd. Hoorn <g.a.vanderhoorn@tudelft.nl>

* Clarified where the speed_scaling value comes from.

* Format ros_control correctly

* Rewrote bullet point about non-moving robot

* Replace time frame with control cycle

Co-authored-by: G.A. vd. Hoorn <g.a.vanderhoorn@tudelft.nl>
* Updated externalcontrol to v1.0.3

* Updated externalcontrol to v1.0.4
@fmessmer fmessmer merged commit e69b612 into mojin-devel Nov 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.