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

Using freedrive mode triggers error on teach pendant: freedrive_mode(): Arguments 'a' and 'V' must be positive #583

Closed
faev999 opened this issue Oct 20, 2022 · 4 comments

Comments

@faev999
Copy link

faev999 commented Oct 20, 2022

Summary

The issue I am experiencing is not yet listed on the existing issues

Introduction to the issue

Versions

  • ROS Driver version:
  • Affected Robot Software Version(s): 5.12.0-2
  • Affected Robot Hardware Version(s): UR10e
  • Robot Serial Number:
  • UR+ product(s) installed:
  • URCaps Software version(s):

Impact

not being able to switch to freedrive mode

Issue details

when using the freedrive service implementation suggested here freedrive service there's an error in the teach-pendandt that reads freedrive_mode(): Arguments 'a' and 'V' must be positive. as described before this only happens on polyscope 5.12, it works perfectly fine on 5.11.

I found this bit on the official Ur forum: apparently it's a bug on the 5.12.x versions less than 5.12.4(bug fixed). I recon it's important to put this info here because it's my understanding (maybe I am wrong) that they are changing the way freedrive should be used, and it might be important for #546 and #573

Project status at point of discovered

When did you first observe the issue?
when testing on a robot with polyscope 5.12.0

Steps to Reproduce

launch driver and trying to call freedrive service

Expected Behavior

robot entering freedrive mode

Actual Behavior

error on teach pendant screen

Workaround Suggestion

for now downgrade to 5.11 or upgrade to 5.12.4

@github-actions
Copy link

This issue has not been updated for a long time. If no further updates are added, this will be closed automatically. Comment on the issue to prevent automatic closing.

@fmauch
Copy link
Contributor

fmauch commented Jan 24, 2023

Since this has never been responded to, this should not get closed before further investigation is done.

@github-actions
Copy link

This issue has not been updated for a long time. If no further updates are added, this will be closed automatically. Comment on the issue to prevent automatic closing.

@github-actions
Copy link

This issue has been closed due to inactivity. Feel free to comment or reopen if this is still relevant.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants