Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
B
burt-sharp
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Jobs
  • Commits
  • burt
  • software
  • burt-sharp
  • Merge Requests
  • !166

Open
Opened Mar 15, 2018 by Alexandros Lioulemes@alexandros💬Developer0 of 6 tasks completed0/6 tasks
  • Report abuse
Report abuse

feature/new-haptic-path

  • Overview 152
  • Commits 64
  • Pipelines 41
  • Changes 15

Description

This example demonstrates the haptic path (Constrain to Path). First, the user records a 3D trajectory and later the robot constrains the user into that path with a force-field mechanism. Also, the user can adjust the tangential forces for custom assistance or resistance along the path.

Steps for implementing the haptic path algorithm:

  1. Record Cartesian position data from the robot while performing a 3D trajectory

  2. Sample this data to be ("almost") equal-distant ( COARSE_STEP = 0.01; ) ==> (output) coarsePath

  3. Calculate the cubic spline from the coarsePath points.

  4. At each robot's control cycle, get its tool position (cp) and search for the closest point in the coarsePath. (This step has been modified slightly, as it is searching around the previous segment area for the detection of the closest distance point. That happened for the avoidance of intersecting-and-curved paths, where jerky situations are caused from the closest segment, far away from the current one.)

  5. Then search the area around the closest coarse point by calculating the minimum distance of the tool position with the spline points between [ - COARSE_STEP , + COARSE_STEP ] iterating with a tiny FINE_STEP.

  6. Finally, calculate the direction from the closest point into the spline.

What to focus on

  • Focus on the force/haptic rendering when you deviate from the recorded path.
  • Focus on the two different examples (Joint space and Tool space)

Reviewers

  • @alexandros
  • @amyblank
  • @bz
  • @cm
  • @lr
  • @tn

Resources

Issues

What issues does this fix?

  • Fixes #117
Edited Jan 11, 2021 by Amy Blank
Assignee
Assign to
Reviewer
Request review from
V3 U.S. Medical Release
Milestone
V3 U.S. Medical Release
Assign milestone
Time tracking
Reference: burt/software/burt-sharp!166
Source branch: feature/new-hapticPath