Logix 5000 Controllers Information and Status: Programming Manual
Logix 5000 Controllers Information and Status: Programming Manual
Logix 5000 Controllers Information and Status: Programming Manual
ATTENTION: 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.
IMPORTANT Identifies information that is critical for successful application and understanding of the product.
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.
ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to potential Arc Flash. Arc Flash
will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL Regulatory requirements for safe work practices and
for Personal Protective Equipment (PPE).
Grammatical and editorial style changes are not included in this summary.
Global changes
Change Topic
Updated branding. Throughout
Chapter 1
Connections Introduction ................................................................................................ 9
Inhibit a Connection .................................................................................. 9
Manage a connection failure ..................................................................... 11
Configure a major fault to occur ......................................................... 12
Monitor the health of a module .......................................................... 13
Chapter 2
Determine controller memory Introduction ............................................................................................... 17
information View data usage ......................................................................................... 17
Capacity tab for controllers that divide memory ............................... 18
Capacity tab for controllers with common memory area ................. 18
Estimate memory information offline for controllers with divided
memory ................................................................................................. 19
View run-time memory information for controllers with divided
memory ................................................................................................ 20
View the maximum and used Ethernet nodes for a controller ........ 21
Write logic to get memory information .................................................. 22
Get memory information from the controller .................................. 22
Choose the memory information .......................................................23
Convert INTs to a DINT...................................................................... 24
Chapter 3
Controller logging Introduction .............................................................................................. 25
Controller log ............................................................................................ 25
Controller log header .......................................................................... 26
Controller log entry ............................................................................. 26
Entries captured in the controller log ............................................... 27
Controller log buffer ........................................................................... 28
Controller log files and the removable media ................................... 28
Writing the controller log to the SD card .......................................... 28
Automatic save .............................................................................. 29
Save on demand ............................................................................ 30
Controller logging counters ................................................................ 31
Total entry count ............................................................................ 31
Chapter 4
Change detection Introduction ...............................................................................................45
Controller change detection .....................................................................45
ChangesToDetect .................................................................................45
AuditValue ............................................................................................47
ChangesToDetect format ................................................................... 48
Change detection in the Logix Designer application ............................. 49
Component tracking ................................................................................. 49
Track the state of components and constant tags ............................. 51
View tracked components ................................................................... 51
Retrieve the tracked state value using a Message instruction.......... 51
Chapter 5
Access status information Introduction ............................................................................................... 53
Status of S:FS when the project has an SFC ............................................. 53
Get and set system data .............................................................................54
In this manual This manual describes how Logix 5000 controllers use connections with other
devices. This manual also describes status keywords and how to get controller
information, such as memory resources. This manual is one of a set of related
manuals that show common procedures for programming and operating
Logix 5000 controllers.
For a complete list of common procedures manuals, refer to the Logix 5000
Controllers Common Procedures Programming Manual, publication 1756-
PM001.
The term Logix 5000 controller refers to any controller based on the Logix
5000 operating system.
Studio 5000 environment The Studio 5000 Automation Engineering & Design Environment® combines
engineering and design elements into a common environment. The first
element is the Studio 5000 Logix Designer® application. The Logix Designer
application is the rebranding of RSLogix 5000® software and will continue to
be the product to program Logix 5000™ controllers for discrete, process,
batch, motion, safety, and drive-based solutions.
Legal notices Rockwell Automation publishes legal notices, such as privacy policies, license
agreements, trademark disclosures, and other terms and conditions on the
Legal Notices page of the Rockwell Automation website.
You can view a full list of all open source software used in this product and
their corresponding licenses by opening the oss_license.txt file located your
product's OPENSOURCE folder on your hard drive. This file is divided into
these sections:
• Components
Includes the name of the open source component, its version number,
and the type of license.
• Copyright Text
Includes the name of the open source component, its version number,
and the copyright declaration.
• Licenses
Includes the name of the license, the list of open source components
citing the license, and the terms of the license.
The default location of this file is:
Connections
Introduction A Logix 5000 controller uses connections for most, but not all, of its
communication with other devices.
Term Definition
Connection A communication link between two devices, such as between a controller and an
I/O module, PanelView terminal, or another controller.
Connections are allocations of resources that provide more reliable
communication between devices than unconnected messages. The number of
connections that a single controller can have is limited.
Configuring the controller to communicate with other devices in the system
indirectly determines the number of connections the controller uses. These
communication types use these connections:
• I/O modules
• Produced and consumed tags
• Program parameters
• Certain types of Message (MSG) instructions (not all types use a connection)
Requested packet The RPI specifies the period at which data updates over a connection. For
interval (RPI) example, an input module sends data to a controller at the RPI assigned to the
module.
• Typically, an RPI is configured in milliseconds (ms). The range is 0.2 ms
(200 microseconds)…750 ms.
• If a ControlNet network connects the devices, the RPI reserves a slot in the
stream of data flowing across the ControlNet network. The timing of this slot
may not coincide with the exact value of the RPI, but the control system
guarantees that the data transfers at least as often as the RPI.
Path The path describes the route that a connection takes to get to the destination.
Typically, the path for a connection is defined when a device is added to the I/O
Configuration folder of the controller.
Inhibit a Connection In some situations, such as when initially commissioning a system, it is useful
to disable portions of a control system and enable them as they are connected
to the control system. Inhibiting individual modules or groups of modules
prevents the controller from trying to communicate with the modules.
ATTENTION: Inhibiting a module breaks the connection to the module and prevents
communication of I/O data.
To Then
Communicate with the module Do not inhibit the module. Clear the Inhibit Module
check box.
Prevent communication with the module Inhibit the module. Select the Inhibit Module check
box.
Manage a connection If the controller loses communication with a module, data from that device
does not update. When this occurs, the logic acts on the data in ways that may
failure or may not be correct. Program the controller to manage faults safely and
efficiently.
See also
Configure a major fault to occur on page 12
Configure a major fault to To force a module to generate a major fault in the controller if it loses
connection with the controller, configure a major fault to occur. This
occur interrupts the execution of logic and runs the Controller Fault Handler. If the
Controller Fault Handler does not clear the fault, the controller shuts down.
See also
Logix 5000 Controllers Major and Minor Faults Programming Manual,
publication no. 1756-PM014
Monitor the health of a Monitor the module status if the module is not configured to generate a
major fault. If a module loses its connection to the controller, outputs go to
module their configured faulted state. The controller and other I/O modules continue
to operate based on old data from the module.
• The I/O status indicator on the front of the controller flashes green.
• A Warning ( ) icon shows over the I/O configuration folder and over
the device that has timed out.
• A module fault code is produced, which is accessible through:
• Module Properties window for the module.
• GSV instruction.
This table describes the meaning of the I/O status indicator on the front of the
controller.
Value Meaning
0 Status Indicator off. No Module objects
are configured for the controller (there
are no modules in the I/O Configuration
section of the controller organizer).
1 Flashing red. None of the Module objects
are Running.
2 Flashing green. At least one Module
object is not Running.
3 Solid green. All the Module objects are
Running.
Example:
This rung checks the status of an I/O connection. The controller checks the
entry status of the connection; any value other than 4 indicates that the
connection is not functioning correctly. When the controller detects an error,
the error code and information is trapped, and the controller tries to re-
establish the connection.
Introduction Depending on the type of controller, the memory of the controller is divided
into several areas.
This controller Stores this In this memory
ControlLogix 5570 I/O tags I/O memory
GuardLogix 5570S Produced / Consumed tags
CompactLogix 5370
Communication via Message (MSG)
Compact GuardLogix 5370S
instructions
ControlLogix 1756-L5x, L6x
Communication with workstations
GuardLogix 1756-L6xS
Communication with polled (OPC/DDE) tags
that use RSLinx software1
Tags other than I/O, produced, or consumed Data and logic
tags memory2
Logic routines
Communication with polled (OPC/DDE) tags
that use RSLinx software1
CompactLogix 1769-L2x, L3x These controllers do not divide their memory. They store all elements
SoftLogix5800 in one common memory area.
CompactLogix 5380
CompactGuardLogix 5380
CompactLogix 5480
ControlLogix 5580
GuardLogixlLogix 5580
(1) To communicate with polled tags, the controller uses both I/O data and
logic memory.
(2) 1756-L55M16 controllers have an additional memory section for logic.
View data usage In the Logix Designer application, the Capacity tab (formerly the Memory
tab) on the Controller Properties dialog box shows data usage in the
controller. The data displayed on the Capacity tab depends on the controller.
Tip: Refer to the Memory information table to see whether a controller divides its
memory or has one common memory area.
See also
Memory information table on page 17
Capacity tab for controllers The Capacity tab for controllers that divide memory shows I/O memory and
Data and Logic memory separately. For each area of controller memory, the
that divide memory tab shows the consumed and available memory in bytes.
Capacity tab for controllers The Capacity tab for controllers that store elements in one common area
differs slightly from the Capacity tab for other controllers.
with common memory area
Instead of describing consumed memory in bytes, the Capacity tab shows
logical program blocks which represent units of executable code. The Capacity
tab shows project size in blocks compared to the specified product capacity in
blocks to determine if the project can be downloaded to the controller. If the
size of the project exceeds the controller capacity available, a message appears
that states the overage size in blocks. When the project size exceeds the
memory available, the project does not download to the controller.
Block units are only used for application source code sizes. Data structures
and messages are still described in bytes.
IMPORTANT Although block sizes are not physically equivalent to the bytes measured in
controllers with divided memory controllers, in general, applications that fit in a
divided memory controller should fit in the same controller with one common memory
area.
Estimate memory For controllers with divided memory, the applications in the project have a
close correlation between the size of the source code and the physical memory
information offline for in the controller. To estimate how much controller memory a project requires,
controllers with divided use the Estimate button on the Capacity tab. It estimates the number of bytes
of:
memory
• Free (unused) memory.
• Used memory.
• Largest free contiguous block of memory.
Tip: This section only applies to controllers with divided memory. Refer to the Memory
information table for a list of controllers with divided memory. Refer to Capacity tab
controllers with common memory area for information about the other controllers.
See also
Memory information table on page 17
Capacity tab for controllers with common memory area on page 18
View run-time memory When online with a controller with divided memory, the Capacity tab shows
the actual memory usage of the controller. While the controller is running, it
information for controllers uses additional memory for communication. The amount of memory the
with divided memory controller needs varies depending on the state of the communication.
The Capacity tab of the controller includes a Max Used entry for each type of
memory. The Max Used values show the peak memory usage as
communication occurs.
Tip: This section only applies to controllers with divided memory. Refer to the Memory
information table for a list of controllers with divided memory. Refer to Capacity tab
controllers with common memory area for information about the other controllers.
See also
Memory information table on page 17
Capacity tab for controllers with common memory area on page 18
View the maximum and Some controllers have limits on the number of Ethernet nodes they support in
the I/O Configuration tree. When a device is added directly to the Ethernet
used Ethernet nodes for a I/O configuration, it is counted toward the node limitation of the controller.
controller The Capacity tab of the Controller Properties dialog box shows the current
number of used Ethernet nodes in the I/O Configuration tree and the
maximum number of Ethernet nodes supported by the controller.
When the controller is online, the controller enforces the node count, and the
node count exceeds the limit:
Write logic to get memory Use a Message (MSG) instruction to get memory information from the
controller.
information
Tip: This procedure applies to controllers with divided memory. The Logix Designer application
determines capacity information for controllers that store elements in one common area.
Get memory information IMPORTANT The information in this section is not applicable to CompactLogix 5380,
CompactLogix 5480, ControlLogix 5580, Compact GuardLogix 5380, and
from the controller GuardLogix 5580 controllers. In these controllers, the memory used
attributes are not supported or accessible.
Choose the memory This table lists the information that the MSG instruction returns to INT_array
information (destination tag of the MSG).
Tip: This procedure applies to controllers with divided memory. The Logix Designer application
determines capacity information for controllers that store elements in one common area.
IMPORTANT The controller returns the values in 32-bit words. To see a value in bytes, multiply it
by 4. If a controller does not divide its memory, the values show up as I/O memory.
For the 1756-L55M16 controller, the MSG instruction returns two values for each logic
memory category. To determine the free or total logic memory of a 1756-L55M16
controller, add both values for the category.
Convert INTs to a DINT The MSG instruction returns each memory value as two separate INTs.
In this example, the COP instruction produces the 32-bit value that represents
the amount of free I/O memory, in 32-bit words.
Example: Convert INTs to a DINT.
Controller logging
Introduction Use the controller logging feature to detect and log changes made to
Logix5000 controllers without adding any auditing software. With controller
logging, the controllers:
Controller log header When the controller creates a log file on the removable media, it includes
some header information. The header information includes these items.
• Record Number
• Time of Occurrence (UTC - 24 hour clock)
• Entry Description
• Windows User Name
• Workstation Name
• FactoryTalk User ID (if available)
• Extended Information
• Change Detection Audit Value
This example shows controller log entries in a spreadsheet. Controller log files
are stored in plain text files in TSV format, so no special tools are required to
read them. Open them in any text editor, or in a spreadsheet application such
as Microsoft Excel.
Entries captured in the These entries are detected and logged by the controller. These events are
described in more detail in Controller Log Events.
controller log
Tip: In Logix Designer versions 30 and later, audit log entries also appear in the controller log. Audit
log entries describe events such as changes to component properties, edits in a routine, and
changes to tag values. The audit log is used for auditing by the FactoryTalk® AssetCentre.
• Project downloaded
• Project loaded from removable media
• Project stored to removable media
• Online edits modified controller program
• Partial import online completed or Transaction committed
• I/O forces enabled, disabled, removed, or modified
• SFC forces enabled, disabled, removed, or modified
• Firmware update
• Constant tag data changed
• Multiple constant tag data changed
• Change to constant tag configuration reset
• Mode change
• Major fault, major fault cleared
• Program properties modified
• Task properties modified
• Controller timeslice modified
• Removable media inserted or removed
• Safety signature created or deleted
• Safety locked or unlocked
• Custom entry: User-defined logic to create a log entry, with user-
defined entry description and extended information
• Safety signature delete inhibited in Run mode
• Safety signature delete allowed in Run mode
See also
Controller log events on page 37
Controller log buffer For the Compact GuardLogix 5370, CompactLogix 5370, ControlLogix 5570,
and GuardLogix 5570 controllers, the controller keeps up to 100 log entries
buffered in its internal memory.
Configure the controller to write the buffered entries to the removable media
when its internal buffer is 80% full, or command the controller to write the
buffered entries to the removable media with a message instruction. This
procedure is detailed below. Once a log entry is written to the removable
media, it is removed from the buffer.
Controller log files and the When written to the removable media, controller logs are stored in plain text
files in the Tab Separated Value (TSV) format. Each time the controller writes
removable media entries to the CompactFlash card, the entries are appended to the text file
until the file reaches 1 MB in size. At this point, the controller creates a new
text file.
The controller does not attempt to write log entries to a full removable media
card. If the removable media becomes full, the system behaves as if the
removable media is not present.
Controller log files are stored in plain text files in the TSV format, so no
special tools are required to read them. Open them in any text editor, or in a
spreadsheet application such as Microsoft Excel.
Writing the controller log to The controller log can be written to the Secure Digital (SD) card either
automatically or on demand.
the SD card
Tip: Some Logix 5000 controllers support additional types of removable media that can be used to
write the controller log entries. Refer to the Logix 5000 controller documentation for information
regarding the type of removable media the controller supports.
Automatic save Configure the controller to automatically write buffered log entries to the SD
card when the controller's internal log entry buffer becomes 80% full.
Alternately, configure the controller to write the buffered entries before a
firmware update. To write buffered entries before a firmware update, send a
message instruction to the controller using a CIP Generic message type and a
service type of Controller Log Automatic Write Set. Sending a value of 0 turns
off automatic writes, and sending a value of 1 turns on automatic writes. By
default, entries are not automatically written.
A rung of logic that performs this configuration and the configuration dialog
box of the message instruction are shown in these examples.
Example: Automatic Save Set ladder instruction and configuration dialog box
Retrieve the current state of the automatic write setting by using a CIP
Generic message type and a service type of Controller Log Automatic Write
Get. Use this rung of ladder logic and message instruction configuration to
get this value.
Example: Automatic Save Get ladder instruction and configuration dialog box
Save on demand Command the controller to write buffered entries to the SD card by using a
message instruction with a CIP Generic message type and a service type of
Controller Log Write To Media.
A rung of ladder logic that sends this message and the configuration of the
message instruction are shown in these examples.
Example: Write Buffered Entries to the SD Card ladder instruction and
configuration dialog box
Controller logging counters Three counters, listed in the following table, provide real-time statistics about
modifications to the controller.
Counter Name Description Access
Total Entry Count Number of entries added to the log since the last firmware GSV/SSV
update.
Unsaved Entry Count Number of entries in controller RAM not yet written to the GSV
CompactFlash card.
Modify Execution Count Count that specifically tracks modifications that can GSV/SSV
change behavior of a running controller. A subset of entries
increment this count.
Total entry count Total Entry Count is the number of controller entries that have been added
since the last firmware update. This counter increments after any entry is
added to the log, and it is written to the log in the Record Number field. Use a
Set System Value (SSV) instruction to set it to a known value. This can be
useful, for example, for monitoring system changes during a production run.
This rung of ladder logic shows how to retrieve the Total Entry Count by using
a Get System Value (GSV) instruction.
Example: Total Entry Count by using a Get System Value (GSV) ladder
instruction
This rung of ladder logic shows how to set the Total Entry Count to a known
value (in this example, 0) by using an SSV instruction.
Example: Set the Total Entry Count to a Known Value ladder instruction
Unsaved entry count The Unsaved Entry Count is the number of log entries that are in controller
memory but have not yet been stored to the CompactFlash card.
This counter value is available via a GSV instruction, and can range from
0…100, the maximum number of entries that the controller can buffer.
Example: Retrieve the Unsaved Entry Count using a Get System Value (GSV)
ladder instruction
Execution modification The Execution Modification Count tracks the number of changes that occur
that can change the behavior of a running controller. Configure the counter
count to include or exclude force changes.
This example rung of ladder logic shows how to retrieve the Execution
Modification Count by using a GSV instruction.
This rung of ladder logic shows how to set the Execution Modification Count
to a known value.
Log file storage When a log file is written to the CompactFlash card, it is stored at
\Logix\XXXXXXXX\Logs\VYY_ZZ, where XXXXXXXX is the eight-digit
serial number of the controller and YY_ZZ is the revision number of the
firmware (major_minor revision).
When there are 1000 files larger than 1 MB, no more logs are created.
However, the controller searches for the file name with the smallest possible
sequence number that it can create or write to. For example, if a user deletes
files 001…100 but leaves the rest, the controller starts creating logs again
starting at a sequence number of 001. If there are already 1000 log files and a
user deletes log entries out of file 005, the controller writes the next log entries
to that file. The controller starts at 000 and looks for the first file that does not
exist or is less than 1 MB in size.
Each time the controller opens a log file for writing, it creates a back-up file
that is a copy of the log file before the write. This file is called Backup.txt. The
controller overwrites the backup every time it opens a log file is opened for
writing.
Log file format This table lists the information that is contained in the controller log file.
Content Description Format
Time Controller's GMT time MMM-DD-YY HH:MM:SS
24-hour time
Entry Entry Description (defined in Entry List
section)
User Name User's login ID Windows domain name with display
name if available
Workstation Name User's computer name Computer Name
FactoryTalk ID User's FactoryTalk login ID Alphanumeric characters
The log file is formatted in UTF-16, and has a file extension of .txt. Double-
clicking the file opens it in Notepad on most systems. However, since it is
formatted as Tab Separated Values (TSV), it also opens correctly in a
spreadsheet application, like Microsoft Excel.
See also
Change detection on page 49
Create Custom Log Entries Use a message instruction to add custom entries to the controller log. The
message instruction uses a CIP Generic message type and a service type of
Controller Log Add Entry.
Example: Send the Message ladder instruction, Controller Log Add Entry
configuration dialog box, and Data Type dialog box.
Sample Ladder Logic File The Logix Designer application contains a controller logging sample ladder
file. If the sample files were installed during the installation, open the sample
files from the Help menu. On the Help menu, select Vendor Sample Projects.
Controller Log Events This table describes the events that the controller stores in the controller log.
Tip: In Logix Designer versions 30 and later, audit log entries also appear in the controller log. Audit
log entries describe events such as changes to component properties, edits in a routine, and
changes to tag values. The audit log is used for auditing by the FactoryTalk® AssetCentre.
(1) In versions 20 and later, the Change Detection Audit Value column is
included in the controller log. This column is used to record the Audit Value
for Change Detection.
(2) In versions 20 and later, this value in the controller log equates to
Transaction committed in the Change Detection mask.
(3) This feature only applies for the Compact GuardLogix 5380, CompactLogix
5380, CompactLogix 5480, ControlLogix 5580, and GuardLogix 5580
controllers.
Change detection
ChangesToDetect The ChangesToDetect mask is a 64-bit value. Each bit of the ChangesToDetect
mask corresponds to a particular event that could cause the Audit Value to
change. See ChangeToDecect format.
Some events always update the audit value when they occur. For example, the
audit value changes when a project is downloaded to the controller, or when
ChangesToDetect is reconfigured. These types of events are not included in
the ChangesToDetect mask.
Use the Set System Value (SSV) instruction to write to the ChangesTo Detect
attribute and the Get System Value (GSV) instruction to read the ChangesTo
Detect attribute programmatically.
Tip: Rockwell recommends using the DINT[2] data type to avoid limitations when working with LINT
data types in Rockwell Automation controllers.
See also
ChangesToDetect Format on page 48
AuditValue Use the Get System Value (GSV) instruction to read the AuditValue attribute
programmatically.
Use the Message Configuration dialog box to read the AuditValue attribute
through CIP Generic Messages. For complete information on how to access
data using an MSG instruction, refer to the Logix 5000 Controllers Messages
Programming Manual, publication no. 1756-PM0012.
Use these settings to read the Audit Value attribute using the Message
Configuration.
To get AuditValue in this property Type or select
Message Type CIP Generic
Service Type Audit Value Get
Source Leave blank
Destination tag_name of type DINT[2] or LINT 1
This tag contains the AuditValue for the controller.
See also
Logix 5000 Controllers Messages Programming Manual, publication
no. 1756-PM012, publication no. 1756-PM012
Change detection in the Use the Security tab in the Controller Properties dialog box (available in
versions 20 and later of the application) to configure Change Detection.
Logix Designer application
To edit the Changes To Detect field, type a new value. To select the events to
monitor for changes from a list, select Configure to open the Configure
Changes to Detect dialog box.
See also
Controller Change Detection on page 45
Component tracking Use component tracking to determine whether tracked components have
changed. Like change detection, component tracking indicates changes to a
project, but at the component level. The Logix Designer application creates a
unique signature for each tracked component and compiles those signatures
into one overall tracked value to indicate their current state. Component
tracking applies to:
Track the state of Designate project components for tracking to monitor the current state of a
component. Use the following instructions to track the state of a routine, an
components and constant Add-On Instruction, an I/O module, or a constant tag.
tags
To track the state of a component:
1. In the Controller Organizer, highlight the component to track.
2. Right-click and select Include in tracking group.
3. To stop tracking a component, right-click and select Include in
tracking group again.
Tip: When using the tracked state value to verify that code in a tracked routine is being
executed, make sure to track all the routines that call the tracked routine, up to and
including the main routine. Tracking all components that call the tracked routine helps to
prevent a user from modifying the project so that the tracked routine is no longer called.
View tracked components After selecting project components for tracking, check project component
status in the Tracked Components dialog box, which is accessible on the
Controller Properties dialog box - Security tab.
Retrieve the tracked state Use a Message (MSG) instruction to retrieve the tracked state value. When the
controller receives the MSG instruction, it calculates the tracked state value
value using a Message and stores it in a destination tag.
instruction Tip: When using the tracked state value to verify that code in a tracked routine is being executed,
make sure to track all the routines that call the tracked routine, up to and including the main
routine. Tracking all components that call the tracked routine helps to prevent a user from
modifying the project so that the tracked routine is no longer called.
Introduction The controller supports status keywords inserted in logic for monitoring
specific events.
Status of S:FS when the The state of S:FS depends on the status of the SFC.
project has an SFC • When using S:FS in an action of a sequential function chart (SFC),
S:FS is set (on) for one scan each time the step goes active. S:FS =
step_name.FS.
• If the SFC calls a routine, S:FS is set (on) for one scan each time the
step that calls the routine goes active. S:FS = step_name.FS.
If the SFC does not call a routine, S:FS is set (on) for the first scan of
the task.
Example: SFC Calls a Ladder Diagram
Get and set system data The controller stores system data in objects. There is no status file, as in the
PLC-5 controller. Use the GSV/SSV instructions to get and set controller
system data that is stored in objects.
To create a GSV/SSV instruction, use Logix Designer online help to find the
required information, and create the instruction in the Logix Designer
application. The following summary describes the steps.
• Open the online help in Logix Designer application to find the object
and data type to use in the GSV/SSV instruction.
• In the Logix Designer application, create a tag for the value of the
attribute.
• In the Ladder Logic editor, create the GSV/SSV instruction.
6. In the list of attributes for the object, identify the attribute to access.
For attribute information, see the Logix 5000 Controllers General
Instruction Reference Manual, publication no. 1756-PM003.
7. In Logix Designer application, create a tag for the value of the
attribute.
If the data type of the attribute is Then
One element (for example, DINT) Create a tag for the attribute.
More than one element (for example, • Create a user-defined data type that matches
DINT[7]) the organization of data that is used by the
attribute.
• Create a tag for the attribute and use the data
type identified for the object.
At the first scan, the following rung of logic gets the DateTime attribute of the
WallClockTime object and stores it in the wall_clock tag, which is based on a
user-defined data type.
For more GSV/SSV information, see the Logix 5000 Controllers General
Instructions Reference Manual, publication no. 1756-RM003.
See also
Logix 5000 Controllers General Instructions Reference Manual,
publication no. 1756-RM003
Literature Library Find installation instructions, manuals, brochures, and technical data publications. rok.auto/literature
Product Compatibility and Download Center Get help determining how products interact, check features and capabilities, and rok.auto/pcdc
(PCDC) find associated firmware.
Documentation feedback
Your comments help us serve your documentation needs better. If you have any suggestions on how to improve our content, complete the form at
rok.auto/docfeedback.
Rockwell Automation maintains current product environmental information on its website at rok.auto/pec.
Allen-Bradley, expanding human possibility, Logix, Rockwell Automation, and Rockwell Software are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Rockwell Otomayson Ticaret A.Ş. Kar Plaza İş Merkezi E Blok Kat:6 34752, İçerenkÖy, İstanbul, Tel: +90 (216) 5698400 EEE YÖnetmeliğine Uygundur