Skip to content
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

MH5 Support Update #377

Open
acbuynak opened this issue Dec 6, 2020 · 4 comments
Open

MH5 Support Update #377

acbuynak opened this issue Dec 6, 2020 · 4 comments
Labels

Comments

@acbuynak
Copy link
Contributor

acbuynak commented Dec 6, 2020

I am working on an update to the MH5 support package.
Primarily changing things to follow ros-i conventions, ie REP-0199.

I have access to a MH5LSII variant.

The current MH5 support package matches the MH5F variant from what I can tell (c72c98c)(it's not notated specifically in package.xml). AFAIK, the MH5F variant is now archived and not sold new.

There are physical differences in link (L&R) shape and length between the "F" and "LSII/SII" variants.

I think it would be helpful to new users to change the default support model to match what Motoman sells, the MH5LSII or MH5SII (differs by long or short variant). If not I'm happy to push to motoman_experimental or otherwise.

Looking for guidance. Thanks!

@EricMarcil
Copy link
Contributor

Hi,

The MH5F (FS100) and MH5SII (DX200) and MH5S(DX100) are the same (physically and parameters)
The MH5LF (FS100) and MH5SLII (DX200) and MH5SL(DX100) are the same (physically and parameters)
For the long model, it has a longer L-axis (different part) and an extension to the U-axis (front of U-axis the arm is the same).

I took a look at the current URDF on github, and I can't the reference to the current values. The physical model matches the later version with the slim (tapered) R-axis. But the parameters are probable from the initial model (none tapered R-axis) for which there were a lot of variants.

The values that I currently have for the short:
image

and for the long model:
image

Below are the spec files for each models:
MH5-series.zip

So I would tend to agree that the model could be updated and we could make a variant for the long model.

@acbuynak
Copy link
Contributor Author

acbuynak commented Jan 5, 2021

Thanks for the info! I'm pulling together an updated short "MH5" and a new long "MH5L" support package. I'll get those into a PR soon.

I can't the reference to the current values. The physical model matches the later version with the slim (tapered) R-axis. But the parameters are probably from the initial model (none tapered R-axis) for which there were a lot of variants.

I'm seeing a disagreement for the U-axis motion limits between the above shared CSV files and the MH5LSII webpage. Not sure if this is a discrepancy error or different model variants. Which should take precedence?

@gavanderhoorn
Copy link
Member

I'm pulling together an updated short "MH5" and a new long "MH5L" support package.

If those are actually variants, please put them in the same package, so we avoid creating more packages than absolutely necessary.

@EricMarcil
Copy link
Contributor

@acbuynak Use the ones from the CSV which are angle relative to the previous axis. The values on the spec sheet you are referring to are angle relative to the ground. So it is actually the compound angle of L and U axis that are written for the U-axis.

cjue added a commit to isys-vision/motoman that referenced this issue Aug 24, 2022
cjue added a commit to isys-vision/motoman that referenced this issue Aug 24, 2022
cjue added a commit to isys-vision/motoman that referenced this issue Aug 29, 2022
cjue added a commit to isys-vision/motoman that referenced this issue Mar 22, 2023
cjue added a commit to isys-vision/motoman that referenced this issue Mar 27, 2023
cjue added a commit to isys-vision/motoman that referenced this issue Aug 15, 2023
cjue added a commit to isys-vision/motoman that referenced this issue Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

3 participants