Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bliss bliss
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 542
    • Issues 542
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge requests 145
    • Merge requests 145
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • BlissBliss
  • blissbliss
  • Issues
  • #2531
Closed
Open
Issue created Jan 29, 2021 by Laurent Claustre@claustreOwner

smaract_mcs2 motor controller

SmarAct MCS2 (Modular Control System 2) controller for pico motor stages,is a new generation of controllers renewing the family of MCS and SCU controllers for stages.

The control interface is supporting TCP/IP connection on default port 55551 using SCPI command protocol. A binary protocol exists but it requires the use of the SDK libraries (C/C++, python).

The MCS2 controller is able to automatically detect the Positioner type (linear, rotating, ....) connected on each channel, nevertheless one can set manually the Positioner type and ask the controller to calibrate a new Positioner. This is not a simple procedure which needs some expertise.

In a first implementation of the smaract_mcs2 bliss controller we will use the SCPI command protocol and do not give access to the Positioner type.

Edited Jan 29, 2021 by Laurent Claustre
Assignee
Assign to
Time tracking