Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
bliss
bliss
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 529
    • Issues 529
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge Requests 133
    • Merge Requests 133
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Bliss
  • blissbliss
  • Issues
  • #92

Closed
Open
Opened Jun 16, 2017 by Matias Guijarro@matias.guijarro
  • Report abuse
  • New issue
Report abuse New issue

Motor state re-reading from hardware

IcePAP motors can have closed loop errors or become OFF while moving. Reported state is an error (no READY flag). In this case, even if the problem is solved with icepapcms or by some other external factor, motion would be impossible in bliss - only .sync_hard() can solve the state problem.

Proposal: when state is not READY when starting a motion, re-read the state from hardware to see if the situation improved since last time. Having the state update will remove the need to call sync_hard().

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
3
Labels
help wanted improvement question
Assign labels
  • View project labels
Reference: bliss/bliss#92