Comments (10)
That seems to work. My code is here rivelinrobotics@d34b4ad if anyone is interested in cherry-picking it into a PR.
from motoman.
Looks like MotomanJointTrajectoryStreamer::create_message
uses a setRobotID
method, which is presumably getting the wrong id from somewhere. I'll see if I can find out where and how to fix it.
from motoman.
Okay, I think I understand what's happening. JointTrajectoryStreamer::jointCommandCB
calls MotomanJointTrajectoryStreamer::create_message(..., JointTrajectoryPoint, ...)
, which uses setRobotId(robot_id_)
.
What I think I need is MotomanJointTrajectoryStreamer::create_message(..., DynamicJointsGroup, ...)
, which uses setRobotId(pt.group_number)
.
So I guess I need to write a JointTrajectoryStreamer::jointCommandCB(DynamicJointTrajectoryConstPtr)
.
from motoman.
Thanks for reporting on your progress + solution.
I noticed rivelinrobotics#1 was closed, not merged.
Did you discover something that was not correct in the end, or was the PR just for running CI?
from motoman.
I have fixed the various MoveIt connections which were causing most of the issues in #585, such that we don't need #259 or #488.
late perhaps, but I would really recommend you do in fact incorporate the changes from #488.
The multi-group implementation in HEAD
is incomplete, and #488 does fix some of those issues.
from motoman.
Thanks for reporting on your progress + solution.
👍
I noticed rivelinrobotics#1 was closed, not merged.
Did you discover something that was not correct in the end, or was the PR just for running CI?
This was just because the branching in our fork is a mess. We decided to make a new master
branch, rather than updating our kinetic-devel
branch. We are now using the contents of that PR.
If we need to keep using motoman1 for much longer we will need to tidy up our fork, but we're hoping to migrate to motoros2 before that is necessary.
from motoman.
we're hoping to migrate to motoros2 before that is necessary.
in this context feedback/input on Yaskawa-Global/motoros2#186 would be highly welcome.
from motoman.
I have fixed the various MoveIt connections which were causing most of the issues in #585, such that we don't need #259 or #488.
late perhaps, but I would really recommend you do in fact incorporate the changes from #488.
The multi-group implementation in
HEAD
is incomplete, and #488 does fix some of those issues.
Our current solution appears to be working, so we're reluctant to make more changes unless something stops working. If we end up sticking with motoros1 for much longer and come across any problems we will look at #488 again.
from motoman.
we're hoping to migrate to motoros2 before that is necessary.
in this context feedback/input on Yaskawa-Global/motoros2#186 would be highly welcome.
Sure thing. We are about half way through our migration to ROS2, and we haven't got to the motoman migration yet. No doubt we will have lots of feedback/input when we get to that stage.
from motoman.
Actually, you're right, that discussion does look relevant to us at this stage. I'll discuss with the team, and hopefully someone will contribute soon.
from motoman.
Related Issues (20)
- Floating precision with Param Extraction Library
- control motoman gp7 with 3 external axis HOT 2
- HC-10DTP Support Files HOT 3
- robot_enable service fails on YRC1000
- Can't start driver correctly on Yaskawa HC10DTP
- HC10DTP not working with MoveIt HOT 1
- GP20 Support files
- Control HC10DTP using an Xbox 360 joystick in real-time
- HC10DTP + MoveIt - Running into singularities
- motoman_driver - simple_message not available
- Update installation procedure and troubleshooting HOT 1
- ERROR :MESSAGE CALLBACK FOR MESSAGE type :2017 , not executed
- Unwanted motion when switching pendant mode HOT 2
- Motoman Ros I/O read/write error HOT 1
- Log Space: missing
- Failed to connect to server, rc: -1. Error: 'Connection refused' (errno: 111): MOTOMAN Driver HOT 1
- Error handling of action server (joint_trajectory_action) HOT 1
- Trajectory start position doesn't match current robot position (3011) when using multiple groups HOT 16
- DX100 / SIA50D stops moving after several trajectories (no error / alarm)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from motoman.