Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • L libbarrett
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 19
    • Issues 19
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • software
  • libbarrett
  • Issues
  • #13

Closed
Open
Created Jan 26, 2017 by Amy Blank@amyblank🌈Owner

Hand::waitUntilDoneMoving should pass a realtime flag

When running both a WAM and a hand simultaneously, it is possible to call hand.trapezoidalMove() and related commands in the main loop. However, using the blocking functionality (hand.trapezoidalMove(position, true)) causes the WAM to heartbeat fault. It looks like this is because the doneMoving() command ends up getting called with realtime=false, so the thread does not acquire a lock on the bus. Calling with realtime=true does not crash.

Assignee
Assign to
Time tracking