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

Add support for additional EGM modes #20

Open
jontje opened this issue Sep 6, 2018 · 4 comments
Open

Add support for additional EGM modes #20

jontje opened this issue Sep 6, 2018 · 4 comments
Labels
enhancement New feature or request

Comments

@jontje
Copy link
Contributor

jontje commented Sep 6, 2018

As per title.

Currently unsupported modes are:

  • EGM Path Correction
    Path correction can be used to correct a programmed robot path (requires using special RAPID move instructions).

  • EGM Position Stream (requires RobotWare 6.07 or later)
    Position streaming can be used for when it is only interesting to track a mechanical unit's position, and not to control it's motion.

This can for example be done by implementing additional EGM interface classes.

@jontje jontje added the enhancement New feature or request label Sep 6, 2018
@gavanderhoorn
Copy link
Member

@jontje: this should now be possible with the merge of #32 right?

@jontje
Copy link
Contributor Author

jontje commented Feb 22, 2019

Yes it is

@gavanderhoorn
Copy link
Member

@jontje: is there still work to be done here?

@jontje
Copy link
Contributor Author

jontje commented Feb 6, 2020

I will not be implementing support for EGM Path Correction anytime soon.

Regarding EGM Position Stream (i.e. only get feedback from the robot, and not send commands), then it works with the current EGMControllerInterface class. However, it might be nice to create an EGMStreamingInterface that only exposes a read method.

I also intend to implement support for external axes, which at the moment needs to be controlled in its own RAPID motion task (the abb_libegm classes currently only work when a six or seven axes robot is "on the other end"). And here it might also be nice to implement an EGMExternalAxisInterface, which doesn't expose the Cartesian write methods.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

2 participants