Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
SmarActMCS
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Wiki
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
spe
ds
SmarActMCS
Commits
44fc938b
Commit
44fc938b
authored
4 years ago
by
Milan Prica
Browse files
Options
Downloads
Patches
Plain Diff
A minor update. Not happy with the original wording.
parent
e46d5214
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+7
-8
7 additions, 8 deletions
README.md
with
7 additions
and
8 deletions
README.md
+
7
−
8
View file @
44fc938b
# SmarAct MCS Tango device server.
There are two separate versions of the device server, one for positioners
with encoder (sensor) and the other for those without encoder (sensorless).
with encoder (sensor) and the other for those without encoder (sensorless)
as their behaviour differs considerably.
An MCS controller can control a number of positioners of both types, one
per channel. We have used 3, 6, 9 and 12 channel versions.
Commands are ASCII, device servers send strings and parse replies.
Typical installation consists of a socket-srv device server connected to
the controller and an instance of Smaract server per positioner.
A MCS controller can control a number of positioners of both types.
Typical installation consists of a socket-srv device server connected to the
controller and an instance of the appropriate Smaract server per positioner.
Symbolic links to the Python files should be created in the deployment
directory named respectively smaractmcs-srv and smaractmcs_ne-srv.
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment