23 Commits

Author SHA1 Message Date
7e111d5931 Merge branch 'dev' 2024-08-09 13:03:49 -05:00
21a553fd3f Fixed replyvalue comparison data type. 2024-08-09 13:03:19 -05:00
cae5b2e8f8 Merge branch 'dev' 2024-08-07 11:21:37 -05:00
daf3527a1e Merge branch 'documentation-update' into dev 2024-08-07 11:21:17 -05:00
39db58a2e9 Cleaned up the IOC configuration section. 2024-08-07 11:20:53 -05:00
66996c3bf2 Cleaned up velocity target section in readme. 2024-08-07 11:01:56 -05:00
ffab0885cb Updated readme IOC usage sections. 2024-08-07 10:46:53 -05:00
b6cdd85d80 Rewrote IOC config description. 2024-08-07 10:44:22 -05:00
8be8f42df0 Reordered sections again. 2024-08-07 10:44:19 -05:00
cd37aa6d09 Reordered sections. 2024-08-07 10:44:17 -05:00
d225024d69 Updated readme for more consistent markdown formatting between sections. 2024-08-07 10:44:09 -05:00
BScatterplot
3fcff74a1b Merge pull request #10 from Binary-Coalescence/dev
Added a minimum wait time after stepping for the Homing routine.
2024-08-06 19:12:30 -05:00
760716f342 Added a minimum wait time after stepping for the Homing routine. Otherwise, you sometimes had to send the Home command twice. (Unsure of the reason.) 2024-08-06 19:10:25 -05:00
4a7868285f Merge branch 'dev' 2024-08-06 15:39:55 -05:00
c6edb953a5 Updated multi-motor ioc config file with new velocities. 2024-08-06 15:39:09 -05:00
c4d9507f84 Merge branch 'homing' into dev 2024-08-06 12:48:20 -05:00
5e36582ecc Added error status checking to home routine. 2024-08-06 12:46:22 -05:00
d605ceceae Merge branch 'homing' into dev 2024-08-06 12:39:24 -05:00
bf680d0c6f Updated homing routine to set initial direction. 2024-08-06 12:30:38 -05:00
10028ba1c1 Merge branch 'dev' 2024-08-05 13:59:37 -05:00
ffada72c50 Updated default motor speeds. 2024-08-05 13:58:33 -05:00
72d6fb6c05 Merge branch 'dev' 2024-08-05 12:05:57 -05:00
f8f457c1c0 Merge branch 'dev' 2024-08-05 12:03:51 -05:00
7 changed files with 200 additions and 147 deletions

246
README.md
View File

