-
Notifications
You must be signed in to change notification settings - Fork 75
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
Controller Development #60
Comments
…nal-crashing to humble * commit '0c6f824ee6ce122056fcfed5e8040b1a2e76ec9e': fix: devcontainer terminal crashing
Hey Peter, |
This is super useful, thanks @BarisYazici. |
If you get something ready, we could make it available to public. So more developers can utilise it. |
Right now my code is more of a proof of concept that I use for occasional debug (found here). At the moment, I am more focused on writing and theory work but once I am back to software development work and I have the capacity to I'll clean up the code and post an example here. Also one of the MoveIt GSoC projects this year is working on a MuJoCo integration for ROS 2 control. I think it will be worth checking out when it is completed. |
Hi Franka Emika Development Team,
I am in the process of developing controllers based on the examples given in this repository. In order to test my controller software I planned to run the software against a MuJoCo simulation of my robot. I have the MuJoCo integration working and the example controllers from this repository running in MuJoCo however, I am facing issue in getting the example controllers stable in MuJoCo.
I had the following question resulting from this that I was hoping it might be possible to get advice on. I wished to ask when developing controllers for the FER and/or FR3, is there a recommended testing protocol to ensure the safety of the hardware when testing a given controller implementation (e.g. test in simulation, protocols for deploying on real hardware)? When it comes to tuning controller parameters on both platforms are there any guides/advice the development team would provide on this (should I assume standard manual tuning practices)?
The text was updated successfully, but these errors were encountered: