00 L CPU Syslib-Rm017 - En-E

Logix Add-On Instructions and Graphics:
Controller CPU Utilization (L_CPU)
Compatible with the Plant-wide Integrated Architecture

Reference Manual
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 office
or 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 application
of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in
this 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.
WARNING
IMPORTANT
ATTENTION
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, or
economic loss.
Identifies information that is critical for successful application and understanding of the product.
Identifies 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.
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.
Summary of Changes
Introduction
This release of this document is updated throughout for version 2.0 of the
Logix CPU Utilization (L_CPU) Add-On Instruction and Graphics. Please
refer to the Release Notes that are distributed with version 2.0 of the Library.
Updated Information
This document contains the following changes:
iiiPublication SYSLIB-RM017C-EN-E - October 2011
Change:
See:
Version 2.0 of instruction
All
iii
Summary of Changes
Notes:
iv
Publication SYSLIB-RM017C-EN-E - October 2011
Table of Contents
Preface
Use of this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Conventions and Related Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Set and Clear. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Edge and Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Relay Ladder Rung Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Pre-Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Function Block States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Entering Text in FactoryTalk View SE . . . . . . . . . . . . . . . . . . . . . . . . . xii
Chapter 1
Overview
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Primary Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Revision Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Chapter 2
Configuration Options
Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 3
Instruction Data Reference
L_CPU_Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configurations (Cfg_). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operator Commands, Maintenance Commands, Command Readies
(OCmd, MCmd_, Rdy_) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operator Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintenance Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Status (Sts_) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Device Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
17
18
19
19
19
21
21
Table of Contents
Chapter 4
HMI Reference
vi
Graphic Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Graphic Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Faceplate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operator Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communications Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CPU Usage Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Memory Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connections Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintenance Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logix CPU Faceplate Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23
24
25
25
27
28
29
30
31
33
Preface
Use of this Document
This document provides a programmer with details on the L_CPU instruction

for a Logix-based controller. You should already be familiar with how the
Logix-based controller stores and processes data.
Novice programmers should read all the details about an instruction before
using the instruction. Experienced programmers can refer to the instruction
information to verify details.
Conventions and Related

Terms
Set and Clear

This manual uses set and clear to define the status of bits (booleans) and values
(non-booleans):
viiPublication SYSLIB-RM017C-EN-E - October 2011
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
vii
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 the
action; 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 a

state, usually 1)
Opposite action (disable) is triggered by input being in
opposite 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;] or
if-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 Level
input on the instruction (one-to-one relationship restriction).
IMPORTANT
viii
All Operator Commands (OCmd_) and Maintenance Commands

(MCmd_) are Edge triggered. The HMI Graphic Symbol or
Faceplate SETS (writes a 1 to) each Command bit and the
Instruction CLEARS (writes a 0 to) the Command bit, then
performs the function, if possible.
Preface
IMPORTANT
This instruction has Program Commands (PCmd_) which are

selectable as Edge or Level, depending on the Configuration
Parameter 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 the
Instruction Data Reference become Level triggered, and
opposite functions are triggered by the primary Program
Command being CLEARED to 0.
Relay Ladder Rung Condition

The controller evaluates ladder instructions based on the rung condition
preceding the instruction (rung-in condition). Based on the rung-in condition
and the instruction, the controller sets the rung condition following the
instruction (rung-out condition), which in turn, affects any subsequent
instruction.
If the rung-in condition to an input instruction is true, the controller evaluates

the instruction and sets the rung-out condition based on the results of the
instruction. 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
The rung-in condition is reflected in the EnableIn parameter and

determines how the system performs each Process Add-On
Instruction. If the EnableIn signal is TRUE, the system performs
the instructions main logic routine. Conversely, if the EnableIn
signal is FALSE, the system performs the instructions
EnableInFalse routine.
The instructions main logic routine sets/clears the EnableOut
parameter, which then determines the rung-out condition. The
EnableInFalse routine cannot set the EnableOut parameter. If
the rung-in condition is FALSE, then the EnableOut parameter
and the rung-out condition will also be FALSE.
ix
Preface
Pre-Scan
During the transition into RUN, the controller performs a Pre-scan before the
first 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 ignores
jumps that could skip the execution of instructions. The controller executes all
FOR loops and subroutine calls. If a subroutine is called more than once, it is
executed each time it is called. The controller uses Pre-scan instructions to
reset non-retentive data values.
During Pre-scan, input values are not current and outputs are not written. The
following 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 Instructions

logic routine as all FALSE and then performs its Pre-scan
routine as TRUE.
Preface
Function Block States

The controller evaluates function block instructions based on the state of
different conditions.
Possible Condition:
Description:
Pre-scan
Pre-scan for function block routines is the same as for relay

ladder routines. The only difference is that the Enableln
parameter for each function block instruction is cleared during
Pre-scan.
Instruction first scan
Instruction first scan refers to the first time an instruction is

executed after Pre-scan. The controller uses instruction first
scan to read current inputs and determine the appropriate
state to be in.
Instruction first run
Instruction first run refers to the first time the instruction

executes with a new instance of a data structure. The
controller uses instruction first run to generate coefficients
and other data stores that do not change for a function block
after initial download.
Every function block instruction also includes EnableIn and EnableOut

parameters.
If the EnableIn parameter is not wired, the instruction always executes as
normal and EnableIn remains set. If you clear EnableIn, it changes to set the
next time the instruction executes.
IMPORTANT
When programming in function block, restrict the range

of engineering units to 1015 because internal floating
point calculations are done using single precision floating
point. Engineering units outside of this range may result in
a loss of accuracy if results approach the limitations of
single precision floating point (1038).
xi
Preface
Entering Text in FactoryTalk View SE

When entering data into String Input fields in FactoryTalk View SE, the data is
not 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.
EXAMPLE
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.
EXAMPLE
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
xii
Chapter
Overview
The L_CPU (Logix Controller CPU Utilization) Add-On Instruction monitors

the Logix controller executing it and provides information on controller CPU
utilization, communication usage, memory usage, task scan times and other
information. The data provided by the L_CPU Instruction can be useful in
diagnosing communication or control responsiveness issues or in tuning the
performance of control Tasks for optimum controller performance.
The L_CPU Instruction can be loaded as part of a control application and left
disabled (the default) until needed. Or it can be enabled at a slow update rate
for general controller monitoring. The instruction can be enabled or the
update rate can be quickened if necessary as directed by a Rockwell
Automation Technical Support specialist to aid in diagnosing controller
performance issues.
The L_CPU Instruction includes Graphic Symbols and a Faceplate display to
use in building your human-machine interface (HMI).
Use when:
You want to monitor general controller resource utilization: processor
utilization, task performance, task scan time, memory usage,
communication capacity, networking performance or connection usage
on a Logix controller.
You need to gather data as directed by a Rockwell Automation Technical
Support specialist to aid in resolving a specific issue.
You want to tune the periods or priorities of multiple Tasks in your
controller to optimize control and you want to see how changes in Task
configuration affect CPU and other resource usage in the controller.
Do NOT use:
At a high update rate on a continuing basis. The L_CPU Instruction
increases the communication load on the controller when it is polling
for performance data. At high update rates, the resource load generated
by the L_CPU Instruction polling can impact control performance,
especially if you already have a fully-loaded controller.
1Publication SYSLIB-RM017C-EN-E - October 2011
Chapter 1
Overview
Functional Description
The L_CPU instruction collects and summarizes a variety of data from the
Logix controller it is monitoring, including:
Processor Identity information
Catalog Number and Description
Major and Minor firmware revision numbers
Communication Responsiveness information
CPU% available for responding to communications requests
CPU% used for responding to communications requests
Optimized Packets used for responding to communications requests
Memory Usage (total and for each of several classes of memory)
Total memory size
Memory used
Memory available
Largest contiguous block of available memory
Scan Times (for a selected Task)
Maximum scan time
Most recent scan time
CPU Utilization (%) for:
The Continuous Task (or unused CPU, if no Continuous Task)
Periodic and Event Tasks
Motion/Synchronization
Safety Tasks
Redundancy
Sending Messages (MSG)
Responding to communications requests (such as from HMI)
System (I/O scan, timer updates, everything else)
Communication Connection usage:
Total connections available
Connections used for each of several classes of communication
Unconnected Buffers and Cached Messages
I/O Forcing status
Controller Minor Faults
Communication Timeslice setting
Overview
Chapter 1
These items are displayed on several Faceplate tabs, with summary

information on the main (home) tab.
TIP
It's a good idea to call up the L_CPU Faceplate when you call Rockwell
Automation Technical Support. The information on the Operator (home) tab is
often asked for up front by the Technical Support specialist when you call. You'll
also likely need your RSLogix 5000 software serial number or other license or
support contract information. The Maintenance tab of the Faceplate has a space
for you to record this information for reference.
Primary Operations
The instruction sets up a monitoring window over which CPU utilization

metrics are collected. For example, if the window time is 1.0 second, the CPU
utilization number will show what percentage of CPU was used for each
purpose (continuous task scanning, periodic/event task scanning, and so
forth) over a 1.0 second window.
The instruction waits for the configured update time (default is 5 seconds),
then collects all the metrics in its L_CPU_Out In/Out parameter tag. The
instruction gathers data every update time as long as it is enabled.
IMPORTANT
The L_CPU Instruction logic is firmware version dependent. There are different
versions of the instruction for each major release (18.x, 19.x, etc.) of Logix
firmware. Be sure to load the right version.
The L_CPU Instruction does not support SoftLogix controllers or the
emulated controller in RSLogix Emulate 5000. If the L_CPU Instruction
identifies the controller as the wrong firmware version or as an unsupported
controller, it will not poll, but rather will assert the Sts_WrongVersion status
flag.
IMPORTANT
The L_CPU Instruction must be configured with the slot number of the controller.
If the Instruction is asserting the Sts_MsgErr flag, that means it cannot
communicate via MSG to the controller. Check the Cfg_SlotNumber
configuration. If you change Cfg_SlotNumber, it may be necessary to cycle the
controller mode to Program, then back to Run, for the change to take effect.
Chapter 1
Overview
TIP
You can find the correct slot number using RSLogix 5000 software. In the
Controller Organizer, select the controller (top item). Right-click and select
Properties. The controller slot number is shown near the bottom of the properties
window. For controllers where the slot number is not configurable, this item will
be disabled (grayed out); regardless, it still displays the correct number to use to
configure the L_CPU Instruction.
Overview
Chapter 1
Operating Modes
The L_CPU Instruction has no commands or outputs intended to control

equipment and so does not have any Modes.
Alarms
The L_CPU Instruction does not generate any alarms. If an alarm is needed
when a specific metric crosses a threshold, you will need to add logic to do the
checking. The logic can be as simple as a comparison (CMP, GRT, GEQ, LES,
LEQ or LIM instruction) plus a P_Alarm Add-On Instruction.
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.

Condition
Description
EnableIn False (False Rung)
The L_CPU Instruction has no EnableInFalse

logic and does nothing on a false rung. Data
associated with the instruction are left in
their last state.
Powerup (Pre-Scan, First Scan)
Logic is set up to ensure the Window Time

is sent to the controller when it transitions
to RUN mode. Previously active polling
(prior to power down or transition to PROG
mode) is cancelled. High-water data stored
in the instruction (not built in to the
controller status registers) are cleared.
Postscan (SFC Transition)
No SFC Postscan logic is provided.
Refer to the Logix5000 Controllers Add-On Instructions Programming

Manual, publication 1756-PM010, for more information on Add-On
Instruction execution condition handling.
Chapter 1
Overview
Revision Compatibility
The L_CPU Add-On Instruction in RSLogix 5000 software and the Faceplate
in FactoryTalk View software are marked with revision information as shown
in the following table:.
Component
Example
The Add-On Instruction in RSLogix 5000 has

revision information visible when the
instruction is selected in the Controller
Organizer.
The Faceplate in FactoryTalk View has

revision information visible when the
pointer is paused just inside the lower
left-hand corner of the Faceplate when
called up on a running HMI Client.
The Instruction and Faceplate are compatible if they have the same Major and
Minor Revision numbers.
The Major Revision is the first number, before the period.
The Minor Revision is the second number, after the period and before the
hyphen or space.
Information after the hyphen or space indicates the Tweak Revision. The
Instruction and Faceplate do not have to have the same Tweak Revision to be
compatible.
In the table above, the Add-On Instruction and Faceplate shown are
compatible because they have the same Major.Minor (1.1).
Chapter
Configuration Parameters
Enter the appropriate values from the following table into the L_CPU
Instructions configuration parameters to configure it for your application.
Use the HMI Faceplate or the RSLogix 5000 Tag Monitor function to set the
applicable configuration parameter(s).
TIP
To install the L_CPU instruction, import the entire L_CPU Ladder Diagram rung
(not just the instruction). When you import the rung, all the User-Defined Data
Types, Tags and their values required by the instruction are imported as well,
including MSG configurations, data required to be sent by the Messages, and
default instruction configuration, Your application will have the Controller Tag
L_CPU_Out created and placed in the L_CPU instruction's Ref_Out InOut
Parameter. In the Associated Parameters column below, references to
L_CPU_Out mean the Tag referenced in the Ref_Out InOut Parameter.
Parameter:
Default:
Cfg_MainTaskInstance 1
Faceplate Tab Usage:

Location:
This parameter determines which Task
in the controller has its Scan Time
(Use GSV to get (Max, Last) monitored by the L_CPU
Instruction. Usually this is the
Task instance
MainTask, but any task can be chosen.
number and
write to this
parameter in
IMPORTANT
logic.)
None
Associated Parameters:
L_CPU_Out.ScanTimes.ScanTimeMax
L_CPU_Out.ScanTimes.ScanTimeLast
This parameter's value should be set

programmatically using data returned
by a GSV instruction. The GSV
instruction should be executed before
the L_CPU instruction, and set up as
follows:
Class: Task
Instance: (name of Task to monitor)
Attribute: Instance
Destination:
L_CPU.Cfg_MainTaskInstance
If you imported the entire L_CPU rung,
not just the instruction, the required
GSV has been placed for you. Just
enter the name of the Task to monitor.
Chapter 2
Parameter:
Default:

Location:
Cfg_SlotNumber
None
(Obtain this
value from
RSLogix 5000
software, then
code a MOV to
move it to this
parameter in
logic.)
Enter the slot number of the controller

executing the L_CPU instruction.
TIP
If this parameter is set incorrectly, the
Message (MSG) instructions
contained in the L_CPU instruction
will error. This is reflected in the
Sts_MsgErr status bit of the L_CPU
instruction.
To determine the value to enter:

Open your application in RSLogix
5000 software
In the Controller Organizer,
right-click on the Controller at the
top and select Properties
In the General tab of the Controller
Properties dialog, find the Slot
number on the lower left.
The Slot selection may be grayed out
for certain controller families, but the
correct Slot number is still displayed.
If you imported the entire L_CPU rung,
not just the instruction, the required
MOV instruction has been placed for
you. Just enter the proper slot number
in the Source parameter of the MOV.
Cfg_SupportInfo
Enter
Software
S/N or
Support
Contract
Number
Maintenance
Enter your RSLogix 5000 software

serial number, your TechConnect
Support contract number, or other
information that Maintenance or
Engineering personnel will need if
they call Rockwell Automation
Technical Support. On the L_CPU
faceplate, this text can only be
changed by an engineer or
administrator, and it will not be visible
to operator-level users
None
Parameter:
Default:

Location:
Cfg_UpdateT
5 sec
Maintenance
This parameter determines how often

the L_CPU instruction polls the
controller for performance data.
Chapter 2
Sts_Timing
All metrics in L_CPU_Out will be updated
at this interval.
This time should be greater than or

equal to the Cfg_WindowT time if the
(Ref_Out tag).CPUUse data are
being used.
IMPORTANT
Setting this parameter too low will
result in a flood of Messages (MSG) to
the controller, possibly impacting
control performance. Do not use a
value less than 5 seconds unless
instructed to do so by a Rockwell
Automation Technical Support
specialist.
Cfg_WindowT
1.0 sec
None
This parameter determines the

timeframe over which controller CPU
use metrics are collected.
CPU Use metrics:

L_CPU_Out.CPUUse.Comms
L_CPU_Out.CPUUse.Messaging
IMPORTANT
Setting this parameter too low may
result in CPU usage data that are
imprecise, or not meaningful
averages, because they are collected
over too short a time to see all tasks
the controller is performing. Setting
this parameter too high may result in
averaged CPU usage data that may not
capture bursts in certain activities. It is
recommended you keep this
parameter at its default value unless
instructed to change it by Rockwell
Automation Technical Support.
L_CPU_Out.CPUUse.Motion
L_CPU_Out.CPUUse.Redundancy
L_CPU_Out.CPUUse.Safety
L_CPU_Out.CPUUse.System
L_CPU_Out.CPUUse.PeriodicAndEvent
L_CPU_Out.CPUUse.ContinuousOrFree
Chapter 2
Notes:
10
Chapter
This chapter describes the L_CPU Instructions public parameters.

The descriptions in the table below show how these data elements are used
with the L_CPU Add-On Instruction.
L_CPU_Out
Name:
Substructure:
This section shows the L_CPU Instructions Ref_Out (reference output) tags
data structure. This structure is contained in the L_CPU_Out User-Defined
Data Type (UDT). This UDT is imported if you import the entire L_CPU
rung rather than just the Add-On Instruction.
Type:
Element:
Style:
L_CPU_Out
Description:
Associated Parameter:
L_CPU Output Data

Identity
Device Identity
SINT[33]
Name
ASCII
INT
VendorID
Decimal Vendor ID (1 = Rockwell

Automation)
INT
ProductType
Decimal Product Type (14 =

Controller)
INT
ProductCode
Decimal Identifies Model of

Controller (e.g., 96 =
1756-L75)
SINT
Major
Decimal Major Firmware Revision

(> = 18)
SINT
Minor
Decimal Minor Firmware Revision
DINT
Serial
Hex
Controller Serial Number
INT
Status
Binary
Device Status (bit

mapped, see
documentation)
Controller and memory

Catalog Number. The first
byte is the number of
characters, which are
contained in the following
32 bytes.
11
Chapter 3
Name:
Substructure:
Type:
Element:
Style:
CommUse
12
Description:
Communication usage
REAL
RespCPUAvail
Float
Available CPU for

responding to Messages
(HMI, etc.)
REAL
RespCPUAct
Float
CPU in use by Comm Task

(responding to Messages
(HMI, etc.)
DINT
MaxTrendInstance
Decimal Highest current Optimized

Packet (Trend Object)
Instance Number
DINT
NumTrendInstances
Decimal Current number of

Optimized Packet (Trend
Object) Instances
DINT
TrendHighWater
Decimal High water mark of

Optimized Packet (Trend
Object) Instance count
Name:
Substructure:
Type:
Element:
Style:
MemUse
Description:
Chapter 3
Memory usage
DINT
FreeIO
Decimal Free bytes of I/O memory
DINT
FreeDataLogic
Decimal Free bytes of Data and

Logic memory
DINT
FreeGen
Decimal Free bytes of General

memory
DINT
FreeSafety
Decimal Free bytes of Safety

memory
DINT
TotalIO
Decimal Total bytes of I/O memory
DINT
TotalDataLogic
Decimal Total bytes of Data and

Logic memory
DINT
TotalGen
Decimal Total bytes of General

memory
DINT
TotalSafety
Decimal Total bytes of Safety

memory
DINT
MinIO
Decimal Low water free bytes of

I/O memory
DINT
MinDataLogic

Data and Logic memory
DINT
MinGen

General memory
DINT
MinSafety

Safety memory
DINT
MaxBlockIO
Decimal Largest available block of

I/O memory
DINT
MaxBlockDataLogic Decimal Largest available block of

Data and Logic memory
DINT
MaxBlockGen
Decimal Largest Available block of

General memory
DINT
MaxBlockSafety
Decimal Largest Available block of

Safety memory
ScanTimes
Scan Times
REAL
ScanTimeMax
Float
Maximum Scan Time (ms)

for selected Task instance
REAL
ScanTimeLast
Float
Most Recent Scan Time

(ms) for selected Task
instance
13
Chapter 3
Name:
Substructure:
Type:
Element:
Style:
CPUUse
14
Description:
CPU usage
REAL
Comms
Float
Communications
(responding to HMI and
MSGs) %CPU
REAL
Messaging
Float
Sending Messages (MSG

instructions) %CPU
REAL
Motion
Float
Motion Axes %CPU
REAL
Redundancy
Float
Redundancy
Communication and
Synchronization %CPU
REAL
Safety
Float
Safety Processes %CPU
REAL
System
Float
System Processes %CPU
REAL
PeriodicAndEvent
Float
User Periodic and Event

Tasks %CPU
REAL
ContinuousOrFree
Float
Continuous Task (if any) or

Free (if none) %CPU
Name:
Substructure:
Type:
Element:
ConnUse
Style:
Description:
Chapter 3
Connection usage
INT
TotalAllow
Decimal Total Connections

Supported
INT
TotalCurr
Decimal Total Connections

Currently Active
INT
TotalHiWater
Decimal High water mark of Total

Connections Active
INT
IOAllow
Decimal I/O Connections Allocated
INT
IOCurr
Decimal I/O Connections Currently

Active
INT
IOHiWater
Decimal High water mark of I/O

Connections Active
INT
ProdAllow
Decimal Produced Tag

Connections Allocated
INT
ProdCurr
Decimal Produced Tag Connections

Currently Active
INT
ProdHiWater

Produced Tag Connections
Active
INT
ConsAllow
Decimal Consumed Tag

Connections Allocated
INT
ConsCurr
Decimal Consumed Tag

Connections Currently
Active
INT
ConsHiWater

Consumed Tag
Connections Active
INT
MSGCurr
Decimal Message/Block Transfer

Connections Currently
Active
INT
MSGHiWater

Message/Block Transfer
Connections Active
INT
IncomCurr
Decimal Incoming Connections

Currently Active
INT
IncomHiWater

Incoming Connections
Active
DINT
UCBsAllow
Decimal Unconnected Buffers

Allocated
DINT
UCBsCurr
Decimal Unconnected Buffers

Currently Active
DINT
UCBsHiWater

Unconnected Buffers
Active
15
Chapter 3
Name:
16
Substructure:
Type:
Element:
Style:
Description:
INT
MCacheAllow
Decimal MSG/BT Cache Entries

Allocated
INT
MCacheCurr
Decimal MSG/BT Cache Entries

Currently In Use
INT
MCacheHiWater

MSG/BT Cache Entries In
Use
TimeSlice
INT
Decimal Controller Timeslice: % of

continuous task time for
communications
IOLEDStatus
INT
Decimal I/O LED Status

0 = Off
1 = RedBlink
2 = GreenBlink
3 = Solid Green
ForceStatus
INT
Decimal Force Status:

bit .0 = force installed
bit .1 = force active
MinorFaultCount
DINT
Decimal Number of Minor Fault

occurrences since last
reset. This is a 16-bit
unsigned value, so it
loops from 65,535 back to
zero.
MinorFaultProg
BOOL
Minor Fault: Program

Logic Problem
MinorFaultTask
BOOL
Minor Fault: Task Overlap
MinorFaultPort
BOOL
Minor Fault: Serial Port

Problem
MinorFaultBatt
BOOL
Minor Fault: Replace /

Reconnect Battery
Execution
Chapter 3
Execution parameters are included with every Add-On Instruction. See the
Logix5000 Controllers Add-On Instructions Programming Manual,
publication 1756-PM010, for more information on these data elements.
Name:
Data Type:
Usage:
Default:
EnableIn
BOOL
Input
Enable Input:
1 = Normal Scan: monitor Logix CPU
utilization
0 = No action (no EnableInFalse logic is
provided)
EnableOut
BOOL
Output
Enable Output: The EnableOut signal is

not manipulated by this instruction. Its
output state always reflects the EnableIn
input state.
Inf_Tab
SINT
Tab to display (FTView ME)
Inf_Type
STRING_16
L_CPU
Must contain AOI name, used for HMI and

Information S/W
L_CPU
BOOL
Unique Parameter Name for auto discovery
Output
Style: Description:
Associated
Configuration
Parameter
17
Chapter 3
Configurations
(Cfg_)
Configuration data elements are used to set configurable capabilities, features,

and functions of the L_CPU Instruction.
The following Configuration data may be modified by controller application
logic, using the HMI Faceplate, or using the Tag Monitor in
RSLogix 5000 software.
Name:
Data Type:
Associated
Configuration
Parameter
Usage:
Default:
Style:
Description:
Cfg_MainTaskInstance DINT
Input
Decimal
Instance Number (from GSV) of Main

Task (or any other task to monitor for
scan time) (0 ...31)
Cfg_SlotNumber
DINT
Input
Decimal
Controller Slot Number in local

chassis
Cfg_UpdateT
DINT
Input
5 sec
Decimal
Refresh (poll and display) time for all

CPU data
Cfg_WindowT
REAL
Input
1.0 sec
Float
Window time for collecting Task data

(sec)
Because they use arrayed or structured data types, the following Configuration
data elements use L_CPU Add-On Instruction Local Tags. These may be
modified using RSLogix 5000 software or using the HMI Faceplates, but
cannot be modified using controller logic.
Name:
Data Type:
Cfg_Desc
STRING_40
'Logix CPU STRING

Utilization
Monitor'
Description for display on HMI
Cfg_Label
STRING_20
'CPU
STRING
Utilization'
Label for graphic symbol displayed on

HMI
Cfg_SupportInfo
STRING_40
Cfg_Tag
STRING_20
18
Usage:
Local
Default:
Style:
Associated
Configuration
Parameter
Description:
Enter
Software
S/N or
Support
Contract
#
ASCII
Enter your RSLogix 5000 software

serial number or your support contract
number for reference in case you call
Rockwell Automation Technical
Support.
'L_CPU'
STRING
Tagname for display on HMI
Operator Commands,
Maintenance Commands,
Command Readies
(OCmd, MCmd_, Rdy_)
Chapter 3
Maintenance Commands are used by the maintenance personnel at the HMI to

request instruction actions. These Commands are set (latched) by the HMI and
are read and then cleared (unlatched) and acted upon by the L_CPU
instruction, allowing a many-to-one relationship between HMI requestors and
each Command. Commands are implemented as public Input Parameters of
the L_CPU instruction.
Operator Commands
Name:
Data Type:
Usage:
Default:
Style: Description:
OCmd_Enable
BOOL
Input
Edge
Operator Command to enable

collection of data
OCmd_Disable
BOOL
Input
Edge
Operator Command to disable

collection of data
Associated
Configuration
Parameter
Maintenance Commands
Name:
Data Type:
Usage:
Default:
Style: Description:
MCmd_Enable
BOOL
Input
Edge
Maintenance Command to enable

collection of data
MCmd_Disable
BOOL
Input
Edge
Maintenance Command to disable

collection of data
Associated
Configuration
Parameter
19
Chapter 3
Maintenance Command Readies

Each Maintenance Command has a corresponding Ready bit which 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 Maintenance Command
button on the Faceplate.
Associated
Configuration
Parameter
Name:
Data Type:
Usage:
Default:
Rdy_Enable
BOOL
Output
1 = Ready to receive MCmd_Enable

(enable button)
Rdy_Disable
BOOL
Output
1 = Ready to receive MCmd_Disable

(enable button)
20
Style: Description:
Status
(Sts_)
Chapter 3
Status data elements contain device status. The HMI displays these Status
points, and they are available for use by other application logic.
Device Status
Style: Description:
Associated
Configuration
Parameter
Name:
Data Type:
Usage:
Default:
Sts_Enabled
BOOL
Output
1 = CPU data collection has been

Enabled
Sts_Timing
BOOL
Output
1 = Instruction is waiting for Update

Time to complete
Sts_Busy
BOOL
Output
1 = Instruction is getting CPU data from

the controller
Sts_Done
BOOL
Output
1 = Data collection complete, updated

CPU data are in the Ref_Out tag
Sts_MsgErr
BOOL
Output
1 = Message Error, unable to read at

least one metric
Sts_WrongVersion
BOOL
Output
1 = Wrong firmware version (must be

18.x) or controller is not supported
Sts_Timing
BOOL
Output
1 = The instruction is waiting for the

Update Time to complete before
gathering CPU data
Cfg_UpdateT
Sts_MsgErr
BOOL
Output
1 = Message Error, unable to read at

least one metric. Check that the
configured Controller Slot Number
is correct.
Cfg_SlotNumber
Sts_WrongVersion
BOOL
Output
1 = Wrong firmware version or

controller is not supported.
IMPORTANT
The L_CPU Add-On Instruction is
firmware major revision dependent.
You must use the L_CPU_18 instruction
with Revision 18.xx firmware, the
L_CPU_19 instruction with Revision
19.xx firmware, and so on.
SoftLogix controllers and
RSLogixEmulate 5000 controllers are
not supported by the L_CPU Instruction.
21
Chapter 3
Notes:
22
Chapter
HMI Reference
This chapter describes the HMI Graphic Symbols and Faceplate provided for
human-machine interface (HMI) for the L_CPU Instruction.
Graphic Symbols
Graphic Symbols are provided for use on end-user process graphic displays.
L_CPU Graphic Symbols have the following common attributes:
L_CPU Graphic Symbol
Other module Graphic Symbols
Status Indicators
Touch Field to
recall Faceplate
Tooltip with Controller

Name and Path
The L_CPU Graphic Symbol looks like a physical controller and is intended to
be used in a chassis view or network view display with symbols for other
modules including I/O, communication cards and others. The L_CPU
Graphic Symbol has indicators that match the status on the face of the actual
controller and use the same colors and blink states.
The L_CPU Graphic Symbol includes a touch field; clicking the Symbol will
call up the L_CPU Faceplate. Hovering the pointing device pointer over the
Symbol will display its tooltip, giving the Controller name and
communication path.
23
Chapter 4
HMI Reference
Graphic Representation
The Status Indicators on the Graphic Symbol change color and blink state
depending on the controller status.
Indicator
State
Run (Upper Left for ControlLogix 1756)
Green Steady: The controller is in Run or

Remote Run mode
Off: The controller is in Program, Remote
Program or Remote Test Mode
Force (Center Left for ControlLogix 1756)
Off: There are no forces in the Controller

Yellow Blinking: There are forces in the
Controller but forcing is not active
Yellow Steady: Forcing is active (I/O being
forced)
Bat (Lower Left for ControlLogix 1756)
Off: The memory battery is installed and OK

Red Steady: The memory battery is low,
missing or not properly connected
I/O (Upper Right for Control Logix 1756)
Green Steady: Communication with all

configured I/O modules is OK
Green Blinking: The controller is not
communicating with one or more configured
I/O modules
Red Blinking: The controller cannot
communicate with the chassis in which it is
installed
Off: No I/O modules are configured in the
application, or no application is loaded into
the controller
RS232 (Center Right for ControlLogix 1756)
Not used: the L_CPU Instruction does not

monitor serial port activity
OK (Lower Right for ControlLogix 1756)
Green Steady: The controller is OK

Red Steady: The controller has a Major
Fault
24
HMI Reference
Faceplate
Chapter 4
The Logix Control Processor Utilization Faceplate consists of six tabbed

pages. The Operator tab is displayed when the Faceplate is initially called up.
Click the appropriate icon at the top of the Faceplate to access a specific tab.
Communications
Operator
Memory
CPU Usage
Maintenace
Connections
Exit
Help
Operator Tab
Controller Mode
Controller Status
Controller Catalog
Number
Controller Clock
Date and Time
Minor Fault Count
Status of HMI
Communication with
Controller
I/O Communication and I/O
Forcing Status Indicators
Redundant Controller
Status
Controller firmware version
(Major. Minor)
Minor Fault Indicators
Controllers configured
Communication Timeslice
Communication Bar graph
Data Values
Optimized Packet Counts

Communication Bar
graph
25
Chapter 4
HMI Reference
The Operator tab shows the following information:
Controller Mode
Controller Status
Status of HMI Communication with the Controller
I/O Communication and I/O forcing status indicators
The Controllers redundancy status (only displayed for a Controller in a
redundant configuration)
Controller identity information, including catalog number and firmware
major and minor revision
Count of Minor Fault occurrences, and indicators for currently active
Minor Faults of specific classes
The Controllers configured Communication Timeslice value
A nested bar graph and numeric displays showing the approximate
percent CPU available for responding to communications requests (such
as from HMI) (outer bar), and the approximate percent CPU actually
being used for responding to communications requests (inner bar). The
outer bar graph changes color from green to yellow when CPU available
for communications is low, and the inner bar graph changes color from
blue to red when nearly all CPU available for communications is being
used.
Count of RSLinx Optimized Packets currently used, the high-water
value of Optimized Packets used, and the largest Optimized Packet
Instance Number used in the controller.
TIP
The Operator (Home) Tab displays the information most commonly requested by
Rockwell Automation Technical Support when you place a call for support for a Logix
controller. You will also need your software serial number or technical support
contract number. A space is provided for you to record this information on the
Maintenance Tab for ready reference when you call. The Technical Support
Specialist may or may not require information from the other tabs depending on the
nature of the issue.
26
HMI Reference
Chapter 4
Communications Tab
The Communications tab displays diagnostic counters for the RSLinx

Enterprise driver used by the HMI to communicate with the controller.
27
Chapter 4
HMI Reference
CPU Usage Tab
The CPU Usage tab displays the approximate CPU percentage used by each
of the controllers major activities. If there is a Continuous Task running in the
controller, the top segment of the bar graph shows the CPU used by the
Continuous Task. If there is no Continuous Task, the top segment shows the
percentage CPU free (unused).
Note: The usage values may not sum to 100%.
The Main Task Scan Times are for the Task whose instance number is passed
into the L_CPU instruction. This instance number is obtained using a GSV
(built-in) Instruction on the rung which executes the L_CPU Instruction. This
GSV is included if you installed the L_CPU instruction using a Rung Import.
Just enter the name of the controller Task you want to monitor into the GSV
Instruction. (The Task name in the GSV can be changed by online editing.)
28
HMI Reference
Chapter 4
Memory Tab
Total Controller Memory

Usage Bar Graph and
Values
I/O Memory Usage

Bar Graph and Values
Data and Logic Memory

Usage Bar Graph and
Values
Safety Memory Usage

(Visible if Safety
Memory is used
General Memory Usage

Note: Only those memory sections that exist (have non-zero size) are shown
in the graphic above. Each section (I/O Memory, Data and Logic Memory,
General Memory, and Safety Memory) is visible only if the controller returns a
size for it that is non-zero.
The Memory tab displays the size of overall controller memory and the
amount free. For each memory section displayed, the Memory Tab shows:
The total memory allocated to that section

The amount of memory in that section which is used
The amount of memory in that section which is unused
The maximum (high-water) amount of memory used
The largest contiguous block of unused memory
29
Chapter 4
HMI Reference
Connections Tab
Controller
Connection Statistics
Message (MSG) and

Block Transfer
Statistics
The Connections tab displays the number of connections currently being

used, the highest number used, and the total available connections for several
types of data transfers, plus statistics for Message (MSG) instructions using
Unconnected Buffers and Message Cache Entries.
30
HMI Reference
Chapter 4
Maintenance Tab
Data Collection Enable

and Disable Buttons
Data Collection Enabled /

Disabled Status Indicator
Data Collection Progress and
Error Indicators
Data Collection Update

(Poll) Interval (in
seconds)
Other Configuration
data (display only)
Free-format text entry for

recording software serial number,
support contract number or other
support information
The Maintenance tab shows the following information:

An indicator to show whether L_CPU data collection (polling) is
Enabled or Disabled.
An indicator to show when the L_CPU instruction is waiting before the
next data collection (poll) and when a poll is in progress
An indicator to show when a poll is busy or the result of the last poll
(Data Received or Error)
Configuration values, some of which cannot be changed from the
Faceplate
31
Chapter 4
HMI Reference
The following table lists the functions on the Maintenance tab.

Button / Field
Action
Security
Required
Click to enable collection of

controller data.
Code C
IMPORTANT
The L_CPU Instruction
accomplishes its data collection
using Message (MSG) instructions
to the controller (MSG to self),
which uses some controller
communication resources. You
may wish to leave data collection
disabled until it is needed. Some
Faceplate data are monitored
without using the polling
messages and will still be
displayed.
Click to disable collection of
controller data.
Code C
Only data collection via MSG

instructions is disabled. Other data
will still be updated and displayed
on the Faceplate. Data not
updated when collection is
disabled are not displayed.
Update (poll) time for CPU data
(sec)
Enter the interval at which to

collect and update data displayed
on the other Faceplate tabs.
Code C
IMPORTANT
Setting this parameter too low will
result in a flood of Messages
(MSG) to the controller, possibly
impacting control performance. Do
not use a value less than 5
seconds unless instructed to do so
by a Rockwell Automation
Technical Support specialist.
Support Information (Serial # or
Contract #)
32
Enter the Serial Number for your

RSLogix 5000 software or the
contract number for your
TechConnect or other technical
support contract so it is available
for ready reference if you call
Rockwell Automation Technical
Support.
Code E or P
HMI Reference
Chapter 4
Logix CPU Faceplate Help
33
Chapter 4
HMI Reference
Notes:
34
Rockwell Automation Support

Rockwell Automation provides technical information on the Web to assist you in using its products.
At http://www.rockwellautomation.com/support/, you can find technical manuals, a knowledge base of FAQs, technical and
application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the
best use of these tools.
For an additional level of technical phone support for installation, configuration, and troubleshooting, we offer TechConnect
support programs. For more information, contact your local distributor or Rockwell Automation representative,
or visit http://www.rockwellautomation.com/support/.
Installation Assistance
If you experience a problem within the first 24 hours of installation, review the information that is contained in this manual.
You can contact Customer Support for initial help in getting your product up and running.
United States or Canada
1.440.646.3434
Outside United States or

Canada
Use the Worldwide Locator at http://www.rockwellautomation.com/support/americas/phone_en.html, or contact

your local Rockwell Automation representative.
New Product Satisfaction Return

Rockwell Automation tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility.
However, if your product is not functioning and needs to be returned, follow these procedures.
United States
Contact your distributor. You must provide a Customer Support case number (call the phone number above to obtain
one) to your distributor to complete the return process.
Outside United States
Please contact your local Rockwell Automation representative for the return procedure.
Documentation Feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document,
complete this form, publication RA-DU002, available at http://www.rockwellautomation.com/literature/.
Rockwell Otomasyon Ticaret A.., Kar Plaza Merkezi E Blok Kat:6 34752 erenky, stanbul, Tel: +90 (216) 5698400

Copyright 2011 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.

00 L CPU Syslib-Rm017 - En-E

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

00 L CPU Syslib-Rm017 - En-E

Uploaded by

Copyright:

Available Formats

Logix Add-On Instructions and Graphics:

Controller CPU Utilization (L_CPU)

Compatible with the Plant-wide Integrated Architecture

Important User Information

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

This document contains the following changes:

iiiPublication SYSLIB-RM017C-EN-E - October 2011

Version 2.0 of instruction

Publication SYSLIB-RM017C-EN-E - October 2011

Use of this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Publication SYSLIB-RM017C-EN-E - October 2011

Publication SYSLIB-RM017C-EN-E - October 2011

Use of this Document

This document provides a programmer with details on the L_CPU instruction

Conventions and Related

Set and Clear

viiPublication SYSLIB-RM017C-EN-E - October 2011

The bit is set to 1 (ON)

The bit is cleared to 0 (OFF)

Edge and Level

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

Action (enable) is triggered by input being at a level (in a

All Operator Commands (OCmd_) and Maintenance Commands

Publication SYSLIB-RM017C-EN-E - October 2011

This instruction has Program Commands (PCmd_) which are

Relay Ladder Rung Condition

If the rung-in condition to an input instruction is true, the controller evaluates

The rung-in condition is reflected in the EnableIn parameter and

Publication SYSLIB-RM017C-EN-E - October 2011

The Pre-scan process performs the Process Add-On Instructions

Publication SYSLIB-RM017C-EN-E - October 2011

Function Block States

Pre-scan for function block routines is the same as for relay

Instruction first scan

Instruction first scan refers to the first time an instruction is

Instruction first run

Instruction first run refers to the first time the instruction

Every function block instruction also includes EnableIn and EnableOut

Publication SYSLIB-RM017C-EN-E - October 2011

When programming in function block, restrict the range

Entering Text in FactoryTalk View SE

Publication SYSLIB-RM017C-EN-E - October 2011

The L_CPU (Logix Controller CPU Utilization) Add-On Instruction monitors

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

Publication SYSLIB-RM017C-EN-E - October 2011

These items are displayed on several Faceplate tabs, with summary

The instruction sets up a monitoring window over which CPU utilization

Publication SYSLIB-RM017C-EN-E - October 2011

Publication SYSLIB-RM017C-EN-E - October 2011

The L_CPU Instruction has no commands or outputs intended to control

The following table explains the handling of instruction execution conditions.

EnableIn False (False Rung)

The L_CPU Instruction has no EnableInFalse

Powerup (Pre-Scan, First Scan)

Logic is set up to ensure the Window Time

Postscan (SFC Transition)

No SFC Postscan logic is provided.

Refer to the Logix5000 Controllers Add-On Instructions Programming

Publication SYSLIB-RM017C-EN-E - October 2011

The Add-On Instruction in RSLogix 5000 has

The Faceplate in FactoryTalk View has

Publication SYSLIB-RM017C-EN-E - October 2011

Faceplate Tab Usage: