|
DMD0517 CTDYNVEL - CTRIO Run Dynamic Velocity Mode |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The CTRIO Run Dynamic Velocity Mode (CTDYNVEL) instruction is used to load and run one of the pre-configured Dynamic Velocity Profiles in the System Configuration for the CTRIO module and put the Pulse Output Device into the Dynamic Velocity Mode, allowing successive velocities to be easily commanded. Once in Dynamic Velocity Mode, velocities are commanded by simply changing the Frequency value. The velocities will execute using the parameters defined by the loaded pulse profile.
The red triangle in the upper left corner indicates the CTRIO Run Dynamic Velocity Mode (CTDYNVEL) is a Fully Asynchronous instruction.
Note: The CTDYNVEL instruction can be used with both the CTRIO and CTRIO2 modules.
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Inputs:The first input (E/R) in the Enable / Reset input. When this input logic is ON the Pulse Output Device is placed in the "Dynamic Velocity Mode", the specified Dynamic Velocity File Number will be loaded, the current position value will be set to 0 (e.g. .OutputPosition = 0) and the Output will be enabled (.OutputEnabled = ON).
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Parameters:Note: Use the F9 key (Element Browser) or Down-Arrow key (Auto-Complete) at any time to see a complete list of the memory locations that are valid in the current field of the instruction.
Part of the configuration for a device is assigning a name to the device. It is that name which will show up in the Pulse Output Device selection drop-down menu. For more information on configuring CTRIO devices go to the Module Configuration Section under System Configuration.
Note: no devices available - indicates that there are no CTRIO Devices that have been pre-configured to perform this instruction.
Note: create module - Selecting this will immediately pull up the System Configuration and allow the creation of a new module (see Module Configuration Section under System Configuration.)
Pulse Output Structure -
Dynamic Velocity File Number
- designates which Dynamic Velocity Profile to Run.
The profile can be specified in one of the following three ways:
Frequency - specifies the Frequency for the Dynamic Velocity Profile. This can be any positive or negative constant value in the range of 0 to 25000 for the CTRIO, or the range of 0 to 250000 for the CTRIO2, or any readable numeric location.
On Success - designates which of the following actions to take if the CTRIO Run Dynamic Velocity Mode operation is successful.
Note: On Success is not indicated upon the every Frequency value change. While the E/R (Enable / Reset) input is ON, the Pulse Output Device is considered in the "Dynamic Velocity Mode". When the E/R (Enable / Reset) input goes OFF, this is when On Success will be indicated.
On Error - designates which
of the following two actions to take if the CTRIO Run Dynamic Velocity
Mode operation is unsuccessful. For example if the specified Dynamic Velocity
Profile is missing, or the specified Profile number is the wrong type
for a Pulse Output.
Note: any time the On Error condition occurs, the CTRIO generates an Error Code that can be read in the <Module Name>.ErrorCode (Module Name is the name assigned to the CTRIO in the Module Configuration). The List of Error Code values (in decimal) follows:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Status Display:The Status display of the CTRIO Run Dynamic Velocity Mode (CTDYNVEL) instruction shows:
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
CTRIO Structure Field Care-Abouts:The following is a list of the"dot" fields of the CTRIO structure that are programmatically used with the CTRIO Run Dynamic Velocity Mode (CTDYNVEL) instruction. To see a complete listing of all CTRIO structures and members, goto the Project Browser --> Configuration --> Memory --> I/O --> Specialty.
COLOR KEY Blue: CTRIO Input Maroon: CTRIO Output Black: CTRIO Module Silver: Not used for this instruction
Note: The red "x" is the digit 0, 1, 2, or 3.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
See Also:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Example 1 of 2: |
Description of a Typical CTRIO Run Dynamic Velocity Mode (CTDYNVEL) Stage Diagram:
The Velocity stage puts the CTRIO pulse output in the Dynamic Velocity mode. Once this is complete (OutEn = ON) then the RunVel stage is enabled (not transitioned to). The reason for this is because the Velocity stage must remain enabled to keep the CTRIO pulse output in the Dynamic Velocity mode.
In the RunVel stage exists ladder logic that would write any number of velocity values as needed for the process. When the last velocity has finished, then Done comes on and it transitions to the Stop stage where the Program code block is exited.
|
Description of a Typical CTRIO Run Dynamic Velocity Mode (CTDYNVEL) Stage Ladder:
This example presupposes the existence of the following System Configuration for the CTRIO (PLC --> System Configuration --> Module Configuration(s) --> CTRIO_000 -->):
Velocity is the initial stage. This stage must remain enabled during the entire velocity process. Instead of transitioning to the next stage (RunVel), the next stage will merely be enabled. When VelocityEnable is turned ON the following happens:
The VelocityEnable must be reset OFF when all velocities are completed.
Note: Turning VelocityEnable bit OFF will cause the CTRIO output to abruptly stop. Thus it is usually a good idea to write a zero (0) to the CTDYNVEL's Frequency parameter (Speed) before turning VelocityEnable bit OFF.
The CTDYNVEL's SUS (Suspend) is controlled by the Suspend bit. This bit must remain OFF for any given velocity. Turning this bit ON will cause the CTRIO's output to immediately stop. Turning it back OFF will cause the CTRIO's output to abruptly restart.
Once the $CTRIO_000_Out0.OutputEnabled bit has come ON the RunVel stage is enabled (not transitioned to).
In the RunVel stage should exist the ladder logic (not shown here) that would write various velocity values to the Speed variable as the process requires (e.g. using a MOVE instruction to move a value from NewValue to Speed as shown). As soon as a new value is written to the Speed variable, the CTRIO will accelerate/decelerate to the new velocity. When the process is deemed as complete RunVel stage should reset VelocityEnable bit OFF (as shown) observing the cautions in the above Note.
Turning VelocityEnable bit OFF causes the following to happen:
The Stop stage merely exits this Program code block. |
|
|
Example 2 of 2:
|
|
|