-
Notifications
You must be signed in to change notification settings - Fork 29
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
What's the situation here? #2
Comments
Hi @v4hn, Thanks for getting in touch. Background reading: Sixad abandoned by its author: ros/rosdistro#6435 (comment) Rationale for Clearpath to carry it forward: ros/rosdistro#9297 (comment) PR that pulls version 1.6.1 onto However, the further wrinkle is that the DualShock 3 is now EOL, and making sixad work with the DS4 was deemed too much of a pain when other projects have covered this ground. So sixad is effectively now abandoned by us (Clearpath) as well, and we use If you'd like to fix or change something, I think your best bet would be to fork the repo from me, tag a new release, push it up to Launchpad, and then make your own PR to FYI @tfoote, @tonybaltovski |
Thanks for the quick response! ✨
Ah, I wasn't aware of that. That changes the situation quite a bit.
As far as I can see, there is neither an official debian/ubuntu-, nor a ROS package for PS4 support available as a moment. Do you know of a ROS module that uses the ds4drv python package (I suppose you mean this one) and provides joy messages?
I'm not sure I have time to do this, especially when the respective hardware is EOL. |
I wouldn't mind helping maintain it. I was able to pair a DS4 controller with my fork but found ds4drv to be a quicker solution at the time. |
Hey @mikepurvis ,
what's the maintenance state of this package? Are you still the maintainer?
Did @RetroPie and or @gizmo98 take over the package in their forks?
OSRF provides a debian package of this module on packages.ros.org and it lists Mike as maintainer.
It also states that the package has version 1.6.1, which does not exist as far as I know...
It is used to teleoperate (among many other things, I'm sure) the PR2 robot.
I just found the (in my very very humble opinion) completely brain-damaged
chmod -x /usr/sbin/bluetoothd
in the sixad wrapper code, because this makes sixad fail to run correctly on the second machine on the PR2. The second machine mounts the first machines/usr
path readonly and thus only gets to see the non-executable read-only file.Now I would like to add a variable to
/etc/default/sixad
to skip this step and get the package pushed to packages.ros.org.Any chance this could happen? Where would I pull-request the patch?
The text was updated successfully, but these errors were encountered: