forked from epics_driver_modules/motorBase
R6-2 update.
This commit is contained in:
Ron Sluiter
@@ -2,7 +2,7 @@ Motor Record R6-2 Release Notice
|
||||
===============================================================================
|
||||
|
||||
The motor record software in this release is compatible with EPICS base
|
||||
R3.14.8.2.
|
||||
R3-14-9.
|
||||
|
||||
|
||||
Contents
|
||||
@@ -122,8 +122,8 @@ Modification Log from R6-1 to R6-2
|
||||
|
||||
File modified: NewportSrc/drvPM500.cc
|
||||
|
||||
2) Bug fix for OMS device support overwriting PID parameter fields during
|
||||
normalization calculation.
|
||||
2) A bug was introduced with R6-0. The OMS device support was overwriting PID
|
||||
parameter fields during normalization calculation.
|
||||
|
||||
File modified: OmsSrc/devOmsCom.cc
|
||||
|
||||
@@ -149,6 +149,15 @@ Modification Log from R6-1 to R6-2
|
||||
File modified: do_work() in motorRecord.cc
|
||||
|
||||
|
||||
6) Joe Sullivan added support for Thorlabs Piezo Control Module, model MDT695.
|
||||
|
||||
Directory added: motorApp/ThorLabsSrc
|
||||
|
||||
7) Due to releasing R6-1 during Newport development, R6-1 can result in linker
|
||||
errors on the symbol "xpsgathering". Newport users should upgrade to
|
||||
R6-2.
|
||||
|
||||
|
||||
Modification Log from R6-0 to R6-1
|
||||
==================================
|
||||
|
||||
|
||||
@@ -91,6 +91,9 @@ Channel support):
|
||||
<li>
|
||||
Spectra-Physics, Encoder Mike Controller, Model 18011.
|
||||
</li>
|
||||
<li>
|
||||
Thorlabs, Piezo Controller, Model MDT695.
|
||||
</li>
|
||||
</ul>
|
||||
The record maintains two coordinate systems for motor position ("user" and "dial
|
||||
" coordinates); displays drive and readback values; enforces limits to motor
|
||||
@@ -1776,7 +1779,7 @@ below.
|
||||
<td>Desired Output Loc</td>
|
||||
<td>INLINK</td>
|
||||
<td>If this field contains a valid EPICS link, and the OMSL field has the value
|
||||
"closed_loop" (1), then every time the <span lang="en-us"></span>motor record is processed, it will
|
||||
"closed_loop" (1), then every time the motor record is processed, it will
|
||||
get a value for the VAL field from the link and move to that location, ignoring
|
||||
all other drive fields. Closed-loop mode has not been tested extensively. </td>
|
||||
</tr>
|
||||
@@ -1787,7 +1790,7 @@ below.
|
||||
<td>GBLCHOICE</td>
|
||||
<td>(0:"supervisory", 1:"closed_loop") <br>
|
||||
If this field has the value "closed_loop" (1), and the field DOL contains a
|
||||
valid EPICS link, then every time the <span lang="en-us"></span>motor record is processed, it will get
|
||||
valid EPICS link, then every time the motor record is processed, it will get
|
||||
a value for the VAL field from the link and move to that location, ignoring all
|
||||
other drive fields. Closed-loop mode has not been tested extensively. </td>
|
||||
</tr>
|
||||
@@ -2826,8 +2829,7 @@ below.
|
||||
</li>
|
||||
<li>
|
||||
When drive-power status monitoring is enabled and a power failure is detected,
|
||||
the device driver will respond by activating the <span lang="en-us">
|
||||
</span>RA_OVERTRAVEL bit in the
|
||||
the device driver will respond by activating the RA_OVERTRAVEL bit in the
|
||||
MSTA. This results in either HLS or LLS being activated depending on the
|
||||
DIR field. In addition, the following message will appear in the error log; "Drive
|
||||
power failure at VME58 card#?? motor#??".
|
||||
|
||||
@@ -5,12 +5,67 @@
|
||||
<meta name="GENERATOR" content="Mozilla/4.77 [en] (X11; U; SunOS 5.8 sun4u) [Netscape]">
|
||||
<meta name="Author" content="Ronald L. Sluiter">
|
||||
<meta name="Description" content="Synopsis of modifications, fixes and new features for each motor record release.">
|
||||
<title>EPICS Motor Record Release R6.1 Notice</title>
|
||||
<title>EPICS Motor Record Release R6.2 Notice</title>
|
||||
<meta name="author" content="Ronald L. Sluiter">
|
||||
<meta name="description" content="Notification of bug fixes, functional changes and new features.">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<CENTER>
|
||||
<H1><B><U>Motor Record Version 6.2 Release Notice</U></B></H1>
|
||||
</CENTER>
|
||||
|
||||
<center>
|
||||
<h4><u>Modifications to Existing Features</u></h4>
|
||||
</CENTER>
|
||||
|
||||
<DIV align="left">
|
||||
<P>
|
||||
<U><B>Newport PM500 Initialization Problem</B></U>
|
||||
</P>
|
||||
<P>
|
||||
The PM500 driver was not issuing the correct command when it queried for the
|
||||
number of axes at boot up. This resulted in a "PM500 system error" message on
|
||||
the 1st axis.
|
||||
</P>
|
||||
<P>
|
||||
<U><B>Overwritten PID Parameters</B></U>
|
||||
</P>
|
||||
<P>
|
||||
A bug was introduced with R6-0; the OMS device support was overwriting PID
|
||||
parameter fields during its' normalization calculation.
|
||||
</P>
|
||||
<P>
|
||||
<U><B>Motor Position Initialization</B></U>
|
||||
</P>
|
||||
<P>
|
||||
There was a bug in the logic that determines the precedence between using the
|
||||
controller's or save/restore's motor position at boot-up. Negative controller
|
||||
positions were not handled correctly.
|
||||
</P>
|
||||
<U><B>Newport Build Problem</B></U>
|
||||
</P>
|
||||
<P>
|
||||
Due to releasing R6-1 during Newport development, R6-1 can result in linker
|
||||
errors on the symbol "xpsgathering". Newport users should upgrade to R6-2.
|
||||
</P>
|
||||
</DIV>
|
||||
|
||||
|
||||
<CENTER>
|
||||
<H4><U>New Features</U></H4>
|
||||
</CENTER>
|
||||
|
||||
<DIV align="left">
|
||||
<P>
|
||||
<U><B>Thorlabs model MDT695</B></U>
|
||||
</P>
|
||||
<P>
|
||||
Joe Sullivan added support for Thorlabs Piezo Control Module, model MDT695.
|
||||
</P>
|
||||
</DIV>
|
||||
|
||||
|
||||
<CENTER>
|
||||
<H1><B><U>Motor Record Version 6.1 Release Notice</U></B></H1>
|
||||
</CENTER>
|
||||
|
||||
Reference in New Issue
Block a user