@@ -9,95 +9,15 @@ motorDSM can also be built outside of motor by copying it's ``configure/EXAMPLE_
motorDSM contains an example IOC that is built if ``configure/CONFIG_SITE.local`` sets ``BUILD_IOCS = YES``. The example IOC can be built outside of the driver module. Copy ``iocs/dsmIOC/configure/EXAMPLE_RELEASE.local`` to ``RELEASE.local`` and uncomment and set the paths for the appropriate lines depending on whether motorDSM was built inside the motor module or independently.
# Running an example IOC
To run the example IOC, build the packages listed below, then:
1. Follow the steps in "Configuring the system for attached controllers" below.
2. Set the "EPICS_CA_ADDR_LIST" environment variable to include the IP address of the server.
If it's running on the same computer, you can use the loopback IP address.
`export EPICS_CA_ADDR_LIST='127.0.0.1'`
3. In the ``iocs/dsmIOC/iocBoot/iocDsm`` directory, run
```
$ ../../bin/linux-x86_64/dsm st.cmd.md90
```
for one attached MD-90 controller, or
```
$ ../../bin/linux-x86_64/dsm st.cmd.md90.multi
```
for eight attached MD-90 controllers. Edit this file to use more than one unit; simply comment out the ones you don't need.
4. Test using the `caget` and `caput` arguments as described in the "Example usage" section below.
# Configuring the system for attached controllers
-------------------------------------------------
The following steps must be used in either st.cmd.md90 (for a single unit) or in st.cmd.md90.multiple (for multiple units).
st.cmd.md90.multiple includes 8 motors predefined on /dev/ttyUSB0 through /dev/ttyUSB7. Comment out all motors you don't need.
**1. Define a new serial port named "serial0" and set the location of the physical port**
`drvAsynSerialPortConfigure([serial name], [device location], 0, 0, 0)`
*e.g., `drvAsynSerialPortConfigure("serial0", "/dev/ttyUSB0", 0, 0, 0)`*
**2. Configure the port**
- Baud = 115200
- Bits = 8
- Parity = none
- Stop bits = 1
- Input end of message: "\r"
- Output end of message: "\r"
- Trace IO mask: 2
```
asynSetOption([serial name], 0, "baud", "115200")
asynSetOption([serial name], 0, "bits", "8")
asynSetOption([serial name], 0, "parity", "none")
asynSetOption([serial name], 0, "stop", "1")
asynOctetSetInputEos("serial0", 0, "\r")
asynOctetSetOutputEos("serial0", 0, "\r")
asynSetTraceIOMask("serial0", 0, 2)
```
where `[serial name]` is the name you assigned in step 1, surrounded by double quotes.
**3. Set initial parameters**
- Power supply enabled (`EPS` command)
- Deadband = 10 nm (`SDB 10` command)
```
asynOctetConnect("initConnection", [serial name], 0)
asynOctetWrite("initConnection", "EPS")
asynOctetWrite("initConnection", "SDB 10")
asynOctetDisconnect('initConnection')
```
**4. Create MD90 Controller object**
`MD90CreateController([controller name], [serial name], 1, 100, 5000)`
where `[controller name]` is the name of the motor to assign. Convention is to use "MD90n", starting with n=0.
**5. Intialize the IOC**
After the call to `iocInit` (still in the st.cmd.md90[.multiple] file), issue the following commands for each motor. The example below uses `DSM:m0` but it should be run for each line described in motor.substitutions.md90 (or motor.substitutions.md90.multiple).
````
dbpf("DSM:m0.RTRY", "0") #sets retries to 0; this is automatic on the MD90
dbpf("DSM:m0.TWV", "0.1") #Tweak distance
dbpf("DSM:m0.VMAX", "1.0") #Sets max velocity to 1 mm/s
dbpf("DSM:m0.HVEL", "1.0") #Sets max velocity to 1 mm/s
````
**6. Update the substitutions file**
Save and close the st.cmd file you've been configuring, then open the motor substitutions file (motor.substitutions.md90[.multiple]).
Ensure the values in the `pattern` block's `PORT` field match the names used in the std.cmd file.
Note that, despite this field being called "Port", they use the names of the MD90 Controller object defined above (by default, MD900, MD901, etc.
Do __not__ use the direct serial port names (by default, serial0, serial1, etc.).
# Compiling motorDSM
------------------------
Compiling motorDSM
-------------------------------------------------
To set up a full EPICS stack for development and testing, install and configure all of the following dependencies:
------------------------
epics-base
------------------------
### epics-base
Install make, gcc, and perl packages if not already installed, then clone and build epics-base:
@@ -110,8 +30,7 @@ Install make, gcc, and perl packages if not already installed, then clone and bu
------------------------
asyn
------------------------
### asyn
$ cd $SUPPORT
$ git clone git@github.com:epics-modules/asyn.git
@@ -132,8 +51,7 @@ if appropriate header files are in ``/usr/include/tirpc/rpc`` instead of ``/usr/
------------------------
seq
------------------------
### seq
$ cd $SUPPORT
$ git clone git@github.com:ISISComputingGroup/EPICS-seq.git seq
@@ -150,8 +68,7 @@ Edit ``seq/configure/RELEASE`` to add the missing '-' before the ``include`` for
------------------------
motor
------------------------
### motor
$ cd $SUPPORT
$ git clone git@github.com:epics-modules/motor.git
@@ -164,8 +81,7 @@ Create ``motor/configure/RELEASE.local`` and set ``SUPPORT``, ``ASYN``, ``SNCSEQ
------------------------
motorDSM (this package)
------------------------
### motorDSM (this package)
$ cd $SUPPORT
$ git clone git@github.com:Binary-Coalescence/motorDSM.git
@@ -181,49 +97,135 @@ In ``motorDSM/iocs/dsmIOC/configure``, copy ``EXAMPLE_RELEASE.local`` to ``RELEA
$ make distclean
$ make
------------------------
# Example usage
After building, run the example IOC described at the top of this section in one terminal window.
Open another terminal window and navigate to [EPICS install directory]/epics-base/bin/linux-x86_64/ (or wherever you built EPICS base.
Use the commands `caput` and `caget` to set and read process variables.
-------------------------------------------------
Configuring the IOC server
-------------------------------------------------
For example, to get the current position, use `./caget DSM:m0.REP`. This reads the REP variable, which is the "Raw Encoder Position". Set m0 to m1, m2, etc. for multiple motors.
The directory `$SUPPORT/motorDSM/iocs/dsmIOC/iocBoot/iocDSM` contains example configurations for the IOC server that runs on the computer the motor controllers are attached to. The `st.cmd.md90` and `motor.substitutions.md90` files provide an example to configure and run one attached MD-90. The `st.cmd.md90.multi` and `motor.substitutions.md90.multi` files provide an example to configure and run eight attached MD-90s connected on ports `dev/ttyUSB0` through `/dev/ttyUSB7`. Add or remove lines from the `*.multi` files as necessary to configure a different number of attached MD-90s.
Other examples
-------------------------
The parameters in the IOC startup scripts are detailed here, but the files should contain reasonable defaults to run as-is.
**1. Define a new serial port named "serial0" and set the location of the physical port**
`drvAsynSerialPortConfigure("[serial name]", "[device location]", 0, 0, 0)`
*e.g., `drvAsynSerialPortConfigure("serial0", "/dev/ttyUSB0", 0, 0, 0)`*
**2. Configure the port**
- Baud = 115200
- Bits = 8
- Parity = none
- Stop bits = 1
- Input end of message: "\r"
- Output end of message: "\r"
- Trace IO mask: 2
```
asynSetOption("[serial name]", 0, "baud", "115200")
asynSetOption("[serial name]", 0, "bits", "8")
asynSetOption("[serial name]", 0, "parity", "none")
asynSetOption("[serial name]", 0, "stop", "1")
asynOctetSetInputEos("[serial name]", 0, "\r")
asynOctetSetOutputEos("[serial name]", 0, "\r")
asynSetTraceIOMask("[serial name]", 0, 2)
```
Here `[serial name]` is the name you assigned in step 1.
**3. Set initial parameters**
- Power supply enabled (`EPS` command)
- Deadband = 10 nm (`SDB 10` command)
```
asynOctetConnect("initConnection", [serial name], 0)
asynOctetWrite("initConnection", "EPS")
asynOctetWrite("initConnection", "SDB 10")
asynOctetDisconnect('initConnection')
```
**4. Create MD-90 Controller object**
`MD90CreateController([controller name], [serial name], 1, 100, 5000)`
Here `[controller name]` is the name of the motor to assign. Convention is to use "MD90n", starting with n=0.
**5. Intialize the IOC**
After the call to `iocInit` (still in the st.cmd.md90[.multi] file), set up some default values for EPICS process variables for each motor. The example below uses `DSM:m0`, but they should also be set for each motor configured in the IOC startup script if connecting more than one.
````
dbpf("DSM:m0.RTRY", "0") #sets retries to 0; this is automatic on the MD90
dbpf("DSM:m0.TWV", "0.1") #Tweak distance
dbpf("DSM:m0.VMAX", "1.0") #Sets max velocity to 1 mm/s
dbpf("DSM:m0.HVEL", "1.0") #Sets max velocity to 1 mm/s
````
**6. Update the substitutions file**
In the motor substitutions file (motor.substitutions.md90[.multi]), ensure the values in the `pattern` block's `PORT` field match the names used in the `std.cmd.md90[.multi]` file. Note that, despite this field being called "Port", it usese the names of the MD90 Controller object defined above (by default, MD900, MD901, etc). Do __not__ use the direct serial port names (by default, serial0, serial1, etc.).
-------------------------------------------------
Running the example IOC
-------------------------------------------------
To run the example IOC configured above:
1. Follow the steps in "Configuring the system for attached controllers" below.
3. In the ``iocs/dsmIOC/iocBoot/iocDsm`` directory, run
`$ ../../bin/linux-x86_64/dsm st.cmd.md90`
for one attached MD-90 controller, or
`$ ../../bin/linux-x86_64/dsm st.cmd.md90.multi`
for multiple attached MD-90 controllers. This is set up for eight controllers, so add or remove lines as appropriate if using a different number.
4. Test using the `caget` and `caput` programs from the `epics-base` package as described in the "Example usage" section below.
-------------------------------------------------
Example usage
-------------------------------------------------
1. After building, run the example IOC described above in one terminal window.
2. Open another terminal window on either the same computer as the IOC or another computer on the LAN and navigate to `[EPICS install directory]/epics-base/bin/linux-x86_64/` (or wherever you built EPICS base). You could alternatively add this directory to your PATH.
3. Set the "EPICS_CA_ADDR_LIST" environment variable to include the IP address of the server. If it's running on the same computer, you can use the loopback IP address:
`$ export EPICS_CA_ADDR_LIST='127.0.0.1'`
4. Use the `caget` and `caput` programs to read and set process variables, respectively.
For example, to get the current position (in encoder counts of 10 nm), use:
`$ ./caget DSM:m0.REP`
This reads the REP variable, which is the "Raw Encoder Position". Additionally, change `m0` to `m1`, `m2`, etc. to read the values from other motors when running more than one.
Homing the motor (must be done before you can issue position commands):
`./caput DSM:m0.HOMF 1 #Begins homing sequence in the forward direction`
`./caput DSM:m0.HOMR 1 #Begins homing sequence in the reverse direction`
`$ ./caput DSM:m0.HOMF 1`
This starts the homing sequence in the forward direction. Alternatively, for homing starting in the reverse direction:
`$ ./caput DSM:m0.HOMR 1`
Moving to a position target:
`./caput DSM:m0.VAL 2.345 #Moves to 2.345 mm`
`$ ./caput DSM:m0.VAL 2.345`
This moves the motor to 2.345 mm.
Setting a velocity target:
`./caput DSM:m0.VELO 0.5 #Sets velocity target to 0.5 mm/s`
(Note that velocity targets are appropriate only. They adjust the step rate of the motor and are not guaranteed to be exact.)
`$ ./caput DSM:m0.VELO 0.5`
This sets the velocity target to 0.5 mm/s. (Note that velocity targets are approximate only. They adjust the step rate of the motor and are not guaranteed to be exact.)
A note aboue velocity targets
-----------------------------
The I-20 motor driven by the MD-90 is a closed loop "step and repeat" motor that takes full steps towards its position target until it is
close, then will perform linear extensions to close the loop on the target position. This is handled internally on the MD-90, not by
EPICS.
The Velocity target parameter sets the step frequency
at which the motor operates on its way to the target position. The speed is not closed loop, and will depend on external loads, environmental
conditions, etc. A speed target of 1 mm/s will generate a roughly 1 mm/s motion, but it is not guaranteed.
-------------------------------------------------
A note about velocity targets
-------------------------------------------------
Additionally, due to the way EPICS operates, setting VELO will not immediately send a command to the MD90. Instead, EPICS remembers the last value you set, and will set this new
velocity target when it sends the next move command. **However, the motor must not be in servo mode to accept a new velocity target.**
The I-20 motor driven by the MD-90 is a closed loop "step and repeat" motor that takes full steps towards its position target until it is close, then will perform linear extensions to close the loop on the target position. This is handled internally on the MD-90, not by EPICS.
The motor enters servo mode when you send a new position target, and stays in servo mode until you issue a Stop command
(by setting the `DSM:m0.STOP` parameter to 1).
The velocity target parameter sets the step frequency at which the motor operates on its way to the target position. The speed is not closed loop, and will depend on external loads, environmental conditions, etc. A speed target of 1 mm/s will generate a roughly 1 mm/s motion, but it is not guaranteed.
If you do not disable servo prior to issuing a Move command at the new velocity, then VELO will become out of sync with the actual motor
velocity, and EPICS will return error 3 "Cannot execute while moving" in its console each time you issue a Move command.
This is because each Move command internally sends a "Set step frequenc" command, which will error if you do not Stop the motor first.
Reading the VELO parameter at this point will return the wrong value- it returns the value you requested, not the actual speed setting
on the motor.
To fix this, you must Stop the motor, then send a new Move command. At
Additionally, due to the way EPICS operates, setting `VELO` will not immediately send a command to the MD-90. Instead, EPICS remembers the last value you set, and will set this new velocity target when it sends the next move command. **However, the motor must not be in servo mode to accept a new velocity target.**
The motor enters servo mode when you send a new position target, and stays in servo mode until you issue a Stop command (by setting the `DSM:m0.STOP` parameter to 1).
If you do not disable servo prior to issuing a Move command at the new velocity, then `VELO` will become out of sync with the actual motor velocity, and EPICS will return error 3 "Cannot execute while moving" in its console each time you issue a Move command. This is because each Move command internally sends a "Set step frequency" command, which will error if you do not Stop the motor first. Reading the VELO parameter at this point will return the wrong value--it returns the value you requested, not the actual speed setting on the motor. To fix this, you must Stop the motor, then send a new Move command.

View File

@@ -12,6 +12,8 @@ March 1, 2012
#include <string.h>
#include <stdlib.h>
#include <math.h>
#include <chrono>
#include <thread>
#include <iocsh.h>
#include <epicsThread.h>
@@ -183,7 +185,7 @@ asynStatus MD90Axis::sendAccelAndVelocity(double acceleration, double velocity)
// Send the velocity
// Velocity provided in steps/sec
// Our unit step size of the encoder is 10 nm, but the motor moves in steps approx. 5 micrometers.
// Our unit step size of the encoder is 10 nm, but the motor moves in steps approx. 10 micrometers.
// Motor controller accepts step frequency in Hz.
freq = NINT(fabs(velocity / COUNTS_PER_STEP));
sprintf(pC_->outString_, "SSF %d", freq);
@@ -219,13 +221,46 @@ asynStatus MD90Axis::move(double position, int relative, double minVelocity, dou
asynStatus MD90Axis::home(double minVelocity, double maxVelocity, double acceleration, int forwards)
{
int sleepTime;
asynStatus status;
static const char *functionName = "MD90Axis::home";
status = sendAccelAndVelocity(acceleration, maxVelocity);
sprintf(pC_->outString_, "HOM");
status = pC_->writeReadController();
// The MD-90 will start the home routine in the direction of the last move
// Here we first make a small move to set the desired direction before homing
if (!status) {
sprintf(pC_->outString_, "SNS %d", SMALL_NSTEPS);
status = pC_->writeReadController();
}
if (!status) {
status = parseReply(functionName, pC_->inString_);
}
if (forwards) {
sprintf(pC_->outString_, "ESF");
} else {
sprintf(pC_->outString_, "ESB");
}
if (!status) {
status = pC_->writeReadController();
}
if (!status) {
status = parseReply(functionName, pC_->inString_);
}
if (!status) {
// Wait for the move to complete, then home
sleepTime = SLEEP_MARGIN * SMALL_NSTEPS * COUNTS_PER_STEP / maxVelocity;
if (sleepTime < HOME_SLEEP_MIN) {
sleepTime = HOME_SLEEP_MIN;
}
std::this_thread::sleep_for(std::chrono::seconds(sleepTime));
sprintf(pC_->outString_, "HOM");
status = pC_->writeReadController();
}
if (!status) {
status = parseReply(functionName, pC_->inString_);
}
@@ -356,7 +391,7 @@ asynStatus MD90Axis::poll(bool *moving)
if (comStatus) goto skip;
// The response string is of the form "0: Power supply enabled state: 1"
sscanf(pC_->inString_, "%d: %[^:]: %d", &replyStatus, replyString, &replyValue);
driveOn = (replyValue == '1') ? 1:0;
driveOn = (replyValue == 1) ? 1:0;
setIntegerParam(pC_->motorStatusPowerOn_, driveOn);
// Read the home status
@@ -365,7 +400,7 @@ asynStatus MD90Axis::poll(bool *moving)
if (comStatus) goto skip;
// The response string is of the form "0: Home status: 1"
sscanf(pC_->inString_, "%d: %[^:]: %d", &replyStatus, replyString, &replyValue);
homed = (replyValue == '1') ? 1:0;
homed = (replyValue == 1) ? 1:0;
setIntegerParam(pC_->motorStatusHomed_, homed);
// Read the moving status of this motor
@@ -374,7 +409,7 @@ asynStatus MD90Axis::poll(bool *moving)
if (comStatus) goto skip;
// The response string is of the form "0: Current status value: 0"
sscanf(pC_->inString_, "%d: %[^:]: %d", &replyStatus, replyString, &replyValue);
done = (replyValue == '2') ? 0:1;
done = (replyValue == 2) ? 0:1;
setIntegerParam(pC_->motorStatusDone_, done);
*moving = done ? false:true;
switch(replyValue) {

View File

@@ -12,7 +12,10 @@ USAGE... Motor driver support for the DSM MD-90 controller.
// No controller-specific parameters yet
#define NUM_MD90_PARAMS 0
#define COUNTS_PER_STEP 1000.0 //Number of encoder counts per motor step (measured by testing)
#define SLEEP_MARGIN 1.2 // Extra factor to wait after stepping before homing
#define HOME_SLEEP_MIN 1 // Minimum amount of time to wait after stepping/before homing
#define SMALL_NSTEPS 5 // Number of steps to take to set direction for homing routine
#define COUNTS_PER_STEP 1000.0 // Number of encoder counts per motor step (measured by testing)
class epicsShareClass MD90Axis : public asynMotorAxis
{

View File

@@ -2,7 +2,7 @@ file "$(MOTOR)/db/basic_asyn_motor.db"
{
pattern
{P, N, M, DTYP, PORT, ADDR, DESC, EGU, DIR, VELO, VBAS, VMAX, ACCL, BDST, BVEL, BACC, MRES, PREC, DHLM, DLLM, INIT}
{DSM:, 0, "m$(N)", "asynMotor", MD900, 0, "MD-90", mm, Pos, 0.5, 0.025, 0.625, 0, 0, 0.03, 0, .00001, 2, 20, -20, ""}
{DSM:, 0, "m$(N)", "asynMotor", MD900, 0, "MD-90", mm, Pos, 1.0, 0.05, 1.0, 0, 0, 0.05, 0, .00001, 2, 20, -20, ""}
}
# P IOC prefix
@@ -19,6 +19,8 @@ pattern
# VMAX Maximum velocity (EGU / s) (note: not getting set here with basic_asyn_motor.db)
# ACCL Acceleration (time in seconds until VELO)
# BDST Backlash distance
# BVEL Backlash velocity
# BACC Backlash acceleration
# MRES Motor step size (EGU)
# PREC Display precision number of decimal places
# DHLM Dial high travel limit (EGU)

View File

@@ -2,14 +2,14 @@ file "$(MOTOR)/db/basic_asyn_motor.db"
{
pattern
{P, N, M, DTYP, PORT, ADDR, DESC, EGU, DIR, VELO, VBAS, VMAX, ACCL, BDST, BVEL, BACC, MRES, PREC, DHLM, DLLM, INIT}
{DSM:, 0, "m$(N)", "asynMotor", MD900, 0, "MD-90", mm, Pos, 0.5, 0.025, 0.625, 0, 0, 0.03, 0, .00001, 2, 20, -20, ""}
{DSM:, 1, "m$(N)", "asynMotor", MD901, 0, "MD-90", mm, Pos, 0.5, 0.025, 0.625, 0, 0, 0.03, 0, .00001, 2, 20, -20, ""}
{DSM:, 2, "m$(N)", "asynMotor", MD902, 0, "MD-90", mm, Pos, 0.5, 0.025, 0.625, 0, 0, 0.03, 0, .00001, 2, 20, -20, ""}
{DSM:, 3, "m$(N)", "asynMotor", MD903, 0, "MD-90", mm, Pos, 0.5, 0.025, 0.625, 0, 0, 0.03, 0, .00001, 2, 20, -20, ""}
{DSM:, 4, "m$(N)", "asynMotor", MD904, 0, "MD-90", mm, Pos, 0.5, 0.025, 0.625, 0, 0, 0.03, 0, .00001, 2, 20, -20, ""}
{DSM:, 5, "m$(N)", "asynMotor", MD905, 0, "MD-90", mm, Pos, 0.5, 0.025, 0.625, 0, 0, 0.03, 0, .00001, 2, 20, -20, ""}
{DSM:, 6, "m$(N)", "asynMotor", MD906, 0, "MD-90", mm, Pos, 0.5, 0.025, 0.625, 0, 0, 0.03, 0, .00001, 2, 20, -20, ""}
{DSM:, 7, "m$(N)", "asynMotor", MD907, 0, "MD-90", mm, Pos, 0.5, 0.025, 0.625, 0, 0, 0.03, 0, .00001, 2, 20, -20, ""}
{DSM:, 0, "m$(N)", "asynMotor", MD900, 0, "MD-90", mm, Pos, 1.0, 0.05, 1.0, 0, 0, 0.05, 0, .00001, 2, 20, -20, ""}
{DSM:, 1, "m$(N)", "asynMotor", MD901, 0, "MD-90", mm, Pos, 1.0, 0.05, 1.0, 0, 0, 0.05, 0, .00001, 2, 20, -20, ""}
{DSM:, 2, "m$(N)", "asynMotor", MD902, 0, "MD-90", mm, Pos, 1.0, 0.05, 1.0, 0, 0, 0.05, 0, .00001, 2, 20, -20, ""}
{DSM:, 3, "m$(N)", "asynMotor", MD903, 0, "MD-90", mm, Pos, 1.0, 0.05, 1.0, 0, 0, 0.05, 0, .00001, 2, 20, -20, ""}
{DSM:, 4, "m$(N)", "asynMotor", MD904, 0, "MD-90", mm, Pos, 1.0, 0.05, 1.0, 0, 0, 0.05, 0, .00001, 2, 20, -20, ""}
{DSM:, 5, "m$(N)", "asynMotor", MD905, 0, "MD-90", mm, Pos, 1.0, 0.05, 1.0, 0, 0, 0.05, 0, .00001, 2, 20, -20, ""}
{DSM:, 6, "m$(N)", "asynMotor", MD906, 0, "MD-90", mm, Pos, 1.0, 0.05, 1.0, 0, 0, 0.05, 0, .00001, 2, 20, -20, ""}
{DSM:, 7, "m$(N)", "asynMotor", MD907, 0, "MD-90", mm, Pos, 1.0, 0.05, 1.0, 0, 0, 0.05, 0, .00001, 2, 20, -20, ""}
}
# P IOC prefix
@@ -26,6 +26,8 @@ pattern
# VMAX Maximum velocity (EGU / s) (note: not getting set here with basic_asyn_motor.db)
# ACCL Acceleration (time in seconds until VELO)
# BDST Backlash distance
# BVEL Backlash velocity
# BACC Backlash acceleration
# MRES Motor step size (EGU)
# PREC Display precision number of decimal places
# DHLM Dial high travel limit (EGU)

View File

@@ -35,4 +35,5 @@ iocInit
# This IOC does not use save/restore, so set values of some PVs
dbpf("DSM:m0.RTRY", "0")
dbpf("DSM:m0.TWV", "0.1")
dbpf("DSM:m0.VMAX", "0.625")
dbpf("DSM:m0.VMAX", "1.0")
dbpf("DSM:m0.HVEL", "1.0")

View File

@@ -147,32 +147,40 @@ iocInit
# This IOC does not use save/restore, so set values of some PVs
dbpf("DSM:m0.RTRY", "0")
dbpf("DSM:m0.TWV", "0.1")
dbpf("DSM:m0.VMAX", "0.625")
dbpf("DSM:m0.VMAX", "1.0")
dbpf("DSM:m0.HVEL", "1.0")
dbpf("DSM:m1.RTRY", "0")
dbpf("DSM:m1.TWV", "0.1")
dbpf("DSM:m1.VMAX", "0.625")
dbpf("DSM:m1.VMAX", "1.0")
dbpf("DSM:m1.HVEL", "1.0")
dbpf("DSM:m2.RTRY", "0")
dbpf("DSM:m2.TWV", "0.1")
dbpf("DSM:m2.VMAX", "0.625")
dbpf("DSM:m2.VMAX", "1.0")
dbpf("DSM:m2.HVEL", "1.0")
dbpf("DSM:m3.RTRY", "0")
dbpf("DSM:m3.TWV", "0.1")
dbpf("DSM:m3.VMAX", "0.625")
dbpf("DSM:m3.VMAX", "1.0")
dbpf("DSM:m3.HVEL", "1.0")
dbpf("DSM:m4.RTRY", "0")
dbpf("DSM:m4.TWV", "0.1")
dbpf("DSM:m4.VMAX", "0.625")
dbpf("DSM:m4.VMAX", "1.0")
dbpf("DSM:m4.HVEL", "1.0")
dbpf("DSM:m5.RTRY", "0")
dbpf("DSM:m5.TWV", "0.1")
dbpf("DSM:m5.VMAX", "0.625")
dbpf("DSM:m5.VMAX", "1.0")
dbpf("DSM:m5.HVEL", "1.0")
dbpf("DSM:m6.RTRY", "0")
dbpf("DSM:m6.TWV", "0.1")
dbpf("DSM:m6.VMAX", "0.625")
dbpf("DSM:m6.VMAX", "1.0")
dbpf("DSM:m6.HVEL", "1.0")
dbpf("DSM:m7.RTRY", "0")
dbpf("DSM:m7.TWV", "0.1")
dbpf("DSM:m7.VMAX", "0.625")
dbpf("DSM:m7.VMAX", "1.0")
dbpf("DSM:m7.HVEL", "1.0")