lin-epics-modules/motorBase
0
0
Fork 0
forked from epics_driver_modules/motorBase
Code Pull Requests Activity

Fix references to menuYesNo.db for LOCK and NTM.

Browse Source
This commit is contained in:
Ron Sluiter
2008-03-17 20:04:13 +00:00
parent 55c702f03e
commit c20ac59586
1 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/motorRecord.html
+10 -10
View File
@@ -578,7 +578,7 @@ below.
<td>R/W*</td>
<td>Soft Channel Position Lock</td>
<td>RECCHOICE</td>
<td>(0:"No", 1:"Yes")</td>
<td>(0:"NO", 1:"YES")</td>
</tr>
<tr>
<td><a href="#Fields_alarm">LOLO</a></td>
@@ -711,7 +711,7 @@ below.
<td>R/W*</td>
<td>New Target Monitor</td>
<td>RECCHOICE</td>
<td>(0:"No", 1:"Yes")</td>
<td>(0:"NO", 1:"YES")</td>
</tr>
<tr>
<td><a href="#Fields_misc">NTMF</a></td>
@@ -757,7 +757,7 @@ below.
<td>R/W</td>
<td>Periodic Limits</td>
<td>RECCHOICE</td>
<td>(0:"No", 1:"Yes")</td>
<td>(0:"NO", 1:"YES")</td>
</tr>
<tr>
<td><a href="#Fields_misc">POST</a></td>
@@ -2893,7 +2893,7 @@ below.
readback position. Soft Channel device support detects that the "hard" motor
has initiated the move when it sees the PV pointed to by DINP go false, while
the "soft" record's DMOV is true. Automatic synchronization is undesirable in a
multi-axis application. Hence, setting the LOCK field to "Yes" disables this
multi-axis application. Hence, setting the LOCK field to "YES" disables this
automatic synchronization.</td>
</tr>
<tr>
@@ -2904,23 +2904,23 @@ below.
<td>The requirements on how the motor record processes a new target position
while the motor is in motion are as follows;<BR>
Case #1: The motor record is given a new position, which is in the opposite
direction from the current motor motion. If NTM is "Yes", the motor is
immediately stopped and given a motion command to the new position. If NTM is "No
direction from the current motor motion. If NTM is "YES", the motor is
immediately stopped and given a motion command to the new position. If NTM is "NO
", the motor completes the previous move before it is given a motion command to
the new position.<BR>
Case #2: The motor record is given a new position, which is in the same
direction as the current motor motion, but the new position is closer to the
motor's current position than the original target position. If NTM is "Yes",
motor's current position than the original target position. If NTM is "YES",
the motor is stopped after it has gone past the new position; then a command is
given to return to the new position. If NTM is "No", the motor completes the
given to return to the new position. If NTM is "NO", the motor completes the
previous move before it is given a motion command to the new position.<BR>
Case #3: The motor record is given a new position, which is in the same
direction as the current motor motion, but the new position is further from the
motor's current position than the original position. After the motor reaches
the original target position and stops, a command is given to the new target
position. This case is independent of NTM.<BR>
NTM defaults to "Yes". It should be set to "No" only for soft motors. Soft
motors should be configured with NTM set to "No" to prevent Case #1 above from
NTM defaults to "YES". It should be set to "NO" only for soft motors. Soft
motors should be configured with NTM set to "NO" to prevent Case #1 above from
interfering with "hard" motors using backlash correction. </td>
</tr>
<tr>