-
Notifications
You must be signed in to change notification settings - Fork 18
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
Update SN002 URDF to consider new battery pack #259
Comments
cc @valegagge |
Hi @S-Dafarra! There are two possible ways of doing it:
To understand, did the new battery pack increase the ergocub version to 1.3?
|
Probably yes; see: |
Probably a bit OT, but should we have a documentation page listing ergoCub versions as we have for iCub (see https://icub-tech-iit.github.io/documentation/icub_versions/)? |
It would start being quite helpful indeed. |
Considering that the plan for future robots would be to use this new battery pack (correct me if I am wrong @maggia80), I would suggest going for the long way |
Ok then! |
|
As we already discussing during summer, there are a few experiments new idea that AMI people worked on to improve the process. Not sure if any can be used in the short term for this, but you may anyhow have a quick alignment coffee once you identified the mechanical engineer that he is working on this, relevant people on AMI side are @FabioBergonti @GiulioRomualdi @Supermonkey-design @Giulero @pillai-s, I guess @FabioBergonti can be the entry point on the AMI side (if he is ok with it). |
Interesting for @icub-tech-iit/silo-mech @fiorisi |
Considering that we have to solve different issues before integrating the new battery in the CAD model in |
Task description
The SN002 has a shiny new battery back located in the back. To avoid inconsistencies at the dynamical level, it would be better to update the SN002 URDF with the new configuration.
Definition of Done
The SN002 URDF is updated considering the new battery pack
cc @Nicogene @traversaro @martinaxgloria @GiulioRomualdi
The text was updated successfully, but these errors were encountered: