drive speed

8/13/2019 drive speed

1/100


2/100

Important User Information

Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1 available from your local Rockwell Automation sales officeor online at http://rockwellautomation.com/literature) describes some important differences between solid state equipment and hard-wired

electromechanical devices. Because of this difference, and also because of the wide variety of uses for solid state equipment, all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable.

In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or applicationof this equipment.

The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements as-sociated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the ex-

amples and diagrams.

No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described inthis manual.

Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited.

Throughout this manual, when necessary, we use notes to make you aware of safety considerations.

Allen-Bradley, Rockwell Automation, and TechConnect are trademarks of Rockwell Automation, Inc.

Trademarks not belonging to Rockwell Automation, Plant PAx Process Automation System, and TechConnect are property of their respective companies.

WARNING

Identifies information about practices or circumstances that can cause an explosion in a

hazardous environment, which may lead to personal injury or death, property damage, oreconomic loss.

IMPORTANT Identifies information that is critical for successful application and understanding of the product.

ATTENTIONIdentifies information about practices or circumstances that can lead to personal injury or death,

property damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and

recognize the consequence.

SHOCK HAZARD Labels may be on or inside the equipment, for example, a drive or motor, to alert people that

dangerous voltage may be present.

BURN HAZARD Labels may be on or inside the equipment, for example, a drive or motor, to alert people that

surfaces may reach dangerous temperatures.


3/100

iiiPublication SYSLIB-RM016C-EN-E - October 2011 iii

Summary of Changes

Introduction This release of this document is updated throughout for version 2.0 of theVariable Speed Drive (P_VSD) Add-On Instruction and Graphics. Please referto the Release Notes that are disrupted with version 2.0 in the Library.

Updated Information This document contains the following changes:

Change: See:

Version 2.0 of instruction All


4/100

iv Publication SYSLIB-RM016C-EN-E - October 2011

Summary of Changes

Notes:


5/100

vPublication SYSLIB-RM016C-EN-E - October 2011 v

Table of Contents

Preface Use of this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiConventions and Related Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Set and Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiEdge and Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiRelay Ladder Rung Condition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixPre-Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xFunction Block States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiEntering Text in FactoryTalk View SE. . . . . . . . . . . . . . . . . . . . . . xii

Chapter 1

Overview Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Primary Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Revision Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 2

Configuration Options Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 3

Instruction Data Reference Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Inputs (Inp_) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Output (Out_) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Configurations (Cfg_) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Program Settings (PSet_) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Program Commands (PCmd_) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Mode Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Alarm Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Operator Settings, Maintenance Settings, Other Settings(OSet_, MSet_, Set_) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Operator / Maintenance Setting Readies . . . . . . . . . . . . . . . . . . . . 35Operator Commands, Maintenance Commands, Command Readies(OCmd_, MCmd_, Rdy_) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Device Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Mode Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Alarm Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Device Command Readies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Mode Command Readies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Alarm Command Readies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Values (Val_) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Status (Sts_) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Device Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Mode Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Alarm Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47


6/100

vi Publication SYSLIB-RM016C-EN-E - October 2011

Table of Contents

Chapter 4

HMI Reference Graphic Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51State Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Mode Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Alarm Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Using Graphics Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Operator Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Alarms Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Maintenance Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Engineering Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Trends Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Alarm Configuration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Variable Speed Drive Faceplate Help . . . . . . . . . . . . . . . . . . . . . . . 85


7/100

viiPublication SYSLIB-RM016C-EN-E - October 2011 vii

Preface

Use of this Document This document provides a programmer with details on the P_VSD instructionfor a Logix-based controller. You should already be familiar with how theLogix-based controller stores and processes data.

Novice programmers should read all the details about an instruction beforeusing the instruction. Experienced programmers can refer to the instructioninformation to verify details.

Conventions and RelatedTerms

Set and Clear

This manual uses set and clear to define the status of bits (booleans) and values(non-booleans):

This term: Means:

Set The bit is set to 1 (ON)A value is set to any non-zero number

Clear The bit is cleared to 0 (OFF)All the bits in a value are cleared to 0


8/100

viii Publication SYSLIB-RM016C-EN-E - October 2011

Preface

Edge and Level

This manual uses Edge and Level to describe how bit (BOOL) Commands,Settings, Configurations, and Inputs to this instruction are sent by other logic

and processed by this instruction.

Send/Receive Method: Description:

Edge Action is triggered by rising edge transition of input (0-1)

Separate inputs are provided for complementary functions(such as enable and disable)

Sending logic SETS the bit (writes a 1) to initiate theaction; this instruction CLEARS the bit (to 0) immediately,then acts on the request, if possible

Ladder Diagram (LD): use conditioned OTL (Latch) to send

Structured Text (ST): use conditional assignment [if

(condition) then bit:=1;] to send Function Block Diagram (FBD): OREF writes a 1 or 0 every

scan, should use Level, not Edge

Edge-triggering allows multiple senders per Command,Setting, Configuration, or Input (many-to-one relationship).

Level Action (enable) is triggered by input being at a level ( in astate, usually 1)

Opposite action (disable) is triggered by input being inopposite state (0)

Sending logic SETS the bit (writes a 1) or CLEARS the bit(writes a 0); this instruction does not change the bit

LD: use OTE (Energize) to send

ST: use unconditional assignment[bit:= expression_resulting_in_1_or_0;] orif-then-else logic [if (condition) then bit:= 1; else bit:= 0;]

FBD: use OREF to the input bit

Level triggering allows only one sender to drive each Levelinput on the instruction (one-to-one relationship restriction).

IMPORTANT All Operator Commands (OCmd_) and Maintenance Commands(MCmd_) are Edge triggered. The HMI Graphic Symbol orFaceplate SETS (writes a 1 to) each Command bit and theInstruction CLEARS (writes a 0 to) the Command bit, then

performs the function, if possible.


9/100

Publication SYSLIB-RM016C-EN-E - October 2011 ix

Preface

Relay Ladder Rung Condition

The controller evaluates ladder instructions based on the rung conditionpreceding the instruction (rung-in condition). Based on the rung-in condition

and the instruction, the controller sets the rung condition following theinstruction (rung-out condition), which in turn, affects any subsequentinstruction.

If the rung-in condition to an input instruction is true, the controller evaluatesthe instruction and sets the rung-out condition based on the results of theinstruction. If the instruction evaluates to true, the rung-out condition is true;if the instruction evaluates to false, the rung-out condition is false.

IMPORTANT This instruction has Program Commands (PCmd_) which areselectable as Edge or Level, depending on the ConfigurationParameter Cfg_PCmdClear. If Cfg_PCmdClear is 1 (the default),all Program Commands are CLEARED when received (edge). If

Cfg_PCmdClear is 0, Program Commands as noted in theInstruction Data Referencebecome Level triggered, andopposite functions are triggered by the primary ProgramCommand being CLEARED to 0.

IMPORTANT The rung-in condition is reflected in the EnableIn parameter anddetermines how the system performs each Process Add-OnInstruction. If the EnableIn signal is TRUE, the system performsthe instructions main logic routine. Conversely, if the EnableInsignal is FALSE, the system performs the instructionsEnableInFalse routine.

The instructions main logic routine sets/clears the EnableOutparameter, which then determines the rung-out condition. TheEnableInFalse routine cannot set the EnableOut parameter. Ifthe rung-in condition is FALSE, then the EnableOut parameterand the rung-out condition will also be FALSE.


10/100

x Publication SYSLIB-RM016C-EN-E - October 2011

Preface

Pre-Scan

During the transition into RUN, the controller performs a pre-scan before thefirst logic scan. Pre-scan is a special scan of all routines in the controller. The

controller scans all main routines and subroutines during pre-scan, but ignoresjumps that could skip the execution of instructions. The controller executes allFOR loops and subroutine calls. If a subroutine is called more than once, it isexecuted each time it is called. The controller uses pre-scan instructions toreset non-retentive data values.

During pre-scan, input values are not current and outputs are not written. Thefollowing conditions generate pre-scan:

toggle from Program to Run mode.

automatically enter Run mode from a power-up condition.

Pre-scan does not occur for a program when:

the program becomes scheduled while the controller is running.

the program is unscheduled when the controller enters Run mode.

IMPORTANT The pre-scan process performs the Process Add-On Instructionslogic routine as all FALSE and then performs its pre-scanroutine as TRUE.


11/100

Publication SYSLIB-RM016C-EN-E - October 2011 xi

Preface

Function Block States

The controller evaluates function block instructions based on the state ofdifferent conditions.

Every function block instruction also includes EnableIn and EnableOutparameters.

If the EnableIn parameter is not wired, the instruction always executes asnormal and EnableIn remains set. If you clear EnableIn, it changes to set thenext time the instruction executes.

Possible Condition: Description:

Pre-scan Pre-scan for function block routines is the same as for relayladder routines. The only difference is that the Enablelnparameter for each function block instruction is cleared duringpre-scan.

Instruction first scan Instruction first scan refers to the first time an instruction isexecuted after pre-scan. The controller uses instruction firstscan to read current inputs and determine the appropriatestate to be in.

Instruction first run Instruction first run refers to the first time the instructionexecutes with a new instance of a data structure. The

controller uses instruction first run to generate coefficientsand other data stores that do not change for a function blockafter initial download.

IMPORTANT When programming in function block, restrict the rangeof engineering units to 1015because internal floatingpoint calculations are done using single precision floatingpoint. Engineering units outside of this range may result ina loss of accuracy if results approach the limitations of

single precision floating point (1038).


12/100

xii Publication SYSLIB-RM016C-EN-E - October 2011

Preface

Entering Text in FactoryTalk View SE

When entering data into String Input fields in FactoryTalk View SE, the data isnot saved to the tag until the user presses the Enter key. When the Input Field

is enabled, its border changes based on the state of the input:

When the Input Field is Active (the cursor is in the field), the Input Field border is a

solid line.

If the user modifies the data in the input field and moves to a different field without

pressing the Enter key, the border remains a solid line indicating that the data has not

been saved to the tag.

If the data in the Input Field has not changed or has been written to the controller

tag, the border is a dashed line.

EXAMPLE

EXAMPLE

EXAMPLE


13/100

1Publication SYSLIB-RM016C-EN-E - October 2011 1

Chapter1

Overview

The P_VSD Variable Speed Drive object is used to operate one variable speedmotor by using a Drive (AC variable frequency or DC) in a variety of Modes,monitoring for fault conditions.

Use when:

You need to operate a motor connected to a variable-speed drive. Thedrive can be an AC (variable frequency) or DC drive, and can beconnected via an I/O or control network (intelligent drive) or viahardwired analog and discrete I/O.

This instruction is designed to work with all currently-available and manylegacy Allen-Bradley drives, including Bulletin 1336, Bulletin 1395, PowerFlex4 / 40 / 70 / 700 / 7000 and PowerFlex DC. This instruction will also workwith drives and other variable-speed motor control products via discrete I/Ofor the start/stop/running signals and analog I/O for the speed reference andspeed feedback signals.

Do NOT use when:

You need to operate a single-speed motor (running / stopped only). Use

the P_Motor Instruction instead. You need to operate a two-speed motor (fast / slow / stopped only).

Use the P_Motor2Spd Instruction instead.

You need to operate a simple reversing motor (forward / reverse /stopped only). Use the P_MotorRev Instruction instead.

You need to operate a motor with multiple discrete speeds. You willneed specific logic for this motor. The P_VSD Instruction is designedfor motors with continuously variable (analog) speed, not multiplediscrete speed selections. You may find the P_D4SD or P_nPosInstruction suitable for these motors.


14/100

2 Publication SYSLIB-RM016C-EN-E - October 2011

Chapter 1 Overview

Functional Description The P_VSD Instruction includes an Add-On Instruction for use withVersion 18 or later of RSLogix 5000 software and Logix controllers, plus amulti-tabbed Faceplate and several graphic symbols for use in building displayson Factory Talk View SE 6.0 or later.

Primary Operations The primary operations of the Variable Speed Drive Add-On Instruction are:

Provide for ownership of the Drive through the standard P_ModeAdd-On Instruction and Modes. Modes of operation are describedbelow.

Provide the ability to Start and Stop the Drive and Motor, control thedrive speed (via Speed Reference), and monitor the Drive run status andspeed feedback to verify the Drive is running or stopped. Providealarms and Drive shutdown for Fail to Start and Fail to Stop if thefeedback does not follow the commanded state within a configuredamount of time. Whether or not the Drive HAS run feedback can beconfigured at the Engineer level. Whether or not to USE the runfeedback can be configured at the Maintenance level.


15/100

Publication SYSLIB-RM016C-EN-E - October 2011 3

Overview Chapter1

Provide scaling of the Speed Reference from user (engineering) units,such as RPM, to drive units, such as 32767 = Max Freq. Provide scalingof the Speed Feedback from drive units to user (engineering) units anddisplay with suitable units of measure text.

Provide optional setting (by Program or Operator) of an OutputDatalink and scaling of this setting from engineering units (such as ramptime in seconds) to drive raw units. Provide optional reading of an InputDatalink and scaling of this value from drive raw units to engineeringunits (such as amperes) for display on the HMI.

Provide for reading from the drive and displaying a Fault Code.

Provide indication of Accelerating, Decelerating, At Speed and Warningor Alarm status as received from the drive.

Provide optional capability to support reversing drives, with commandsfor Forward and Reverse rotation and display of actual rotationdirection.

Provide an input and Alarm for Drive Fault condition and an output tosend a drive fault Reset to the drive. Provide a configurable time to pulsethe drive fault Reset output when a reset command is received.

Provide the above inputs and outputs formatted to work with any drivescommonly used in the Process industries, including, but not limited to,1336 Plus II, 1395, PowerFlex 4 / 40 / 70 / 700 / 7000 and PowerFlexDC, in a form that still allows for use with non-A-B drives via hardwired

I/O.

Provide for Permissives (Bypassable and Non-Bypassable) which areconditions that allow the Drive to start, and Interlocks (Bypassable andNon-Bypassable) which are conditions that stop the Drive as well asprevent starting. Provide an Alarm when an Interlock stops the Drive.Provide Maintenance the capability to bypass the BypassablePermissives and Interlocks.

Provide Maintenance the capability to Disable (soft lock out) the Drive.

IMPORTANT

This capability is not a substitute for hard lockout/target (LOTO) procedures.

Monitor an I/O Fault input, Alarm on an I/O Fault.

The I/O Fault condition can optionally de-energize the outputs to thedrive, requiring a reset.


16/100


Chapter 1 Overview

In Override mode, provide an Override State input which determineswhether the Override is to run or stop the Drive (default = stop) and, ifthe Drive is to run, an Override Speed Reference and direction. SeeModes below for more information on Override.

Provide a Simulation capability, in which the outputs to the Drive arekept de-energized, but the object can be manipulated as if a workingDrive were present, including a basic ramp-up of speed feedback valueon starting and ramp-down on stopping. The simulatedramp-up-to-speed time is configurable. This capability is often used foractivities such as system testing and operator training.

Operating Modes The following standard Modes, implemented using the P_Mode Add-OnInstruction, are used by the Variable Speed Drive Add-On Instruction:

Some drive capabilities can be kept by (reserved for) the operator or programlogic, independent of the Program or Operator Mode selection. See Chapter 2,Configuration Options, for details.

Refer to the Process Add-On Instructions and Graphics: Mode (P_Mode)Reference Manual, publication SYSLIB-RM005, for more information.

Mode Description

Operator The Operator starts and stops the Drive and sets the Drive speedreference (and Output Datalink, if used) using the HMI Faceplate.

Program Logic outside the P_VSD instruction starts and stops the Driveand sets the speed reference and Output Datalink using ProgramCommands (PCmd_Start, PCmd_Stop) and Program Settings(PSet_SpeedRef, PSet_OutDatalink).

Override Priority logic outside the P_VSD instruction determines whetherto run or stop the Drive, and if to run, at what speed. (The defaultis to stop the Drive.) If so configured, Bypassable Interlocks arebypassed in Override Mode.

Maintenance Maintenance personnel have control of the Drive using the HMIFaceplate and it is not available for normal operation byoperators or program logic; bypassable permissives andinterlocks are bypassed, and fail-to-start and fail-to-stopchecking is not performed.

Hand Logic, usually hardwired, has superseded P_VSD control of theDrive; the P_VSD instruction tracks the state and speed of theDrive for bumpless transfer back to one of the other modes.


17/100


Overview Chapter1

Alarms The following Alarms, implemented using the P_Alarm Add-On Instruction,are used by the Variable Speed Drive Add-On Instruction:

The Fail to Start and Fail to Stop Alarms have a configurable delay to allow therun feedback time to align with the commanded output (time for the Drive toactually start or stop).

Refer to the Process Add-On Instructions and Graphics: Alarm (P_Alarm)Reference Manual, publication SYSLIB-RM002, for more information.

Execution The following table explains the handling of instruction execution conditions.

Refer to Logix5000 Controllers Add-On Instructions Programming Manual,publication 1756-PM010, for more information.

Alarm Description

Fail to Start Raised if the Drive has and is using run feedback, an attempt ismade to Start the Drive, and the run feedback does not indicate theDrive running within the configured time.

Fail to Stop Raised if the Drive has and is using run feedback, an attempt ismade to Stop the Drive, and the run feedback does not indicate theDrive stopped within the configured time.

I/O Fault Raised if the Inp_IOFault input is true.

Drive Fault Raised if the Inp_Faulted input is true. Enables display of the DriveFault Code.

Interlock Trip Raised if the Drive is running and an Interlock causes it to stop. IfInterlocks are not bypassed, a Non-Bypassable Interlock not OK or aBypassable Interlock not OK will stop the Drive. If Interlocks are

bypassed, only a Non-Bypassable Interlock not OK will stop theDrive.

Condition Description

EnableIn False (False Rung) Processing for EnableIn False (False Rung) ishandled the same as if the Drive wereDisabled by Command. The Drive outputsare de-energized and the Drive is shown asDisabled on the HMI.

Powerup (Pre-Scan, First Scan) Processing of Modes and Alarms onPrescan and Powerup is handled by theembedded P_Mode and P_Alarm Add-OnInstructions - refer to their specifications for

details.

On Powerup, the Drive is treated as if it hadbeen Commanded to Stop.

Postscan (SFC Transition) No SFC Postscan logic is provided.
http://literature.rockwellautomation.com/idc/groups/literature/documents/pm/1756-pm010_-en-p.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/pm/1756-pm010_-en-p.pdf


18/100


Chapter 1 Overview

Revision Compatibility The P_VSD Add-On Instruction in RSLogix 5000 software and the Faceplatein FactoryTalk View software are marked with revision information as shownin the following table.

The Instruction and Faceplate are compatible if they have the same Major andMinor Revision numbers.

The Major Revision is the first number, before the period.

The Minor Revision is the second number, after the period and before thehyphen or space.

Information after the hyphen or space indicates the Tweak Revision. TheInstruction and Faceplate do not have to have the same Tweak Revision to becompatible.

In the table above, the Add-On Instruction and Faceplate shown arecompatible because they have the same Major.Minor (1.1).

Component Example

The Add-On Instruction in RSLogix 5000 hasrevision information visible when theinstruction is selected in the ControllerOrganizer.

The Faceplate in FactoryTalk View hasrevision information visible when thepointer is paused just inside the lowerleft-hand corner of the Faceplate when

called up on a running HMI Client.


19/100


Chapter2

Configuration Options

Configuration Parameters Enter the appropriate values from the following table into the P_VSDInstructions configuration parameters to configure it for your application.

Use the HMI Faceplate or the RSLogix 5000 Tag Monitor function to set theapplicable configuration parameter(s).

Parameter Default FaceplateTab Location

Usage Associated Parameters

Cfg_Desc VariableSpeed Drive

Engineering These Local Tags determine the textdisplayed on the various GraphicSymbols and Faceplates for:

None

Description

Cfg_Label Motor SpeedControl

Label (if used)

Cfg_Tag P_VSD Tagname

Cfg_FwdText FORWARD Forward direction

Cfg_RevText REVERSE Reverse direction

Cfg_InpDatalinkEU Empty/null Input Datalink Engineering Units (unitsof measure)

Cfg_InpDatalinkLabel Empty/null Input Datalink Label

Cfg_OutDatalinkEU Empty/null Output Datalink Engineering Units(units of measure)

Cfg_OutDatalinkLabel Empty/null Output Datalink Label

Cfg_SpeedFdbkEU Hz Speed Feedback Engineering Units(units of measure)

Cfg_SpeedRefEU Hz Speed Reference Engineering Units(units of measure)


20/100


Chapter 2 Configuration Options

Cfg_DriveFaultAckReqd ON AlarmConfiguration

When this parameter is:

ON, the Acknowledge (Ack) bit iscleared when an alarm occurs,indicating an unacknowledgedalarm. An Acknowledge Commandis required to acknowledge thealarm (set the Ack bit).

OFF, the Acknowledge (Ack) bit isset when an alarm occurs,indicating an acknowledged alarm.No Acknowledge Command isrequired.

Ack_DriveFault

DriveFault.OCmd_Ack

Cfg_FailToStartAckReqd ON Ack_FailToStart

PCmd_FailToStartAck

FailToStart.OCmd_Ack

Cfg_FailToStopAckReqd ON Ack_FailToStop

PCmd_FailToStopAck

FailToStop.OCmd_Ack

Cfg_IntlkTripAckReqd ON Ack_IntlkTrip

PCmd_IntlkTripAck

IntlkTrip.OCmd_Ack

Cfg_IOFaultAckReqd ON Ack_IOFault

PCmd_IOFaultAck

IOFault.OCmd_Ack

Cfg_DriveFaultResetReqd OFF AlarmConfiguration


ON, the alarm status is latched ONwhen an alarm occurs. After thealarm condition returns to normal,a Reset is required to clear thealarm status.

IMPORTANT

If the Reset clears the alarm, it alsoacknowledges the alarm.

OFF, the alarm status is set whenan alarm occurs and cleared whenthe alarm condition returns tonormal. No Reset is required.

Inp_Reset

Alm_DriveFault

DriveFault.OCmd_Reset

Cfg_FailToStartResetReqd OFF Alm_FailToStart

FailToStart.OCmd_Reset

Cfg_FailToStopResetReqd OFF Alm_FailToStop

FailToStop.OCmd_Reset

Cfg_IntlkTripResetReqd OFF Alm_IntlkTrip IntlkTrip.OCmd_Reset

Cfg_IOFaultResetReqd OFF Alm_IOFault

IOFault.OCmd_Reset

Cfg_DriveFaultSeverity

Cfg_FailToStartSeverity

Cfg_FailToStopSeverity

Cfg_IntlkTripSeverity

Cfg_IOFaultSeverity

4

4

4

2

4

AlarmConfiguration

These parameters determine theSeverity of each alarm, and thus thecolor of alarm animations for eachalarm.

Valid values are:

1 = Information (blue)

2 = Warning (yellow)

3 = Exception (red)

4 = Fault (magenta)

Val_Notify




21/100


Configuration Options Chapter2

Cfg_FailToStartT 15 sec Engineering If a Start or Jog Command is given tothe drive and drive feedbacks arebeing used, the P_VSD instructionallows this much time for thefeedbacks to show the drive is runningbefore generating a Fail to Start Alarm.

Cfg_HasRunFdbk

Cfg_UseRunFdbk

OCmd_Start

PCmd_Start

Sts_Starting

Alm_FailToStart

Cfg_FailToStopT 15 sec Engineering If a Stop Command is given to thedrive and drive feedbacks are beingused, the P_VSD instruction allowsthis much time for the feedbacks toshow the drive is stopped beforegenerating a Fail to Stop Alarm.

Cfg_HasRunFdbk

Cfg_UseRunFdbk

OCmd_Stop

PCmd_Stop

Sts_Stopping

Alm_FailToStop

Cfg_HasDriveFaultAlm

Cfg_HasFailToStartAlm

Cfg_HasFailToStopAlm

Cfg_HasIntlkTripAlm

Cfg_HasIOFaultAlm

OFF

OFF

OFF

OFF

OFF

AlarmConfiguration

These parameters determine whetherthe corresponding alarm exists andwill be checked, or doesnt exist andwill not be used.


ON, the Alarm exists and will bechecked

OFF, Alarm does not exist and willnot be used

Alm_DriveFault

Alm_FailToStart

Alm_FailToStop

Alm_IntlkTrip

Alm_IOFault

Cfg_HasInpDatalink OFF Engineering Set this parameter:

ON if the drive provides an InputDatalink signal and it is connectedto the Inp_Datalink parameter.

OFF if the Inp_Datalink Parameteris not being used. The InputDatalink items will not bedisplayed on the HMI Faceplate.

Inp_Datalink

Val_InpDatalink Cfg_InpDatalinkEU

Cfg_InpDatalinkEUMax

Cfg_InpDatalinkEUMin

Cfg_InpDatalinkLabel

Cfg_OutDatalinkRawMin

Cfg_OutDatalinkRawMax

Cfg_HasIntlkObj OFF Engineering Set this parameter:

ON if this instruction has a P_Intlkinstruction connected to theInp_IntlkOK and Inp_NBIntlkOKinputs. The Operator Faceplateinterlock indicator becomes apushbutton that navigates to theP_Intlk (Interlocks) Faceplate.

OFF if the interlock inputs are notconnected to a P_Intlk instruction.The Operator Faceplate interlockindicator becomes an indicatoronly.

Inp_IntlkOK

Inp_NBIntlkOK




22/100



Cfg_HasJog OFF Engineering Set this parameter:

ON if you want to be able to Jogthe Drive from the HMI Faceplate.The Out_Jog parameter must besent to the drive.

OFF if the Drive will not be Joggedfrom the HMI Faceplate. The Jogbutton will not be displayed on theFaceplate.

OCmd_Jog

Out_Jog

IMPORTANT

The OCmd_Jog OperatorCommand is LEVEL triggered. TheFaceplate SETS OCmd_Jog toJog the drive and CLEARSOCmd_Jog to stop jogging.

Cfg_HasOutDatalink OFF Engineering Set this parameter:

ON if you want to allow theOperator to enter an OutputDatalink value on the HMI

Faceplate and have it sent to theDrive via the Out_Datalinkparameter.

OFF if the Out_Datalink Parameteris not being used. The OutputDatalink items will not bedisplayed on the HMI Faceplate.

PSet_OutDatalink

OSet_OutDatalink

Val_OutDatalink

Out_Datalink

Cfg_OutDatalinkEU Cfg_OutDatalinkEUMax

Cfg_OutDatalinkEUMin

Cfg_OutDatalinkLabel

Cfg_OutDatalinkMax

Cfg_OutDatalinkMin



Cfg_HasFwdPermObj OFF Engineering Set this parameter:

ON if this instruction has a P_Perm

instruction connected to theInp_FwdPermOK andInp_FwdNBPermOK inputs. TheOperator Faceplate forwardpermissive indicator becomes apushbutton that navigates to theP_Perm (Permissives) Faceplate.

OFF if the forward permissiveinputs are not connected to aP_Perm instruction. The OperatorFaceplate forward permissiveindicator becomes an indicator only

Inp_FwdPermOK

Inp_FwdNBPermOK




23/100



Cfg_HasRevPermObj OFF Engineering Set this parameter:

ON if this instruction has a P_Perminstruction connected to theInp_RevPermOK andInp_RevNBPermOK inputs. TheOperator Faceplate reversepermissive indicator becomes apushbutton that navigates to theP_Perm (Permissives) Faceplate.

OFF if the reverse permissiveinputs are not connected to aP_Perm instruction. The OperatorFaceplate reverse permissiveindicator becomes an indicator only

Inp_FwdPermOK

Inp_FwdNBPermOK

Cfg_HasResInhObj OFF Engineering Set this parameter:

ON if this instruction has aP_ResInh instruction monitoring itsstopped, starting and runningstatus. The Operator FaceplateRestart Inhibit (hourglass)pushbutton that navigates to theP_ResInh (Restart Inhibit)Faceplate becomes visible.

OFF if no Restart Inhibit instructionis associated with this drive. TheRestart Inhibit pushbutton is notdisplayed.

These status parameters areused by the Restart Inhibitinstruction if one is used:

Sts_Starting

Sts_Running

Sts_Stopped

Cfg_HasReverse OFF Engineering Set this parameter:

ON if you want to be able to Run(or Jog) the Drive in the Reversedirection. The Forward and ReverseCommand buttons will bedisplayed and active on the HMIFaceplate, and the ProgramForward and Reverse Commandswill be accepted. The Input andOutput parameters associated withDrive direction must be connectedto/from the drive.

OFF if the Drive will not be Run orJogged in Reverse. The Forwardand Reverse Command buttons willnot be displayed on the Faceplate.

Inp_CommandDir

Inp_ActualDir

Out_Fwd

Out_Rev

OCmd_Fwd

OCmd_Rev

PCmd_Fwd

PCmd_Rev

Sts_CommandDir

Sts_ActualDir

Rdy_Fwd

Rdy_Rev




24/100



Cfg_HasRunFdbk OFF Engineering Set this parameter:

ON if the drive provides a runfeedback signal and the signal isconnected to Inp_Running.

OFF if the drive has no runfeedback to this instruction. Theinstruction will simulate theStarting, Accelerating,Decelerating and Stopping statususing the Cfg_SimFdbkT timeconfiguration.

This configuration identifies whetherthe run feedbacks exist.Cfg_UseRunFdbk determines whetherthe feedbacks are actually used.

Sts_Starting

Sts_Stopping

Cfg_HasRunTimeObj OFF Engineering Set this parameter:

ON if this instruction has aP_RunTime instruction monitoringits starting and running status. TheOperator Faceplate Run Time (hourmeter or odometer) pushbuttonthat navigates to the P_RunTime(Run Time and Starts) Faceplatebecomes visible.

OFF if no P_RunTime instruction isassociated with this drive. The RunTime pushbutton is not displayed.

These status parameters areused by the Run Time and Startsinstruction if one is used:

Sts_Starting

Sts_Running

Cfg_InpDatalinkEUMin 0.0 Engineering These parameters are used for scalingthe Input Datalink received from thedrive from Drive (Raw) Units toEngineering Units.

Check the User Manual for your driveand/or I/O cards to determine thescaling of the Input Datalink sent bythe drive.

IMPORTANT

The Input Datalink is not used ifCfg_HasInpDatalink is 0.

TIP

If you have multiple Input Datalinksfrom your drive, the additionalDatalinks can be scaled and processedby P_AIn Analog Input Add-OnInstructions.

Inp_Datalink

Cfg_InpDatalinkEUMax 409.5 Val_InpDatalink

Cfg_InpDatalinkRawMin 0 Cfg_InpDatalinkEU

Cfg_InpDatalinkRawMax 4095 Cfg_InpDatalinkLabel




25/100



Cfg_MaxJogT 0.0 Maintenance Enter the maximum time (in seconds)for which the Drive may be joggedusing OCmd_Jog.

IMPORTANT

This value is used to stop drive joggingin the case where HMI communicationis lost during a jog.

Cfg_MaxSpdRef 60.0 Maintenance These values limit the SpeedReference Output to the Drive (inengineering units) to the specifiedrange.

IMPORTANT

These limits may be set narrower thanthe Speed Reference scaling limits torestrict the output, or wider than thescaling limits to allow generation ofoutputs outside the normal scaledrange.

OSet_SpeedRef

PSet_SpeedRef

Val_SpeedRef

Cfg_MinSpdRef 0.0

Cfg_OutDatalinkEUMin 0.0 Engineering These parameters are used for scalingthe Output Datalink setting fromEngineering Units to Drive (Raw) Unitsprior to sending to the drive.

Check the User Manual for your driveand/or I/O cards to determine thescaling of the Output Datalink sent tothe drive.

IMPORTANT

The Output Datalink is not used ifCfg_HasOutDatalink is 0.

TIP

If you have multiple Output Datalinks

to your drive, the additional Datalinkscan be scaled and processed byP_AOut Analog Output Add-OnInstructions.

Out_Datalink

OSet_OutDatalink

PSet_OutDatalink

Val_OutDatalink

Cfg_OutDatalinkEU Cfg_OutDatalinkLabel

Cfg_OutDatalinkMax

Cfg_OutDatalinkMin

Cfg_OutDatalinkEUMax 409.5

Cfg_OutDatalinkRawMin 0

Cfg_OutDatalinkRawMax 4095




26/100



Cfg_OutDatalinkMax 100.0 Maintenance These values limit the Output Datalinkvalue sent to the Drive (in engineeringunits) to the specified range.

IMPORTANT

These limits may be set narrower thanthe Output Datalink scaling limits torestrict the output, or wider than thescaling limits to allow generation ofoutputs outside the normal scaledrange.

OSet_OutDatalink

PSet_OutDatalink

Val_OutDatalink

Cfg_OutDatalinkMin 0.0

Cfg_OvrdPermIntlk OFF Engineering Set this parameter:

ON if Override Mode should bypass

the bypassable Permissives andInterlocks when starting andrunning the drive.

OFF if Override Mode should notbypass the bypassable Permissivesand Interlocks when starting andrunning the drive.

IMPORTANT

Override Mode cannot bypass thenon-bypassable Permissives andInterlocks regardless of the setting of

this configuration.

Inp_Ovrd

Inp_OvrdSpeed

Inp_OvrdState

Inp_IntlkOK

Inp_NBIntlkOK

IMPORTANT

If Inp_OvrdState is off andOverride Mode is active, thedrive will be stopped.Permissives are only checkedwhen starting, and Interlocks areonly checked when starting orrunning the drive.

Cfg_OperKeep 2#0000_0000 Engineering Set bits within this 8-bit integer toselect functions to keep underOperator control even when thisinstruction is in Program Mode. Clearbits to leave the correspondingfunctions under control of theinstruction Mode.

Bit..0: Speed Reference

Bit .1: Start / Stop Commands

Bit .2: Forward / Commands

Bit .3: Output Datalink

TIP

A function cannot be reserved forOperator using Cfg_OperKeep and alsobe reserved for Program usingCfg_ProgKeep. And at least onefunction must be not kept (remainunder control of the Instruction Mode.)

OSet_SpeedRef

OCmd_Start

OCmd_Stop

OCmd_Jog

OCmd_Fwd

OCmd_Rev

OSet_OutDatalink

Err_Keep




27/100



Cfg_ProgKeep 2#0000_0000 Engineering Set bits within this 8-bit integer toselect functions to keep under Programcontrol even when this instruction is inOperator Mode. Clear bits to leave thecorresponding functions under controlof the instruction Mode.

Bit .0: Speed Reference

Bit..1: Start / Stop Commands

Bit .2: Forward / Commands

Bit .3: Output Datalink

TIP

A function cannot be reserved for

Operator using Cfg_OperKeep and alsobe reserved for Program usingCfg_ProgKeep. And at least onefunction must be not kept (remainunder control of the Instruction Mode.)

PSet_SpeedRef

OCmd_Start

OCmd_Stop

OCmd_Jog

OCmd_Fwd

OCmd_Rev

PSet_OutDatalink

Err_Keep

Cfg_PCmdClear ON Engineering Set this parameter:

ON to use Edge-triggered ProgramCommands.

OFF to use Level-triggered ProgramCommands.

See the Edge and Levelsection in thePreface for more information.

The Cfg_PCmdClear parameterconfigures all ProgramCommands (PCmd_)for eitherLevel or Edge triggering.

Cfg_ProgDefault OFF When this parameter is:

ON, the Mode defaults to Programif no Mode is being requested.

OFF, the Mode defaults to Operatorif no Mode is being requested.

IMPORTANT

Changing this parameter online maycause unintended mode changes.

Val_Mode

Sts_Prog

Sts_Oper

Cfg_OCmdResets OFF When this parameter is:

ON, latched alarms may be clearedand latched shed faults (Fail toStart, I/O Fault) can be reset byissuing an Operator Start, Stop orJog command (in Operator Modeonly)

OFF, the latched alarms and shedfaults must be reset by a ResetCommand (Program or Operator) orthe Inp_Reset input.

OCmd_Start

OCmd_Stop

OCmd_Jog




28/100



Cfg_ShedOnFailToStart OFF When this parameter is:

ON, if the motor fails to start, a Failto Start status and alarm areraised, the start is cancelled and areset is required to try anotherstart.

OFF, if the motor fails to start, onlythe Fail to Start status and alarmare raised. The outputs are still setso the instruction keeps trying tostart the motor.

Sts_FailToStart

Alm_FailToStart

Cfg_ShedOnIOFault OFF When this parameter is:

ON, if an I/O Fault is detected, anI/O Fault status and alarm areraised, the motor is stopped and areset is required to try anotherstart.

OFF, if an I/O Fault is detected, onlythe I/O Fault status and alarm areraised. The instruction does notchange the state of the motor.

Sts_IOFault

Alm_IOFault

Cfg_SimScaleEU OFF When this parameter is:

ON, if the drive is being simulated,the speed feedback is simulated bySCALING the speed reference fromreference engineering units tofeedback engineering units.

OFF, if the drive is being simulated,the speed feedback is simulated byCOPYING the speed referencevalue directly to the speedfeedback without scaling. Thissetting is superseded by the settingof Cfg_SimScaleRaw.

Cfg_SpeedRefEUMin,

Cfg_SpeedRefEUMax

Cfg_SpeedFdbkEUMin

Cfg_SpeedFdbkEUMax

Cfg_SimScaleRaw OFF When this parameter is:

ON, if the drive is being simulated,the speed feedback is simulated bySCALING the speed reference fromengineering units to raw units,copying the raw reference to theraw feedback, the scaling from rawfeedback unit to feedbackengineering units.

OFF, if the drive is being simulated,the speed feedback simulation isdetermined by the setting ofCfg_SimScaleEU.

Cfg_SpeedRefRawMin

Cfg_InpDatalinkRawMax

Cfg_SpeedRefEUMin,

Cfg_SpeedRefEUMax

Cfg_SpeedFdbkEUMin

Cfg_SpeedFdbkEUMax

Cfg_SpeedFdbkEUMin

Cfg_SpeedFdbkEUMax




29/100



Cfg_ResetPulseT 2 sec Maintenance The output Out_ClearFault is held ONfor at least this much time when aReset Command is received or theinput Inp_Reset is asserted, triggeringa Drive Fault Reset).

IMPORTANT

If Inp_Reset is held ON for longer thanCfg_MinHoldTime, Out_ClearFault willbe held on as long as Inp_Reset istrue.

The Out_ClearFault Output must beconnected to the Drives Clear Fault orFault Reset input.

The Reset Pulse Time ensures theDrive sees the Clear Fault Output forone or more I/O scans.

Inp_Faulted

Alm_DriveFault

Inp_Reset

PCmd_Reset

Out_ClearFault

Cfg_SetTrack ON Maintenance When this parameter is:

ON, Operator Settings track theProgram Settings when the Modeis Program, and Program Settingstrack the Operator Settings whenthe Mode is Operator. Transitionbetween Modes is bumpless.

OFF, Operator Settings and ProgramSettings are not modified by thisinstruction and retain their valuesregardless of Program or OperatorMode. When the mode is changed,the value of the output may bump,say from the Program-set value tothe Operator-set value.

Out_SpeedRef

PSet_SpeedRef

Val_SpeedRef

OSet_OutDatalink

PSet_OutDatalink

Val_OutDatalink




30/100



Cfg_SetTrackOvrdHand OFF Maintenance When this parameter is:

ON, Operator and Program CVSettings track the Tieback CV(Inp_Tieback) when the Mode isHand, and track the Override CV(Inp_OvrdCV) when the Mode isOverride.

OFF, Operator Settings and ProgramSettings are not modified by thisinstruction and retain their valueswhen the Mode is Hand orOverride. When the mode ischanged back to Operator orProgram, the value of the outputmay bump, say from the

Override-set value to theOperator-set value.

Inp_Hand

Inp_Ovrd

Inp_OvrdSpeed

OSet_SpeedRef

PSet_SpeedRef

Val_SpeedRef

IMPORTANT

The Output Datalink setting(OSet_OutDatalink,PSet_OutDatalink) is not affectedby Hand or Override Modes. It isonly affected by the underlying

Program / Operator selection.

See the P_Mode Instructiondocumentation for moreinformation.

Cfg_SimRampT 10 sec Engineering This parameter determines theacceleration rate (rate to ramp up theSpeed Feedback value) when startingthe drive, and deceleration rate (rate toramp down the Speed Feedback value)when stopping the drive when thedrive is being Simulated (Inp_Sim = 1)or when the drive does not have or isnot using Run Feedback. The Ramp

Time is the time to accelerate fromzero speed to the scaled maximumspeed, or decelerate from the scaledmaximum speed to zero speed.

The default value of 10 seconds meansthe drive shows an Acceleratingstatus for up to 10 seconds beforeshowing At Speed when starting insimulation, and shows aDecelerating status for up to 10seconds before showing Stoppedwhen stopping in simulation.

Inp_Sim

Val_SpeedRef

Val_SpeedFdbk

IMPORTANT

If Cfg_SimFdbkT is set greaterthan Cfg_FailToStartT, the drive

(in simulation) will generate aFail To Start Alarm. See:Cfg_FailToStartT

If Cfg_SimFdbkT is set greaterthan Cfg_FailToStopT, the drive(in simulation) will generate aFail To Stop Alarm. See:Cfg_FailToStopT

Cfg_SpeedFdbkEUMin 0.0 Engineering These parameters are used for scalingthe Speed Feedback received from thedrive from Drive (Raw) Units toEngineering Units.

Check the User Manual for your driveand/or I/O cards to determine thescaling of the Speed Feedback sent bythe drive.

Inp_SpeedFdbk Val_SpeedFdbk

Val_SpeedRef

Inp_OvrdSpeed

Val_SpeedRef

Cfg_SpeedFdbkEUMax 130.0

Cfg_SpeedFdbkRawMin 0

Cfg_SpeedFdbkRawMax 32767




31/100



Cfg_SpeedRefEUMin 0.0 Engineering These parameters are used for scalingthe Speed Reference sent to the drivefrom Engineering Units to Drive (Raw)Units.

Check the User Manual for your driveand/or I/O cards to determine thescaling of the Speed Reference sent tothe drive.

Out_SpeedRef

OSet_SpeedRef

PSet_SpeedRef

Inp_OvrdSpeed

Val_SpeedRef

Cfg_SpeedRefEUMax 130.0

Cfg_SpeedRefRawMin 0

Cfg_SpeedRefRawMax 32767

Cfg_UseRunFdbk OFFf Maintenance Set this parameter:

ON if the run feedback signalsconnected to Inp_Running shouldbe used for Failure to Start andFailure to Stop checking.

OFF to disable the feedbackchecking and disable the Fail toStart and Fail to Stop alarms. Theinstruction will instead simulatethe Starting and Stopping statususing the Cfg_SimFdbkT timeconfiguration.

This configuration identifies whetherthe run feedback should be used.Cfg_HasRunFdbk determines whetherthe feedback exists.

If the feedback does not exist(Cfg_HasRunFdbk=0), the

Cfg_UseRunFdbk is forced to Off.

Inp_Running

Cfg_HasRunFdbk

Sts_Starting

Sts_Stopping

Alm_FailToStart

Alm_FailToStop




32/100



Notes:


33/100


Chapter3

Instruction Data Reference

This chapter describes the P_VSD Instructions public parameters.

The descriptions in the tables below show how these data elements are usedwith the P_VSD Add-On Instruction.

Execution Execution parameters are included with every Add-On Instruction. See theLogix5000 Controllers Add-On Instructions Programming Manual,publication 1756-PM010, for more information on these data elements.

Name:DataType: Usage: Default: Style: Description:

AssociatedConfigurationParameter

EnableIn BOOL Input 1 1 = Normal Scan: control / monitorVariable-Speed Drive

0 = Disabled is asserted; Outputs OFF;Run Status shown but Alarmsdisabled

EnableOut BOOL Output 0 Not manipulated by this instruction;EnableOut state always reflectsEnableIn

Inf_Tab SINT 0 Tab to display (FTView ME)

Inf_Type STRING_16

P_VSD Must contain Add-On Instruction name,used for HMI and Information software

P_VSD BOOL Output 0 Unique Parameter Name forauto-discovery
http://literature.rockwellautomation.com/idc/groups/literature/documents/pm/1756-pm010_-en-p.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/pm/1756-pm010_-en-p.pdf


34/100


Chapter 3 Instruction Data Reference

Inputs(Inp_)

Input data elements are used to connect field inputs from I/O modules orsignals from other objects to the P_VSD instruction. Each Input used shouldhave mapping logic or a function block wire to get the input value from theinput card or other instruction every scan.


AssociatedConfiguration Parameter

Inp_SpeedFdbk INT Input 0 Decimal Speed Feedback in Drive Units(typ. 0-32767 = 0 to max freq.)

Cfg_SpeedFdbkEUMin

Cfg_SpeedFdbkEUMax

Cfg_SpeedRefRawMin

Cfg_SpeedRefRawMax

Inp_FaultCode INT Input 0 Decimal Current Drive Fault Code(enumeration)

Inp_Datalink INT Input 0 Decimal Auxiliary Signal (datalink) Input inDrive (raw) Units

Cfg_HasInpDatalink

Cfg_InpDatalinkEUMin

Inp_Ready BOOL Input 1 Level 1 = Drive is ready to run

Inp_Running BOOL Input 0 Level 1 = Drive is Running (active) Cfg_UseRunFdbk

Inp_CommandDir BOOL Input 1 Level 1 = Drive is commanded Forward0 = Drive is commanded Reverse

Cfg_HasReverse

Inp_ActualDir BOOL Input 1 Level 1 = Drive is running Forward0 = Drive is running Reverse

Cfg_HasReverse

Inp_Accelerating BOOL Input 0 Level 1 = Drive is accelerating

Inp_Decelerating BOOL Input 0 Level 1 = Drive is decelerating

Inp_Alarm BOOL Input 0 Level 1 = Drive has an Alarm Condition(see drive display or manual)

Inp_Faulted BOOL Input 0 Level 1 = Drive has Faulted (see drivedisplay or manual)

Cfg_ResetPulseT

Inp_AtSpeed BOOL Input 0 Level 1 = Drive is at commanded speed

Inp_FwdPermOK BOOL Input 1 Level 1 = Permissives OK, drive can startForward

Cfg_HasFwdPermObj

Cfg_HasRevPermObj

Inp_FwdNBPermOK BOOL Input 1 Level 1 = Non-bypassable PermissivesOK, drive can start Forward

Cfg_HasFwdPermObj

Cfg_HasRevPermObj

Inp_RevPermOK BOOL Input 1 Level 1 = Permissives OK, drive can startReverse

Inp_RevNBPermOK BOOL Input 1 Level 1 = Non-Bypassable Permissives

OK, motor can start Reverse

Inp_IntlkOK BOOL Input 1 Level 1 = Interlocks OK, drive canstart/run

Cfg_HasIntlkObj

Cfg_OvrdPermIntlk

Inp_NBIntlkOK BOOL Input 1 Level 1 = Non-Bypassable Interlocks OK,drive can start/run

Cfg_HasIntlkObj

Cfg_OvrdPermIntlk

Inp_IOFault BOOL Input 0 Level Input Communication Status0 = OK1 = Fail


35/100


Instruction Data Reference Chapter3

Inp_Sim BOOL Input 0 Level 1 = Simulate working drive0 = Start/Stop/ Monitor actual

drive

Cfg_SimRampT

Inp_Hand BOOL Input 0 Level 1 = Select Hand (hardwired)Control Strategy

Cfg_SetTrackOvrdHand

Inp_Ovrd BOOL Input 0 Level 1 = Select Override controlstrategy

Cfg_OvrdPermIntlk


Inp_OvrCmd SINT Input 0 Decimal Override Mode Command:0 = None1 = Stop2 = Start Forward3 = Start Reverse

Inp_OvrSpeed REAL Input 0 Float Value to set Speed Reference inOverride Mode (SpeedRef EU)

Inp_OvrdOutDataLink

REAL Input 0 Float Value to set Output Datalink inOverride Mode (OutDatalink EU)

Inp_OvrdState BOOL Input 0 Level 1 = Override to RUN0 = Override to STOP

Cfg_OvrdPermIntlk

Inp_OvrdDir BOOL Input 1 Level Override direction1 = FORWARD2 = REVERSE

Inp_OvrdSpeed REAL Input 0 Float Speed at which to run drive inOverride if Overriding to RUN

Cfg_OvrdPermIntlk


Cfg_SpeedFdbkEUMin

Cfg_SpeedFdbkEUMax

Cfg_SpeedRefRawMin

Cfg_SpeedRefRawMax

Cfg_SpeedRefEUMin

Cfg_SpeedRefEUMax

Inp_Reset BOOL Input 0 Level 1 = Reset drive fault conditionsand latched Alarms

Cfg_DriveFaultResetReqd

Cfg_ResetPulseT


AssociatedConfiguration Parameter


36/100



Output(Out_)

Output data elements are used to connect from the P_VSD instruction to fieldoutputs on I/O modules or to other objects. Each Output used should havemapping logic or a function block wire to write the output value to the output

card or other object every scan.

Name: Data Type: Usage: Default: Style: Description:Associated ConfigurationParameter

Out_SpeedRef INT Output 0 Decimal Drive Speed Reference inDrive Units (typ. 0-32767 = 0to max freq.)

Cfg_SpeedRefEUMin

Cfg_SpeedRefEUMax

Cfg_SpeedRefRawMin

Cfg_SpeedRefRawMax

Out_Datalink INT Output 0 Decimal Auxiliary Signal (datalink)Output in Drive (raw) Units

Cfg_HasOutDatalink


Cfg_OutDatalinkEUMax



Out_Run BOOL Output 0 1 = Start/Run Drive0 = Stop Drive (for held

starter type)

Out_Stop BOOL Output 0 1 = Stop Drive0 = drive left in current state

Out_Start BOOL Output 0 1 = Start Drive0 = drive left in current state

Out_Jog BOOL Output 0 1 = Jog drive at Jog Speed0 = stop jogging

Cfg_HasJog

Out_ClearFault BOOL Output 0 1 = Attempt to clear DriveFault

Cfg_ResetPulseT

Out_Fwd BOOL Output 0 1 = Set drive direction toForward

Cfg_HasReverse

Out_Rev BOOL Output 0 1 = Set drive direction toReverse

Cfg_HasReverse


37/100



Configurations(Cfg_)

Configuration data elements are used to set configurable capabilities, featuresand functions of the P_VSD Instruction.

The following Configuration data may be modified by controller applicationlogic, using the HMI Faceplate, or using the Tag Monitor in RSLogix 5000software.


Cfg_HasReverse BOOL Input 0 Level 1 = Drive can be runreverse

0 = Forward only

Cfg_HasJog BOOL Input 0 Level 1 = Drive Jog Commandenabled/visible

0 = Drive Jog Commandnot allowed

Cfg_HasRunFdbk BOOL Input 1 Level 1 = Drive provides speedfeedback and runsignal

Cfg_FailToStartT Cfg_FailToStopT

Cfg_UseRunFdbk

Cfg_UseRunFdbk BOOL Input 1 Level 1 = Drive run feedbackshould be used forfailure checking

Cfg_FailToStartT

Cfg_FailToStopT

Cfg_HasRunFdbk

Cfg_HasInpDatalink BOOL Input 0 Level 1 = A signal is connectedto Inp_Datalink

Cfg_HasOutDatalink BOOL Input 0 Level 1 = A signal is connectedto Out_Datalink

Cfg_HasFwdPermObj BOOL Input 0 Level 1 = Tells HMI a P_Perm isconnected toInp_FwdPerm

Cfg_HasRevPermObj BOOL Input 0 Level 1 = Tells HMI a P_Perm isconnected toInp_RevPerm

Cfg_HasIntlkObj BOOL Input 0 Level 1 = Tells HMI a P_Intlk isconnected toInp_Intlk

Cfg_HasResInhObj BOOL Input 0 Level 1 = Tells HMI a P_ResInhRestart Inhibit isconnected

Cfg_HasRunTimeObj BOOL Input 0 Level 1 = Tells HMI aP_RunTime isconnected

Cfg_SetTrack BOOL Input 1 Level 1 = PSets track OSets inOper, OSets trackPSets in Prog

0 = No tracking

Cfg_SetTrackOvrdHand BOOL Input 0 Level 1 = Prog/Oper Settingstrack Override/Handspeed reference


38/100



Cfg_PCmdClear BOOL Input 1 Level 1 = Clear ProgramCommands on receipt

0 = Leave Set

Cfg_ProgDefault BOOL Input 0 Decimal Default Mode:1 = Program Mode if no

requests0 = Operator Mode if no

requests

Val_Mode

Sts_Prog

Sts_Oper

Cfg_OCmdResets BOOL Input 0 Decimal 1 = New Oper drivecommand. resetsfault,

0 = reset required to clearfault

OCmd_Start

OCmd_Stop

OCmd_Jog

Cfg_OvrdPermIntlk BOOL Input 0 Level 1 = Override ignoresBypassable Perm/

Intlk0 = always use Perm/Intlk

Cfg_ShedOnFailToStart BOOL Input 1 Decimal 1 = Stop Motor and Alarmon Fail to Start

0 = Alarm only on Fail toStart

Sts_FailToStart

Alm_FailToStart

Cfg_ShedOnIOFault BOOL Input 1 Decimal 1=Stop Motor and Alarmon I/O Fault

0 = Alarm only on I/OFault

Sts_IOFault

Alm_IOFault

Cfg_SimScaleEU BOOL Input 0 Decimal 1 = In simulation, scaleSpeed Ref EU to

Speed Fdbk EU

Cfg_SpeedRefEUMin,

Cfg_SpeedRefEUMax

Cfg_SpeedFdbkEUMin

Cfg_SpeedFdbkEUMax

Cfg_SimScaleRaw BOOL Input 0 Decimal 1 = In simulation, scaleSpeed Ref EU to raw,then raw to SpeedFdbk EU

Cfg_SpeedRefRawMin

Cfg_InpDatalinkRawMax

Cfg_SpeedRefEUMin,

Cfg_SpeedRefEUMax

Cfg_SpeedFdbkEUMin

Cfg_SpeedFdbkEUMax

Cfg_SpeedFdbkEUMin

Cfg_SpeedFdbkEUMax

Cfg_HasFailToStartAlm BOOL Input 0 Level 1 = Fail to Start Alarmexists and will bechecked

Cfg_HasFailToStopAlm BOOL Input 0 Level 1 = Fail to Stop Alarmexists and will bechecked

Cfg_HasIntlkTripAlm BOOL Input 0 Level 1 = Interlock Trip Alarmexists and will bechecked



39/100



Cfg_HasDriveFaultAlm BOOL Input 0 Level 1 = Drive Fault Alarmexists and will bechecked

Cfg_HasIOFaultAlm BOOL Input 0 Level 1 = I/O Fault Alarm existsand will be checked

Cfg_FailToStartResetReqd BOOL Input 0 Level 1 = Reset required to clearFail to Start Alarm

Cfg_FailToStartAckReqd BOOL Input 1 Level 1 = Acknowledge requiredfor Fail to Start Alarm

Cfg_FailToStopResetReqd BOOL Input 0 Level 1 = Reset required to clearFail to Stop Alarm

Cfg_FailToStopAckReqd BOOL Input 1 Level 1 = Acknowledge requiredfor Fail to Stop Alarm

Cfg_IntlkTripResetReqd BOOL Input 0 Level 1 = Reset required to clearInterlock Trip Alarm

Cfg_IntlkTripAckReqd BOOL Input 1 Level 1 = Acknowledge requiredfor Interlock TripAlarm

Cfg_DriveFaultResetReqd BOOL Input 1 Level 1 = Reset required to clearDrive Fault Alarm

Cfg_DriveFaultAckReqd BOOL Input 0 Level 1 = Acknowledge requiredfor Drive Fault Alarm

Cfg_IOFaultResetReqd BOOL Input 0 Level 1 = Reset required to clearI/O Fault Alarm

Cfg_IOFaultAckReqd BOOL Input 1 Level 1 = Acknowledge requiredfor I/O Fault Alarm

Cfg_FailToStartSeverity SINT Input 4 Decimal Fail To Start AlarmSeverity

1 = Information2 = Warning3 = Exception4 = Fault

Cfg_FailToStopSeverity SINT Input 4 Decimal Fail To Stop AlarmSeverity

1 = Information2 = Warning3 = Exception

4 = FaultCfg_IntlkTripSeverity SINT Input 2 Decimal Interlock Trip Alarm

Severity1 = Information2 = Warning3 = Exception4 = Fault



40/100



Cfg_DriveFaultSeverity SINT Input 4 Decimal Drive Fault Alarm Severity1 = Information2 = Warning3 = Exception4 = Fault

Cfg_IOFaultSeverity SINT Input 4 Decimal I/O Fault Alarm Severity1 = Information2 = Warning3 = Exception4 = Fault

Cfg_MinSpdRef REAL Input 0.0 Float Minimum SpeedReference in EU (forlimiting)

Cfg_MaxSpdRef REAL Input 60.0 Float Maximum SpeedReference in EU (for

limiting)

Cfg_SpeedRefRawMin INT Input 0 Decimal Speed ReferenceMinimum in Drive (raw)Units (for scaling)

Cfg_SpeedRefRawMax INT Input 32767 Decimal Speed ReferenceMaximum in Drive (raw)Units (for scaling)

Cfg_SpeedRefEUMin REAL Input 0.0 Float Speed ReferenceMinimum in EngineeringUnits (for scaling)

Cfg_SpeedRefEUMax REAL Input 130.0 Float Speed ReferenceMaximum in EngineeringUnits (for scaling)

Cfg_SpeedFdbkRawMin INT Input 0 Decimal Speed FeedbackMinimum in Drive (raw)Units (for scaling)

Cfg_SpeedFdbkRawMax INT Input 32767 Decimal Speed FeedbackMaximum in Drive (raw)Units (for scaling)

Cfg_SpeedFdbkEUMin REAL Input 0.0 Float Speed FeedbackMinimum in EngineeringUnits (for scaling)

Cfg_SpeedFdbkEUMax REAL Input 130.0 Float Speed Feedback

Maximum in EngineeringUnits (for scaling)

Cfg_InpDatalinkRawMin INT Input 0 Decimal Input Datalink Minimumin Drive (raw) Units (forscaling)

Cfg_HasInpDatalink

Cfg_InpDatalinkRawMax INT Input 4095 Decimal Input Datalink Maximumin Drive (raw) Units (forscaling)

Cfg_HasInpDatalink



41/100



Cfg_InpDatalinkEUMin REAL Input 0.0 Float Input Datalink Minimumin Engineering Units (forscaling)

Cfg_HasInpDatalink

Cfg_InpDatalinkEUMax REAL Input 409.5 Float Input Datalink Maximumin Engineering Units (forscaling)

Cfg_HasInpDatalink

Cfg_OutDatalinkMin REAL Input 0.0 Float Minimum Output Datalinkin EU (for limiting)

Cfg_HasOutDatalink





Cfg_OutDatalinkMax REAL Input 100.0 Float Maximum OutputDatalink in EU (for

limiting)

Cfg_HasOutDatalink





Cfg_OutDatalinkRawMin INT Input 0 Decimal Output Datalink Minimumin Drive (raw) Units (forscaling)

Cfg_HasOutDatalink

Cfg_OutDatalinkRawMax INT Input 4095 Decimal Output DatalinkMaximum in Drive (raw)Units (for scaling)

Cfg_HasOutDatalink

Cfg_OutDatalinkEUMin REAL Input 0.0 Float Output Datalink Minimumin Engineering Units (for

scaling)

Cfg_HasOutDatalink

Cfg_OutDatalinkEUMax REAL Input 409.5 Float Output DatalinkMaximum in EngineeringUnits (for scaling)

Cfg_HasOutDatalink

Cfg_SimRampT DINT Input 10 Decimal Time to ramp speed fdbkwhen in Simulation (sec)

Cfg_FailToStartT DINT Input 15 Decimal Time after Start to getRun Feedback beforeFault (sec)

Cfg_FailToStopT DINT Input 15 Decimal Time after Stop to dropRun Feedback beforeFault (sec)

Cfg_ResetPulseT DINT Input 2 Decimal Time to pulse Out_Resetto clear drive fault



42/100



Because they contain arrayed or structured data types, the followingConfiguration data elements use P_VSD Add-On Instruction Local Tags.These may be modified using RSLogix 5000 or using the HMI Faceplates, butcannot be modified using controller logic:

Cfg_MaxJogT REAL Input 0 Float Maximum jog time (sec,0 = unlimited)

Cfg_OperKeep SINT Input 2#0000_0000

Binary Operator keeps control inProgram Mode:.0 = Speed Reference.1 = Start/Stop.2 = Forward/Reverse.3 = Output Datalink

Cfg_ProgKeep SINT Input 2#0000_0000

Binary Program keeps control inOperator Mode:.0 = Speed Reference.1 = Start/Stop.2 = Forward/Reverse.3 = Output Datalink



Cfg_Desc STRING_40 Local 'Variable SpeedDrive'

Description for display onHMI

Cfg_FwdText STRING_16 Local 'FORWARD' Name for ForwardDirection, e.g., Up,

ForwardCfg_InpDatalinkEU STRING_8 Local Empty/null Input Datalink

Engineering Units fordisplay on HMI

Cfg_HasInpDatalink

Cfg_SpeedRefRawMin

Cfg_InpDatalinkLabel STRING_20 Local Empty/null Input Datalink Labeldisplayed on Faceplate

Cfg_HasInpDatalink

Cfg_SpeedFdbkRawMax

Cfg_Label STRING_20 Local 'Motor SpeedControl'

Label for graphic symboldisplayed on HMI

Cfg_OutDatalinkEU STRING_8 Local Empty/null Output DatalinkEngineering Units fordisplay on HMI

Cfg_HasOutDatalink





Cfg_OutDatalinkLabel STRING_20 Local Empty/null Output Datalink Labeldisplayed on Faceplate

Cfg_HasOutDatalink






43/100



Cfg_RevText STRING_16 Local 'REVERSE' Name for ReverseDirection, e.g., Down,Reverse

Cfg_SpeedFdbkEU STRING_8 Local 'Hz' Speed FeedbackEngineering Units fordisplay on HMI

Cfg_SpeedRefEU STRING_8 Local 'Hz' Speed ReferenceEngineering Units fordisplay on HMI

Cfg_Tag STRING_20 Local 'P_VSD' Tagname for display onHMI



44/100



Program Settings(PSet_)

Program Setting data elements are used by application logic to establishsetpoints, thresholds, and other settings of the P_VSD Instruction.Automation logic may write to these settings any time; the P_VSD Instructionuses them in its logic when it is in the Program Mode.


PSet_SpeedRef REAL Input 0 Float Program Setting of SpeedReference (EU)

Cfg_MaxSpdRef

Cfg_MinSpdRef

Cfg_SetTrack


Cfg_SpeedFdbkEUMin

Cfg_SpeedFdbkEUMax

Cfg_SpeedRefRawMin

Cfg_SpeedRefRawMax

Cfg_SpeedRefEUMin

Cfg_SpeedRefEUMax

PSet_OutDatalink REAL Input 0 Float Program Setting of Output Datalink(EU)

Cfg_HasOutDatalink





Cfg_OutDatalinkMax

Cfg_OutDatalinkMin

Cfg_SetTrack

PSet_Owner DINT Input 0 Decimal Program Owner Request ID(non-zero) or Release (zero)


45/100



Program Commands(PCmd_)

Program Command data elements are used by application logic to requestP_VSD Instruction actions, such as changing Modes, acknowledging alarms,or specific P_VSD actions. Application logic sets the Program Command to 1or 0 to request the action. (See the Edge and Levelsection in the Preface formore information). The P_VSD Instruction then performs the requestedaction if it is in Program Mode and the action can be performed.

Devices Commands*

* Primary Function: IfCfg_PCmdClear= 0, triggered by Level = 1 If Cfg_PCmdClear = 1, triggered by rising Edge

* * Opposite Function: If Cfg_PCmdClear = 0, triggered by primary function bit Level = 0 (this bit NOT USED) If Cfg_PCmdClear = 1, triggered by rising Edge of this bit

Mode Commands





PCmd_Start BOOL Input 0 * Program Command to Start Drive Cfg_FailToStartT

PCmd_Stop BOOL Input 0 ** Program Command to Stop Drive Cfg_FailToStopT

PCmd_Fwd BOOL Input 0 * Program Command to set direction to

Forward

Cfg_HasReverse

PCmd_Rev BOOL Input 0 ** Program Command to set direction toReverse

Cfg_HasReverse

Name: Data Type: Usage: Default: Style: Description:


PCmd_Acq BOOL Input 0 * Program Command to Acquireownership (Oper to Prog)

PCmd_Rel BOOL Input 0 ** Program Command to Releaseownership (Prog to Oper)

PCmd_Lock BOOL Input 0 * Program Command to Lock Mode inProg

PCmd_Unlock BOOL Input 0 ** Program Command to Unlock Mode


46/100



Alarm Commands



Name: Data Type: Usage: Default: Style: Description:AssociatedConfiguration Parameter

PCmd_Reset BOOL Input 0 * Program Command to Resetdrive fault and all Alarmsrequiring Reset

Cfg_ResetPulseT

PCmd_FailToStartAck BOOL Input 0 * Program Command toAcknowledge Fail to StartAlarm

Cfg_FailToStartAckReqd

PCmd_FailToStartInhibit BOOL Input 0 * Program Command to InhibitFail to Start Alarm

PCmd_FailToStartUninhibit BOOL Input 0 ** Program Command toUninhibit Fail to Start Alarm

PCmd_FailToStopAck BOOL Input 0 * Program Command to

Acknowledge Fail to StopAlarm

Cfg_FailToStopAckReqd

PCmd_FailToStopInhibit BOOL Input 0 * Program Command to InhibitFail to Stop Alarm

PCmd_FailToStopUninhibit BOOL Input 0 ** Program Command toUninhibit Fail to Stop Alarm

PCmd_IntlkTripAck BOOL Input 0 * Program Command toAcknowledge Interlock TripAlarm

Cfg_IntlkTripAckReqd

PCmd_IntlkTripInhibit BOOL Input 0 * Program Command to InhibitInterlock Trip Alarm

PCmd_IntlkTripUninhibit BOOL Input 0 ** Program Command toUninhibit Interlock Trip Alarm

PCmd_DriveFaultAck BOOL Input 0 * Program Command toAcknowledge Drive FaultAlarm

Cfg_DriveFaultAckReqd

PCmd_DriveFaultInhibit BOOL Input 0 * Program Command to InhibitDrive Fault Alarm

PCmd_DriveFaultUninhibit BOOL Input 0 ** Program Command toUninhibit Drive Fault Alarm

PCmd_IOFaultAck BOOL Input 0 * Program Command toAcknowledge I/O Fault Alarm

Cfg_IOFaultAckReqd

PCmd_IOFaultInhibit BOOL Input 0 * Program Command to InhibitI/O Fault Alarm

PCmd_IOFaultUninhibit BOOL Input 0 ** Program Command toUninhibit I/O Fault Alarm


47/100



Operator Settings,Maintenance Settings,Other Settings(OSet_, MSet_, Set_)

Operator, Maintenance and Other Setting data elements are used by the HMIFaceplate to let the operator establish setpoints, thresholds, and other settingsof the P_VSD Instruction. The P_VSD Instruction uses Other Settings in itslogic regardless of Mode. It uses Operator and Maintenance Settings when it isin Operator or Maintenance Mode.

Operator / Maintenance Setting Readies

Operator / Maintenance Setting Readies are used to enable (1) or gray-out (0)the Setting data entry fields on the HMI faceplate. Specific ready bits are usedfor certain Operator or Maintenance Settings. Rdy_OSet applies to all otherOperator or Maintenance Settings for which there are no specific Ready bits.

Name: Data Type: Usage: Default: Style: Description:AssociatedConfiguration Parameter

OSet_SpeedRef REAL Input 0.0 Float Operator Setting of SpeedReference (EU)

Cfg_MaxSpdRef

Cfg_MinSpdRef

Cfg_SetTrack


Cfg_SpeedRefEUMin

Cfg_SpeedRefEUMax

OSet_OutDatalink REAL Input 0.0 Float Operator Setting of OutputDatalink (EU)

Cfg_HasOutDatalink Cfg_OutDatalinkEUMin




Cfg_OutDatalinkMax

Cfg_OutDatalinkMin

Cfg_SetTrack



Rdy_SpeedRef BOOL Output 0 1 = Ready to receive OSet_SpeedRef

(enables data entry field)Rdy_OSet BOOL Output 0 1 = Ready to receive OSets (enables

data entry fields)


48/100



Operator Commands,Maintenance Commands,Command Readies(OCmd_, MCmd_, Rdy_)

Operator Commands and Maintenance Commands are used by the Operatorat the HMI to request instruction actions, such as changing modes;acknowledging, enabling or disabling, suppressing or unsuppressing alarms; orother instruction-specific actions. Except for items marked Level theseCommands are set (latched) by the HMI and are read and then cleared(unlatched) by this instruction, allowing a many-to-one relationship betweenHMI requestors and each Command. Commands are implemented as publicInput Parameters of the instruction or as Input Parameters of instructionsinternal to the P_VSD instruction (embedded Commands).

Device Commands


AssociatedConfiguration

ParameterOCmd_Start BOOL Input 0 Edge Operator Command to Start Drive Cfg_FailToStartT

OCmd_Stop BOOL Input 0 Edge Operator Command to Stop Drive Cfg_FailToStopT

OCmd_Jog BOOL Input 0 Level Operator Command to Jog Drive (notcleared by P_VSD!)

Cfg_HasJog

OCmd_Fwd BOOL Input 0 Edge Operator Command to set direction toForward

Cfg_HasReverse

OCmd_Rev BOOL Input 0 Edge Operator Command to set direction toReverse

Cfg_HasReverse

OCmd_Bypass BOOL Input 0 Edge Operator Command to Bypass allBypassable Interlocks and Permissives

OCmd_Check BOOL Input 0 Edge Operator Command to Check (notbypass) all Interlocks and Permissives

MCmd_Disable BOOL Input 0 Edge Maintenance Command to Disable(red tag) Drive

MCmd_Enable BOOL Input 0 Edge Maintenance Command to Enable(allow to run) Drive


49/100



Mode Commands

Alarm Commands

IMPORTANT Mode Commands are sent to a P_Mode Instruction embeddedwithin the P_VSD Instruction. The P_Mode Instruction instanceis named Mode.



Mode.MCmd_Acq BOOL Input 0 Edge Maintenance Command to AcquireOwnership (Oper/Prog/Ovrd to Maint)

Mode.MCmd_Rel BOOL Input 0 Edge Maintenance Command to ReleaseOwnership (Maint to Oper/Prog/Ovrd)

Mode.OCmd_AcqLock BOOL Input 0 Edge Operator Command to Acquire and LockMode in Oper

Mode.OCmd_Unlock BOOL Input 0 Edge Operator command to Unlock OperatorMode

IMPORTANT Alarm Commands are sent to P_Alarm Instructions embeddedwithin the P_VSD Instruction. Each P_Alarm Instructioninstance is named for the alarm condition.


OCmd_Reset BOOL Input 0 Edge Operator Command to Resetall Alarms requiring Reset

Cfg_ResetPulseT

OCmd_ResetAckAll BOOL Input 0 Edge Operator Command to Resetall Alarms and latched Shedconditions

FailToStart.OCmd_Reset BOOL Input 0 Edge Operator Command to Resetlatched Failure to StartAlarm

Cfg_FailToStartResetReqd

FailToStart.OCmd_Ack BOOL Input 0 Edge Operator Command toAcknowledge Failure toStart Alarm

Cfg_FailToStartAckReqd

FailToStart.OCmd_Disable BOOL Input 0 Edge Operator Command toDisable Failure to StartAlarm

FailToStart.OCmd_Enable BOOL Input 0 Edge Operator Command toEnable Failure to Start Alarm


50/100



FailToStop.OCmd_Reset BOOL Input 0 Edge Operator Command to Resetlatched Failure to StopAlarm

Cfg_FailToStartResetReqd

FailToStop.OCmd_Ack BOOL Input 0 Edge Operator Command toAcknowledge Failure to StopAlarm

Cfg_FailToStopAckReqd

FailToStop.OCmd_Disable BOOL Input 0 Edge Operator Command toDisable Failure to StopAlarm

FailToStop.OCmd_Enable BOOL Input 0 Edge Operator Command toEnable Failure to Stop Alarm

IntlkTrip.OCmd_Reset BOOL Input 0 Edge Operator Command to Resetlatched Interlock Trip Alarm

Cfg_IntlkTripResetReqd

IntlkTrip.OCmd_Ack BOOL Input 0 Edge Operator Command to

Acknowledge Interlock TripAlarm

Cfg_IntlkTripAckReqd

IntlkTrip.OCmd_Disable BOOL Input 0 Edge Operator Command toDisable Interlock Trip Alarm

IntlkTrip.OCmd_Enable BOOL Input 0 Edge Operator Command toEnable Interlock Trip Alarm

DriveFault.OCmd_Reset BOOL Input 0 Edge Operator Command to Resetlatched Drive Fault Alarm

Cfg_DriveFaultResetReqd

DriveFault.OCmd_Ack BOOL Input 0 Edge Operator Command toAcknowledge Drive FaultAlarm

Cfg_DriveFaultAckReqd

DriveFault.OCmd_Disable BOOL Input 0 Edge Operator Command toDisable Drive Fault Alarm

DriveFault.OCmd_Enable BOOL Input 0 Edge Operator Command toEnable Drive Fault Alarm

IOFault.OCmd_Reset BOOL Input 0 Edge Operator Command to Resetlatched I/O Fault Alarm

Cfg_IOFaultResetReqd

IOFault.OCmd_Ack BOOL Input 0 Edge Operator Command toAcknowledge I/O FaultAlarm

Cfg_IOFaultAckReqd

IOFault.OCmd_Disable BOOL Input 0 Edge Operator Command toDisable I/O Fault Alarm

IOFault.OCmd_Enable BOOL Input 0 Edge Operator Command toEnable I/O Fault Alarm



51/100



Device Command Readies

Each Operator or Maintenance Command has a corresponding Ready bitwhich indicates whether the Command will be accepted and acted upon when

received. The Ready bit is used to enable (1) or gray-out (0) the Commandbutton on the Faceplate.

Mode Command Readies



Rdy_Start BOOL Output 0 1 = Ready to receive OCmd_Start (enablesHMI button)

Rdy_Stop BOOL Output 0 1 = Ready to receive OCmd_Stop (enablesHMI button)

Rdy_Jog BOOL Output 0 1 = Ready to receive OCmd_Jog (enables

HMI button)Rdy_Fwd BOOL Output 0 1 = Ready to receive OCmd_Fwd (enabled

HMI button) Cfg_HasReverse

Rdy_Rev BOOL Output 0 1 = Ready to receive OCmd_Rev (enablesHMI button)

Cfg_HasReverse

Rdy_Bypass BOOL Output 0 1 = Ready to receive OCmd_Bypass(enables HMI button)

Rdy_Check BOOL Output 0 1 = Ready to receive OCmd_Check(enables HMI button)

Rdy_Disable BOOL Output 0 1 = Ready to receive MCmd_Disable(enables HMI button)

Rdy_Enable BOOL Output 0 1 = Ready to receive MCmd_Enable(enables HMI button)

IMPORTANT Mode Command Readies are provided by a P_Mode Instructionembedded within the P_VSD Instruction. The P_ModeInstruction instance is named Mode.



Mode.Rdy_Acq BOOL Output 0 1 = Ready for MCmd_Acq (enables HMIbutton)


52/100



Alarm Command Readies

Mode.Rdy_Rel BOOL Output 0 1 = Ready for MCmd_Rel (enables HMIbutton)

Mode.Rdy_AcqLock BOOL Output 0 1 = Ready for OCmd_AcqLock (enablesHMI button)

Mode.Rdy_Unlock BOOL Output 0 1 = Ready for OCmd_Unlock (enables HMIbutton)



IMPORTANT Alarm Command Readies are provided by P_Alarm Instructions

embedded within the P_VSD Instruction. Each P_AlarmInstruction instance is named for the alarm condition.

Name: Data Typ

Documents

drive speed